** Package changed: ubuntu => xserver-xorg-video-intel (Ubuntu)
--
X with intel driver crashes on video playback
https://bugs.launchpad.net/bugs/374431
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel 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
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.
https://bugs
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 receiv
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
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 xserver-xorg-vi
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: Undec
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 Ubun
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 pPriv->pScrn->
Some random extra debug (from a separate run):
(gdb) up
#3 0x7f0485ef1af3 in ShadowCopyArea (pSrc=0x7f048ba948f0,
pDst=0x7f048c4ca910, pGC=0x7f048c3def70,
srcx=, srcy=, width=,
height=434, dstx=0, dsty=0)
at ../../../../hw/xfree86/shadowfb/shadow.c:618
618 ../../../../hw/xfree86
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
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.
h
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
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 crash
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 open
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 ma
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 re
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,
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
anyway
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 received
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
** 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 xserver-xorg-video-cirr
** 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 crash
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 fo
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 bu
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.
https://bugs.
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 sc
Hi Marc,
Nicely fixed - that bug has been around for ages!
One question; Am I reading your comments right that this is due to the card
running in packed 24 bpp rather than 32? If so do you know why? Is that a
limitation of the cirrus being emulated?
Dave
--
You received this bug notificati
Hi Kevin,
Do you have a reference to the upstream bug that this patch came from?
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in Ubuntu.
https://bugs.launchpad.net/bugs/835817
Title:
xrandr client truncates pixel c
Hi Kevin,
Interesting - I've just tried this in an Oneiric vm and it's not done a
straight truncation - it seems to have done a bit of a round though, which
makes me wonder if your original bug is present or not;
dg@kdedev:~$ xrandr --newmode "640x480_75.00" 30.75 640 664 728 816 480 483 487
I've just:
1) Added xorg to the bug because I'm also seeing in a KDE session inside a
kvm guest on a separate machine - the KDE session is actually built from
source, rather than kubuntu. However given it's the same symptoms and gtk
shouldn't be involved it sounds like it may be more widespre
The sleeping is possibly bug 862813, but the GPU stuff is a separate
issue.
Dave
--
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/863232
Title:
When returning from sleep (WHY
* Colin Law (864...@bugs.launchpad.net) wrote:
> I am seeing the same symptom after login with a black screen and stuck
> mouse pointer in the middle of screen (well actually at mid point of
> virtual screen as I have dual screen setup) and similar messages in the
> logs. For me it is intermittent
** 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 xserve
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 machine).
** Package changed: ubuntu => xserver-xorg-input-evdev (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/871241
Title:
No keyboard input after logging in
To manage not
Hi Jasper,
By default Ubuntu doesn't have an xorg.conf - it works stuff out
automagically. You can create one and add sections in that you need. There is
also /usr/share/X11/xorg.conf.d which is a directory where you can add
fractions of config file.
Dave
** Changed in: xorg (Ubuntu)
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
--
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/870472
Title:
2048x1536 max resolution worked in 10.04,
Hi Ken,
Can you run apport-collect 874694with your machine in this state? It
should add a load of logs to the bug report to determine what's happening.
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubun
Odd; it doesn't! OK, can you add:
1) /var/log/Xorg.0.log
2) /var/log/kern.log
3) The output of xrandr
Dave
--
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/874694
Title:
Hi,
Can you please runapport-collect 874276 - it should add some bugs
to this log.
Dave
** Package changed: ubuntu => xorg (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/874
logs to this bug even!
--
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/874276
Title:
Corrupted video on Live CD with nVIDIA Cards
To manage notifications about this bug go to:
https://bugs.launc
Yes, we really need them from Oneiric.
--
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/874276
Title:
Corrupted video on Live CD with nVIDIA Cards
To manage notifications about this bug go to:
ht
Ken, thanks for the logs - can you just clarify what machine model this is and
what monitors it has?
xrandr and X think that it has a 640x480 internal LCD and an external higher
res monitor - what's the reality?
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
w
Hi Alen,
Please run
apport-collect 878501
on your computer - it will gather some logs and attach it to this bug;
then set the status on the bug back to 'New'.
What model of computer and keyboard do you have? When it freezes does
the mouse still move the cursor?
Dave
** Package changed:
** Package changed: ubuntu => xserver-xorg-input-evdev (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/874096
Title:
problem with Touchpad behavior on EEE PC 1000H &
Warren: Please file it as a separate bug because it's different hardware
- if it turns out to be the same reason then it'll get merged.
blueskyabove: Can you please runapport-collect 858046 it'll add
some logs and details of your hardware to this bug report.
Dave
** Package changed: ubun
OK, thanks - can you please also add:
1) A copy of /var/log/Xorg.0.log
2) The output of the command
sudo dmesg
What model did you say the machine and keyboard was?
Dave
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xor
Hi Alen,
Thanks for the info; I'll have to leave it to the X guys to debug further,
but looking at the logs it seems to see a keyboard:
[ 33.944] (II) XINPUT: Adding extended input device "AT Translated Set 2
keyboard" (type: KEYBOARD)
[ 33.944] (**) Option "xkb_rules" "evdev"
[ 33.944] (**) O
Can you add to this bug the URLs of the web pages you found describing
similar problems?
Dave
--
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/878501
Title:
ps/2 keyboard not
I've added linux into this bug since Alen says he fixed it by disabling
irqbalance
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- ps/2 keyboard not working
+ ps/2 keyboard not working [irqbalance?]
--
You received this bug notification because
** Package changed: ubuntu => xorg (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/883319
Title:
xrandr --scale 1.2x1.2 restricts area in which mouse moves
To manage notifications about
Hi Roger,
Sorry, I forgot to ask you to do something prior to the apport-collect; can
you install the xdiagnose package and then redo the apport-collect 858046-
that will then add *loads* of info about your X setup.
--
You received this bug notification because you are a member of Ubuntu-
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 x11-xserver
** Description changed:
In Ubuntu 10.04 when adding new modes using "--newmode" the pixel clock
is truncated, for example 119.9 will become 119. This is due to
check_strtod in xrandr.c returning an int when it should be returning in
double. This bug is already fixed upstream. Please con
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
(0x7f838736
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 nvidia-gr
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.
https://bugs
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 bec
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)
resol
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 Pani
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.
https://bugs.launchpad.net/bugs/117364
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:
incor
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 xserver-xorg-video
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 install
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: Bug
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
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
s
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 o
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 defaul
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 ubunt
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 Ub
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 D
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 /var/l
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 you
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 syst
Triaged: User supplied set of how to trigger and the upstream bug/patch
that fixes it.
** Bug watch added: freedesktop.org Bugzilla #60182
https://bugs.freedesktop.org/show_bug.cgi?id=60182
** Also affects: xserver-xorg-driver-ati via
https://bugs.freedesktop.org/show_bug.cgi?id=60182
Im
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 of
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? 12.04.1,12.04.2,12.04
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 wa
** 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 SIGABR
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 xserve
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 memcp
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 prec
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 xserver-xorg-video
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 subs
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:
http://mjg59.drea
(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
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) open
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
Title:
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
https://bugs.freedesktop.org/show_bug.cgi?id
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 a
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 port=5930,disable-ticketing
** 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
1 - 100 of 258 matches
Mail list logo
