Bug 274885

Summary: KDE crashes on startup if Xinerama is enabled.
Product: [Plasma] kwin Reporter: Cole Gleason <colewashere>
Component: xineramaAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: investigated, triaged
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: xorg.conf

Description Cole Gleason 2011-06-04 07:49:36 UTC
Created attachment 60598 [details]
xorg.conf

Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

Whenever I attempt to use an xorg.conf that has Xinerama enabled while using the fglrx drivers, KDE will crash during the loading process (after I login).

Reproducible: Always

Steps to Reproduce:
1. Delete xorg.conf
2. Start KDE (It works!)
3. Enable Xinerama using aticonfig, amdccle or with a text editor.
4. Reboot and login.
5. Watch that little loading screen start to fill with icons, then it freezes.

Actual Results:  
Splash screen freezes and is unresponsive.  I can switch to a TTY or SSH in however.

Expected Results:  
KDE should have loaded me into a usable enviorment with Xinerama enabled.

Video cards: 2x HD6850s
Drivers: Proprietary Catalyst drivers (need OpenCL support, otherwise I'd use free ones).
Distro: Arch Linux
Comment 1 Christoph Feck 2011-06-10 00:54:18 UTC
Not sure what to do with this bug (lots of information is missing), KWin developers should know better which information to request.
Comment 2 Thomas Lübking 2011-06-10 10:46:56 UTC
The settings to try some of the below can be adjusted "kcmshell4 kwincompositing"

a) can you see/move the mouse cursor?
b) is this related to the usage of compositing (1. tab) - try "SHIFT+Alt+F12" to suspend compositing when it freezes.
c) what's the combined area of your screens, why is there a second GPU, how are they connected?
d) is it related to opengl compositing (3. tab, try xrender)
e) is it related to a particular effect (eg. "login" or "blur", 2. tab)
-> disable all effect plugins, then try and see what happens. Then re-enable them one by one to find the culprit (i'd try the two mentioned above first)
f) have you tried the free radeon driver before, did it work with that?
g) using fglrx (also after using another driver) iirc requires some initial aticofig calls, did you?
Comment 3 Martin Flöser 2011-06-26 09:30:05 UTC
please reply to questions in comment #2.
Comment 4 Andrew Crouthamel 2018-09-22 01:57:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 03:39:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!