You are not logged in.
I can reproduce this problem in a live session, but not in an installed system that was installed with the desktop-live. Might have to do with the tty-autologin feature in the live isos, or maybe not.
You can use screen instead. It's already installed and it does work in console in the live session.
My script for comparing the package lists is spammed with packages that are different only in architecture. Here's a simper diff showing what mate packages we have. Anything that starts with a + is one that I have and you don't. Anything that starts with - is one you have that I don't. The only one of those is mate-tweak, and when I added it (without Recommends) it didn't fix the problem. Not sure where to go with this now.
$ diff -u mlevd-list my-mate-list | grep "^[\+|\-]mate"
+mate-applet-brisk-menu 0.5.0-9
+mate-applets 1.20.3-2
+mate-applets-common 1.20.3-2
+mate-backgrounds 1.20.0-2
+mate-calc 1.20.3-1
+mate-calc-common 1.20.3-1
+mate-desktop-environment 1.20.0+5
+mate-desktop-environment-core 1.20.0+5
+mate-icon-theme-faenza 1.20.0+dfsg1-2
-mate-polkit:i386 1.20.2-1
+mate-polkit:amd64 1.20.2-1
+mate-screensaver 1.20.3-3
+mate-screensaver-common 1.20.3-3
+mate-system-monitor 1.20.2-1
+mate-system-monitor-common 1.20.2-1
-mate-tweak 18.10.2-1
+mate-themes 3.22.18-1
+mate-user-guide 1.20.2-1
+mate-utils 1.20.2-3
+mate-utils-common 1.20.2-3Note: That vertical bar that we use to pipe the output of one command to another is called a pipe. Or it could mean "OR" when there are two in a row.
I've been testing by adding two image files to directories under /usr/share/backgrounds/ (cosmos and mate/abstract). Then right-click desktop to change background. Neither show up when I navigate to the directory that holds the files I just added.
Next step is to click on the Add button and add those pictures. Then select one and close that window.
Then try to change the bg again, and the added image that I'm not currently using no longer shows up. It's still in the directory, but my desktop has forgotten about it.
update/upgrade did not change it.
I think we need to compare package lists.
dpkg -l | awk '/^ii/ { print $2 " " $3 }' > pkglist-debianDo the same to make pkglist-devuan and compare them. Send them to me and I'll compare them (I have a script to do that).
Yes, I can reproduce this stupid bug in 64-bit beowulf mate. It's not a problem in xfce, because you don't have to "add" a picture in your settings if you copy the file into the folder that holds the other bg images. Xfce shows you all the image files in the selected directory.
Does mate not do this in debian?
Surely a cli mode for deadbeef or audacious needs to happen?Already done and in repo.
-H, --headless
Start in command-line mode; i.e., without any graphical user interface.Ah, I didn't see that. Yeah the actual file is farther down the page. That first screenshot is the output of pacmd list-cards
When I run that command, I get "No PulseAudio daemon running, or not running as a session daemon." So I can't find what the active profile is to put the line in default.pa
ps ax shows that it's running and that the --start option was used, which should make it run as a daemon. That's what the man page says.
There are a bunch of error messages about pulseaudio in the syslog, but they may be related to settings for the screen reader. They're complaining about a run file for user lightdm. I think I should stop here. It may not be a good comparison.
MLEvD, I hope you have better luck. Are you sure you need pulseaudio? Maybe plain alsa would behave better.
Yeah, I'm not seeing an efi directory in mounted installer isos or imaged usb sticks with 3.0.0 or 3.1.0. So I have no idea how that boots.
It does exist in the amd64 desktop-live iso. Could you have put that on the usb?
I had to look up that term to see what it meant. Audacious does gapless playback. I just tested. It went from Mona to Maiden of the Cander Moon without missing a beat. (Quicksilver Messenger Service). And unlike deadbeef (which I like a lot) audacious is in the repo.
It does playlists, but I never bother with them, so I don't know how good or bad they are.
In vbox I usually end up in the efi shell. Exit or Esc gets you out of there to a menu where you can select 'Boot from file' where you can drill down in the efi partition to find grubx64.efi or whatever boot file you're using.
I did a uefi install from usb onto real hardware and it worked like it's supposed to.
In the meantime, can anyone here reproduce this bug? I'm all 32-bit here, can someone try on 64 please?
I can confirm that setting to output only is not saved across reboots. Tested amd64 mate in a qemu virtual machine. This happens to be an install with speech synthesis enabled (screen reader) but that probably doesn't matter.
I can also confirm that /etc/pulse/default.pa does not look anything like the one in the mycomputertips help page.
I don't see any bugs about settings not saved, but there are a couple about crashing mate-volume-control (the Sound Preferences app)
https://bugs.debian.org/cgi-bin/pkgrepo … mate-media
I also poked around in ~/.config/pulse and found 141 binary files. No help there.
Will a simple apt update/upgrade do the job and bring my systems up to 3.1?
Yes. Regular update/upgrade will get you there. We made a new set of isos to include all the updates, so if you install without a network mirror, you will get the new stuff.
I think it means we were successful. The init diversity team made up of devuan and debian developers working together have been around for over a year. You may notice that some debian packages that rely on systemd now rely on systemd or elogind. Every time that happens, that's one less package we have to fork.
Tunapie
I've got it but don't use it much. Here it's working with audacious as a player. I just open tunapie and can select from a huge list of radio stations, sorted by genre if I want.
Looks like it does not include real broadcast radio stations. I tried a few call letters in the search box and got no hits. Even for stations that I know do web streaming. For those, you can put their url in just about any player.
Dear Init Freedom Lovers,
Once again the Veteran Unix Admins salute you on this day commemorating six years since the first Devuan pre-alpha Valentine's Day release in 2015!
Devuan Beowulf 3.1.0 point release installer ISOs, desktop-live, and minimal-live isos are now available. Note that ARM and virtual images are not updated in this release.
## What’s new in this point release
### Installation
The installer now offers a choice of three init systems. runit has been added, along with sysvinit and openrc.
If you would like to select an alternate bootloader (lilo) or exclude non-free firmware, you must select one of the Expert install options.
The recommended default mirror is now deb.devuan.org. If you would like to use a country code mirror, please check the mirror list to see if there is one suitable for your needs.
### Security updates and bug fixes
linux-image-4.19.0-14 Debian 4.19.171-2 (2021-01-30)
firefox-esr 78.7.0esr-1~deb10u1
lightdm 1.26.0-4+devuan1 (fixes bugs related to power buttons and accessibility features)
New package, debian-pulseaudio-config-override corrects problem of pulseaudio being off by default
And many more. (See https://www.debian.org/security/2020/ and https://www.debian.org/security/2021/)
## Documentation
Please read the Release Notes carefully:
https://files.devuan.org/devuan_beowulf … _notes.txt
Beowulf 3.0.0 announcement:
https://www.devuan.org/os/announce/beow … 60120.html
## Download
https://files.devuan.org/devuan_beowulf/
https://www.devuan.org/get-devuan (mirrors)
The latter URL also includes information about the official Devuan package repositories, an ISO selection guide and links to installation guides.
## What about ARM and virtual images?
ARM and Virtual Machine images are provided by the greater Devuan community rather than as part of official releases. Users are being encouraged to build and contribute ARM images for their particular hardware. This will increase the variety of images available and allow the release schedule of the installer ISOs to move forward more quickly.
Images can be built using using arm-sdk and vm-sdk:
https://www.devuan.org/os/distro-kit
Arm-related discussion happens at #devuan-arm (Freenode) and the Dev1Galaxy forum
## Resource Channels
Mailing list: https://mailinglists.dyne.org/cgi-bin/m … stinfo/dng
IRC: #devuan #devuan-dev (Freenode)
Forum: https://dev1galaxy.org
Source code: https://git.devuan.org
Bug tracker: https://bugs.devuan.org
Popularity contest: https://popcon.devuan.org
Package information: https://pkginfo.devuan.org
Press contact: freedom@devuan.org
## Chimaera coming soon
The Devuan development team will now focus on polishing our fourth release, codename “Chimaera”, minor planet no. 623.
## Appreciation
We wish to thank all of you for the incredible support given to this development effort, which continues to make Devuan a useful and reliable base distribution.
To support the Devuan project you can donate at:
https://www.devuan.org/donate (includes financial reports)
or take up one of the tasks listed at:
https://dev1galaxy.org/viewtopic.php?pid=1380#p1380
Happy hacking ;^)
Another solution (new in devuan 3.1.0 point-release.)
Install debian-pulseaudio-config-override
Description: Debian configuration overrides for pulseaudio
You'll get this automatically if you install a desktop environment from the 3.1.0 installer isos.
(task-desktop Recommends debian-pulseaudio-config-override)
I will be playing with it some more for chimaera and will post here with any useful updates.
Another way to make a live iso that tends to be easier is with refractasnapshot. It makes a copy of your installed system and packs it into a bootable live-iso. You could build a system in a VM, and when you get it the way you want it, make the snapshot. It's in the devuan repo.
https://refracta.org/docs/readme.refractasnapshot.txt
Looks like there's a mis-match in the directory name and maybe confusion between a function name and a directory. I see
custom-packages
install-custpackages
install-custdebs
#!/bin/sh
cd custom-packages
dpkg -i *_all.deb *_amd64.deb (*) Chrooting to execute 'install-custpackages' ...
chmod: cannot access '/home/user1/live-sdk/tmp/devuan-amd64-build/bootstrap/install-custpackages': No such file or directoryI have to go out and can't poke around in this right now. My build failed on trying to install firmware. And every time the build fails, I have to reboot my computer. I am not a happy camper right now. Maybe later I'll tar up the version of live-sdk that I'm actually using to build the official isos and you can download it.
One more item: live-sdk is getting a complete re-write. I don't know the current status, but I intend to get in on that effort.
Line 40 of blends/devuan-minimal-live/devuan-minimal-live.blend needs closing quotes on the login/password.
echo "${username}:${userpass} | chpasswd || exit 1echo "${username}:${userpass}" | chpasswd || exit 1Watch out for the arch setting. I found it in live-sdk/config and it's also in my blend config. Both were set to amd64. It does not work in the blend config file. It must be set in live-sdk/config. I just tested that.
I don't have tmp/devuan-amd64-build/bootstrap/ after the build is done. It all gets wrapped up in stage3 and stage4 tarballs. Unpacking the tarballs does not restore the bootstrap dir.
FWIW, I ran this version of the live-sdk yesterday and made a desktop-live iso that works. I'm running a minimal-live build now, after adding the missing quote. Will be back soon with results.
Without a blend, you could adjust the package lists in lib/libdevuansdk/config but you're better off creating a blend. It gives you more control. This is the file:
https://github.com/parazyd/libdevuansdk … 300/config
For the package sets, edit where the sets are defined to add or comment/remove packages, and you can exclude whole sets in the stanza you posted that shows which sets to include by commenting them out.
I'm not sure what commands to use on the version you're running. I've been using an older version to build isos. Changes were made since I last interacted with the git repo (on git.devuan.org). And I've had some trouble using the newer version. However, I can reproduce your error with the new version.
You need to define the arch in your blend config file instead of on the command line. So put
arch="amd64"
or
arch="i386"
in blends/devuan-minimal-live/config
and use these commands (as root):
zsh -f
source sdk
load devuan devuan-minimal-live
build_iso_distOne more thing. If you build for i386 you might want to look in lib/libdevuansdk/zlibs/kernel if you want to change it from plain 686 kernel to the 686-pae kernel.
Here's the one on devuan's git: https://git.devuan.org/devuan-sdk/live-sdk
Just for the records, I'm not trying to sell something that I don't use or that it's completely untested;
Just for the record, I don't use runit, but I'm commited enough to the idea of diversity in the ecosystem that I'm willing to do some testing or make it easy for other to test. Last year I made a live-iso based on devuan beowulf that uses runit so that people could try it. I know there are a few people using runit in devuan.
I made another live-iso based on chimaera (bullseye) but I haven't uploaded it yet. That might happen soon.
About my issues:
Skip to the end to see that it's fixed. I used the advice you gave to xinomilo for haveged.
Longer version:
I switched it back to sysvinit for cron and anacron and managed to get my test script to work.
Then switched it back to runit, commented set -e and added set -x (the latter did nothing) and also set VERBOSE and DEBUG. Then I started cron manually with # /usr/sbin/cron -f
Got the following:
2021-02-11_13:54:02.22150 invoke-run: ERROR -1 in anacron: runscript didn't exit normally
2021-02-11_13:54:02.22156 invoke-run: anacron : run exit code is -1
2021-02-11_13:54:02.22157 invoke-run: anacron stopped
2021-02-11_13:59:00.98343 invoke-run: ERROR -1 in anacron: runscript didn't exit normally
2021-02-11_13:59:00.98348 invoke-run: anacron : run exit code is -1
2021-02-11_13:59:00.98349 invoke-run: anacron stopped
# ps ax | grep runsvdir
1384 ? Ss 0:01 runsvdir -P /etc/service log: ...........................................................................................................................................................................................................................................................................................................................................................................................................
4373 pts/0 S+ 0:00 grep runsvdir
# sylog
Feb 11 13:43:13 chimaera-2 runsv-cron: invoke-run: ERROR -1 in cron: runscript didn't exit normally
Feb 11 13:52:59 chimaera-2 runsv-cron: invoke-run: ERROR -1 in cron: runscript didn't exit normally
Feb 11 13:52:59 chimaera-2 runsv-cron: invoke-run: cron : run exit code is -1
Feb 11 13:52:59 chimaera-2 runsv-cron: invoke-run: cron stopped
Feb 11 13:54:16 chimaera-2 runsv-cron: invoke-run: ERROR -1 in cron: runscript didn't exit normally
Feb 11 13:54:16 chimaera-2 runsv-cron: invoke-run: cron : run exit code is -1
Feb 11 13:54:16 chimaera-2 runsv-cron: invoke-run: cron stoppedSaw your advice to xinomilo and did the same -
- remove the symlinks in /etc/init.d/
- dpkg-divert --remove /etc/init.d/<service>
- sv e cron
# sv status cron
run: cron: (pid 4615) 696s; run: log: (pid 4614) 696sThanks!
This doesn't seem to be working for me, and I can't figure out what I'm doing wrong. I followed the directions in the README and set up cron and then anacron to work with runit. I can't tell whether it's running or not because it looks like I'm getting contradictory information.
Also, I made a test script that dumps the time into a file in user's home and put it in /etc/cron.hourly/. It works when I run it manually but does not run every hour.
sv says they are down but shows the pid and how long they've been running.
root@chimaera-2:/home/user# sv status cron
down: cron: 24s, normally up; run: log: (pid 2038) 24s
root@chimaera-2:/home/user# sv status anacron
down: anacron: 34s, normally up; run: log: (pid 2042) 34sAttempt to bring them up makes no change.
root@chimaera-2:/home/user# sv up anacron
root@chimaera-2:/home/user# sv up cron
root@chimaera-2:/home/user# sv status cron
down: cron: 4s, normally up; run: log: (pid 2038) 59s
root@chimaera-2:/home/user# sv status anacron
down: anacron: 14s, normally up; run: log: (pid 2042) 63s'ps ax' says they are running but pstree does not.
root@chimaera-2:/home/user# ps ax | grep cron
2033 ? Ss 0:00 runsv cron
2034 ? Ss 0:00 runsv anacron
2038 ? S 0:00 logger -p daemon notice -t runsv-cron
2042 ? S 0:00 svlogd -tt /var/log/runit/anacron
├─runsvdir─┬─6*[runsv───getty]
│ ├─runsv─┬─acpid
│ │ └─svlogd
│ ├─runsv─┬─sshd
│ │ └─svlogd
│ ├─runsv───logger
│ └─runsv───svlogdWhat next?
Got an answer in irc:
<parazyd> fsmithred: It's not ready yet. I'm going to get it working in Maemo Leste first, and then continue in ceres to avoid useless builds.
One of the founding fathers of devuan is an astronomer. All our releases are named after minor planets.
https://www.devuan.org/os/releases
1+ for apod. Some of my favorite desktop backgrounds come from there.
Oh yeah, pmount. Try this -
https://sourceforge.net/projects/refrac … nt-1.2.deb
It works for removable USB, CD and mmc devices. Add any fixed drives to /etc/pmount.allow.
Maybe you can do something with these.
From refractainstaller. This lists partitions. It does not differentiate between encrypted and non-encrypted. Using blkid would be one way to find the encrypted partitions.
find /dev -mindepth 1 -maxdepth 1 | egrep "*[shv]d[a-z][1-99]|*nvme[0-9]n[0-9]p[1-99]|*mmcblk[0-9]p[1-99]" | sort | awk '{print "\n" $0 }'Same thing with a graphical interface (yad)
device=$(find /dev -mindepth 1 -maxdepth 1 | egrep "*[shv]d[a-z][1-99]|*nvme[0-9]n[0-9]p[1-99]|*mmcblk[0-9]p[1-99]" \
| sort | awk '{print "\n" $0 }' \
| yad --list --title="Select device" --center --borders=10 --text="Select a device." \
--separator="" --column ' ' --column$'Partitions' --height=380 --width=200 --button="OK":0)From refracta2usb. These list usb devices.
usbdevlist=$(/usr/sbin/hwinfo --usb --short|grep "/dev/sd"|awk '{print $1}')
usbdevfulllist=$(/usr/sbin/hwinfo --usb --short|grep "/dev/sd"|awk '{print $0}')And used with yad.
device=$(yad --width=400 --height=200 --center --title="$TITLE" --list --separator="" --column="" --text=$"Detected USB devices:\n\n$usbdevfulllist\n\nSelect the target device you want to copy the live image to." $usbdevlist \
--button="OK":0 --button="Exit":1I had to alter some of these so they would make sense. I hope I didn't break anything.