trash on thunar (dwm & i3wm)

manyroads · 2022-01-28 17:53:36

For some reason, I lose Trash on Thunar when running sysvinit on my Devuan dwm or i3wm installs. This is true even though the Trash folder remains intact. When I attempt to install gvfs I get the following message:

gvfs is already the newest version (1.48.1-2)

Any ideas or help are appreciated.

=================

System:
  Kernel: 5.15.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: dwm 6.3 vt: 7 dm: LightDM 1.26.0
    Distro: Devuan GNU/Linux 5 (daedalus/ceres)
Machine:
  Type: Laptop System: Dell product: Inspiron 5493 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0M4FW1 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.8.0 date: 03/24/2020
Battery:
  ID-1: BAT0 charge: 33.7 Wh (100.0%) condition: 33.7/42.0 Wh (80.2%)
    volts: 12.6 min: 11.4 model: BYD DELL 1VX1H9A type: Li-ion serial: <filter>
    status: Full
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: Discharging
CPU:
  Info: quad core model: Intel Core i5-1035G1 bits: 64 type: MT MCP
    smt: enabled arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 6 MiB
  Speed (MHz): avg: 830 high: 1187 min/max: 400/3600 cores: 1: 804 2: 874
    3: 754 4: 546 5: 1187 6: 816 7: 908 8: 751 bogomips: 19046
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel
    bus-ID: 00:02.0 chip-ID: 8086:8a56 class-ID: 0300
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-6:4 chip-ID: 0c45:671e class-ID: 0e02
  Display: x11 server: X.Org 1.20.14 compositor: xcompmgr driver:
    loaded: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
    s-dpi: 96
  OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.6
    direct render: Yes
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:34c8
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-3-amd64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: yes
  Sound Server-3: PipeWire v: 0.3.43 running: no
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
    driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8136
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0
    chip-ID: 168c:0042 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:5
    chip-ID: 0cf3:e009 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
    bt-v: 2.1 lmp-v: 4.2 sub-v: 25a hci-v: 4.2
Drives:
  Local Storage: total: 1.84 TiB used: 1.21 TiB (65.9%)
  ID-1: /dev/nvme0n1 vendor: Silicon Power model: SPCC M.2 PCIe SSD
    size: 953.87 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: ECFM22.5 temp: 26.9 C scheme: GPT
  ID-2: /dev/sda vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 043 scheme: GPT
Partition:
  ID-1: / size: 936.39 GiB used: 620.11 GiB (66.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 8.6 MiB (1.7%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 977 MiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 65.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 243 Uptime: 18m wakeups: 4 Memory: 23.26 GiB
  used: 2.26 GiB (9.7%) Init: SysVinit v: 3.00 runlevel: 2 default: 2
  Compilers: gcc: 11.2.0 alt: 11 Packages: 2018 apt: 2006 flatpak: 12
  Shell: Bash v: 5.1.16 running-in: st inxi: 3.3.12

Last edited by manyroads (2022-01-28 17:54:08)

Head_on_a_Stick · 2022-01-28 20:32:52

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.

Last edited by Head_on_a_Stick (2022-01-28 20:33:26)

manyroads · 2022-01-28 22:17:49

@Head_on_a_Stick Here is how I start i3wm (via LightDM):

[Desktop Entry]
Name=i3
Comment=improved dynamic tiling window manager
Exec=i3
TryExec=i3
Type=Application
X-LightDM-DesktopName=i3
DesktopNames=i3
Keywords=tiling;wm;windowmanager;window;manager;

and for dwm I start that via this 'autostart.sh' also called via LightDM

#! /bin/sh
#
# 		 dwm autostart, etc.
#
# Numerous functions (autostart) are located in .xsessionrc (Debian) .xprofile (arch)
# including power management, polkit, dropbox, f.lux, dunst etc.

# conky 
pkill conky 
conky -c ~/.local/bin/Suckless/dwm/conky/.dwm-1rc &
conky -c ~/.local/bin/Suckless/dwm/conky/.dwm-2rc &
~/.local/share/scripts/xsetroot.sh &

# Dropbox
DISPLAY= dropbox start -i &

#start dwm
exec dwm

Head_on_a_Stick · 2022-01-28 22:52:19

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.

manyroads · 2022-01-28 23:31:18

@Head_on_a_Stick... I tried the above on both dwm and i3wm. Things still don't work. As you implied when I encounter the problem on MX, I just boot with systemd and everything works fine. Obviously I don't have that option here.

Last edited by manyroads (2022-01-28 23:32:41)

Head_on_a_Stick · 2022-01-28 23:37:27

How about running /usr/libexec/gvfsd from a terminal? Does that do anything?

manyroads · 2022-01-28 23:46:30

When I run it (after booting with your above commands) I get

mark@devuan:~$ /usr/libexec/gvfsd
Failed to acquire daemon name, perhaps the VFS daemon is already running?

manyroads · 2022-01-28 23:48:09

I think it might be a thunar bug (when running SysV).

manyroads · 2022-01-28 23:51:40

Nope the error is reproducible in PCmanFM and nemo....

Head_on_a_Stick · 2022-01-29 11:06:28

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=false

To this:

ifneq (,$(filter $(DEB_HOST_ARCH), hurd-i386 kfreebsd-i386 kfreebsd-amd64))
        ADMIN_BACKEND=-Dadmin=false
        SYSTEMD_FLAGS= \
                -Ddisable-systemd

Then 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 devscripts

Careful 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=medium

to

gvfs (1.46.2-1.1) bullseye-backports; urgency=medium

Then 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-upgrade

Last edited by Head_on_a_Stick (2022-01-29 11:30:48)

Head_on_a_Stick · 2022-01-29 17:00:03

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 policy

Looks like this is a PEBKAC issue

manyroads · 2022-01-29 19:20:35

Here is what I get:

Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 https://repo.skype.com/deb stable/main amd64 Packages
     release o=. stable,a=stable,n=stable,l=. stable,c=main,b=amd64
     origin repo.skype.com
 500 http://deb.devuan.org/merged daedalus/main amd64 Packages
     release v=5.0,o=Devuan,a=testing,n=daedalus,l=Devuan,c=main,b=amd64
     origin deb.devuan.org
Pinned packages:

manyroads · 2022-01-29 19:24:26

FWIW... I prefer "loose nut on the keyboard" to PEBKAC...

Head_on_a_Stick · 2022-01-29 19:53:37

^ Lol. Indeed

So how did you install ceres then?

And what do you mean by "I lose Trash on Thunar", exactly? What behaviour do you expect to see and in what way does the observed behaviour differ?

You can use this to check what has been installed from that Skype repository:

aptitude search '?narrow(?installed, ?origin(. stable))'

^ That should just show skypeforlinux. Hopefully. I would just use chromium for Skype, or even the flatpak, but you might be comfortable handing over the keys to your system to the repository maintainers.

manyroads · 2022-01-29 20:32:53

I installed the liveUSB for Devuan (chimaera) and then replaced the repos for chimaera with daedalus (testing). I then performed a full-upgrade. Nowhere along the line does Trash function for me on my machine unless I use systemd.

Interestingly when I use MX it does not have functioning trash (when booted usingsysv-init); identical with Devuan. However, MX when booted with systemd has normally functioning Trash. Debian also works just fine in it's systemd incarnation.

In all cases, the trash folder remains existent in my .local/share folder. On MX, a boot/ reboot between systemd- sysvinit on the same machine (minutes apart) has the trash folder appear/ disappear. FWIW. I, also, either loose or have the delete/trash maintenance options appear/disappear in accordance with the Trash folder. (Exists in systemd booted envirnment, not in the non-systemd incarnation.)

I tried the following file managers with the exact same results:
PCmanFM, nemo, nautilus...

It all makes me happier when using systemd.....

Head_on_a_Stick · 2022-01-29 22:49:27

manyroads wrote:

functioning trash

^ What does this mean? You will have to explain it to me in as much detail as possible because I don't use graphical file managers so I have no idea how "trash" is supposed to work.

When I load up devuan_chimaera_4.0.0_amd64_desktop-live.iso in a VM I can navigate to the "Trash" [sic] side pane shortcut (identified as trash:/// in the location bar) and if I highlight a file elsewhere and press the <Delete> key the file appears in the trash:/// location so it seems to work but perhaps I am misunderstanding.

manyroads · 2022-01-29 23:15:55

@Head_on_a_stick You got it.... Functioning Trash to me means when I setup Thunar I get the option to either move an item into Trash or Delete it (bypassing Trash). Right now on Devuan and MX (sysV init) I do NOT have the option to place items into Trash and delete them later. I can only Delete (now).

trash:/// is actually located at $Home/.local/share/Trash.

Whether or not I have 'functioning' trash, the folder exists on both (Devuan and MX). It only functions on systemd MX.

Later that same day in a city 'not far away'... I decided to try and see what happens with antiX21 (runit). It works just fine. Trash functions exactly as it should. Aside from my lack of skills and manually dexterity, I am left thinking the problem has to do with sysV init. I think gvfs does not like sysV.

I am left wondering.... "How many angels,ARE able to stand on the head of a pin?"

Last edited by manyroads (2022-01-29 23:18:52)

Head_on_a_Stick · 2022-01-29 23:57:10

manyroads wrote:

I think gvfs does not like sysV

So then why does it work under sysvinit in both my installed system (see earlier screenshot for proof of this) and also in the chimaera live ISO? Try the live image for yourself and report back.

manyroads · 2022-01-30 18:14:21

The chimaera live does work... the remaining variable then must involve something in my .xsessionrc. I have included that below. Maybe something problematic obvious jumps out.

###########################################
#
# .xprofile (common settings) for
# i3wm & dwm window managers on Arch
# Mark Rabideau @ eirenicon.org (ManyRoads)
# 
###########################################

# compositor
 xcompmgr -CnfF -I-.015 -O-.03 -D6 -t-1 -l-3 -r4.2 -o.5 &
# picom &

# shared common keybindings (applications)
sxhkd -c ~/.config/sxhkd/base.conf &

# Dropbox &  Google Drive #####################
#sleep 30 && vgrive &
pkill dropbox 
# the display= removes problem systray icon.
sleep 10 && DISPLAY= dropbox start -i & 
#sleep 20 && dropbox start -i &   

# set network manager #####################
nm-applet &

# bluetooth
/usr/bin/blueman-applet &
#blueman &

# set sound functions #####################
start-pulseaudio-x11 & 
pnmixer &
#amixer -c 0 set Master playback 25% unmute &

# power related functions #####################
lxqt-powermanagement &#
#xfce4-power-manager &
sudo tlp start 
sudo powertop --auto-tune
xautolock -time 8 -locker i3lock-fancy &

#Dell fan control ~ (ref. https://www.cyberciti.biz/faq/controlling-dell-fan-speeds-temperature-on-ubuntu-debian-linux/) 
sudo /etc/init.d/i8kmon start &
i8kctl fan 1 1 &

# Red-spectrum & gamma light shift #####################
redshift-gtk -l 39.3914:-104.7528 &
xrandr --output eDP-1  --primary --brightness 0.9 --mode 1920x1080 &

# keyboard settings #####################
/bin/bash -c  "sleep 5 && setxkbmap -option compose:ralt" &
#xsetroot -xcf /usr/share/icons/Bibata-Original-Amber/cursors/left_ptr 34 &
#setxkbmap -option compose:ralt & 
	
# gnome settings #####################
gnome-keyring-daemon --start --components=pkcs11 &

# Polkit #####################
#lxpolkit &
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

# Notification #####################
dunst -conf  ~/.config/dunst/dunstrc &
apt-notifier &

# wallpaper ##################### 
# currently using nitrogen to manually change wallpapers
feh --randomize --bg-fill /home/mark/Dropbox/wallpapers/VladStudio/* 

# Caffeine #####################
caffeine-indicator &

# USB unmounter #####################
udiskie -s --automount --notify &
 
# misc #####################
diodon &
touchpad-indicator &
# sleep 15 && /opt/extras.ubuntu.com/my-weather-indicator/bin/my-weather-indicator &
/usr/libexec/gvfsd &
/usr/libexec/gvfsd-trash &

Head_on_a_Stick · 2022-01-30 18:31:00

manyroads wrote:

udiskie -s --automount --notify &

^ This. GVFS should be taking care of automounting. Use the relevant options in thunar to configure it.

I could bring up a lot of other potential issues in that file but they would all be off topic here so I will restrict myself to observing that ~/.xsessionrc is read by /bin/sh so bash -c is redundant and also that & should only be appended to a command if it doesn't return the prompt when run from a terminal — unnecessary fork()ing can cause race conditions and strange problems. And it's best to use update-rc.d or sysv-rc-conf to enable services rather than starting them manually. And don't use xrandr to set brightness, that's just a software alteration and reduces the available colour range. And [snip]

The officially official Devuan Forum!

#1 2022-01-28 17:53:36

trash on thunar (dwm & i3wm)

#2 2022-01-28 20:32:52

Re: trash on thunar (dwm & i3wm)

#3 2022-01-28 22:17:49

Re: trash on thunar (dwm & i3wm)

#4 2022-01-28 22:52:19

Re: trash on thunar (dwm & i3wm)

#5 2022-01-28 23:31:18

Re: trash on thunar (dwm & i3wm)

#6 2022-01-28 23:37:27

Re: trash on thunar (dwm & i3wm)

#7 2022-01-28 23:46:30

Re: trash on thunar (dwm & i3wm)

#8 2022-01-28 23:48:09

Re: trash on thunar (dwm & i3wm)

#9 2022-01-28 23:51:40

Re: trash on thunar (dwm & i3wm)

#10 2022-01-29 11:06:28

Re: trash on thunar (dwm & i3wm)

#11 2022-01-29 17:00:03

Re: trash on thunar (dwm & i3wm)

#12 2022-01-29 19:20:35

Re: trash on thunar (dwm & i3wm)

#13 2022-01-29 19:24:26

Re: trash on thunar (dwm & i3wm)

#14 2022-01-29 19:53:37

Re: trash on thunar (dwm & i3wm)

#15 2022-01-29 20:32:53

Re: trash on thunar (dwm & i3wm)

#16 2022-01-29 22:49:27

Re: trash on thunar (dwm & i3wm)

#17 2022-01-29 23:15:55

Re: trash on thunar (dwm & i3wm)

#18 2022-01-29 23:57:10

Re: trash on thunar (dwm & i3wm)

#19 2022-01-30 18:14:21

Re: trash on thunar (dwm & i3wm)

#20 2022-01-30 18:31:00

Re: trash on thunar (dwm & i3wm)

Board footer