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 494792 - 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: 2007-11-07 23:14 UTC by soliman.esam
Modified: 2007-11-13 08:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description soliman.esam 2007-11-07 23:14:13 UTC
Version: 2.18.3

What were you doing when the application crashed?



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

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 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: 29859840 vsize: 29859840 resident: 10989568 share: 8753152 rss: 10989568 rss_rlim: 4294967295
CPU usage: start_time: 1194431434 rtime: 114 utime: 94 stime: 20 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 -1208190432 (LWP 2534)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208190432 (LWP 2534))

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


----------- .xsession-errors (18 sec old) ---------------------
If you need additional public API, please contact the maintainers via
<dbus@lists.freedesktop.org>.
  from dbus.dbus_bindings import *
INFO     Starting up Miro
INFO     Version:  0.9.8-svn
INFO     Revision: unknown
INFO     Loading preferences...
INFO     Starting event loop thread
INFO     Restoring database...
INFO     Connecting to /home/esam/.miro/sqlitedb
/usr/bin/miro: line 2:  2463 Segmentation fault      LD_LIBRARY_PATH=/usr/lib/firefox-2.0.0.8 miro.real
/usr/local/RealPlayer/realplay.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/usr/local/RealPlayer/realplay.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
error getting update info:  Cannot retrieve repository metadata (repomd.xml) for repository: freshrpms. Please verify its path and try again
--------------------------------------------------
Comment 1 Vincent Untz 2007-11-13 08:56:28 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 ***