You are not logged in.
So to start off, UUIDs have to be changed and that can be done with gparted but I have only done it on HDDs with a single partition.
Any pointers would be appreciated.
tune2fs -U e3eb81d0-bc67-492b-b57d-94eb1f892d9e /dev/sdb3Do it for each and every partition you need to change the UUID on changing to a different UUID for each one. For a fat32 partition used for the EFI.
mkfs.vfat -F32 -n EFI -i 0x11111111 /dev/sd??Gives UUID="1111-1111" for the fat32 EFI partition when you format it, the only way I have ever seen to do it is by a fresh formatting.
As for Vivaldi, their website claims that after installing the the .deb package "our Linux update repositories will be configured automatically for you to receive updates".
Personally I doubt this "Users are stupid so we don't give technical details, just click button and we'll handle everything" corpo-speak bullshit, but I'm not about to install the thing to find out.
I did not install the piece of trash but did download and extract the package and its data payload. It puts the browser in the opt directory and nowhere is there to be found a gpg key. They install a cron job file which when trying to look at has nothing in it so it is a bit of a mystery what it does. I tried their junk once many years ago and gave up once I discovered they were more interested in controlling their "smart" lights from the browser than actually fixing the bugs I reported. My reward for that effort was constant spam from the scumbags on the email that reported the bugs such that I had to create a special filter for anything coming from them going straight to /dev/null. That is the type of people you deal with when using it.
You are welcome.
2. It looks like that the way you commented the Suites: section wasn't correct. apt was still seeking for non-existant things.
You are welcome, probably should have done that myself while replying, I never tested it on my machine which would have shown my mistake in thinking a comment (the # in the line for it being ignored) would work there.
You are welcome good to read you got it sorted out. If you have not cleaned your apt cache you should be able to install the -36 version of the kernel still in there and get rid of the junk buggy -37. As to why GRUB did it no clue for the longest time I always thought it was steaming pile of dung. Since I got it figured out using the EFI booting my opinion has improved a little from that but not by much. It has to be well north of a decade since I have used an MBR machine but I always remembered having to do re-installs with it. Oh before I forget to mention it the location to find the old kernel is /var/cache/apt/archives/ if you did not know. Now it can be there or not is depending on whether the system is set up to keep the files or if you have cleaned the cache manually.
BTW it looks like freia-updates doesn't exist either. Should I remove the second line too?
Of course it is the same as the security, you would add both of them back in once they are created some time next year before the next release and the proposed-updates as well. You have until 2030 or so as well but you should consider switching too the new format devuan.sources too. My current file that has all of these things enabled.
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: amd64It is rather easy to switch sudo mv /etc/apt/sources.list /etc/apt/old.style.sources.list then sudo nano /etc/apt/sources.list.d/devuan.sources with this as its contents.
## Devuan 7 freia
## 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 freia sources
Types: deb
URIs: http://gnlug.org/pub/devuan/merged
Suites: freia #freia-backports freia-proposed-updates freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
## freia security sources
Types: deb
URIs: http://gnlug.org/pub/devuan/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64Then sudo apt update to refresh the mirrors package list. Once the freia is released remove the # in the Suites line to have them used and change the no to yes in the security part to enable it and you will be good to use all of them. You can change the URIs line to be http://deb.devuan.org/merged to continue using the round robin mirror selection you currently use if you wish. Also if you ever need package sources for your install the Types line can have deb deb-src there to enable the fetching of source packages.
Edit: And since you ask about upgrading then the procedure for that is before changing to the new freia sources do an sudo apt update and sudo apt upgrade to have the latest for everything installed once everything is done then sudo apt update and sudo apt full-upgrade when you have changed to the freia sources file.
Looks like you do a BIOS MBR boot method since it says nothing about adding the UEFI firmware entry. I would open up the grub.cfg and make certain the entries get created for both kernels. Then once confirmed sudo grub-install /dev/sda to have it do a new install.
Apparently grub.cfg is properly updated but grub somehow does not display the changes on the boot screen.
What makes you think that? Have you looked into the file and confirmed this? Also posting the output of the update-grub command would be helpful to be able to see what it does when it runs, mine for instance.
root@9600k:~# update-grub
Generating grub configuration file ...
Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-6.12.57+deb13-amd64
Found initrd image: /boot/initrd.img-6.12.57+deb13-amd64
Found linux image: /boot/vmlinuz-6.12.48+deb13-amd64
Found initrd image: /boot/initrd.img-6.12.48+deb13-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
doneEdit: and now I think of it.
I purged one of the previous kernels + headers (5.10.0-36) as I have always done,
What is the matter with sudo apt autoremove which would have done it by removing the third oldest entry the -35 version leaving the last two version that were installed by apt, the method of doing it in/on a Debian based system. Adding the --purge option to that command is always a good idea to get rid of the leftover cruft it leaves behind without it used.
because it apparently doesn't exist. Is it OK?
It never does until the release of the new OS is coming near. The security repository is for fixes that apply to already released software while it is a still supported version, the unreleased versions get fixed by new uploads to the development repositories. Which then find their way into the testing/unstable branches of those repositories. This is the way it has worked forever really or at least the twenty plus years I have used Debian based system.
I unchecked the MATE polkit agent, but it rechecked automatically after some reboots.
What can I do?
Remove the damn thing then it has no chance of starting again.
sudo apt remove --purge mate-polkitUsed in a Terminal to do the actual removal.
The keys you want to remove can be backed up to some other location then if needed again they can be copied back into the keyring directory.
sudo rm /etc/apt/keyrings/keyring-2022-archive.asc
sudo rm /etc/apt/keyrings/keyring-2016-archive.ascUsed in a Terminal if in old location if in the new then /usr/share/keyrings/ could be the location to remove them from.
why didn't they at the same time fix synaptic to receive them over https?
Same reason they left it unable to use the new .sources format when they shipped Trixie, they care about their users, it says so in their policies they like to quote so often...
Package libxapian30 is not installed.
Then sudo apt install libxapian30 and since the system is borked from trying to install the -dev package sudo dpkg -r --purge synaptic-build-deps you may want to do that first. This is why I dislike those GUI programs they do nothing to show you how the system works and leaves you unable to solve even the most basic of problems due to this lack of eperience.
That is not the synaptic package those are the development files you try to install. Download this package here and use the command I showed you in the last posting to install it from a Terminal.
https://download.opensuse.org/repositor … _amd64.deb
That will result in the package being installed with only seven others if memory serves me perhaps no others if you already have the Debian/Devuan package installed as it will only update the synaptic with the newer version in that case.
This is from the control file I extracted from the downloaded .deb file from that location.
Package: synaptic
Version: 0.91.7+nmu1
Architecture: amd64
Maintainer: Michael Vogt <mvo@debian.org>
Installed-Size: 7805
Depends: libapt-pkg7.0 (>= 1.9.0), libc6 (>= 2.38), libgcc-s1 (>= 3.0), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0t64 (>= 2.14.0), libgtk-3-0t64 (>= 3.21.5), libpango-1.0-0 (>= 1.14.0), libstdc++6 (>= 14), libvte-2.91-0 (>= 0.49.92), libxapian30 (>= 1.4.28~), hicolor-icon-theme, polkitd | policykit-1, pkexec | policykit-1
Recommends: libgtk3-perl, xdg-utils
Suggests: dwww, deborphan, apt-xapian-index, tasksel, software-properties-gtkVery few packages needed and looking at the same package it appears before it gets cut off by my Terminal width it is going to list exactly the same packages.
zeus@9600k:~$ apt show synaptic
Package: synaptic
Version: 0.91.7
Priority: optional
Section: admin
Maintainer: Michael Vogt <mvo@debian.org>
Installed-Size: 7,975 kB
Depends: libapt-pkg7.0 (>= 1.9.0), libc6 (>= 2.38), libgcc-s1 (>= 3.0), libgdk-p>
Recommends: libgtk3-perl, xdg-utils
Suggests: dwww, deborphan, apt-xapian-index, tasksel, software-properties-gtkSo all of them dependencies shown should already be installed on your machine, I am failing to see how it wants to install all those extra packages you say it does. The git failure in your previous posting is due to it not being installed. Show us the output of the sudo dpkg -i /path/to/downloaded/synaptic_0.91.7+nmu1_amd64.deb.
How then as you can see i cant reinstall anything?
Because you try to install the broken packages until Debian gets updated packages you will be in that situation trying to use apt. Now you can look into the /var/cache/apt/archives directory to see if those broken packages are there at an older version you can install to try and get it working. You would need to use the dpkg pckage to install them manually with a line like dpkg -i /var/cache/apt/archives/xorg_old_version.deb /var/cache/apt/archives/xfonts-scalable_old_version.deb ..... for all the packages it complains about that will not install with the new packages. This stands a chance of getting back to a working graphical system on your machine. If you get this to work then go into your sources.list or devuan.source if using that and change it to follow the testing then you should not end up with this kind of mess again. Your other option is to follow a stable system which will allow you to use it all the time without this junk happening to you.
If I do, just run these 3 commands in terminal?
Yes if you have the build-essential and build-depends for synaptic installed that should probably do it. I doubt the package you got is built for Debian 13/Devuan 6 a simulated install here shows very few packages needed for a fresh install.
root@9600k:~# agis synaptic
Installing:
synaptic
Installing dependencies:
libcairo-gobject-perl libextutils-depends-perl libglib-perl
libcairo-perl libglib-object-introspection-perl libgtk3-perl
Suggested packages:
libfont-freetype-perl dwww apt-xapian-index
libxml-libxml-perl deborphan software-properties-gtk
Summary:
Upgrading: 0, Installing: 7, Removing: 0, Not Upgrading: 1
Inst libcairo-perl (1.109-5+b1 Devuan:6.0/stable [amd64])
Inst libextutils-depends-perl (0.8002-1 Devuan:6.0/stable [all])
Inst libglib-perl (3:1.329.3-3+b3 Devuan:6.0/stable [amd64])
Inst libcairo-gobject-perl (1.005-4+b4 Devuan:6.0/stable [amd64])
Inst libglib-object-introspection-perl (0.051-2+b1 Devuan:6.0/stable [amd64])
Inst libgtk3-perl (0.038-3 Devuan:6.0/stable [all])
Inst synaptic (0.91.7 Devuan:6.0/stable [amd64])
Conf libcairo-perl (1.109-5+b1 Devuan:6.0/stable [amd64])
Conf libextutils-depends-perl (0.8002-1 Devuan:6.0/stable [all])
Conf libglib-perl (3:1.329.3-3+b3 Devuan:6.0/stable [amd64])
Conf libcairo-gobject-perl (1.005-4+b4 Devuan:6.0/stable [amd64])
Conf libglib-object-introspection-perl (0.051-2+b1 Devuan:6.0/stable [amd64])
Conf libgtk3-perl (0.038-3 Devuan:6.0/stable [all])
Conf synaptic (0.91.7 Devuan:6.0/stable [amd64])
root@9600k:~# alias agis
alias agis='apt -s install'it requires the installation of 115 additional packages. Is there a way to install it without those 115 extra things?
Yes follow the instructions on that page to build it on your system with the already existing packages you have. This is the problem with using random .deb files built by other people on their system not an exact copy of the system you are using having built it.
why no variants like "roll back" i.e. copy(replace) over my broken healthy files that not affected this bug, is it possible?
Always possible if you know the packages required to be be installed to have them used again. Then you need to stop updating the system or have put them packages on hold to stop them from being updated until new packages arrive that fix the broken mess. Either way it requires someone who knows their way around the system and the pitfalls of using it with the skills to fix it once broken.
i am ask is it fixible or not?
Eventually the bugs in it and the broken packages will be fixed, until then you get to wait for the fixes like everyone else. Running that version of the OS is only for very experienced people who are ready and able to fix these broken things themselves. A re-install of it will result in the same broken state you are in now if you want newer software with less chance of having broken packages and systems then use the testing/Freia branch this is composed of software that is just slightly older by a few days or week or two than the Ceres/unstable but only get into it if no major bugs are found in it while it is being confirmed by people not reporting any in the unstable packages. This allows you to run the newer software with greater likelihood of it being usable most of the time.
Should I purge the Synaptic now on my system, then install the fixed one?
Should just be a simple sudo dpkg -i synaptic_downloaded.deb which will overwrite the version installed. With its higher version number as it has the +nmu1 added to the version number telling the system that it is newer higher versioned packaged than the plain 0.97.1 installed now.
Why all broken?
Because it is the unstable version of the development branch of Debian being used by it. Which if you took the time to learn about it has breakages all the time. It is not for the faint of heart who want a good working system all the time this is what the stable version is for. The best strategy for running such a system is to not upgrade for days after you see the packages available while you scour the various forums and mailings list to determine what has been broken with the latest updates and if any work a rounds have been found. Especially when you have an nVidia graphics card who drivers always break with just about every new kernel update put out by such a distribution. With such a card you are set for failure on a regular basis using it.
I decided to test it for a while. What's your take?
I went with the Waterfox after going on twenty-eight years of use, since the fork from Netscape that later become Firefox, them idiots at Mozilla finally got me to give it up with this latest bunch of BS they pulled. It has been building for years now with all the trash changes they have made but that announcement was the straw that broke the camels back. The Waterfox works great everything just runs like it did except my fonts look much better for some reason, using the same ones too.
Apparently they actually listened for once when we all said "please give us a simple toggle not buried in about:config."
If they had listened they would have heard all the complaints when the first put that garbage into the browser and did bury it in about:config. All that is now is damage control now they have been seriously called out on their scummy behaviour towards us.
it seems picky with copied over .iso?
just copied over from NAS latest ubuntu 26.04 and got error when using the isoimagewriter.
If by picky you mean verifying you have a proper copy of the .iso then yeah I guess so. To get by that download 256sum file into the same directory as the .iso as it tells you to do or create it with the sha256sum program.