Bug 156962 - Force YaST2 to use XIM to prevent from launching another scim instance, when launching yast2 by a normal user.
Summary: Force YaST2 to use XIM to prevent from launching another scim instance, when ...
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 09:56 UTC by Zhe Su
Modified: 2006-03-10 11:20 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zhe Su 2006-03-10 09:56:52 UTC 
Because we are using immodule enabled qt3 and scim-qtimm, yast2-qt will load scim-qtimm module to get input method service. Then it'll launch another scim instance for root user, if yast2 is launched by a normal user. It's annoying, and may confuse users.

I suggest to add "export QT_IM_MODULE=xim" in yast2 startup script to force yast2 use XIM instead of scim-qtimm to prevent from launching another scim instance.
Comment 1 Mike Fabian 2006-03-10 10:25:57 UTC 
Reassigning to Marcus Schäfer <ms@suse.de>, he can add this to the
YaST2 start scripts.
Comment 2 Mike Fabian 2006-03-10 10:28:20 UTC 
Do you want to set QT_IM_MODULE=xim in the yast2 start script only if
yast2 is launched by a normal user?
What should happen if the user is already logged in as root?
Should we set QT_IM_MODULE=xim always in the yast2 start script?
Comment 3 Zhe Su 2006-03-10 10:58:31 UTC 
I think setting QT_IM_MODULE=xim always in the yast2 start script should be the simplest way, and it should be just ok.
Comment 4 Marcus Schaefer 2006-03-10 11:20:41 UTC 
ok, I added that variable, fixed