Bug 991765

Created attachment 782461 [details]
File: backtrace

Created attachment 782462 [details]
File: cgroup

Created attachment 782463 [details]
File: core_backtrace

Created attachment 782464 [details]
File: dso_list

Created attachment 782465 [details]
File: environ

Created attachment 782466 [details]
File: limits

Created attachment 782467 [details]
File: maps

Created attachment 782468 [details]
File: open_fds

Created attachment 782469 [details]
File: proc_pid_status

Created attachment 782470 [details]
File: var_log_messages

Crashed immediately after startx from command line

reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /bin/volumeicon
crash_function: __assert_fail_base
executable:     /usr/bin/volumeicon
kernel:         3.10.5-201.fc19.x86_64
package:        volumeicon-0.4.6-3.fc19
reason:         Process /usr/bin/volumeicon was killed by signal 6 (SIGABRT)
runlevel:       N 3
uid:            500

*** Bug 995938 has been marked as a duplicate of this bug. ***

Message popup upon entering fvwm window manager, with stalonetray as the sys tray.

reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/volumeicon
crash_function: __assert_fail_base
executable:     /usr/bin/volumeicon
kernel:         3.10.9-200.fc19.x86_64
package:        volumeicon-0.4.6-3.fc19
reason:         Process /usr/bin/volumeicon was killed by signal 6 (SIGABRT)
runlevel:       N 5
uid:            1000

Also occurs on Fedora 20.

The bug 995938 is not the same as this one. In bug 995938, the crash appears in
asound_set_volume (volume=184) at alsa_backend.c:209 due to assert(volume >= 0 && volume <= 100);
There is a fix for that upstream:
https://github.com/Maato/volumeicon/commit/056e6d003d0d7f8e15e003fed31a4d19f2baac7c

This bug is an assertion in asound_get_volume(): assert(m_elem != NULL);
There is also a fix for that upstream
https://github.com/Maato/volumeicon/commit/395d4d7ea118f917bb090e2cb927a1fef595fe67

Please include the fixes to F20, best take a new snapshot.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

The crashes still happen, on every boot (Fedora 21, openbox, tint2).

I downloaded upstream volumeicon 0.5.0 and updated spec file accordingly to build it. Then I made latest snaphot from volumeicon upstream master to fix crashes.
See the next comment for the patches. Could you please push them to dist-git and make an official build?

Scratch build for Fedora 21:
http://koji.fedoraproject.org/koji/taskinfo?taskID=8784976

Scratch build for rawhide:
http://koji.fedoraproject.org/koji/taskinfo?taskID=8785035

Created attachment 986308 [details]
[PATCH] dist-git patch updating to released volumeicon 0.5.0

Created attachment 986309 [details]
[PATCH] dist-git patch updating latest master - fixing crashes

This path applies on top of the previous patch.

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.