Bug 776567

Summary:	YaST2 doesn't support Input Method
Product:	[openSUSE] openSUSE 12.2	Reporter:	Marguerite Su <i>
Component:	YaST2	Assignee:	Thomas Göttlicher <tgoettlicher>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	mfilka
Version:	RC 2
Target Milestone:	---
Hardware:	All
OS:	openSUSE 12.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/var/log/YaST2 and hwinfo.txt

Description Marguerite Su 2012-08-20 10:53:13 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/22.0.1190.0 Safari/537.1 SUSE/22.0.1190.0

Modern input methods have provided im modules for GTK/QT/XIM a long time. 

But YaST2 didn't catch up, which makes i18n a failure or "half-done"/"read-only" effort.

eg: if I translate a package description to Chinese/Japanese/Korean/Tamil, any Asian or African langs, how could I search them? no way if you can't input anything local. 

Reproducible: Always

Steps to Reproduce:
1. add M17N repo
2. sudo zypper in fcitx or ibus
3. start YaST2 software management or repositories or anything can input.
4. put your mouse into the search textarea
5. ctrl+space combined keys
6. input "woshi" then press space
Actual Results:  
nothing. Your can't even see input panel toggled out.

but if you (even) reproduce in Chromium/Firefox, which is not a pure Linux staff. input panel can show and let you input

Expected Results:  
input panel should show and let user input.

https://github.com/fcitx/fcitx/tree/master/src/frontend

You could see here for how input modules are coded so you'll know how to cooperate with them.

Comment 1 Kun Kun Zhang 2012-08-21 05:19:18 UTC

Hi, thank you for your report.could you please help to provide y2logs according to the following URL?Thanks
http://en.opensuse.org/openSUSE:Bugreport_YaST

Comment 2 Marguerite Su 2012-08-21 06:37:27 UTC

Created attachment 502895 [details]
/var/log/YaST2 and hwinfo.txt

Actually it's a design fault. so personally I don't think logs can help too much.

I mark it "major" because the "input" feature of YaST2 is missing for locals thus a lot of further feature can't use for locals. But actually we never have input feature for locals before. 

In YaST2 design, we may just "give it a GUI using GTK/QT" without take too much consideration that "there're specific things to notice when giving a GUI".

Hope it helps

Marguerite

Comment 3 Marguerite Su 2012-08-24 14:19:08 UTC

Hi, I consulted some Input Methods developers, and here's an easy fix:

kdesu -c "yast2" << this doesn't work apparently

kdesu -c "QT_IM_MODULE=xim GTK_IM_MODULE=xim yast2" << this works perfectly

The magic behind this is because modern IMs use DBus. So the only working input method in su environment is xim. export that environment variable to YaST2 can solve the problem.

so YaST developers please help modifying YaST startup codes to include these environment variables and fix it in packages.

Thanks,

Marguerite

Comment 4 Marguerite Su 2012-08-24 16:49:13 UTC

fixes see:

yast2 pull request 7 on Github:

https://github.com/yast/yast-yast2/pull/7

SR#131531 on OBS:

https://build.opensuse.org/request/show/131531


And this needs a maintenance update.

Thanks.

Marguerite

Comment 5 Marguerite Su 2012-08-27 09:51:28 UTC

fixed in 2.23.4