>From the upstream bug report, the failure in OsLookupColor() is just a
common point where the system falls over once it's run out of graphics
memory. There could be a number of reasons why the memory got exhausted
in the first place (e.g. video drivers leaking memory, misc. bugs in GL
apps, ...)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Bryce Harrington (bryce) => (unassigned)
--
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/174650
Title:
x
I no longer use the machine in question.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Also affects: xserver-xorg-video-ati (Ubuntu Saucy)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-ati (Ubuntu Saucy)
Importance: Undecided = High
** Tags added: saucy
** Changed in: xserver-xorg-video-ati (Ubuntu Saucy)
Assignee: (unassigned) =
** Changed in: xdiagnose
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1005573
Title:
Apport should not present the user with non-actionable information
Expired, here and upstream.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: Incomplete = Invalid
--
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/713864
Believed to be fix now as of plymouth (0.8.8-0ubuntu6.1) and lightdm
(1.6.0-0ubuntu2.1).
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Confirmed = New
--
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/1174042
Title:
System crashes with open-source
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
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/1170174
Title:
Freeze when starting up - screen won't turn on, fan
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = New
--
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/1168188
Title:
black screen on lenovo g580
** Changed in: mesa (Ubuntu Oneiric)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
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/830136
Title:
[sandybridge-m-gt2+] GPU lockup
** Changed in: fglrx-installer (Ubuntu)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
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/772873
Title:
Vino does not work
** Changed in: mesa (Ubuntu)
Assignee: Bryce Harrington (bryce) = (unassigned)
** Changed in: mesa (Ubuntu)
Status: Triaged = Invalid
--
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
** Changed in: nvidia-graphics-drivers-updates (Ubuntu)
Assignee: Bryce Harrington (bryce) = Canonical X.org (canonical-x)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net
** Changed in: fglrx-installer (Ubuntu)
Assignee: Bryce Harrington (bryce) = Canonical X.org (canonical-x)
--
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/960597
Title:
package
** Changed in: xorg-server (Ubuntu)
Assignee: Bryce Harrington (bryce) = Canonical X.org (canonical-x)
--
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/836876
Title:
not checked
** Changed in: xdiagnose (Ubuntu)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
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/747338
Title:
LiveCD should have
** Changed in: xkeyboard-config (Ubuntu Precise)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/937822
Title:
[precise] F10
Fwiw, I don't get an X crash when tapping Windows+P. If I hold Windows
long enough, the shortcuts menu pops up (normally), but Win+P gives me
nothing. Are you still seeing this crash with recent raring?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I also tested with the screen rotated (xrandr -o 1). Hitting the key
combination under unity causes the screen to return to normal
orientation, however the xserver did not crash. Also attempted to use
the key combo while rotating the screen simultaneously but also did not
repro any crash.
--
If you can still reproduce the crash, give this patch a try. It skips
damaging the pixmap on rotation if there's no drawable. So, possibly
this could result in less pretty rotation animations but only in
situations where X would otherwise be crashing.
** Patch added:
I've set up a ppa to make it easier for you to test the patch:
https://launchpad.net/~bryce/+archive/lp1155136
If anyone affected by this bug is still able to reproduce the crash
currently, then install the xserver from the PPA and verify it resolves
the crash and report back here.
** Changed
** Description changed:
I don't have any additional info because I am not sure why the error
happened. I was just surfing the internet when I received this message.
I did, however, have both Firefox and Chrome opened at the same time
along with a music player (Musique).
+
+ #8 signal
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Xorg freeze - GPU lockup
+ [radeon] Xorg freeze - GPU lockup; doesn't occur with mainline kernel
3.8.0-030800rc3-generic
** Summary changed:
- [radeon] Xorg freeze - GPU lockup; doesn't occur
As per
https://errors.ubuntu.com/problem/a31cdcd9bf251f11fae54d2c9e4dcf24e37cf64f
this issue also affects Quantal.
** Also affects: xdiagnose (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: xdiagnose (Ubuntu Quantal)
Importance: Undecided = Medium
** Changed in:
As per
https://errors.ubuntu.com/problem/b7df7d76c9f58330e3da6c6d30d4463ac282ae32
affects Quantal as well
** Information type changed from Private to Public
** Changed in: xdiagnose (Ubuntu Quantal)
Importance: Undecided = High
** Changed in: xdiagnose (Ubuntu Quantal)
Status: New =
...however as of 3.2.3 the apport hook is no longer being run, so this
issue should not crop up in practice anymore.
** Changed in: xdiagnose (Ubuntu Quantal)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
...however as of 3.2.3 the apport hook is no longer being run, so this
issue should not crop up in practice anymore.
** Changed in: xdiagnose (Ubuntu Quantal)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Information type changed from Private to Public
--
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/1155948
Title:
Xorg crashed with SIGABRT in updateMotionHistory() - buff =
Unfortunately that bug has hit its maximum # of dupe bugs. So I'll
close out this bug report instead of marking it as a dupe.
Thanks again
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Changed in: xorg-server (Ubuntu)
Importance: Medium = High
--
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/1161777
Title:
Xorg crashed with SIGABRT in x86emuOp_mov_byte_R_R()
To
What is the command line you're using? Does it work if run from gnome-
terminal? Does it show any error messages?
** Changed in: xdiagnose (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in
You aren't the first to mention keyboard or mouse problems when using
failsafeX, but the issue is not reproducible here.
The failsafeX server doesn't enable or disable input devices, and there
isn't any particular difference in how it handles them vs. standard X,
although some daemon processes
https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fbin%2Fxdiagnose%3AIOError%3Amove%3Ahandle_enable_apport%3Amove%3Acopy2%3Acopyfile
This indicates people are still running into problems using xdiagnose on
12.10 due to not running it as root, so reopening task.
** Changed in: xdiagnose (Ubuntu
** Description changed:
+ [Impact]
+ xdiagnose requires root permission to run, otherwise it crashes when it tries
to update the grub configuration.
+
+ This is showing up in the automatically collected errors:
+
** Description changed:
[Impact]
xdiagnose requires root permission to run, otherwise it crashes when it tries
to update the grub configuration.
This is showing up in the automatically collected errors:
** Also affects: xdiagnose (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: xdiagnose (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: xdiagnose (Ubuntu Quantal)
Status: Triaged = Fix Committed
** Changed in: xdiagnose (Ubuntu Raring)
Good to hear. We're anticipating seeing a formal fix for 982889 before
long.
--
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/1165306
Title:
Xorg crashed with SIGABRT in
Sounds like a plan.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = 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/1094097
Title:
Xorg crashed with SIGSEGV
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
--
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/1163425
Title:
[hybrid] Displays detects a secondary unknown display
sudodus, thanks for this information.
I think you want to install python-launchadlib. (I thought that was
installed by default; by chance did you uninstall it manually? If not
then there may be a bug there too...)
--
You received this bug notification because you are a member of Ubuntu-X,
So I guess you have three bugs:
1. Xorg crashed (this bug)
2. The webcam generates bad jpeg images
3. python-launchpadlib wasn't installed
I'd like to focus this bug report only to the first issue. Bug reports
for the second and third would be worth filing, but I'm not sure what to
file
Actually I did test against quantal in #35, I just typo'd badly and
called it oneiric. I apparently fail at the alphabet.
== QUANTAL-proposed ==
Linux lynmouth.bryceharrington.org 3.5.0-26-generic #42-Ubuntu SMP Fri
Mar 8 23:18:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Before:
Not necessarily the same bug, this one appears to be crashing in SNA
xserver code. We may be able to fix this on the X side.
A local workaround might be to run with UXA instead of SNA.
** Description changed:
Xorg crashes every time when I try to run ReText with PyQt built against
Qt 5.
+
*** This bug is a duplicate of bug 1163635 ***
https://bugs.launchpad.net/bugs/1163635
Public bug reported:
Seen in the wild at:
https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fshare%2Fapport%2Fpackage-
hooks%2Fsource_xorg.py%3AAttributeError%3A%2Fusr%2Fshare%2Fapport
** Tags added: kernel-handoff-graphics
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
Chris, what is the upstream status for the ring kicker patch? Is that
likely to get incorporated upstream, or do you feel it needs further
polish before it's ready? Would this patch incur some risk of
regressions in other areas were it be backported for inclusion in
Ubuntu?
--
You received
** Description changed:
After reinstalling nvidia-current, launching Unity Desktop failed with
message no decoration
+
+ #4 0xb7781d52 in AbortServer () at ../../os/log.c:655
+ No locals.
+ #5 0xb778243e in FatalError (f=f@entry=0xb7786426 no screens found)
+ at ../../os/log.c:793
+
[Duplicate of bug #982889, which has reached its duplicants limit.]
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Summary changed:
- Xorg crashed with SIGABRT in raise()
+ Xorg crashed with SIGABRT in raise() Address 0x7f669c3b1e58 out of bounds
** Description changed:
after every logon, the message appears
+
+ #3 0x7f66a2bf7223 in AbortServer () at ../../os/log.c:655
+ No locals.
+ #4
[Duplicate of bug #982889, which has reached its duplicants limit.]
** Information type changed from Private to Public
** Description changed:
Brand new Lenovo ideapad Y500, live booting 13.04 daily from 02/04/2013.
Used nomodeset to get to shell, then used nvidia-current from
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command in a terminal after
reproducing the issue, and it it will automatically gather debugging
information needed for this bug:
apport-collect 1171061
Can you reproduce this under
Huh, looks like it crashed trying to handle itself crashing. Never
good. But neither the stack traces nor the Xorg.0.log's offer a hint as
to what went wrong.
Are you able to reproduce this issue easily? If so, please collect a
full backtrace - see http://wiki.ubuntu.com/X/Backtracing for
Have you reproduced this issue, or did the crash happen just the once?
** Description changed:
- ...
+ Thread 1 (LWP 1236):
+ #0 0x7fe2dad96cd4 in mieqMoveToNewScreen (screen=0x7fe2db30dbb0,
dev=0x7fe2db52c770, event=optimized out) at ../../mi/mieq.c:490
+ No locals.
+ #1
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ X trying to start before plymouth has finished using the drm driver
** Description changed:
- REbooting after synaptic updates - I think the update failed to fully
- install kernel 3.8.0-13 on previous update.
+ This bug is a dupe
** Description changed:
I don't know what is it, I need simple answer what to do. Screen has
- stopped, only reset was helpfull
+ stopped, only reset was helpful.
+
+ #2 0x7f2554204fde in OsReleaseSIGIO () at ../../os/utils.c:1224
+ #3 0x7f255420a798 in FatalError (f=0x5a4 Address
Are you still able to reproduce this bug?
** Description changed:
No other nvidia-graphics-driver or nouveau-driver is working with my
TECRA-M9 ( NVIDIA Quadro-NVS 130M ).
+
+ #4 0x7facfcc8cbdd in FatalError (f=0x7facf6446e58 Address
0x7facf6446e58 out of bounds) at ../../os/log.c:793
Did it only crash the once, or have you seen additional X crashes since
this one?
** Description changed:
Bug reported on restart after an upgrade of 13.04 on 25 March 2013.
+
+ #10 signal handler called
+ #11 DeleteDeviceEvents (dev=optimized out, client=0xb7f6b9d0,
pWin=0xb7dba5d0) at
*** This bug is a duplicate of bug 1155902 ***
https://bugs.launchpad.net/bugs/1155902
** This bug has been marked a duplicate of bug 1155902
X trying to start before plymouth has finished using the drm driver
--
You received this bug notification because you are a member of Ubuntu-X,
Hmm, I think the backtrace for this bug didn't get auto-collected
properly.
Are you able to reproduce this issue easily? If so, please collect a
full backtrace manually - see http://wiki.ubuntu.com/X/Backtracing for
directions. If not, could you describe the conditions under which the
crash
*** This bug is a duplicate of bug 1155902 ***
https://bugs.launchpad.net/bugs/1155902
** This bug has been marked a duplicate of bug 1155902
X trying to start before plymouth has finished using the drm driver
--
You received this bug notification because you are a member of Ubuntu-X,
** Description changed:
- Nothing more to comment
+ #12 0x7feb3090e29d in xf86CloseConsole ()
+ #13 0x7feb308e8f45 in ddxGiveUp ()
+ #14 0x7feb30897774 in ?? ()
+ #15 0x7feb2e5a0ea5 in __libc_start_main (main=0x7feb30897110, argc=10,
ubp_av=0x7fff037dc318, init=optimized out,
Does this crash still occur with latest raring? If so, please collect a
full backtrace on this crash - see http://wiki.ubuntu.com/X/Backtracing
for guidance.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
** 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-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1077616
Title:
10de:0ca3 (EE) [mi] EQ
*** This bug is a duplicate of bug 1155902 ***
https://bugs.launchpad.net/bugs/1155902
** This bug is no longer a duplicate of private bug 1159292
** This bug has been marked a duplicate of bug 1155902
X trying to start before plymouth has finished using the drm driver
--
You received
The original patch is large due to some code refactoring. Here is a
more minimal patch that just shows the functional changes without the
refactoring.
You can see the patch:
a) Adds a routine to check the scanout size
b) Adds code to cleanup the large_inactive and scanout lists in a couple
** Description changed:
+ [Impact]
With updated 13.04 beta, unplugging an external monitor from laptop results
in corrupted screen. Logging out fixes it.
A screen capture looks normal (not like what the display is showing!).
Plugging an external monitor in does not produce any similar
** Description changed:
I get black screens while working since last updates, not sure if
xserver-xorg-video-intel is involved or something else
by pressing ctrl+alt+f2 I can access the console
+
+ == intel_reg_dumper before/after ==
+
+ --- normal.log2013-04-16
@Fiorenzo, thanks. I've pasted the diff into the description of this
bug.
@Chris, does the intel reg dumper output provide any clues?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = New
** Description changed:
If I plug in and and remove an external monitor it will make the login
manager show up. Also, random crashes happen while using flash for
youtube.
+
+ [ 4611.400871] [ cut
Agreed, this does sound like the recently fixed nautilus bug. Can you
re-test with current raring?
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
The patch listed as a fix for this issue in the upstream bug has been
uploaded for ubuntu raring. Since it sounds like that should fix this
issue I'm closing this bug. If it proves to still be reproducible,
reopen the bug.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix
Public bug reported:
Saw this on a recently reported bug (don't remember which one):
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/apport/report.py, line 197, in
_run_hook
symb['add_info'](report, ui)
File
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Medium = Low
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Medium = Low
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Description changed:
following up from bug 1157614
+
+ #8 signal handler called
+ No locals.
+ #9 0x7fe6dc884b03 in drmmode_from_scrn (scrn=0x7fe6e0fa18f0) at
../../src/drmmode_display.c:109
+ conf = 0x7fe6e11e2260
+ crtc = 0x0
+ #10 drmmode_wakeup_handler
** Description changed:
- ...
+ #12 0x7f431b65cbdd in FatalError (f=f@entry=0x7f431b66fcb8 %s:
VT_ACTIVATE failed: %s\n) at ../../os/log.c:793
+ args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area =
0x7fff1c3a70b0, reg_save_area = 0x7fff1c3a6ff0}}
+ args2 =
Perhaps it merely needs an extra null pointer check?
** Patch added: nullptr_check_drmmode_from_scrn.patch
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1157819/+attachment/3647879/+files/nullptr_check_drmmode_from_scrn.patch
--
You received this bug notification because you
Maarten - since we're at release now, a null pointer check would
probably be simplest to sru. But why would
conf-crtc[0]-driver_private be null here?
** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-nouveau
(Ubuntu)
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Importance:
also note this was filed against 1.0.6, so should check if it got fixed
in 1.0.7. At least crtc is still not being checked for null so
guessing the issue is still relevant.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Description changed:
- Not sure where things went wrong but jsut reporting it just in case.
+ Not sure where things went wrong but jsut reporting it just in case.
+
+ #13 signal handler called
+ No symbol table info available.
+ #14 0xb7758dab in miSlideAndSizeWindow (pWin=0xb86c1190, x=0,
** Summary changed:
- Xorg crashed with SIGABRT in EVERGREENUploadToScreen()
+ Xorg crashed with SIGABRT in EVERGREENUploadToScreen() [exa]
** Summary changed:
- Xorg crashed with SIGABRT in EVERGREENUploadToScreen() [exa]
+ [HD 7310] Xorg crashed with SIGABRT in EVERGREENUploadToScreen() [exa]
#14 0xb7758dab in miSlideAndSizeWindow (pWin=0xb86c1190, x=0, y=0,
w=1024, h=600, pSib=0x0) at ../../mi/miwindow.c:395
Hmm, that's this bit of code:
for (pChild = pWin-firstChild; pChild; pChild = pChild-nextSib) {
g = pChild-winGravity;
if (g != UnmapGravity) {
Have you been able to reproduce this crash, or did it just occur the
once?
The only thing that jumps out to me is that width=1 and height=1; I
wonder if some window was getting resized to be 1x1 and X freaked out or
something? Would be nice to have a CoreDump or some way to reproduce
the crash
** Summary changed:
- Xorg crashed with SIGABRT in xi2mask_isset()
+ [Samsung Series 7 Slate] Xorg crashed with SIGABRT in xi2mask_isset()
** Description changed:
I am running 13.04 on a Samsung Series 7 Slate, which has an Atmel
Digitizer and Wacom tablet input. The touchscreen input
For GPU lockup bugs with Intel graphics, you need to collect the output
of 'dmesg' and your /sys/kernel/debug/dri/0/i915_error_state file. Both
of these must be collected while the machine is locked up (e.g. by
sshing into the sick machine over ethernet). See
** Information type changed from Private to Public
** Description changed:
#11 0xb6f876d1 in read_b (pInt=0xb8df60c8, addr=-19837937) at
../../../../hw/xfree86/int10/generic.c:371
- No locals.
#12 0xb6f86637 in Mem_rb (addr=4275129359) at
../../../../hw/xfree86/int10/helper_exec.c:450
- No
If the breakage you're referring to is the failure to respond to clicks,
that may have been a bug in nautilus that recently got fixed. Try with
latest bits and see if it is no longer reproducible.
Regardless, this crash looks worth further examination, as it may be an
unrelated problem. It is
** Description changed:
Logging in to Gnome Shell on MacBook pro Retina (scaled resolution) with
external monitor (Display port) than the display froze
I'm using nvidia-313-updates
+
+ #8 signal handler called
+ #9 RRSetChanged (pScreen=0x7f513954fb30) at ../../randr/randr.c:486
+
Crashing due to code in autoconfig-fixup-tell-changed-so-randr-clients-
can-t.patch.
Looks like RRSetChanged needs to check for mastersp being null now.
** Patch added: nullptr_rrsetchanged.patch
Guessing you'll want this bug too. Probably an easy fix.
** Changed in: xorg-server (Ubuntu)
Importance: Medium = High
** Changed in: xorg-server (Ubuntu)
Status: New = In Progress
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
--
** Description changed:
When i load pages from internet the system exit from graphical mode for
few seconds and close all applications
#7 OsSigHandler (signo=11, sip=optimized out, unused=optimized out) at
../../os/osinit.c:107
#8 signal handler called
#9 0x in ??
Verified
== Precise-proposed ==
Linux lynmouth.bryceharrington.org 3.2.0-29-generic #46-Ubuntu SMP Fri
Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Before:
lynmouth+12.10:~$ grep apport-gpu-error /lib/udev/rules.d/*
/lib/udev/rules.d/40-xdiagnose.rules:#SUBSYSTEM==drm,
Boot a 12.10 livecd, and collect the /var/log/Xorg.0.log and post here,
so we can compare against a working session.
** Package changed: xorg (Ubuntu) = xserver-xorg-input-synaptics
(Ubuntu)
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Incomplete
--
You received
** Description changed:
When i load pages from internet the system exit from graphical mode for
few seconds and close all applications
+
+ #7 OsSigHandler (signo=11, sip=optimized out, unused=optimized out) at
../../os/osinit.c:107
+ #8 signal handler called
+ #9 0x in ??
** Description changed:
using abiworld and others programs contemporanelythe system go out
after one black terminal screen lubuntu start from login page
+
+ #9 OsSigHandler (signo=11, sip=0xbfb8288c, unused=0xbfb8290c) at
../../os/osinit.c:107
+ #10 signal handler called
+ #11
** Description changed:
Crashed while playing a flash game
+
+ Thread 1 (LWP 1261):
+ #0 0x7ff5c5523460 in _int_free (av=0x7ff5c5864740 main_arena,
p=0x7ff5c967b210, have_lock=0) at malloc.c:3912
+ size = 304
+ fb = optimized out
+ nextchunk = 0x7ff5c967b340
+
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has finished using the drm driver
--
You received this bug notification because you are a member of Ubuntu-X,
which
1 - 100 of 26231 matches
Mail list logo
