[Ubuntu-x-swat] [Bug 1041584] [NEW] /usr/bin/X crashed with Signal 11
Public bug reported: For the past week or so, I've been getting 2 or 3 X server crashes a day on my computer. After the crash, I normally get an apport popup and walk through the dialogs in an attempt to report the crash. Based on what I've read, the 12.04 release process is supposed to report these crashes invisibly to the user. I'm not sure if these crashes are getting reported since the new process is silent as to whether the reporting is successful or not. There is also very little information regarding the crash. I have found a report in the /var/crash directory that indicates a Signal 11. Here is the section of the report with the signal identified. Mems_allowed: 1 Mems_allowed_list: 0 voluntary_ctxt_switches: 1030192 nonvoluntary_ctxt_switches:29511 Signal: 11 Uname: Linux 3.2.0-29-generic-pae i686 UserGroups: CoreDump: base64 H4sICAAC/0NvcmVEdW1wAA== The crashes don't have anything in common other than the computer is working fine and then the screen goes black and the login screen is displayed. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1041584 Title: /usr/bin/X crashed with Signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1041584/+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 469470] Re: proprietary nvidia driver does not work under karmic
I started experiencing something similar today after enabling Karmic proposed repositories and performing an upgrade. The upgrade pulled in updates for xserver. The updates seem to be related to the failsafe server. Reverting to the Karmic released versions of the xserver packages resolves the problem for me. I run Kubuntu and use kdm for my login manager. I also have Ubuntu desktop installed and sometimes use the gnome desktop but not gdm. However, gdm is installed. It almost looks like the failsafe server is attempting to startup and creating a conflict with kdm. If I cancel the low resolution mode dialog quickly enough, kdm is able to startup and everything is ok. I've attached my kdm log which shows the conflict with accessing the display. ** Attachment added: "kdm.log" http://launchpadlibrarian.net/36209046/kdm.log -- proprietary nvidia driver does not work under karmic https://bugs.launchpad.net/bugs/469470 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 485651] Re: Karmic + KDM + NVidia = Can't boot (low graphic mode)
I started experiencing this today after applying the latest xserver updates for Karmic (1:7.4+3ubuntu10). If you cancel out of the low graphic mode dialog quickly enough, kdm will restart and run normally. The problem results in the following messages in the kdm.log file: Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Please consult the The X.Org Foundation support at http://wiki.x.org for help. ddxSigGiveUp: Closing log Warning: Failsafe mode was already attempted within 30 seconds. Warning: Falling back to gdm to report the issue. -- Karmic + KDM + NVidia = Can't boot (low graphic mode) https://bugs.launchpad.net/bugs/485651 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 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 542950] [NEW] Screen corruption on startup
Public bug reported: Binary package hint: xorg I'm testing out the Lucid beta by booting from a USB drive. Initial splash screen displays progress. When boot up sequence switches to the X display, the screen becomes corrupted. There are portions of the screen from the last time the system ran, but they are scattered across the screen. I can hear the Ubuntu startup sounds, so the system is coming up. However, I'm not able to access anything on the screen so I can't open a terminal to enter any commands. I'm also not able to switch to a tty. Hitting ctrl-alt-f1 - f6 do nothing. Any clues on how I can debug this. Live disk is AMD 64 version running on an Athlon 64 with an Nvidia GeForce 6100 graphics card ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
Additional info Adding nomodeset as a boot option allows X to startup and I'm able to test out the beta. -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
Here are the requested log files. Note that these files were only able to be collected after a successful boot to the desktop. The failed boot did not provide any opportunity to collect the files. I've included both Xorg.0.log and Xorg.0.log.old. ** Attachment added: "Xorg log file" http://launchpadlibrarian.net/41524689/Xorg.0.log -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
** Attachment added: "Xorg log from failed startup" http://launchpadlibrarian.net/41524692/Xorg.0.log.old -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
** Attachment added: "dmesg of successful startup" http://launchpadlibrarian.net/41524803/dmesg -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
** Attachment added: "dmesg of failed startup" http://launchpadlibrarian.net/41524854/dmesg.0 -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
** Attachment added: "output of lspci -vvnn command after successful startup" http://launchpadlibrarian.net/41524982/lspci.out -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 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 542950] Re: Screen corruption on startup
Added blacklist=vga16fb as a boot option. This didn't help. System still behaves the same. Screen becomes corrupted instead of showing the desktop. I am attaching the dmesg and X org log file from the attempt. ** Attachment added: "dmesg file from attempt with blacklist=vga16gb as boot option" http://launchpadlibrarian.net/41669757/dmesg.0 -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau 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 542950] Re: Screen corruption on startup
** Attachment added: "Xorg log from attempt with blacklist=vga16fb" http://launchpadlibrarian.net/41669856/Xorg.0.log.old -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau 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 542950] Re: Screen corruption on startup
Adding blacklist=vga16fb nouveau.noaccel=1 works. Desktop is up and running. I'm using FireFox now to update the comment. The transition from the splash (plymouth? Ubuntu with the dots underneath) to desktop wasn't an issue. Screen went black for a couple of seconds and then desktop appeared. Attaching dmesg and X org log again in case they help. ** Attachment added: "dmesg with blacklist=vga16fb nouveau.noaccel=1" http://launchpadlibrarian.net/41681981/dmesg -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau 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 542950] Re: Screen corruption on startup
** Attachment added: "Xorg log for blacklist=vga16fb nouveau.noaccel=1" http://launchpadlibrarian.net/41682024/Xorg.0.log -- Screen corruption on startup https://bugs.launchpad.net/bugs/542950 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau 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 308191] Re: Multitouch support not available for Synaptics touchpads v7.2
Multi-finger now detected on Asus 1005PE with the latest patch. Synaptics Capabilities (292): 1, 0, 1, 1, 1 synclient -m reporting multiple fingers 7.001 3396 3521 84 2 5 0 0 0 0 0 0 0 0 0 0 8.002 3393 3503 84 2 5 0 0 0 0 0 0 0 0 0 0 9.002 3404 3565 84 2 5 0 0 0 0 0 0 0 0 0 0 10.002 3407 2412 87 3 5 0 0 0 0 0 0 0 0 0 0 11.002 3405 2463 96 3 5 0 0 0 0 0 0 0 0 0 0 12.002 3404 2489 97 3 5 0 0 0 0 0 0 0 0 0 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/308191 Title: Multitouch support not available for Synaptics touchpads v7.2 ___ 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
