Description of problem: Tried to launch workrave in a GNOME Wayland session. Crashes on launch. Version-Release number of selected component: workrave-1.10.16-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: workrave crash_function: _XSend executable: /usr/bin/workrave global_pid: 7732 kernel: 4.8.1-1.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 _XSend at xcb_io.c:447 #1 XQueryExtension at QuExt.c:47 #2 XInitExtension at InitExt.c:47 #3 XextAddDisplay at extutil.c:110 #4 XScreenSaverQueryExtension at XScrnSaver.c:158 #5 XScreenSaverMonitor::init at XScreenSaverMonitor.cc:71 #6 UnixInputMonitorFactory::get_monitor at UnixInputMonitorFactory.cc:107 #7 ActivityMonitor::ActivityMonitor at ActivityMonitor.cc:76 #8 Core::init_monitor at Core.cc:286 #9 Core::init at Core.cc:171
Created attachment 1210208 [details] File: backtrace
Created attachment 1210209 [details] File: cgroup
Created attachment 1210210 [details] File: core_backtrace
Created attachment 1210211 [details] File: dso_list
Created attachment 1210212 [details] File: environ
Created attachment 1210213 [details] File: exploitable
Created attachment 1210214 [details] File: limits
Created attachment 1210215 [details] File: maps
Created attachment 1210216 [details] File: mountinfo
Created attachment 1210217 [details] File: namespaces
Created attachment 1210218 [details] File: open_fds
Created attachment 1210219 [details] File: proc_pid_status
Created attachment 1210220 [details] File: var_log_messages
*** Bug 1357244 has been marked as a duplicate of this bug. ***
Workrave has no Wayland backend; until such time that it has one, it simply won't work thereon.
Non-native apps are generally supposed to work fine with XWayland. Are you saying workrave is somehow special and must be ported to native Wayland in order to work? It can't work with XWayland?
Workrave is not a normal X11 application, it is for "typing-break"s; it needs native access to the windowing system to get input idle times as well as being able to lock out input. Therefore, it requires native support for whatever it's running on, and while it does support multiple backends (Cocoa, Win32, and X11), Wayland is not one of them.
*** Bug 1401833 has been marked as a duplicate of this bug. ***
*** Bug 1468408 has been marked as a duplicate of this bug. ***
*** Bug 1480017 has been marked as a duplicate of this bug. ***