You are not logged in.
I used devuan testing/daedalus from mid last year to when it went stable and had no any issues, if i did they were probably my own fault. I think you will find there are quite a few users who go the testing/unstable route.
Yes, that's about how I did it. I am currently with Daedalus. I use LXQt and KDE Plasma, Plasma because it can use Wayland. Plasma has a few tiny bugs with Wayland though. For example, the control bar disappears during the most important tasks. These are only very small bugs and I think they might be fixed in Testing or Ceres. Yes, but on the other hand I'm dealing with other things ...
I think it all depends on what you want to install and how you want to use testing and or unstable branches. Bleeding edge can be an issue from time to time, especially anything to do with gnome and kde desktop environments. I prefer setting up minimal desktop environments using bleeding edge branches, for example simple window managers like openbox and dwm and add tried and true software to them, learning how the x window system works to make full use of it instead of using 3rd party programs and the like. Just my take, its not a one size fits all and many issues might arise from the core components of devuan and debian like libc and xorg that could break a system using unstable and testing.
Thanks for the feedback. Yes, with Debian Sid for me it was always good to have Openbox or LXDE on the machine at least at the same time as KDE Plasma, to some extent as a fallback solution. apt-listbugs, nala etc. are also good helps with Unstable.
However, among Devuan users I have the feeling that Testing and Unstable are not used as often as with Debian. Maybe someone who works with Testing or Ceres and gets along with it will contact me. I would be interested to know.
Question: is it as unproblematic to use testing or even unstable with Devuan as it is with Debian? For many years I used testing with Debian and for quite a long time also Sid. There were no real problems. But I was always careful with updates and upgrades. Now I am itching to try testing or even Ceres. Are the possible problems different than with Debian? Do I have to expect something that does not exist with Debian?
I'd wait - if your distro includes it, fine, otherwise......
Yes, I refrain from installing this tool ... Thanks
Upscaly offers an interesting possibility for me to improve old photographs or also cuttings from photographs. When I install from foreign sources, of course, there is always a risk. What would be safer? Flatpack or DEB? However, I can only poorly assess this risk. What do you think about this tool: https://www.upscayl.org/
Would you install it or would you rather leave it alone?
For those who understand German, here is an interesting and well done report on systemd, Devuan is also mentioned:
https://linuxnews.de/das-beste-oder-nichts-systemd/
Run apt update once and confirm. ...
Thank you for this tutorial. It works. I will read everything again carefully.
Thank you very much!
Default configuration of Devuan package repositories looks like this
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware deb http://deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware deb http://deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmwareMore info here:
Also with this sources.list
cat /etc/apt/sources.list
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmwareI get this error message:
Fehler: Repository 'http://deb.devuan.org/merged daedalus-security InRelease' changed its 'Label' value from 'Devuan Security' to 'Devuan-Security'I am getting that same Label message.
I think there is something wrong. I've had something like this a few times. Wait and see has helped. Maybe we should just wait and see. Maybe it's being worked on right now.
Hello. I think you should remove
non-free-firmwarefrom
#Proposed-Updates
Yes, thank you! I did that and now I only get this message:
Repository 'http://deb.devuan.org/merged daedalus-security InRelease' changed its 'Label' value from 'Devuan Security' to 'Devuan-Security'I don't really understand that.
I mean that this sources.list was still working fine on my machines just before Daedalus became stable:
cat /etc/apt/sources.list
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
#Updates
deb http://deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
#Security
deb http://deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
#Proposed-Updates
deb http://deb.devuan.org/devuan daedalus-proposed-updates main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/devuan daedalus-proposed-updates main contrib non-free non-free-firmware
#Backports
deb http://deb.devuan.org/merged daedalus-backports main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged daedalus-backports main contrib non-free non-free-firmwareToday I get this message:
nala update && nala upgrade && nala clean && nala autopurge && nala autoremove
╭─ Aktualisierung der Paketlisten ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│Keine Änderung: http://deb.devuan.org/merged daedalus InRelease │
│Keine Änderung: http://deb.devuan.org/merged daedalus-updates InRelease │
│Keine Änderung: http://deb.devuan.org/devuan daedalus-proposed-updates InRelease │
│Keine Änderung: http://deb.devuan.org/merged daedalus-backports InRelease │
│Aktualisiert: http://deb.devuan.org/merged daedalus-security InRelease [31 KB] │
│Holte 31 KB in 0s (0 bytes/s) │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Warnung: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Fehler: Repository 'http://deb.devuan.org/merged daedalus-security InRelease' changed its 'Label' value from 'Devuan Security' to 'Devuan-Security'
Warnung: Skipping acquire of configured file 'non-free-firmware/dep11/icons-128x128.tar' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-de_DE' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/dep11/Components-amd64.yml' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/dep11/icons-64x64@2.tar' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-de' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/source/Sources' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/dep11/icons-64x64.tar' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
Warnung: Skipping acquire of configured file 'non-free-firmware/dep11/icons-48x48.tar' as repository 'http://deb.devuan.org/devuan daedalus-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)Does anyone know anything about this?
Daedalus is stable
https://www.devuan.org/os/releases
... The 'nonsense' did not come from me ...
If you don't give a source, don't say where you got it, it looks like it came from you ....
If not you, who? Don't you want to be part of the solution?
All right. I will register with this forum and I will correct it as best I can.
Sometimes they write nonsense ....
Yes, that seems to be the case. But in this way, nonsense is spread about Devuan. I don't have (and don't want) an account at linuxnews.de, otherwise I would write a statement.
... Nope ...
Yes, I realize that. But there seems to be a bit of confusion among the friends of linuxnews.de.
https://linuxnews.de/systemd-254-deklar … -veraltet/
"Systemd 254 is already available in Arch-Testing, Debian and, oddly enough, Devuan-Unstable, Gentoo and Fedora Rawhide, with more distributions to follow. On October 2, systemd 255 is to follow as the next version."
I read this here:
https://linuxnews.de/systemd-254-deklar … -veraltet/
Hello everyone, I'm currently testing a new installation of Daedalus and I've observed a strange behavior with Plasma Wayland that I'll briefly outline:
1. Booting, SDDM, Plasma Wayland: blank graphical user interface, only cursor icon and KRunner (Alt+F2) works.
2. Booting, SDDM, Plasma X11: known graphical user interface, everything works
3. Booting, SDDM, LXQt: known graphical user interface, everything works
4. Booting, SDDM, Xfce X11: known graphical user interface, everything works
5. Booting, SDDM, Plasma Wayland: empty graphical user interface, only cursor icon and KRunner works. Log out, start Plasma X11 or LXQt or Xfce, log out, start Plasma Wayland, known graphical user interface, everything works.
Has anyone else experienced this problem?
On another computer, on which Daedalus came not by a new installation, but by an upgrade from Cimaera, I could not observe the problem yet.
Best regards
New finding:
I have now clicked in the Plasma System Settings, in Display Setup (for me this is in German, I have translated it and don't know if it is also called so exactly in English), "Conventional applications - perform scaling myself". At least after booting three times and logging into Plasma Wayland, everything is fine.
Good morning everyone, I have proceeded according to instructions. However, problems have arisen that I have not seen through. The graphical interfaces did not work properly. Lxqt and plasma was not usable. I might have been able to fix it with a lot of time, but had doubts that I could do it cleanly. My skills probably don't extend that far. So I decided to do a fresh install. I have only taken over /home.
Best regards from my new Devuan Daedalus machine.
PS: Devuan Daedalus works well on my Thinkpad and I'm happy to have landed with Devuan Daedalus for my desktop now.
Bookworm to Daedalus should be similar to the migration of Bullseye to Chimaera. ...
Thank you very much, I will try that!
Hello each other,
Is there any way to switch from Debian Bookworm (stable) to Devuan Daedalus (soon stable)?
I have a Daedalus-sources.list from my Thinkpad, I could probably use that as a base. I would have to install the init system of course and eliminate systemd. Does anyone have a tip for me?
... I have added this to the daedalus repository and can confirm that they are now active. Have not checked the backports, yet.
I have this sources.list. I have not observed any problems so far.
deb http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ daedalus-updates main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus-updates main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware
deb http://deb.devuan.org/devuan daedalus-proposed-updates main contrib non-free non-free-firmware
deb-src http://deb.devuan.org/devuan daedalus-proposed-updates main contrib non-free non-free-firmwareI would recommend this sources.list. Sources that are not wanted can be commented out
Yesterday I upgraded from Chimaera to Daedalus without any issues. Here are the steps I followed:
Edit /etc/apt/sources.list to point to daedalus $ sudo apt-get update $ sudo apt-get upgrade $ sudo apt-get dist-upgrade # at the end there are some errors having to do with old version of linux kernel $ sudo apt-get autoremove --purge # this removes the packages that caused errors $ sudo apt-get dist-upgrade # now it completes without any errors $ sudo apt-get autoclean Reboot
Sometime about a year ago I read about Nala. I installed it and tried it out and stuck with it:
nala update && nala upgrade && nala clean && nala autopurge && nala autoremoveNow from Daedalus it can be used.
... running Daedalus for several months ...
Yes, that's the same here with me.
But when Daedalus is actually ready, the sources.list should be adjusted (at will: security, updates, backports ... ).
... "You may modify the style sheet in any way you wish, but not the HTML." ...
Yes, and a clean HTML code is very clear. Errors are quickly detected.
You can play creatively with the style sheet. But for some things, e.g. scientific texts, you don't even need a style sheet. For me, this is currently the most economical and practical way to store texts (including links).