Bug 539367 – crash in Panel: i closed the application

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 539367 - crash in Panel: i closed the application


Summary:	crash in Panel: i closed the application


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-06-20 20:46 UTC by raddy2
Modified:	2008-06-20 21:29 UTC

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

Description raddy2 2008-06-20 20:46:00 UTC

Version: 2.20.3

What were you doing when the application crashed?
i closed the application


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.20.3 2008-03-23 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-gentoo-r8 #1 SMP Mon Jun 16 18:01:33 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79097856 vsize: 79097856 resident: 31182848 share: 16130048 rss: 31182848 rss_rlim: 4294967295
CPU usage: start_time: 1213976931 rtime: 985 utime: 912 stime: 73 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb601aaa0 (LWP 5946)]
[New Thread 0xb4210b90 (LWP 8371)]
0xb7f1d410 in __kernel_vsyscall ()

+ Trace 200967

Thread 1 (Thread 0xb601aaa0 (LWP 5946))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 369
#3 IA__g_spawn_command_line_sync
at gspawn.c line 677
#4 run_bug_buddy
at gnome-breakpad.cc line 213
#5 check_if_gdb
at gnome-breakpad.cc line 283
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
#7 google_breakpad::ExceptionHandler::HandleException
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
#8 <signal handler called>
#9 IA__g_slist_remove
at gslist.c line 207
#10 backend_died_cb
at calendar-sources.c line 432
#11 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#12 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2440
#14 IA__g_signal_emit_valist
at gsignal.c line 2199
#15 IA__g_signal_emit
at gsignal.c line 2243
#16 backend_died_cb
at e-cal.c line 428
#17 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2440
#20 IA__g_signal_emit_valist
at gsignal.c line 2199
#21 IA__g_signal_emit
at gsignal.c line 2243
#22 connection_listen_cb
at e-component-listener.c line 50
#23 link_connection_emit_broken
at linc-connection.c line 146
#24 link_connection_broken_idle
at linc-connection.c line 167
#25 g_idle_dispatch
at gmain.c line 4132
#26 IA__g_main_context_dispatch
at gmain.c line 2061
#27 g_main_context_iterate
at gmain.c line 2694
#28 IA__g_main_loop_run
at gmain.c line 2898
#29 IA__gtk_main
at gtkmain.c line 1163
#30 main
at main.c line 95
#0 __kernel_vsyscall



----------- .xsession-errors (105 sec old) ---------------------
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
[swscaler @ 0x879b758]using unscaled yuv420p -> rgb32 special converter
VO: [gl] 848x480 => 852x480 BGRA 
A:   0.1 V:   0.0 A-V:  0.149 ct:  0.000   0/  0 ??% ??% ??,?% 0 0              
A:   0.3 V:   0.0 A-V:  0.235 ct:  0.004   0/  0 ??% ??% ??,?% 2 0              
A:   0.3 V:   0.1 A-V:  0.194 ct:  0.0
A:   2.5 V:   2.5 A-V: -0.007 ct:  0.017   0/  0 22% 16%  1.1% 6 0              
A:   2.5 V:   2.5 A-V: -0.005 ct:  0.017   0/  0 22% 16%  1.1% 6 0              
A:   2.6 V:   2.6 A-V: -0.005 ct:  0.0
A: 993.3 V: 993.3 A-V: -0.004 ct: -0.160   0/  0  8%  6%  1.0% 0 0              
A: 993.3 V: 993.3 A-V:  0.018 ct: -0.158   0/  0  7%  6%  1.0% 0 0              
A: 993.4 V: 993.4 A-V: -0.001 ct: -0.1
A: 994.9 V: 994.9 A-V:  0.012 ct: -0.165   0/  0  7%  7%  1.0% 0 0              
A: 994.9 V: 995.0 A-V: -0.008 ct: -0.166   0/  0  7%  7%  1.1% 0 0              
A: 995.0 V: 995.0 A-V:  0.014 ct: -0.1
A: 997.9 V: 997.9 A-V: -0.006 ct: -0.161   0/  0  8%  8%  1.0% 0 0              
A: 997.9 V: 997.9 A-V:  0.016 ct: -0.160   0/  0  8%  8%  1.0% 0 0              
A: 998.0 V: 998.0 A-V: -0.003 ct: -0.1
8552:error:0606506D:digital envelope routines:EVP_DecryptFinal_ex:wrong final block length:evp_enc.c:454:
2008-06-20 16:43:28	Service.Main	ERROR	openssl did not run successfully, error code 1
A: 998.3 V: 998.3 A-V:  0.005 ct: -0.159   0/  0  8%  8%  1.0% 0 0              
A: 998.4 V: 998.4 A-V:  0.006 ct: -0.158   0/  0  8%  8%  1.0% 0 0              
A: 998.4 V: 998.4 A-V:  0.007 ct: -0.1
A:1000.0 V:1000.0 A-V:  0.001 ct: -0.159   0/  0  9%  8%  1.0% 0 0              
A:1000.0 V:1000.0 A-V:  0.001 ct: -0.159   0/  0  9%  8%  1.0% 0 0              
A:1000.0 V:1000.0 A-V:  0.001 ct: -0.1
A:1003.5 V:1003.5 A-V: -0.004 ct: -0.164   0/  0  9%  8%  1.2% 0 0              
A:1003.5 V:1003.5 A-V: -0.003 ct: -0.164   0/  0  9%  8%  1.2% 0 0              
A:1003.6 V:1003.6 A-V:  0.019 ct: -0.1
A:1005.2 V:1005.2 A-V:  0.014 ct: -0.157   0/  0  9%  8%  1.1% 0 0              
A:1005.2 V:1005.3 A-V: -0.006 ct: -0.158   0/  0  9%  8%  1.1% 0 0              
A:1005.3 V:1005.3 A-V: -0.005 ct: -0.1
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Philip Withnall 2008-06-20 21:29:49 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 ***