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 601519 - Cannot start evolution-alarm-notify process
Cannot start evolution-alarm-notify process
Status: RESOLVED DUPLICATE of bug 602102
Product: evolution
Classification: Applications
Component: Calendar
2.30.x (obsolete)
Other Linux
: Normal blocker
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-11 12:06 UTC by Milan Crha
Modified: 2013-09-13 01:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2009-11-11 12:06:37 UTC 
I cannot start today's (commit 3dfdf08) evolution-alarm-notify from master, located at $PREFIX/bin/evolution-alarm-notify .
It starts but after a little while I get a segmentation fault in Thread 2:

+ Trace 219006

Thread 2 (Thread 0x7fffeec5b910 (LWP 11478))

  • #0 _int_malloc
    from /lib64/libc.so.6
  • #1 malloc
    from /lib64/libc.so.6
  • #2 g_malloc
    from /lib64/libglib-2.0.so.0
  • #3 g_strdup
    from /lib64/libglib-2.0.so.0
  • #4 gconf_engine_get_fuller
    from /usr/lib64/libgconf-2.so.4
  • #5 gconf_engine_get_entry
    from /usr/lib64/libgconf-2.so.4
  • #6 ??
    from /usr/lib64/libgconf-2.so.4
  • #7 ??
    from /usr/lib64/libgconf-2.so.4
  • #8 gconf_client_get_string
    from /usr/lib64/libgconf-2.so.4
  • #9 config_data_get_timezone
    at config-data.c line 212
  • #10 load_alarms_for_today
    at alarm-queue.c line 563
  • #11 alarm_queue_add_async
    at alarm-queue.c line 1972
  • #12 message_proxy
    at alarm-queue.c line 164
  • #13 ??
    from /lib64/libglib-2.0.so.0
  • #14 ??
    from /lib64/libglib-2.0.so.0
  • #15 start_thread
    from /lib64/libpthread.so.0
  • #16 clone
    from /lib64/libc.so.6
  • #17 ??

Thread 1 (Thread 0x7ffff4e86800 (LWP 11459))

  • #0 __lll_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_lock_949
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 g_main_context_prepare
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #6 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 main
    at notify-main.c line 80 






Comment 1


Matthew Barnes





          2009-11-11 13:08:55 UTC
        



Calling GConf from Thread != 1 --> FAIL.






Comment 2


Chenthill P





          2009-11-17 06:58:12 UTC
        



Fix at https://bugzilla.gnome.org/show_bug.cgi?id=602102#c4 would fix this. Will see if we can separate the gconf part to main thread.






Comment 3


Milan Crha





          2009-11-18 11:39:02 UTC
        



Yes, thanks, that de-threading works for me. Even with potential issues on slowness or something, it's still better than crashing and no notifications at all. I'm marking this as a duplicate and I'm providing a comment there as well.

*** This bug has been marked as a duplicate of bug 602102 ***