You are not logged in.
debian repos always have unfresh old software;)
And for the most part those packages will install and work. You are using the wrong distribution if you want bleeding edge software. A Debian based system is never going to give you that. You have two options tried and true install old version package which could work WHEN it installs or waste the time never getting the newest to even install. To top it off it is .run file which is going to do nothing but pollute the system with files it will have no idea of, possibly causing conflicts if it installs file(s) over existing one(s).
It will install here without problems but then again I use the system as intended with native debian/devuan packages, not some third party versions that as you have experienced can cause problems.
root@9600k:~# apt -s install hplip
Installing:
hplip
Installing dependencies:
hplip-data printer-driver-postscript-hp python3-ptyprocess
libhpmud0 python3-freetype python3-reportlab
libraqm0 python3-olefile python3-rlpycairo
libsane-hpaio python3-pexpect
printer-driver-hpcups python3-pil
Suggested packages:
hplip-doc python-pexpect-doc python3-egenix-mxtexttools rl-accel
hplip-gui python-pil-doc python-reportlab-doc rl-renderpm
Summary:
Upgrading: 0, Installing: 14, Removing: 0, Not Upgrading: 0
Inst hplip-data (3.22.10+dfsg0-8.1 Devuan:6.0/stable [all])
Inst libhpmud0 (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Inst libsane-hpaio (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Inst printer-driver-hpcups (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Inst python3-ptyprocess (0.7.0-6 Devuan:6.0/stable [all])
Inst python3-pexpect (4.9-3 Devuan:6.0/stable [all])
Inst libraqm0 (0.10.2-1 Devuan:6.0/stable [amd64])
Inst python3-pil (11.1.0-5+deb13u2 Devuan:6.0/stable-proposed-updates, Devuan-Security:6.0/stable-security [amd64])
Inst python3-freetype (2.5.1-1 Devuan:6.0/stable [all])
Inst python3-rlpycairo (0.3.0-3 Devuan:6.0/stable [all])
Inst python3-reportlab (4.3.1-1 Devuan:6.0/stable [all])
Inst hplip (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Inst printer-driver-postscript-hp (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Inst python3-olefile (0.47-1 Devuan:6.0/stable [all])
Conf hplip-data (3.22.10+dfsg0-8.1 Devuan:6.0/stable [all])
Conf libhpmud0 (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Conf libsane-hpaio (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Conf printer-driver-hpcups (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Conf python3-ptyprocess (0.7.0-6 Devuan:6.0/stable [all])
Conf python3-pexpect (4.9-3 Devuan:6.0/stable [all])
Conf libraqm0 (0.10.2-1 Devuan:6.0/stable [amd64])
Conf python3-pil (11.1.0-5+deb13u2 Devuan:6.0/stable-proposed-updates, Devuan-Security:6.0/stable-security [amd64])
Conf python3-freetype (2.5.1-1 Devuan:6.0/stable [all])
Conf python3-rlpycairo (0.3.0-3 Devuan:6.0/stable [all])
Conf python3-reportlab (4.3.1-1 Devuan:6.0/stable [all])
Conf hplip (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Conf printer-driver-postscript-hp (3.22.10+dfsg0-8.1 Devuan:6.0/stable [amd64])
Conf python3-olefile (0.47-1 Devuan:6.0/stable [all])The highest version available is a .22
https://packages.debian.org/search?keyw … ection=all
Try a package built for your system you may get it working.
But since it hasn't updated, I suppose I should ask: How often should I expect updates in Excalibur?
With all Debian based stable releases few and far between mostly only security updates like the kernel that got updated a few days and now it is showing me libc6 and its related package are to be done. Some of these will only be shown if you have enabled the proposed-updates.
Edit:
root@9600k:~# cat /etc/apt/sources.list.d/devuan.sources
## Devuan 6 excalibur
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
## Normal excalibur sources
Types: deb
URIs: http://gnlug.org/pub/devuan/merged
Suites: excalibur excalibur-backports excalibur-proposed-updates excalibur-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
## excalibur security sources
Types: deb
URIs: http://gnlug.org/pub/devuan/merged
Suites: excalibur-security
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64Using that for your .sources file will get everything, if you want source packages to install from add deb-src to the Types line.
I believe Debian will install with secure boot turned on. With that as an example, would it be terribly difficult to update Devuan to do it, too?
So install that and do the conversion to a Devuan system as per the instructions given on the site..
failed to turn on DPMS: DPMS is not enabled . I guess we found the issue , but this is an issue in of itself right ? I deleted the xsession error log , wich freed up the space , but what could be causing MATE power manager to spam errors ?
Certainly have found it two choices find out why the DPMS is not getting enabled to stop it spamming the log. I despise shoddy programming like that by the clueless fool that did it. Second option is this a bash/sh script you put in executable location to allow cron to run it every two hour say to delete the old file and create new. First fin the permissions of the file.
zeus@9600k:~$ ls -lh .xsession-errors
-rw------- 1 zeus zeus 305M Mar 19 21:47 .xsession-errorsOn my machine it is read write only so that is how you want it to be when recreating it. So something like this for the file.
#!/bin/bash
# A script to remove the spam filed .xsession-errors that has been filling my /home partition
rm /home/username/.xsession-errors
touch /home/username/.xsession-errors
chmod 0600 /home/username/.xsession-errorsNow that does it for the file save it to somewhere that is in your and set the executable bit for me I would use my /home/username/bin directory for things like this.
nano /home/username/bin/xsession_errors_remove.sh
chmod +x /home/username/bin/xsession_errors_remove.shNow set it up to run from the crontab by using crontab -e to add a line in there for the normal user. My listing showing a script I run ever two hours to backup my home directory.
zeus@9600k:~$ crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
snip ...
#
# m h dom mon dow command
## Run my rsync snapshot script every two hours.
0 */2 * * * /home/zeus/bin/snapshot_home.sh > /dev/null 2>&1Change the path and file name to yours and you should have no more problems with that piece of junk messing you about.
Open a terminal and use one of the commands in the page below to find the files. Space on a partition does not get taken up by nothing. Your "solving" it once by using live usb suggests the cache files that accumulate and get deleted on a restart may be part of the problem. Those are in hidden directories and if those programs you use to search for them do not check for those they will appear to be hidden. Try the qdirstat program it definitely shows the hidden files/directories on a partition in a graphical program.
I had no idea where Firefox ESR saved my passwords or bookmarks, or where my personalized dictionary was located.
For an older install it would have stored all of that in the .mozilla directory in your /home/username directory, for a new fresh install using the latest versions that have changed to XDG desktop specification it is in the .config/mozilla directory now.
Edit: All may not yet be lost if you have created a Firefox account on old install you should be able to login and sync it to get most of you old stuff back like the bookmarks, extentions, passwords.
In my opinion, this isn't normal.
It is normal for apt everything is signed with the official Debian or in this case Devuan gpg keys. This provides the security in knowing you are getting exactly what was uploaded to the mirrors. If the signatures do not match apt errors and will not install from that mirror. If that is not good enough for your security needs then do not use it or pony up the cash and effort to make every single mirror capable of supporting SSL over the http connection(s).
If using a Devuan install without a desktop already installed, will the TDE login manager be pulled in? Is it better to start with a minimal install such as LXDE and then remove it after TDE gets installed?
The TDM (TDE Display Manager) will be installed no matter the current one on the machine. If already installed different manager then you get the debconf choice to choose the one to login with. Should be no need for anything other than the basic install then installing the software wanted for the TDE and Xlibre if wanted instead of Xorg. With the TDE you get the choice of the tdebase-trinity to install or the tdedesktop-trinity the whole thing I think it is called.
https://wiki.trinitydesktop.org/Devuan_ … structions
https://github.com/xlibre-debian/devuan/
The .sources files from my testing machine I use for both of them.
root@9600k:~# cat /etc/apt/sources.list.d/trinity.sources
# This file trinity.sources adds the settings needed to install the TDE
# desktop on Devuan Excalibur.
# Trinity R14.1.x Stable Release (not for testing/unstable)
Types: deb
URIs: http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.1.x
Suites: excalibur
Components: main deps
Architectures: amd64
Signed-By: /etc/apt/trusted.gpg.d/trinity-archive-keyring.gpg
Enabled: yes
# Testing builds if wanted need to enable then disable the stable above
Types: deb
URIs: http://mirror.ppa.trinitydesktop.org/trinity-testing
Suites: excalibur
Components: main deps extra
Architectures: amd64
Signed-By: /etc/apt/trusted.gpg.d/trinity-archive-keyring.gpg
Enabled: no
root@9600k:~# cat /etc/apt/sources.list.d/xlibre-debian.sources
# Xlibre built for Devuan
# https://github.com/xlibre-debian/devuan/
Types: deb
URIs: https://xlibre-debian.github.io/devuan/
Suites: main
Components: stable
Enabled: yes
Architectures: amd64
Signed-By: /usr/share/keyrings/NexusSfan.pgpYou can remove it without any problems at least I have not seen any without it.
zeus@9600k:~$ dpkg -l | grep systemd
rc dbus-user-session 1.14.10-1~deb12u1 amd64 simple interprocess messaging system (systemd --user integration)What am I missing?
Appears you have it formatted incorrectly. This what I use forit with a file in the sudoers.d directory to tell it the settings to use, it works flawlessly.
root@9600k:~# cat /etc/sudoers.d/zeus
# User privilege specification
zeus ALL=(ALL:ALL) NOPASSWD: ALL
And you do not to be in the sudo group to use it this way.
zeus@9600k:~$ groups
zeus cdrom floppy audio dip video plugdev users netdev bluetooth lpadmin scannerzeus@9600k:~$ fdisk -l
fdisk: cannot open /dev/nvme1n1: Permission denied
fdisk: cannot open /dev/nvme0n1: Permission denied
fdisk: cannot open /dev/sda: Permission denied
fdisk: cannot open /dev/sdb: Permission denied
zeus@9600k:~$ sudo fdisk -l
Disk /dev/nvme1n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SPCC M.2 PCIe SSD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CBEC129E-0D94-4784-A2DC-3E5F15FBF4C3
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 411647 409600 200M EFI System
/dev/nvme1n1p2 411648 84297727 83886080 40G Linux filesystem
/dev/nvme1n1p3 84297728 252069887 167772160 80G Linux filesystem
/dev/nvme1n1p4 252069888 1000215182 748145295 356.7G Linux filesystem
Disk /dev/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: CT4000P3SSD8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9DF2CDC4-F766-486D-AA06-ADDFBAEF6A1C
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 411647 409600 200M EFI System
/dev/nvme0n1p2 411648 84297727 83886080 40G Linux filesystem
/dev/nvme0n1p3 84297728 252069887 167772160 80G Linux filesystem
/dev/nvme0n1p4 252069888 1594247167 1342177280 640G Linux filesystem
/dev/nvme0n1p5 1594247168 7814035455 6219788288 2.9T Linux filesystem
Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: MKNSSDE3480GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D4AAE03C-25EB-4FF0-BA58-E541CA6CDD77
Device Start End Sectors Size Type
/dev/sda1 40 409639 409600 200M EFI System
/dev/sda2 409640 84295719 83886080 40G Linux filesystem
/dev/sda3 84295720 235046911 150751192 71.9G Linux filesystem
/dev/sda4 235046912 937177087 702130176 334.8G Linux filesystem
Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: WDC WD60EZRZ-00G
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8057E6FD-95D1-4FAA-A427-E687AB7F0423
Device Start End Sectors Size Type
/dev/sdb1 2048 11721045134 11721043087 5.5T Linux filesystemBut not when new packages or more extensive changes are needed to have things actually work properly without systemd. It's always "remove garbage" or "sanitise", never "fix", "improve" or "add alternative".
So long as this attitude persists, every Devuan release will have less stuff that works, less functionality, and less user choice.
You are using the wrong distribution if you want something like that where the developers are always straying away from a solid Debian base with their changes then MXLinux is for you. You get the choice of it with or without the systemd garbage and developers who do exactly what you want, namely always messing with it putting out new packages for it when requested to do so. Or you can stick around here and bitch and complain about these developers and how hard done by you are by them taking the path they have chose over a decade ago. Then there is getting off your ass option and doing these so easy changes you complain about all the time. I suspect you will do neither help out or shut up about this as that is all you do is complain and bitch about how people should be doing the work you want done in a volunteer project.
Devuan follows Debian. It's OK, the idea is clear. But why does Devuan follows obsolet versions of inits that are not inits in Debian?
Yo do not understand what you talk about the openrc IS in Debian, Devuan follows the packages as they are in Debian except where changes are required to remove the systemd garbage.
https://packages.debian.org/search?keyw … ection=all
That is the version you will get for the lifetime of the stable distribution.
There is. The version of openrc in Devuan is, as usual, many versions behind.
Well since Devuan only repackages the Debian released packages it is as always Debian is so far behind the curve most times it is pathetic.
I considered adding the deb-multimedia repository and installing it that way, but it requires very careful management and resolution of possible conflicts
Yes it certainly does you have to be careful or you end up with one hell of a mess. But then again is is not made for us it is a Debian idea though his care for respecting the build/install dependencies could be much better. You would think as a Debian developer he would know these things.
I found that Avidemux can do most of the things that Handbrake can, with a better interface too.
It can do more even you can edit the video, combine videos together things like that. I use it all of the time the deb-multimedia.org archive I get it from has the -qt variant you can install of it, which I did.
Man it's great ain't it? I'm in the big love right now with ffmpeg, so many things you can do.
Oh it certainly is one hell of a program a bit of a steep learning curve to it but damn the things you can do..
can i just switch the repository back from Freia/Ceres to Excalibur or how could i freeze the OS so that i don§t get trouble once KDE 6.6 get release?
thanks.
No you are committed to them now you have upgraded libc to the newer version it is the MAIN building block of your entire operating system in Linux. Once you do that there is no going back.
I really wanted to like TDE, but it's a bit wonky to set up, and the hard dependency on Konqueror (a shitty file manager and an even shittier Web browser in one) is a major turnoff.
Old Konqueror which it is was at its time the best file manager around allowing the split view of side by side or up/down split or both if wanted. With plenty of plugins so you could sftp, ftp, ssh, smb from the address bar and need nothing else but it to do all of your work if you want. Still can in the modern version too I have numerous bookmarks that do just that to connect to my various machines using them protocols. Then of course the killer feature a split the screen in a top / bottom arrangement so you can see the entire file name and not some truncated piece of junk view that side by side view all other file managers do. Wasting all of that space that can give you a proper view of the name. It is my only browser I have used in all of these years since I first started using it and it works fantastically. I avoid the Gnome like the plague and have for decades now, gtk apps well there are some that you have no choice but to use like the Handbrake though if not feeling like going graphical I have my encoding scripts that do the same thing using the ffmpeg.
Edit:
You and me both. I do like KDE, (even the current iteration) but the development model is utterly infuriating. Sadly, warts and all, I'm not convinced there's a better "full DE" option right now.
Yes it is definitely a polished effort I will give them that but they way they have gone about it over the years has severely pissed me off to the point I do not even care to use it anymore. Who knows perhaps the LXQt will not continue to be my good enough for me to use in its place option. But I have figured out the quirks that bother me and it is working well. If not I will have to build a bridge and get over it on the KDE BS go back to it if it is even possible then.
I'd say "definitely is", and probably soon. IME KDE will do what they always do - death by a thousand bugs. Let [thing they want gone] rot until the userbase is sufficiently annoyed, then trot out a replacement that requires [thing they want to depend on] and use it as justification for never fixing what used to work...
I see you have noticed the same as I have in my got to be twenty-five years of using it now since the pre-1.0 days all them years ago. The way they do the death by thousand cuts method of elimination. I was pissed enough at the x11 rot they did on the transition to the version 6 but seeing the deeper integration with the systemd garbage and the wayland only announce pushed me over the top and I dumped it. I went with the LXQt still uses the toolkit and same type layout but way less resources. First time in years I have seen a load under 1 on my machine and it is on a regular basis, none of this three or four BS anymore for just being logged in. I used to think those people going on about it being bloated piece of junk were just Gnome trolls, they were/are most times, but they actually had a point about the resources the damn thing used for doing next to basically nothing but showing desktop. Who knows if the Sonic people can gather enough momentum to get a fork going to allow for a reasonable means to go forward, I gave the TDE a try as well it is based on the old 3.5 code with a modern skin applies it looks good not like a Fisher Price toy OS those old skins from twenty years ago make it look like. So hopefully there will be couple of choices for people who like the free software they use to actually support freedom of choice not just pay lip service to it, while the developers kiss the ass of the parasite corporations who seek to lock down everything and tell you how to use your own computer.
The DUR will only have the recipes. A user would need to build the package themselves with the recipes. The built packages will not be added to the main archive. Security will be on the users.
Security will be mostly on users, you basically installing random software from the internet.
That ought to work out well with that strategy you may as well be using Arch or Artix. At least they have more of the infrastructure to do it more securely.
Edit: And I would add not a single thought has gone into security with this, at least the recipes could be signed with a gpg key to add some sort of verification.
I see very little mentioned about security. I fail to see the reason to compromise the archive with unsigned packages.
Or do I need an extra flag to get rid of the packages that came as a dependency of okular?
Use apt remove --purge okular then apt autoremove --purge when it tells you that the autoremove command can be used to remove package that are no longer required since you removed the okular. Oh when installing software you should always use apt install -s okular that will show you that you are about to install a whole extra bunch of packages to get the single program you want. If that is acceptable to you then you can remove the -s in the line to not just simulate the installing but actually do the installing.
is that it will result in SDDM being abandoned
It already was I read somewhere in a posting that it had been years since a commit was made to it, just like the Xorg people and their effort kill that off with the bitrot. At this point in time anyone who seriously believes they are not going systemd only is a GD fool. And get in contact with me I have bridge for sale in Brooklyn going dirt cheap only one owner... ![]()
Figures. I guess that means no more KDE on FreeBSD as well. Back to XFCE then. Well, at least if one wants to use their PLM. As long as SDDM is still compatible, we're ok?
Yes until the bitrot settles in theoretically they have left it to die for years now like the Xorg weasels have done or as I have read in places they are going to further enshitify it with systemd-home for the login. The cancer keeps spreading, you may want to look at LXQt it is what settled on after dumping KDE after more than twenty-five years of use due to this garbage they do.
I already have AI disabled, atleast i think i have with below user.js settings.
I thought I had everything disabled until I ran across this posting a week or so ago from my install notes.
Locked and disabled the AI garbage on both Waterfox and Firefox with the settings in this article.
My location where the files are to be done anyone would have to adjust to their locations.
zeus@9600k:~$ nano bin/waterfox/defaults/pref/local-settings.js
zeus@9600k:~$ cp bin/waterfox/defaults/pref/local-settings.js bin/firefox/defaults/pref/local-settings.js
zeus@9600k:~$ nano bin/waterfox/mozilla.cfg
zeus@9600k:~$ cp bin/waterfox/mozilla.cfg bin/firefox/mozilla.cfgAnd if anyone is interested in moving to the new XDG specification location for Firefox >= 147 which I have kept for a backup if the waterfox ever goes tit up. Then this is the totally simple procedure I used to do it..
To move to the new XDG specification in firefox it is simpy a matter of doing this.
https://www.reddit.com/r/firefox/comments/1ql3huj/migrating_profile_with_version_147_and_the_new/
zeus@9600k:~$ mv .mozilla .config/mozilla