No trashcan and others

Topic: No trashcan and others (Read 800 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

No trashcan and others

16 November 2023, 18:08:11

In nemo it doesn't show the action to send to the trashcan.
I checked the options it should always show it.

evince doesn't remember the last page and I cannot bookmark them.

polybar's battery module it is not updated when battery state changes.
Edit: battery problem was in the config.

Are these problems maybe related?

Re: No trashcan and others

Reply #1 – 16 November 2023, 19:29:30

is the gvfs package installed?
if not install it

https://wiki.archlinux.org/title/File_manager_functionality#Mounting

Quote

The Gnome virtual filesystem (gvfs) provides mounting and trash functionality.

Re: No trashcan and others

Reply #2 – 16 November 2023, 20:21:57

It is installed already.

trash-restore from trash-cli shows the trash.

I am on bspwm (as WM).

Re: No trashcan and others

Reply #3 – 17 November 2023, 21:10:20

You may need to start your DE with dbus-launch.

I have this in my .xinitrc (you may change it however you want)

Code: [Select]

exec dbus-launch --sh-syntax --exit-with-session $1

Re: No trashcan and others

Reply #4 – 18 November 2023, 15:22:33

I used to do that but I remove it since I am now using dinit user service.
dinitctl shows it fine.

I can see that things work on sxmo-dwm.

I removed dinit user dbus service and using again "exec dbus-launch --exit-with-session bspwm" it works.

Should I report the bug?

Re: No trashcan and others

Reply #5 – 20 November 2023, 04:49:50

dinit might be starting the service, but is dbus launching gvfsd (which then launches gvfsd-fuse) like it's supposed to? It may be a misconfiguration with the service if everything worked properly before.

For example, when starting my window manager with dbus-run-session I see the following:

Quote

$ pgrep -l gvfs
19862 gvfsd
19876 gvfsd-fuse

These daemons should be running after a dbus session starts regardless of how it is started. If they're running and aren't being used I'd check the dbus logs for permissions or connection errors.

As an aside, while dbus-launch still works it isn't recommended. The code is a mess, it's antiquated, and even the man page cautions against using it with --exit-with-session. It'll start becoming more of an issue as X dies out, just something to be aware of for now I guess.

Quote

--exit-with-session
If this option is provided, a persistent "babysitter" process will be created, as if for --exit-with-x11. If it cannot connect to the X server, it will monitor the terminal from which dbus-launch was started instead, and if it gets a HUP on stdin, the message bus daemon will be killed. This option is not recommended, since it will consume input from the terminal where it was started; it is mainly provided for backwards compatibility.

Re: No trashcan and others

Reply #6 – 20 November 2023, 20:11:10

Recently I started to use the dinit user services on this machine too.
They have been packaged not long ago.

I'll have to test it.
I enabled the log for dbus service:

Code: [Select]

# dbus session bus user service

type               = process
command            = /usr/lib/dinit/user/dbus --print-address=4
ready-notification = pipefd:4
logfile = $HOME/.local/share/dinit/dbus.log

It's from the package galaxy/dbus-dinit-user.

Re: No trashcan and others

Reply #7 – 22 November 2023, 20:18:22

dbus log is empty and no output too for:

Code: [Select]

pgrep -l gvfs

I have to export tmp dir manually for pipewire:

Code: [Select]

mkdir /tmp/$(id -u)-runtime-dir &
export XDG_RUNTIME_DIR=/tmp/$(id -u)-runtime-dir

When using dinit user service (and no trash can).