Description of problem: When I add the volume control in the lxpanel, the setting is not remembered at the next session (no volume icon). I did not have this problem with F-14. I have tried with 2 different notebooks running F-15, and it is the same. When I log-back, the volume icon is gone. (the only "change" in the panel, if it is relevant, was to increase the icon size from (default) 24 to 25 pixels.) Version-Release number of selected component (if applicable): lxpanel 0.5.6 How reproducible: always Steps to Reproduce: 1. set the icon size in lxpanel 24 > 25 (the volume icon change not only in size, but in design--I like it better this way). 2. add volume control to panel 3. switch off and boot again, the volume icon in the panel is gone. Actual results: Expected results: setting is remembered Additional info: it's a small annoyance. would you mind explaining me how to make the setting permanent. Thank you.
added: I have just realized that in "Add/Remove panel items", i.e. when I click the "Add/Remove panel items" and it opens the Panel Preferences, I have 6 lines with the same text "Volume panel control". These are all the times I re-added the volume control in the panel. This must be a bug.
I edited the title. Definitively a bug. Changing the icon size back to the default, or moving its place on the bar has the same effect. the icon is always gone at the next session, but the volume control is present in the panel preference. Waiting for feedback now. Thanks.
I can confirm the bug. The mixer is still in the panel config but not visible. I don't have a solution ATM. My suggestion is to install pnmixer, a new package I recently imported into Fedora and that I'm planning to have in the Fedora 16 LXDE spin. It has more features then lxpanel's mixer plugin - but still, this is just a workaround.
Thank you, I will install pnmixer. Do I need to remove the lxpanel's mixer plugin before (or after), and what is the correct command synthax to remove it: # yum remove (?)
The mixer plugin is part of lxpanel, there is nothing to uninstall, you only can remove it in the panel's preferences.
I have installed pnmixer I don't know how to run it or to install it in the lxpanel. It crashes the panel when I run (bash): $ pnmixer& msg: (pnmixer:5911): Gdk-CRITICAL **: IA__gdk_window_get_root_coords: assertion `GDK_IS_WINDOW (window)' failed What am I doing wrong? And how can I include it in the panel (if I need to edit a config file, can you give me the full path of the file to edit and the lines to copy and past, thank in advance).
Just log in again, it will be started automatically.
Can we discuss it on the bug report, because it does not start automatically as you say. I have installed pnmixer. It fails when I launch it from the shell, but it works when I Alt+F2 and type pnmixer; only then I have a volume icon in the tray but I have to run Alt+F2 each time I log-in.
I am sorry, it does. I just did not know pnmixer was supplanting the default volume control, and all I had to do was to re-enable the same volume control in the panel. thanks
well, I have to add another comment. when I switch on, there is NO pnmixer icon volume in the taskbar. Even though pnmixer option is checked in Desktop session control. I have to "Alt+F2" to launch pnmixer. however, If I log-out and log-back (switch on + log-off + log-in), only then, the pnmixer icon is in the tray...? Is there a way to start pnmixer straight when I switch on?
I'm afraid this is caused by a problem with pulseaudio. Can you please edit /etc/xdg/lxsession/LXDE/autostart and remove the line which starts pulseadio? Repeat the same for ~/.config/lxsession/LXDE/autostart (if present). I guess this will also fix the problem with the mixer plugin of lxpanel that we discussed here initially.
(In reply to comment #11) > I'm afraid this is caused by a problem with pulseaudio. > > Can you please edit /etc/xdg/lxsession/LXDE/autostart and remove the line which > starts pulseadio? Thank you. Removing pulseaudio line in autostart fixed the problem.
OK, then this is basically the same problem we are dealing with in bug 713292. I will issue an update soon. *** This bug has been marked as a duplicate of bug 713292 ***