You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: DIY » Announcement of the OpenMATE desktop environment » 2024-02-02 06:03:16
The github link is now broken; is the project cancelled?
#2 Re: Devuan » Wifi setup in devuan » 2023-12-29 06:06:41
I think if you use apt pinning of the current repos to be over 1000, it will downgrade, quickfur.
#3 Re: Installation » Bookworm -> Daedalus migration nscd network-manager failed » 2023-12-28 20:07:13
Oh, sorry, I misunderstood twice that it was required. First in the sticky, then in here.
#4 Re: Installation » Bookworm -> Daedalus migration nscd network-manager failed » 2023-12-28 05:16:07
Yes, that is the one I read; task-mate-desktop kept removing libsystemd0. Now, when I try to install libsystemd0, it wants to remove task-mate-desktop, mate-desktop-environment, mate-desktop-environment-core, caja, gvfs-backends, mate-applets, gvfs, gvfs-daemons, gvfs-fuse, udisks2, network-manager-gnome, network-manager, libpam-elogind, and libelogind-compat
I am currently booted without libsystemd0 because it apparently conflicts, either directly or indirectly, with these packages. I do not think libsystemd0 is harmful, but I seem to be unable to have it, as holding it when installed would not allow installing these packages (well, dummy-elogind allowed some of them, but not all).
#5 Re: Devuan » Wifi setup in devuan » 2023-12-28 02:50:23
This is not important, but is it possible to get this to show up on wifi indicator applets? If not, I may (depending on free time next semester) try to edit the mate applet showing wifi to have a gui for this.
#6 Re: Installation » Bookworm -> Daedalus migration nscd network-manager failed » 2023-12-28 02:42:10
Alright, I've had it fixed for a day, but I just now fixed the DE and halfway fixed the internet. Thank you everyone.
I misunderstood the sticky on systemd mentioning libsystemd0 being used sometimes to determine if systemd was running, and thought that this package was necessary, so I tried to use the dummy-elogind, but this would not allow some packages that were part of task-mate-desktop, so I had a partial de install and dummy-elogind. Fortunately, I figured it out when I looked into what would break when I removed libsystemd0. My wifi applet does not work (that is okay; I don't necessarily need a gui for it as long as it works), but I followed the excellent guide by quickfir and got it working (the only difference was I had to use apt-file to locate iwconfig and ifup... now they work). If I have time next semester, I may try to edit the applet to get a gui method for this workaround.
#7 Re: Installation » Bookworm -> Daedalus migration nscd network-manager failed » 2023-12-27 00:19:20
Thank you! Should I continue where I left off, or do I need to force upgrade the packages that did not upgrade and then reboot again?
#8 Installation » Bookworm -> Daedalus migration nscd network-manager failed » 2023-12-26 01:09:57
- paculino
- Replies: 8
Today I started to migrate my Debian bookworm installation (using stable, updates, security, and one package from backports) to daedalus. In preparation, I fully cloned it and booted into both the original and the clone using the grub installed in my old KDE Neon install (which I am now using). After seeing that both worked, I followed the migration guide. Initially, after the apt upgrade, I noticed that a few packages were upgradable but not upgraded (dbus-bin, dbus-daemon, dbus-x11, dbus, libdbs-1-3, and init... also octave*). However, looking ahead I saw -f install, rebooting, purging, and autocleaning, so thought that maybe this was as intended. I suspect this is where I made a mistake. Installing eudev and sysvinit-core did force init to install without me manually doing that. Rebooting after the -f install I had a headless install, as expected (I use mate), but it said at the top
startpar: services returned failure: nscd network-manager . . . failed* octave is upgradable but not upgraded since I edited the .deb from the debian repo to remove the gui since I use geany for it and have no qt except on the neon install; I highly doubt this has any effect but am telling out of precaution
Now, what would be the safest way to continue? I chrooted into it to get that list of upgradable and not upgraded packages (I'm lazy and didn't write it down), and could install that way, similar to installing enough packages to set up wifi on a debootstrap-install. Alternatively, I could download the remaining packages and install them when truly booted into that install (well, efibootmgr will say I'm booted into neon since I'm using this grub to avoid ambiguities for the time being, but I assume it is okay since grub gets me in the correct one). I do not like the other options of using the clone or cloning the clone over this attempt, because I want to keep at least one working debian/devuan install at all times and cloning takes a day and a half. Is it safe to continue the migration from a chroot (since I already rebooted), at least enough to get wifi working? This is my preferred method as it is easiest.
Pages: 1
Board footer
