Bug 1117732 - ibus-hangul's setup option does not work
Summary: ibus-hangul's setup option does not work
Keywords:
Status: CLOSED DUPLICATE of bug 1115411
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus-hangul
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-09 09:32 UTC by anish
Modified: 2015-04-12 23:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-07 04:30:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description anish 2014-07-09 09:32:24 UTC
I am using Fedora-Live-Workstation-x86_64-rawhide-20140702 with GNOME.3.13.3.
using g-c-c or ibus-hangul's setup option does not show any preferences window.

When i manually ran setup menu i got following error
./ibus-setup-hangul 
Traceback (most recent call last):
  File "/usr/share/ibus-hangul/setup/main.py", line 208, in <module>
    Setup(bus).run()
  File "/usr/share/ibus-hangul/setup/main.py", line 43, in __init__
    self.__builder.add_from_file(ui_file)
GLib.Error: gtk-builder-error-quark: Invalid property: GtkNotebook.tab_hborder on line 21 (11)
[anish@localhost libexec]$ ./ibus-setup-hangul -help
Traceback (most recent call last):
  File "/usr/share/ibus-hangul/setup/main.py", line 208, in <module>
    Setup(bus).run()
  File "/usr/share/ibus-hangul/setup/main.py", line 43, in __init__
    self.__builder.add_from_file(ui_file)
GLib.Error: gtk-builder-error-quark: Invalid property: GtkNotebook.tab_hborder on line 21 (11)




How reproducible:


Steps to Reproduce:
1. Select ibus-hangul input method. 
2. Using IME's menu or g-c-c choose its setup menu

Actual results:
Nothing happens 

Expected Results:-
Setup option window should be visible.

Comment 1 Daiki Ueno 2014-08-07 04:30:06 UTC

*** This bug has been marked as a duplicate of bug 1115411 ***


Note You need to log in before you can comment on or make changes to this bug.