Menu

#167 gtk2 immodule cause gnome-screensaver-dialog to hang on exit

1.4.x
closed
nobody
5
2017-01-05
2009-03-25
No

When unlocking the screensaver, from time to time the dialog stays there forever

The reason is that it gets blocked on a lock when exit() is called:

#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb775a829 in __lll_lock_wait () from /lib/i686/libpthread.so.0
#2 0xb7755d93 in _L_lock_89 () from /lib/i686/libpthread.so.0
#3 0xb77557ea in pthread_mutex_lock () from /lib/i686/libpthread.so.0
#4 0xb77a0c65 in IA__g_main_context_find_source_by_id (context=0x93eace8, source_id=10) at gmain.c:1247
#5 0xb77a0cee in IA__g_source_remove (tag=4294966784) at gmain.c:1379
#6 0xb6b2e57d in ?? () from /usr/lib/gtk-2.0/immodules/im-scim.so
#7 0xb6b35676 in ?? () from /usr/lib/gtk-2.0/immodules/im-scim.so
#8 0xb6b3598f in gtk_im_context_scim_shutdown () from /usr/lib/gtk-2.0/immodules/im-scim.so
#9 0xb6b3e0d9 in FinalizeHandler::~FinalizeHandler () from /usr/lib/gtk-2.0/immodules/im-scim.so
#10 0xb7628cd9 in exit (status=0) at exit.c:75
#11 0xb66ddff7 in _unix_fork (pamh=0x95ba900, callback=0xb66daab0 <acct_shadow>, param=0x9527460) at support.c:147
#12 0xb66dad58 in pam_sm_acct_mgmt (pamh=0x95ba900, flags=0, argc=2, argv=0x95bca50) at pam_unix_acct.c:114
#13 0xb7e73282 in ?? () from /lib/libpam.so.0
#14 0xb7e728c5 in pam_acct_mgmt () from /lib/libpam.so.0
#15 0x08052db3 in gs_auth_thread_func (auth_operation_fd=18) at gs-auth-pam.c:523
#16 0xb77c9fb4 in g_thread_create_proxy (data=0x95befb0) at gthread.c:635
#17 0xb7754315 in start_thread () from /lib/i686/libpthread.so.0
#18 0xb76d826e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Discussion

  • Rolf

    Rolf - 2011-09-12
    • assigned_to: suzhe --> nobody
     
  • Rolf

    Rolf - 2017-01-05
    • status: open --> closed
     
  • Rolf

    Rolf - 2017-01-05

    scim has moved development to github. Seeing that this ticket is unverified I ask you to kindly open a new ticket at https://github.com/scim-im/scim/issues/ if you are still affected by this bug. Thank you.

     

Log in to post a comment.