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 560651 - Crash in Clock Applet when clicked
Crash in Clock Applet when clicked
Status: RESOLVED DUPLICATE of bug 546834
Product: gnome-panel
Classification: Other
Component: clock
2.22.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-13 15:44 UTC by Harlan Lieberman-Berg
Modified: 2008-12-08 12:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Bug Buddy Output (2.08 KB, text/plain)
2008-11-15 17:28 UTC, Harlan Lieberman-Berg 		Details
Real Output (14.37 KB, text/plain)
2008-11-15 17:33 UTC, Harlan Lieberman-Berg 		Details

Description Harlan Lieberman-Berg 2008-11-13 15:44:14 UTC 
Steps to reproduce:
When the clock applet is clicked to get a list of appointments and tasks, it immediately terminates, and prompts you to reload or not reload it.

Evolution version is 2.22.3.1.  The calender in Evolution works fine.


Stack trace:
Unable to get stack trace because of it being an applet.

Other information:
Comment 1 Harlan Lieberman-Berg 2008-11-13 15:50:29 UTC 
Interesting.

When I test the applet with panel-test-applets, it works fine.  Full functionality, no crash.  Maybe a configuration file is bad somewhere? I haven't changed any.
Comment 2 palfrey 2008-11-13 20:21:32 UTC 
Can you try running the gnome-panel from the command line (run "gnome-session-remove gnome-panel" first to stop it from respawning automatically) and see if crashes then?
Comment 3 Harlan Lieberman-Berg 2008-11-13 23:25:46 UTC 
Still crashes when I run gnome-panel from the command line.  No output.

The crash happens when the "tasks" tab is open. When closed, it runs fine.
Comment 4 palfrey 2008-11-14 16:30:47 UTC 
Hmm. I'm guessing you have a /usr/libexec/clock-applet then (other locations may also apply, depending on your distro, should be in the gnome-panel package)? If so, then remove the clock applet from your panel, run that in a terminal window, then re-add it to your panel and do the steps necessary to crash it. That *should* result in the clock-applet from the terminal terminating, and then if you can follow the standard instructions for gdb at http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running to get us a stacktrace that would be great!
Comment 5 Harlan Lieberman-Berg 2008-11-14 22:14:51 UTC 
Stack trace attached, though it probably won't help very well without the debugging symbols... I can compile it by hand using an SRPM, but that may take me a while to figure out how to do.

Program received signal SIGSEGV, Segmentation fault.
0x0000003abae0b6cd in g_closure_invoke () from /lib64/libgobject-2.0.so.0
(gdb) 
(gdb) thread apply all bt

+ Trace 209795

Thread 1 (Thread 0x7f0fb962c7f0 (LWP 21779))

  • #0 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #1 ??
    from /lib64/libgobject-2.0.so.0
  • #2 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #3 g_signal_emit_by_name
    from /lib64/libgobject-2.0.so.0
  • #4 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 gtk_widget_size_request
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #12 ??
    from /lib64/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #15 bonobo_generic_factory_main_timeout
    from /usr/lib64/libbonobo-2.so.0
  • #16 panel_applet_factory_main_closure
    from /usr/lib64/libpanel-applet-2.so.0
  • #17 gtk_toggle_button_set_active
  • #18 __libc_start_main
    from /lib64/libc.so.6
  • #19 gtk_toggle_button_set_active
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ?? 






Comment 6


palfrey





          2008-11-15 13:27:29 UTC
        



I don't know what distribution you're running, but http://live.gnome.org/GettingTraces/DistroSpecificInstructions has instructions for various ones on how to get debug symbols for them (often without recompiling). Judging from the stack, we especially need the debug symbols for glib, gobject and gtk, and the symbols for the clock applet itself (which should be in the gnome-panel debug package).

Thanks for all your help!






Comment 7


Harlan Lieberman-Berg





          2008-11-15 17:28:08 UTC
        



Created attachment 122737 [details]
Bug Buddy Output






Comment 8


Harlan Lieberman-Berg





          2008-11-15 17:29:39 UTC
        



Once I installed the debuginfo, Bug Buddy started doing it's job! 

I've attached the output.

Thanks for your help! :3






Comment 9


palfrey





          2008-11-15 17:31:56 UTC
        



Um, that appears to only be the data from frame #19 downwards... could we possibly have the rest of the output?






Comment 10


Harlan Lieberman-Berg





          2008-11-15 17:33:22 UTC
        



Created attachment 122739 [details]
Real Output






Comment 11


Harlan Lieberman-Berg





          2008-11-15 17:33:58 UTC
        



Sorry for the spam - I didn't copy all the output to the text file correctly! Got it right this time.

Sorry for the problems. :(







Comment 12


Vincent Untz





          2008-12-08 12:44:55 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 546834 ***