Bug 10561 - Desktop switch pager in KDE does not remember number of rows and (re-)sets it to 1
Summary: Desktop switch pager in KDE does not remember number of rows and (re-)sets it...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-18 22:23 CEST by darkduck
Modified: 2015-03-31 16:05 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description darkduck 2013-06-18 22:23:28 CEST 
Description of problem:
Upon each login, Desktop Pager on the panel resets number of rows to 2, even when it is specifically set to (presumably default) value 2 in kwinrc


Version-Release number of selected component (if applicable):
KDE 4.10, 64-bit

How reproducible:
On each KDE start

Steps to Reproduce:
1. Boot and see that Desktop Pager set to 1*4.
2. Set number of rows to 2 in Pager settings. Desktop pager becomes 2*2.
3. Reboot, or restart KDE (Ctrl-backspace)
4. See that Desktop pager is again 1*4.

Discussion and some fixes tried so far: https://forums.mageia.org/en/viewtopic.php?f=7&t=5274

Reproducible: 

Steps to Reproduce:
darkduck 2013-07-15 22:49:31 CEST

CC: (none) => darkduck

David Walser 2013-08-11 01:43:17 CEST

CC: (none) => balcaen.john, nicolas.lecureuil

Comment 1 Marja Van Waes 2015-03-31 16:05:32 CEST 
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.