mate-session spawns 10 x-caja-desktop windows on first login.

[dmashal]

Apparently marco can't start fast enough or .config/dconf does not get created fast enough for first login and exactly 10 x-caja-desktop windows get spawned.

edit:

If you run mate-session from a terminal you can notice an endless spawning of caja.

I thought switching to metacity would help but in reality it didn't.

I suspect systemd or msd to be the culprit here.

MDykstra is experiencing a similar issue with ArchLinux and systemd 196

Thanks in advance.

[MDykstra]

Toggling boolean GSettings key "/apps/caja/preferences/desktop-is-home-dir" gives additional icons on the visual desktop "Desktop, Documents, Downloads, Pictures". Icons are not removed after boolean is set to "false"

Caja pops up showing "x-caja-desktop" in path-bar showing three icons "Computer, Home, Trash", when boolean is set to false initially being true. However, Caja does not show "Computer, Home, Trash" icons when manually browsing to "home-dir/Dektop".

Console output from mate-session at time of setting boolean to false:

ERROR:caja-pathbar.c:1871:button_data_file_changed: assertion failed: (path_bar->current_path != NULL)

** (caja:6060): WARNING **: Failed to get the current CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files

[szesch]

I occasionally get one of these opening on Wheezy and Precise.

[dmashal]

It seems that this is a mate-settings-daemon and/or mate-session problem.

Ways To reproduce:

1. Log out and log back in really fast over and over

or

2. rm -rf .config, logout log back in

And for fun:

3. Run mate-session as a normal user from a terminal

Disabling mate-settings-daemon as a startup application seems to fix this.

[bhull2010]

I experience this as well on Ubuntu 12.04 if I create a new user and log in for the first time with that user. It also happens if I remove ~/.confg and log out/in. To fix this, I created /usr/share/applications/caja-desktop.desktop with the following:

[Desktop Entry]
Name=Desktop
Exec=caja -n
Icon=user-desktop
Terminal=false
Type=Application
StartupNotify=false
NoDisplay=true
OnlyShowIn=MATE;
X-MATE-Bugzilla-Bugzilla=MATE
X-MATE-Bugzilla-Product=caja
X-MATE-Bugzilla-Component=general
X-MATE-Bugzilla-Version=1.5.2
X-MATE-Autostart-Phase=Desktop
X-MATE-Autostart-Notify=true
X-MATE-AutoRestart=true
X-MATE-Provides=filemanager

This is mostly based on the existing caja.desktop file in /usr/share/applications. I then edit /usr/share/glib-2.0/schemas/org.mate.session.gschema.xml and change "caja" to "caja-desktop", save the file, and use glib-compile-schemas to rebuild the schemas. Now, removing .config and logging out/in does not cause x-caja-desktop windows to appear.

The change is essentially running "caja -n" instead of "caja" from mate-session. I based this on what GNOME/Unity did in http://git.gnome.org/browse/nautilus/tree/data/nautilus-autostart.desktop.in

[dmashal]

thankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyouthankyou

[dmashal]

@bhull2010's fix works for me

[dmashal]

Real fix here:
mate-desktop/caja@c1d965c

[hadrons123]

I still have this issue in Fedora and I had to use bhull2010 fix.

rpm -qi mate-file-manager
Name : mate-file-manager
Version : 1.6.1
Release : 3.fc19
Architecture: x86_64
Install Date: Fri 24 May 2013 07:04:09 AM IST

[dmashal]

@hadrons123 thanks for your comment. Please try the latest updates from updates-testing and provides the exact steps you do to reproduce the issue?

[hadrons123]

Looks like it doesn't happen anymore.

rpm -qi mate-file-manager
Name : mate-file-manager
Version : 1.6.1
Release : 4.fc19
Architecture: x86_64

[dmashal]

good

[hadrons123]

Thanks for your efforts Dan.

[dmashal]

np. thanks @niceandgently for his help too

[dag-erling]

Unfortunately, I still get this issue in Fedora 19 with

% rpm -qa | grep mate-file-manager
mate-file-manager-sendto-1.6.0-2.fc19.x86_64
mate-file-manager-extensions-1.6.2-3.fc19.x86_64
mate-file-manager-schemas-1.6.2-3.fc19.x86_64
mate-file-manager-image-converter-1.6.0-1.fc19.x86_64
mate-file-manager-open-terminal-1.6.0-3.fc19.x86_64
mate-file-manager-1.6.2-3.fc19.x86_64

installed via 'yum groupinstall "MATE Desktop"'.

% rpm -qf /usr/share/applications/caja.desktop
mate-file-manager-1.6.2-3.fc19.x86_64
% grep ^Exec /usr/share/applications/caja.desktop
Exec=caja -n

[raveit65]

Mostly this happens only one time after first or second login to mate-session.

[dag-erling]

Even “only one time after first or second login” is once too many. Most users trying out Mate will log in, see this and switch back to Gnome or KDE—or worse yet, Windows.

[monsta]

Okay, I see the fix has been committed, then the issue was closed and reopened several times... Now, what version of Caja is needed to get rid of this annoying bug? It still happens in Mint 16. Caja is 1.6.2 here, mate-session-manager is 1.6.1.

[hadrons123]

At the moment fedora is the distro which used to get flooded with multiple caja windows on every login. But whenever I get the issue there is usually an updated version available in the repos which used to solve it. I have to thank fedora maintainers for this relentless help on this bug. But in Arch and Debian it happens only once during the first login and it never re occur again. Surprising when I moved to systemd in Debian I got flooded again. In someway logind is playing tricks I guess. When it comes to mint, I absolutely have no clue.

This issue has been around an year and there is still no clear permanent solution yet.

In fedora I am using this version and it might work for you if could build it yourself from source.

rpm -qa | grep mate-file-manager
mate-file-manager-schemas-1.6.3-0.10.gitbf47018.fc21.x86_64
mate-file-manager-1.6.3-0.10.gitbf47018.fc21.x86_64
mate-file-manager-extensions-1.6.3-0.10.gitbf47018.fc21.x86_64

[monsta]

Okay, I understand. If it depends on what init system the distro is using, then it's surely not yet fixed here in the code.
Well, too bad. Will wait for a real fix then.

[habamax]

@dag-erling That is exactly what I do right now. I have just tried mate but could do nothing with it. Back to KDE. I will check it later this year.

[pgaltieri]

This is still broken in Fedora. It happens much less frequently, but it still happens. I have 3 systems running F19 and it happens on all 3. Usually it's the first login after I reboot the system, but it has happened other times as well.

Paolo

[raveit65]

@pgaltieri , which version of mate-file-manager do you use?
Pls check if /run/user//dconf is writeable for your user?
see https://bugzilla.redhat.com/show_bug.cgi?id=753882

[pgaltieri]

On 03/01/2014 03:14 PM, Wolfgang Ulbrich wrote:

@pgaltieri https://github.com/pgaltieri , which version of
mate-file-manager do you use?
Pls check if /run/user//dconf is writeable for your user?
see https://bugzilla.redhat.com/show_bug.cgi?id=753882

—
Reply to this email directly or view it on GitHub
#19 (comment).

I'm using the latest version

mate-file-manager.x86_64 1.6.3-2.fc19

drwx------. 2 pgaltieri pgaltieri 60 Mar 1 09:49 /run/user/1000/dconf/

As I mentioned it doesn't always happen.

Paolo

[raveit65]

Unfortunately, the issue isn't cause by caja himself.
One reason is the /run/user/1000/dconf/ permission issue, the other reason is related to gsettings, see https://bugzilla.gnome.org/show_bug.cgi?id=721590 .
As workaround i've add a 3 sec delay to caja autostart. You can increase the value on your systems, maybe it helps.

[root@mother rave]# cat /usr/bin/caja-autostart 
#!/bin/bash

sleep 3 && 
exec  caja -n &

exit

Use 'sleep 6 &&' or a higher value.

[kawing-chiu]

Hi.
This bug is still persistent here on Arch with mate-file-manager 1.6.3-1

[stefano-k]

mate-desktop/caja@4f1e756

[monsta]

Cool. If it proves to be the real solution, can it be backported to Caja 1.6.x?

[stefano-k]

No. We support only current stable release. But distribution maintainers could always cherry pick that commit.

[CarbonFixer]

When logging into MATE under Arch Linux (caja version 1.8.0-2), I get infinite spawns of Caja. Should I file a separate bug report? logging in and out several time does not fix the issue. I tried deleting every configuration file that seems to be related to MATE, without any impact.

[infirit]

@CarbonFixer It has not yet landed in a 1.8 release. Maybe @flexiondotorg can add it to the package build (if not done already).

[flexiondotorg]

@infirit This patch is already applied in the Arch package.

[flexiondotorg]

Update you system because mate-session-manager 1.8.1-1 has been available for some while now. Are you running Manjaro?

[CarbonFixer]

I'm running Arch. List of installed MATE packages:
http://pastebin.com/eLqqcRup

[flexiondotorg]

Curious, because the patch is applied in caja 1.8.0-2.

• https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/caja&id=b2a4b84ccd60cb464e63df698b8b25e3be365ab5

[CarbonFixer]

Then maybe it is another bug? I'm not getting exactly 10 windows, It just goes on to infinity.

[monsta]

It just goes on to infinity

mate-desktop/caja#100

[monsta]

Some people reported it still happens in Mint 17 where MATE is 1.8.

[gauravlnx]

I have installed Mate 1.8 on openSuSE 13.1 and I am facing the same issue. After logging in, mate open endless instances on caja in the status bar and I am unable to use any of the application in mate. They just don't open. I am even not able to open terminal. I cannot log out, reboot and shutdown the system.

[farvardin]

I got this as well (on linux mint current LTS with mate 1.8).
If I start another WM then launch mate-session, I got those errors in the console:

** (caja:10092): WARNING **: Can not determine workarea, guessing at layout
The program 'caja' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 7 error_code 9 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

I can't start caja as a standalone file manager either.

it seems it's the same error here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746339

On a similar computer with a similar installation (same linux mint), no problem with mate.

Like the user in the debian bug report, I can only start caja with "caja --sync".

[aperezbios]

This appears to be happening to me on an Ubuntu-MATE LiveCD boot (on PowerPC, though I doubt that actually matters) with the latest nightly ISO for Ubuntu 16.10 . Can't seem to shake this issue, eh?

[monsta]

Did you file a report on Launchpad (preferably via apport)?

[Brownegmx]

I have always experienced this bug from all the versions of MATE I have used, including 1.18, on different machines. For what I know this bug has always been present and still is. It is a real limitation and I suspect if must put-off a lot of people. The option Startup Applications Preferences/Options/Automatic remember... comes off by default at installation as it should while the bug is still not solved. I have not experienced that bug with Gnome 2.

[raveit65]

I have not experienced that bug with Gnome 2.

Please read carefully this report, otherwise you would understand that this issue is dconf related and gnome2 use another config setting system.
And please check if this dir is writable for your user

[rave@mother ~]$ ls -ls /var/run/user/1000/dconf/
insgesamt 4
4 -rw------- 1 rave rave 2 24. Apr 13:30 user

Is there a reason why you post several reports today without saying which distro and distro-release are you using?

[Brownegmx]

I have filed two reports today because I have found out today the correlation between the caja file rename editing problem and the mouse pointer option. I have used MATE with several distributions over the years. I presently use it for my day-to-day, operational work with the latest versions of Ubuntu-MATE-16.04 (MATE-1.12.1) and Mint-MATE-18.1 (MATE-1.16.1) on two different machines. The issue of not being able to re-open the desktop in the state it has been left has always been present in all the distributions I have used and I can see it is still not solved. I have checked the access to the 'user' file you mention and I confirm it belongs to the user concerned with the read and write access. You suggests I read a report and there is no report attached or any reference or link to a report. Can you point me to it? I am not qualified to figure out where the problem comes from; whether the bug is with MATE or dconf, for the users it remains a bug. Gnome-2 was a great desktop concept and implementation. Its being dropped by the Gnome team was, in my view, a destructive blow to the credibility of all OSS as an operational solution. Thanks to the MATE team for having picked up from there. I can see MATE is now offered by most of the major distributions which is testimony of the need there is for such desktop concept. Cheers, On 24/04/17 12:34, raveit65 wrote: I have not experienced that bug with Gnome 2. Please read carefully this report, otherwise you would understand that this dconf related and gnome2 use another config setting system. And please check if this dir is writable for your user [rave@mother ~]$ ls -ls /var/run/user/1000/dconf/ insgesamt 4 4 -rw------- 1 rave rave 2 24. Apr 13:30 user Is there a reason why you post several reports today without saying which distro and distro-release are you using? Or — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/mate-desktop/mate-session-manager","title":"mate-desktop/mate-session-manager","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/mate-desktop/mate-session-manager"}},"updates":{"snippets":[{"icon":"PERSON","message":"@raveit65 in #19: \u003e I have not experienced that bug with Gnome 2.\r\n\r\nPlease read carefully this report, otherwise you would understand that this dconf related and gnome2 use another config setting system.\r\nAnd please check if this dir is writable for your user\r\n```\r\n[rave@mother ~]$ ls -ls /var/run/user/1000/dconf/\r\ninsgesamt 4\r\n4 -rw------- 1 rave rave 2 24. Apr 13:30 user\r\n```\r\n\r\nIs there a reason why you post several reports today without saying which distro and distro-release are you using?\r\nOr "}],"action":{"name":"View Issue","url":"#19 (comment)"}}}

[raveit65]

Have fun with reading :-)
Link already posted here #19 (comment)

[monsta]

I have always experienced this bug from all the versions of MATE I have used, including 1.18, on different machines. For what I know this bug has always been present and still is.

Please give us more details. Do you get several "x-caja-desktop" windows on start? Does it stop at some point, or are these windows spawning infinitely?

[rhiltbrunn]

I didn't have the exact same problem, but it sounds very close. My problem was infinite Caja windows spawning after startup!

The work-around I found was to edit the "/usr/share/applications/caja.desktop" file by changeing:

X-MATE-AutoRestart=true

to

X-MATE-AutoRestart=false

I'm a real novice with Linux, and especially with Ubuntu-Mate, so I don't know what side the effects of this change will be, if any. So far though, this solved my problem.

I found the answer here:
http://blog.aguilarbros.com

Cheers!