Bug 297763 - Pager do not maintain row/column settings
Summary: Pager do not maintain row/column settings
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-pager (other bugs)
Version First Reported In: 4.7.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-09 09:28 UTC by rgb.mldc
Modified: 2012-06-02 21:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 4.8.3
Sentry Crash Report:


Attachments
Screen shot that shows the change (10.33 KB, image/png)
2012-04-09 09:28 UTC, rgb.mldc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rgb.mldc 2012-04-09 09:28:43 UTC
Created attachment 70253 [details]
Screen shot that shows the change

I have the pager widget on a vertical panel, configured as one column. Every now and then, without a clear trigger, when I log-in on my system I find that setting changed to four columns as you can see on the attached screen shot, so I need to change the setting again. 

This problem do not happens all the time, but sooner or later (more sooner than later) it happens.
Comment 1 Francisco 2012-04-11 00:07:02 UTC
I have the same problem using kde 4.7.4 on Debian wheezy, but with 9 desktops in 3 rows (3x3 grid). The configuration changes sometimes (very often) to 2 rows when i log in.
Comment 2 Stefan Schwarzer 2012-05-10 22:21:50 UTC
I see similar behavior (debian wheezy, kde 4.7.4, Dell E6410, Nvidia NVS3100M/nouveau), my pager is of 4 (vertical) x 1 (horizontal) dimension on a vertical panel at the left of the screen. Often the behavior is triggered by resolution changes (attaching an external moritor/projector). At the same time other scary things happen as the panel does not redraw properly when high resolution is restored, etc. I have seen all these effects also at earlier kde versions.
Comment 3 rgb.mldc 2012-05-10 22:34:22 UTC
Since I switched to KDE SC 4.8.x (now, 4.8.3) some weeks ago, the problem did not happen again. 

Just in case I'm not closing this yet (I'll wait a bit more), but it seems fixed now.
Comment 4 Myriam Schweingruber 2012-06-02 21:55:48 UTC
Closing based on comment #3