You are not logged in.
Question: since this has worked on older versions of Devuan, and since this file did not exist on my current system, does this mean that Devuan or Debian has deliberately made the choice to have this disabled?
Thanks HoaS (again). It works now on an unfrozen system. Waiting for another freeze to see if it works then (I'm assuming it will).
Along the lines of my other recent post about browser crashes, I had a computer freeze-up while browsing the web, and for the first time Alt + SysRq then r e i s u b did not reboot the system. It stayed frozen; had to do a hard shut down. This has now happened more than once. Any idea what why the reboot didn't work?
After playing a handful of youtube videos on Chromium it hasn't crashed at all yet, unlike Vivaldi where I'd get crashes on just about every other video (and sometimes multiple crashes on the same video). FTR, Chromium did crash on me once, but there were no videos playing at the time.
So, I'm guessing there really isn't anything that can be done about this? I'd really prefer using Vivaldi over Chromium for youtube watching.
I thought uBlock Origin did that automatically. Maybe I'm missing something . . .
I think it does. 🤔
Thanks for the link HoaS. I run uBlock Origin in all my browsers . . . is the add-on you linked to still necessary?
In going through Chromium's settings I came across something that looks like a typical "gooble-ism" spyware, the setting Continue running background apps when Chromium is closed in Settings >> Advanced >> System. Anybody have any idea what in the world this is? Why would I want background apps (apparently for Chromium??) to continue running when I close the browser? Of course I unchecked it. Any input on what this is and does would be appreciated.
Try the three vertically-placed dots at the top-right, just underneath the window close button.
Looked all through there. It doesn't look like Chromium has an option for a menu bar, which doesn't surprise me.
![]()
Anyway, so far, no crashes on it; but haven't tested long enough yet to my satisfaction.
If the problem is indeed PM and Vivaldi are using their own libraries, then the first question that comes to my mind is then why didn't I experience so many crashes when I was running Devuan 2.1 (i.e., the Miyo version based on 2.1)?
So are those Steve Pusser's and Vivaldi's own .deb packages, respectively?
They both bundle their own libraries in flagrant violation of Debian policy[1] so I would advise trying a browser from the Devuan repositories instead. The firefox-esr package tends to stay up to date better than chromium so I would (and do) use that. Report back if that also crashes.
If an "official" browser remains stable then perhaps take your chances on the Pale Moon forums. If you do that then please share a link, I have some popcorn ready...
For Vivaldi, yes I use its own .deb packages, for Pale Moon I download the tarball direct off the Pale Moon's site, I don't use Steve's packages. I will download Chromium (I don't like FF lately) for testing purposes (only to test Youtube). Will report back here if I get crashes on it or not.
Note: installed Chromium as I was typing this. How to get a menu bar? I hate it already.
I've been getting a lot of browser crashes. Here's the details. I did not have this problem on Devuan 2, but I have it on Devuan 3, and now on Devuan 4 (this is all via Miyo) since day 1. It happens with both browsers I use. On Pale Moon, it mostly happens when I have a handful of yahoo news tabs opened; yahoo news stories usually have playing video. On Vivaldi, I get crashes when watching youtube videos. So I'm guessing it has something to do with videos being played, along with something that must have changed between Devuan 2 and 3/4. Below are my computer's specs. Any ideas what the problem is and if anything can be done about it?
System:
Kernel: 5.10.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
Desktop: MATE 1.24.1 Distro: Devuan GNU/Linux 4 (chimaera)
Machine:
Type: Desktop System: ASUS product: All Series v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: H81M-C v: Rev X.0x serial: <superuser required>
BIOS: American Megatrends v: 3602 date: 03/26/2018
CPU:
Info: dual core model: Intel Pentium G3220 bits: 64 type: MCP arch: Haswell
rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2993 min/max: 800/3000 cores: 1: 2993 2: 2993
bogomips: 11972
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0
Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting
unloaded: fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (HSW GT1) v: 4.5 Mesa 20.3.5
direct render: Yes
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.10.0-11-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Sound Server-3: PipeWire v: 0.3.19 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK H81M-C driver: r8169 v: kernel port: e000 bus-ID: 03:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 387.53 GiB used: 90.54 GiB (23.4%)
ID-1: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB
ID-2: /dev/sdb vendor: Seagate model: ST3160815AS size: 149.05 GiB
Partition:
ID-1: / size: 233.66 GiB used: 5.9 GiB (2.5%) fs: ext4 dev: /dev/sda5
Swap:
ID-1: swap-1 type: file size: 256 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
Info:
Processes: 154 Uptime: 5h 24m Memory: 3.71 GiB used: 1.59 GiB (43.0%)
Init: SysVinit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1597
Shell: Bash v: 5.1.4 inxi: 3.3.12Thanks MiyoLinux. That's got everything working as it should.
Hi Miyo, I installed your new upload of Miyo and the bootup works great. But one problem I'm having is this: to fix the major screen tearing I get in my browser, I always edit the compton.conf file from this:
backend = "xrender";
#backend = "glx";to this:
#backend = "xrender";
backend = "glx";However for some reason, this time this file doesn't exist. What can I do? (Yes I deleted picon and installed compton. Was that a mistake?)
Okay then. But the system should reflect that, like it did for ascii.
So then am I to assume that I really am on 3.1?
I have installed the Miyo version based on beowulf. When I hover over the start menu button on the panel, the pop-up says Devuan GNU/Linux 3 (beowulf). An inxi report also says version 3. However, this page here says the current version of beowulf is 3.1. When I was on ascii the pop-up would say 2.1 for ascii. According to Synaptic I'm up to date. So why isn't my system being upgraded to beowulf 3.1?
Once again, HoaS for the win! Thanks.
Both versions will play the sound file until it ends (or until the script/command is interrupted with <ctrl>+c).
I'm sorry, I wasn't clear. What I want is for it to repeat the sound file until I tell it to stop repeating.
Thanks to all who answered. I have a question for using both Kelsoo's and HoaS's answer:
For Kelsoo's simple command: sleep 300 ; mplayer loud-song.ogg
is there a way to set it so that mplayer continues to play the sound file, until I tell it to stop?
For HoaS's script, same question.
I assume this is a terminal command? What does "sleep" do? I don't want my computer to go to sleep.
I used to use an app called Alarm-clock-applet, or something like that. It is not available in the Devuan 3 repos. Can anybody suggest something like it? I just want a simple timer to set that will ring/play an alarm alerting me that time's up. I usually use it when I set water to boil on the stove-top (one time I forgot and boiled away all the water, yikes).
On a related question, I see one potential replacement, gnome-clocks, however it needs avahi-daemon installed. On my list of "things to do" after a fresh OS install is to delete avahi-daemon. I don't have why, just delete it. Is there any reason why having this avahi-daemon is a bad idea? There must have been a reason why I wanted/needed it deleted.
Hi Ron.
I installed Modern on a partition, but I'm not getting a "wait message".
No, I meant on the Mate Miyo version; sorry I wasn't clear about that. I'm not getting any errors or delay with Modern, nor when I had the rolling release (except when I downloaded the buggy updates for the rolling). Sorry for the confusion.
There was one thing I wish I did before I reinstalled Modern. When the boot up process picked up after the message in the image above, the first line said something to the effect of "No longer waiting . . . ." I don't remember if it said what it was waiting for as the text would speed by very fast (I don't think it did). Does this offer any clues as to what could've been the problem?
Use this command to list all UUIDs for your drives:
I'm sorry, earlier today I just reinstalled Miyo Modern/Devuan 3. The login delay was too much for me. And since then have been busy watching (American) football until now.
Ron wrote:I don't understand why it isn't working cause aren't these the kernels from the unstable version 5? Yet I didn't have this problem running that version.
So you don't see the errors with other distributions that use the 5.15 kernel?
No, I didn't get this error while I was running the unstable Miyo/Devuan 5. Version 5 uses the 5.15 kernel, I think. Honestly, I'm thinking of either going back to version 3 (Miyo Modern), or the unstable and make sure this time I'm running apt-listbugs.
On a side note, I want to thank you HoaS . . . you've helped me out a handful of times here on the forums. It is appreciated. ![]()
Thanks HoaS. Unfortunately I still have this problem. I went with the backports, and it installed the 5.14 kernel. I noticed in Synaptic there was a 5.15 kernel and installed that, but still no joy. BTW, I noticed the 5.15 kernel was unsigned, there wasn't a signed one available. Is it bad to use an unsigned kernel? I don't understand why it isn't working cause aren't these the kernels from the unstable version 5? Yet I didn't have this problem running that version.
I guess the only thing now to do is try Liquorix. I assume I need to do the following:
curl 'https://liquorix.net/add-liquorix-repo.sh' | sudo bashand
sudo apt-get install linux-image-liquorix-amd64 linux-headers-liquorix-amd64In the first, I notice an apostrophe before https. I never noticed anything like that before. Is that correct or a typo?