Bug 878352

Please make sure you have updated all your mate packages to the versions listed here before filing any more reports

 https://admin.fedoraproject.org/updates/FEDORA-2012-17936

Ah, okay. seems mirror I'm using was broken. and I see you think this isn't a bug even. thanks.

(In reply to comment #2)
>  and I see you think this isn't a bug even. thanks.


It's more a symptom on the beta freeze,  this would have been pushed to stable.

https://admin.fedoraproject.org/updates/FEDORA-2012-17936

Once everything is pushed it will work, perhaps I should add a version requirement on mate-desktop.

Well, if you are sure it was a known bug and fixed in the latest, CURRENTRELEASE would be best choice to indicate the status of bug or DUPLICATE if there are any bugs in bugzilla that can be referenced FWIW. otherwise I see it _is_ expected behavior a.k.a. NOTABUG, but anyway.

tried with mate-session-manager-1.5.0-1.fc18.x86_64. it doesn't spawn imsettings-switch via imsettings-start.desktop. i.e. no input methods available on MATE. this report is still valid. reopening.

(In reply to comment #5)
> tried with mate-session-manager-1.5.0-1.fc18.x86_64. it doesn't spawn
> imsettings-switch via imsettings-start.desktop. i.e. no input methods
> available on MATE. this report is still valid. reopening.


Did you try rebuilding imsettings against the new mate libs

Please read the original report carefully again. rebuilding doesn't help because it's the issue in how MATE handles AutostartCondition in .desktop file.

From reading the code of mate-session-manager, it seems disabling all of autostart files which contains _unknown_ keywords. it may be conservative way but unfortunately it caused this.

(In reply to comment #5)
> tried with mate-session-manager-1.5.0-1.fc18.x86_64. it doesn't spawn
> imsettings-switch via imsettings-start.desktop. i.e. no input methods
> available on MATE. this report is still valid. reopening.

You expect it to start with this AutostartCondition?

Exec=imsettings-switch -n -q -x 
Terminal=false
AutostartCondition=GNOME3 if-session gnome-fallback


Well that will only start for a gnome-fallback session

re-assigned to imsettings

Welcome to the gnome-3.6 changes that suck

I had a similar issue on cinnamon with gnome-screensaver

https://github.com/linuxmint/Cinnamon/issues/1271

Do you have any pointers it _is_ correct behavior? if so, I have to file bugs to other desktops as I wrote in Comment#0.

at least I couldn't find any documents out about AutostartCondition. so I tested it on other desktops to see how they behaves on it. and I see same behavior there, except MATE. thus, I decided to file this to MATE because it may be most likely a bug in MATE then.

(In reply to comment #11)
> Do you have any pointers it _is_ correct behavior? if so, I have to file
> bugs to other desktops as I wrote in Comment#0.
> 

It's the correct behaviour for mate-session-manager

https://github.com/mate-desktop/mate-session-manager/issues/10


> at least I couldn't find any documents out about AutostartCondition. so I
> tested it on other desktops to see how they behaves on it. and I see same
> behavior there, except MATE. thus, I decided to file this to MATE because it
> may be most likely a bug in MATE then.

I doubt gnome-shell uses /etc/xdg/autostart/imsettings-start.desktop to start imsettings.
As for KDE, XFCE and LXDE do they actually use it or do they have there own startup files?


As I read this

AutostartCondition=GNOME3 if-session gnome-fallback

it says only start for gnome fallback session, am I wrong?

(In reply to comment #12)
> (In reply to comment #11)
> > Do you have any pointers it _is_ correct behavior? if so, I have to file
> > bugs to other desktops as I wrote in Comment#0.
> > 
> 
> It's the correct behaviour for mate-session-manager
> 
> https://github.com/mate-desktop/mate-session-manager/issues/10

I was asking for a pointer that "AutostartCondition...." in imsettings-start.desktop only start for a gnome-fallback session as you said at Comment#8. not what MATE developers recommends how to manage the user session on MATE.

plus, this isn't something can be added into the session management because it's just an one time process at the startup time to invoke the input method through DBus.

> I doubt gnome-shell uses /etc/xdg/autostart/imsettings-start.desktop to
> start imsettings.

They don't. they don't even need imsettings to have the input method anymore, but on fallback mode. this is why it has such line.

> As for KDE, XFCE and LXDE do they actually use it or do they have there own
> startup files?

Yes, they do. and No, they don't have any own startup files.

> As I read this
> 
> AutostartCondition=GNOME3 if-session gnome-fallback
> 
> it says only start for gnome fallback session, am I wrong?

on _GNOME3_. yes.
You are not GNOME3 right. so it shouldn't be applied. plus, if it has OnlyShowIn=GNOME or GNOME3, you're right. it should be exclusive. but it doesn't have it nor even NotShowIn. so should be inclusive IMHO.

I have looked at the issue more, indeed it doesn't autostart.
I then tried starting it from a terminal and it still doesn't start ibus


imsettings-switch -n -q -x


There are no errors running this command

I launch im-chooser and it offers to start ibus, these are the warnings in ~/.xsession-errors

** (im-chooser:1468): WARNING **: 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.

** (main.py:1909): WARNING **: 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.

(In reply to comment #14)
> I have looked at the issue more, indeed it doesn't autostart.
> I then tried starting it from a terminal and it still doesn't start ibus

It depends on your locale. we are running ibus by default for certain languages only so far. see /etc/X11/xinit/xinitrc.d/50-xinput.sh

> I launch im-chooser and it offers to start ibus, these are the warnings in
> ~/.xsession-errors
> 
> ** (im-chooser:1468): WARNING **: 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.
> 
> ** (main.py:1909): WARNING **: 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.

Well, this is because no at-spi2-registryd is running. and this is similar reason that MATE incompletely support AutostartCondition. see /etc/xdg/autostart/at-spi-dbus-bus.desktop how it's brought up.

Will my pull request help this issue?

https://github.com/mate-desktop/mate-session-manager/pull/13

as for this AutostartCondition I see no gain in porting it.


http://git.gnome.org/browse/gnome-session/commit/gnome-session/gsm-autostart-app.c?id=58ebdfac223e6246323a6fcc452221a7581ed868

That helps only for at-spi issue as that condition depends on gsettings. MATE needs to do further work to deal with (if|unless)-session, and the case when it is non-MATE desktops.

Tagoh,

Ping me on IRC when you get a chance.

Sorry for not updating. by Bug#887951, I've reverted this change in imsettings and  doesn't have AutostartCondition stuff anymore. so closing this. thanks.

This was reverted in imsettings-1.5.1-2.fc18 and already pushed into stable.