Ubuntu
gnome-cups-manager package

[apport] gnome-cups-manager crashed with SIGSEGV

Bug #83060 reported by JPSanchez on 2007-02-03

This bug report is a duplicate of: Bug #91218: MASTER: [apport] gnome-cups-manager crashed with SIGSEGV in g_signal_emit_valist(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	gnome-cups-manager (Ubuntu)	Incomplete	Medium	Ubuntu Printing Team

Bug Description

Binary package hint: gnome-cups-manager

Ubuntu 7.04 Hurd 3
After installing an HP deskjet 3920 printer, I clicked on the New Printer, and the program crashed.

ProblemType: Crash
Date: Sat Feb 3 09:22:22 2007
Disassembly: 0x2aca28568b75:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-cups-manager
Package: gnome-cups-manager 0.31-3ubuntu1
ProcCmdline: gnome-cups-manager
ProcCwd: /home/jp
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-cups-manager
Stacktrace:
Using host libthread_db library "/lib/libthread_db.so.1".
#0 0x00002aca28568b75 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux jp-desktop 2.6.20-6-generic #2 SMP Wed Jan 31 19:04:30 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message

JPSanchez (pediatracancun) wrote on 2007-02-03:

Dependencies.txt Edit (4.3 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (40.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (697 bytes, text/plain; charset="utf-8")
Registers.txt Edit (952 bytes, text/plain; charset="utf-8")

Revision history for this message

Daniel Holbach (dholbach) wrote on 2007-03-23:

Thanks for your bug report.

Changed in gnome-cups-manager:
assignee:	nobody → ubuntu-printing
importance:	Undecided → Medium

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-03-25:

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.