critiqjo / key-mon

Automatically exported from code.google.com/p/key-mon
https://github.com/scottkirkwood/key-mon
Apache License 2.0
97 stars 8 forks source link

keymon 1.13-1 broke in Ubuntu 12.10 32-bit #123

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Install keymon 1.13-1 either from downloaded .deb or through Software Center
2.Run keymon.
3.Nothing happens.  Also, the icon for keymon comes up as a gray box with a 
question mark in it.

Please provide any additional information below.
keymon 1.12-1 works on Ubuntu 12.10 32-bit with no problems.  Its just keymon 
1.13-1 that does not.

Original issue reported on code.google.com by shaun...@gmail.com on 28 Dec 2012 at 5:36

GoogleCodeExporter commented 9 years ago
I don't use Ubuntu, but if you can provide some debug information by running 
with `--debug` from command-line, that may be helpful for others to see the 
problems.

Original comment by livibet...@gmail.com on 30 Dec 2012 at 6:05

GoogleCodeExporter commented 9 years ago
Just to reply to your bug.
I tried installing 1.13 on Ubuntu 12.04 64 bit and it works.
I'll have to use Virtual box to try your setting...

Original comment by scottaki...@gmail.com on 30 Dec 2012 at 7:06

GoogleCodeExporter commented 9 years ago
Just to reply to your bug.
I tried installing 1.13 on Ubuntu 12.04 64 bit and it works.
I'll have to use Virtual box to try your setting...

Original comment by scottaki...@gmail.com on 30 Dec 2012 at 7:06

GoogleCodeExporter commented 9 years ago
Just tried this under Virtual Box and got an installation error, so I was able 
to reproduce the bug.
Probably caused by not being able to install python-xlib.

 keymon depends on python-xlib; however:
  Package python-xlib is not installed.

dpkg: error processing keymon (--install):
 dependency problems - leaving unconfigured

Will investigate further.

Original comment by sc...@forusers.com on 30 Dec 2012 at 11:42

GoogleCodeExporter commented 9 years ago
Isn't that strange? From Shaun's description, it doesn't seem to be stuck at 
package manager on that dependency issue.

He's said the 1.12-1 has no problems. So, his system should already have 
python-xlib installed. Unless, something wasn't told in his description.

This sounds like there is an issue in packaging to me, which should pull 
python-xlib and install it while installing keymon package. I don't know 
anything about .deb or Ununtu packaging, so I may be wrong. Anyways, this 
should be a separate issue, IMO.

Original comment by livibet...@gmail.com on 31 Dec 2012 at 4:58

GoogleCodeExporter commented 9 years ago
I just try reinstalling keymon 1.13-1 in the software-center using --debug in a 
terminal. (File Attached)

After having installed keymon I tried running it in terminal.  It says: 
No command 'keymon' found, did you mean:
 Command 'keymod' from package 'dnssec-tools' (universe)
 Command 'key-mon' from package 'keymon' (universe)
keymon: command not found

As if keymon were not installed.  It created an icon in the launcher for keymon 
but running it does nothing as well.

Original comment by shaun...@gmail.com on 31 Dec 2012 at 8:47

Attachments:

GoogleCodeExporter commented 9 years ago
Something I noticed while working in the terminal:
key-mon and keymon refer to the same program.  Perhaps this has something to do 
with why 1.13-1 won't install properly.

Original comment by shaun...@gmail.com on 3 Jan 2013 at 8:44

GoogleCodeExporter commented 9 years ago
So was that the issue?  You need to call key-mon and not keymon ?

Original comment by scottaki...@gmail.com on 4 Jan 2013 at 11:30

GoogleCodeExporter commented 9 years ago
No. In both cases, keymon doesn't install properly.

Original comment by shaun...@gmail.com on 5 Jan 2013 at 6:23

GoogleCodeExporter commented 9 years ago
Since I don't use Ubuntu, so I can't really know what's going on.

But this would be what I do.

1. Remove keymon package(s) and all keymon configuration files (`rm -rf 
~/.config/key-mon`). Double-check to make sure there is no keymon files on your 
system by using `find`.
2. Download source tarball, run it to see if it works.
3. Do #1 again, install the package, and see if it works.

Run keymon with `--debug`. (That was the suggestion I meant for keymon not your 
package manager)

Optional: search Ubuntu/Debian bug tracker to see if there is similar cases.

Original comment by livibet...@gmail.com on 5 Jan 2013 at 11:03

GoogleCodeExporter commented 9 years ago
Not sure if this resolves this, but I created a new version of the debian 
package with updated standards version.

Original comment by sc...@forusers.com on 6 Jan 2013 at 10:17

GoogleCodeExporter commented 9 years ago
Yes!!  The newest version 1.15-1 works!  I've tested it both on Ubuntu 32-bit 
and 64-bit and it works perfect, as long as you uninstall the older version 
first.

Original comment by shaun...@gmail.com on 8 Jan 2013 at 1:10

GoogleCodeExporter commented 9 years ago
Thanks for confirming, changed a fixed.

Original comment by sc...@forusers.com on 12 Jan 2013 at 12:11

GoogleCodeExporter commented 9 years ago
i using ubuntu 12.10 64 bit i tried all latest versions including the ubuntu 
software center versionnone of them working, but when i try to open in terminal 
i got the following error.

"Traceback (most recent call last):
File "/usr/bin/key-mon", line 3, in <module>
km.main()
File "/usr/lib/pymodules/python2.7/keymon/key_mon.py", line 1032, in main
keymon = KeyMon(opts)
File "/usr/lib/pymodules/python2.7/keymon/key_mon.py", line 123, in __init__
self.enabled = dict([(img, self.get_option(cstrf(img.lower))) for img in 
self.IMAGES])
File "/usr/lib/pymodules/python2.7/keymon/key_mon.py", line 80, in cstrf
locale.setlocale(locale.LC_CTYPE, OLD_CTYPE)
File "/usr/lib/python2.7/locale.py", line 547, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting"

Original comment by darknigh...@gmail.com on 16 Jan 2013 at 10:31

GoogleCodeExporter commented 9 years ago
darknightguys,

Your issue is different than this bug, please open a new issue with same 
traceback and supply with the following commands' outputs:

  locale
  locale -a

Original comment by livibet...@gmail.com on 16 Jan 2013 at 1:53