Bug 353530 – crash in Bug Report Tool: Starting a freshly built...

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 353530 - crash in Bug Report Tool: Starting a freshly built...


Summary:	crash in Bug Report Tool: Starting a freshly built...


Status:	RESOLVED DUPLICATE of bug 352718

Product:	bug-buddy
Classification:	Deprecated
Component:	general
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Bug-buddy Maintainers
QA Contact:	Bug-buddy Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-30 11:21 UTC by Rafaël Carré
Modified:	2006-08-30 19:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Rafaël Carré 2006-08-30 11:21:40 UTC

Version: 2.15.92

What were you doing when the application crashed?
Starting a freshly built garnome 2.15.92 session under Archlinux


Distribution: Unknown
Gnome Release: 2.15.92 2006-08-29 (GARNOME)
BugBuddy Version: 2.15.92

Memory status: size: 29798400 vsize: 0 resident: 29798400 share: 0 rss: 15933440 rss_rlim: 0
CPU usage: start_time: 1156936750 rtime: 0 utime: 110 stime: 0 cutime:103 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/fun/garnome/bin/bug-buddy'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230067072 (LWP 20841)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71250

Thread 1 (Thread -1230067072 (LWP 20841))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
from /home/fun/garnome/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /home/fun/garnome/lib/libglib-2.0.so.0
#8 g_log
from /home/fun/garnome/lib/libglib-2.0.so.0
#9 g_return_if_fail_warning
from /home/fun/garnome/lib/libglib-2.0.so.0
#10 gdk_window_invalidate_rect
from /home/fun/garnome/lib/libgdk-x11-2.0.so.0
#11 text_window_invalidate_rect
from /home/fun/garnome/lib/libgtk-x11-2.0.so.0
#12 blink_cb
from /home/fun/garnome/lib/libgtk-x11-2.0.so.0
#13 g_timeout_dispatch
from /home/fun/garnome/lib/libglib-2.0.so.0
#14 g_main_context_dispatch
from /home/fun/garnome/lib/libglib-2.0.so.0
#15 g_main_context_iterate
from /home/fun/garnome/lib/libglib-2.0.so.0
#16 g_main_loop_run
from /home/fun/garnome/lib/libglib-2.0.so.0
#17 gtk_main
from /home/fun/garnome/lib/libgtk-x11-2.0.so.0
#18 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-08-30 18:54:49 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.


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

Comment 2 Karsten Bräckelmann 2006-08-30 19:01:36 UTC

/me puts on his GARNOME maintainer hat

Also, thanks for using GARNOME. :)