Bug 533352 – crash in Panel: just browsing the pdf fi...

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 533352 - crash in Panel: just browsing the pdf fi...


Summary:	crash in Panel: just browsing the pdf fi...


Status:	RESOLVED DUPLICATE of bug 378854

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.20.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-05-15 23:57 UTC by tomaszross
Modified:	2008-05-16 06:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description tomaszross 2008-05-15 23:57:37 UTC

Version: 2.20.3

What were you doing when the application crashed?
just browsing the pdf file


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Tue Feb 12 09:22:35 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 364957696 vsize: 364957696 resident: 13672448 share: 4902912 rss: 13672448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210566203 rtime: 2706 utime: 1950 stime: 756 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(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 0x2b9039d9c220 (LWP 3594)]
[New Thread 0x40040950 (LWP 12939)]
(no debugging symbols found)
0x00002b9033fa434f in waitpid () from /lib/libpthread.so.0

+ Trace 197826

Thread 1 (Thread 0x2b9039d9c220 (LWP 3594))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 g_slist_remove
from /usr/lib/libglib-2.0.so.0
#6 ??
from /usr/lib/gnome-panel/libclock-applet.so
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 ??
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libedataserver-1.2.so.9
#16 ??
from /usr/lib/libORBit-2.so.0
#17 ??
from /usr/lib/libORBit-2.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 ??
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Philip Withnall 2008-05-16 06:00:56 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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