Caja does not start on GNOME Shell

Bug #1791305 reported by Norbert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
caja (Ubuntu)
New
Undecided
Unassigned

Bug Description

Steps to reproduce:
1. Install latest 18.10 iso
2. Install `caja`
3. Try to launch `caja` from terminal in GNOME sHell session

Expected behaviour:
* Caja started normally.

Actual results:
* Caja does not start, shows error message in the terminal:

$ caja

(caja:8695): dbind-WARNING **: 17:05:50.301: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Initializing caja-open-terminal extension

(caja:8695): GLib-GIO-CRITICAL **: 17:05:51.189: g_dbus_connection_call_internal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: caja 1.20.2-5
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 7 17:06:27 2018
InstallationDate: Installed on 2018-09-06 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
SourcePackage: caja
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Norbert (nrbrtx) wrote :
Revision history for this message
Norbert (nrbrtx) wrote :

Ubuntu 18.04 LTS is also affected.

tags: added: bionic
removed: cosmic
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.