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 522348 - crash in Clock: Exaile was playing minim...
crash in Clock: Exaile was playing minim...
Status: RESOLVED DUPLICATE of bug 519493
Product: gnome-panel
Classification: Other
Component: clock
2.22.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-14 01:18 UTC by i_am_the_master_potato
Modified: 2008-03-14 06:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description i_am_the_master_potato 2008-03-14 01:18:20 UTC 
Version: 2.22.0

What were you doing when the application crashed?
Exaile was playing minimised in the system tray


Distribution: Unknown
Gnome Release: 2.22.0 2008-03-11 (Foresight Linux)
BugBuddy Version: 2.22.0

System: Linux 2.6.23.16-0.0.1.smp.gcc4.1.x86.i686 #1 SMP Tue Feb 12 00:14:27 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Foresight
Icon Theme: Tango

Memory status: size: 112975872 vsize: 112975872 resident: 20217856 share: 13619200 rss: 20217856 rss_rlim: 4294967295
CPU usage: start_time: 1205453592 rtime: 571 utime: 554 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6771900 (LWP 12313)]
[New Thread 0xb636fb90 (LWP 15771)]
0xb7eeb410 in __kernel_vsyscall ()

+ Trace 192359

Thread 1 (Thread 0xb6771900 (LWP 12313))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 clock_map_place_locations
    at clock-map.c line 432
  • #10 highlight
    at clock-map.c line 673
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 ??
    from /usr/lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libpthread.so.0
  • #19 ??
  • #20 ??
    from /usr/lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
  • #23 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (54 sec old) ---------------------
3/14/2008 1:16:17 AM [Info]: Updated "GNOME Do Item Sources" Item Source.
3/14/2008 1:16:18 AM [Info]: Updated "Applications" Item Source.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'd'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'e'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'f'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'g'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'h'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'i'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'j'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'k'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'l'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'm'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'n'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'o'.
3/14/2008 1:16:18 AM [Info]: Updated first results for 'p'.
--------------------------------------------------
Comment 1 Philip Withnall 2008-03-14 06:37:12 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 519493 ***