Bug 863673

Created attachment 622734 [details]
File: event_log

Created attachment 622735 [details]
File: core_backtrace

(In reply to comment #0)

Probably it's good to fix this. But which locale did you run ibus-setup on?

I can not reproduce your problem even though LANG is removed.

% env LANG= ibus-setup

ibus-1.4.99.20121006-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-15547/ibus-1.4.99.20121006-2.fc18

ibus-1.4.99.20121006-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/FEDORA-2012-15571/ibus-1.4.99.20121006-2.fc17

I have my F18 latest updated. ibus-setup gives a gui menu, leaving the following messages in terminal:

$ ibus-setup

(main.py:7180): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [general:load_xkb_layouts] does not exist.

(main.py:7180): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue: GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value [general/xkblayoutconfig:group_list] does not exist.


I don't really see how changing the settings of menu will let me use other input language (I select Chinese-intelligent pinyin as input method). Shortcut key doesn't work. My default locale is US english, if that is what you are asking.


As for input method selector from applications menu, choosing "Use IBus (recommended)" now gives the following message:

GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._imsettings_2derror_2dquark.Code5: Current desktop isn't targeted by Input Method.

Package ibus-1.4.99.20121006-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ibus-1.4.99.20121006-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15547/ibus-1.4.99.20121006-2.fc18
then log in and leave karma (feedback).

(In reply to comment #6)
> I have my F18 latest updated. ibus-setup gives a gui menu, leaving the
> following messages in terminal:
> 
> $ ibus-setup
> 
> (main.py:7180): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue:
> GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value
> [general:load_xkb_layouts] does not exist.
> 
> (main.py:7180): IBUS-WARNING **: org.freedesktop.IBus.Config.GetValue:
> GDBus.Error:org.freedesktop.DBus.Error.Failed: Config value
> [general/xkblayoutconfig:group_list] does not exist.


It's another problem.
As you see, this bug is updated and ibus-1.4.99.20121006-2.fc18 is available now and I think the [general:load_xkb_layouts] issue is fixed.

But I'm asking the original bug instead:

(In reply to comment #0)
> backtrace:
> :locale.py:539:setlocale:Error: unsupported locale setting

Which locale did you use to see this problem?
I guess you set a wrong locale or an anaconda bug.


> I don't really see how changing the settings of menu will let me use other
> input language (I select Chinese-intelligent pinyin as input method).
> Shortcut key doesn't work. My default locale is US english, if that is what
> you are asking.

If you use gnome-shell instead of metacity + gnome-panel, you need to run 'gnome-control-center region' instead of ibus-setup because ibus is integrated into GNOME3.
ibus-setup needs to be called for non-GNOME desktops or metacity + gnome-panel.


> As for input method selector from applications menu, choosing "Use IBus
> (recommended)" now gives the following message:
> 
> GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._imsettings_2derror_2dquark.
> Code5: Current desktop isn't targeted by Input Method.

I don't see the error but I guess you use gnome-shell.

BTW, to check the current locale, 'locale' command is good.

> But I'm asking the original bug instead:
> 
> (In reply to comment #0)
> > backtrace:
> > :locale.py:539:setlocale:Error: unsupported locale setting
> 
> Which locale did you use to see this problem?
> I guess you set a wrong locale or an anaconda bug.
> 
I believe this problem is fixed after the latest update. The crash never occur anymore.

> If you use gnome-shell instead of metacity + gnome-panel, you need to run
> 'gnome-control-center region' instead of ibus-setup because ibus is
> integrated into GNOME3.
> ibus-setup needs to be called for non-GNOME desktops or metacity +
> gnome-panel.

Unless I'm very wrong, I thought the purpose of having an icon in the apps menu is to free me from the burden of remembering every command and of typing into the terminal just to start an application?

Or maybe I have used the wrong application here, because going to the menus and click "input method selector" is just a natural destination if I want to switch keyboard language. Btw after your reminder I can now set another keyboard language in gnome-control-center->Region and Language, but honestly this is a sucky experience. Hope this will be fixed in future.

(In reply to comment #10)
> > But I'm asking the original bug instead:
> > 
> > (In reply to comment #0)
> > > backtrace:
> > > :locale.py:539:setlocale:Error: unsupported locale setting
> > 
> > Which locale did you use to see this problem?
> > I guess you set a wrong locale or an anaconda bug.
> > 
> I believe this problem is fixed after the latest update. The crash never
> occur anymore.
> 
> > If you use gnome-shell instead of metacity + gnome-panel, you need to run
> > 'gnome-control-center region' instead of ibus-setup because ibus is
> > integrated into GNOME3.
> > ibus-setup needs to be called for non-GNOME desktops or metacity +
> > gnome-panel.
> 
> Unless I'm very wrong, I thought the purpose of having an icon in the apps
> menu is to free me from the burden of remembering every command and of
> typing into the terminal just to start an application?

I'm asking the result of the 'locale' command to know the root cause and why this problem could be happend.
The purpose does not mean to fix ibus itself, I think.

(In reply to comment #11)
> (In reply to comment #10)
> > > But I'm asking the original bug instead:
> > > 
> > > (In reply to comment #0)
> > > > backtrace:
> > > > :locale.py:539:setlocale:Error: unsupported locale setting
> > > 
> > > Which locale did you use to see this problem?
> > > I guess you set a wrong locale or an anaconda bug.
> > > 
> > I believe this problem is fixed after the latest update. The crash never
> > occur anymore.
> > 
> > > If you use gnome-shell instead of metacity + gnome-panel, you need to run
> > > 'gnome-control-center region' instead of ibus-setup because ibus is
> > > integrated into GNOME3.
> > > ibus-setup needs to be called for non-GNOME desktops or metacity +
> > > gnome-panel.
> > 
> > Unless I'm very wrong, I thought the purpose of having an icon in the apps
> > menu is to free me from the burden of remembering every command and of
> > typing into the terminal just to start an application?
> 
> I'm asking the result of the 'locale' command to know the root cause and why
> this problem could be happend.
> The purpose does not mean to fix ibus itself, I think.

$ locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=

(In reply to comment #12)
> $ locale
> LANG=en_US.utf8
> LC_CTYPE="en_US.utf8"
> LC_NUMERIC="en_US.utf8"
> LC_TIME="en_US.utf8"
> LC_COLLATE="en_US.utf8"
> LC_MONETARY="en_US.utf8"
> LC_MESSAGES="en_US.utf8"
> LC_PAPER="en_US.utf8"
> LC_NAME="en_US.utf8"
> LC_ADDRESS="en_US.utf8"
> LC_TELEPHONE="en_US.utf8"
> LC_MEASUREMENT="en_US.utf8"
> LC_IDENTIFICATION="en_US.utf8"
> LC_ALL=

OK, thanks.
AFAIK, it's the anaconda's bug 858591.
The installer system should provide en_US.utf8.

But this fix will launch ibus-setup with the wrong locale.

ibus-1.4.99.20121006-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.