Hangs up on text edit

Bug #1385009 reported by inferrna on 2014-10-24
96
This bug affects 20 people
Affects Status Importance Assigned to Milestone
Inkscape
Undecided
Unassigned
inkscape (Ubuntu)
High
Unassigned

Bug Description

Inkscape window became not responding when I edited an simple text element in simple svg.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: inkscape 0.48.5-2ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 24 11:24:51 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/inkscape
InstallationDate: Installed on 2014-09-17 (36 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916)
SourcePackage: inkscape
UpgradeStatus: No upgrade log present (probably fresh install)

inferrna (inferrna) wrote :
inferrna (inferrna) wrote :

Core dump.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in inkscape (Ubuntu):
status: New → Confirmed
nimu (n-mussin) wrote :

seems to be Linux or Ubuntu specific. Works fine on Windows.

Bug still occurs in Inkscape nightlies

Changed in inkscape (Ubuntu):
importance: Undecided → High
Adam Matejko (adam-matejko) wrote :

I have the same bug in my ubuntu 14.10 64-bit and Inkscape 0.48.5 r10040.

Joshua O'Leary (jmoleary) wrote :

This bug appears to be a problem with Unity, as it doesn't occur in Gnome Shell (both using 14.10)

Reinhold Kainhofer (reinhold) wrote :

Unity can't be the problem. I'm experiencing the same lockup when editing text, but I'm on kubuntu 14.10 running the plasma desktop (kwin as window manager).
There's no output to the console, btw.

Reinhold Kainhofer (reinhold) wrote :

Probably related to this bug: Sometimes before the lockup, the keyboard input lags severely. In particular, I suddenly have to press each key twice to get the letter entered in inkscape. Sometimes it needs even more key presses of the same key before it is accepted by inkscape. Shortly after that, inkscape will typically lock up completely.

Reinhold Kainhofer (reinhold) wrote :

Some googling found me this thread: http://www.inkscapeforum.com/viewtopic.php?f=29&t=18042

The suggestion is to unset GTK_IM_MODULE to solve the issue...

So far, this bug has not happened when inkscape is called with GTK_IM_MODULE unset (by default it was set to xim). So maybe this is actually a bug in the xim Gtk im module?

I can confirm this bug on Lubuntu 14.10 as well as on Ubuntu 14.10

Additionally, I think (but I'm not sure how to prove it) evince suffers from the same bug. It freezes if I want to fill forms in PDF documents. Starting evince with 'unset GTK_IM_MODULE evince' again works as a workaround.

This could be an indicator, that Reinhold is right and the problem is in the xim module (or somewhere else), but not in inkscape/evince.

su_v (suv-lp) wrote :

AFAICT this was reported earlier for Inkscape here:
- Bug #1323061: Inkscape freezes when writing text (Lubuntu, Kubuntu)

Likely related to the same conflict with xim:
- Bug #1257413: Inkscape crashes when trying to modify text

Nobuto Murata (nobuto) wrote :

Hi,
can you still reproduce the hang up after installing "ibus-gtk" package and re-login? I'm curious it's related to bug 1377370 or not.

Changed in inkscape (Ubuntu):
status: Confirmed → Incomplete
Vorik (launchpad-gerapeldoorn) wrote :

I cannot reproduce it anymore after installing ibus-gtk. It was someone intermittant before, but it looks good!

Keith (klumpkin86) on 2015-03-19
Changed in inkscape (Ubuntu):
assignee: nobody → Keith (klumpkin86)
assignee: Keith (klumpkin86) → nobody
Trucoto (trucoto) wrote :

I can confirm too, I installed ibus-gtk, now it works without hanging.

Doug (dotang76) wrote :

i can confirm too, installing ibus-gtk on 14.10 appears to work

Gunnar Hjalmarsson (gunnarhj) wrote :

@Nobuto: It seems like you were spot on with suggesting that ibus-gtk is/was missing. In that case this bug is fixed in Unity in 15.04 (bug #1377370), but not in the flavours.

So probably ibus-gtk should be added to the seed in kubuntu-meta, lubuntu-meta, etc. Maybe those should be affected packages at bug #1377370.

Valentin Lab (vaab) wrote :

I have ``ibus-gtk``, and Ubuntu 15.04, inkscape 0.91.0+47~ubuntu14, but I was hit by the same issue.

The value of GTK_IM_MODULE is ``xim``. Had to launch inkscape with: "unset GTK_IM_MODULE && inkscape" to use it properly.

This bug is extremely old and even if it seems related to other packages than inkscape, inkscape is the only package that freezes in such conditions.

Alisdair Tullo (alisdair) wrote :

unset GTK_IM_MODULE && inkscape

seems to work in xubuntu 14.04 LTS, too.

Torsten Bronger (bronger) wrote :

This still is a problem on Lubuntu 16.10, and "unset GTK_IM_MODULE" is still a workaround.

Gunnar Hjalmarsson (gunnarhj) wrote :

@Torsten: Do you remember which value GTK_IM_MODULE had before you unset it?

I'm asking because if the value was "xim", and if that caused the problem, it was a leftover from previous releases. On a fresh install of Lubuntu 16.10, and due to the fix of bug #1605408, the GTK_IM_MODULE value defaults to "none".

Torsten Bronger (bronger) wrote :

GTK_IM_MODULE is "xim" on my system. I don't know where this default comes from, though.

Gunnar Hjalmarsson (gunnarhj) wrote :

It's set by im-config. The simplest way to change it permanently is to open Language Support, change the "keyboard input method system" to "none", and relogin.

Mattia Rizzolo (mapreri) on 2018-03-05
Changed in inkscape (Ubuntu):
status: Incomplete → New
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers