Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=28882.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: xorg-server (Debian)
Status: Confirmed = Fix Released
--
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/705078
Title:
Xorg crashed with SIGSEGV in
** Changed in: xorg-server (Debian)
Status: New = Confirmed
--
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/705078
Title:
Xorg crashed with SIGSEGV in
Btw, resolution was that there was an out-of-memory situation which led
to the X crash.
So if anyone still finds there are other kinds of problems during
installation, you might want to analyze it as a memory bug...
--
You received this bug notification because you are a member of Ubuntu-X,
Bryce, thanks so much for this fix.
I'm still experiencing issues during installation. Admittedly it appears
to happen in a different section of code though the symptoms look
similar. I observed this using the 20110207 images that contain the fix
for this bug, and I was able to reproduce it on
Hi i'm from 709508.
Bryce Harrington wrote on 2011-02-04: #7
Were you able to successfully install after running into this crash?
Yes i was. But the system is somewhat strange (don't know how to describe).
I'll test it with todays build and report if the problem isn't solved (on my
Laptop).
** Branch linked: lp:ubuntu/xorg-server
--
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/705078
Title:
Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip()
The previous patch seems to still be relevant, so I've pushed it upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=33892
** Bug watch added: freedesktop.org Bugzilla #33892
http://bugs.freedesktop.org/show_bug.cgi?id=33892
--
You received this bug notification because you are a
Hi, visiting from bug 708744. I managed to collect a crash report of one
of our failed systems (a Dell Vostro 3400), which I'm attaching,
hopefully it will help confirm what Bryce found. This happens during the
live install process, stopping the installation and dropping the user
into a LiveCD
Hi Daniel, yes that looks like the same crash.
--
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/705078
Title:
Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip()
As luck would have it, I reproduced this bug myself while booting the
livecd on one of my systems.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Mine is bug #712866. However even though apport showed the error, I
didn't actually notice a crash of X... things seemed to come up fine in
the LiveCD environment.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because
Bumping to critical since this appears to be a widespread crash
reproducible on the livecd.
** Description changed:
I was doing an installation from ubiquity and during the file copy phase
X crashed.
+
+ #1 0x08067984 in DisableDevice ()
+ No symbol table info available.
+ #2 0x08067bb3
I'm noticing the crash appears in a libpixman call, the source code of
which is trivial:
PIXMAN_EXPORT void
pixman_image_set_has_client_clip (pixman_image_t *image,
pixman_bool_t client_clip)
{
image-common.client_clip = client_clip;
}
Looks like it could
Aha progress.
(gdb) bt full
#0 XISendDeviceHierarchyEvent (flags=0xbfb2d73c) at
../../Xi/xichangehierarchy.c:73
ev = 0x0
info = value optimized out
dummyDev = {public = {devicePrivate = 0x0, processInputProc = 0,
realInputProc = 0, enqueueInputProc = 0,
on
While not precisely the same crash, deb #596155 and fdo #28882 bugs are
all faulting on the same bit of code. create_bits_picture() attempts to
instantiate an image via a call to pixman_image_create_bits(), however
that call can fail under a variety of circumstances and return a NULL
image
** Bug watch added: Debian Bug tracker #596155
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596155
** Also affects: xorg-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596155
Importance: Unknown
Status: Unknown
** Bug watch added: freedesktop.org
Please test tomorrow's ISO with this fix and reopen if it still occurs.
--
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/705078
Title:
Xorg crashed with SIGSEGV in
Adds trivial check for null pointer
** Patch added: 210_pixman_null_ptr_check.patch
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/705078/+attachment/1828776/+files/210_pixman_null_ptr_check.patch
** Package changed: xserver-xorg-video-intel (Ubuntu) = xorg-server
(Ubuntu)
--
You
xorg-server (2:1.9.99.901+git20110131.be3be758-0ubuntu3) natty;
urgency=low
* Restore 208_switch_on_release.diff - the patch does not appear to be
upstream actually. Users confirm the fix regressed without it.
(LP: #711842)
* Add 210_pixman_null_ptr_check.patch:
** Changed in: xorg-server (Debian)
Status: Unknown = New
** Changed in: xserver-xorg-video-intel
Status: Unknown = Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I can confirm this on x86_64 architecture too
--
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/705078
Title:
Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip()
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Released = Confirmed
--
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/705078
Title:
Xorg crashed with
I've not been able to reproduce this bug with the rebuilt image this AM.
--
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/705078
Title:
Xorg crashed with SIGSEGV in
Ah, excellent, alright re-closing. If it regresses please open the bug.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
** Tags added: iso-testing
--
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/705078
Title:
Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip()
Natty 20110201 today's build installing from USB onto an Aspire one
D255E and got this bug.
Was running Unity 3D fine on the -12 kernel. Updated to kernel -18 and
will not run Unity 3D so since the USB booted into Unity 3D O.K. tried
an install. So the failure occurred on 2 Feb with the latest
Just had this appear iso-testing i386 Alpha 2. It appeared along with
bug 652916 and bug 702898 during installation just as the Keyboard
layout screen opened.
No idea if the three are in any way related.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Please read:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/702898/comments/8
--
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/705078
Title:
Xorg crashed with
This bug was fixed in the package xserver-xorg-video-intel -
2:2.13.901-2ubuntu3
---
xserver-xorg-video-intel (2:2.13.901-2ubuntu3) natty; urgency=low
* Add 107_solid_null_ptr.patch: uxa_acquire_solid() can return NULL
under some circumstances, so check for this when called.
Well maybe this is hard for you to test given that it shows up during
installation from a livecd.
Since the patch is just a simple null pointer check it's quite safe. So
for your testing convenience I'll go ahead and push it to the archive.
Please snag tomorrow's livecd image and test it to see
Famous last words, I know.
Anyway, reopen bug if for some reason this does not fix the crash.
I expect that there is a chance this is papering over a deeper problem,
and that the livecd will still fail but in some new and more exciting
way. If that does happen please file a new bug report
** Tags added: crash
--
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/705078
Title:
Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip()
** Tags added: patch
--
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/705078
Title:
Xorg crashed with SIGSEGV in pixman_image_set_has_client_clip()
Perfect mario, that points to the cause of the crash:
#0 0x00228004 in uxa_solid_rects (op=value optimized out, dst=0xbe38080,
color=0xbdb73c0, num_rects=4, rects=0xbdb73c8) at ../../uxa/uxa-render.c:1070
solid = 0x0
src = 0x0
Code at this location is:
This adds the missing null pointer checks.
** Patch added: solid_nullptr_check.patch
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/705078/+attachment/1802753/+files/solid_nullptr_check.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I've set up a PPA with the patch at
https://launchpad.net/~bryce/+archive/bug705078
Hopefully there should be a .deb there for you in a few hours. Give it
a go, let me know how it works.
While the check for the null pointer seems obviously needed, it's not
clear why it got a null in the first
Hrm, unfortunately it looks like the apport retracer is choking, so the
interpreted backtrace isn't valid.
However, poking around through the X logs, I notice it prints out a
bunch of this:
[40.000] (II) Dell WMI hotkeys: Device reopened after 1 attempts.
[45.264] (II) AIGLX: Suspending
The above is making me wonder if this is just a symptom of something
that changed in the kernel.
Could you please provide a bit more context behind this crash? Was this
the first time you tested natty livecd install on this hw, or have you
been doing regular test installs up until now and it
Hi Bryce,
Natty live CD install's haven't been functional for about a week, but
they were working fine on both of the pieces of hardware that i've filed
bugs on.
Ubuntu's ran successfully with previous versions (10.10 and 10.04) on
both pieces of hardware. I was able to complete the
And to be clear (probably should have reread before posting).
* Natty live cds from a week ago worked, but there haven't been any live
cds up until a few days ago
* I was able to successfully install 10.10 and 10.04 on both pieces of
hardware without workarounds. Same as the natty builds from
On Thu, Jan 20, 2011 at 08:25:26PM -, Mario Limonciello wrote:
* Natty live cds from a week ago worked, but there haven't been any live
cds up until a few days ago
Hmm, ok that's very interesting information.
There was a fix to mesa I posted to mesa for bug 681915 within the past
week, but
Bryce:
I can reproduce this at will by scrolling text in windows or dragging
windows around even on a live session. What exactly are you looking for
with gdb attached? I tried to attach gdb to the running X process, but
the box hung when I did that. Could you give me a particular set of
steps
Well managed to get it to crash over SSH, but doesn't look too useful to
me without ddeb's installed.
(gdb) backtrace full
#0 0x00491004 in ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
No symbol table info available.
#1 0x081183f8 in CompositeRects ()
No symbol table info available.
Here we go, here's a better one with -dbg symbols installed:
Program received signal SIGSEGV, Segmentation fault.
0x00228004 in uxa_solid_rects (op=value optimized out, dst=0xbe38080,
color=0xbdb73c0, num_rects=4, rects=0xbdb73c8) at ../../uxa/uxa-render.c:1070
1070../../uxa/uxa-render.c:
45 matches
Mail list logo
