Description of problem: When I try to start a second session without closing the current KDE session, it fails. It doesn't look like a KDE problem, it's X that can't start (see attached logs). How reproducible: always here Steps to Reproduce: 1. start KDE 2. select "switch user" 3. it shows a black screen then falls back to the first session Reproducible: Steps to Reproduce:
Created attachment 198 [details] Xorg logs for the second session
Created attachment 199 [details] lspcidrake -v
Just in case it's relevant, I have 2 screens.
CC: (none) => thierry.vignaudAssignee: bugsquad => anssi.hannulaSummary: Can't start a second X session in parallel => Can't start a second X session in parallel with fglrxSource RPM: (none) => x11-driver-video-fglrx
Please attach /etc/X11/xorg.conf .
For the record, this looks like the same issue: http://forum.mandriva.com/fr/viewtopic.php?t=134203&p=844262 Looks like xorg.conf info for fglrx may need to be changes (that rings a bell about a bug in mdv bugzilla).
Created attachment 203 [details] xorg.conf
Is that bug still valid ?
Keywords: (none) => NEEDINFO
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Samuel Please close this report if it isn't valid anymore for current cauldron @ Anssi Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
Keywords: NEEDINFO => (none)
3-monthly ping
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
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD