pipes assert failure: pipes: ../../radeon/radeon_cs_gem.c:129: cs_gem_write_reloc: Assertion `boi->space_accounted' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xscreensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xscreensaver
On Ubuntu 10.04, with lubuntu-desktop installed.
I unlogged my GNOME session, then connected on my lubuntu session. I went into Preferences-
1) if I choose not to exit GNOME screensaver deamon, my Xscreensaver don't start
2) if I choose to exit GNOME screensaver deamon, the "pipes" screensaver freezes after about ~8seconds, showing 2 error lines at the top of the frozen pipe image, and then the screen becomes black. (and then if I move my mouse, the black screen disappears, showing my desktop and the Apport window.. see attached data).
I can repeat every time I use the "pipe" screensaver. I could not reproduce with another screensaver.
May be duplicate of Bug #602267
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xscreensaver-
ProcVersionSign
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
AssertionMessage: pipes: ../../radeon/
CheckboxSubmission: 7bf4676ac92338d
CheckboxSystem: bd9978d0ff03d4f
CrashCounter: 1
Date: Fri Jul 9 17:51:15 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100328)
ProcCmdline: pipes -root
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.utf8
SHELL=/bin/bash
Signal: 6
SourcePackage: xscreensaver
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
__assert_fail () from /lib/tls/
?? () from /lib/libdrm_
Title: pipes assert failure: pipes: ../../radeon/
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src
XsessionErrors:
(polkit-
(polkit-
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #602267, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.