Red Hat Bugzilla – Bug 160395
Unwarranted sound errors on a session startup
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
On a machine without a sound card (yes, such things do exist) on every
start of a gnome-session one is accosted by the following alert:
"No volume control elements and/or devices found". The only possible
reaction to that can be "Doh!". On the top of this there is no timeout
to this alert so it has to be explicitely closed every time.
A naive assumption was that removing gnome-volume-manager from a session
startup would resolve that. This turn out to be false. Also turning
sound off in whatever could be found in preferences did not help.
How to kill that alert, with a zero information content as sound is NOT
configured, is far from obvious if at all possible.
Moreover even if a required hardware would exist if I have a sound
not configured then this is likely because I do _not want_ that box
to make sounds.
Version-Release number of selected component (if applicable):
always - unfortunately
*** Bug 160864 has been marked as a duplicate of this bug. ***
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
> Could you please check ...
The problem is that at this moment I do not have a machine capable
of running gnome-session and which would not have a sound hardware
or even something not on mobo which I could remove. It is clearly
something which can be checked by anybody with an suitable box around
and not necessarily by me.
OTOH whomever "owns" that code could have remove this misguided
alert years ago, or at least provide an option to shut it up, and
close that bug. Obviously it is known at that moment that
"No ... devices found". Seems like a good clue.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)