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 737632 - Freeze when click on 'Manage Filters...' in GNOME 3.14
Freeze when click on 'Manage Filters...' in GNOME 3.14
Status: RESOLVED OBSOLETE
Product: gnome-system-log
Classification: Core
Component: general
3.9.x
Other Linux
: Normal major
: ---
Assigned To: gnome-system-log-maint
gnome-system-log-maint
Depends on:
Blocks:
 
 
Reported: 2014-09-29 23:37 UTC by Balló György
Modified: 2015-07-26 23:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
[PATCH] Don't freeze when opening filter manager with GTK+>=3.14 (1.32 KB, patch)
2014-10-21 17:24 UTC, Balló György 		accepted-commit_now Details | Review

Description Balló György 2014-09-29 23:37:04 UTC 
In GNOME 3.14, when I click on the 'Manage Filters...' menu item, the whole window become unresponsive. I can't do anything except close it via application menu.

Package versions:
- gnome-system-log 3.9.90
- gtk3 3.14.0

Distribution: Arch Linux

Console log:

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

(gnome-system-log:10108): Gtk-WARNING **: gtk_window_set_titlebar() called on a realized window

(gnome-system-log:10108): Gtk-CRITICAL **: _gtk_widget_captured_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
Comment 1 André Klapper 2014-09-30 07:55:59 UTC 
Can you run this under gdb to get a stacktrace when it hangs? See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
Comment 2 Balló György 2014-09-30 11:13:45 UTC 
It doesn't crash, just become unresponsive for mouse or keyboard events.
Comment 3 André Klapper 2014-09-30 13:38:39 UTC 
You can use Ctrl+C in gdb to get a stacktrace when it becomes unresponsive.
Comment 4 Balló György 2014-09-30 14:33:13 UTC 
Here is the backtrace:

+ Trace 234148

  • #0 poll
    from /usr/lib/libc.so.6
  • #1 ??
    from /usr/lib/libglib-2.0.so.0
  • #2 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #3 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #4 main 






Comment 5


André Klapper





          2014-09-30 15:40:35 UTC
        



Is there really only one thread running, or was this created by not using "thread apply all bt"? Also, this is missing any debug symbols, hmm. :-/






Comment 6


Balló György





          2014-09-30 15:52:06 UTC
        



Here is the backtrace of all thread:





+
Trace
    234149






Thread 7
          (Thread 0x7fffe4df2700 (LWP 5543))


    

  • 
#0
syscall

    
                from
                /usr/lib/libc.so.6

    

    • 

  • 
#1
g_cond_wait_until

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#2
??

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#3
g_async_queue_timeout_pop

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#4
??

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#5
??

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#6
start_thread

    
                from
                /usr/lib/libpthread.so.0

    

    • 

  • 
#7
clone

    
                from
                /usr/lib/libc.so.6

    

    • 













Comment 7


Balló György





          2014-10-01 02:14:17 UTC
        



Someone reported this also on Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1133319






Comment 8


Balló György





          2014-10-21 17:24:09 UTC
        



Created attachment 289058 [details] [review]
[PATCH] Don't freeze when opening filter manager with GTK+>=3.14

I found the problem. I attached a patch that fixes the problem.






Comment 9


Cosimo Cecchi





          2014-10-21 17:36:18 UTC
        



Review of attachment 289058 [details] [review]:

Looks good to me






Comment 10


Balló György





          2015-07-26 23:20:04 UTC
        



It was fixed in GTK+, so this workaround is no longer needed.