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 125773 - crash after systray aplet close
crash after systray aplet close
Status: RESOLVED FIXED
Product: GnomeICU
Classification: Deprecated
Component: General
0.98.x
Other Linux
: Normal minor
: ---
Assigned To: gnomeicu-maint
gnomeicu-maint
Depends on:
Blocks:
 
 
Reported: 2003-10-29 13:06 UTC by Stanislav Brabec
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stanislav Brabec 2003-10-29 13:06:23 UTC
gnomeicu &

Wait for systray icon and double click to hide gnomeicu window.

killall gnome-panel

Systray icon will not re-appear in new systray applet instance.

gnomeicu &

You will now see force disconnect message from old (invisible) gnomeicu
instance. Immediatelly after it, old instance crashes with segfault.
Comment 1 Elijah Newren 2003-12-11 17:02:05 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash.  Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.

Comment 2 Stanislav Brabec 2003-12-12 09:46:39 UTC
How to repeat was not complete:
Very first condition is:
- You must have running gnome-panel with systray applet.

It occur nearly evary time.

Even if it does not crash, second problem, occur every time: Systray
icon will not re-appear after "killall gnome-panel".

Sorry for not having debug symbols.

Backtrace was generated from '/opt/gnome/bin/gnomeicu'

(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 29399)]
[New Thread 32769 (LWP 29400)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...0x40b67006 in waitpid
    () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 29399))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_cast
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #5 tray_update
  • #6 v7_handler
  • #7 g_io_unix_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #8 g_main_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #10 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 3 Stanislav Brabec 2004-01-05 10:21:45 UTC
This bug can have relation with bug 130554.
Comment 4 Patrick Sung 2004-01-26 05:30:10 UTC
bug 130554 marked as dup of bug 122327. bug 122327 seems to be fixed.
Have to test against gtk+ CVS head to confirm.
Comment 5 Stanislav Brabec 2004-01-26 09:41:56 UTC
Tested against gtk+-2.2.4 with explicit fix of bug 122327 (SuSE Linux
9.0 online update). Still the same crash.
Comment 6 Patrick Sung 2004-01-27 01:53:35 UTC
Two things I want you to check, after you kill gnome-panel. do a 'ps
ax' . Can you see if the gnomeicu process is still there? If it is,
can you go to /tmp (before killing gnomeicu) and do 'ls -a' and can
you see any directory named '.gnomeicu-USERNAME' where USERNAME is
your unix user name. If it is there, tell me the files inside the
directory. Thanks.
Comment 7 Stanislav Brabec 2004-01-27 09:59:10 UTC
I have tried it again. It seems, that crash is not 100% repeatable
(but never behaves correctly). There are problems for both "GUI hidden
via systray" and "GUI visible".

I found following behaviors during tests:

GUI hidden or visible: after "killall gnome-panel" gnomeicu process
segfaults.

GUI hidden via systray: after "killall gnome-panel" gnomeicu process
continues to exist without any GUI. After issuing new gnomeicu, old
one does not respond.

GUI hidden via systray: after "killall gnome-panel" gnomeicu process
continues to exist without any GUI. After issuing new gnomeicu, old
one segfaults.

GUI visible: after "killall gnome-panel" gnomeicu process continues to
exist, but GUI is dead and does not respond.

Expected correct behavior:

After "killall gnome-panel" gnomeicu process redisplays systray icon
or shows GUI.

> ps ax | grep -i gnomeicu ; ls -al /tmp/.gnomeicu-sbrabec
 2230 ?        T      0:00 gnomeicu
25009 ?        S      0:00 gnomeicu
25010 ?        S      0:00 gnomeicu
25068 pts/4    R      0:00 grep -i gnomeicu
total 2
drwx------    2 sbrabec  users         104 2004-01-27 10:40 .
drwxrwxrwt   19 root     root         2024 2004-01-27 10:38 ..
lrwxrwxrwx    1 sbrabec  users          36 2004-01-26 10:36 ctl ->
/tmp/.gnomeicu-sbrabec/ctl-116020046
srwx------    1 sbrabec  users           0 2004-01-27 10:40 ctl-116020046
> killall gnome-panel
> sleep 5
> sbrabec@unicorn:~> ps ax | grep -i gnomeicu ; ls -al
/tmp/.gnomeicu-sbrabec
 2230 ?        T      0:00 gnomeicu
25009 ?        S      0:00 gnomeicu
25010 ?        S      0:00 gnomeicu
25078 pts/4    R      0:00 grep -i gnomeicu
total 2
drwx------    2 sbrabec  users         104 2004-01-27 10:40 .
drwxrwxrwt   19 root     root         2024 2004-01-27 10:38 ..
lrwxrwxrwx    1 sbrabec  users          36 2004-01-26 10:36 ctl ->
/tmp/.gnomeicu-sbrabec/ctl-116020046
srwx------    1 sbrabec  users           0 2004-01-27 10:40 ctl-116020046
Comment 8 Olivier Crête 2004-03-14 14:20:41 UTC
Ok, I changed the code to show the main window if the tray is
destroyed... but I can't reproduce any segfault.. For gnomeicu or the
panel freezing, there is a bug in gtk 2.2.4.. there is a patch at
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/x11-libs/gtk%2B/files/gtk%2B-2.2-notificationarea_loop.patch?rev=1.1&content-type=text/plain

Re-open if you can reproduce with current cvs and patched gtk+...