Opened 2 years ago

Closed 16 months ago

Last modified 16 months ago

#9353 closed defect (fixed)

Keyboard does not work in 64-bit TBB 2.3.25-10 and 3.0 when ibus is running

Reported by: biosh Owned by: erinn
Priority: major Milestone: TorBrowserBundle 2.3.x-stable
Component: Tor bundles/installation Version:
Keywords: ibus, tbb-3.0, MikePerry201402 Cc: stranger27@…, envite@…, micahlee, aproposnix, mcs, mikeperry, jens@…
Actual Points: Parent ID:
Points:

Description

I'm running Tor Browser in Gentoo, ~amd64 arch.
32-bit bundle works.
With 64-bit bundle I can't input any characters with keyboard.

I start start-tor-browser from terminal and no errors appear later in console.

Child Tickets

Change History (73)

comment:1 Changed 2 years ago by gk

  • Component changed from - Select a component to Tor bundles/installation
  • Milestone set to TorBrowserBundle 2.3.x-stable
  • Owner set to erinn

comment:3 Changed 2 years ago by biosh

No.

tor-browser-linux32-3.0-alpha-2_en-US.tar.xz works.
tor-browser-linux64-3.0-alpha-2_en-US.tar.xz does not.

comment:4 Changed 2 years ago by arma

Sounds like a mystery. I wonder if you're the only user with this problem? Did you do anything weird to your gentoo system? Are you super-duper-sure it's a 64-bit system?

comment:5 Changed 2 years ago by biosh

Yes, it's 64. Everything works except keyboard. I can copy-paste a URL with mouse and it opens the page.
It is Gentoo running systemd and KDE environment, everything is installed from official tree except cloudfuse from a local overlay and lvm2 with nfs-tools from systemd-overlay. Nothing weird besides that :)

comment:6 Changed 2 years ago by gk

Does a 64bit vanilla Firefox work? Maybe it is not a TBB issue:
https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/17.0.7esr/

comment:8 Changed 2 years ago by biosh

Ok, I was wrong when I said that no errors appear in console.
When I press a button in Tor browser, this warning appears:
(firefox:2879): IBUS-WARNING : Events queue growing too big, will start to drop.

If I quit ibus, Tor browser accepts my keyboard input. I've never encountered this error with another app though.
Who is the culprit: Tor, Firefox, GTK, ibus?

comment:9 Changed 2 years ago by biosh

  • Summary changed from Keyboard does not work in TBB 2.3.25-10 (64-bit) to Keyboard does not work in TBB 2.3.25-10 (64-bit) when ibus is running

comment:10 Changed 23 months ago by MMXX

I'm got the same problem here I'm running Sabayon Linux amd64 13.09.

comment:11 follow-up: Changed 22 months ago by dcf

  • Summary changed from Keyboard does not work in TBB 2.3.25-10 (64-bit) when ibus is running to Keyboard does not work in 64-bit TBB 2.3.25-10 and 3.0 when ibus is running

I get this problem too with 64-bit 3.0alpha4 on a newly installed Debian testing.

I can make the problem go away by setting the environment variable

export GTK_IM_MODULE=xim

(e.g., in ~/.xsessionrc), away from the default

export GTK_IM_MODULE=ibus

Ibus input still seems to work after this. GTK_IM_MODULE is normally set by Debian somewhere in /etc/X11/Xsession.d/.

comment:12 Changed 21 months ago by skull88

Same problem here, TBB worked till I upgraded today from Ubuntu 13.04 to 13.10.

Worked fine:
Ubuntu 13.04 64 bit and TBB 2.3.25-13 64bit

Problem occurred with:
Ubuntu 13.10 64 bit and TBB 2.3.25-13 64 bit

comment:13 Changed 21 months ago by GlobalwebGate

I have the same problem after upgrading from Ubuntu 13.04 to 13.10

With 64-bit bundle I can't input any characters with keyboard.

comment:14 Changed 21 months ago by GlobalwebGate

FIXED!

Just go to Software Center und uninstall IBUS. Then restart or just kill all IBUS related tasks. That also fixed another issue, where the fonts in browsers looked crappy after moving from 13.04 to 13.10
Seems that Ibus was responsible for that too. What a piece of crap :D :D

comment:15 Changed 21 months ago by GlobalwebGate

P.S: I also had some serious lags on my PC after moving to 13.10 and now those are gone too! :))
Ibus, what a piece of crap indeed. Reminds me of Google Play Services under Android _

comment:16 Changed 21 months ago by biosh

What do you mean by fixed? Not running ibus?
I already said that in comment 8. And this isn't a solution since people (including me) need ibus.

comment:17 Changed 21 months ago by biosh

GTK_IM_MODULE=xim does not help here: it breaks Japanese input in GTK apps even though the switcher itself works. Input in 64-bit TBB works with GTK_IM_MODULE=xim.

comment:18 Changed 21 months ago by harmony

This bug has stopped all versions of the TBB working for me. Can somebody spell out dcf's workaround above for novices? If I attempt it, will it interfere with the way Ubuntu manages multiple international keyboard layouts? I use that feature a lot, so anything that mucks it up will not work for me, and I'm not sure what role ibus plays in it these days.

comment:19 follow-up: Changed 20 months ago by Simplehuman

The same problem on Ubuntu 13.10 x64

comment:20 in reply to: ↑ 19 Changed 20 months ago by monteiro

Replying to Simplehuman:

The same problem on Ubuntu 13.10 x64

Same problem on Ubuntu 13.10 x32. Solved by creating a shell script: "sh ibus exit; cd path/tor & ./start-tor-browser"

comment:21 Changed 20 months ago by erinn

Does anyone reading this bug happen to use TBB on Debian with a Gnome desktop? Could some of you try installing ibus and seeing if you run into this issue? I'm not using Gnome but I installed ibus and made it run (I guess) so I'll see if I run into this issue.

comment:22 Changed 20 months ago by erinn

There is also this bug, which may be relevant: https://code.google.com/p/ibus/issues/detail?id=1618

The current ibus in Ubuntu 13.10 is 1.5.3. Anyone with an older ibus seeing this? (The one I installed [Debian unstable] is also 1.5.3, so I'll see what happens here.)

comment:23 Changed 20 months ago by rpw

Results on some nightly dabbling done on Ubuntu 13.10 x86_64:

A build from source of Debian sid's ibus-1.5.4 packages http://packages.debian.org/sid/ibus resulted in the same problems as using the Ubuntu 13.10 packages. Note that ibus-1.5.4 is the most current upstream as of 2013-10-31.

However, building debs for Debian wheezy's ibus-1.4.1 from source and replacing Ubuntu 13.10's ibus packages made me able to use keyboard input again. Hilariously, that version of ibus has a format string issue. This can be worked around by stripping the -Werror=format-security option from CFLAGS and CXXFLAGS, for instance by setting DEB_CFLAGS_STRIP and DEB_CXXFLAGS environment variables before running dpkg-buildpackage. So there's a patch

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=ibus.debdiff;att=1;bug=710643

for ibus-1.5.1.is.1.4.2 (someone might want to find out why they reverted their 1.5.1 binary packages to be built from 1.4.2 source at that point) attached to this bug

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710643

Building and installing ibus-1.5.1.is.1.4.2 packages makes TBB work again as well. The most straightfoward conclusion I would draw from these experiments is that whatever changes were done between ibus 1.4 and ibus 1.5 is causing the pain seen here. Downgrading to ibus 1.4 seems like a temporary option, but is not a real solution.

Also see related fix (#16) in this bug over at launchpad:

https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1007423

Note that Rik Shaw is pointing to the wrong PPA though; it should be wasta-testing instead of wasta:

https://launchpad.net/~wasta-linux/+archive/wasta-testing

More investigation is need to figure out and eliminate the root cause, I think this task is up to the ibus people, though. Especially since TBB is only one of many applications affected.

comment:24 Changed 20 months ago by Simplehuman

It is strange. On another PC with 13.10 x64 Ubuntu - Keyboard input is working fine on the same ibus version

comment:25 Changed 20 months ago by beroal

I can't enter text, but Ctrl+R works.
Arch Linux
kernel 3.11.1-1-ARCH
ibus 1.5.3-2
tor-browser-en 2.3.25_14-1

comment:26 Changed 20 months ago by beroal

  • Cc stranger27@… added

comment:27 Changed 20 months ago by biosh

Original poster here.
I no longer experience the problem with ibus 1.5.4 (previously was on ibus 1.5.3).
Since rpw still complains about 1.5.4 in comment 23, I'm not closing this bug.

comment:28 Changed 20 months ago by biosh

Forget the last comment, it was broken ibus so it didn't run for some reason.

comment:29 Changed 20 months ago by Envite

User from RT ticket RT15647 experiences same issue. His kernel is
Linux [HostnameDeleted] 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 GNU/Linux

Last edited 20 months ago by Envite (previous) (diff)

comment:30 Changed 20 months ago by Envite

  • Cc envite@… added

comment:31 Changed 20 months ago by micahlee

  • Cc micahlee added

comment:32 follow-up: Changed 20 months ago by aproposnix

  • Cc aproposnix added
  • Keywords ibus added

comment:33 in reply to: ↑ 32 ; follow-up: Changed 20 months ago by aproposnix

I'm having this issue as well. In order to use TOR I have to kill ibus completely. I understand that this is not so much an issue with TOR browser however, I think this needs to be fixed ASAP. Shouldn't the urgency of this be bumped up a notch?

It would be great if someone with the deep knowledge of this issue could reach out directly to the ibus team - assuming it hasn't already happened.

comment:34 in reply to: ↑ 33 Changed 20 months ago by bolli

Replying to aproposnix:

I'm having this issue as well. In order to use TOR I have to kill ibus completely. I understand that this is not so much an issue with TOR browser however, I think this needs to be fixed ASAP. Shouldn't the urgency of this be bumped up a notch?

It would be great if someone with the deep knowledge of this issue could reach out directly to the ibus team - assuming it hasn't already happened.

Worked for me as well - having the same issue.

killall ibus-x11

And keyboard works again in Tor Browser.

comment:35 Changed 20 months ago by pedro_sland

I am also having this problem after upgrading Ubuntu from 13.04 to 13.10. I can confirm that after killing ibus (killall ibus-x11) it worked. I didn't have to close TBB's FF.

comment:36 Changed 20 months ago by Envite

User from RT15647 confirms that killal ibus-x11 works for him.

comment:37 Changed 20 months ago by harmony

Neither killall ibus nor killall ibus-x11 works for me.

comment:38 follow-up: Changed 20 months ago by Radu Rădeanu

Until this bug will be fixed, I found the followings to be the right solution:

  1. Open start-tor-browser script file with your favorite editor. I use gedit for scripts:
gedit /path/to/start-tor-browser
  1. Add the following line on the second line (immediately after the line containing shebang interpreter directive - #!/bin/sh):
export GTK_IM_MODULE="xim"
  1. Save the file and close it.

Source: http://askubuntu.com/a/377321/147044.

Last edited 20 months ago by Radu Rădeanu (previous) (diff)

comment:39 Changed 20 months ago by mcs

  • Cc mcs added

comment:40 in reply to: ↑ 38 Changed 19 months ago by checkmate

Replying to Radu Rădeanu:

Until this bug will be fixed, I found the followings to be the right solution:

  1. Open start-tor-browser script file with your favorite editor. I use gedit for scripts:
gedit /path/to/start-tor-browser
  1. Add the following line on the second line (immediately after the line containing shebang interpreter directive - #!/bin/sh):
export GTK_IM_MODULE="xim"
  1. Save the file and close it.

Source: http://askubuntu.com/a/377321/147044.

Radu´s entry nonetheless, took me the best part of two nights to decipher. In simpler terms, this is how I got the keyboard to work in tor browser (under Ubuntu 13.10 3.11.0-14-generic HP Pavilion dv9843cl with 4 GB and 500 MB hdd 7200):

  1. Open a terminal [Ctrl]+[Alt]+T
  2. Type/copy and paste ´cd ~/.tor-browser-en/INSTALL´ (not the single qoute marks!)
  3. Type/copy and paste ´gksu gedit ./start-tor-browser´
  4. In the window that pops up, on the 3rd line type ´export GTK_IM_MODULE=xim´. The end result will show the following in the first five lines:

1 #!/bin/sh
2 #
3 export GTK_IM_MODULE=xim
4 #
5 # GNU/Linux does not really require something like RelativeLink.c

  1. Save the above. Close tor, reopen it and give it a try. Hopefully this will do it until a permanent fix is worked out!

Toodles!

comment:41 Changed 19 months ago by beroal

Both of your instructions are too verbose. This is an instruction for people who know Linux and Bash.

Add a line "export GTK_IM_MODULE=xim" to the beginning of the script "start-tor-browser". On my Linux, its name with path is "~/.tor-browser-en/INSTALL/start-tor-browser".

comment:42 follow-up: Changed 19 months ago by arma

Is there a downside to adding this env var to all Linux TBB users?

comment:43 in reply to: ↑ 42 Changed 19 months ago by biosh

Replying to arma:

Is there a downside to adding this env var to all Linux TBB users?

Yes, layout switching with ibus will not work inside the browser.

comment:44 Changed 18 months ago by conualfy

I tried this
https://trac.torproject.org/projects/tor/ticket/9353#comment:40
and the keyboard works. Thanks and I hope it gets in the official package. I use Ubuntu 13.10 amd64.

comment:45 Changed 18 months ago by arma

  • Cc mikeperry added
  • Keywords tbb-3.0 added

comment:46 Changed 18 months ago by qbi

  • Cc jens@… added

comment:47 Changed 18 months ago by biosh

With ibus 1.5.4 things seem to have changed a bit.

  1. Simple ./start-tor-browser: I can use the keyboard, but anthy input does not work (for Japanese)
  2. start-tor-browser with GTK_IM_MODULE=xim: EVERYTHING WORKS :)

comment:48 Changed 18 months ago by biosh

I forgot to mention my default:
GTK_IM_MODULE=ibus
in case somebody thinks it wasn't set

comment:49 Changed 18 months ago by mikeperry

  • Keywords MikePerry201401R added
  • Status changed from new to needs_review

comment:50 Changed 18 months ago by beroal

"Simple ./start-tor-browser: I can use the keyboard, but anthy input does not work (for Japanese)"
That's great, but I need Anthy.

comment:51 Changed 18 months ago by mikeperry

  • Status changed from needs_review to needs_revision

Yeah, I just tested and the GTK_IM_MODULE=xim value causes my compose key to break. It sounds like we need a way to point TBB at the proper ibus instance, or find out what changed in the Ubuntu 13.10 ibus to cause it to no longer work.

comment:52 in reply to: ↑ 11 Changed 18 months ago by dcf

Replying to dcf:

I get this problem too with 64-bit 3.0alpha4 on a newly installed Debian testing.

I can make the problem go away by setting the environment variable

export GTK_IM_MODULE=xim

(e.g., in ~/.xsessionrc), away from the default

export GTK_IM_MODULE=ibus

Ibus input still seems to work after this. GTK_IM_MODULE is normally set by Debian somewhere in /etc/X11/Xsession.d/.

This workaround seems no longer to be necessary for me on Debian testing, using TBB 3.5 with ibus 1.5.4.

I had GTK_IM_MODULE=xim in my start-tor-browser for a long time, because it allowed me to type in the browser, even though ibus input was broken. Today I tried removing that variable assignment, and now everything appears to work. I can type in the browser, then I can also activate ibus and type that way, too, which I couldn't do before. See? I ♥ żółwie лол.

Last edited 18 months ago by dcf (previous) (diff)

comment:53 follow-ups: Changed 18 months ago by mikeperry

I still don't understand this yet, but https://lwn.net/Articles/503320/ makes me think recent gnome changes might have caused the IPC channel to ibus to switch to d-bus. If TBB can't properly access D-BUS, that could be the problem here.

dcf: are you able to tell if either dbus or ibus changed recently in testing that may have fixed this? Can you possibly try reverting either of them to the versions in ubuntu 13.10 to see if the problem comes back, or is that painful?

FWIW, ibus in the release of 13.10 was 1.5.3-6ubuntu2. dbus was 1.6.12-0ubuntu10. Ibus has been updated to 1.5.3-6ubuntu2.1. dbus appears to remain the same.

comment:54 Changed 18 months ago by mikeperry

In Debian wheezy, ibus is 1.4.1-9+deb7u1. dbus is 1.6.8-1+deb7u1. Testing lists ibus 1.5.4-1 and dbus 1.7.10-2. I am not sure if I am looking at the right apt url for that to tell if that is the current update version or if that was the original release, though.

In Ubuntu 13.04, ibus is currently 1.4.2-0ubuntu2 and dbus is 1.6.8-1ubuntu6.1.

comment:55 in reply to: ↑ 53 Changed 18 months ago by dcf

Replying to mikeperry:

I still don't understand this yet, but https://lwn.net/Articles/503320/ makes me think recent gnome changes might have caused the IPC channel to ibus to switch to d-bus. If TBB can't properly access D-BUS, that could be the problem here.

dcf: are you able to tell if either dbus or ibus changed recently in testing that may have fixed this? Can you possibly try reverting either of them to the versions in ubuntu 13.10 to see if the problem comes back, or is that painful?

I'm not sure how to do that on Debian. It's a bit painful because there's more than one package: ibus, ibus-gtk, dbus, and dbus-x11 at least. If you know where to get old debs I'll give that a try.

FWIW, ibus in the release of 13.10 was 1.5.3-6ubuntu2. dbus was 1.6.12-0ubuntu10. Ibus has been updated to 1.5.3-6ubuntu2.1. dbus appears to remain the same.

My exact versions are

ibus 1.5.4-1
dbus 1.7.10-2
im-config 0.24-1
tor-browser-24.2.0esr-3.5rc1-build3

I'm not using GNOME at all.

Here are the Debian changelogs: ibus dbus; nothing stands out to me.

Last edited 18 months ago by dcf (previous) (diff)

comment:56 Changed 18 months ago by mikeperry

Is anyone on Ubuntu 13.10 brave enough to try installing the Debian ibus and dbus packages (one at a time, so we know which is the culprit) to see if they fix this issue? You can download them from http://ftp.ca.debian.org/debian/pool/main/d/dbus/dbus_1.7.10-2_amd64.deb and http://ftp.ca.debian.org/debian/pool/main/i/ibus/ibus_1.5.4-1_amd64.deb, but you may need to also pull in several dependencies and ibus input method subpackages too.

The reverse (trying the Ubuntu 13.10 ibus and dbus packages on Debian/testing) would also be helpful. An https version of the ubuntu pool can be found at https://mirrors.kernel.org/ubuntu/pool/main/.

comment:57 Changed 18 months ago by lunar

Using a live system, I have installed ibus 1.5.4-1. I then restarted the desktop session by restarting lightdm. Still no input for the Tor Browser.

I have then installed dbus 1.7.10-2. Restarted lightdm. I was then not able to re-open the desktop session.

comment:58 Changed 18 months ago by damico

For what it's worth, I had reported this issue to Canonical for my default Ubuntu 13.10 (using Unity) setup using the latest 64-bit Tor Browser Bundle to date, and they immediately invalidated my bug report.

Ubuntu Bug #1272032
Title: Tor Browser Bundle on Ubuntu 13.10 is useless until/unless one manually kills the ibus process
URL: ​https://bugs.launchpad.net/ubuntu/+bug/1272032

The invalidation comments say I should report it to you.
So, I'm just following instructions, by reporting this to you.

Last edited 18 months ago by damico (previous) (diff)

comment:59 in reply to: ↑ 53 Changed 18 months ago by dcf

Replying to mikeperry:

dcf: are you able to tell if either dbus or ibus changed recently in testing that may have fixed this? Can you possibly try reverting either of them to the versions in ubuntu 13.10 to see if the problem comes back, or is that painful?

FWIW, ibus in the release of 13.10 was 1.5.3-6ubuntu2. dbus was 1.6.12-0ubuntu10. Ibus has been updated to 1.5.3-6ubuntu2.1. dbus appears to remain the same.

I tried downgrading both ibus and dbus, and there is no change; i.e., everything continues to work now.

I got ibus 1.5.3-7 debs from
http://snapshot.debian.org/package/ibus/1.5.3-7/
http://snapshot.debian.org/archive/debian/20130913T214650Z/pool/main/i/ibus/ibus_1.5.3-7.debian.tar.gz
http://snapshot.debian.org/archive/debian/20130913T214650Z/pool/main/i/ibus/ibus_1.5.3-7.dsc
http://snapshot.debian.org/archive/debian/20130823T214936Z/pool/main/i/ibus/ibus_1.5.3.orig.tar.gz

I got dbus 1.6.12-1 debs from
http://snapshot.debian.org/package/dbus/1.6.12-1/
http://snapshot.debian.org/archive/debian/20130613T155323Z/pool/main/d/dbus/dbus_1.6.12-1_amd64.deb
http://snapshot.debian.org/archive/debian/20130613T155323Z/pool/main/d/dbus/dbus-x11_1.6.12-1_amd64.deb
http://snapshot.debian.org/archive/debian/20130613T155323Z/pool/main/d/dbus/libdbus-1-3_1.6.12-1_amd64.deb

I also tried an old 3.0-rc-1 bundle.
https://archive.torproject.org/tor-package-archive/torbrowser/3.0rc1/tor-browser-linux64-3.0-rc-1_en-US.tar.xz

I tried all combinations of different versions. When I changed ibus, I did ibus exit and then ibus-daemon --xim. When I changed dbus, I did /etc/init.d/dbus restart. I restarted the browser for each test.

ibus dbus Tor Browser
1.5.3-7 1.6.12-13.0-rc-1_en-US works
1.5.3-7 1.6.12-13.5-rc-1_pl works
1.5.3-7 1.7.10-23.0-rc-1_en-US works
1.5.3-7 1.7.10-23.5-rc-1_pl works
1.5.4-1 1.6.12-13.0-rc-1_en-US works
1.5.4-1 1.6.12-13.5-rc-1_pl works
1.5.4-1 1.7.10-23.0-rc-1_en-US works
1.5.4-1 1.7.10-23.5-rc-1_pl works

I don't know. It might have been something else that changed that made things start working for me.

Last edited 18 months ago by dcf (previous) (diff)

comment:60 Changed 17 months ago by mikeperry

  • Keywords MikePerry201402 added; MikePerry201401R removed

Maybe we can get together and try to find out what is the broken component for people at the dev meeting?

comment:61 follow-up: Changed 17 months ago by conualfy

Not sure this is helpful, but for all versions, at least in my Ubuntu 13.10 amd64 adding "export GTK_IM_MODULE=xim" after the comments in the beginning of "~/.tor-browser-en/INSTALL/start-tor-browser" fixes the problem. Maybe it works for all and it is the fasters solution for now to add it by default.

comment:62 in reply to: ↑ 61 ; follow-up: Changed 17 months ago by mikeperry

Replying to conualfy:

Not sure this is helpful, but for all versions, at least in my Ubuntu 13.10 amd64 adding "export GTK_IM_MODULE=xim" after the comments in the beginning of "~/.tor-browser-en/INSTALL/start-tor-browser" fixes the problem. Maybe it works for all and it is the fasters solution for now to add it by default.

Does this fix still allow you to type unicode/non-latin characters?

comment:63 Changed 17 months ago by mikeperry

Well, I tried to install 13.10 on two different laptops to try to reproduce this myself, but I seem to be running into https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237843 or some variant. After a dist-upgrade, X11 becomes totally unusable. Upgrading to the "Proposed" kernel that supposedly contains a fix did not help.

As I am still unable to run Ubuntu 13.10, I can't reproduce this or make any forward progress. :/.

I still suspect that this has something to do with the fact that ibus, dbus, or some related component's IPC mechanism is not reachable from TBB now due to the fact that we reset $HOME to the TBB dir, but I cannot confirm this.

comment:64 Changed 17 months ago by cypherpunks

  • Status changed from needs_revision to new

And that's a win for Mike! I'm typing this very comment under Ubuntu 13.10 after those commands:

ubuntu@ubuntu:~/tor-browser_fr$ mkdir -p .config/ibus && ln -nsf ~/.config/ibus/bus .config/ibus
ubuntu@ubuntu:~/tor-browser_fr$ ./start-tor-browser

Creating this symlink should probably be made part of the start-tor-browser script, I guess.

comment:65 Changed 16 months ago by lunar

  • Priority changed from normal to major

I'm bumping priority now that we have a solution. I think Ubuntu users deserve working bundles. :)

comment:66 Changed 16 months ago by gk

  • Status changed from new to needs_review

comment:67 Changed 16 months ago by nivatius

the bundel from gk in comment 66 works for me
(Ubuntu 13.10 64bit , german layout)

comment:68 Changed 16 months ago by sroecker

I applied gk's patch manually and can confirm that it now works with Ubuntu 13.10 (after of course deleting the old .config/ibus directory in the bundle dir). Tested it with pinyin input.

comment:69 in reply to: ↑ 62 Changed 16 months ago by conualfy

Replying to mikeperry:

Replying to conualfy:

Not sure this is helpful, but for all versions, at least in my Ubuntu 13.10 amd64 adding "export GTK_IM_MODULE=xim" after the comments in the beginning of "~/.tor-browser-en/INSTALL/start-tor-browser" fixes the problem. Maybe it works for all and it is the fasters solution for now to add it by default.

Does this fix still allow you to type unicode/non-latin characters?

Yes @mikeperry, I can write șț characters.

comment:70 Changed 16 months ago by arma

It appears this fix went into both TBB 3.5.3 and 3.6-beta1. Does that mean it's done?

comment:71 Changed 16 months ago by gk

  • Resolution set to fixed
  • Status changed from needs_review to closed

I hope so, yes.

comment:72 follow-up: Changed 16 months ago by conualfy

At least mine does not work. I will have to manually edit the file to make it work, nothing seems to have changed after last update.

comment:73 in reply to: ↑ 72 Changed 16 months ago by arma

Replying to conualfy:

At least mine does not work. I will have to manually edit the file to make it work, nothing seems to have changed after last update.

Can you try TBB 3.5.3 with a fresh unzip to a fresh location?

And if that's broken for you, can you try TBB 3.6-beta-1?

Note: See TracTickets for help on using tickets.