| Summary: | Can't start a second X session in parallel with fglrx | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Samuel Verschelde <stormi-mageia> |
| Component: | RPM Packages | Assignee: | Anssi Hannula <anssi.hannula> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11, thierry.vignaud |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | x11-driver-video-fglrx | CVE: | |
| Status comment: | |||
| Attachments: |
Xorg logs for the second session
lspcidrake -v xorg.conf |
||
|
Description
Samuel Verschelde
2011-04-05 15:33:13 CEST
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.
Thierry Vignaud
2011-04-05 18:26:59 CEST
CC:
(none) =>
thierry.vignaud 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
Marja Van Waes
2012-01-21 10:37:35 CET
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 Keywords:
(none) =>
NEEDINFO 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 =>
RESOLVED |