Public bug reported:
I've had two X crashes today on this machine running current Wily; but it's
been stable for years,
so I'm assuming that something in the last couple of days has broken it. I'm
just running KDE5 with Pidgin irc
and a little bit of web browsing (only lightly on this
** Attachment added: "Xorg.0.log.old from after the restart of X"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1492503/+attachment/4457719/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Flipped package to intel xserver
** Package changed: ubuntu = xserver-xorg-video-intel (Ubuntu)
** Bug watch added: freedesktop.org Bugzilla #45092
https://bugs.freedesktop.org/show_bug.cgi?id=45092
** Also affects: xserver-xorg-video-intel via
Added suspected upstream bug number.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1393205
Title:
Intel q35 bug on Ubuntu 14.04 (Screen Artifacts)
To manage notifications
Comment #19 https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1248368 is showing a regressing caused by this fix.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/408903
Same here; unusable - 14.04 in KVM guest, dies immediately after I search for
'terminal' and select it.
The terminal eventually starts but by that time compiz is dead.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hi ALl,
I was looking back through my list of bugs and noticed this had been closed
in an odd way.
Jorge you reported this a while back; is it still a problem for you? Have you
tried more recent updates?
** Changed in: xorg (Ubuntu)
Status: Fix Committed = Incomplete
--
You received
OK, fair enough - I'll leave it as incomplete and it should close itself
in a couple of months; leaves time for anyone else woh was affected at
the same time to jump in.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I don't currently have Ubuntu on the system that triggered that so can't really.
However, I think Olivier is onto something.
--
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/717870
High: Problem with essential hardware component (touchpad) - although
the work around of the mouse is tempting to set a little lower.
Hamilton please confirm:
1) which model computer you're using
2) Does 13.10 help?
3) When you say you reverted to 12.04, which 12.04?
Still seems to do it on Saucy host, and guest. (Guest up to date as of
2013-10-12, host a few days older).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-qxl in Ubuntu.
https://bugs.launchpad.net/bugs/1176920
Title:
lots
Yes, but I didn't have many other ideas how to track it down except to
leave it to the compiz/X devs.
--
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/1205633
Title:
Xorg stalls out the whole
hmm, a bit tricky to figure out from that.
Can you login from another machine over a network while it does that?
If so then it's worth seeing if the remote shell hangs while the display is
hung,
and use something like top to see what's happening.
--
You received this bug notification because
Hi Mirko,
I noticed in your X log file there is a stream of errors like:
[ 589.510] (EE) RADEON(0): [DRI2] DRI2SwapBuffers: bad drawable
[ 589.542] (EE) RADEON(0): [DRI2] DRI2SwapBuffers: bad drawable
can you figure out if they correspond to your stalls? I think if you
were to look at
Flipping to xserver-xorg-video-intel since there are loads of i915
errors in the current-dmesg logs.
Karol: Tell us a bit more about your setup; what displays do you have
connected, via what interface?
From the logs I think you have one on an HDMI output, and something else
(lower res?) on a
Is this https://bugs.freedesktop.org/show_bug.cgi?id=54013 ?
** Bug watch added: freedesktop.org Bugzilla #54013
https://bugs.freedesktop.org/show_bug.cgi?id=54013
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
I've just seen this on an openSUSE vm, so whatever it is, it's not just
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/774434
Title:
mouse pointer disappears in
Craig: I'm curious, what apps are you seeing looking bad because of
this; my understanding from what Chris is saying and from your xdpyinfo
is that it's just the default that's 16, so any app that wants to do
nice graphics should be able to ask for the highest quality visual
rather than the
On the basis that you say it's only this kernel that does it I've changed the
package to the kernel package.
You say it doesn't respond to anything; how about:
* Does it ping from another machine on your network (if you have one)
* Does ctrl-alt-f1 go to a text console (ctrl-alt-f7 or f8 to
Can you try an
apport-collect 1184085
after triggering it? In the hope it will include a full set of info.
(I tried triggering this on my Arch box running KDE on Intel and it
doesn't trigger, so it's not as general as that)
From your logs:
[ 409.670] (EE)
[ 409.670] (EE) Backtrace:
[
High: High impact on small proportion of users (i.e. xfig users on Intel) -
but I guess ther eis a chance that it could be a cause of other X crashes as
well.
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member
I merged 1037895 into this
Changing from the intel xserver to gnome-screensaver; from the reports it
doesn't seem to be Intel specific.
Whether it's actually gnome-screensaver or something else seems to be difficult
to tell; most people seem to be saying removing it helps them, but #30 is not
Still present in current Saucy ISO on a raring host.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1080674
Title:
[QEMU] Corrupted desktop screen for raring desktop
Public bug reported:
Saucy-daily iso in a KVM guest under raring running with QML/Spice.
Unity as the desktop.
Every time I open any app I get a few more lines of debug/warnings in
the X logs in the guest.
It doesn't seem to be having any bad effect other than fillin the logs.
ProblemType:
and some more that weren't in the set captured by the report:
[ 578.859] qxl_surface_create: Zero width or height
[ 578.861] - 0th attempt
[ 578.861] - OOM at 658 59 32 (= 155288 bytes)
[ 578.861] Cache contents: null null null null null null null null null null
null null null null null
OK thanks Chris - is this a recent change?
the reporter is saying that on 12.10 it was defaulting to 24bpp
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1173649
Title:
OK, fair enough. IMHO it would have been a good idea to put something
in a release note or the like - I don't think I've seen any other PC
system default to 15bpp for many years.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Hi,
Can you add to this bug report the output of dmesg and your
/var/log/Xorg.0.log please.
I think if you run
apport-collect 1173649
I think it should add that and loads of other stuff.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
Huh, OK that'sweird
From your Xorg.0.log:
[40.999] (==) intel(0): Depth 15, (--) framebuffer bpp 16
[40.999] (==) intel(0): RGB weight 555
so that's saying the default is 15bit
and from your xdpyinfo output:
screen #0:
dimensions:1680x1050 pixels (444x278 millimeters)
You say it was a kernel panic; so it belongs in the kernel package.
** Package changed: xorg (Ubuntu) = linux (Ubuntu)
--
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/1161575
Title:
Kernel
Chris can you explain that statement please; he's seeing 15bpp, I'd
expect 24bpp and that's what I've seen everywhere else.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Maarten: Filled in test case stuff (what did you mean about eth2?)
I wonder if this should be marked security; we know it's
scribbling over bits of the X server, that's running as root,
although I don't know how to control what is scribbled where
(I'll get
Precise won't get Unity 3D up (even with some forcing); so I'll say not
repeatable.
[If as per previous question it's a security issue though that may need some
more looking at]
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Thanks Maarten; that does seem to have nailed it in Raring; SRU for
Quantal?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SIGABRT in
Thanks Maarten, that looks good; I guess with cirrus module loaded it's
probably not actually that important on a raring release; but it's good
to fix anyway, and I'd say backport to Quantal.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with
This looks suspiciously similar to bug 1039341(which is marked fix
released - but because the reporter couldn't reproduce) .
Melchiaros: Can you reproduce this every time ? How is the monitor
connected - VGA?DVI?HDMI?
--
You received this bug notification because you are a member of Ubuntu-X,
Hi Adrien,
This can be rather difficult to find the cause of; I've seen it once on one
of my machine, and it turned out to be an application I was using that was
doing a lot to the X server for no good reason. (It was animating a little
icon but was trying to be too clever).
Run top and
Maarten:
OK, it still crashes, and the reason is you're MIN/MAX aren't sufficient:
cirRefreshArea: pbox: (-958,52 / -236,486) clipped: (0,52 / -236,486)
pScrn-vX/Y 1024,768 rotate=0
you need to use both MIN and MAX on each coordinate to cope with the box
being completely off one side of the
Hang on, scrap that analysis - I noticed the logs show it's not loading
the rebuilt cirrus module with that change; It's now showing an EABI
mismatch error. I'll get back to you.
Dave
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Triaged = Incomplete
--
You received this
and to compound things, the kernel driver is now working on raring, so I
can't load this one to test it; let me get back to you next weekend.
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
** Attachment added: lankhostversion.png
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3460902/+files/lankhostversion.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: myversion.png
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1043513/+attachment/3460904/+files/myversion.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
Hi Maarten,
That patch isn't happy; but I'm not sure why yet; I've attached three screen
captures:
1) The version with the ubuntu built package - which shows the strange
crosshatching from bug 1080674
2) myversion.png - the version with my patch, looks the same as (1) but
doesn't
psivaa: Can you run an xdpyinfo in VBox and KVM and attach both the
outputs?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1080674
Title:
[QEMU] Corrupted desktop screen
reporter asked for it to be closed.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
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/1087115
Title:
Xorg process is eating my CPU cores
Hi,
Attached is a patch that seems to fix this; however it needs looking at by
someone who understands the code; in particular I have some questions:
1) Does this also need to go in cirRefreshArea8/16/24/32 ?
2) Why is the generic one being called if there are those specialised ones
Yeh I'm also seeing this; note that the cirrus driver is the same
1:1.5.1-0ubuntu2 Quantal (that works) and Raring (where it gets this
corruption).
Note that Cirrus tends to run with 24bpp packed that always adds fun and
excitement; and might explain the odd rhythmic patterning.
--
You
OK, I'll leave it as 'incomplete' for the moment; if you get around to trying
12.10 again then please add any more detail you can and flip it back to 'New'.
There's probably not too much we can do without more diagnostics, other than to
remember this and watch out for any similar reports.
Thanks
Hi Jorge,
If you use shift during booting to get the 'grub' menu to display, it should
let you choose a previous kernel version to try;
if that helps you then please add a note saying the kernel version that works
and the version that fails.
Also can you describe the make and model of the
Have you got a different resolution monitor that you could borrow to try it
with?
I notice the monitors you are using are 1366x768 and I've seen other problems
with that res because it's not divisible by 8
exactly, and various things sometimes get upset.
(Only a hunch, may be wrong).
--
You
Confirmed still happening in Raring (That's a raring guest with Quantal
host) as of today's install.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg
Whether the two failures are related is difficult to say; the SecondLife
one seems to be failing with a fairly clear problem finding the dri
modules:
libGL: OpenDriver: trying /tls/i965_dri.so
libGL: OpenDriver: trying /i965_dri.so
libGL error: dlopen /i965_dri.so failed (/i965_dri.so: cannot
It's interesting, I can't trigger this in either my quantal or raring
vm, but I've had it happen on two different quantal machines; one Intel
graphics one ATI (open driver).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I've just put a load of comments on the upstream bug
The short story is that a patch to
Xext/xres.c ResFindAllRes
to change
counts[(type TypeMask) -1]++
to
if ((type TypeMask)!=0) counts[(type TypeMask) - 1]++;
stops the crash.
The longer story is, I don't think that case of a 0
To simplify my instructions from comment #15:
1) Open a terminal (sits in top left)
2) Ctrl-alt-down arrow to move down one virtual deskop
It blows up at (2).
(pScrn-virtual X/y in cirRefreshArea is 1024/768)
--
You received this bug notification because you are a member of Ubuntu-X,
which
Some random extra debug (from a separate run):
(gdb) up
#3 0x7f0485ef1af3 in ShadowCopyArea (pSrc=0x7f048ba948f0,
pDst=0x7f048c4ca910, pGC=0x7f048c3def70,
srcx=optimised out, srcy=optimised out, width=optimised out,
height=434, dstx=0, dsty=0)
at
Confirmed, I can see this on
ii libxt-doc 1:1.1.3-1 allX11 toolkit
intrinsics library
but I also see this in libx11-doc in
/usr/share/doc/libx11-dev/libX11/libX11.html, so this is something
common - some docbookism???
** Changed in: libxt (Ubuntu)
Importance:
actually, I seem to have found a reasonably repeatable sequence:
1) Login
2) open a gnome-terminal
3) Walk through the 4 workspaces with ctrl-alt-arrows, within 2 or 3 times of
doing that reasonably quickly it blows up.
--
You received this bug notification because you are a member of
Hi Bryce,
See backtrace attached; just generated, on an up to date Quantal:
ii xserver-xorg-video-cirrus 1:1.5.1-0ubuntu2
amd64X.Org X server -- Cirrus display driver
Looks the same one to me; it's a lot harder to hit this than it was a
few weeks ago - this survived an
Some more diags;
(gdb) p *pbox
$2 = {x1 = -958, y1 = -716, x2 = -236, y2 = -282}
I'm not sure what the space these values are working is supposed to be; if
they're supposed to be -ve then they're in a sensible
range as far as I can tell - but are they supposed to be -ve?
(gdb) p
Timo: As mentioned in #10 It's worth checking that bug 1056511 as well
which is nouveau based, the backtrace looks similar enough to me to make
me wonder if it's not driver specific.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Looks like 1048304 is another dupe of this?
1056511 looks like a very similar backtrace to me as well, even though the
driver at the last stage is nouveau rather than cirrus, the rest of it looks
the same.
As of todays Quantal update it's stable enough to allow me to login and
get a few minutes
I agree with Jarosław's comment #29, that this looks like
http://wiki.openchrome.org/pipermail/openchrome-
devel/2012-August/000737.html you can see the i2cProbeAddress call in
the backtraces from both Lars and Michael.
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status:
Looking at the Xorg.0.log we have the following; so it's an X server
crash:
[23.755] (EE) Backtrace:
[23.755] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb77519e9]
[23.755] (EE) 1: /usr/bin/X (0xb75aa000+0x1ab8d6) [0xb77558d6]
[23.755] (EE) 2: (vdso) (__kernel_rt_sigreturn+0x0)
Lars, can you install the xserver-xorg-video-openchrome-dbg package
(sudo apt-get install xserver-xorg-video-openchrome-dbg), then reboot
and attach the new Xorg.0.log; with any luck it'll have a better
backtrace in.
Dave
--
You received this bug notification because you are a member of
High-A problem with an essential hardware component (Video card)
** Package changed: xorg (Ubuntu) = xserver-xorg-video-openchrome
(Ubuntu)
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Importance: Undecided = High
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status:
OK, thanks - doesn't look like it's added any more info there, I'll just
have to hand this over to the X guys.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1041625
High: Has a moderate impact on a large portion of Ubuntu users (estimated)
(FireGL not uncommon, and it's in 12.04 as well)
** Package changed: ubuntu = fglrx-installer (Ubuntu)
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = High
--
You received this bug notification
High: Has a moderate impact on a large portion of Ubuntu users
(estimated)
(865984 is a possible dupe - backtrace isn't quite the same though)
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
Looks like a graphics driverism (confirmed by comment #2 as well).
** Package changed: frozen-bubble (Ubuntu) = xserver-xorg-video-nouveau
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
OK, so bash-completion is doing the right thing here; it's looking for
the next director,y finding the right thing and there is only one
directory to go to; so this is correct behaviour.
So, I say if this is a bug it's x11-common's.
So - is it a bug?
Well /usr/bin/X11 is probably there for
as per previous comment, I believe this is an invalid.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
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/565447
Title:
bash completion cd
This seems to be fixed in current Quantal; if your previous upgrades broke it
in this way then you'll need to
reinstall the xservers that disappeared; certainly I can now install
xserver-xorg-video-radeon and xserver-xorg-video-ati and I'm back with
a working accelerated X (Note you need the
Hi Maurico - what graphics card do you have in your LTS box?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/774434
Title:
mouse pointer disappears in ubuntu (11.04
Confirmed - it also affects me
Medium - although it's a problem with an essential component (video card) that
would be 'high' since it only slows it rather than kills it, it seems more
appropriate to be medium.
** Changed in: xorg-server (Ubuntu)
Importance: Undecided = Medium
** Changed
High-Problem with an essential hardware component (monitor)
** Changed in: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
High - A problem with an essential hardware component (Keyboard)
** Changed in: xkeyboard-config (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
I've just encountered this on my Quantul box; it lost the xserver-xorg-
video-radeon driver (see separate bugs) - so it seems to be doing it
with the FB driver it's dropped back to.
xserver-xorg-core 2:1.12.1.902-1ubuntu1
--
You received this bug notification because you are a member of
** Summary changed:
- mouse pointer disappears in ubuntu 11.04
+ mouse pointer disappears in ubuntu (11.04 onwards...)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/774434
Flipping to fglrx since it's the closed driver they're using
High - problem with an essential hardware component (video card)
** Package changed: xserver-xorg-video-ati (Ubuntu) = fglrx-installer (Ubuntu)
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided = High
--
You received
(Importance High - Essential component)
** Changed in: lightdm (Ubuntu)
Importance: Undecided = High
** Changed in: lightdm (Ubuntu)
Status: Incomplete = New
** Package changed: lightdm (Ubuntu) = xserver-xorg-video-ati (Ubuntu)
--
You received this bug notification because you are
OK, thanks - I'll let the X guys look at this a bit further.
Notes:
Your /var/log/Xorg.0.log looks fine to me
however the x-0.log in the tar from your /var/log/lightdm looks dodgier:
(EE) No supported AMD display adapters were found
(II) [KMS] drm report modesetting isn't supported.
(EE)
Public bug reported:
I'm filing this as hopefully a generic/master bug (if any one knows of
another please add).
I've got two entirely distinct set ups that won't do the 1366x768 that the
monitor/display is capable of over VGA;
I suspect this is related to the discussion here:
Steven; can you explain why this requires a reboot - that's not the behaviour
I've seen.
For me, the mouse disappears until you move it and it reappears and then
disapears again - reboots
don't help.
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Hi Jules,
It's interesting your backtrace does still include an entry in librecord - it
looks very much like the original bug in 774978.
--
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/940761
Jadi, Christian, Retrokid, Jules,
Are you sure it's the same bug? Only a few random X crashes fit into this
bug, It's only the same bug if the backtrace (in /var/log/Xorg.0.log.old after
X restarts) ends in something like:
[ 15223.014] 2: /lib/x86_64-linux-gnu/libpthread.so.0
Confirm - that fixed it for me (on both my machines) - thanks! That was
a really frustrating bug in use!
--
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/925785
Title:
Starting to scroll
Thanks - I pulled the packages from the 0.0.16-2 from the link on the
packages page; works nicely (mouse a bit random in spicey, but not sure
where that's from).
The server seems stable and lets me do things like play youtube and BBC
iPlayer video.
Dave
--
You received this bug notification
** Package changed: xorg (Ubuntu) = xserver-xorg-video-nouveau (Ubuntu)
--
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/926637
Title:
Xorg crashes to black screen when
ah, so it's not just me
For me the behaviour is that if I repeatedly scroll down slowly sometimes the
scroll will suddenly jump right back up.
I had wondered if it's something like moving the mouse at the same time as I
was scrolling but I don't think so.
(Logitech M90 USB mouse)
--
You
'A problem with an essential hardware component (disk controller, laptop
built-in wireless, video card, keyboard, mouse)' - High
** Changed in: xkeyboard-config (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Hi Serge,
Are you going to push a build with that change in?
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-qxl in Ubuntu.
https://bugs.launchpad.net/bugs/913314
Title:
Corrupted display with Spice
To manage
Public bug reported:
Hi,
This is a precise kvm guest running on a precise host. At boot, after
logging in and starting unity (2d?) clicking on the terminal button causes X to
crash about 50% of the time.
Host command to start the guest:
kvm-spice -vga qxl -spice
** Package changed: xorg (Ubuntu) = xserver-xorg-video-qxl (Ubuntu)
--
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/913311
Title:
X crashes repeatedly (qxl/spice)
To manage notifications about
** Also affects: spice (Ubuntu)
Importance: Undecided
Status: New
** Package changed: xorg (Ubuntu) = xserver-xorg-video-qxl (Ubuntu)
** Also affects: qemu-kvm-spice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
(Also see bug 913311)
Unity in xorg-qxl doesn't render properly - the simplest example is here:
http://www.treblig.org/debug/badspice.png
where you can see the terminal title bars are missing and the top of the
left panel is missing.
Both host and guess are upto date
Good, that's got the xdiagnose data in it, so hopefully someone who
knows the Nvidia stuff can look at it.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Backtrace:
[ 343.970] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]
[ 343.970] 1: /usr/bin/X (0x40+0x64b7a) [0x464b7a]
[ 343.970] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f83899bf000+0x10060)
[0x7f83899cf060]
[ 343.970] 3: /usr/lib/xorg/modules/extensions/librecord.so
Medium-Moderate impact on core app
** Changed in: x11-xserver-utils (Ubuntu)
Importance: Undecided = Medium
** Changed in: x11-xserver-utils (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
1 - 100 of 254 matches
Mail list logo
