[Ubuntu-x-swat] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
@Niccolo Welcome. I don't think this old bug report is a way to get this problem solved as it is already closed. Since you have already looked for a current bug report and can't find one I'd suggest you file a new one yourself. Please don't be shy. I'd suggest you use the approach at https://wiki.ubuntu.com/X/Reporting since `ubuntu-bug xorg` will collect a lot of pertinent information automatically. That page has lots of useful advice. WRT your question about viewing your xorg log files yourself, I would would suggest starting gedit and navigate to /var/log/ and the files you want to examine. askubuntu.com is great for getting answers to this kind of question, by the way. Here on Launchpad is the best place to get bugs worked on. @Jorge The message about the quit signal is just like the ones that occurred with this sort of bug. It might be good to see if there is an error in the still older xorg log. @Both I think closed bugs don't appear on developers' lists so a new bug report is much better, as Steve Langasek suggested to someone above. In addition gdm was involved in this old bug but now lightdm is used for the sign on screen so this really is a brand new bug even though there are probably events in common and the symptoms are the same. If you are both having the same problem on Precise perhaps one of you can file the bug and the other can mark it as affecting him as well . You both should attach the logs produced by `ubuntu-bug xorg` to help move the bug toward triaging. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/532047 Title: Plymouth text-mode splash causes X to crash on first run due to shared tty7 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532047/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
Helge, Since the original problem was resolved (it was rather specific), and since this bug is therefore marked as closed, this bug doesn't show up on searches for bug triagers to work on. While I noticed your comments because I'm still subscribed, those triaging problems such as yours probably won't. Please submit your report as a new bug. Thanks for your contribution in improving Ubuntu. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747126] Re: X crashes on first touchpad touch
That's a perfectly reasonable question, Daniel. Thanks to Chase, it is going to the main natty repositories, no need for a PPA. It has already been published at http://us.archive.ubuntu.com/ubuntu/pool/main/x/xserver-xorg-input-synaptics/ and should be headed to all of them shortly (maybe it has already propagated fully). I was able to install by running update-manager a few minutes ago without doing anything special. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/747126 Title: X crashes on first touchpad touch ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 747126] Re: X crashes on first touchpad touch
Work-around: If, like me, you have difficulty not touching the touchad while you type, you can use xinput to disable it: xinput --list and find the id of the touchpad. Say it is 12: xinput set-prop 12 "Device Enabled" 0 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/747126 Title: X crashes on first touchpad touch ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 694430] Re: mesa bug affects new kernels
natty has moved the mesa package version past that in my ppa. As an update, there are plans to upgrade mesa in natty to 7.10, perhaps shortly if xorg-edgers testing goes well. It appears to me that the upstream patch referred to above is currently included in 7.10. (5b15b5f in git://cgit.freedesktop.org/mesa/mesa) Thank you for your bug report. ** Changed in: mesa (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/694430 Title: mesa bug affects new kernels ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
** Branch linked: lp:~jsjgruber/ubuntu/natty/mesa/mesa.fix681915 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
** Changed in: mesa (Ubuntu) Assignee: (unassigned) => John S. Gruber (jsjgruber) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
@manny: Any luck getting it to work? Anyone else? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
The patch from upstream: Author: Dave Airlie Date: Fri Dec 10 15:40:48 2010 +1000 r300g: fixup rs690 tiling stride alignment calculations. The RS690 memory controller prefers things to be on a different boundary than the discrete GPUs, we had an attempt to fix this, but it still failed, this consolidates the stride calculation into one place and removes the really special case check. This fixes gnome-shell and 16 piglit tests on my rs690 system. NOTE: This is a candidate for both the 7.9 and 7.10 branches. Signed-off-by: Dave Airlie (cherry picked from commit d19b5cbd317620f3977e68fffb7a74793436b7e2) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
I was able to trace this problem on my machine to libgl1-mesa-dri. Using git bisect I was able to identify and successfully test mesa commit 32218e4cc88f7dedebadffe4a80247decf4498f1 as addressing the problem. I've rebuilt the mesa package with this patch cherry-picked in ppa:jsjgruber/ppatwo, and this seems sufficient to fix the problem for me. Would anyone having the problem like to test this fix on their computer? If so, please be sure to run ppa-purge against xorg-edgers if you have applied that ppa to your system. Also, please be sure to select the correct ppa. I have another ppa containing another mesa package without this patch! ** Also affects: mesa Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 694430] Re: mesa bug affects new kernels
** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/694430 Title: mesa bug affects new kernels ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] peripherals.txt
apport information ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784400/+files/peripherals.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784398/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] glxinfo.txt
apport information ** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784399/+files/glxinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] XorgLog_.txt
apport information ** Attachment added: "XorgLog_.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784397/+files/XorgLog_.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784401/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] XorgLogOld_.txt
apport information ** Attachment added: "XorgLogOld_.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784396/+files/XorgLogOld_.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784395/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784394/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] UdevLog_.txt
apport information ** Attachment added: "UdevLog_.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784393/+files/UdevLog_.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784392/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784391/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] ProcModules_.txt
apport information ** Attachment added: "ProcModules_.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784390/+files/ProcModules_.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] ProcInterrupts_.txt
apport information ** Attachment added: "ProcInterrupts_.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784388/+files/ProcInterrupts_.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784389/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] ProcCpuinfo_.txt
apport information ** Attachment added: "ProcCpuinfo_.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784386/+files/ProcCpuinfo_.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784385/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784384/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784383/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784382/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784381/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784380/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784379/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/681915/+attachment/1784387/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins' CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1440x900 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: AP///wBMo0c4AAAQAQOAJRd4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEBnyWgQFGEDDBAIDMAb+YQAAAZDwAAAHjmAiMA/gBTQU1TVU5HCiAgICAg/gBMVE4xNzBYMi1MMDIKAPE= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DistUpgraded: Fresh install DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu GraphicsCard: Subsystem: Toshiba America Info Systems Device [1179:ff68] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101216) InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101216) InstallationMedia__: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101216) MachineType: TOSHIBA Satellite L355D Package: xserver-xorg-video-ati 1:6.13.2-1ubuntu2 PackageArchitecture: i386 PciDisplay: 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller]) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=e2dc8b84-1a90-4666-8b40-0536ef6da840 ro i2c-algo-bit.bit-test=1 ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=e2dc8b84-1a90-4666-8b40-0536ef6da840 ro i2c-algo-bit.bit-test=1 ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 ProcVersionSignature_: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 ProcVersionSignature__: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 RelatedPackageVersions: xserver-xorg 1:7.5+6ubuntu6 libgl1-mesa-glx 7.9+repack-1ubuntu3 libdrm2 2.4.22-2ubuntu1 xserver-xorg-video-intel 2:2.13.901-2ubuntu2 xserver-xorg-video-ati 1:6.13.2-1ubuntu2 Renderer: Hardware acceleration Tags: natty natty natty natty ubuntu Uname: Linux 2.6.37-11-generic i686 UnitySupportTest: UserGroups: XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 06/04/2009 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.90 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.90:bd06/04/2009:svnTOSHIBA:pnSatelliteL355D:pvrPSLE0U-01000R:rvnTOSHIBA:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L355D dmi.product.version: PSLE0U-01000R dmi.sys.vendor: TOSHIBA system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-11-generic version.libdrm2: libdrm2 2.4.22-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 7.9+repack-1ubuntu3 version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu6 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.13.901-2ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20100805+b96170a-0ubuntu1 ** Tags added: apport-collected ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 681915] Re: garbled graphics and text after launching unity
If I run qtdemo as follows the corruption disappears: LIBGL_ALWAYS_INDIRECT= qtdemo This also works with firefox flash videos if I start firefox's initial browser instance with this environment variable. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/681915 Title: garbled graphics and text after launching unity ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 694430] Re: mesa bug affects new kernels
Jaime: I've applied the patch to mesa from the above bugzilla bug report and built it in my ppa. You may want to try it. It didn't fix the bug I'm having but I guess it should fix yours. The ppa is: ppa:jsjgruber/ppa -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. https://bugs.launchpad.net/bugs/694430 Title: mesa bug affects new kernels ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
Thanks for your comment, jedioetzi. I wonder if you would find it worthwhile to look further for another report, or to open a new one, perhaps with the command: ubuntu-bug xorg The 532047 bug has been marked fixed (and it was), and therefore may not show up on many triagers' bug searches. (In addition those experiencing this bug were getting SIGINT and SIGQUIT from particular key presses. Yours is a segment fault.) Whatever you decide, thanks for posting your experience and good luck with maverick. -- Plymouth text-mode splash causes X to crash on first run due to shared tty7 https://bugs.launchpad.net/bugs/532047 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty because gdm starts before nvidia driver is ready
*** This bug is a duplicate of bug 615549 *** https://bugs.launchpad.net/bugs/615549 @Jamie: Looks like Martin is taking care of it in #615549. If I recall correctly, it will be (has been?) uploaded to the proposed queue and, after testing, it will be released to Lucid. -- X starts on wrong tty because gdm starts before nvidia driver is ready https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 639810] Re: X crashes when NM asks for wifi keyring password
*** This bug is a duplicate of bug 615549 *** https://bugs.launchpad.net/bugs/615549 Are you running the latest version of gdm? gdm (2.30.5-0ubuntu4) or later? See bug #615549. I know this may sound odd, but are you running apache, and if so, are you running the latest version? apache2 (2.2.16-1ubuntu3) (See bug #626723 where X crashed on a quit signal while running on VT7). -- X crashes when NM asks for wifi keyring password https://bugs.launchpad.net/bugs/639810 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
** Description changed: - Binary package hint: xorg - After the system boots and the plymouth screen disappears and X starts - up, if I press the enter key (occurs only with the enter key) X shuts - down and starts again in around 2 seconds. In the session of X that - comes up after this, the problem doesn't occur. + After the system boots and the plymouth screen disappears and X starts up on tty1 or tty2, if I press the enter key in a few minutes X shuts down and starts again. In the session of X that comes up after this, the problem doesn't occur. - UPDATE: Problem seems to be affecting plymouth and is a lot similar to - bug #532047, however in this case GRAPHICAL plugin is affected. The - workaround on that bug works, and pressing enter crashes both X and - Plymouth, forcing X to start on tty8 . + The problem happens when gdm starts X and X crashes silently. gdm + restarts X but X starts on tty1(2) as getty hasn't yet started and it + isn't the first X start. When getty does start on tty1 it eventually + interferes with X by setting ISIG on the tty. - ProblemType: Bug - DistroRelease: Ubuntu 10.10 - Package: xorg 1:7.5+6ubuntu3 - ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 - Uname: Linux 2.6.35-19-generic i686 - Architecture: i386 - CheckboxSubmission: 5e476a0872a6160d4830741693075266 - CheckboxSystem: 1e11ce1f0b739629ea3e4cbfa4fff3ab - DRM.card0.LVDS.1: - Â status: connected - Â enabled: enabled - Â dpms: On - Â modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 - Â edid-base64: AP///wBMozM2AAAPAQOAIRV4Cof1lFdPjCcnUFQBAQEBAQEBAQEBAQEBAQEB7hoAgFAgEDAQMBMAS88QAAAZDwAAACOHAmQC/gBTQU1TVU5HCiAgICAg/gBMVE4xNTRYMy1MMDYKAHA= - DRM.card0.VGA.1: - Â status: disconnected - Â enabled: disabled - Â dpms: On - Â modes: - Â edid-base64: - Date: Fri Aug 27 13:39:05 2010 - InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) - MachineType: TOSHIBA TECRA A7 - PccardctlIdent: - Â Socket 0: - Â Â Â no product info available - PccardctlStatus: - Â Socket 0: - Â Â Â no card - ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=ba586c06-64e7-4734-a35f-5320ea8063a4 ro quiet splash - ProcEnviron: - Â PATH=(custom, user) - Â LANG=en_US.utf8 - Â SHELL=/bin/bash - SourcePackage: xorg - dmi.bios.date: 08/30/2006 - dmi.bios.vendor: Phoenix Technologies LTD - dmi.bios.version: 2.00 - dmi.board.name: MPAD-MSAE Customer Reference Boards - dmi.board.vendor: Intel Corporation - dmi.board.version: Not Applicable - dmi.chassis.asset.tag: No Asset Tag - dmi.chassis.type: 1 - dmi.chassis.vendor: No Enclosure - dmi.chassis.version: N/A - dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd08/30/2006:svnTOSHIBA:pnTECRAA7:pvrPTA71E-09401CAR:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: - dmi.product.name: TECRA A7 - dmi.product.version: PTA71E-09401CAR - dmi.sys.vendor: TOSHIBA - glxinfo: Error: [Errno 2] No such file or directory - system: - Â distro: Ubuntu - Â codename: maverick - Â architecture: i686 - Â kernel: 2.6.35-19-generic + In the cases discussed here, the computer systems are very fast and gdm + is starting X before the nvidia kernel module is ready to run. + + NOTE WELL--the original reporter had the problem that his system was starting on tty7 and others were discussing tty1 starts here as well. At comment 30 + the problem was split with regard to tty1/tty7 starts and tty7 discussion moved to #626723. See original description below for his original report. ** Summary changed: - X starts on wrong tty: pressing enter after 5 minutes crashes X + X starts on wrong tty: pressing enter after 5 minutes crashes X; gdm restart of X involved -- X starts on wrong tty: pressing enter after 5 minutes crashes X; gdm restart of X involved https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
In syslog you might find messages like: gdm_binary[2542]WARNING: GdmDisplay: display lasted 0.945450 seconds Those are the ones Jamie has coming out quickly. I only get one when I start. It may be easier to look for those than to look at the log files. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 631003] Re: X server crash on my first login after I insert my password to unlock my key ring
You may want to check out bug #626723 -- X server crash on my first login after I insert my password to unlock my key ring https://bugs.launchpad.net/bugs/631003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Seth: I just saw that I missed several of your messages above. In particular 98 and 99. I'm sorry. Before I say it you coded it and had it building on launchpad. Great. I see no problem with your code. I built your change here and am running it successfully. Since I didn't see the bug I can't say any more. You said: > I have seen evidence in Xorg.*.log that this appeared to work even though I had four X session launch attempts within about a second (the first failing because of nvidia not being around). daemon/gdm-local-display-factory.c:#define MAX_DISPLAY_FAILURES 5 Sounds like you are close to the limit. Do you think there was another reason for the other 4? I do get one message about a session not lasting long, but not two or more like you and Jamie. I assume that's normal but I don't know. Even if we go no farther here I want to note in the record that driver failures are happening because X is being started prematurely. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Jamie: Rats. We don't need the plymouth:debug anymore. Would deleting it help? Can you simply go back to where you were last night when you were getting logs (albeit with the tty1 bug). If you can, maybe you can try Seth's new gdm fix. modeset and nomodeset are other possible things to try (I can't tell from the log what it is doing, and I don't even know if the nvidia driver supports kernel mode setting). In grub the linux cmdline parameters matter, but nothing else should. Grub should be loading the same kernel and initramfs into memory and passing control to linux. The linux command line is the only way to tell the kernel it just loaded to do anything different. The other parameters just tell grub how to behave before it loads the kernel. The xorg.0.log doesn't help. I can't tell if it is the same kind of problem as in this and bug #626723 or not since it just says it's going to give a backtrace and then doesn't. A dmesg or syslog from when the crash occurs may contain more information, you might look there. Attach them if you want us to take a look. Is there an X log in something like :n.log.n that shows the error with more output? It's one thing after another, I'm afraid. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Bilal: Congratulations. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Jamie: One of the earlier X logs you posted had an error that ended like that--without giving any backtrace. I see you are running apache. Does Dino's have your fix? Sounds like our fraternal twin bug may have been fixed since Bilal confirmed it is gone. Great catch, Dino. It also sounds like vt7 is as fragile a place to start X as vt1 or vt2, unfortunately. I have a suggestion for helping us determine how different solutions to both of our currently known problems (X crashes when kernel module is not ready, and early X crashes cause X to start on tty1-6) might delay the login screen, but I'm not sure Jamie's computer is in a position to run them. I hope the apache fix does the trick. My suggestion would be to add init jobs that would run the logger command when current gdm start conditions are met, when tty starting conditions are met, when udev ends, when nvidia is modprobed, and other events others think might be significant. I don't know how long we need to delay gdm's start, or delay gdm's restart of X, which might be another approach. @Seth: I'm still trying to understand your thoughts in your solution (B). If I understand, you thought init was telling gdm that it was boot time and start on vt7. init runs mountall which mounts a tempfs (like on /tmp) on /var/run. That wipes out the last boot stamp file and gdm looks for it when it runs without direction from plymouth. So init doesn't explictly tell gdm to run on vt7, or even that it is boot time, but that is the point of a file in the /var/run file system. (The file doesn't really get rm'd, it only existed in RAM during the last boot, but the tmpfs at /var/run keeps it from being kept). But it doesn't have to work that way, of course. Your approach sounds good to me. init jobs could explicitly create a booting-done file and gdm could look for that booting-done file in /var/run. I don't know whether is should specify a vt or whether that should be local to plymouth, gdm, and X. Is that the kind of thing you are talking about? I agree with you (A) sounds good, but is probably impossible to do, particularly between now and 10/10. Because of the 10/10 Maverick release, small, contained, fixes are probably best. And I assume the release team won't want to slow down boot more than necessary and avoid blinking the display unnecessarily. Another, minimal approach, might be to find where in gdm X is ready and create the stamp file there rather than on initial start so retries go to the same place. To address the looping problem, maybe after a failure gdm could sleep for a few seconds before trying X again. Just that change might address both problems and the first part of it is very like what is in place now. In effect gdm would be polling X and it would be polling the kernel. I like both the upstart job and the gdm modification ideas. The perfect fix where upstart is being used to minimize start time would be for nvidia (and intel and ati) to emit a signal to init so it could delay gdm until the necessary kernel driver is ready. But either every driver would need to do that, or the gdm jobs would have to change with the driver, or there would have to be several gdm scripts, each testing to see if it is the one responsible job to start gdm for the graphics driver configuration in use. Maybe the multiple jobs could be done, but I wouldn't like to see that tried this late in the release cycle. Just joining in brainstorming. What do you think about temporary init jobs to measure time between events? -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Jamie: Great! That's confirmation that gdm is starting too early relative to the tty's. and helps confirm similarity of your situation with Seth's. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Seth: I don't believe initctl passes a VT parameter. gdm is either starting X with a VT parameter, or not. It determines whether plymouth is running and if it is, and if it has its screen before the user, gdm tries to determine what VT that is and specifies that to X in a VT parameter. If that is ever VT1, etc. we will know that went wrong. If plymouth isn't running or doesn't think it is showing the splash screen to the user, but the /var/run/gdm file is missing, gdm figures this is the first X to start and hardcodes a start to VT7. If none of that is true, it starts X without a VT parameter, assuming that since it isn't the first launch of X all of the tty jobs will have started by then and there won't be a conflict. There's our current problem. Does that make sense? Please see the Ubuntu/debian patched gdm files daemon/gdm-simple-slave.c and daemon/gdm-server.c. After getting the source you need to apply the patches in debian/patches by doing a "debian/rules patch" (I always forget). If gdm isn't restarting it might be able to remember that the /var/run/gdm file was missing when it looked and keep the hardcoded VT7. I don't know whether gdm is restarting after X halts with a non-ready kernel module. That possible fix wouldn't fix gdm and X spinning until the the kernel is ready, however. The devs understand that the /var/run/gdm/firstserver-stamp approach is a hack. See the comments in the daemon/gdm-server.c gdm_server_start() function. That's where the vt7 hardcode is that's supposed to stop this from happening if plymouth hasn't already led gdm to vt7. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Brian This bug was split at about comment 30. We have been working on the case where the X crash happens some time after login because it has been started on tty1. Bilal's case start on tty7 is now being discussed in bug #626723. I feel a little bad that we aren't discussing his situation but that's how others split things up. I hope Bilal's not unhappy. I don't think the current theory for Jamie and Seth's case of this bug necessarily depends on the nvidia driver being used. It is that the driver, whichever one it is, isn't ready to work with X as soon as the current gdm upstart job's preconditions are met and that breaks the assumptions made in the methods used to prevent tty1 from being fought over. I think a good case could be made for delaying gdm's start until X can be successfully run. If you have the "start on tty1" situation would you mind attaching the output of ps aux gathered while you are still on tty1 (before the crash)? That would be a good start toward figuring out if you match the pattern we are currently discussing or if there is another case to be addressed. By the way, we know there are two ways the X crash on Enter or 2 key can happen--X started on tty1 or tty7. There may again be several ways either of those might happen. In particular we don't know here for sure that Jamie and Seth are really the same and don't know the root cause of Dino problems. -- @Dino I can't speak for all of your fellow bug fighters, but I'm very happy that your problem is gone. I'm glad you are still with us. Since a race condition is involved, I still really don't know whether the problem you were experiencing was the same thing as Jamie's or not. I can't challenge your assumptions in comment 75. The way this is supposed to work is quite complicated and the config files must be correct to avoid problems. I hope you will again speak up about your situation if the problem comes back, but I hope it doesn't. I was having the tty1 problem with pre- release lucid last Spring until the Plymouth megafix and it's a real nuisance (I had the tty7 problem sometime during testing, too) my tty1 cases were intermittent, where the problem would happen during one boot and everything would work the next--with no change at all. I spent more than a week researching what was happening until the devs were able to fix it. Thanks for sticking with us and for continuing to contribute (and for your patient contributions above). --- @Seth Do you think your xorg.conf file could be involved in the problem? -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
I don't see any errors in the dmesg log and it looks like the nvidia kernel module is ready rather late in that log. Looking at the udev log I would guess that the module isn't loaded any sooner than about .31 seconds before the last entry in the udev log (if I'm reading it correctly). @Seth: *IF* the theory hold up, I think your basic approach in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/532047/comments/91 might make the most sense as a fix to propose. gdm should wait until the graphics system is ready--it's attempting to do that now. What would you think about the gdm job also waiting for udev to finish or udevtrigger to start rather than for the tty's? It might happen sooner than the tty's and it's probably no later than 1/3 second from the earliest it could happen without error, and actually the module might not be ready until even closer to the end of the udev run. I don't notice any other udev event that would necessarily match when the nvidia module is done initializing, much less one that would be emitted with the use of any graphics driver (and modeset/nomodeset). Do you see anything in the udev log that looks like it would work or know of any other trigger? Any other approach? Is this something you would like to experiment with? Anyone--any other ideas? -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Jamie, It's my pleasure to work with you all. Would you mind posting your /var/log/udev file and /var/log/dmesg file? It probably doesn't matter when they are collected relative to when the bug occurs. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
So here is a theory for Seth and Jamie's case: gdm starts its race with the tty's before the nvidia software is really ready for X. Plymouth is running and gdm starts up, hand shakes with plymouth. Starts X. Gdm in the handshake tells plymouth to quit and it does. X crashes because it is too early for the nvidia driver. Gdm starts X again. Plymouth is no longer running so there is no handshake. Since this is no longer the first time an X server has been started, the hack to stop the use of tty1-6 no longer applies. Therefore gdm starts X with no VTx parameter. (How that could happen is what had been bothering me--this explains it, Seth). @Seth: for more confimation: when you are on tty1 does 'ps aux' show X without the last parameter being VTx? Since X hasn't been told where to go, and tty1 still hasn't started X starts there, or if it has started and tty2 hasn't X goes the first free one. X may crash some more, but gdm would limit how many times. There are examples of that on the "interwebs". tty1 starts and, as the dev said, hears Klingon. Some of that sounds like a login to it, but a wrong one. After several attempts, and usually some minutes, it restarts and sets the ISIG flag. There may be more going on here, too. An enter sends a QUIT signal to X, or a 2 sends the INT signal (keycode 3, control-c) because ISIG is incorrectly set and raw keyscan codes are being sent. X crashes. By now all the tty's are started, so when gdm restarts X, even though there is no VTn parameter at the end of the start command, it goes to VT7 or VT8 (8, I guess) and that isn't shared, so all is well. My working system gets this message once: "WARNING: GdmDisplay: display lasted 0.262511 seconds", but in his log, Jamie gets two in quick succession at boot time. I found an item on the internet relating messages like that to X crashes. --- What part of the theory can be contradicted? Confirmed? Other theories? @Jamie, can you find more Xorg.0.log's (or, more probably, :m.log.n's in /var/log/gdm) that can help confirm that Seth's find is present in your case? Another ps aux that confirms the absence of the VTn parameter at the end of the started X command? Xorg.0.log.old is at least one generation too old after the Enter crash, so the gdm :n.log.n's are probably where to look for another X log with the No Screens error and Radeon error messages. Whether not my theory is correct is not, that's a great find, Seth! -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
Seth: That is simply wonderful. One of Jamie's logs from comment 62 says: (**) Sep 07 22:16:47 NVIDIA(0): Enabling RENDER acceleration (II) Sep 07 22:16:47 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is (II) Sep 07 22:16:47 NVIDIA(0): enabled. NVIDIA: could not open the device file /dev/nvidiactl (No such device or address). (EE) Sep 07 22:16:47 NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the (EE) Sep 07 22:16:47 NVIDIA(0): system's kernel log for additional error messages and (EE) Sep 07 22:16:47 NVIDIA(0): consult the NVIDIA README for details. (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. ddxSigGiveUp: Closing log -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
Hi Dino Thanks for the information. That's good about firstserver.stamp. >From the ps.out I assume that the bug is still gone on your system since X started on tty7. If it ever fails again (starting on tty1-tty6) that time stamp, the output of ps before X crashes, and, if possible, the output in /var/log/plymouth-debug.log would be good information to gather to restart an investigation (from *my* perception). -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
It would be great if anyone else having the problem could post the output from the ps command on their system while they are running X on tty1 through tty6. @Dino: That's great news! -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Dino Could you attach the output from ps as Jamie did? If it starts happening again perhaps you can do the same again during a session you expect to crash? @Jamie and Dino Could you look again at that file creation time? sudo ls -l /var/run/gdm/firstserver.stamp It should exist and be empty, it's its creation/modification time that is important. It should be created the first time gdm starts at each boot, which is what Jamie reported above. It must not exist before gdm starts. If it is older than the last boot there may be a problem with the /var/run file system. @Jamie That ps.out file floored me. Unless I've misread the code, it looks to me like you and Dino have two different underlying causes for this bug. By the way, I assume anybody who has this bug can log out immediately after first logging in and won't have a subsequent crash. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
It's a shame about the crash getting in our way, but oh well. I don't see anything in the log either, sad to say. the acpid messages at 10:00:17 are from an unrelated daemon that tells interested processes on your computer about closing the lid, etc., if I'm not mistaken. Could you recreate the situation where X is on tty1 and, before X has a chance to quit, switch to a different tty, login, and save the output of the ps aux command? e.g. ps aux >~/ps.out and then attach ps.out? In particular the X command in the process list should tell us how gdm is starting X when there is going to be an X crash on Enter. Steve suggested this command in another bug report for someone having a similar problem. I'm still reading source code. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Jamie, Do you remember how you got the first log? Could the log you posted be from some time it hung? If it's complete it does look like plymouth crashed. For the crash situation does anything get recorded in the plymouth-debugging log? Maybe we should look in your /var/log/syslog from the time of a crash to look for any messages related to what is happening. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
@Seth: Please join us over at bug #625239. I'd love to see one of your failing Xorg.0.logs and a plymouth-debug.log if you could manage it in order to compare them to those contributed by Jamie and Dino. In Dino's case we can see that gdm is trying to follow plymouth to plymouth's tty (which should be tty7), but there is confusion somewhere. You may also want to take a look at closed karmic bug #396226. It explains why starting on the same tty as getty is bad news, though I think the reason is that the restart of getty sets the ISIG flag on the shared terminal rather than an issue of control. When I set this flag manually on tty7 from another terminal I can go back to tty7, press enter, and X gives this crash. I think I remember that you could tell whether the session is "primed" by looking at the stty from another terminal with sudo stty --file /dev/stty1 --all , but the scroll- lock sounds much better. Unfortunately I only have caps lock and num lock lights. I think your suggestion in 91 is interesting, but I guess there is the speed issue, and there is the issue that if someone ever decides only to run 5 tty's it won't be very obvious why gdm isn't starting. Seems like a good work-around to me, though, until this is fixed. -- Plymouth text-mode splash causes X to crash on first run due to shared tty7 https://bugs.launchpad.net/bugs/532047 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Carl, Dino99 has the problem with Maverick. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
Thanks for sticking with this even though you guys have found circumventions. If someone can fix this without adding boot parameters, etc. -- if it just works-- it will be better for many Ubuntu users. @Jamie: It looks like :2.log.1 is what I would expect for the bug we have been hunting. It was started quiet splash and crashed on VT2 after hitting Enter key rather than hitting the 2 key. :0.log.2 started on VT7 and X couldn't get started. It suggests looking at the corresponding Xorg.0.log file and some other files. It says no screens are available. It may mean what you were trying in booting it up wasn't giving you a good graphic environment to use, but I don't know that. The complaint it has is: (EE) Sep 07 22:16:47 NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the (EE) Sep 07 22:16:47 NVIDIA(0): system's kernel log for additional error messages and (EE) Sep 07 22:16:47 NVIDIA(0): consult the NVIDIA README for details. (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration. Perhaps it is a non-drm nvidia boot where the X driver and kernel driver don't match? I really don't know, but it isn't what we have been looking at and doesn't appear to have anything to do with plymouth or splash screens. :0.log.3 looks like a good splash start on VT8 :0.log.4 looks like an X crash during one of your VGA= experiments. I can't tell what the crash was and don't know if it is the same as what we have been looking at. It doesn't match :0.log.2, though. :1.log.2 looks like a good session on VT8. :1.log.3 looks like a session on VT2 that ended before it crashed The rest are unremarkable as far as I can tell right now. Here's the thing. The file I was most interested in seeing was your plymouth-debug.log. The one you posted shows the same error message Dino and I have (I'm not crashing). It shows the same variation in error messages we expected (you are using the fourth renderer). It shows gdm knows it is running and asks it to get ready to go away. But then it seems to end rather abruptly, unlike Dino's. If you copies and pasted it could you have missed some of it? Could you put your system back to the original state except for asking for plymouth:debug and attaching another so we can confirm it stops there. If that's all there is then plymouth crashed or was killed by another process before gdm started X, and that differs from Dino's case where it's the same to the point where gdm asks plymouth to get ready to go away (deactivate). THEN Dino's (and mine) ask it if it is controlling the VT you are looking at, and then starts X and later asks plymouth to quit. @Dino: Xorg.0.log looks to me like a Enter key crash on VT1, but when you booted without the splash or quiet parameters. I assume you didn't see a splash screen that time (plymouth would still run, I believe). Good confirming log. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
Jamie and Dino: If I understand, you each reported a problem with an X crash when X had already crashed. As Dino pointed out, that's very different. Would you please post the failing Xorg log? You can probably figure out which one by the time on the file. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
Cool, Jamie. I'm glad you found a work-around, and I appreciate your kind offer to post the logs later. I'd like to see how they match up with dino's, both with regard to the messages dino saw in his plymouth log post, and with regard to the little dance gdm and plymouth do to keep on the same VT7 (and not flicker). For now I'm thinking about how that dance could go wrong. It may be that changing to the text splash is changing a race condition, but it may also be that the code in plymouth for the graphics splash screen has a bug that the text screen software doesn't have. I'm not betting one way or the other. @Dino: I think the messages are ok, but I certainly may be mistaken. In the first case, while x11.so isn't being used, the program then tries drm.so, which seems to be working since there is not an error message. I would guess that Jamie's non-working configuration may be using drm.so also, and that his text mode splash may be using frame-buffer.so or vga16fb.so, but we will have to wait to see. In the second case, plymouth is trying several ways to get configuration information. It finally uses /lib/plymouth/themes/default.plymouth which tells plymouth to use the ubuntu splash screen. I'm predicting Jamie and all other Ubuntu users will see the same. It simply knows how it should be configured by what file it can read and from what files it cannot read. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
Our comments crossed. Sorry. Please take your time and only do things you are ok with. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
I don't have /etc/grub/default either. I do have /etc/default/grub. The file names are confusing. I see no reference to the former in update-grub or grub-mkconfig, but grub-mkconfig includes the contents of /etc/default/grub. Are you missing /etc/default/grub? I sometimes get nervous about grub, too. I do keep my boot cd's handy just in case. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
On Tue, Sep 7, 2010 at 10:53 AM, dino99 <625...@bugs.launchpad.net> wrote: > hi Jamie, > have done it by editing the boot line (E) into grub menu ( added at end of > quiet splash ) then boot (ctrl+x) Yep. That's what I do, too. As soon as the grub menu appears I move the arrow to the item I want to boot and press e for edit. Then I add (or subtract) what I want and press ctr+x. I think your method would work too, though. The method Jamie and I use is just for one boot and the one you suggest would continue to set the option every time you boot until you change it back. With regard to which /var/log/gdm files, I would open a terminal and do a "sudo ls -ltr /var/log/gdm" and look at the bottom of the output for the files that were created since the boot. The you can copy with "sudo cp /var/log/gdm/FILE ~/Desktop/" or some such. Jamie, please remember to post your upstart and gdm versions so your all your logs can be matched up with the software version you are running. Please forgive me if you included it above and I missed it. I see that you are running the same version of plymouth I am. (Dino's running maverick and has a newer version). You are both very patient. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
merci, Dino -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: X starts on wrong tty: pressing enter after 5 minutes crashes X
@Jamie: Since I'm only another member of the community it's completely possible that I won't be able to see this through to a fix. A glance from a plymouth or gdm developer may mean more progress than I could make in days. If it's ok with you, though, maybe we can move this towards a successful triage state on our own so it will be easy for a developer to find the problem. I appreciate your willingness to try things. I may not recognize when we have enough info. I think your reply was very interesting. 1. You have a system that flies. This bug may be a problem caused by a race condition. A faster system may have different results than a slower one. How many processors or cores does your system have? What speed? I ask this to look for correlations between your report and those by others. 2. You are configured to use splash and it is working. 3. The timestamp on your file is correct. Because you were occasionally starting on tty2, I had myself half convinced that it would have an old date and that gdm wasn't even trying to start on the same virtual terminal as plymouth. It may be that gdm thinks plymouth's active terminal is tty1 (or maybe even tty2). 4. Between the time you see the splash and you see the login you see a blink. There isn't supposed to be a blink. That may be where your virtual console is switching from tty7 to tty1 and X is sealing its fate by starting there (or may not). Some basics first: You said you are running plymouth version plymouth 0.8.2-2ubuntu2. What version of gdm and upstart are you running? Next: Could you try adding the boot option plymouth:debug in grub and on that boot recreate the problem? Could you then attach the plymouth debugging log, gdm log, and the log from the failing X. It will probably be in Xorg.0.log.old after you restart. The failing X log will contain a traceback and say something about a quit signal or another signal depending upon the key you pressed when it crashed. @Dino: If you are still with us. Would you mind terribly telling us, when it fails for you, what you see? What versions of plymouth, gdm, and upstart are you running? What is your computer like? Like Jamie, does the creation time of /var/run/gdm/firstserver.stamp match the login time (it should). I'm just trying to confirm there aren't two separate underlying reasons for starting X on tty1 or tty2. Warning: If this is a race condition just adding plymouth:debug might change the timing and "fix" the problem by slowing plymouth down. The logs may still be helpful. I'm thinking that it's a race condition and that Dino's compiz experiment changed the timing. I certainly may be wrong. The purpose of the logs is to make sure plymouth is running on tty7 as expected, to see if gdm is asking if plymouth is active on plymouth's virtual terminal, and to watch where X starts. The idea is to get an idea where things get directed to tty1. We won't need the auth logs. They simply helped establish the interference from the getty process. We already know if you are starting X on tty1 that we have this problem. Whether you each have the time and inclination to continue on with me or not, thanks to you both for posting your experiences. -- X starts on wrong tty: pressing enter after 5 minutes crashes X https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: Pressing Enter crashes both X and plymouth in graphical mode
@Jamie: What are you seeing right before gdm brings up the login screen? In particular, are you watching the splash screen? >From the command "sudo ls -l /var/run/gdm" when was the firstserver.stamp file created? -- Pressing Enter crashes both X and plymouth in graphical mode https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: Pressing Enter crashes both X and plymouth in graphical mode
I'm an Ubuntu amateur, so believe what Steve says over what I say. He's no amateur. I don't think the message "requirement "user ingroup nopasswdlogin" not met by user "bilal" " is a problem. I see from the forum post http://ubuntuforums.org/showthread.php?t=819198 that this is a requirement that a userid like "guest" might meet so that no password is required for that particular userid. Userid's requiring passwords should not be in this group. If I'm right, and if the userid bilal and oem require passwords, that particular message in the log would be expected. The reason I suggested in now closed duplicate bug #529230 that someone look in the auth file was to look for evidence that the getty program , responsible for getting people logged in on virtual consoles 1-6, was active seeing keystrokes coming from the xsession and getting confused. This only happens if x is started on tty1-tty6, as is happening to Jamie. See Steve's comment 18 above. This probably isn't happening to Bilal. His xorg.0.log.old has the X crash and that log says it started on vt7. Andres says his crashing X is starting on vt7. I haven't gotten my head around dino99's report, but I don't think most people who have had this problem have had a problem with authentication, only with interference with x, either from plymouth (which should have quit just before X started, if I'm correct), or from getty. In the case of getty, I think the interference only crashes X after getty thinks, mistakenly, that it has seen several login attempts and restarts. It messes with the virtual terminal when it does that and that does in X when you next press the 2 or enter key. That might be the reason for Jamie's delay before the crash. -- Pressing Enter crashes both X and plymouth in graphical mode https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 625239] Re: Pressing Enter crashes both X and plymouth in graphical mode
@Jamie: If you don't mind my asking, what version of Plymouth are you running? -- Pressing Enter crashes both X and plymouth in graphical mode https://bugs.launchpad.net/bugs/625239 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
Looks like the regression in Maverick has been filed as bug #625239 and has been marked as confirmed. -- Plymouth text-mode splash causes X to crash on first run due to shared tty7 https://bugs.launchpad.net/bugs/532047 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
Madde, Matteo: I've had both the login problem, and the later "Enter or 2" problem. The difficulty is the keyboard scancodes, so different keyboards can have different triggers if the keyboards have different scancode assignments. Whenever it happens later, it seems that my crashed X session had been on tty1 (VT1) rather than on tty7 (VT7) or higher. I suspect this symptom might involve the getty program (and maybe plymouth as well). If your /var/log/Xorg.0.log.old file is still around from the crash I wonder if you could check the beginning of the file to see on what VT X had started (and save it somewhere for possible posting later)? I've had trouble reproducing the VT1/late crash problem since uninstalling and reinstalling plymouth, but as I typed this reply the first time a few minutes ago X crashed when I typed "2". (Whew!). I checked my session and it had started on tty1 and thus had been vulnerable to whatever getty had been doing to tty1. There are reports on the situation with late (after the problem key had previously been pressed in an X session--login or after) in LP: #529230. In both my case, and the case of the original reporter, X had started on tty1 (VT1). I don't know about the new case. I wonder if this late crash problem is related to the situation closed for karmic in LP: #396226. -- Plymouth text-mode splash causes X to crash on first run due to shared tty7 https://bugs.launchpad.net/bugs/532047 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 529230] Re: X server crashes when enter key is pressed
** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/40308463/Xorg.0.log.old -- X server crashes when enter key is pressed https://bugs.launchpad.net/bugs/529230 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 529230] Re: X server crashes when enter key is pressed
I can reproduce at times right after booting current Lucid kernel. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Tags added: lucid -- X server crashes when enter key is pressed https://bugs.launchpad.net/bugs/529230 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 529230] Re: X server crashes when enter key is pressed
This happens to me intermittently. I noticed it some weeks ago, I didn't see it for a while, and it returned in the last several days. It may happen more often if I boot with the radeon.modeset=0 option and I also see it with a rather new 2.6.33 release candidate stock kernel I sometimes boot. It may happen 3 out of 10-20 times and seems to happen in runs. At times, after a reboot, rather than the login screen, I see a mostly blank screen and when I type I see scan codes echoed as I type. If I switch to VT1 at this point and then back to VT7 I see the login screen. If I press Enter, X will crash with the same traceback listed above. If, when this has happened and I'm at VT7's framebuffer, I press ALT-Sysrq-R I can proceed correctly. When in the above error mode I avoid pressing enter by using the touchpad or mouse I can proceed to logging in and start a terminal, type a few things, and then press Enter. At that point X will crash and the framebuffer image, when I see it, will contain scan codes for the ascii characters I typed into the terminal session, ending in ^\ . Ascii ^\ is 0x1c and the scan code for enter is 0x1c as well. Of course the Ascii code ^\ is the standard thing to use to send SIGQUIT to a running process. I've determined that the error case and good case can be determined when I get to the login screen by switching to VT1 and entering sudo stty -F /dev/tty7 In good cases -isig is displayed. In bad cases isig is set. Thus, there are times when tty7 is left with processing of signal producing control characters on when set up to pass scan codes to the X server and the kernel reacts to processing the Enter scan code by sending the SIGQUIT signal to the X server, causing it to quit. While in VT1 in the error case I can use sudo stty -F /dev/tty7 -isig and then on return to VT7 can proceed without a crash. I don't see a pattern in my /var/log/syslog between working and error cases. While one approach might be to try to figure out why isig sometimes is being left unset, I wonder why the tty driver is getting confused between scan codes and Ascii anyway. When X crashes this way it is restarted on the next VT and another login screen is presented. I haven't seen this happen more than once in a boot session. -- X server crashes when enter key is pressed https://bugs.launchpad.net/bugs/529230 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 321128] Re: windows seem to want to be at the top-left
I turned Compiz and the Snapping Windows plugin on with Karmic but I didn't see the problem. -- windows seem to want to be at the top-left https://bugs.launchpad.net/bugs/321128 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
