Description of problem: This problem has been appearing for several years... there are several outstanding bug reports AND updates for this problem. Again, I had just rebooted this system and issued a startx command. KDE was in the process of initalizing itself when this abort occurred. Version-Release number of selected component: volumeicon-0.5.1-3.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 3 cmdline: /usr/bin/volumeicon crash_function: g_log_structured_standard executable: /usr/bin/volumeicon journald_cursor: s=e4b2e897d758488999f3f4e20a26ded0;i=1235093;b=72935fa6fb554f548e3e2163982c0bb4;m=e93fdf81e;t=585a68ddd159f;x=6e818cbdbf205bc8 kernel: 5.1.0-0.rc3.git0.1.fc31.x86_64 rootdir: / runlevel: N 3 type: CCpp uid: 0
Created attachment 1551604 [details] File: backtrace
Created attachment 1551605 [details] File: cgroup
Created attachment 1551606 [details] File: core_backtrace
Created attachment 1551607 [details] File: cpuinfo
Created attachment 1551608 [details] File: dso_list
Created attachment 1551609 [details] File: environ
Created attachment 1551610 [details] File: limits
Created attachment 1551611 [details] File: maps
Created attachment 1551612 [details] File: mountinfo
Created attachment 1551613 [details] File: open_fds
Created attachment 1551614 [details] File: proc_pid_status
Thanks for your report. > This problem has been appearing for several years... there are several > outstanding bug reports AND updates for this problem Can you provide some reference? A quick look into the provided backtrace lets me assume a memory leak somewhere. But it's hard to reproduce and this backtrace is not much useful.
Raphael, Thanks for your response. I don't know what's causing this problem. It always seems to happen right after a reboot and manual start of kde. George...
Well, I guess KDE is not compatible or not supported by upstream. We may consider to forward this bug to upstream. Can you create another report for upstream or should I do?
Raphael, I don't get much cooperation from the KDE folks so I would ask you to do the report if you would please? Best regards, George...
Done: https://github.com/Maato/volumeicon/issues/74 Let's cross fingers and hope they can provide a fix.
Raphael, Good work! Thanks for your help. George...
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
*** Bug 1701599 has been marked as a duplicate of this bug. ***
Pinged upstream.
*** Bug 1779522 has been marked as a duplicate of this bug. ***
No release from upstream since 2017, I tend to orphan this package. https://github.com/Maato/volumeicon/issues/69
Similar problem has been detected: crash right after start reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: /usr/bin/volumeicon crash_function: g_log_structured_standard executable: /usr/bin/volumeicon journald_cursor: s=7c7ec704d23049148f342c78cb5d8874;i=40860;b=ffdd52102e614e8f903fb665653c8bc1;m=269c1b5;t=59dacb3e8ce38;x=4fa1363a20fdd908 kernel: 5.4.15-200.fc31.x86_64 package: volumeicon-0.5.1-5.fc31 reason: volumeicon killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1657564 [details] File: backtrace
Similar problem has been detected: right after login reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: /usr/bin/volumeicon crash_function: g_log_structured_standard executable: /usr/bin/volumeicon journald_cursor: s=10b81e878d4048a280f0ee13ec5c9abc;i=c82a;b=d66f220bfae04ee39208dafc054f2344;m=2a3f987;t=59e1170fc1b5d;x=1ff7fdc74e587d90 kernel: 5.4.15-200.fc31.x86_64 package: volumeicon-0.5.1-5.fc31 reason: volumeicon killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1805211 has been marked as a duplicate of this bug. ***
Similar problem has been detected: crashed right after logging in. I've manually uninstalled volumeicon, but somehow this thing got installed again (dependency) and is now crashing again. reporter: libreport-2.12.0 backtrace_rating: 4 cmdline: /usr/bin/volumeicon crash_function: g_log_structured_standard executable: /usr/bin/volumeicon journald_cursor: s=4c2069881dc942afbc9b3142c73206d6;i=1d3a;b=78826c44ef3e4e969bfc75b3cb7a6fcd;m=474d95d;t=5a1c4fef1f13b;x=f3f025144d7ebd6c kernel: 5.5.10-200.fc31.x86_64 package: volumeicon-0.5.1-5.fc31 reason: volumeicon killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Nasty. Could you try to give the output of the following command to look for any dependencies? Do you have enabled weak dependencies? $ dnf repoquery --whatrequires volumeicon
Similar problem has been detected: again, right after logging in it crashed ... again reporter: libreport-2.12.0 backtrace_rating: 4 cmdline: /usr/bin/volumeicon crash_function: g_log_structured_standard executable: /usr/bin/volumeicon journald_cursor: s=4c2069881dc942afbc9b3142c73206d6;i=d9a6;b=e8483327a2d64ef992517d3866292d7d;m=1d226a9;t=5a1e89fe143c3;x=d8d0a325276c0719 kernel: 5.5.10-200.fc31.x86_64 package: volumeicon-0.5.1-5.fc31 reason: volumeicon killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Can you please answer my questions in comment #29. You may keep in mind this package has no official support for KDE/Plasma. (In reply to Raphael Groner from comment #29) > Nasty. Could you try to give the output of the following command to look for > any dependencies? Do you have enabled weak dependencies? > > $ dnf repoquery --whatrequires volumeicon You could also try to add volumeicon into dnf's blacklist of unwanted packages to install.
Ralph, My system is now FC33, volumeicon is volumeicon-0.5.1-6.fc32.x86_64 but I'm running windowmaker and so have not seen the problem. I could try to startup KDE and see what happens if that'd help. Regards and sorry for the delay in responding, George...
I got no results from the above dnf command.
(In reply to George R. Goffe from comment #33) > I got no results from the above dnf command. Since there are no similiar issues reported since some time I'm going to close here. Please feel free to reopen if there's still an issue.
Hi Raphael, I just ran "dnf update" and here it was again - volumeicon got installed, despite I removed it so many times before (as weak dependency). I wonder - why are weak dependencies even installed for updates? ========================================================================================================================================== Package Architecture Version Repository Size ========================================================================================================================================== Aktualisieren: containernetworking-plugins x86_64 0.8.7-1.fc32 updates 11 M hwdata noarch 0.339-1.fc32 updates 1.4 M icewm x86_64 1.8.0-1.fc32 updates 1.2 M icewm-3rd-party-cfg noarch 1.8.0-1.fc32 updates 15 k icewm-data noarch 1.8.0-1.fc32 updates 451 k icewm-fonts-settings noarch 1.8.0-1.fc32 updates 9.7 k icewm-themes noarch 1.8.0-1.fc32 updates 2.1 M icewm-wallpaper noarch 1.8.0-1.fc32 updates 16 M mercurial-lang x86_64 5.2-5.fc32 updates 1.0 M mercurial-py2 x86_64 5.2-5.fc32 updates 3.9 M pinta x86_64 1.7-2.fc32 updates 882 k Schwache Abhängigkeiten werden installiert: volumeicon x86_64 0.5.1-6.fc32 fedora 73 k Transaktionsübersicht ========================================================================================================================================== Installieren 1 Paket Aktualisieren 11 Pakete
No idea about icewm package. Maybe it has strange dependencies.
Forwarding to maintainer of icewm, why is volumeicon added as weak dependency as noted in comment #35? https://src.fedoraproject.org/rpms/icewm/blame/icewm.spec?identifier=rawhide#_90 https://src.fedoraproject.org/rpms/icewm/c/d90990b6569e196c454188ff515d87a6e6f11a3f As a work around, dnf can generally ignore weak dependencies by configuration. But that can't be a preferable fix here.
(In reply to Raphael Groner from comment #37) > Forwarding to maintainer of icewm, why is volumeicon added as weak > dependency as noted in comment #35? > https://src.fedoraproject.org/rpms/icewm/blame/icewm. > spec?identifier=rawhide#_90 > https://src.fedoraproject.org/rpms/icewm/c/ > d90990b6569e196c454188ff515d87a6e6f11a3f > > As a work around, dnf can generally ignore weak dependencies by > configuration. But that can't be a preferable fix here. Hello. Sorry, this is terrible. I've for the first time see this bug report. Added because of this https://src.fedoraproject.org/rpms/icewm/blob/rawhide/f/icewm.spec#_1 Quote: # Note: there is always trade off between build IceWM more like full DE or vanilla build. One group of people ask for first one and pre-configured out of box another one for for second. Some people even asked for IceWM spin with preinstalled apps and look and feel close to antiX. But there is no such issue on GNOME and i testing regularly every IceWM update. If upstream can't fix for KDE only what i can do is to remove it at all as dependency. The update with fix on the way.
Sorry for the delay to report this crash and thanks for your fast response. Personally, I'll vote for a separate spin if icewm chosen for a full desktop to not kid users with individual preference. Maybe volumeicon could be at least a soft weak dependency and you can change Recommends: into Suggests: instead to smooth it to a better update process as originally seen by reporter?
> change Recommends: into Suggests: instead Yep. Already building. Also i agree that we should build vanilla or almost vanilla IceWM. Now i just don't know how to do this better and need your advise: incrementally drop deps or at once. Maybe need this wider discussion since opinions very differs here.
Thanks. This issue is about volumeicon, especially. Discussion generelly about a spin is not topic for this bug. You may ask for help from FESCo and follow the policy with a request as a System-Wide Change for further distribution releases. https://docs.fedoraproject.org/de/fesco/Spins/
FEDORA-2021-d200d08e9d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d200d08e9d
Since upstream did not respond so far to my reported issue #74 neither provides any new release requested several years ago in issue #69, I'd tend to orphan volumeicon package, unfortunately. It's a lovely relict from those times with actively maintained LXDE spin based originally on Gtk2.
In case of a possible spin idea, you could look into OpenSUSE's desktop configuration, they provide a nice and minimal installation template with icewm. But as said, I'm not the right person to discuss that with.
Additionally, please notice there's currently no upstream support for wayland. https://github.com/Maato/volumeicon/issues/79
FEDORA-2021-ab24be4967 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ab24be4967
FEDORA-2021-98f191ab89 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-98f191ab89
(In reply to Raphael Groner from comment #43) Well, agree. :) I don't know alternative for volumeicon but its time has come probably.
FEDORA-2021-d200d08e9d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d200d08e9d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d200d08e9d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-ab24be4967 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-98f191ab89 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-98f191ab89` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-98f191ab89 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-98f191ab89 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-d200d08e9d has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.