Caja starts multible instances after login

Support & Help Requests
1

Mate 16.04, std paketsources, update, upgrade, dist-upgrade…

I have no idea what the cause is…

After login caja starts multible instances in the taskbar, its full of it (more than 30?.. less than 300?), but the Notebook stays responsible, no crash. Only caja is not usable.

almost the same as here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746339

if I start " caja --sync" in terminal, the cajainstances will shrink till zero, afterwards the caja starts again.
Here is a terminalsession:

########## begin terminal session ###########

rudi@mutu-ge60:~$ caja --sync

Message: Initializing gksu extension...
Initializing caja-open-terminal extension
Initializing caja-main-menu extension
/usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module.  Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail.  As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0
  warnings.warn(warn_msg, RuntimeWarning)
sys:1: PyGIWarning: Caja was imported without specifying a version first. Use gi.require_version('Caja', '2.0') before import to ensure that the right version gets loaded.
Namespace Gtk is already loaded with version 2.0

rudi@mutu-ge60:~$ caja --sync

(caja:7706): Unique-DBus-WARNING : Error while sending message: Message recipient disconnected from message bus without replying

------- here it closes caja instances until ther are no left but then -------------------
------- it writes the following: ------------------------

(caja:7706): Unique-DBus-WARNING **: Error while sending message: 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.
rudi@mutu-ge60:~$

------------- and caja begins to start multible instances again (no key is pressed)---------

########## end terminal session ############

btw, htop says:

  1  [||||||||||||||||||||||||||||||||||||||||                63.3%]   Tasks: 101, 214 thr; 2 running
  2  [|||||||||||||||||||||||||||||||||||||                   58.0%]   Load average: 2.69 2.66 1.83 
  3  [|||||||||||||||||||||||||||||||||                       51.7%]   Uptime: 00:16:26
  4  [||||||||||||||||||||||||||||||||                        50.7%]
  Mem[||||||||||||||||||                                1.35G/7.70G]
  Swp[                                                     0K/3.91G]

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
 2378 rudi       20   0  740M  177M 47040 S 63.9  2.3  9:11.85 compiz
 1456 root       20   0  508M  195M 62024 S 40.3  2.5  5:30.52 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten
 2190 rudi       20   0  559M 63588 23276 S 27.6  0.8  4:01.73 /usr/lib/mate-panel/wnck-applet
 2635 rudi       20   0  740M  177M 47040 S 14.1  2.3  2:02.97 compiz 
 2636 rudi       20   0  740M  177M 47040 S 11.4  2.3  1:50.68 compiz 
 2638 rudi       20   0  740M  177M 47040 S 11.4  2.3  1:47.41 compiz
 2637 rudi       20   0  740M  177M 47040 S 13.4  2.3  1:45.67 compiz 
 2289 rudi       20   0  465M 18404 15748 S  3.4  0.2  0:28.16 /usr/lib/mate-applets/mate-multiload-applet
 2133 rudi       20   0 43524  4040  2840 S  1.3  0.1  0:14.18 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
 2075 rudi       20   0  673M 30060 24660 S  1.3  0.4  0:08.92 mate-session
 2168 rudi       20   0  839M 37164 28004 S  0.7  0.5  0:09.45 mate-panel
 2291 rudi       20   0  344M  9128  6204 S  1.3  0.1  0:05.07 /usr/lib/gvfs/gvfsd-trash --spawner :1.9 /org/gtk/gvfs/exec_spaw/0
21560 rudi       20   0 27716  4068  3280 R  0.0  0.1  0:00.27 htop
 6764 rudi       20   0  762M 35072 26240 S  0.7  0.4  0:03.07 mate-terminal
 2688 rudi       20   0  455M 38876 23856 S  1.3  0.5  0:09.63 /usr/bin/gtk-window-decorator
 2164 rudi       20   0 1081M 30424 21956 S  1.3  0.4  0:08.66 /usr/bin/mate-settings-daemon
 2247 rudi       20   0  232M 31164 15224 S  0.7  0.4  0:04.30 /usr/bin/python3 /usr/share/system-config-printer/applet.py
F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  F10Quit

I testet system repair, deletet “.caja”, purged and installed caja, switched from compitz to compton…
nothing helped.

any ideas?

The laptop worked without any problems until maybe 1 or 2 weeks ago, and I really don’t remember what i’ve done except update, upgrade, dist-upgrade and installed midnight-commander :wink:

2

There’s some glitch happening with Antiviral and endless “Starting Caja…” Have you recently installed that program too?

I think there’s something buggy with how Caja respawns itself, since I can reproduce this too:

killall caja && caja

The correct way to “quit” Caja (which only re-opens itself) is this command:

caja -q

I’d suggest checking which extensions are enabled in Caja, and if Midnight Commander has an extension too, it’s possible this is causing the problem too.

PS. From your htop output, it seems a bit strange compiz is using a lot of CPU. Is that normal on your system?

1 Like
3

synaptic > searched for caja > found installed antiviral-for-caja removed it:

that did the trick! :wink: thanks alot!

htop:
the laptop has nvidia optimus. Because I have no idea whats the best way to deal with it, I use the xorg - nouveau driver until now. Later I will find a better solution with optimus and mate 16.04…
May be thats the cause withe strange compitz reports in htop?

1 Like
4

See the following and try installing Nvidia drivers and see what happens!. :smiley: