Ever since I installed Stacer the volume control stopped working. I uninstalled Stacer and the volume control still doesn't respond to the keyboard. I have to use the mouse in order to adjust the volume. I have "Enable keyboard shortcuts for volume control" checked.I also tried this and it didn't work. https://unix.stackexchange.com/quest...e-keys-in-xfce Anyone know how to fix it?

It's a long shot but did you completely purge Stacer rather than just removing it?

I don't know what you mean by purge. I just removed it.

(replace stacer with the actual name of the package).

It was just a thought that some of stacer's system config files may remain, and one of them may be causing the issue. The problem is that even purging a package doesn't get rid of all the changes that installing a package makes, e.g. personal config files and any changes made to config files that are also used by other packages. Effectively the only way to cleanly return to your pre-stacer days is to revert to a previous system snapshot/backup/image that you made before you installed it. However, hopefully even if the purge doesn't work, you can find out what it has changed (have a look at stacer's installation and removal scripts for clues).

Thanks. That means I would have to re-install MX Linux. :| As for scripts, I was never able to understand any scripts.

Don't reinstall it yet. Try the purge, search the web, and wait to see if anyone on here comes up with answers. Also try the MX Linux forums.

O.K. Will do. Someone on the Xfce forum is on to something. It looks like Stacer removed some unknown commands in the kerboard application shortcuts.

Good stuff. Let us know how it goes.

Will do. So far Stacer has proven that it's Malware because it delete "amixer -D pulse sset Master 3%+ unmute" and "amixer -D pulse sset Master 3%- unmute" from the keyboard shortcuts without my permission. It accepted each key I pressed setting those shortcuts so the keyboard is good. It still doesn't work after restoring those commands and rebooting.

Update. It looks like Stacer is definitely Malware! Somehow it was able to change file permissions. I changed them all back. Keyboard volume control still doesn't work. I have to wait for someone elses help.

A bug report here - https://github.com/oguzhaninan/Stacer/issues - might be in order.

Fixed the problem. I compared everything from my Laptop with my Desktop. I deleted all the garbage left behind from that Malware Stacer. Then deleted two shortcuts in the keyboard shortcuts which were recommended that I install from an other forum. Then re-added checks on the sound icon and it started working fine. Looks like Sourceforge can no longer be trusted when they have applications that can botch a distro. The other sad thing is one of the MX Linux developers responded with a wiseguy comment on the Xfce forum "You have it on ours, for instance: are you actually running MX Linux?" This wiseguy knows very well who I am and what Linux distro I am using. I look at it as a learning experience with Linux and I will search for another distro that has good support which MX Linux used to have but no longer since the quality of support has taken a nose dive ever since they hit #1 on Distrowatch. Thank you for all for trying.

I'm glad you resolved the issue. Comparison against a fresh install/profile is often a good recovery technique.

I don't get your comments about Sourceforge though. Stacer appears to have changed system settings that in retrospect it shouldn't have, but it isn't malware, imo, just software that, from the evidence you've given, appears to not have fully considered the consequences of its actions on a system like yours. How are Sourceforge supposed to know about and react against that? - they can't analyse all the code that they host. I know that you disagree with this, but it's always "caveat emptor" when it comes to software, I'm afraid. By all means stay clear of Stacer, but don't tar all software hosted on Sourceforge with the same brush (and I say that with no connection to Sourceforge at all, in fact I have no idea if I run any software hosted there).

2 members found this post helpful.

I am not saying all software is bad on Sourceforge but when Sourceforge has software that does that much damage to a system it should be removed because otherwise Sourceforge looses all credibility. Other software hosting sites have a way of determining if software is harmful. What I don't understand is all this complacency in the Linux community when something is bad, they make all kinds of excuses rather than admit the fact it's bad.

Yes, but there's bad and there's BAD. Any software repository worth its salt scans the software it hosts for viruses, rootkits, worms and other known malware. But it can't scan for software that doesn't do its job properly. With only the limited knowledge of the situation that I have, it looks as if the software in question changed some common configurations/settings in order to do its job, but didn't reset certain settings when it was uninstalled. Software is always conservative about this - who knows what other software has also played about with those settings in the meantime, and changing those settings back to what the software remembers they were before it started operating may in fact act to the detriment of other software. It really is a minefield.

I still advise you to post an Issue on Stacer's GitHub page. They need to be made aware that you've experienced these problems and see if they can resolve the issue. If you can remember the changes you made to resolve the situation, all the better. We all need to work together to help developers improve their software.

And, of course, I'm sorry you faced this issue at all. You worked it out though, without reinstalling, and that's important.

1 members found this post helpful.

Yes, but there's bad and there's BAD. Any software repository worth its salt scans the software it hosts for viruses, rootkits, worms and other known malware. But it can't scan for software that doesn't do its job properly. With only the limited knowledge of the situation that I have, it looks as if the software in question changed some common configurations/settings in order to do its job, but didn't reset certain settings when it was uninstalled. Software is always conservative about this - who knows what other software has also played about with those settings in the meantime, and changing those settings back to what the software remembers they were before it started operating may in fact act to the detriment of other software. It really is a minefield.

I still advise you to post an Issue on Stacer's GitHub page. They need to be made aware that you've experienced these problems and see if they can resolve the issue. If you can remember the changes you made to resolve the situation, all the better. We all need to work together to help developers improve their software.

And, of course, I'm sorry you faced this issue at all. You worked it out though, without reinstalling, and that's important.

1 members found this post helpful.