Bug 1779522

Summary: [abrt] volumeicon: g_log_structured_standard(): volumeicon killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Clemens Eisserer <linuxhippy>
Component: volumeiconAssignee: Raphael Groner <projects.rg>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: christoph.wickert, projects.rg
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1e7157576e04832735b01aae01204b5cd23984f4
Whiteboard: abrt_hash:45788541514e6c6aac5e5ebbbcd779bca1d8dc66;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-07 10:07:39 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
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: xsession_errors none

Description Clemens Eisserer 2019-12-04 06:43:54 UTC
Description of problem:
crash right after logging into kde

Version-Release number of selected component:
volumeicon-0.5.1-5.fc31

Additional info:
reporter:       libreport-2.11.3
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/bin/volumeicon
crash_function: g_log_structured_standard
executable:     /usr/bin/volumeicon
journald_cursor: s=19f89b6abbf94b299828810d56328c08;i=45c9;b=03f5df9ba8274210a8e08d7bc2d586ec;m=1c97432;t=598daf9826828;x=c4ab9cb2685f1772
kernel:         5.3.13-300.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Clemens Eisserer 2019-12-04 06:43:58 UTC
Created attachment 1641900 [details]
File: backtrace

Comment 2 Clemens Eisserer 2019-12-04 06:44:00 UTC
Created attachment 1641901 [details]
File: core_backtrace

Comment 3 Clemens Eisserer 2019-12-04 06:44:01 UTC
Created attachment 1641902 [details]
File: cpuinfo

Comment 4 Clemens Eisserer 2019-12-04 06:44:03 UTC
Created attachment 1641903 [details]
File: dso_list

Comment 5 Clemens Eisserer 2019-12-04 06:44:04 UTC
Created attachment 1641904 [details]
File: environ

Comment 6 Clemens Eisserer 2019-12-04 06:44:06 UTC
Created attachment 1641905 [details]
File: limits

Comment 7 Clemens Eisserer 2019-12-04 06:44:08 UTC
Created attachment 1641906 [details]
File: maps

Comment 8 Clemens Eisserer 2019-12-04 06:44:09 UTC
Created attachment 1641907 [details]
File: mountinfo

Comment 9 Clemens Eisserer 2019-12-04 06:44:10 UTC
Created attachment 1641908 [details]
File: open_fds

Comment 10 Clemens Eisserer 2019-12-04 06:44:12 UTC
Created attachment 1641909 [details]
File: proc_pid_status

Comment 11 Clemens Eisserer 2019-12-04 06:44:13 UTC
Created attachment 1641910 [details]
File: xsession_errors

Comment 12 Clemens Eisserer 2019-12-04 15:11:05 UTC
Similar problem has been detected:

crashed again after logging in

reporter:       libreport-2.11.3
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/bin/volumeicon
crash_function: g_log_structured_standard
executable:     /usr/bin/volumeicon
journald_cursor: s=7c9e60d5b3914f178ed569bae872ff0b;i=79b7;b=e79e40736f174309b590125a2e234004;m=1d23b49;t=598e1e3eb740d;x=aeb8664edb0012d0
kernel:         5.3.13-300.fc31.x86_64
package:        volumeicon-0.5.1-5.fc31
reason:         volumeicon killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Raphael Groner 2019-12-04 19:57:05 UTC
Thanks for the report. Upstream doesn't seem to be very active, I wonder if it's worth to request a patch to prevent this crash in future.

Comment 14 Clemens Eisserer 2019-12-05 06:51:15 UTC
I wonder why it starts up at all - I am using KDE and haven't seen the icon in systray until I upgraded f30->f31 via dnf.

Comment 15 Raphael Groner 2019-12-05 18:59:42 UTC
Well, volumeicon was mostly designed to enhance desktops based on Gtk and it sits in your autostart by default. Maybe you've installed several desktop environments. 
You can try to remove the package with dnf remove, does it report about any b0rken dependencies?

Comment 16 Raphael Groner 2019-12-07 10:07:39 UTC
Quite obviously another dup of bug #1695951.

*** This bug has been marked as a duplicate of bug 1695951 ***