Bug 2310864

Summary: gtk4 apps do not paint their window in XFCE
Product: [Fedora] Fedora Reporter: Mike FABIAN <mfabian>
Component: gtk4Assignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 41CC: gnome-sig, klember, mclasen, mcrha, mfabian, rhughes, suraj.ghimire7, tfujiwar
Target Milestone: ---Keywords: Desktop
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-16 17:10:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Video showing gnome-software not starting
none
Screenshot showing that the same problem happens with gtk4-demo
none
It also does not work when using `su -` to become root and then trying to start a gtk4 program none

Description Mike FABIAN 2024-09-09 15:00:39 UTC
When using the XFCE desktop, gnome-software does not start and hangs somewhere.

It works when using the Gnome desktop.

But on XFCE, when typing 

`gnome-software RETURN` 

in a terminal, no window pops up. gnome-software keeps running and therfore one does not get the terminal prompt back. 

There are some error messages or warnings visible in the terminal.


Reproducible: Always

Steps to Reproduce:
Try to start gnome-software from a terminal on the XFCE desktop.

Comment 1 Mike FABIAN 2024-09-09 15:03:21 UTC
Created attachment 2045965 [details]
Video showing gnome-software not starting

This video shows the error messages or warnings appearing in the terminal when trying to start gnome-software.

Comment 2 Mike FABIAN 2024-09-09 15:04:28 UTC
Created attachment 2045966 [details]
Screenshot showing the error messages/warnings in the terminal

Comment 3 Mike FABIAN 2024-09-09 15:06:38 UTC
Attaching with gdb shows this:

```
gdb --pid=3663
...
Downloading separate debug info for system-supplied DSO at 0x7fb52e223000                                                    
[Thread debugging using libthread_db enabled]                                                                                
Using host libthread_db library "/lib64/libthread_db.so.1".
Downloading source file /usr/src/debug/glibc-2.40-3.fc41.x86_64/io/../sysdeps/unix/sysv/linux/ppoll.c
0x00007fb52cd87f70 in __GI_ppoll (fds=fds@entry=0x7fb4d8119180, nfds=nfds@entry=3, timeout=<optimized out>,                  
    timeout@entry=0x7ffc556d1760, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42
42        return SYSCALL_CANCEL (ppoll_time64, fds, nfds, timeout, sigmask,
(gdb) 
```

Comment 4 Milan Crha 2024-09-09 15:13:45 UTC
Thanks fr a bug report. It seems to me the window is there, only not painted properly. Could you try for example a `gtk4-demo` application, whether it'll be affected in a similar way, please?

I faced something similar in GNOME OS, as reported here: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/878 but it was in the GNOME itself. I cannot tell whether the two are related.

Comment 5 Mike FABIAN 2024-09-09 17:24:21 UTC
Created attachment 2046001 [details]
Screenshot showing that the same problem happens with gtk4-demo

Screenshot showing that the same problem happens with gtk4-demo

Comment 6 Mike FABIAN 2024-09-09 17:26:28 UTC
Yes, same problem with gtk4-demo.

By the way, if I do `ssh -X` to the virtual machine and try to start gnome-software or gtk4-demo with X forwarding via ssh, then it does not work either, a window opens but no contents are drawn. And the terminal shows this error messages:

mfabian@f41:~$ gtk4-demo
libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI3: Screen seems not DRI3 capable
MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen

Comment 7 Mike FABIAN 2024-09-09 17:27:53 UTC
**All** Gtk4 applications seem to have this problem, gnome-text-editor as well.

Comment 8 Milan Crha 2024-09-10 05:34:31 UTC
Thanks for the update. I'm moving this to the gtk4 for further investigation.

Comment 9 Milan Crha 2024-09-10 05:35:56 UTC
Could you provide the gtk4 package version you've installed, please?

Comment 10 Mike FABIAN 2024-09-10 13:07:49 UTC
> Could you provide the gtk4 package version you've installed, please?

mfabian@f41:~$ rpm -q gtk4 
gtk4-4.15.5-3.fc41.x86_64
mfabian@f41:~$ rpm -q gtk4-devel-tools 
gtk4-devel-tools-4.15.5-3.fc41.x86_64
mfabian@f41:~$

Comment 11 Mike FABIAN 2024-09-12 07:57:57 UTC
Created attachment 2046504 [details]
It  also does not work when using `su -` to become root and then trying to start a gtk4 program

It  also does not work when using `su -` to become root and then trying to start a gtk4 program.

Comment 12 fujiwara 2024-09-17 08:27:49 UTC
From https://gitlab.gnome.org/GNOME/gtk/-/issues/6840#note_2206428
The following is the workaround.

env GSK_RENDERER=cairo gnome-text-editor

Comment 13 Mike FABIAN 2024-10-22 13:12:33 UTC
I updated my f41 virtual machine again today.

I can start gtk4 programs on XFCE now, and I can do `ssh -X` to the virtual machine and start a gtk4 program.

But the problem still exists when using `su -` to become root and then trying to start a gtk4 program.

Comment 14 Jens Petersen 2024-10-22 14:53:11 UTC
(In reply to Mike FABIAN from comment #13)
> But the problem still exists when using `su -` to become root and then
> trying to start a gtk4 program.

If that's a regression maybe better to open a separate bug for that.

I think the main issue is fixed so it would be reasonable to close this issue already.

Comment 15 Adam Williamson 2025-12-02 01:16:53 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 16 Samyak Jain (RedHat) 2025-12-16 17:10:10 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.