Forums

I can't run PlayOninux in my debian Wheezy

Auteur Réponses
BigBen Samedi 25 Avril 2015 à 0:33
BigBenAnonymous

Hi,

I have debian wheezy x64. When restart and try to run PlayOnLinux, displays something like this:

Looking for python... 2.7.3 - wxversion(s): 2.8-gtk2-unicode
selected
Traceback (most recent call last):
  File "mainwindow.py", line 37, in <module>
    import lib.lng as lng
ImportError: No module named lib.lng

How to fix this?

petch Samedi 25 Avril 2015 à 7:09
petch
Développeur

Hi,

Works for me, lng.py is part of PlayOnLinux own package:

$ dpkg -L playonlinux|grep lng
/usr/share/playonlinux/python/lib/lng.py

Packages installing partially? Never heard of such thing, so I don't know what's going on...

 

BigBen Samedi 25 Avril 2015 à 12:39
BigBenAnonymous

I try:

apt-get install -reinstall playonlinux

But now have:

Looking for python... 2.7.3 - wxversion(s): 2.8-gtk2-unicode
selected
Traceback (most recent call last):
  File "mainwindow.py", line 37, in <module>
    import lib.lng as lng
  File "/usr/share/playonlinux/python/lib/lng.py", line 6, in <module>
    import gettext, Variables as Variables, os
  File "/usr/share/playonlinux/python/lib/Variables.py", line 143, in <module>
    current_user = os.environ["USER"]
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'USER'
 

Edité par BigBen

petch Samedi 25 Avril 2015 à 17:40
petch
Développeur

$LOGNAME and $USER are both quite standard Unix environment variables representing the login name of the current user ($USER seems to have a more BSD ancestry; To please everybody under Linux both are usually defined).

They're defined by "login" program, but under X environment this role seems to be fulfilled by the session manager (?) instead. Either way it's hardcoded in programs, not to be found in configuration files, so they should always be defined, at least unless the user messes with his environment variables, which is still always possible ;)

In fact it's so standard that, as you can see, some programs just expect them to be present, and system not defining them to be called broken instead.

And yes, it was defined when I tried under Wheezy 64bit in a VM.

 

BigBen Samedi 25 Avril 2015 à 17:42
BigBenAnonymous

Problem is solved. I run my vnc in @reboot by crontab :D

Now all is ok. Thanks for trying to help and interest. :)