Hide Forgot
Description of problem: In the plugin options page I activated the first one (I believe it was gkrlemtop), and crashed. After this, it won't start again. I have had the moon plugin running for a long time. Version-Release number of selected component: gkrellm-2.3.7-2.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: gkrellm crash_function: _g_log_abort executable: /usr/bin/gkrellm global_pid: 7174 kernel: 4.8.8-200.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:325 #7 XGetGeometry at GetGeom.c:47 #8 gkrellm_winop_apply_rootpixmap_transparency at winops-x11.c:723 #9 gkrellm_build at main.c:1941 #10 enable_plugin at plugins.c:1038 #11 cb_enable_plugin at plugins.c:1633 #12 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794 #13 _g_closure_invoke_va at gclosure.c:867 #16 gtk_cell_renderer_toggle_activate at gtkcellrenderertoggle.c:407 #17 gtk_tree_view_column_cell_process_action at gtktreeviewcolumn.c:2913
Created attachment 1227407 [details] File: backtrace
Created attachment 1227408 [details] File: cgroup
Created attachment 1227409 [details] File: core_backtrace
Created attachment 1227410 [details] File: dso_list
Created attachment 1227411 [details] File: environ
Created attachment 1227412 [details] File: limits
Created attachment 1227413 [details] File: maps
Created attachment 1227414 [details] File: mountinfo
Created attachment 1227415 [details] File: namespaces
Created attachment 1227416 [details] File: open_fds
Created attachment 1227417 [details] File: proc_pid_status
Created attachment 1227418 [details] File: var_log_messages
Hi, Thanks for the bug report. We've seen this bug before, but I've never been able to reproduce it. What desktop environment / window manager are you using ? Also can you describe this bit: "In the plugin options page I activated the first one (I believe it was gkrlemtop), and crashed. After this, it won't start again." In a bit more detail ? Try "rm ~/.gkrellm2/user-config" and then see if you can reproduce. If we can get a reliable reproducer for this bug then that would be great. Regards, Hans
I am using LXDE. Upon resetting the .gkrlemlm2 folder I managed to get it running again. I have three plugins installed: gkrellm-gkfreq, gkrelltop, and moon clock. I was for sure using the later two, and I think the first one was desactivated. When I activated it last Friday, the crash happened. Unfortunately, I can no longer reproduce the crash. gkfreq is running, even though my settings are, as far as I know, the same as on Friday. I did update the kernel.
(In reply to David from comment #14) > Unfortunately, I can no longer reproduce the crash. gkfreq is running, even > though my settings are, as far as I know, the same as on Friday. I did > update the kernel. Bummer, are you using the same gkrellm theme as before ? I believe that this crash only happens when using a theme with transparent panes / background.
I always used one of the default variations. I tried now to activate and deactivate all the plugins with all the variations, with no crash. I also tried to deactivate them, set a transparent variation, exit, restart, activate the plugins.
Ok, if you do find a reproducer please let us know.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.