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 t
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 p
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:
Ser
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,
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.
___
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://l
** 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.
___
** 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.
_
** 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.
___
** 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
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
** 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 xser
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.
** 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 xser
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
15 matches
Mail list logo
