Frequent hang and render glitches in Xorg, caused by SNA

Bug #1282867 reported by Rohan Dhruva
126
This bug affects 26 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
High
linux (Ubuntu)
Fix Released
High
Unassigned
mesa (Ubuntu)
Fix Released
High
Unassigned

Bug Description

After the latest kernel upgrade, my system has many graphical glitches, and is locking up frequently. The dmesg output has errors like these:

[ 1951.568672] Watchdog[2753]: segfault at 0 ip 00007fe00773a32e sp 00007fdff869f680 error 6 in chrome[7fe003cbe000+5dd9000]
[ 1959.241676] [drm] stuck on render ring
[ 1959.241685] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1959.241686] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1959.241687] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1959.241688] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1959.241689] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1959.244266] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3dc32000 ctx 17) at 0x3dc32c48
[ 3964.330034] perf samples too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 4849.028446] [drm] stuck on render ring
[ 4849.028492] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x565c2000 ctx 17) at 0x565c2c48
[ 4861.093551] Watchdog[5226]: segfault at 0 ip 00007fc00d36f32e sp 00007fbffe2d4680 error 6 in chrome[7fc0098f3000+5dd9000]
[ 4863.020198] [drm] stuck on render ring
[ 4863.020255] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3dc32000 ctx 17) at 0x3dc32c48
[ 4893.028245] [drm] stuck on render ring
[ 4893.028295] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x4cbed000 ctx 10) at 0x4cbedc98
[ 4899.041855] [drm] stuck on render ring
[ 4899.041900] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xea3d000 ctx 10) at 0xea3dc98
[ 4899.041903] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
[ 5833.173837] warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use)
[ 5833.326542] device vboxnet0 entered promiscuous mode
[ 6429.476175] [drm] stuck on render ring
[ 6488.455986] [drm] stuck on render ring
[ 6547.507818] [drm] stuck on render ring
[ 6615.490047] [drm] stuck on render ring

I am not sure if the xserver-xorg-video-intel ricver was also updated at the same time. This is the version in use:

rdhruva@ubuntu:~$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.910-0ubuntu1
  Candidate: 2:2.99.910-0ubuntu1
  Version table:
 *** 2:2.99.910-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-11-generic 3.13.0-11.31
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rdhruva 2154 F.... pulseaudio
 /dev/snd/pcmC0D0p: rdhruva 2154 F...m pulseaudio
CurrentDesktop: KDE
Date: Thu Feb 20 19:29:20 2014
HibernationDevice: RESUME=UUID=33c83ff3-ead7-4122-a1f0-9602e848cb80
InstallationDate: Installed on 2014-01-24 (27 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1)
MachineType: LENOVO 2356EF2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-11-generic root=UUID=9a425350-3b9f-45f7-9587-97f5e539c7e6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-11-generic N/A
 linux-backports-modules-3.13.0-11-generic N/A
 linux-firmware 1.125
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ET98WW (2.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2356EF2
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: 2045260
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG7ET98WW(2.58):bd12/16/2013:svnLENOVO:pn2356EF2:pvrThinkPadT430s:rvnLENOVO:rn2356EF2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2356EF2
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

Revision history for this message
Rohan Dhruva (rohandhruva) wrote :
Revision history for this message
Rohan Dhruva (rohandhruva) wrote :

Attaching /sys/class/drm/card0/error as directed in the dmesg. Could this be caused by a recent switch to SNA?

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

After the latest kernel upgrade, my system has many graphical glitches, and is locking up frequently. The dmesg output has errors like these:

[ 1951.568672] Watchdog[2753]: segfault at 0 ip 00007fe00773a32e sp 00007fdff869f680 error 6 in chrome[7fe003cbe000+5dd9000]
[ 1959.241676] [drm] stuck on render ring
[ 1959.241685] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1959.241686] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1959.241687] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1959.241688] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1959.241689] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1959.244266] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3dc32000 ctx 17) at 0x3dc32c48
[ 3964.330034] perf samples too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 4849.028446] [drm] stuck on render ring
[ 4849.028492] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x565c2000 ctx 17) at 0x565c2c48
[ 4861.093551] Watchdog[5226]: segfault at 0 ip 00007fc00d36f32e sp 00007fbffe2d4680 error 6 in chrome[7fc0098f3000+5dd9000]
[ 4863.020198] [drm] stuck on render ring
[ 4863.020255] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3dc32000 ctx 17) at 0x3dc32c48
[ 4893.028245] [drm] stuck on render ring
[ 4893.028295] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x4cbed000 ctx 10) at 0x4cbedc98
[ 4899.041855] [drm] stuck on render ring
[ 4899.041900] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xea3d000 ctx 10) at 0xea3dc98
[ 4899.041903] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!
[ 5833.173837] warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use)
[ 5833.326542] device vboxnet0 entered promiscuous mode
[ 6429.476175] [drm] stuck on render ring
[ 6488.455986] [drm] stuck on render ring
[ 6547.507818] [drm] stuck on render ring
[ 6615.490047] [drm] stuck on render ring

I am not sure if the xserver-xorg-video-intel ricver was also updated at the same time. This is the version in use:

rdhruva@ubuntu:~$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.910-0ubuntu1
  Candidate: 2:2.99.910-0ubuntu1
  Version table:
 *** 2:2.99.910-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

The corresponding ubuntu bug is: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282867. That bug has a lot of information, including dmidecode output.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Created attachment 94469
File /sys/class/drm/card0/error

Attaching as directed by dmesg.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Created attachment 94470
Complete dmesg

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

The versions might be incorrect, I am not sure about that.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Created attachment 94471
Latest Xorg log

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
In , Chris Wilson (ickle) wrote :

Any clue as to what OpenGL applications are running at the time of the hangs? Also what version of mesa is installed (i.e. the output of glxinfo)?

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

I don't remember the exact list of applications, but I use KDE 4.12.2. I also have Chrome and Hexchat open. No games, video playback, or other graphic intensive applications were running.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Created attachment 94481
Output of glxinfo

Changed in linux:
importance: Unknown → High
status: Unknown → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

I have switched to UXA for now, and that seems to have solved all the problems: I don't see any display glitches, and no lock-ups. The "stuck on render ring" messages are also gone.

Let me know if I can provide any more debugging information.

Revision history for this message
Rohan Dhruva (rohandhruva) wrote : Re: Many bugs in rendering with lockups, likely caused by SNA

I have switched to UXA for now, and that seems to have solved all the problems: I don't see any display glitches, and no lock-ups. The "stuck on render ring" messages are also gone.

Let me know if I can provide any more debugging information.

Revision history for this message
In , Oe-frepdesktoh-n8 (oe-frepdesktoh-n8) wrote :

I've been seeing the same glitches, starting when the updated mesa packages were pushed out on 2/20: http://ubuntuforums.org/showthread.php?t=2206883

At exactly the same time the glitches appeared, the primus bridge quit working for Bumblebee: https://github.com/amonakov/primus/issues/133

Backleveling mesa to the packages in the saucy repository causes the graphical glitches to disappear and everything looks normal again.

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote : Re: Many bugs in rendering with lockups, likely caused by SNA

Another i915 user running KDE here: I started experiencing the exact problems after the package pushes on 2/20.

The screen corruption doesn't always start immediately, but when it does it's horrible: http://i.imgur.com/W2N2y6e.png

Hangups/crashes are frequent (multiple times a day).

I backleveled the mesa (to saucy packages) and xserver-xorg-video-intel (to xserver-xorg-video-intel_2.99.910+git20140210) , and the corruption/crashes went away.

The current packages also break Primus (the render window is solid black). Backleveling the mesa/intel packages fixes this issue as well.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

Can you try to bisect through the mesa git history to find this regression?

Changed in linux:
status: Confirmed → Incomplete
Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Are there any instructions on how to do this for Ubuntu?

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

First hit on google for kernel besicting ;-)

https://wiki.ubuntu.com/Kernel/KernelBisection

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Sorry, I was not aware that this is a kernel thing. I thought this bisection was required in the mesa source package.

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

It's a mesa thing, it's me being confused since the bugzilla update somehow ended up in my kernel bugs folder.

For bisecting mesa you can simply build from sources without any need to install anything. You only need to set LIBGL_DRIVERS_PATH to the i965_dri.so binary built by mesa, e.g.

LIBGL_DRIVERS_PATH=~/home/mesa/src/mesa/drivers/dri/i965/.libs/ glxinfo

Mesa built from git has the git version tag in the Gl version string embedded, so you can check you run the right thing.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Following the instructions to build mesa, I think I was able to get it running successfully:

rdhruva@ubuntu:~/build/mesa$ LIBGL_DRIVERS_PATH=./lib LD_PRELOAD=./lib/libGL.so.1 glxinfo | grep -i version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.0-devel (git-079bff5)
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 10.2.0-devel (git-079bff5)
OpenGL shading language version string: 1.30

Now when I try "glxgears", everything is fine. I am unable to determine if this because the latest git checkout fixed the problem, or if the problem is not surfacing because I am running X in the UXA acceleration mode (instead of SNA).

Looking at the logs, can you suggest a good way to reproduce this problem? Thanks!

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

You need to check out the same version of mesa you have currently installed, to make sure you can reproduce the issue correctly when building from sources. Then the same for the last known working version.

Only once that's confirmed should you start the bisect.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

I updated to the latest packages in Ubuntu, and this bug still exists.

Daniel, are you sure this is a problem in i965? dmesg seems to indicate i915:

[ 70.826529] [drm] stuck on render ring
[ 70.826536] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 70.826538] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 70.826538] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 70.826539] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 70.826540] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 70.829103] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x4ddb4000 ctx 2) at 0x4ddb4d50
[ 76.828152] [drm] stuck on render ring
[ 76.828189] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x9162000 ctx 2) at 0x9162c64
[ 76.828191] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned!

Revision history for this message
In , Chris Wilson (ickle) wrote :

The kernel is just the messenger here reporting that someone hung the GPU. The details about who and how are all in the error state.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

@Chris: Does that mean a bisect is not required? Is the attached error information enough to debug the issue?

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Hello: what can I provide to remove the NEEDINFO status? I am confused whether the git bisect is still required: Chris' message seems to imply that the problem might be completely visible in the attached error file.

If a bisect is indeed required, I am not sure if it's for i965 or i915 (the dmesg errors reference i915).

Revision history for this message
Rohan Dhruva (rohandhruva) wrote : Re: Many bugs in rendering with lockups, likely caused by SNA

This is still happening to me with all the updates applied. Can I provide any more information to help debug this issue?

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

This is still happening to me with all the updates applied. Can I provide any more information to help debug this issue?

Revision history for this message
In , Daniel-ffwll (daniel-ffwll) wrote :

Chris comment was just about your statement in comment #17 that this is i915 related: The kernel driver is called i915, but the mesa driver for your hw is i965. And like Chris said the kernel is just the messenger.

In short, the bisect of mesa is still required, nothing changed.

Revision history for this message
Arthur Schiwon (blizzz) wrote : Re: Many bugs in rendering with lockups, likely caused by SNA

Same happens for me on Kubuntu 13.10, last time with Firefox being on Github. It always happens with Firefox.

Revision history for this message
Rohan Dhruva (rohandhruva) wrote :

Note that this still happens on trusty with all updates installed as of few minutes back.

summary: - Many bugs in rendering with lockups, likely caused by SNA
+ Frequent hang and render glitches in Xorg, caused by SNA
Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

Daniel: I updated my git repo and checked out version 10.1 (which is what my install currently hast). I am still unable to repro the problem from git checkout because the moment I start X with "AccelMethod uxa", the problem goes away.

Is there any better of testing this one library against an X which is not started with UXA? Starting X with SNA and testing this is not really an option because everything is unusable then.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Rohan Dhruva (rohandhruva) wrote :

The latest ubuntu mesa update fixes all issues for me.

Revision history for this message
In , Rohan Dhruva (rohandhruva) wrote :

The latest "mesa" updates in Ubuntu fixed all the problems for me. The relevant patch I see is http://permalink.gmane.org/gmane.linux.debian.devel.x/115099, but I am not sure.

Revision history for this message
In , Kenxeth (kenxeth) wrote :

Closing as fixed per comment #24.

Revision history for this message
Horrendus (stefan-derkits-net) wrote :

All my issues (black boxes in Firefox & Thunderbird, white artifacts when moving windows in KDE, desktop becoming unresponsible for some time and then KDE desktop effects restart) are gone with the latest update.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Byoungchan Lee (bclee) wrote :

Sorry for re-opening this bug, but I think it is not fixed yet. (or Ubuntu`s xserver-xorg-video-intel is latest in upsream. I heared that 2.99.912 is released in June 10th.)

Maybe this will help for debuging. (I got gliches 3~4 times per day.)

Do I need to test lastest one by using xorg-edgers ppa ?

leebc@leebc-laptop:~$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.910-0ubuntu1
  Candidate: 2:2.99.910-0ubuntu1
  Version table:
 *** 2:2.99.910-0ubuntu1 0
        500 http://ftp.jaist.ac.jp/pub/Linux/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

leebc@leebc-laptop:~$ tail /var/log/syslog
Jun 18 18:02:18 leebc-laptop kernel: [ 6382.035567] [drm] stuck on render ring
Jun 18 18:02:18 leebc-laptop kernel: [ 6382.035571] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun 18 18:02:18 leebc-laptop kernel: [ 6382.035573] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun 18 18:02:18 leebc-laptop kernel: [ 6382.035574] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun 18 18:02:18 leebc-laptop kernel: [ 6382.035575] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun 18 18:02:18 leebc-laptop kernel: [ 6382.035576] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

Revision history for this message
Chris Wilson (ickle) wrote :

Except that isn't a bug in the ddx, but mesa.

Revision history for this message
Mark Edgington (edgimar) wrote :

I am experiencing the same problem on a Dell Inspiron 6400 with an Intel GM945 display controller. Symptoms occur frequently when using chromium-browser. Forcing AccelMethod to "UXA" resolved the symptoms. I'm using Ubuntu 14.04, kernel 3.13.0-32-generic, and xserver-xorg-video-intel version 2:2.99.910-0ubuntu1.

Revision history for this message
Alex Crazy (k0l0b0k) wrote :

Hey guys, is there any chance to fix this crap in up to date 14.04? My system hangs suddenly every day...

Revision history for this message
Byoungchan Lee (bclee) wrote :

I have reported this to the freedesktop.org, and it seems that Chris Wilson, one of the moderator of the open-source Intel graphic driver, is been watching my bug report.

Here : https://bugs.freedesktop.org/show_bug.cgi?id=80229

Changed in mesa (Ubuntu):
importance: Undecided → High
Revision history for this message
schoofseggl (schoofseggl) wrote :

I face the same issue on a fresh installed ubuntu 14.10 with a celeron haswell processor, especially when browsing with firefox it sometimes happens.

[ 1045.621449] [drm] stuck on render ring
[ 1045.623026] [drm] GPU HANG: ecode 0:0x87d3bffa, in Xorg [1123], reason: Ring hung, action: reset
[ 1045.623035] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1045.623037] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1045.623039] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1045.623041] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1045.623044] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1047.623048] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 1952.317206] [drm] stuck on render ring
[ 1952.318754] [drm] GPU HANG: ecode 0:0x87d3bffa, in Xorg [1123], reason: Ring hung, action: reset
[ 1954.318777] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 3392.453403] [drm] stuck on render ring
[ 3392.454925] [drm] GPU HANG: ecode 0:0x87d3bffa, in Xorg [1123], reason: Ring hung, action: reset
[ 3394.455101] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

Linux version 3.16.0-28-generic (buildd@komainu) (gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) ) #38-Ubuntu SMP Fri Dec 12 17:37:40 UTC 2014

Revision history for this message
Ronan SALMON (ronan-salmon) wrote :

for what it worth,

I was having the same issues using kernel 3.18.2-031802-generic (amd64) from http://kernel.ubuntu.com/~kernel-ppa/mainline/

I've updated to kernel 3.19.8-031908-generic (amd64) and I no longer get "ERROR* gpu hanging too fast, banning" or [drm] GPU HANG...

Ronan

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

looks like the original bug reporter doesn't have this bug anymore, as the upstream bug is closed, and the kernel is also a newer one in wily

if you still see hangs in wily, file a new bug.

Changed in mesa (Ubuntu):
status: Confirmed → Fix Released
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.