After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 352656 - crash in Bug Report Tool: Another application (I t...
crash in Bug Report Tool: Another application (I t...
Status: RESOLVED DUPLICATE of bug 353348
Product: bug-buddy
Classification: Deprecated
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-24 10:10 UTC by Simon Geard
Modified: 2006-08-29 08:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Simon Geard 2006-08-24 10:10:22 UTC
Version: 2.15.92

What were you doing when the application crashed?
Another application (I think NetworkManager's nm-applet) crashed. A bug-buddy window appeared on the screen, then that too crashed producing a second one which seems to work.


Distribution: Unknown
Gnome Release: 2.15.92 2006-08-22 (GNOME.Org)
BugBuddy Version: 2.15.92

Memory status: size: 29093888 vsize: 0 resident: 29093888 share: 0 rss: 14630912 rss_rlim: 0
CPU usage: start_time: 1156407349 rtime: 0 utime: 96 stime: 0 cutime:89 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/bug-buddy'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229850016 (LWP 15269)]
0xffffe410 in ?? ()

Thread 1 (Thread -1229850016 (LWP 15269))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #5 libgnomeui_segv_handle
    at gnome-ui-init.c line 867

Comment 1 Sergej Kotliar 2006-08-29 08:55:31 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

The other bug is newer, but it had a slightly better stack trace, so I'm closing this a duplicate instead!

*** This bug has been marked as a duplicate of 353348 ***