gnome-screenshot crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()

Bug #804924 reported by Muelli on 2011-07-02
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
Medium
Unassigned

Bug Description

It was consuming memory like mad

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-screenshot 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic x86_64
Architecture: amd64
Date: Sat Jul 2 22:14:12 2011
ExecutablePath: /usr/bin/gnome-screenshot
ProcCmdline: gnome-screenshot --window
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:140
 pa_threaded_mainloop_wait () from /usr/lib/libpulse.so.0
 pulse_driver_play () from /usr/lib/libcanberra-0.28/libcanberra-pulse.so
 ca_context_play_full () from /usr/lib/libcanberra.so.0
 _start ()
Title: gnome-screenshot crashed with SIGSEGV in pthread_cond_wait@@GLIBC_2.3.2()
UpgradeStatus: Upgraded to oneiric on 2011-07-02 (0 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin netdev plugdev powerdev scanner tty video

StacktraceTop:
 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:140
 pa_threaded_mainloop_wait () from /usr/lib/libpulse.so.0
 pulse_driver_play (c=0x18682e0, id=4294967295, proplist=0x1864c20, cb=<value optimized out>, userdata=<value optimized out>) at pulse.c:1082
 ca_context_play_full (c=0x18682e0, id=0, p=0x1864c20, cb=0, userdata=0x0) at common.c:522
 play_sound_effect (user_data=0x183c9c0) at gnome-screenshot.c:800

Changed in gnome-utils (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-utils (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers