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 519493 - Crash in clock_map_place_locations
Crash in clock_map_place_locations
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 522348 522679 523964 527250 527344 533325 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-02-29 11:30 UTC by Priit Laes (IRC: plaes)
Modified: 2008-05-15 21:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Priit Laes (IRC: plaes) 2008-02-29 11:30:24 UTC 
Version: 2.21.92

What were you doing when the application crashed?
I was clicking around on different cities (in the clock view) then closed the view.


Distribution: Gentoo Base System release 2.0.0_rc6-r1
Gnome Release: 2.21.92 2008-02-27 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.25-rc3-00081-g7704a8b #11 SMP PREEMPT Thu Feb 28 09:43:44 EET 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 455454720 vsize: 455454720 resident: 27635712 share: 15466496 rss: 27635712 rss_rlim: 18446744073709551615
CPU usage: start_time: 1204185481 rtime: 4956 utime: 4501 stime: 455 cutime:8 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7fa9b91b26f0 (LWP 3305)]
[New Thread 0x40249950 (LWP 4639)]
[New Thread 0x42315950 (LWP 3569)]
0x00007fa9b656dfbf in __libc_waitpid (pid=4735, stat_loc=0x7fffc11ed410, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 190832

Thread 1 (Thread 0x7fa9b91b26f0 (LWP 3305))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #3 bugbuddy_segv_handle
    at gnome-breakpad.cc line 213
  • #4 <signal handler called>
  • #5 clock_map_place_locations
    at clock-map.c line 432
  • #6 highlight
    at clock-map.c line 673
  • #7 g_timeout_dispatch
    at gmain.c line 3499
  • #8 IA__g_main_context_dispatch
    at gmain.c line 2065
  • #9 g_main_context_iterate
    at gmain.c line 2698
  • #10 IA__g_main_loop_run
    at gmain.c line 2906
  • #11 IA__gtk_main
    at gtkmain.c line 1163
  • #12 main
    at main.c line 95 


----------- .xsession-errors (384 sec old) ---------------------
Error (51287): Illegal character '>'
Error (51297): Missing 'endstream'
Error (48160): Illegal character '>'
Error (48170): Missing 'endstream'
Error (66665): Illegal character '>'
Error (66675): Missing 'endstream'
Error (65782): Illegal character '>'
Error (65792): Missing 'endstream'
Error (48160): Illegal character '>'
Error (48170): Missing 'endstream'
Error (48160): Illegal character '>'
Error (48170): Missing 'endstream'
Error (57053): Illegal character '>'
Error (57063): 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Priit Laes (IRC: plaes) 2008-02-29 11:47:03 UTC 
The way to reproduce:
1) Open the clock applet 
2) Click on any of the cities so it shows blinking dot on the map
3) Quickly close the clock applet
4) It crashes.
Comment 3 Philip Withnall 2008-03-14 06:37:12 UTC 
*** Bug 522348 has been marked as a duplicate of this bug. ***
Comment 4 Philip Withnall 2008-03-15 23:21:31 UTC 
*** Bug 522679 has been marked as a duplicate of this bug. ***
Comment 5 Vincent Untz 2008-04-02 16:19:26 UTC 
*** Bug 523964 has been marked as a duplicate of this bug. ***
Comment 6 Vincent Untz 2008-04-02 16:22:16 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 7 Vincent Untz 2008-04-10 06:35:33 UTC 
*** Bug 527250 has been marked as a duplicate of this bug. ***
Comment 8 Vincent Untz 2008-04-11 09:38:35 UTC 
*** Bug 527344 has been marked as a duplicate of this bug. ***
Comment 9 Philip Withnall 2008-05-15 21:18:58 UTC 
*** Bug 533325 has been marked as a duplicate of this bug. ***