You are not logged in.
You most likely need a newer kernel. This has come up before and will come up again, so I just made an unofficial ascii desktop-live iso with the ascii-backports 4.19 kernel. You can try this, or you can wait until beowulf is released (or at least a beta).
https://get.refracta.org/files/experime … 5_1512.iso
sha256sum:
6c6bc57e33f48c55e4bcc53cfed14f5001b4f6a3c4f045082adf29def7084bb5 unofficial_devuan_ascii_2.1_bpo_amd64-20191105_1512.isoI don't know if the ascii versions of wireless firmware work with the backports kernel. (Not your issue, but someone else might need them.)
Sorry I didn't respond sooner. I passed the message along and we're working on it. Package dependencies will be adjusted to fix this.
The usual way to downgrade a package after an upgrade is to find the package and its dependencies in /var/cache/apt/archives/ and install them with dpkg --force-downgrade -i <filename.deb filename2.deb...>
If possible, save the console output. There may be clues to diagnose the problem.
<command> | tee mylog
You can run reportbug to get a report, but you need to submit the bug by email. For cryptsetup, you'd need to send it to debian's bug list, but I wouldn't bother. They aren't going to fix it. From the bug report you cited:
There's no easy solution to fix this instead of using a initramfs which
is executed just after root device has been unmounted. To my knowledge,
this is not implemented for sysvinit shutdown process in Debian yet.
Tagging the bug as wontfix for that reason.
A plain i386 iso (not isohybrid) was needed for an old mac mini, but all the devuan images are isohybrid. It's possible to turn an isohybrid file into a plain CD iso. Here's a detailed account of how to do it:
https://n0a110w.github.io/notes/sys-adm … -ISOs.html
Here's a brief description:
- mount the isohybrid
- copy the contents to an empty directory (myiso/ in the example below)
- repack the contents into a new iso file using xorriso:
xorriso -as mkisofs -r -J -joliet-long -rr -l -partition_offset 16 -V test-devuan-live -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -o my-new.iso myiso/There are no devuan cryptsetup devs to shame.
I did get someone else to look at this, and we will probably make a package that replaces the functions file similar to the one that mx/antix uses.
Yes, we removed lxde from the desktop choices in the installer because we couldn't get the 'kits to play nice. Please keep us informed, and maybe we can add lxde back into the installer for beowulf.
Jessie was two years late. Ascii was one year late. If the trend continues, beowulf will be six months late.
We've gained more devs than we've lost in the past year, and we've had collaboration between debian and devuan devs. We are very much alive.
Put APT::Install-Recommends "no"; in /etc/apt/apt.conf.d/norecommends and Recommends will be excluded on upgrades as well as installations.
Maybe aptitude why avahi-daemon will tell you something useful.
@fsmithred - On your no-dbus system, are you able to create a system tray icon using yad? What happens when you run $ yad --notification --image=dialog-ok --text="testing" &?
I get a notification icon in lxpanel. I can't tell what it is - maybe a bell - it's light on lighter background. If I use dialog-warning, then I get the warning icon, which is easy to recognize. It just works. I don't know why. The only new process that shows up is the yad command. Using this iso: https://get.refracta.org/files/experime … -04-16.iso
UPDATE: If I run the same command on my ascii/xfce with dbus, I get the icon in the systray and no additional instances of dbus in ps output. If I run strace on that command, the string 'dbus' does not appear in the output.
I have yad installed and working in a no-dbus system. (live iso) There are some dbus libs installed, but not dbus itself. Yad's deps don't include any dbus packages. What are you seeing?
Copy those lines to ~/.bashrc and they'll work. I don't know why. I should, and I'm sure I've read an explanation, but I don't remember it. It's been like that for as long as I can remember (maybe as far back as lenny or etch.)
Graphics files can be part of a git project just like any other files. For example, go into the backgrounds folder here - https://git.devuan.org/devuan-packages/desktop-base - and click on one of the .png files.
The change in behavior of su is due to moving login from the shadow package to util-linux.
To revert to the old behavior:
https://dev1galaxy.org/viewtopic.php?pid=16456#p16456
util-linux: Please use login/passwd implementations provided by util-linux
https://bugs.debian.org/cgi-bin/bugrepo … bug=833256
It was correct the first way. If id is zero, you are root and need the sbin directories. If id is not zero, you are user and get games in your path.
If you think there's a problem with root's path in beowulf, I would say you are correct, but you mis-identified the cause of the problem.
In Beowulf:
- If you use su to become root, you keep the user's PATH, and need to use the full path to commands in *sbin, like this: /sbin/reboot
- If you use su - to become root, you get root's PATH and can run commands in *sbin directly, like this: reboot
To keep the old behavior, see https://dev1galaxy.org/viewtopic.php?pid=16456#p16456
It works here in xfce (refracta ascii), but I'm not seeing the icon on the panel. I haven't checked to see if I did anything wrong.
Even better, it installs and runs in my nodbus beowulf, and the icon shows up on lxpanel. Testing in a live-iso running in a VM was less than ideal, and I didn't jump through all the hoops to get it to actually connect. I can do that with an installed system some time.
Thanks.
cat /etc/sudoers.d/user_shutdown
phred ALL= NOPASSWD /sbin/shutdown, /sbin/halt, /sbin/poweroff, /sbin/rebootNo dbus needed. You can make panel buttons for 'sudo halt' and the others if you don't want to type it.
I'm no sudo expert, but you shouldn't have to mess with pam to allow a user to have certain commands with no password. First thing I would try is to just list the command with its full path but without the arguments. And maybe leave out the (ALL).
Maybe this:
os ALL= NOPASSWD: /sbin/wondershaperfsmithred wrote:I think the installer normally asks you for additional CDs early in the install. It's been a long time since i've done that. I do know that if you install without a mirror, there are some packages that won't get installed, such as wicd, firefox, and synaptic. If you want them, you'll need to install them afterward, even though they are on the installer media.
Please explain why this is considered acceptable?
I can't think of a reason why synaptic doesn't get installed automatically, but skipping the network stuff does kinda make sense if you don't have a network.
It's not one of ours.
$ apt-file find /usr/share/themes/Shiny
mate-themes: /usr/share/themes/Shiny/metacity-1/metacity-theme-1.xmlbash: make: command not found
apt install build-essential linux-headers-$(uname -r)I don't know about the tar error. It sounds like there's a tar command in the script that has the -f option but no filename after it.
I think the installer normally asks you for additional CDs early in the install. It's been a long time since i've done that. I do know that if you install without a mirror, there are some packages that won't get installed, such as wicd, firefox, and synaptic. If you want them, you'll need to install them afterward, even though they are on the installer media.
If you're having trouble with a particular package mirror, you can either use pkgmaster.devuan.org or select another from this list:
http://pkgmaster.devuan.org/mirror_list.txt. You might need to select one of the expert install options (graphical or not) to be able to put in any mirror you want.
I didn't think anyone was still using wvdial. It's now on my TODO list, so it will most likely be added in some future release. (probably beowulf)
The rc before the package name means that the package was installed previously, has been removed and left behind one or more config files. The original iso only has the four libraries listed, so you must have installed something that pulled in dbus and dbus-x11 and then removed it.
To get those two out of the list, purge them. (Note: 'aptitude search ~c' will show you others that left behind config files, and 'aptitude purge ~c' will get rid of them.)
It's a mouse, not a rat. (I've known that for so long, I can't cite the source.)
It's possible to run a 5.2 kernel in beowulf, which is mostly ready. (If you need policykit and its friends, getting there might be tricky right now.)
I don't think there's a way to delete an account without also deleting that user's posts. That would be too great a loss. Just stick with the new name.