Bug 100271 - Weston crashes after typing in GTK open dialog
Summary: Weston crashes after typing in GTK open dialog
Status: RESOLVED MOVED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-18 23:33 UTC by Bug Report
Modified: 2018-06-08 23:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bug Report 2017-03-18 23:33:33 UTC
Weston crashes after opening a GTK application (say gedit) pressing Ctrl+O, typing file name (e.g starting with a dot) when once file opens clicking the close icon. Using mouse does not seem to cause a crash.
Comment 1 Bug Report 2017-03-18 23:33:59 UTC
This is on Archlinux 64bit, intel and latest weston
Comment 2 Bug Report 2017-03-18 23:39:06 UTC
The issue does not occur on Gnome or sway so it's an issue with weston and/or weston+gtk.
Comment 3 bugreport11 2018-03-27 19:49:38 UTC
Still an issue with latest master and latest Archlinux
Comment 4 Daniel Stone 2018-03-28 09:12:06 UTC
This only happens for me in Xwayland mode, not when GEdit runs natively. Backtrace for xwl:

#0  0x00007f4e0b305de9 in wl_signal_get (signal=0xaef438, notify=0x7f4e0b309556 <surface_destroy>) at /home/daniels/prefix/wayland/include/wayland-server-core.h:449
#1  0x00007f4e0b30aec3 in get_wm_window (surface=0xaef430) at ../xwayland/window-manager.c:2638
#2  0x00007f4e0b30aeff in is_wm_window (surface=0xaef430) at ../xwayland/window-manager.c:2649
#3  0x00007f4e0b7360d0 in transform_handler (listener=0x9dc518, data=0xaef430) at ../desktop-shell/shell.c:4121
#4  0x00007f4e16a47ebd in wl_signal_emit (signal=0x80de68, data=0xaef430) at /home/daniels/prefix/wayland/include/wayland-server-core.h:468
#5  0x00007f4e16a4b779 in weston_view_update_transform (view=0xaf1dc0) at ../libweston/compositor.c:1313
#6  0x00007f4e16a4d623 in view_list_add (compositor=0x80de20, view=0xaf1dc0) at ../libweston/compositor.c:2220
#7  0x00007f4e16a4d7c8 in weston_compositor_build_view_list (compositor=0x80de20) at ../libweston/compositor.c:2248
#8  0x00007f4e16a4da40 in weston_output_repaint (output=0x9af890, repaint_data=0x0) at ../libweston/compositor.c:2300
#9  0x00007f4e16a4dedb in weston_output_maybe_repaint (output=0x9af890, now=0x7ffe292f7040, repaint_data=0x0) at ../libweston/compositor.c:2402
#10 0x00007f4e16a4e097 in output_repaint_timer_handler (data=0x80de20) at ../libweston/compositor.c:2468
#11 0x00007f4e168323ab in wl_event_source_timer_dispatch (source=0x80e3a0, ep=<optimized out>) at ../src/event-loop.c:236
#12 0x00007f4e16832992 in wl_event_loop_dispatch (loop=0x803ee0, timeout=timeout@entry=-1) at ../src/event-loop.c:641
#13 0x00007f4e1683128a in wl_display_run (display=0x806900) at ../src/wayland-server.c:1260
#14 0x0000000000407574 in main (argc=1, argv=0x7ffe292f7638) at ../compositor/main.c:1881


Can't seem to make it happen under Valgrind, annoyingly.
Comment 5 bugreport11 2018-03-29 16:03:23 UTC
It crashes on native Wayland for me. Here are the steps

In terminal run weston

Click weston-terminal and type gedit

Press Ctrl+O, then start typing /home/username/.config/weston.ini - The actual file doesn't have to exist, but the dot after /home/username/ has to for the crash to occur. Interestingly, typing /home/.username/somefile doesn't crash.

After pressing Enter in the file picker, within 1-3 secs click close icon in gedit. It should crash in 1-3 secs.

Getting these in journalctl

Process 10925 (weston) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 10925:
                                                 #0  0x00007f7b35090860 raise (libc.so.6)
                                                 #1  0x00007f7b350908e0 __restore_rt (libc.so.6)
                                                 #2  0x000055880e702e50 n/a (n/a)


Process 10788 (weston) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 10788:
                                                 #0  0x00007fc41066a860 raise (libc.so.6)
                                                 #1  0x00007fc41066a8e0 __restore_rt (libc.so.6)
                                                 #2  0x00007fc41066a860 raise (libc.so.6)
                                                 #3  0x00007fc41066bec9 abort (libc.so.6)
                                                 #4  0x00007fc4106ad437 __libc_message (libc.so.6)
                                                 #5  0x00007fc4106b378b malloc_printerr (libc.so.6)
                                                 #6  0x00007fc4106b536c _int_free (libc.so.6)
                                                 #7  0x00007fc41104ac20 n/a (libwayland-server.so.0)
                                                 #8  0x00007fc41104f619 n/a (libwayland-server.so.0)
                                                 #9  0x00007fc41104acff wl_client_destroy (libwayland-server.so.0)
                                                 #10 0x00007fc41104adb9 n/a (libwayland-server.so.0)
                                                 #11 0x00007fc41104c9b2 wl_event_loop_dispatch (libwayland-server.so.0)
                                                 #12 0x00007fc41104b14c wl_display_run (libwayland-server.so.0)
                                                 #13 0x0000556795293417 n/a (weston)
                                                 #14 0x00007fc410656f4a __libc_start_main (libc.so.6)
                                                 #15 0x00005567952939ba _start (weston)
Comment 6 GitLab Migration User 2018-06-08 23:55:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/88.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.