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 510016 - crash in Clock:
crash in Clock:
Status: RESOLVED DUPLICATE of bug 357939
Product: gnome-panel
Classification: Other
Component: clock
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-16 21:40 UTC by soliman.esam
Modified: 2008-01-16 22:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description soliman.esam 2008-01-16 21:40:05 UTC 
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve-Lime
Icon Theme: Fedora

Memory status: size: 29876224 vsize: 29876224 resident: 10993664 share: 8753152 rss: 10993664 rss_rlim: 4294967295
CPU usage: start_time: 1200544475 rtime: 75 utime: 61 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/clock-applet'

(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 -1208731104 (LWP 3071)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 185625

Thread 1 (Thread -1208731104 (LWP 3071))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_list_free
    from /usr/lib/libpango-1.0.so.0
  • #5 pango_attr_iterator_destroy
    from /usr/lib/libpango-1.0.so.0
  • #6 ??
    from /usr/lib/libpango-1.0.so.0
  • #7 ??
    from /usr/lib/libpango-1.0.so.0
  • #8 pango_layout_get_pixel_extents
    from /usr/lib/libpango-1.0.so.0
  • #9 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #10 ??
  • #11 ??
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #18 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #19 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #20 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #21 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (164 sec old) ---------------------
(bug-buddy:2919): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:2919): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:3029): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
(bug-buddy:3029): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject'
(bug-buddy:3029): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:3029): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:3029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
ICE default IO error handler doing an exit(), pid = 2867, errno = 0
ICE default IO error handler doing an exit(), pid = 2869, errno = 0
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-16 22:47:48 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 357939 ***