This hits me on 14.04 as well with an updated google-chrome. So perhaps
this is a google-chrome bug?
--
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/1461645
Title:
[Ubuntu
On 13 Mar 17, Rafal Cieślak wrote:
I am affected by a bug which looks just as this one, and appeared in in
apparently the same version of unity package, yet I can't tell if it's
indeed the same - for I am using AMD graphics. If this is the same bug,
I might provide additional information.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
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/1154431
Title:
Unity doesn't start up
To manage notifications about
Public bug reported:
I'm running stock 13.04. Previously I was affected by bug 982889. Now
that X comes up, I don't see unity - no common toolbar on the top, no
icons on the left side, no unity in the process list.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
On 13 Feb 19, Bryce Harrington wrote:
Oh, and if you do run the PPA, I'd like to see your Xorg.0.log,
regardless of whether it worked or not, so I can verify the error code
being passed up.
Please find my Xorg.0.log and Xorg.0.log.old attached. I see Xorg win
sometimes (1 out of 5 reboots?).
Public bug reported:
Fresh install of 13.04 dev on this desktop machine with an Nvidia
graphics.
Nouveau only shows the system is running in low-graphics mode dialog and
doesn't allow reconfiguring.
Nvidia-current drivers give a desktop but X crashes very often.
12.04 worked just fine on this
** Summary changed:
- touchscreen not recognized on del xps 17
+ touchscreen not recognized on dell xps 17
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/832189
Title:
touchscreen
Public bug reported:
I just installed the nvidia-current driver through jockey. Upon reboot,
only 1 display was detected by Xorg/nvidia driver. The other display
remained in standby.
I had to start nvidia-settings and configure the second display in
TwinView configuration and save the result to
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/726492
Title:
nvidia driver doesn't detect two displays by default
___
Mailing
Seen on up to date natty too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in ubuntu.
https://bugs.launchpad.net/bugs/583760
Title:
Mouse cursor dissappears with nouveau
___
Mailing list:
Public bug reported:
Binary package hint: xorg
Twice in two days now, X just died on me while work and returned me to
the gdm screen
Xorg.0.log.old suggests a segfault. I suspect (but not confirmed yet)
that it happens when some video is playing.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/50424638/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/50424639/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50424640/Dependencies.txt
**
apparently the script runs a compiler check; I don't know why it fails, can't
reproduce it, but I assume that it tries to compile something which fails. I
mean this testcase
Please find it attached.
** Attachment added: conftest.sh
http://launchpadlibrarian.net/34318011/conftest.sh
--
On Wed, Oct 21, 2009 at 12:48 PM, Matthias Klose
matthias.kl...@canonical.com wrote:
Please attach the testcase and options to build the testcase.
What testcase are you looking for? The nvidia dkms package itself?
--
package nvidia-185-kernel-source 185.18.36-0ubuntu8 failed to
Public bug reported:
Just finished updating Karmic using update-manager and was shown this
error.
ProblemType: Package
Architecture: amd64
Date: Tue Oct 20 14:23:11 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit
status 10
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/34034724/AptOrdering.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34034725/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34034726/CurrentDmesg.txt
**
make.log for the dkms package is also attached.
** Attachment added: make.log
http://launchpadlibrarian.net/34034848/make.log
--
package nvidia-185-kernel-source 185.18.36-0ubuntu8 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 10
I don't run Jaunty anymore. You can close this bug.
--
Display resolution is set incorrectly
https://bugs.launchpad.net/bugs/335379
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
On 09 Jul 21, Bryce Harrington wrote:
The upstream bug is marked fixed, although it's a little ambiguous what
exactly the fix is. In any case I know from other people's testing that
a HUGE amount of bugs of this class have been fixed in recent months so
it's a good guess this bug is gone.
2.6.31-rc2 fixed the issue.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Fix Released
--
2.6.31 kernel + xorg doesn't detect correct resolution on LG Flatron L226W
https://bugs.launchpad.net/bugs/395115
You received this bug notification because you are a member of
On 09 Jul 06, Jithin Emmanuel wrote:
I believe that the issue is with kernel 2.6.31 and not xorg.
Amit can you verify that?
Since the KMS stuff is so inter-linked, I can't be sure. But since the
only variable is the kernel (2.6.30 works, 2.6.31 doesn't), it might be
a kernel issue.
--
2.6.31
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/28653280/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28653281/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28653282/Dependencies.txt
**
This bug has not been observed in newer versions of Ubuntu.
** Changed in: mesa (Ubuntu)
Status: Incomplete = Invalid
--
sundancer2 crashed with SIGILL in _mesa_x86_64_transform_points4_2d_no_rot()
https://bugs.launchpad.net/bugs/199615
You received this bug notification because you are
Confirmed that with the packages from the PPA, X started up all the way
with KMS enabled and no xorg.conf.
--
KMS failed on Lenovo X60s: Cannot run in framebuffer mode. Please specify
busIDs for all framebuffer devices (KMS bug)
https://bugs.launchpad.net/bugs/383407
You received this bug
** Bug watch added: freedesktop.org Bugzilla #21480
https://bugs.freedesktop.org/show_bug.cgi?id=21480
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=21480
Importance: Unknown
Status: Unknown
--
Xorg driver locks up and screen goes blank (black) -
Since the kernel doesn't yet provide the mach64_drm.h header, marking
this as invalid for linux.
Please reopen this when the kernel starts providing the headers.
** Changed in: linux (Ubuntu)
Status: New = Invalid
--
libdrm-dev should install mach64_drm.h
Public bug reported:
Binary package hint: xorg
On my Karmic upgrade, Xorg periodically just blanks out (black screen)
and I can never get it back.
Sshing into the machine shows the following attached logs
(/var/log/kern.log)
Jun 6 00:12:59 k2 kernel: [56280.880058] INFO: task events/0:9
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/27659519/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/27659520/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27659521/Dependencies.txt
**
On Thu, Jun 04, 2009 at 06:55:01PM -, Bryce Harrington wrote:
This is a weird error, and not consistent with other problems I'm
familiar with. Why is it so hung up regarding the framebuffer? Well, a
few random ideas... I note you're running with no xorg.conf, and I
wonder if you'd get
On Thu, Jun 04, 2009 at 06:55:01PM -, Bryce Harrington wrote:
Hi Amit, I've forwarded this bug upstream to
https://bugs.freedesktop.org/show_bug.cgi?id=22089 - please subscribe to
that bug report in case upstream needs more info or wishes you to test
something. Thanks ahead of time.
This
** Bug watch added: freedesktop.org Bugzilla #21315
https://bugs.freedesktop.org/show_bug.cgi?id=21315
--
KMS failed on Lenovo X60s: Cannot run in framebuffer mode. Please specify
busIDs for all framebuffer devices (KMS bug)
https://bugs.launchpad.net/bugs/383407
You received this bug
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/27474965/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/27474966/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27474967/Dependencies.txt
**
For everyone that has sent their lshal output to this bug, try the
following:
$ lsusb
Find your vendor id and product id for the touchscreen.
$ modprobe usbtouchscreen
$ sudo sh -c echo vendor id product id
/sys/bus/usb/drivers/usbtouchscreen/new_id
e.g. From my lsusb, one of the entries is:
33 matches
Mail list logo
