Crash changing TTY (paintOutput)

Bug #269120 reported by Niels Egberts
142
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: compiz

I was trying to use the guest account option in Intrepid for the first time. It loaded the guest-account background but gnome would not load. I went back with ctrl-alt-f9 to my dekstop and then this message appeared, I needed to run it with admin rights. Compiz fusion with all the effects kept on working.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.7+git20080807-0ubuntu6
ProcAttrCurrent: /usr/share/gdm/guest-session/Xsession (enforce)
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding core ccp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libGLcore.so.1
 ?? ()
 paintOutput ()
 paintScreen ()
Title: compiz.real crashed with SIGSEGV in paintOutput()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups:

Revision history for this message
Niels Egberts (nielsegberts) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? () from /usr/lib/libGLcore.so.1
paintOutputRegion (screen=0x19247d0, transform=0x7fffe51cff40, region=0x1a218b0,
paintOutput (screen=0x19247d0, sAttrib=<value optimized out>,
paintScreen (s=0x19247d0, outputs=<value optimized out>, numOutput=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in compiz:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Hew (hew) wrote : Re: compiz.real crashed with SIGSEGV in paintOutput()

This problem is reproducible by using compiz and attempting to switch to a guest session. The welcome music and wallpaper appear, but the gnome-panels do not. The command line can be accessed with Alt-F2. Ctrl-Alt-Bksp kills the guest session and returns back to the original (locked) session.

I have tried to obtain a backtrace, but as soon as I attach gdb to compiz.real, my whole system freezes (except the mouse cursor). Even Alt-Sysrq-K doesn't work. Any ideas on how I can obtain a backtrace are appreciated.

Changed in compiz:
status: Incomplete → Confirmed
Revision history for this message
Adam Petaccia (mighmos) wrote :

I also have this issue, 100% reproducable.

Revision history for this message
Alexander Jones (alex-weej) wrote : Re: [Bug 269120] Re: compiz.real crashed with SIGSEGV in paintOutput()

Hew, attach it to GDB from another terminal, like from a TTY VT
(Ctrl+Alt+F1..6). Once you have attached, the program is interrupted,
which means it can't paint or send any events to anything. You just
need to enter "c" (continue) in GDB to resume it. From there, you can
get debugging once it crashes.

If you do it in "Screen", you can restart Compiz/Metacity and carry on
working in an X terminal.

Revision history for this message
Hew (hew) wrote : Re: compiz.real crashed with SIGSEGV in paintOutput()

Thanks for your help. I used Ctrl+Alt+F1 to run gdb, found the pid of compiz.real and attached it, and typed continue. I switched back to Ctrl+Alt+F7 and attempted to reproduce the problem.

With the upload of the new intrepid theme, it looks like the freezing part of the problem has been solved. The gnome-panels load and the session runs just fine. I switched back to gdb and it still hadn't caught anything. I switched to X and logged in as myself (with compiz) and apport was in the notification area telling me about the compiz.real crash. I checked the pid and it was still running.

What's going on? Am I attaching gdb to the right thing?

Revision history for this message
Lambros Lambrou (lambros) wrote :

I have this exact same bug in Intrepid and it's reproducible every time. In my case, I don't use Compiz (Desktop Effects) on my regular account, because it interferes with 3D gaming. But I have the proprietary nVidia driver installed, so I assume that, when I start up the Guest session, it defaults to switching on Desktop Effects and therefore starts compiz.

From the Alt-F2 screen, I can run gnome-terminal. Doing "killall gnome-panel" gives me the panels back. And "killall nautilus" restores the ability to get a right-click menu on the desktop.

Revision history for this message
gali98 (korylp) wrote :

Same exact thing as above. When I started the guest session, it got stuck at showing the desktop background (no toolbars came up) so I pressed ctrl+alt+backspace to restart X. When I logged back into my other session, it showed the bug.
Kory

Revision history for this message
electhor (electhor) wrote :

I ditto the above, however my monitor was completely black, no background at all.

summary: - compiz.real crashed with SIGSEGV in paintOutput()
+ Crash changing TTY (paintOutput)
Revision history for this message
Travis Watkins (amaranth) wrote :

Moving to nvidia driver since everyone having this problem is using nvidia and the crash occurs inside nvidia's libGL.

affects: compiz (Ubuntu) → linux-restricted-modules-2.6.24 (Ubuntu)
Revision history for this message
KJ (kunjin-md) wrote : Re: [Bug 269120] Re: Crash changing TTY (paintOutput)

Thanks. I am very new to this group. What does that mean? Is the problem fixed? How can now do to my machine?

Best,

Kun

--- On Tue, 9/15/09, Travis Watkins <email address hidden> wrote:

> From: Travis Watkins <email address hidden>
> Subject: [Bug 269120] Re: Crash changing TTY (paintOutput)
> To: <email address hidden>
> Date: Tuesday, September 15, 2009, 3:03 PM
> Moving to nvidia driver since
> everyone having this problem is using
> nvidia and the crash occurs inside nvidia's libGL.
>
> ** Package changed: compiz (Ubuntu) =>
> linux-restricted-modules-2.6.24
> (Ubuntu)
>
> --
> Crash changing TTY (paintOutput)
> https://bugs.launchpad.net/bugs/269120
> You received this bug notification because you are a direct
> subscriber
> of a duplicate bug.
>
> Status in “linux-restricted-modules-2.6.24” package in
> Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: compiz
>
> I was trying to use the guest account option in Intrepid
> for the first time. It loaded the guest-account background
> but gnome would not load. I went back with ctrl-alt-f9 to my
> dekstop and then this message appeared, I needed to run it
> with admin rights. Compiz fusion with all the effects kept
> on working.
>
> ProblemType: Crash
> Architecture: amd64
> Disassembly: 0x0:
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/bin/compiz.real
> NonfreeKernelModules: nvidia
> Package: compiz-core 1:0.7.7+git20080807-0ubuntu6
> ProcAttrCurrent: /usr/share/gdm/guest-session/Xsession
> (enforce)
> ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints
> --replace --loose-binding core ccp
> ProcEnviron:
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=nl_NL.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: compiz
> StacktraceTop:
> ?? ()
> ?? () from /usr/lib/libGLcore.so.1
> ?? ()
> paintOutput ()
> paintScreen ()
> Title: compiz.real crashed with SIGSEGV in paintOutput()
> Uname: Linux 2.6.27-2-generic x86_64
> UserGroups:
>

Bryce Harrington (bryce)
tags: added: intrepid
Revision history for this message
Bryce Harrington (bryce) wrote : linux-restricted-modules-2.6.24 is obsolete

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.

Changed in linux-restricted-modules-2.6.24 (Ubuntu):
status: Confirmed → Won't Fix
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.