Description of problem: the ATI catalyst control center from the fglrx drivers: dkms-fglrx-8.902-1.mga2.nonfree x11-driver-video-fglrx-8.902-1.mga2.nonfree fglrx-control-center-8.902-1.mga2.nonfree seem to set the desktop correctly but after a reboot of the system the settings are not kept. when logging into KDM it looks ok at first on the logging screen but after this the startup for the user starts to show the startup screen for both desktops. When the logging is complete the desktops are a clone of each other instead of using multiple desktops. When using the KDE control center to try and correct this the settings do not stick and after changing to absolute positioning so that I can manually set the screens after clicking apply they go back to clone instead. I have to change orientation as well as use absolute positioning to get the settings to stay but sometimes they still do not stay. After changing the settings a few times it will finally stick until I reboot and then they go back. This sounds like a permissions issue or maybe a stale file in my home directory but I have recently fixed all those I could find so not sure if this is the case.
Hi, thanks for reporting this bug. Assigned to the package maintainer.
Keywords: (none) => TriagedAssignee: bugsquad => anssi.hannula
Have you tried the catalyst control center in superuser mode? i.e. Menu -> Tools -> System Tools -> Catalyst control center (Administrative)
CC: (none) => djmarian4uSummary: After reboot screen orientation is not kept and it has to be set up every time after logging into desktop => after reboot screen orientation is not kept and it has to be set up every time after logging into desktop
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
@brook : Can you give a answer to comment2 within 2 weeks. Otherwise we have to close this bug. Roelof
CC: (none) => r.wobben
No response so close
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => OLD