Bug#923361: caja: Caja unable to start from command line , multiple errors
Package: caja
Version: 1.20.3-1+b1
Severity: important
There are several problems I am encoutering after an 82 item update on
Debian Sid today.
Caja is spamming the .xsession-errors file with this
Initializing caja-image-converter extension
Initializing caja-xattr-tags extension
Initializing caja-image-converter extension
Initializing caja-xattr-tags extension
Initializing caja-image-converter extension
Initializing caja-xattr-tags extension
Starting caja from the command line gives me this:
frank@franklin:~$ caja
Could not register the application:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface
“org.gtk.Actions” on object at path /org/mate/Caja
frank@franklin:~$
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages caja depends on:
ii caja-common 1.20.3-1
ii desktop-file-utils 0.23-4
ii gvfs 1.38.1-3
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-7
ii libcairo-gobject2 1.16.0-3
ii libcairo2 1.16.0-3
ii libcaja-extension1 1.20.3-1+b1
ii libexempi8 2.5.0-2
ii libexif12 0.6.21-5.1
ii libgail-3-0 3.24.5-1
ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7
ii libglib2.0-0 2.58.3-1
ii libglib2.0-bin 2.58.3-1
ii libglib2.0-data 2.58.3-1
ii libgtk-3-0 3.24.5-1
ii libice6 2:1.0.9-2
ii libmate-desktop-2-17 1.20.4-2
ii libnotify4 0.7.7-4
ii libpango-1.0-0 1.42.4-6
ii libpangocairo-1.0-0 1.42.4-6
ii libselinux1 2.8-1+b1
ii libsm6 2:1.2.3-1
ii libstartup-notification0 0.12-6
ii libx11-6 2:1.6.7-1
ii libxml2 2.9.4+dfsg1-7+b3
ii mate-desktop 1.20.4-2
ii shared-mime-info 1.10-1
Versions of packages caja recommends:
ii gvfs-backends 1.38.1-3
Versions of packages caja suggests:
ii engrampa 1.20.2-1
pn gstreamer1.0-tools <none>
pn meld <none>
-- no debconf information
Reply to: