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 527250 - Crash in clock_map_mark
Crash in clock_map_mark
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-04-09 23:39 UTC by Cláudio Esperança
Modified: 2008-04-10 13:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Cláudio Esperança 2008-04-09 23:39:28 UTC 
Version: 2.22.0

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.12
Gnome Release: 2.22.0 2008-04-07 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-gentoo-r4 #1 SMP Mon Mar 31 19:42:01 WEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: etiquette

Memory status: size: 97157120 vsize: 97157120 resident: 54116352 share: 17076224 rss: 54116352 rss_rlim: 4294967295
CPU usage: start_time: 1207777447 rtime: 2583 utime: 2501 stime: 82 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

[Thread debugging using libthread_db enabled]
[New Thread 0xb609e6f0 (LWP 17799)]
[New Thread 0xb4ed8b90 (LWP 3041)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 194786

Thread 1 (Thread 0xb609e6f0 (LWP 17799))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 clock_map_mark
    at clock-map.c line 292
  • #10 highlight
    at clock-map.c line 422
  • #11 g_timeout_dispatch
    at gmain.c line 3443
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2009
  • #13 g_main_context_iterate
    at gmain.c line 2642
  • #14 IA__g_main_loop_run
    at gmain.c line 2850
  • #15 IA__gtk_main
    at gtkmain.c line 1163
  • #16 main
    at main.c line 95
  • #0 __kernel_vsyscall 


----------- .xsession-errors (4125 sec old) ---------------------
09-04-2008 23:38:15 [Info]: Updated "Internal GNOME Do Items" Item Source.
09-04-2008 23:38:15 [Info]: Updated "GNOME Do Item Sources" Item Source.
Could not read Banshee database file: Unable to open the database file
unable to open database file
09-04-2008 23:38:15 [Info]: Updated "Banshee Music" Item Source.
09-04-2008 23:38:15 [Info]: Updated "Epiphany Bookmarks" Item Source.
09-04-2008 23:38:15 [Info]: Updated "GNOME Session Commands" Item Source.
09-04-2008 23:38:15 [Info]: Updated "Pidgin Buddies" Item Source.
Could not read Rhythmbox database file: Could not find a part of the path "/home/cesperanc/.gnome2/rhythmbox/rhythmdb.xml".
09-04-2008 23:38:15 [Info]: Updated "Rhythmbox Music" Item Source.
09-04-2008 23:38:15 [Info]: Updated "SSH Hosts" Item Source.
Cannot index Thunderbird contacts because a System.ArgumentNullException was thrown: Argument cannot be null.
Parameter name: path
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-04-10 06:05:37 UTC 
Similar to bug #519493.
Comment 2 Vincent Untz 2008-04-10 06:35:33 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 519493 ***
Comment 3 Cláudio Esperança 2008-04-10 13:44:38 UTC 
Amazing... Thanks a lot for your answer. I will update this software very soon.