Description of problem: Immediately after upgrading from Fedora 28 to 29, gkrellm crashes immediately after starting. Version-Release number of selected component: gkrellm-2.3.10-6.fc29 Additional info: reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: gkrellm crash_function: gdk_display_sync executable: /usr/bin/gkrellm journald_cursor: s=8098ad5cab044edabb3eb8da647686f4;i=af71;b=a76499fdbed046189978677c5a254146;m=4174c0e1;t=581048afcfb00;x=eeb2e71305b8f45a kernel: 4.20.5-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #10 gdk_display_sync at gdkdisplay-x11.c:727 #11 gdk_x11_drawable_get_xid at gdkdrawable-x11.c:937 #12 gkrellm_winop_draw_rootpixmap_onto_transparent_chart at winops-x11.c:550 #13 gkrellm_winop_apply_rootpixmap_transparency at winops-x11.c:742 #14 gkrellm_build at main.c:1941 #15 cb_load_theme at gui.c:1780 #20 _gtk_action_emit_activate at gtkaction.c:795 #25 gtk_widget_activate at gtkwidget.c:5048 #26 gtk_menu_shell_activate_item at gtkmenushell.c:1305 #27 gtk_menu_shell_button_release at gtkmenushell.c:730
Created attachment 1526520 [details] File: backtrace
Created attachment 1526521 [details] File: cgroup
Created attachment 1526522 [details] File: core_backtrace
Created attachment 1526523 [details] File: cpuinfo
Created attachment 1526524 [details] File: dso_list
Created attachment 1526525 [details] File: environ
Created attachment 1526526 [details] File: limits
Created attachment 1526527 [details] File: maps
Created attachment 1526528 [details] File: mountinfo
Created attachment 1526529 [details] File: open_fds
Created attachment 1526530 [details] File: proc_pid_status
gkrellm has a history of BadPixmap problems dating back >10 years (you can search for gkrellm badpixmap). I do see this problem occasionally but I have run gkrellm on all of my machines for many years including on F28, F29, F30 and it works reasonably well. What desktop environment are you running?
It looks like you are running under XFCE. There are several other bugs under XFCE as well. I'll look into this.
*** Bug 1647697 has been marked as a duplicate of this bug. ***
*** Bug 1648979 has been marked as a duplicate of this bug. ***
Yes, I'm using XFCE.
*** Bug 1655228 has been marked as a duplicate of this bug. ***
I am reassigning this to xfwm4 since the code is very old in gkrellm and the code in xfwm4 is very new. As a workaround in gkrellm, you can change your theme variant to not use transparency. xfwm4 recently changed to enable the root pixmap by default in https://bugzilla.xfce.org/show_bug.cgi?id=15709 This appears to break gkrellm when it is trying to read the root pixmap to simulate transparency (an old trick). When a transparent theme is used and the root window has a pixmap, XSetTile is called with the root window pixmap. This generally works, but does not work with xfwm4.
*** Bug 1745191 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Adam: Since you understand the issue would you be willing to file it upstream?
Yes let me try to remember the details and I'll file an upstream bug if I can still reproduce the crash.
Yes it still reproduces.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It seems that a fix for this was merged upstream about 2 months ago: https://gitlab.xfce.org/xfce/xfdesktop/-/issues/62 Can someone from Fedora confirm which release(s) includes the fix?
Will definitely be in f34 (xfce 4.16).
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Definitely not fixed in F34. Still crashes 100% of the time. For a bug that I reported nearly *3* years ago, this is kinda ridiculous.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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.
Four years, and still unfixed.
Can you try this scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=87092379
Good news and bad news: Good news is that the scratch build does prevent gkrellm from crashing when using a transparent theme. The bad news is that transparency is broken, and instead is replaced with a gray color in gkrellm.
:( well, I can push this change if you like (I suppose broken transparency is better than a crash?) or you could open a new bug upstream and see if that part of it could get fixed as well (or I can, but I don't use gkrellm, so not sure I would explain things correctly). Or I suppose we could reopen the old upstream one?
Please push the change. I agree that eliminating instability is better than nothing.
As long as only gkrellm transparency is broken, I have no issues with pushing the fix.
I didn't notice any other regressions in XFCE.
FEDORA-2022-f76b045905 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f76b045905
FEDORA-2022-f76b045905 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-f76b045905` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f76b045905 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b0d24fd00a has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b0d24fd00a
FEDORA-2022-b0d24fd00a has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b0d24fd00a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b0d24fd00a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-f76b045905 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-b0d24fd00a has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.