You are not logged in.
Just doing some investigating 'cos I'm bored so tried LightDM, i3 & thunar in my VM and trash seems to work just fine in chimaera. I "upgraded" the system to daedalus and then ceres and it works fine there as well.
Scrot or it didn't happen:
So now the question is: how exactly did you install your "daedalus/ceres" system? I used the chimaera netinstall ISO image.
Use this command to show us exactly which version is installed (which you should have done in the OP btw):
apt policyLooks like this is a PEBKAC issue ![]()
Are the kernel versions the same in both Debian and Devuan?
EDIT: find the kernel version with
uname -aBut the GPL is the reason why hardware support for Linux is so broad — if the companies want to use the licensed code then they are forced to share any changes they make afterwards.
The problem is with GVFS. It uses dbus to activate a systemd unit file.
You could try recompiling the source package with --disable-systemd:
apt source gvfs && cd "$_"-*Then edit debian/rules and change this section:
ifneq (,$(filter $(DEB_HOST_ARCH), hurd-i386 kfreebsd-i386 kfreebsd-amd64))
ADMIN_BACKEND=-Dadmin=false
SYSTEMD_FLAGS= \
-Dsystemduserunitdir=no \
-Dtmpfilesdir=no \
-Dlogind=false \
-Dgudev=false \
-Dudisks2=false \
-Dcdda=false \
-Dgphoto2=false \
-Dmtp=falseTo this:
ifneq (,$(filter $(DEB_HOST_ARCH), hurd-i386 kfreebsd-i386 kfreebsd-amd64))
ADMIN_BACKEND=-Dadmin=false
SYSTEMD_FLAGS= \
-Ddisable-systemdThen run
# apt install devscripts
# mk-build-deps --install --remove
$ rm gvfs-build-deps*
$ dch --bpo # open debian/changelog in an editor, save the file to exit
$ debuild -us -uc
# apt install ../gvfs*.deb
# apt purge --autoremove gvfs-build-deps devscriptsCareful with that --autoremove option though, it might take out your desktop if you've uninstalled any critical metapackages. Pay close attention to the output. Or leave devscripts installed if you want to keep it for any future rebuilds or package patching.
Anyway, if that gets the Trash working edit debian/changelog to change
gvfs (1.46.2-1~bpo11+1) bullseye-backports; urgency=mediumto
gvfs (1.46.2-1.1) bullseye-backports; urgency=mediumThen rebuild the packages again and install them. You'll have to repeat this whenever the GVFS packages are updated.
If it doesn't work then reinstall the stock packages:
# apt update
# apt full-upgradeHow about running /usr/libexec/gvfsd from a terminal? Does that do anything?
You sure?
Yes. All true UNIX systems provide a unified set of user space tools along with /sbin/init. The BSDs are closer to true UNIX than Linux so they emulate that approach.
I made no comment about commercial influences.
I will now though:
http://www.openbsdfoundation.org/contributors.html ← both Google and Microsoft are regulars in that list.
https://freebsdfoundation.org/our-donors/donors/ ← Facebook as a top level contributor? Really? ![]()
Add this line to ~/.xsessionrc:
/usr/libexec/gvfsd &You might also need
/usr/libexec/gvfsd-trash &The gvfsd daemon is started with a systemd unit file, which is why it's not working in Devuan.
Don't be silly. Governments put backdoors in places like hard drive controller firmware where the operating system is irrelevant. EDIT: that even works with coreboot ![]()
Which desktop is this? Is it Xfce?
Are the brightness keys recognised if you run
xev^ That command is provided by the x11-utils package.
You may find that FreeBSD and probably OpenBSD are ten years behind Linux.
Not really. I don't know about FreeBSD but OpenBSD works just fine on my brand new Ryzen 5850U laptop. The 7.0 release brought in the DRM stack from Linux 5.10.65 and so supports Intel Tiger Lake and AMD Navi 12 & 21 "Sienna Cichlid", Arcturus & Cezanne "Green Sardine" GPUs. And in my experience although hardware support for OpenBSD isn't as broad as with Linux the quality and longevity is *much* better. YMMV.
A word of warning though: opponents of systemd probably won't like the BSDs because all of the user space utilities are developed by the exact same team that provides /sbin/init, just like with Lennart & co... [/troll]
[1257191.630039] mmc0: new high speed SDHC card at address 59b4 [1257191.630340] mmcblk0: mmc0:59b4 00000 7.35 GiB [1257191.649111] mmcblk0: p1 [1257192.028782] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
So the card is actually assigned to /dev/mmcblk0 then? I presumed it was in a card reader or something.
Did you try using dd and/or wipefs on /dev/mmcblk0? Use dmesg to confirm the block device after inserting the card and before attempting to wipe it.
I presume you're starting Thunar with --daemon?
If so then try this wrapper script at /usr/local/bin/thunar:
#!/bin/sh
if [ "$1" = --daemon ] ; then
until pgrep gvfs >/dev/null ; do
sleep 1
done
exec /usr/bin/Thunar "$@"
else
exec /usr/bin/Thunar "$@"
fi^ That ensures Thunar is started after GVFS. Make sure it's executable (chmod +x /usr/local/bin/thunar).
If you share exactly how you are starting the graphical desktop I might be able to provide a better solution.
The dmesg dump is quite large, how much of it is needed? last 20 lines? last 50 or 100?
Remove the SD card then open a terminal and run this command (as root):
dmesg -wThen insert the SD card and only post any new output that appears in the terminal after you insert the card.
Technical explanation here:
https://blog.qualys.com/vulnerabilities … -2021-4034
Of particular note:
we note that OpenBSD is not exploitable, because its kernel refuses to execve() a program if argc is 0
Puffy ftw! ![]()
Anyway it's only a local vulnerability with a severity of 7.8. Ho hum.
EDIT:
is it really a systemd specific problem?
Nope.
As noted above OpenBSD has polkit but that OS is fundamentally incompatible with systemd, as is Alpine Linux.
But (in my opinion) wipefs is a very powerfool tool and --backup gives the user a false sense of security by presenting a remedy/insurance of sorts to not having been thorough enough.
But it's not a "false" sense of security because the remedy actually works.
[wall of meaningless text]
Why are you not providing the requested fdisk and dmesg output? Is this a wind-up? It's certainly winding me up...
Anyway good luck. I'm out.
I have had those lines in my /home/glenn/.asoundrc for quite some time ... it didn't iron out any wrinkles for my system.
That's not really surprising because as I explained above that file does absolutely nothing at all. All it does is set card "0" as the default output but ALSA names the default card "0" so it's already set.
You probably want:
defaults.pcm.card 1
defaults.ctl.card 1^ That works for every laptop I have ever owned that has an HDMI audio output. It sets the analogue card as the default and so makes FF produce sound without needing PulseAudio to hold your hand.
EDIT: this was clearly explained in the ArchWiki link I gave earlier but obviously clicking on a link is far too much work... ![]()
There's no turning back from wipefs.
Yes there is — that's what the --backup option is for. The man page explains what it does and how to use the backup file to restore the magic strings to a device.
Did you reboot after using dd?
This command should make the kernel aware of the new (lack of) partition table on the device without needing to reboot:
# partprobe /dev/sdcThe partprobe command is supplied by the parted package.
If that still doesn't work then try clearing any magic strings with
# wipefs --all --backup /dev/sdcIf you accidentally target the wrong drive the strings can be restored by referring to the EXAMPLES section of man wipefs.
And if the device still seems to have files on it even after using wipefs then please share the fdisk output requested above and also the content of dmesg after plugging in the device.
I think that option is already set by default. Or at least it is in my Arch box and Devuan chimaera VM (when I load the module).
Check
cat /sys/module/usbcore/parameters/use_both_schemes@OP: can we see the error message(s) in full please? What is the nature of the USB device in question?
But card 0 is always the default anyway, that's why it's called "0" ![]()
Just remove the file.
Yeah, resolvectl(1) is part of the systemd conglomerate so it would be worrying if it was found.
You can stop resolvconf(8) from managing /etc/resolv.conf by adding this line /etc/resolvconf.conf:
resolvconf=NOSee https://wiki.debian.org/resolv.conf for more on this.
EDIT: in case you're wondering what you're missing:
$ resolvectl
Global
Protocols: -LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported
resolv.conf mode: stub
Current DNS Server: 9.9.9.10#dns.quad9.net
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.10#dns.quad9.net 8.8.8.8#dns.google
2606:4700:4700::1111#cloudflare-dns.com 2620:fe::10#dns.quad9.net
2001:4860:4860::8888#dns.google
Link 2 (enp2s0f0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported
Link 3 (enp5s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported
Link 4 (wlan0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS +DNSOverTLS DNSSEC=yes/supported
$As you can see it's a really nice tool: a caching resolver with full support for DNSSEC, LLMNR, mDNS and DNS over TLS.
It "works" in chimaera but the .deb is missing a dependency for libasound2 so that needs to be installed manually. Gives some idea of the quality of the packaging, I think.
I ran lintian on the .deb, just for a laugh:
E: code: arch-dependent-file-in-usr-share usr/share/code/chrome-sandbox
E: code: arch-dependent-file-in-usr-share usr/share/code/code
E: code: arch-dependent-file-in-usr-share usr/share/code/libEGL.so
E: code: arch-dependent-file-in-usr-share usr/share/code/libGLESv2.so
E: code: arch-dependent-file-in-usr-share usr/share/code/libffmpeg.so
E: code: arch-dependent-file-in-usr-share usr/share/code/libvk_swiftshader.so
E: code: arch-dependent-file-in-usr-share usr/share/code/libvulkan.so.1
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/sqlite.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/keytar/build/Release/keytar.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/keytar/build/Release/obj.target/keytar.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/native-is-elevated/build/Release/iselevated.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/native-watchdog/build/Release/watchdog.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/vscode-encrypt/build/Release/vscode-encrypt-native.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/vscode-nsfw/build/Release/nsfw.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/windows-foreground-love/build/Release/foreground_love.node
E: code: arch-dependent-file-in-usr-share usr/share/code/resources/app/node_modules.asar.unpacked/windows-foreground-love/build/Release/obj.target/foreground_love.node
E: code: arch-dependent-file-in-usr-share usr/share/code/swiftshader/libEGL.so
E: code: arch-dependent-file-in-usr-share usr/share/code/swiftshader/libGLESv2.so
E: code: description-starts-with-package-name
E: code: embedded-library usr/share/code/code: freetype
E: code: embedded-library usr/share/code/code: libjpeg
E: code: embedded-library usr/share/code/code: libjsoncpp
E: code: embedded-library usr/share/code/code: libpng
E: code: embedded-library usr/share/code/code: srtp
E: code: executable-desktop-file usr/share/applications/code.desktop 0755
E: code: missing-dependency-on-libc needed by usr/share/code/chrome-sandbox and 22 others
E: code: no-changelog usr/share/doc/code/changelog.Debian.gz (non-native package)
E: code: no-copyright-file
E: code: shared-library-is-executable usr/share/code/libEGL.so 0755
E: code: shared-library-is-executable usr/share/code/libGLESv2.so 0755
E: code: shared-library-is-executable usr/share/code/libffmpeg.so 0755
E: code: shared-library-is-executable usr/share/code/libvk_swiftshader.so 0755
E: code: shared-library-is-executable usr/share/code/libvulkan.so.1 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/sqlite.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/keytar/build/Release/keytar.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/keytar/build/Release/obj.target/keytar.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/native-is-elevated/build/Release/iselevated.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/native-watchdog/build/Release/watchdog.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/vscode-encrypt/build/Release/vscode-encrypt-native.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/vscode-nsfw/build/Release/nsfw.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/windows-foreground-love/build/Release/foreground_love.node 0755
E: code: shared-library-is-executable usr/share/code/resources/app/node_modules.asar.unpacked/windows-foreground-love/build/Release/obj.target/foreground_love.node 0755
E: code: shared-library-is-executable usr/share/code/swiftshader/libEGL.so 0755
E: code: shared-library-is-executable usr/share/code/swiftshader/libGLESv2.so 0755
E: code: statically-linked-binary usr/share/code/resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg
E: code: unknown-control-interpreter control/postinst #!/usr/bin/env
E: code: unknown-control-interpreter control/prerm #!/usr/bin/env
E: code: unstripped-binary-or-object usr/share/code/chrome-sandbox
E: code: unstripped-binary-or-object usr/share/code/code
E: code: unstripped-binary-or-object usr/share/code/libEGL.so
E: code: unstripped-binary-or-object usr/share/code/libGLESv2.so
E: code: unstripped-binary-or-object usr/share/code/libffmpeg.so
E: code: unstripped-binary-or-object usr/share/code/libvk_swiftshader.so
E: code: unstripped-binary-or-object usr/share/code/libvulkan.so.1
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/@parcel/watcher/build/Release/watcher.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/@vscode/sqlite3/build/Release/sqlite.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/keytar/build/Release/keytar.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/keytar/build/Release/obj.target/keytar.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/native-is-elevated/build/Release/iselevated.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/native-keymap/build/Release/keymapping.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/native-watchdog/build/Release/watchdog.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/vscode-encrypt/build/Release/vscode-encrypt-native.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/vscode-nsfw/build/Release/nsfw.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/vsda/build/Release/vsda.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/windows-foreground-love/build/Release/foreground_love.node
E: code: unstripped-binary-or-object usr/share/code/resources/app/node_modules.asar.unpacked/windows-foreground-love/build/Release/obj.target/foreground_love.node
E: code: unstripped-binary-or-object usr/share/code/swiftshader/libEGL.so
E: code: unstripped-binary-or-object usr/share/code/swiftshader/libGLESv2.so
W: code: appstream-metadata-in-legacy-location usr/share/appdata/code.appdata.xml
W: code: executable-not-elf-or-script usr/share/applications/code.desktop
W: code: executable-not-elf-or-script usr/share/code/resources/app/out/vs/workbench/browser/parts/editor/media/letterpress-dark.svg
W: code: executable-not-elf-or-script usr/share/code/resources/app/out/vs/workbench/browser/parts/editor/media/letterpress-hc.svg
W: code: executable-not-elf-or-script usr/share/code/resources/app/out/vs/workbench/browser/parts/editor/media/letterpress.svg
W: code: executable-not-elf-or-script usr/share/code/resources/app/resources/linux/code.png
W: code: executable-not-elf-or-script usr/share/pixmaps/com.visualstudio.code.png
W: code: maintainer-script-ignores-errors postrm
W: code: setuid-binary usr/share/code/chrome-sandbox 4755 root/rootIdiots.
Note that it silently fails under Wayland even if xwayland is installed and also that it adds Microsoft's repositories to the system, which I consider to be an act of vandalism.
is there a good [...] alternative ?
Looks like the certificate ran out today just before lunch. Time to get a new one from Let's Encrypt...