You are not logged in.
That article uses the words "immutable" and "update" in the same sentence. I'm confused. It sounds like RedHat (or whoever) can make changes to your system, but you cannot. Someone who understands this, please tell me I'm wrong.
I don't know if this gets rid of the icon, but this will disable searching in the address bar. Or at least it will make it so that your mouse doesn't automatically bounce up to the address bar when you start typing. I haven't actually tried to see if searching in the address bar still works. And I don't have the ddg icon.
In case the search bar gets disabled by an update, here's how to get it back.
https://support.mozilla.org/en-US/questions/1356391
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.
More info on about:config: Configuration Editor for Firefox. The moderators would like us to remind you that changes made through this back door aren't fully supported and aren't guaranteed to continue working in the future. Since I use this one myself, I feel comfortable mentioning it, even if it does turn out to be temporary relief only.
(2) In the search box in the page, type or paste handoff and pause while the list is filtered
(3) Double-click the browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar preference to switch the value from true to falseEdit: I tried it. "about:blank" gives me a blank page. In the address bar, it says something like "Search with ddg or enter a url" but there's no icon and the page is blank. It is still possible to search in the address bar but it doesn't jump there from the search bar.
Edit2: Sorry, I forgot I was in Chimaera when I did the test. In excalibur there's a duck icon in the address bar. I assume that can be changed by changing the default search engine, in case you like the bing or wikipedia icon better. Do what I do and don't look at the duck.
I can confirm your results with the latest 1065-refracta-lang. Standard live-config option works and I can log out and change the language on login except if I disable refracta-lang. Short option works, too.
Thanks for the fixes. New isos are up.
Oh, maybe I wasn't clear. 1065-refracta-lang is working correctly while the standard live-config option for locales is not working. I just changed the boot menu to use lang= and it works. I haven't tried the latest 1065 yet. And "works" means it shows the language selected at boot plus C plus American English. The keyboard selector has a full range of choices.
One odd thing. In the VM I'm using to make the snapshots, the lightdm puts the widgets on the left side of the top bar, but in the live isos, they're on the right.
- Updated 1065-refracta-lang - and I see that the standard live-config options for locales no longer works. Only the keyboard layout changes. I'll have to hack the boot menu on the next build.
- Fixed lightdm as indicated. Note: lightdm-gtk-greeter allows you to select the locale, slick-greeter allows you to select the keyboard. I don't know how to get either one to do both. (I like the look of slick-greeter)
- Added lines to /etc/pmount.allow (and hacked refractasnapshot and installer to deal with the nvme line)
#/dev/sd[a-z][0-9]*
#/dev/nvme[0-9]n[0-9]p[1-99]- Diverted xfce background image
inkscape -l deepsea_173556_640x480.png -o deepsea.svg
dpkg-divert --rename --divert /usr/share/backgrounds/xfce/xfce-x.svg.distrib /usr/share/backgrounds/xfce/xfce-x.svg
ln -s deepsea.svg xfce-x.svg- Added libmtp-runtime and modified /etc/udev/rules.d/90-alsa-restore.rules
- Unchecked the box in desktop settings for showing fixed drives. (That box is new, thanks.)
- Thunar mounts disks. In the case of encrypted disks, it says it failed after you give the password, but the /dev/mapper device appears and clicking on it mounts it.
I also forgot to install gtk3-nocsd. Firefox looks like it got scalped.
Not sure where mpv went.
I'm not seeing the error messages - they're flying by too fast. I'm guessing the alsa error is for 90-alsa-restore.rules. I can add the corrected file for that.
The rat seems inconsistent. Sometime I see it and sometimes not.
Fixes are welcome, thanks. I almost uploaded another iso for the nocsd, but I decided to wait in case there was something else. ![]()
I just now added mpv, jmtpfs, mtp-tools, f2fs-tools.
Atlante,
You might have a better time using the old-style sources.list. It makes it easier to find typographical errors like the one you made above which I can't find now. There was an extra space somewhere. That's in addition to the error message regarding "Types". I can't figure out what that one means.
You can use this for /etc/apt/sources.list and get rid of the devuan file in sources.list.d.
deb http://deb.devuan.org/merged excalibur main non-free-firmware contrib non-free
deb http://deb.devuan.org/merged excalibur-updates main non-free-firmware contrib non-free
deb http://deb.devuan.org/merged excalibur-security main non-free-firmware contrib non-freeYou have to exclude a few things and then you can add them later.
https://dev1galaxy.org/viewtopic.php?pid=47276#p47276
All the live images use codenames in sources.list, so excalibur is/was/will be excalibur whether it's testing, stable or oldstable. The last few pre-release isos had excalibur-security and excalibur-updates enabled in addition to the main repo. You shouldn't need to change any of that.
You need to run 'apt update' to refresh the cache. Then you'll be able to search for packages. Run 'apt upgrade' to get whatever updates there are.
Old but still useful -
https://refracta.org/docs/debian-handbook-wheezy.pdf
Last Debian Administrator's Handbook before systemd.
sources.list examples:
https://www.devuan.org/os/packages
Replace http with https and replace "deb.devuan.org" with "mirrors.dotsrc.org/devuan".
I don't usually look at the output you posted, so I can't sort out what you did wrong in sources.list. But I'll go ahead and guess - did you forget the /merged?
The Sources.list is set to Daedalus.
Kernel is: 6.1.0-41-686
It still says you're missing non-free firmware. Do you know which firmware package you need? If you're going to use a devuan kernel, you can install the non-free stuff. If you use the libre kernel, you can't use the non-free stuff.
If the system doesn't work without the non-free stuff then you can't use the libre kernel.
If the system does work without the non-free stuff, you can ignore the warnings.
N: Unable to locate package systemd-standalone-usersIt gets confusing with all the overlapping names. The correct name for that package is systemd-standalone-sysusers
# apt remove systemd-standalone-sysusers
The following packages were automatically installed and are no longer required:
libwtmpdb0 openssh-sftp-server
Use 'apt autoremove' to remove them.
REMOVING:
cron cron-daemon-common openssh-server systemd-standalone-sysusersInstalling opensysusers instead will remove systemd-standalone-sysusers without removing cron or ssh.
And either one of those will give you /usr/bin/systemd-sysusers.
In general, you should not try to mix testing/unstable packages with the stable release. That can lead to a lot of mismatched programs and libraries, and that will get worse as the testing progresses.
Instead, you should backport the package to build it for your stable system.
https://wiki.debian.org/SimpleBackportCreation
For some packages that's easy, and for some it's not.
Here's the fixed version of /usr/lib/udev/rules.d/90-alsa-restore.rules that you get in a netinstall of excalibur. The edit is hacked into the installer isos, so you won't get this fix on an upgrade from daedalus. And it might get clobbered if there's an upgrade to alsa.
The desktop-live iso got the upstream version, which has a few other changes. I hope that doesn't cause problems. That file is in /etc/udev/rules.d so if it does cause trouble, it can be removed without breaking anything.
This replaces /usr/lib/udev/rules.d/90-alsa-restore.rules
or better, put it in /etc/udev/rules.d/90-alsa-restore-rules
# do not edit this file, it will be overwritten on update
ACTION=="add", SUBSYSTEM=="sound", KERNEL=="controlC*", KERNELS!="card*", TEST=="/usr/sbin", TEST=="/usr/share/alsa", GOTO="alsa_restore_go"
GOTO="alsa_restore_end"
LABEL="alsa_restore_go"
ENV{ALSA_CARD_NUMBER}="$attr{device/number}"
# mark HDA analog card; HDMI/DP card does not have capture devices
DRIVERS=="snd_hda_intel", TEST=="device/pcmC$env{ALSA_CARD_NUMBER}D0p", RUN+="/bin/sh -c 'echo ALSA_CARD_HDA_ANALOG=$env{ALSA_CARD_NUMBER} >> /run/udev/alsa-hda-analog-card'"
# check for ACP hardware
TEST=="device/device/acp3x-dmic-capture", GOTO="alsa_hda_analog"
TEST=="device/device/acp6x-dmic-capture", GOTO="alsa_hda_analog"
TEST=="device/device/acp63-dmic-capture", GOTO="alsa_hda_analog"
TEST=="device/device/acp-dmic-codec", GOTO="alsa_hda_analog"
GOTO="alsa_restore_std"
LABEL="alsa_hda_analog"
# restore configuration for profile with combined cards (HDA + digital mic)
TEST!="/run/udev/alsa-hda-analog-card", GOTO="alsa_restore_std"
IMPORT{program}="/usr/bin/cat /run/udev/alsa-hda-analog-card"
ENV{ALSA_CARD_HDA_ANALOG}!="", ENV{ALSA_CARD_NUMBER}="$env{ALSA_CARD_HDA_ANALOG}"
LABEL="alsa_restore_std"
TEST!="/etc/alsa/state-daemon.conf", TEST=="/usr/sbin/alsactl", RUN+="/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore $env{ALSA_CARD_NUMBER}"
TEST=="/etc/alsa/state-daemon.conf", TEST=="/usr/sbin/alsactl", RUN+="/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime nrestore $env{ALSA_CARD_NUMBER}"
LABEL="alsa_restore_end"I got it from here: https://github.com/pixelb/ps_mem
You don't need to "install" anything. Just grab the script itself and make it executable. I changed "python" to "python3" in the shebang and run it with 'python3 ps_mem.py".
Those memory figures aren't written in stone. I checked an excalibur lxqt on a laptop here, and it only uses 305 MiB, That's the result of a more selective install without the task-* packages.
The top of the output is cut off in all the screenshots. Here are the column headings:
Private + Shared = RAM used ProgramComparison of memory use according to ps_mem.py.
Default desktop installations of Excalibur (Devuan 6.0.0) in qemu.
Screenshots: https://git.devuan.org/fsmithred/screenshots
Desktop ----- Memory use (ps_mem.py)
lxde (xorg) 332 MiB
lxqt (xorg) 428 MiB
xfce (xorg) 440 MiB
Gnome (wayland) 767 MiB
Gnome (xorg) 819 MiB
Cinnamon (xorg) 834 MiB
Cinnamon (wayland) ??? "experimental" (no desktop, login screen loops)
KDE (xorg) 1.1 GiB
KDE (wayland) 1.2 GiBsystemd has /etc/machine-id in addition to /var/lib/dbus/machine-id. We have the latter and if you don't want it to change on every boot, edit /etc/default/dbus.
I'm not sure, but I think PeppermintOS uses Calamares. Talk to Grafiksinc, one of their devs who also happens to post here occasionally. You probably need to go over there to get his attention. There might be a way to remove the systemd dependency.
Update (in case anyone else runs into this): The other person who had trouble used Ventoy to prepare the usb, and apparently, it chose to use the syslinux bootloader in the iso rather than the grub bootloader, even though that computer only does uefi.
Stultumanto beat me to it. Someone in IRC mentioned the same problem, so I just did a uefi install in qemu, and sure enough, I screwed up the first time and didn't boot uefi. When I did it right, the install worked and it installed grub. I still had to go through the uefi shell in qemu to get to the boot file, but it did boot. On a real hardware boot, there's probably a key to press that will show you a boot device menu, listing all the hard drives and usb or cdroms that are present. There might be two entries for the usb - one for legacy and one for uefi.
As mentioned, check to see that /sys/firmware/efi exists when you boot the live. There are other ways, to tell.
Note the color of the grub boot menu background. If it's blue, you booted in legacy bios mode. And it's a syslinux/isolinux boot menu, which looks different from a grub boot menu. When you boot the desktop-live in uefi mode, you get a black background at the boot menu.
You must have looked at the page right before I updated it yesterday. Either that or you need to refresh the page in your browser. I uploaded new Refracta 13 (Excalibur) isos yesterday. Those are ready.
https://get.refracta.org/
For upgrades, I think the only preparation that's needed is that you should update/upgrade your daedalus and install the usrmerge package before changing sources to excalibur. Refracta is Devuan with a different selection of packages and a few different settings. So it's ready for the next devuan release whenever the next devuan release is ready. And that happened two weeks ago.
I may as well mention it here because someone is sure to ask. "Why is it 13.1? What happened to 13.0?"
Answer: 13.0 was made two months ago and is still sitting on my hard drive. It never got uploaded while I was busy on the devuan release. So I made new ones.
https://get.refracta.org/files/stable/
https://get.refracta.org/files/testing/
More on desktops:
lxqt pulls in pulseaudio (like lxde does)
cinnamon (I had forgotten about this one) pulls in pipewire.
That leaves gnome to be checked. Someone else can do that, please.
The default installs of xfce and lxde pull in pulseaudio. KDE and mate pull in pipewire, but it doesn't work without some setup. See other recent discussions for details. I don't know what lxqt and gnome pull in.
If you install just the base system with no desktop, you can add whatever you want. Avoid the task-* packages if you want to be selective. You can have just alsa or alsa with either pipewire or pulseaudio.
Steve,
Thanks for the report. It took me a little while to find "switch user". It's only in the action button on the right side of the panel. It doesn't appear in the Logout window you get from the Applications menu. I can confirm that switch user doesn't work in the default setup. Also, the who command returns nothing.
I believe you found another bug in the Slim display manager. If you install lightdm, then "Switch user" becomes an additional choice in the logout screen, and it does work. Also, 'who' works then. This problem wasn't in the betas because slim was creating a black window over the desktop with autologin, so I used lightdm in the builds instead.
I was able to reproduce the grub failure in virtualbox, but in qemu it worked normally. I'll stop here on that point - I'm suppressing a rant about grub.
Point taken about the "copy files" button. If you do a uefi install, the button says "Install bootloader". That's an easy fix.
Edit: Forgot to mention ssh. The desktop-live is based on a default task-xfce-desktop install which does not include openssh-server.