FS#47813 - [mono] smuxi-frontend-gnome hangs on exit
Attached to Project:
Arch Linux
Opened by Sebastiaan Lokhorst (lonaowna) - Monday, 18 January 2016, 15:21 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 31 January 2016, 12:23 GMT
Opened by Sebastiaan Lokhorst (lonaowna) - Monday, 18 January 2016, 15:21 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 31 January 2016, 12:23 GMT
|
Details
When I quit Smuxi, the window freezes and nothing happens.
My WM (Openbox) then says: "The window "Smuxi" does not seem
to be responding.
In the terminal, the following is shown (not sure if related): (smuxi-frontend-gnome:11585): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion 'iter->user_data != NULL' failed (smuxi-frontend-gnome:11585): Gtk-CRITICAL **: IA__gtk_tree_model_get_iter: assertion 'path != NULL' failed (smuxi-frontend-gnome:11585): Gtk-CRITICAL **: IA__gtk_progress_set_percentage: assertion 'percentage >= 0 && percentage <= 1.0' failed (smuxi-frontend-gnome:11585): Gtk-CRITICAL **: IA__gtk_progress_set_percentage: assertion 'percentage >= 0 && percentage <= 1.0' failed I already wiped ~/.config/smuxi, but made no difference. This is 100% reproducible for me. |
This task depends upon
Closed by Isenmann Daniel (ise)
Sunday, 31 January 2016, 12:23 GMT
Reason for closing: Fixed
Additional comments about closing: Package version 2 is in the repos and should be on your preferred mirror soon.
Sunday, 31 January 2016, 12:23 GMT
Reason for closing: Fixed
Additional comments about closing: Package version 2 is in the repos and should be on your preferred mirror soon.
Also a debug log would help, quit Smuxi and then start it from a terminal like this: smuxi-frontend-gnome -d
The debug log should be checked for sensitive data, before you paste/post it.
(and by the way, also the latest smuxi: 1.0.1-1)
Log (I pressed the quit button at 08:04:03):
https://gist.github.com/lonaowna/48a3b13e29d01c8637a8
Thanks!
That will print a thread dump on the terminal, please paste it here.
However, when I "quit" Smuxi, and then run "kill -QUIT $(pidof mono)", nothing happens. It just remains in the freezed/non-responding state. "kill -KILL $(pidof mono)" works, but that doesn't print a thread dump.
(Smuxi is the only mono process running)
It's really weird: after experimenting with some older versions I reinstalled the latest one, and now the problem is gone!
I have no idea what happened.. Maybe a file got corrupted or something..
In any case, thanks a lot for helping me debug!
It stays for me in another situation.
Choosing a remote engine (although running on localhost) makes smuxi unresponsive und needs to be killed the hard way.
A thread dump from this: https://paste.archlinux.de/CHpG/
Should note though, that I use a fresh build from master
The message on quit are unrelated
to the reported issue and they are harmless.
And I mainly wrote the message because of the behaving of smuxi, although on a different action was the same (hanging, unresponsive) and wondered if they could be related.
If not sorry for the noise
This issue is tracked upstream here: https://smuxi.im/issues/show/1084