[apport] gimmie_applet crashed with SIGSEGV

Bug #103158 reported by eppy 1
2
Affects Status Importance Assigned to Milestone
gimmie (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gimmie

I wasn't doing anything when it crashed that I was aware of, but apport asked me to post this so I guess I will. I hope it helps. I'm using Feisty Fawn.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Apr 4 23:40:23 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/gimmie/gimmie_applet
InterpreterPath: /usr/bin/python2.5
Package: gimmie 0.2.4.repack-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/lib/gimmie/gimmie_applet --oaf-activate-iid=OAFIID:GNOME_Gimmie_Factory --oaf-ior-fd=33
ProcCwd: /home/chris
ProcEnviron:
 LANG=en_CA.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: gimmie
StacktraceTop:
 ?? () from /usr/lib/libgnomecups-1.0.so.1
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux promax 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
eppy 1 (choppy121212) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. Looks like a crash in libgnomecups.

Changed in gimmie:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libgnomecups-1.0.so.1
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

gimmie 0.2.7 has just been published in feisty-backports, do you still have this issue ?

Changed in gimmie:
status: New → Incomplete
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gimmie:
status: Incomplete → Invalid
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.