You are not logged in.
Hello:
How can I fix this?
You may be able to solve it by first manually installing the dependency.
ie: libwacom-common (= 2.6.0-1)
Once installed and present in the system, the dist-upgrade should go smoothly as apt will find it and proceed.
See:
https://pkginfo.devuan.org/cgi-bin/poli … 1.84.27.71
https://packages.debian.org/bookworm/libwacom-common <- 2.14.0-1
https://packages.debian.org/trixie/libwacom-common <- 2.6.0-1
If that does not work, you may have to uninstall whatever requires libwacom-common before the dist-upgrade.
See here: https://packages.debian.org/search?suit … s=libwacom
It would seem that libwacom2 in Chimaera has been replaced with libwacom9 in Daedalus, Excalibur and Ceres.
See
https://pkginfo.devuan.org/cgi-bin/poli … 1.84.27.71 <- Chimaera and earlier
https://pkginfo.devuan.org/cgi-bin/poli … 1.84.27.71 <- Daedalus and later
Let us know how you fared with this.
Best,
A.
Hello:
... a bug in the installer?
Hmm ...
You may want to consider the possibility of the Excalibur installer becoming self-aware.
And as a result, defending itself from XFCE.
Just taking the piss ...
Best,
A.
Hello:
... if deb.devuan.org isn't working out for them.
I do not recall ever having had any issues with deb.devuan.org*, save for those generated by my FO service provider. 8^°
* ie: -34.60° lat -58.38° long
Best,
A.
Hello:
... and not be held back by trying to shoehorn modern software on retro computing devices.
Of course ... 8^°
--->
Tech *bros* have to make a living.
Make ends meet, if you will.
Have you not been observing?
There are still many landfills to fill.
<---... would tell you this is great news ...
Yes, he would.
I take small confort in the fact that Civilisation (in general) has always had an incredibly over-abundant supply of [braindead / stupid / DHs / AHs]*.
That little snippet from the debian_dev only confirms it.
* choose one, a combination of two or even three. But a combination of four is not an option, lest depression set in.
Best,
A.
Hello:
... not in the menus and not found by a file search or by command line.
You may want to run a fine tooth comb through all your logs, just in case.
There has to be / should be some indication as to what transpired when you installed it.
Should not be an issue if you got it from the Devuan repository,but still.
Have a look here: https://linux.die.net/man/8/tcplay
Best,
A.
Hello:
Might be a longshot, but ...
I had thought of doing that but decided not to bother the chap with this.
But seeing that I have not made much progress, I just fired a short one asking.
Hopefully he will pitch in.
Best,
A.
Hello:
... obmenu2 on Crowz, try downloading tarbal ...
... also : https://github.com/keithbowes/obmenu
Thanks, saw those already.
But I was wanting to have the #! *.deb file to directly install in my upcoming Daedalus test.
And try it out on my Devuan Chimaera i386 1000HE installation.
Not sure what Miyo meant by downloading a .deb from an install ...
Hmm ...
Exactly that? Maybe ...
I don't have an installation, just a live i386 *.iso and I haven't seen it there.
Thanks for your input.
Best,
A.
Hello:
maybe it's from ...
Yes, I'm quite sure of that as it seems (?) to be of their own production.
And it is part of the #! installation, at least for Bookworm.
But I have not seen it available for download or found it within the live i386 *.iso.
Thanks for your input.
Best,
A.
Hello:
here are some additional info
Thanks for that. 8^)
But what I am interested in is knowing if / how the OP actually solved the issue.
Or not and what steps he took while attempting to do it.
All useful information for the forum.
ie: towards getting Devuan installed on a Mac.
Best,
A.
Hello:
A long time ago, this thread came to my attention:https://dev1galaxy.org/viewtopic.php?id=4897
MiyoLinux posted this:
... #!++ has repackaged obmenu to work on newer systems using python3.
... downloaded the .deb file from my installation of #!++, and I've installed it on Chimaera, Daedalus, and Ceres...it works perfectly ...
I have a live i386 CBPP / #! *.iso which works perfectly well but I cannot find the *.deb file mentioned by MiyoLinux.
Any idea as to how I can get a hold of it?
I want to test it on a Daedalus VM as a possible transition away from XFCE.
Best,
A.
Hello:
@deviate
Try adding this stanza to the kernel command line: ACPI_OSI=Darwin
See here: https://wiki.archlinux.org/title/MacBookPro11,x
Did you get your Mac / ACPI issue worked out?
Whatever data you have been able to gather will be useful to others.
Best,
A.
Hello:
What a wonderful story!
Indeed. 8^D
And a just reward for your volunteer work too.
Best,
A.
Hello:
"Fun" is something subjective, obviously.
Indeed ...
Just like the "utility" of systemd. 8^°
Best,
A.
Hello:
... any extra obstacles with excalibur?
Yes.
A non-zero chance of there being extra obstacles is to be expected with a testing Suite.
ie: Maintained but Not Released status
testing is where the next stable suite is developed. Software is usually more up-to-date but there may still be issues. testing becomes stable “when it is ready”.
Backports is the safe route, Excalibur means a slightly higher risk ...
+1
Best,
A.
Hello:
thanks ...
You're welcome
... can't get apt to update from the obsolete libupower-glib1 ...
I see ...
And if you try to purge it, it nukes the whole shebang.
A sticky wicket ...
Just an idea:
Since apt will not (for whatever reason) update libupower-glib1, you may want to try some other way to do it.
First check that your etc/apt/sources.list file does not have anything but daedalus repositories.
ie: sometimes shit does happen. 8^°
Then see if you can get around apt upgrade not doing the job by resorting to apt install:
eg:
apt install -s libupower-glib3 # <- simulation modeIt may well replace the old version. (?)
Please let us know how you fared.
Best,
A.
Hello:
my daedalus vm has been upgraded since ascii.
Same for my Daedalus installation with the exception of it not being a VM.
$ uname -a
Linux devuan 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/Linux
$ ... checked for obsolete packages ...
For whatever reason, I have quite a few of those packages ...
$ apt list '~o'
--- snip ---
libssl1.1/now 1.1.1w-0+deb11u1 amd64 [installed,local]
libswresample3/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
###### <--- would have been listed here
libvpx6/now 1.9.0-1+deb11u2 amd64 [installed,local]
libwebp6/now 0.6.1-2.1+deb11u2 amd64 [installed,local]
--- snip ---
$ ... but libupower-glib1 is not one of them.
$ apt list '~o' | grep libupower-glib1
--- snip ---
$ That said, I do have libupower-glib3 installed ...
$ apt list | grep installed | grep libupower
--- snip ---
libupower-glib3/stable,now 0.99.20-2 amd64 [installed,automatic]
$ $ aptitude why libupower-glib3
i task-desktop Depends xorg
i A xorg Depends xinit
i A xinit Recommends xterm | x-session-manager | x-window-manager | x-terminal-emulator
i A xfce4-session Provides x-session-manager
i A xfce4-session Depends xfce4-settings
i A xfce4-settings Depends libupower-glib3 (>= 0.99.0)
$ ... but no upower:
$ apt list | grep installed | grep upower
--- snip ---
libcpupower1/stable-security,now 6.1.153-1 amd64 [installed,automatic]
libupower-glib3/stable,now 0.99.20-2 amd64 [installed,automatic]
linux-cpupower/stable-security,now 6.1.153-1 amd64 [installed]
$ $ apt-cache policy upower
upower:
Installed: (none)
Candidate: 0.99.20-2
Version table:
0.99.20-2 500
500 http://deb.devuan.org/merged daedalus/main amd64 Packages
$ That upower package is a recommends from the hw-probe package which I do have installed ...
$ apt list | grep installed | grep hw-probe
--- snip ---
hw-probe/stable,stable,now 1.6.5-1 all [installed]
$ $ aptitude why upower
i hw-probe Recommends upower
$ ... but I do not allow recommends in my system.
Unless I am mistaken, your 'Installed' version is the same as your 'Candidate' version:
ie: apt says that is the correct version to have in your system.
Installed: 1:0.9.23-2+devuan1.3
Candidate: 1:0.9.23-2+devuan1.3Being a recommends and not a hard dependency, you probably don't need it.
You may want to try purging the upower package and see if the obsolete package gets purged along with it.
Then if you get complaints from the system, just reinstall it and see what gets dragged in along with it.
Please let us know how you fared.
Best,
A.
Hello:
... shops here have mostly kingston drives ...
Same here, but without an official representative so it is more or less the wild west.
Not to mention all the fake/counterfeit crap with different brands stamped on them.
Moot point now as in light of my recent experience, Kingston is no longer the go-to brand I had purchased for almost 20 years without a second thought.
Not for USB sticks or SSDs for that matter.
Kingston has now gone the way of Seagate, Hewlett Packard, Texas Instruments, Sony and others.
The purchase of RAM sticks/modules is another matter as I expect that OEM branded hardware will be (?) properly specced, albeit more expensive.
Nowdays we will have to rely heavily on independent testing from whoever does that reliably.
ie: not sponsored or on a payroll.
With respect to IT gear, trust is something that takes a long time to build but once it is lost, that is that.
As always, YMMV.
Best,
A.
Hello:
... see also this forum thread ...
Yes.
As the OP, I was the one that posted a link to this thread on that one. 8^D
Best,
A.
Hello:
... came that way.
I see.
I assume it came in a sealed blister package without any indication of use.
I have never seen a USB drive with what you see in your fdisk printout but one never knows.
I have read that memory prices are surging lately, mainly due to dwindling stocks and foundry production having reached their limit.
It would be interesting to know the brand/model of your USBs.
It may well be that (for whatever commercial reason) the chip in the 128Gb drive is a higher capacity (eg: 256Gb or higher) but with the firmware blocking access to those sectors due to it being sold at 128Gb prices or because it is damaged and instead of binning it, the OEM decided to sell it as a 128Gb device.
That said, the only (?) answer to your OP may lie in checking the drive as suggested.
ie: a read-only check on it with dosfsck and looking at what the gnome-disk-utility says about it.
You may also want to check read/write speeds with the gnome-disk-utility, I had a nasty surprise from Kingston some time ago.
If interested see here: https://dev1galaxy.org/viewtopic.php?id=7264
Whatever the result, do let us know what you find out.
Best,
A.
Hello:
... 128 GB drive is the one ...
Is this how it came 'out-of-the-box' or did you format it?
You may want to run a read-only check on it with dosfsck and/or have a look at it with the gnome-disk-utility
It shows things that Gparted will not.
Best,
A.
Hello:
... where you want to alliow someone to carry out a specific task ...
Exactly what it was written for.
I have a long list in sudoers.d, some with, some without PW, for myself.
As an added value, the auditing is also a helpful tool for remembering what was and when.
PCLinuxOS devs make the point quite well: https://pclosmag.com/html/Issues/201205/page11.html
Best,
A.
Hello:
... zram and zstd ...
... aren't these useful?
Yes, depending on your box and hardware, they can be very useful.
See:
https://wiki.debian.org/ZRam
https://dev1galaxy.org/viewtopic.php?id=4800
https://linuxblog.io/running-out-of-ram-linux-add-zram/
What can I remove?
That's a more difficult question which requires some research on your part.
First you need to check and see what modules are being loaded by your system.
Then check if you are actually using them.
Done that, evaluate the convenience of removing them or not.
ie: just what is the upside to doing it.
It is not hard to do: just needs work but you will learn quite a bit in the process.
See:
https://www.tecmint.com/remove-unwanted … rom-linux/
Make sure to search Dev1 on how to unload/remove* modules in a Devuan (sysvinit) system.
Debian (systemd) based installations do it according to how their installation works.
Best,
A.
* do remember to back up your system first and also make notes. ie: log your actions
Hello:
Thanks for keeping us all together ...
+1 8^)
Best,
A.
Hello:
... euthanize all the "excess load" ...
Really?
Well ...
The numbers will undoubtedly be stacked against us.
But should it actually come to that, I know how to use a 12 gauge well enough.
I will not go quietly.
But when all is said and done and the dust settles down, those who waited and voted in favour will ultimately perish.
They will not know how to survive in the world they created.
The irony is that it will be a world which we actually enabled them to create.
Among other things, through our generation's lack of values, empathy, education and basic common sense.
Right ...
Enough OT* for today.
Time to step off my box, take my pill and go for a walk.
Best,
A.
* not entirely, you know what I mean.
Hello:
... really a fix, or whether it breaks something else.
Good question ...
And that's exactly what release candidates* are for: finding the answer/s. ;^ )
* testing cycles prior to finally releasing Excalibur to stable.
There's nothing to be nervous about, just have to be patient.
Best,
A.