I do wish you would stop marking this bug incomplete. It is very much
incomplete, is an upstream bug, and the developers are not asking for
further information.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
I have an Atom N455 convertible with Pineview graphics. Unity8 session
just displays a black screen forever. Unity 7 works fine.
--
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/1549455
Title:
This bug has been around since 2011. The nouveau developers have no idea
how to fix it. Unless you can show me a commit which you believe fixes
the problem I'm going to assume it is not fixed.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete = Confirmed
--
You
This is visible on the lightdm log too. Here it is, trying to start :1
on VT7, which is already in use by :0
[+101.59s] DEBUG: Seat: Starting local X display
[+101.59s] DEBUG: Using VT 7
[+101.59s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+101.59s] DEBUG: DisplayServer x-1:
If you search for VT in the Xorg.1.log you can see it attempts to
start Xorg on VT 7... which is the VT where :0 is running. When
everything works correctly, :1 should be started on VT 8, and the log
confirms it.
--
You received this bug notification because you are a member of Ubuntu-X,
which
I now know exactly what causes this bug. The problem is that the VT gets
unref'd once when the server shuts down, and then unref'd again much
later when the object gets finalized. This might happen after the VT has
already been allocated and ref'd to another server. This makes lightdm
think the VT
** Branch linked: lp:~a-j-buxton/lightdm/vt-double-unref-fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1256150
Title:
Xorg guest session fails to start if the user has logged out and
I wonder why this bug didn't get any hardware information attached?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau
Public bug reported:
With the Nouveau driver I get random system hangs in the Live CD - any
version since it was switched to nouveau up until today's daily images.
It happens after half an hour to a couple of hours usage and affects
installed systems as well, until they are switched to the
I just got this crash. I have GT215 based nvidia card too. This card is
notorious for crashing with Nouveau. I got the crash 7 minutes after
installing 12.10, while I was installing the first updates. I hadn't
installed any extra software and nothing was running except for the
default desktop and
Public bug reported:
To reproduce:
Xephyr :1
in a new shell:
DISPLAY=:1 xterm
press ctrl-c to kill the xterm. Now Xephyr crashes with a segfault. 100%
reproducable.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xserver-xephyr 2:1.11.4-0ubuntu10.2
ProcVersionSignature: Ubuntu
--
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/1012798
Title:
segfault in xserver-xephyr
To manage notifications about this bug go to:
apport information
** Tags added: apport-collected
** Description changed:
To reproduce:
Xephyr :1
in a new shell:
DISPLAY=:1 xterm
press ctrl-c to kill the xterm. Now Xephyr crashes with a segfault. 100%
reproducable.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/1012798/+attachment/3188252/+files/BootLog.gz
--
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/1012798
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188251/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188253/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: DkmsStatus.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188254/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188255/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188256/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188257/+files/Lspci.txt
--
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/1012798
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188258/+files/Lsusb.txt
--
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/1012798
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188260/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188259/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188261/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188262/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188263/+files/UdevDb.txt
--
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/1012798
apport information
** Attachment added: nvidia-settings.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188270/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188264/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188265/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: XorgConf.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188266/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188267/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188271/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I give up. It seems that apport no longer allows submitting core dumps.
If you want to see the core dump from this bug, you can find it on
errors.launchpad.net somewhere.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188268/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1012798/+attachment/3188269/+files/Xrandr.txt
--
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/1012798
I've noticed this happens with metacity as well. Note that it only
happens when restarting the window manager manually without restarting
X, usually due to a crash and failure to auto-restart. It never happens
during normal use.
--
You received this bug notification because you are a member of
Public bug reported:
fglrx is non-functional after upgrading. After a failed install I
attemped to purge it, got this crash. It seems to be in a strange half-
installed state.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/908648
Title:
package fglrx (not installed) failed to install/upgrade: subprocess
installed post-removal script returned error exit
My observations (using firefox 3.6.13 and nvidia 260.19.06)
- The problem only happens on launchpad.net. None of the other examples given
on this bug still exhibit the problem. Likely they were all caused by the old
slow javascript engine that was replaced in a version of FF since 3.0. But the
As a test I tried the firefox versions in ppa:ubuntu-mozilla-daily/ppa.
I now have namoroka 3.6.14pre and minefield 4.0b9pre and they are
both *much* faster than the standard maverick firefox when browsing
launchpad.
--
You received this bug notification because you are a member of Ubuntu-X,
Please ignore previous comment - it turns out that those versions are
equally affected, including firefox 4.0 beta. And it seems the problem
is made much worse when the graphics card is under load from some other
application doing 3D stuff...
--
You received this bug notification because you are
** Bug watch added: Mozilla Bugzilla #490563
https://bugzilla.mozilla.org/show_bug.cgi?id=490563
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=490563
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
I also find that this bug does not happen in Lucid. I used to see Xorg
using up to 10gb under Karmic when using 3D apps with Nvidia 190. Now in
Lucid it stays at normal levels.
--
X leaks memory while team fortress 2 is running in wine
https://bugs.launchpad.net/bugs/494064
You received this bug
This bug was fixed upstream in xserver 1.6.1.902 and the fix is in Karmi
and later.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Fix Released
** Tags removed: needs-lspci-vvnn needs-retested-on-lucid-by-june needs-
xorglog
--
SEGFAULT in Xephyr
same result here with 190.53 and rc6
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: New = Confirmed
--
building module with dkms against 2.6.33-rc fails
https://bugs.launchpad.net/bugs/503446
You received this bug notification because you are a member of Ubuntu-X,
which is
This happens because some headers were moved from include/linux to
include/generated on 2.6.33. You also need to patch a changed ACPI
function call to successfully build.
--
building module with dkms against 2.6.33-rc fails
https://bugs.launchpad.net/bugs/503446
You received this bug
** Bug watch added: freedesktop.org Bugzilla #21591
https://bugs.freedesktop.org/show_bug.cgi?id=21591
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=21591
Importance: Unknown
Status: Unknown
--
SEGFAULT in Xephyr
Are you sure? Xephyr is a nested X server. It does not touch any
hardware, does not write to dmesg and does not create a log file.
Attaching requested files anyway, even though they do not show anything
useful.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
** Attachment
** Attachment added: lspci.txt
http://launchpadlibrarian.net/31300631/lspci.txt
--
SEGFAULT in Xephyr
https://bugs.launchpad.net/bugs/423188
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/31300633/Xorg.0.log
--
SEGFAULT in Xephyr
https://bugs.launchpad.net/bugs/423188
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Public bug reported:
Binary package hint: xserver-xephyr
Xephyr version: 2:1.6.0-0ubuntu14
Ubuntu version: 9.04
Steps to reproduce:
1. Install the Maemo 4.1.2 SDK from maemo.org
2. Launch the Maemo device emulator as instructed, including starting Xephyr:
Xephyr :2 -host-cursor -screen
Closing again. In my case this was probably caused by a hardware
failure: the fan on the graphics card had died.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: New = Invalid
--
Display gets corrupted and garbled every 5-7 minutes when using compiz. VT
switch which takes
Reopening - I've just today started to get a very similar problem using
nvidia-graphics-drivers-180 on Jaunty, after installing some updates.
** Changed in: compiz (Ubuntu)
Status: Invalid = New
** Package changed: nvidia-graphics-drivers-177 (Ubuntu) = nvidia-
graphics-drivers-180
** Attachment added: Picture of the corruption
http://launchpadlibrarian.net/28640202/IMAGE_00117.jpg
--
Display gets corrupted and garbled every 5-7 minutes when using compiz. VT
switch which takes ~1min required to reset screen
https://bugs.launchpad.net/bugs/309739
You received this bug
** Attachment added: xorg.conf
http://launchpadlibrarian.net/28640242/xorg.conf
--
Display gets corrupted and garbled every 5-7 minutes when using compiz. VT
switch which takes ~1min required to reset screen
https://bugs.launchpad.net/bugs/309739
You received this bug notification because
** Attachment added: output of lspci -vvnn
http://launchpadlibrarian.net/28640230/lspci.txt
--
Display gets corrupted and garbled every 5-7 minutes when using compiz. VT
switch which takes ~1min required to reset screen
https://bugs.launchpad.net/bugs/309739
You received this bug
Steps to reproduce: none, it randomly happens every 5-10 minutes while
using compiz. Cannot reproduce with other (none compositing) WM, nor see
any kind of corruption in opengl games. Switching to VT clears the
corruption until the next time. Nothing freezes or crashes at any point.
** Attachment
Installed versions:
compiz: 1:0.8.2-0ubuntu8.1
nvidia: 180.44-0ubuntu1
kernel: 2.6.28-13-generic
The problem started happening immediately after rebooting for the kernel
upgrade.
--
Display gets corrupted and garbled every 5-7 minutes when using compiz. VT
switch which takes ~1min required to
58 matches
Mail list logo
