Ubuntu
caja package

Unable to launch Caja file manager on GNOME Shell

Bug #1846612 reported by Norbert
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
caja (Ubuntu)
Fix Released
Undecided
Unassigned
gnome-shell (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Steps to reproduce:
1. Install Ubuntu 19.04
2. Install Caja with `sudo apt install caja`
3. Try to start Caja with `caja`

disco@disco:~$ caja

(caja:5226): Gtk-WARNING **: 00:03:15.323: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client

disco@disco:~$ caja --no-desktop

(caja:5262): Gtk-WARNING **: 00:04:07.741: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
disco@disco:~$ caja --no-desktop --browser

(caja:5270): Gtk-WARNING **: 00:04:12.536: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
disco@disco:~$ killall caja
caja: no process found

Expected results:
* Caja started, its window is shown

Actual results:
* Caja is not started, its window is not shown

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 3 23:58:17 2019
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Norbert (nrbrtx) wrote :
description: updated
Revision history for this message
Norbert (nrbrtx) wrote :

Caja starts only with

```
caja --no-desktop computer:
caja --no-desktop network:
caja --no-desktop ~
```

As for me - this is very strange and unpredictable behavior.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It sounds like Caja is trying to fulfill a role that some other component is already registered for.

This would not be a bug in gnome-shell. You would need to find out what other package/component is conflicting and find a way to disable or uninstall it.

no longer affects: gnome-shell (Ubuntu)
Norbert (nrbrtx)
tags: added: bionic
Norbert (nrbrtx)
tags: added: xenial
Revision history for this message
Norbert (nrbrtx) wrote :

The same happens with 16.04 LTS and 18.04 LTS.

Caja starts normally in Ubuntu 18.04 LTS on Xfce, Unity and Plasma.

Norbert (nrbrtx)
Changed in caja (Ubuntu):
status: New → Confirmed
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Changed in nautilus (Ubuntu):
status: New → Confirmed
tags: removed: disco
Revision history for this message
Norbert (nrbrtx) wrote :

Ubuntu 20.04 LTS is not affected. Caja starts here normally.

Daniel van Vugt (vanvugt)
Changed in caja (Ubuntu):
status: Confirmed → Fix Released
Changed in nautilus (Ubuntu):
status: Confirmed → Fix Released
Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
Changed in nautilus (Ubuntu):
status: Fix Released → Invalid
no longer affects: nautilus (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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