Iggy64

I have resolved this issue , but thought I'd post my results for the possible benefit of anyone else who might run into this issue with Firefox. There is no issue with firefox-esr's audio in PeppermintOS Devuan if you are running PulseAudio. But, if you are keeping things as simple as possible and don't need most of PulseAudio's server functions for you use case, you turn off PulseAudio and get great ALSA sound directly through ALSA. If you need to run multiple concurrent streams, or if you want...

I have several machines all running various Debian/Devuan-based operating systems, including PeppermintOS-Devuan-runit. Although each of these systems has either PipeWire or plain PulseAudio installed, I generally do not use either of these servers, as I have no need for the additional services and have always gotten along very well with good old ALSA. I am a music enthusiast, but have always been extremely with the sound quality and reliability I get from direct-to-ALSA. In PeppermintOS-Daedalus,...

I invested a bit more time on this today and discovered the following: If I make the ~/.xscreensaver file read-only (to keep it from changing), then open the xscreensaver GUI, the .xscreensaver file flips back to read-write and the dpmsQuickOff parameter flips to False. So I decided that opening the GUI somehow causes the Display Power Management parameter to go back to defaults, and you have to remember to reset them before closing it. Even better, I tried not using the GUI altogether. I edited...

I have PeppermintOS Devuan runit running on one laptop and one desktop machine. Both run 24/7, so I have no need for system power management. I also occasionally want to use a screen locker. The xscreensaver provides the screen locker I need. It also provides power management for the display. Therefore I do not need the xfce Power Manager, and have disabled its daemon via the Startup menu. In xscreensaver, I set the display mode to Blank Screen Only, and "Blank After" to 5 minutes. Then, in the Advanced...

Thanks for your input, Peppermint OS! I certainly can understand the thinking that went into setting up the xDaily panel launcher in "automatic" mode. It's great that you responded to the community feedback and made the default behavior benefit the majority of users. I regret that I published my initial confusion on this board before properly examining the code for xDaily. As noted earlier, I had read a couple of publications praising xDaily, and describing its interactive nature. No doubt they were...

Thank you for your very kind and very complete response. I had read some blurbs describing xDaily, and each mentioned that the user would be given option of allowing or declining each group of changes available on one's system. I was simply surprised when I gave it a try (from the panel launcher) and the whole process buzzed by with no interaction whatsoever. Later, when I tried it from the Hub, I got the interaction. That's when I checked the code and saw that the "-i" option can be appended to...

Thank you for your very kind and very complete response. I had read some blurbs describing xDaily, and each mentioned that the user would be given option of allowing or declining each group of changes available on one's system. I was simply surprised when I gave it a try (from the panel launcher) and the whole process buzzed by with no interaction whatsoever. Later, when I tried it from the Hub, I got the interaction. That's when I checked the code and saw that the "-i" option can be appended to...

Oh, well. I grabbed the code from Source Forge and noted the following: ### Our options are going to be # = "full output to the terminal, no stopping." # -i = "interactive" # -q = "interactive but suppressed output" OPTIND="0" for i in _quiet _interactive ; do unset -v $i ; done So I changed the tray launcher command to sudo xDaily -i and now I have interactive mode. Hence, the tray launcher now makes xDaily a useful alternative to package-update-indicator for handling system updates on a regular...