Bug 468679
| Summary: | compiz often fails to start on initial login | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeff Layton <jlayton> | ||||||||||||||||
| Component: | compiz | Assignee: | Adel Gadllah <adel.gadllah> | ||||||||||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||
| Priority: | medium | ||||||||||||||||||
| Version: | 10 | CC: | jrb, mcepl, opossum1er, steved, xgl-maint | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | All | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2009-11-17 13:01:12 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
So, first things first -- don't talk to me about nvidia binary-only driver. It is unsupported, and especially in case of OpenGL we cannot do much about it, because nvidia replaces even parts of GL implementation with their own stuff. So, please, let's talk just about your intel computer at work. Please attach your X server config file (/etc/X11/xorg.conf), X server log file (/var/log/Xorg.*.log), /var/log/dmesg, and ~/.xsession-errors from that computer to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 321926 [details]
xorg.conf from intel machine
Created attachment 321927 [details]
xsession-errors from intel machine
Created attachment 321928 [details]
Xorg.0.log
Created attachment 321929 [details]
dmesg.out
/var/log/dmesg doesn't show the DRM initialization, so here's the actual output from dmesg after boot and login
Created attachment 321930 [details]
Xorg.0.log from X start with no xorg.conf
I updated my workstation at work to F10 this morning and am getting different results. compiz no longer works at all and gives a black screen on login. I suspect the problem may be the DRM error messages that are showing up in the kernel ring buffer (or some other Intel X driver related problem).
I also tried booting the machine with no xorg.conf file and the display completely froze soon after displaying the login screen. ctrl-alt-backspace had no effect.
Attached is the Xorg.0.log from that attempt.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Created attachment 330347 [details]
display corruption after switching to compiz and reloading window manager
More recent updates to f10 show a different problem when I enable compiz on my machine with intel video. When I use the panel applet to switch to compiz the window manager still immediately exits and leaves me with no window bars. When I then use the applet to reload the window manager, I get a completely scrambled screen.
Attaching a screenshot of what I see after reloading the window manager. Mousing over elements in the menu bars or windows seems to make the elements display correctly but there doesn't seem to be any way to force a redraw of the entire screen.
Let me know if there is other info that would be helpful.
I think I found the cause of the initial problem... metacity had the compositing_manager option enabled in gconf. I believe that was preventing compiz from taking over the compositing manager at login. After disabling that it seems to work. On the other issue with intel video, F11 doesn't currently give any display corruption when I enable compiz, but it does completely hang the box after a period of time. That's a separate issue however, so we can deal with that separately. I'm not sure what the solution is here...maybe metacity should be fixed to hand over control to compiz when it starts? Switching incorrect assignees to the default one. FWIW, compiz seems to work correctly with F12 now... The issue of contention between metacity and compiz for the compositing manager is still a problem that needs to be solved however. (In reply to comment #12) > FWIW, compiz seems to work correctly with F12 now... > > The issue of contention between metacity and compiz for the compositing manager > is still a problem that needs to be solved however. metacity as a compositing manager is unsupported hack which is there left undocumented for those who dare to try. I don't think we will bother with doing anythig to support it. Closing as fixed. |
Created attachment 321609 [details] .xsession-errors Usually, on initial login compiz fails to start, leaving my desktop running without a window manager. Using the "Reload window manager" selection in the fusion-icon applet typically gets compiz started correctly. Because of this, it seems like a race of some sort. This happens on both my home workstation (using proprietary nvidia graphics driver) and on my workstation at work (Intel graphics). The intel machine also seems to often get hit with the "whitescreen" problem, but that may not be related... I've attached my .xsession-errors file from my home w/s (nvidia graphics). I'm using: compiz-manager-0.6.0-8.fc10.noarch compiz-gnome-0.7.6-15.fc10.x86_64 compiz-fusion-gnome-0.7.6-7.fc10.x86_64 compiz-0.7.6-15.fc10.x86_64 compiz-fusion-0.7.6-7.fc10.x86_64 compizconfig-python-0.7.6-1.fc10.x86_64 compizconfig-backend-gconf-0.7.6-1.fc10.x86_64 fusion-icon-qt-0.1.0-0.3.5e2dc9git.fc10.noarch fusion-icon-0.1.0-0.3.5e2dc9git.fc10.noarch ccsm-0.7.6-2.fc10.noarch ...I've had this problem during all of F9 and am still seeing it in F10 (maybe also during F8? Not sure...) Other info available upon request. I should also be able to test packages if needed...