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 523964 - Crash in clock_map_place_location
Crash in clock_map_place_location
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-23 10:50 UTC by Christoph Reiter (lazka)
Modified: 2008-04-02 16:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Christoph Reiter (lazka) 2008-03-23 10:50:31 UTC 
Steps to reproduce:
1. add a location so it will show in the applet and on the map
2. click 3-4 times on the location so that the blink animation on the map will last for some time
3. while the blink animation is going on click on the clock applet (for closing the dialog) -> crash


Stack trace:


Other information:
Comment 1 Philip Withnall 2008-03-23 11:16:12 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Christoph Reiter (lazka) 2008-03-23 21:17:19 UTC 
Like this?

(gdb) cont
Continuing.
[New Thread 0xb556ab90 (LWP 8506)]
[New Thread 0xb5d80b90 (LWP 8510)]
[Thread 0xb5d80b90 (LWP 8510) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6d7e720 (LWP 8403)]
clock_map_place_location (this=0x8159720, loc=0x8333660, hilight=1)
    at clock-map.c:292
292	clock-map.c: No such file or directory.
	in clock-map.c
(gdb) thread apply all bt

+ Trace 193162

Thread 1 (Thread 0xb6d7e720 (LWP 8403))

  • #0 clock_map_place_location
    at clock-map.c line 292
  • #1 highlight
    at clock-map.c line 671
  • #2 ??
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
  • #4 __pthread_mutex_unlock_usercnt
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ?? 






Comment 3


Philip Withnall





          2008-03-23 22:39:36 UTC
        



Could you make sure you've got the debug symbols in place and try to get a more complete stack trace please?






Comment 4


Christoph Reiter (lazka)





          2008-03-23 23:06:34 UTC
        



Hm, sorry.. my thirst time.
Better? :)

(gdb) cont
Continuing.
[New Thread 0xb5d7ab90 (LWP 7835)]
[Thread 0xb5d7ab90 (LWP 7835) exited]
[New Thread 0xb5564b90 (LWP 7836)]
[New Thread 0xb5d7ab90 (LWP 7840)]
[Thread 0xb5d7ab90 (LWP 7840) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6d7b720 (LWP 7811)]
clock_map_place_location (this=0x852b000, loc=0x8335280, hilight=1)
    at clock-map.c:292
292	clock-map.c: No such file or directory.
	in clock-map.c
(gdb) thread apply all bt





+
Trace
    193166






Thread 1
          (Thread 0xb6d7b720 (LWP 7811))


    

  • 
#0
clock_map_place_location

    
                at clock-map.c
                  line
                  292

    

    • 

  • 
#1
highlight

    
                at clock-map.c
                  line
                  671

    

    • 

  • 
#2
g_timeout_dispatch

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  3437

    

    • 

  • 
#3
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  2003

    

    • 

  • 
#4
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  2636

    

    • 

  • 
#5
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.16.1/glib/gmain.c
                  line
                  2844

    

    • 

  • 
#6
IA__gtk_main

    
                at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c
                  line
                  1163

    

    • 

  • 
#7
main

    
                at main.c
                  line
                  100

    

    • 













Comment 5


Philip Withnall





          2008-03-23 23:14:15 UTC
        



Looks very similar to bug #519493. Thanks for the nice stack trace.






Comment 6


Vincent Untz





          2008-04-02 16:19:26 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 ***