peshte, do not hijack this bug, start a new bug. I dont' want to be rude, but
this isn't a support forum.
If you need support you can open the new bug or ask help in
https://answers.launchpad.net/. It may be that there is already an answer to
your question.
--
You received this bug
Hi everyone.
I'm a bit newbie in linux systems.
How can I use/install the lsb-4.0 package?
I've updated my kubuntu 12.1, installed the lsb packages from muon package
manager, lsb-core, lsb-base, but my VMplayer 5.0 won't start any virtual
machine. When I press Play virtual machine, the
No more errors. Tested using vmware player 5.0.0.812388.
verification-done
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
This bug was fixed in the package lsb - 4.0-0ubuntu20.2
---
lsb (4.0-0ubuntu20.2) precise-proposed; urgency=low
* lsb_release: Add -Es to #! line for Python so that it will ignore
the $PYTHON* environment variables, and not add the user's site
directory to sys.path. Both
This bug was fixed in the package lsb - 4.0-0ubuntu26.1
---
lsb (4.0-0ubuntu26.1) quantal-proposed; urgency=low
* lsb_release: Add -Es to #! line for Python so that it will ignore
the $PYTHON* environment variables, and not add the user's site
directory to sys.path. Both
** Changed in: lsb (Ubuntu Raring)
Assignee: Matthias Klose (doko) = Barry Warsaw (barry)
** Changed in: lsb (Ubuntu Quantal)
Assignee: (unassigned) = Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to be clear, the shebang line needs to use -Es
#!/usr/bin/python3 -Es
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
Title:
lsb_release crashed with SIGABRT in Py_FatalError()
To
** Changed in: lsb (Ubuntu Quantal)
Status: Triaged = In Progress
** Changed in: lsb (Ubuntu Raring)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
** Description changed:
+ = SRU =
+
+ All Python system scripts should use -Es to ignore $PYTHON* envars and
+ to ignore the user's site directory. This is a general recommendation.
+
+ [Test Case]
+ $ PYTHONHOME=/does/not/exist lsb_release
+ - crashes without the fix
+ - works correctly with
** Also affects: lsb (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: lsb (Ubuntu Precise)
Status: New = In Progress
** Changed in: lsb (Ubuntu Precise)
Importance: Undecided = High
** Changed in: lsb (Ubuntu Precise)
Assignee: (unassigned) = Barry
This bug was fixed in the package lsb - 4.0-0ubuntu27
---
lsb (4.0-0ubuntu27) raring; urgency=low
* lsb_release: Add -Es to #! line for Python so that it will ignore
the $PYTHON* environment variables, and not add the user's site
directory to sys.path. Both of these are
Hello tolostoi, or anyone else affected,
Accepted lsb into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/lsb/4.0-0ubuntu26.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I am reminded of the -E switch to python3 which ignores environment
variables. lsb_release should use this.
** Package changed: python3.2 (Ubuntu) = lsb (Ubuntu)
** Changed in: lsb (Ubuntu)
Milestone: None = quantal-updates
** Also affects: lsb (Ubuntu Quantal)
Importance: Undecided
All system command should have -E -s in the shebang line to isolate
them from the user's env vars and local site-packages directory.
-E : ignore PYTHON* environment variables (such as PYTHONPATH)
-s : don't add user site directory to sys.path
None of Ubuntu's Python scripts in /usr/bin
-s may also be neede:
quoting from python-dev:
- -E : ignore PYTHON* environment variables (such as PYTHONPATH)
- -s : don't add user site directory to sys.path
- -E -s are useful for system commands and mandatory for suid commands.
--
You received this bug notification because you
Thanks Barry and Christian!
Modifying '/usr/bin/lsb_release' shebang to use -E python3 switch does
the trick for installing VMPlayer 5.0.0 (x86) on 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- I'm just login, and the message to some aplication crashed pops up.
+ = Details =
+
+ During the installation process of either VMware Player major version 4
+ or 5 you will receive a crash report regarding lsb-release as VMware
+ ships a version of python 2 with the
got a couple of errors during the installation of vmware player.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
Title:
lsb_release crashed with SIGABRT in Py_FatalError()
To manage
The problem here is presumably that there's no correct way to set
PYTHONHOME in this case. They need the python2.4 that they ship in the
installer and to point it to their PYTHONHOME. But if from that
environment you ever call any other python program then it will abort
since PYTHONHOME is set
On Oct 02, 2012, at 08:35 PM, Rob Adams wrote:
The problem here is presumably that there's no correct way to set
PYTHONHOME in this case. They need the python2.4 that they ship in the
installer and to point it to their PYTHONHOME. But if from that
environment you ever call any other python
Here is a workaround for installing vmware workstation:
Create a file called python3.2mu with the following contents:
-- start after this line
#!/bin/bash
unset PYTHONHOME
unset PYTHONPATH
exec /usr/bin/python3.2mu-real $@
-- end before this line
Then run sudo
The most boiled down example that provides Python 3 to fatally exit is:
$ PYTHONHOME=/does/not/exist /usr/bin/python3
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named encodings
Aborted (core dumped)
That's to be expected I suppose; it's not a bug
New duplicates of this bug can be found in bug 1045726. It doesn't seem
like it has been fixed.
** Changed in: python3.2 (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was able to recreate this when installing vmware-player version
VMware-Player-4.0.4-744019.x86_64.bundle and by following the steps
indicated in comment #6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
looks like the vmware installer uses a partial python2.x environment,
and then calling everything else with this environment. when lsb_release
is called, then they try to run a python3 with a partial python2.x
library, which is ... interesting.
not seen on other distros, because lsb_release isn't
I tried replacing the /usr/bin/lsb_release file with a hard-coded bash
script but the vmware install still fails in roughly the same place.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
Title:
This problem still occuries while installing VMWare Workstation 9 in
quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
Title:
lsb_release crashed with SIGABRT in Py_FatalError()
To
the segfault is fixed in quantal.
couldn't reproduce this with vmware player 5.0 on precise.
** Changed in: python3.2 (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Evan Broder wrote in
https://bugs.launchpad.net/ubuntu/+source/python3.2/+bug/917088:
---
I ran into this error while installing VMware Player on Precise. I
believe I've tracked it down to the
malus wrote on
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/831731:
-
happened upon boot of installed system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
File Kolodny wrote on
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/831731:
-
Also happened while installing Vmware Workstation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Stacktrace Top from bug original generated to Ubuntu11.10 Oneric
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/831731:
--
StacktraceTop:
Py_FatalError (msg=optimized out) at ../Python/pythonrun.c:2142
initfsencoding
Happen to myself on direct hardware installation (HP655 laptop), during
figuring arround with mounted tar.gz archives (archive mount). - Why
ever; may correlated by accident.
** Tags added: oneiric
** Tags added: amd64
** Tags added: qa-manual-testing
--
You received this bug notification
qa-manual-testing is imported from
https://bugs.launchpad.net/ubuntu/+source/python3.2/+bug/917088
The procedure is given by:Crashed during installation of vmplayer 4.01
on amd64
May be actual versions make sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: lsb (Ubuntu) = python3.2 (Ubuntu)
** Changed in: python3.2 (Ubuntu)
Assignee: (unassigned) = Matthias Klose (doko)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
** Visibility changed to: Public
** Changed in: lsb (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938869
Title:
lsb_release crashed with SIGABRT in
36 matches
Mail list logo
