Bug 342139 - Kontact when opening the first time shows only half the side bar in summary.
Summary: Kontact when opening the first time shows only half the side bar in summary.
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: summary (show other bugs)
Version: 5.2.2
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-22 22:17 UTC by stakanov.s
Modified: 2017-06-23 22:29 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
the side bar is not reppresented normally (60.80 KB, image/jpeg)
2014-12-22 22:17 UTC, stakanov.s
Details
side bar (76.57 KB, image/png)
2015-10-20 23:34 UTC, Andrey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stakanov.s 2014-12-22 22:17:03 UTC
Created attachment 90093 [details]
the side bar is not reppresented normally

When you open the summary for the first time, no matter if full screen or in automatic with smaller size, the summary window displays the menue bar only to its half. This persists if you use the sidebar but can be "fixed" if you maximize or minimize and then maximize the window. It is minor, but it is an irritating bug for eldery people (you find them working with the side bar this way because they do not know how to set it right). It is also ugly, therefore, why do we have such a nice summary view if it has this bug, right?
 
I can confirm this independently of the videodriver and size, for nouveau driver with nvidia, with the proprietary nvidia driver, with intel HD video driver, with 64 bit and with 32 bit. To better understand what I am speaking about I join a snapshot. That said, it is IMO minor but it would be nice if it would at least not "migrate" to the version of KDE5. Currently it persists since...I think 4.7 or so.
Comment 1 Nicolas 2015-03-01 11:36:25 UTC
I can confirm this bug. I think that happens when one uses a higher DPI setting than usual (I have set 120).
Resizing the window vertically fixes the problem, but it will reoccur on every startup.
Comment 2 Tim Ruffing 2015-08-18 03:52:31 UTC
The same happens if the scaling factor of the new high DPI settings is set to 1.5.
(see http://blog.davidedmundson.co.uk/blog/high_dpi_again)

I guess the reason is that this scaling factor just changes the font DPI? The sidebar works fine with an integer scaling factor; I tried 2.
Comment 3 Nicolas 2015-10-06 09:05:57 UTC
This bug is still present in Kontact 5.0.1 (KDE Applications 15.08.1)
Comment 4 stakanov.s 2015-10-06 09:24:59 UTC
I can confirm this bug being present also in the latest opensuse beta "leap".
Comment 5 Nicolas 2015-10-06 12:41:42 UTC
After inspecting this a little, i found the following behaviour in Navigator::sizeHint() (in kontact/src/iconsidepane.cpp)
At start siteHint() calculates different values for rect().width() and contentsRect().width() than after resizin the window

start (first 4 calls to sizeHint()): 
maxWidth: 102, rect().width(): 74, contentsRect().width(): 70

later (when resizing):
maxWidth: 102, rect().width(): 106, contentsRect().width(): 102

I hope this is helpful..
Comment 6 Andrey 2015-10-20 23:30:52 UTC
Confirm that on KDEPIM 15.08.01 [Gentoo Linux, amd64]
It happens every time when I start Kontact.
Comment 7 Andrey 2015-10-20 23:34:12 UTC
Created attachment 95064 [details]
side bar
Comment 8 stefanprobst 2016-07-09 06:42:26 UTC
This is still present in 16.04.2
To restore the correct size of the sidebar, right-click -> show icons only -> right click -> show icons & text. But on next start, the incorrect size is restored again.
Comment 9 stakanov.s 2016-07-09 08:02:12 UTC
it also helps (as usual) to detach the window from full-screen and then to go back to full screen.
Comment 10 Gery 2016-08-19 18:14:40 UTC
Looks like this bug has been fixed with Applications 16.08.
Comment 11 Gery 2016-08-19 18:15:00 UTC
*** This bug has been confirmed by popular vote. ***
Comment 12 Denis Kurz 2017-06-23 22:29:57 UTC
Reports suddenly stopped after Gery announced that the bug was fixed in 16.08. I close here and with the option to reopen if Gery was wrong.