Please provide steps to reproduce
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs
First, say it "froze" or "locked up". "crashes" are something different
entirely. :-)
Second, when you get gpu freezes, 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 sshin
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
https://wiki.ubuntu.com/X/Troubleshoo
We've carried this patch for a few years, meantime a number of
improvements have been made to upstream handling of multi-GPU.
We're going to optimistically drop this patch in hopes that whatever
situation led to the crash are long since gone. This bug is kind of a
corner case we don't expect very
** Bug watch added: freedesktop.org Bugzilla #24181
https://bugs.freedesktop.org/show_bug.cgi?id=24181
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=24181
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
There is udev code to detect gpu lockups which will capture
i915_error_state in that case, but the general apport-collect script
doesn't (we haven't needed it up til now, but probably can't hurt to
collect). Since it sounds like that didn't happen here, it suggests
you're experiencing something di
[Hook error filed as bug #1119808]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1119793
Title:
[arrandale] GPU lockup IPEHR: 0x0200
Status in “xserver-xorg-vi
There are also bugs 1116732 and 1112871 with IPEHR: 0x0200, but the
chipset and reproduction steps are different from here, so not obviously
dupes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
ht
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1117563
Title:
X hard lockup in r
Looks like you got apport to pick up the gpu lockup after all: bug
#1119793
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1117563
Title:
X hard lockup in raring, ca
*** 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 Desktop
Packages
** Patch added: "First cut at a patch for this issue"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3525858/+files/drm_check_for_eagain.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ub
Similar patch, for xorg-server.
** Patch added:
"0001-If-drm-device-couldn-t-be-opened-keep-trying-for-a-s.patch"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+attachment/3527196/+files/0001-If-drm-device-couldn-t-be-opened-keep-trying-for-a-s.patch
** Changed in: xorg-server
e (Ubuntu Quantal)
Importance: Undecided => High
** Changed in: xdiagnose (Ubuntu Quantal)
Assignee: (unassigned) => Bryce Harrington (bryce)
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** No longer affects: xserver-xorg-video-intel (Ubuntu Quantal)
** Also affects: xdiagnose
Applied the same change as done in 2.5.1 for precise (see bug #997470).
Leaving a raring task open as a reminder that this needs disabled when
raring releases as well.
** Description changed:
+ [Impact]
+ Apport hook is triggered for GPU lockups in the stable release, in cases
where the system
Thanks for the clarification. The situation you described could well be
associated with the gpu lockup. The way to be certain is to look at
dmesg after experiencing one of these lags:
[ 630.190999] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[ 630.1
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1124699
Title:
[gm45] GPU lockup IPE
Let's give it 2-3 weeks and see if it can still be repro'd with newer
bits. If not, we'll close as expired/unreproducible.
** Description changed:
- No idea what happened.
+ #8
+ #9 _sna_pixmap_move_to_cpu (pixmap=pixmap@entry=0x7fd2ac56a150,
flags=flags@entry=3) at ../../../src/sna/sna_acc
Fixed in revision 351
** Changed in: xdiagnose (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/1119808
Title:
TypeError: unorderable type
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100
+ [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 - no hang or
other symptoms
--
You received this bug notifica
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
>From the core dump:
#4 0x7f105c20880d in FatalError (
f=f@entry=0x7f105c210148 "Cannot run in framebuffer mode. Please specify
busIDsfor all framebuffer devices\n") at ../../os/log.c:793
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1124296
Title:
Xorg crashed with SIGABRT
Status in “xorg-server” package in Ubun
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1123166
Title:
Xorg crashed with SIGABRT in DamageRegister()
Status in “xorg-ser
For some reason apport didn't generate a proper stack trace on this one,
so please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Information type changed from Private to Public
** Changed in: xorg-server (Ubuntu)
Importance: Medium => High
** Description changed:
- crashed on upgraded
+ crashed on upgrade
+
+ #10
+ #11 elf_machine_runtime_setup (profile=0, lazy=1, l=0xb8d18b40) at
../sysdeps/i386/dl-machine.h:113
+ got = 0xb699d000
+ #12 _dl_relocate_object (scope=0xb8d18cf8, reloc_mode=reloc_mode@entry=1,
consider_profi
** Description changed:
LENOVO T500 Raring Ringrail 3.8.0.5-generic
KDE crash while LogIn
+
+ #10
+ No symbol table info available.
+ #11 DamageRegister (pDrawable=0x0, pDamage=0xb90e9520) at
../../../miext/damage/damage.c:1774
+ pScrPriv = 0xb8d7b2e0
+ #12 0xb7651fe1 in xf86Rotate
** Summary changed:
- Xorg crashed with SIGABRT
+ Xorg crashed with SIGABRT in dl_open
** Changed in: xorg-server (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** Description changed:
#4 0x7f4ddcfde3ed in FatalError (f=f@entry=0x7f4ddcfe5d08 "Cannot run in
framebuffer mode. Please specify busIDsfor all framebuffer devices\n")
at ../../os/log.c:793
-
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
** This bug is no longer a duplicate of bug 1065288
Xorg crashed with SIGABRT "Cannot run in framebuffer mode"
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has
ail" - Alpha amd64 (20121120)
MarkForUpload: True
ProcCmdline: compiz
ProcCwd: /home/bryce
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x182a76: Cannot access memory at address 0x182a76
PC (0
13.04 "Raring Ringtail" - Alpha amd64 (20121120)
MarkForUpload: True
ProcCmdline: compiz
ProcCwd: /home/bryce
ProcEnviron:
- PATH=(custom, user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/
Please attach your mplayer config and/or command line arguments you're
using for running it.
Also, can you tell us or share the video? It can help developers to
reproduce the problem.
The i915_error_state file must be collected *while* the system is
frozen, so I'm not sure the i915_error_state y
ssh in while it's frozen.
Playing videos (mp4) full screen through mplayer Works For Me.
Maybe your hardware's bad or something.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.
** Also affects: xorg-server (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Raring)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu Quantal)
Status: New => Triaged
** Changed in: xorg-server (Ubuntu Raring)
** Changed in: ubuntu-nexus7
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1076627
Title:
When in portrait mode, mouse movement glitc
I've also double-checked that after installing jockey 0.9.7-0ubuntu7.7,
fglrx-experimental-9 installs cleanly and boots up to a usable Unity
session. Looks good, I'll close out the jockey task as well.
** No longer affects: fglrx-installer (Ubuntu)
** No longer affects: fglrx-installer (Ubuntu
Actually, I take that back. I see that jockey 0.9.7-0ubuntu7.4 is in
-updates currently, but fglrx-experimental-9 won't install properly with
that version of jockey. It looks like 0.9.7-0ubuntu7.5 or
0.9.7-0ubuntu7.6 are required at a minimum.
--
You received this bug notification because you a
[ 6043.229] (EE)
[ 6043.229] (EE) Backtrace:
[ 6043.229] (EE)
[ 6043.229] (EE) Segmentation fault at address 0x0
[ 6043.230]
Fatal server error:
[ 6043.230] Caught signal 11 (Segmentation fault). Server aborting
[ 6043.230]
[ 6043.230] (EE)
Now there's a backtrace!
--
You received t
The onboard icon works for me. Got anything else?
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1108861
Title:
xorg core
Please explain the steps to reproduce the crash in further detail.
** Description changed:
X-server crashes while using multiple master cursors with xinput (both
gnome3 and unity).
+
+ #7 OsSigHandler (signo=11, sip=, unused=) at
../../os/osinit.c:107
+ No locals.
+ #8
+ No locals.
+ #9
Was this being run under virtualbox?
** Description changed:
- Xorg crashed with SIGABRT in OsAbort()
+ #4 0x7f4ddcfde3ed in FatalError (f=f@entry=0x7f4ddcfe5d08 "Cannot run in
framebuffer mode. Please specify busIDsfor all framebuffer devices\n")
at ../../os/log.c:793
+ ar
** Summary changed:
- Xorg crashed with SIGABRT in memcpy()
+ Xorg crashed with SIGABRT in sna_video_copy_data()
** Description changed:
Xorg crashed with SIGABRT in XvdiPutImage()
+
+ #12 0xb6f43f40 in memcpy (__len=, __src=0xb3e24000,
__dest=) at /usr/include/i386-linux-gnu/bits/string3.h:
** Description changed:
To reproduce:
Use ubuntu desktop
Shut laptop lid (screen turns off)
Shortly afterwards I hear the login noise and when I open the lid I've been
logged out
+ I don't have gnome-screensaver installed as I thought it might be part
+ of the problem.
- I don't
** Description changed:
Fast-user switching results in a black screen, X crash.
+
+ #8
+ No locals.
+ #9 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:272
+ No locals.
+ #10 0x7f402c498737 in memcpy (__len=7680, __src=,
__dest=0x7f402606e000) at /usr/include/x86_64-linux-g
** Description changed:
After upgrade to raring and reboot, I'm seeing frequent Freezes in
normal usage of X. The mouse cursor moves but cannot interact with
windows.
ctrl-alt-f1 will work, and I can login there.
Running 'sudo restart lightdm' from the console ends up with multiple X
** Summary changed:
- [sandybridge-gt1] False GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
+ [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
** Description changed:
- apport showed up for no reason
+ apport showed up because I had a hung system
ProblemType: Crash
Dist
Alright well even if the issue is still happening, we'd need log files
for the 3.8 kernel. I'll close this report out and if it occurs again
hopefully there'll be a new report.
I think IPEHR: 0x0200 may be a generic error code, so it's possible
Brian and Neven are seeing unrelated issues.
*
Please collect a full backtrace on this crash - see
http://wiki.ubuntu.com/X/Backtracing for guidance.
** Summary changed:
- Xorg crashes when playing a video
+ Xorg crashes when playing an mkv video with SNA
** Description changed:
- chrashes when watching video
+ crashes when watching video
+
** Also affects: xdiagnose (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: xdiagnose (Ubuntu Quantal)
Importance: Undecided
Status: New
--
You received this bug
[Unsubscribing ubuntu-sponsors since it appears the posted patches need
further work.]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1065979
Title:
external/internal mo
Are you able to reliably reproduce it by playing that video in totem?
If not, out of 10 tries how many times does it happen?
If you can repro it with that video (or another similar video), please
attach to this bug or provide a pointer to an online source.
Has your system had other similar freeze
(Targeting to ubuntu's xorg package; it's not clear if this is
appropriate to upstream, it could just be an error in my xrotate
script.)
** Project changed: xorg-server => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xor
.
** Summary changed:
- Rotating screen does not rotate touch input
+ Rotating screen using gnome-settings does not rotate touch input
** Bug watch added: GNOME Bug Tracker #624880
https://bugzilla.gnome.org/show_bug.cgi?id=624880
** Changed in: ubuntu-nexus7
Assignee: Bryce Harrington
Any luck so far the last couple weeks?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1065113
Title:
Xorg crashed with SIGABRT in free()
Status in “xorg-server” package in Ubuntu
** Also affects: nvidia-graphics-drivers-experimental-310 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-settings-experimental-310 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: jockey (Ubuntu Oneiric)
Importance: Undecided
Status: Ne
Thanks for following up. At this point let's assume the bug is fixed.
** Changed in: xorg-server (Ubuntu Quantal)
Status: Incomplete => Fix Released
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a memb
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1056039
Title:
X crashes in
I didn't spot anything in the libdrm changelog relevant to this. There's
a few buffer flushing changes in the newer ddx driver, but they appeared
related to corruption issues rather than crashes.
I'd built compiz from source and installed it, but on restart unity
didn't come up. Does compiz need
** Changed in: mesa (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mesa (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1061073
As per discussion with Alberto, this is not a critical bug but rather a
lack of feature support in the nvidia driver.
NVIDIA does not support running on framebuffer drivers, and testing has
proven that doing so leads to system instability in many cases. People
can switch on the drivers manually i
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1084842
Title:
Crash in r600_dri:evergreen_set_global_binding while playing C
I'm not able to reproduce on a 1920x1200 Dell monitor running -ati on
precise on a PC, although not with an HD 6310 (I don't have that card).
If you can suggest other information that would help us reproduce the
bug, I'm willing to try. But since you've ruled out it being a recent
regression, and
** Summary changed:
- [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest
(Cirrus graphics)
+ [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest
(Cirrus graphics). Affects KVM but not VBox.
--
You received this bug notification because you
Yes, it's true -cirrus hasn't changed. It could be a change in
something underneath -cirrus that it depends on.
; in fact we haven't changed much of X in raring from quantal really:
xserver is different but mainly just bug fixes, mesa the same (although
since it affects gnome classic (no effects)
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SI
** Changed in: xserver-xorg-video-cirrus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu.
https://bugs.launchpad.net/bugs/1043513
Title:
Xorg crashed with SI
Had you found that setting up screen parameters had worked properly in
the past, or was this just the first you've tried?
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa
*** This bug is a duplicate of bug 1041063 ***
https://bugs.launchpad.net/bugs/1041063
** This bug has been marked a duplicate of bug 1041063
mouse pointer periodically leaps to left and top of screen with absolute
pointing devices
--
You received this bug notification because you are a
a7x, the patch was uploaded for precise prior to comment #25, because
it had been nominated for precise. Keep in mind that precise includes a
backport of the input stack, so it's not surprising to find input bugs
introduced after 1.11 affecting precise, however that stack is 1.12 so a
1.13-specif
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/137234
Title:
[i945] Second
igh
** Changed in: xorg-server (Ubuntu)
Status: New => In Progress
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubun
igh
** Changed in: xorg-server (Ubuntu)
Status: New => In Progress
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubun
igh
** Changed in: xorg-server (Ubuntu)
Status: New => Fix Committed
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification bec
*** This bug is a duplicate of bug 1094097 ***
https://bugs.launchpad.net/bugs/1094097
** This bug has been marked a duplicate of bug 1094097
Xorg crashed with SIGSEGV in mieqMoveToNewScreen()
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
*** This bug is a duplicate of bug 1094097 ***
https://bugs.launchpad.net/bugs/1094097
** This bug is no longer a duplicate of bug 1039341
Xorg crashed with SIGABRT in mieqMoveToNewScreen()
** This bug has been marked a duplicate of bug 1094097
Xorg crashed with SIGSEGV in mieqMoveToNewS
The crash is occurring in code that handles keyboard and mouse input
when the screen is being woken up.
For those trying to find out how to reproduce the bug, it must be some
combination of keyboard or mouse button input while waking the screen or
vt switching.
--
You received this bug notificat
*** This bug is a duplicate of bug 1059316 ***
https://bugs.launchpad.net/bugs/1059316
** This bug is no longer a duplicate of bug 459637
totem assert failure: totem: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:863:
vm_get_video_aspect: Assertion `aspect == 0 || aspect == 3' failed.
** This
** Description changed:
- Binary package hint: rhythmbox
+ [Impact]
+ In the fr(oss) keymap, both space and Ctrl + space return the same
XLookupString, which prevents space from being used in some applications.
- I tried to search for "The Do" in the search bar, but the space bar
- didn't writ
** Also affects: rhythmbox (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: quodlibet (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: xkeyboard-config (Ubuntu Precise)
Importance: Undecided
Status: New
** No longer affects: rhy
** Description changed:
- Looking at software center page, it seems that neither System Settings
- nor KDE System Settings is installed, while, as you can see from my
- screen shot I have System Settings installed in my system (by default).
- If I install System Settings (NOT KDE System Settings)
** Description changed:
- Select (in 10.04) the System -> Preferences -> Startup Applications...
- menu choice. Then click the Options tab and notice the "Remember
- Currently Running Application" button. The button has a typo, it should
- say "Applications" (plural) because all running applicatio
** Changed in: jockey (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/919484
Title:
Need untranslated output from jockey-text -l
Status in “jo
Public bug reported:
[Impact]
Various commercial games (including several from the Humble Bundle) require
s3tc texture support. However this is not available with Intel graphics due to
patent issues. Users with Intel graphics must manually install
libtxc-dxtn-s2tc0 to make the games work.
Th
** Changed in: mesa (Ubuntu)
Status: New => In Progress
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Desktop
*** This bug is a duplicate of bug 1053065 ***
https://bugs.launchpad.net/bugs/1053065
** This bug has been marked a duplicate of bug 1053065
MIR for s2tc, required by various games
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Also affects: nvidia-graphics-drivers-experimental-304 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-settings-experimental-304 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-experimental-304 (Ubuntu Precise)
Importa
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers
This issue is the origin of these build failures in Quantal:
pycuda - https://launchpad.net/ubuntu/+source/pycuda/2012.1-1/+build/3603969
(needs nvidia-cuda-toolkit)
nvidia-cuda-toolkit -
https://launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/4.2.9-1/+build/3510919
(needs libcua1)
--
You
** Changed in: nvidia-settings-experimental-304 (Ubuntu Quantal)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-experimental-304 (Ubuntu Quantal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Deskto
201 - 300 of 1123 matches
Mail list logo
