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 446401 - Crush on clicking on notification area
Crush on clicking on notification area
Status: RESOLVED DUPLICATE of bug 378854
Product: gnome-panel
Classification: Other
Component: general
2.19.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-11 14:58 UTC by Maciej (Matthew) Piechotka
Modified: 2007-06-11 21:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Maciej (Matthew) Piechotka 2007-06-11 14:58:17 UTC 
Steps to reproduce:
I've get some message on gajim and I click on icon as usuall. gnome-panel crashed. It is not easly reproducable.


Stack trace:
Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.19.3 2007-06-05 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.19-suspend2-r3 #16 Thu May 31 14:56:28 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 128557056 vsize: 128557056 resident: 26558464 share: 19132416 rss: 26558464 rss_rlim: 4294967295
CPU usage: start_time: 1181440116 rtime: 56185 utime: 52687 stime: 3498 cutime:1 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

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

Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal]
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225935184 (LWP 7745)]
[New Thread -1319732336 (LWP 4517)]
_______________________________________________________________________________
     eax:FFFFFE00 ebx:00005921  ecx:BFB5ADD8  edx:00000000     eflags:00000293
     esi:00000010 edi:0851C080  esp:BFB5ACF4  ebp:BFB5ADE8     eip:B7F3A410
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t S z A p C 
[007B:BFB5ACF4]---------------------------------------------------------[stack]
BFB5AD24 : 68 EE 32 08  48 AD B5 BF - 00 00 00 00  00 D4 47 08 h.2.H.........G.
BFB5AD14 : D8 AD B5 BF  00 00 00 00 - 00 DD E5 B1  00 00 00 00 ................
BFB5AD04 : 60 B1 F0 B7  00 00 00 00 - 05 52 ED B7  21 59 00 00 `........R..!Y..
BFB5ACF4 : E8 AD B5 BF  00 00 00 00 - D8 AD B5 BF  1B 62 78 B7 .............bx.
[007B:0851C080]---------------------------------------------------------[ data]
0851C080 : 00 C2 36 08  05 00 00 00 - 00 00 00 00  90 64 57 08 ..6..........dW.
0851C090 : 68 B1 17 08  3F 07 00 00 - 00 00 00 00  62 37 6E ED h...?.......b7n.
[0073:B7F3A410]---------------------------------------------------------[ code]
0xb7f3a410 <__kernel_vsyscall+16>:	pop    %ebp
0xb7f3a411 <__kernel_vsyscall+17>:	pop    %edx
0xb7f3a412 <__kernel_vsyscall+18>:	pop    %ecx
0xb7f3a413 <__kernel_vsyscall+19>:	ret    
0xb7f3a414 <_fini+92624>:	nop    
0xb7f3a415 <_fini+92625>:	nop    
------------------------------------------------------------------------------
0xb7f3a410 in __kernel_vsyscall ()

+ Trace 140088

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 IA__g_slist_remove
    at gslist.c line 207
  • #5 backend_died_cb
    at calendar-sources.c line 432
  • #6 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #7 IA__g_closure_invoke
    at gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #9 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #10 IA__g_signal_emit
    at gsignal.c line 2243
  • #11 backend_died_cb
    at e-cal.c line 430
  • #12 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #13 IA__g_closure_invoke
    at gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #16 IA__g_signal_emit
    at gsignal.c line 2243
  • #17 connection_listen_cb
    at e-component-listener.c line 50
  • #18 link_connection_emit_broken
    at linc-connection.c line 141
  • #19 link_connection_broken_idle
    at linc-connection.c line 162
  • #20 g_idle_dispatch
    at gmain.c line 4096
  • #21 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #22 g_main_context_iterate
    at gmain.c line 2694
  • #23 IA__g_main_loop_run
    at gmain.c line 2898
  • #24 IA__gtk_main
    at gtkmain.c line 1142
  • #25 main
    at main.c line 99 




Other information:
Comment 1 Pascal Terjan 2007-06-11 21:02:07 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 378854 ***