gscim-gtk-applet spawing out of control

Bug #268516 reported by tessonec
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
skim (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Intrepid by FriedChicken

Bug Description

Under KDE 4.1, the scim-gtk-applet respawns a lot (and there are many instances running at the same time).

In fact, at some point (if you want to start a new process) you get an error that no more windows can be open because of
"maximum clients reached error"

The only workaround that I could find (and that I reported here: https://bugs.launchpad.net/kde4-backports/+bug/263211 ) is to remove scim altogether.

Revision history for this message
Arne Goetje (arnegoetje) wrote :

If you have skim (yes, with 'k') installed, please purge it from your system and see if the problem goes away. The reason is that skim was installed by default, but has not been ported to qt4 yet. Therefor it causes problems like this in a qt4 environment
Also, please try with scim-bridge-client-gtk installed.

Changed in scim:
status: New → Incomplete
Revision history for this message
tessonec (tessonec) wrote :

Perfect, removimng skim sloved the problem (in any case, I expected something like kscim :) ).. tricky name.

Revision history for this message
tessonec (tessonec) wrote :

Besides, the workaround suggested in the fisrt message, created a huge delay until windows appeared. Now it is gone.

Thanks!

Revision history for this message
FriedChicken (domlyons) wrote :

I had exactly the same problem. Removing "skim" seems sto help (I will watch this).

As I haven't installed it, there seems to be a dependency installing skim by default. I guess this should be resolved until Intrepid.

Changed in scim:
status: Incomplete → Confirmed
Revision history for this message
FriedChicken (domlyons) wrote :

Removing skim doesn't seem to be a good idea. A lot of apps try to reach the applet and this causes a delay:

$ bluetooth-applet
Failed to open the panel socket
... [10 x] ...
Failed to allocate the agent. Exitting...
Failed to invoking the agent: No such file or directory
Cannot launch the agent
Failed to open the panel socket
... [10 x] ...
Failed to allocate the agent. Exitting...
Failed to invoking the agent: No such file or directory
Cannot launch the agent

$ kbluetooth4-devicemanager
[...]
kbluetooth4-devicemanager(16284) DeviceMan::DeviceMan: Device Manager - Welcome
Failed to open the panel socket
... [10 x] ...
Failed to allocate the agent. Exitting...
Failed to invoking the agent: No such file or directory
Cannot launch the agent

Rolf Leggewie (r0lf)
affects: scim (Ubuntu) → skim (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.