Bug 317788 - Instance Message Settings window is vertically oversized and unresizable
Summary: Instance Message Settings window is vertically oversized and unresizable
Status: RESOLVED DUPLICATE of bug 308199
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: contactlist (show other bugs)
Version: 0.6.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-03 16:20 UTC by Siddhartha
Modified: 2013-04-06 18:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot showing improper window size (124.79 KB, image/png)
2013-04-03 16:21 UTC, Siddhartha 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Siddhartha 2013-04-03 16:20:47 UTC 
The settings window goes beyond the screen space, and I'm not able to resize it vertically.

Reproducible: Always

Steps to Reproduce:
1. Open Telepathy Contact List
2. Open Instance Message Settings from settings-button
Actual Results:  
Window is extended beyond screen, and is unresizable vertically. Horizontal resizing works aright.

Expected Results:  
Window should have proper dimensions and should be vertically resizable as well.
Comment 1 Siddhartha 2013-04-03 16:21:54 UTC 
Created attachment 78615 [details]
Screenshot showing improper window size
Comment 2 Roman 2013-04-06 11:06:56 UTC 
It goes beyond the screen due to huge height or/and kde/qt related problem, I guess.
Minimal height is a problem, yes, it's too high. I assume, this was made due to General settings module, which could be remastered.
Comment 3 David Edmundson 2013-04-06 11:09:17 UTC 
Am I right in thinking it works when opened from SystemSettings but not when opened from the contact list?
Comment 4 Siddhartha 2013-04-06 15:13:52 UTC 
@David: yes thats right, it works properly from the System Settings
Comment 5 David Edmundson 2013-04-06 18:19:55 UTC 

*** This bug has been marked as a duplicate of bug 308199 ***