pidgin g on keyboard only enables/disables logging...cannot type a lowercase g!

[rlou]

Binary package hint: pidgin

when I start a new chat, the chat window opens. whenever I type a lowercase 'g', logging either stops or starts. I cannot type a lowercase 'g' into the chat window! Uppercase G seems ok.

When I click the Options menu, sure enough I see G associated as a shortcut for logging. But this doesn't seem right to only use a letter and not a ctrl-g or something.....

ProblemType: Bug
Architecture: i386
Date: Mon Jun 30 08:59:05 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.4.1-1ubuntu2
PackageArchitecture: i386
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.24-19-generic i686

[Magnus S (magnuss)]

Hi, sounds like a weird bug. Are you still able to reproduce this bug?

//magnus

[rlou (robert-lou)]

I was able to correct the problem. I forget where, but somewhere there
is a place where you can set up hotkeys for pidgin. Somehow the g key
was set to enable/disable logging.

I just tried to find the place where these hotkeys are set, but I cannot
find it now. Checked pidgin preferences, but didn't see it there.

Anyways, was very weird when it was happening, but via google I was able
to find how to fix it.

rob

On Sat, 2008-12-20 at 18:15 +0000, Magnus S wrote:

> Hi, sounds like a weird bug. Are you still able to reproduce this bug?
>
> //magnus
>
> ** Changed in: pidgin (Ubuntu)
> Status: New => Incomplete
>

[Magnus S (magnuss)]

Okay, glad you fixed it!
There is a line in ~/.purple/accels that looks like this: ; (gtk_accel_path "<main>/Options/Enable Logging" ""), which i suspect somehow got the value "g", and you probably used pidgin-hotkeys to fix it.

There doesn't seem to be a way to figure out what caused this in the first place, so...closing. If the bug appears again, please reopen this bug report by setting the status back to "new".

Thanks again, and don't hesitate to submit bug reports in the future:)
//magnus