Bug 355646 – crash in Bug Buddy: He intentado acceder a l...

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 355646 - crash in Bug Buddy: He intentado acceder a l...


Summary:	crash in Bug Buddy: He intentado acceder a l...


Status:	RESOLVED DUPLICATE of bug 353348

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:

Duplicates:	355647 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-12 19:54 UTC by sergi.alvarezguillem
Modified:	2006-09-12 20:07 UTC

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

Description sergi.alvarezguillem 2006-09-12 19:54:36 UTC

Version: 2.15.92

What were you doing when the application crashed?
He intentado acceder a la ventana en la que se muestran los accesos directos a las demas aplicaciones


Distribution: openSUSE 10.2 (X86-64) Alpha4
Gnome Release: 2.15.92 2006-09-04 (SUSE)
BugBuddy Version: 2.15.92

Memory status: size: 258490368 vsize: 258490368 resident: 5193728 share: 15208448 rss: 20402176 rss_rlim: -1
CPU usage: start_time: 1158090823 rtime: 67 utime: 61 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/bug-buddy'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46992523941376 (LWP 5853)]
(no debugging symbols found)
0x00002abd440aaf85 in waitpid () from /lib64/libpthread.so.0

+ Trace 72213

Thread 1 (Thread 46992523941376 (LWP 5853))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /opt/gnome/lib64/libglib-2.0.so.0
#6 g_log
from /opt/gnome/lib64/libglib-2.0.so.0
#7 gdk_window_invalidate_rect
from /opt/gnome/lib64/libgdk-x11-2.0.so.0
#8 gtk_text_view_buffer_to_window_coords
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#9 gtk_text_view_buffer_to_window_coords
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#10 g_source_get_current_time
from /opt/gnome/lib64/libglib-2.0.so.0
#11 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#12 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#13 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#14 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#15 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-09-12 20:01:27 UTC

*** Bug 355647 has been marked as a duplicate of this bug. ***

Comment 2 Karsten Bräckelmann 2006-09-12 20:07:29 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.


Looks like another duplicate of bug 353348 (see bug 353491).

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