This problem is probably related to:
https://bugs.launchpad.net/command-not-found/+bug/1480388
In that case a simple solution is to change a line in /usr/lib/command-
not-found from:
os.execvp("python3", [sys.argv[0]] + sys.argv)
to:
os.execvp("/usr/bin/python3", [sys.argv[0]] + sys.argv)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3.3 in Ubuntu.
https://bugs.launchpad.net/bugs/1192890
Title:
update-manager fails to upgrade from quantal to raring No module named
'_sysconfigdata_m'
Status in python3.3 package in Ubuntu:
Confirmed
Status in python3.4 package in Ubuntu:
New
Bug description:
I ran update manager and chose to upgrade to raring. The packages all
downloaded. On installation, I repeatedly saw something like this in
the console:
File "/usr/lib/python3.3/site.py", line 633, in <module>
main()
File "/usr/lib/python3.3/site.py", line 618, in main
known_paths = addusersitepackages(known_paths)
File "/usr/lib/python3.3/site.py", line 284, in addusersitepackages
user_site = getusersitepackages()
File "/usr/lib/python3.3/site.py", line 260, in getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python3.3/site.py", line 250, in getuserbase
USER_BASE = get_config_var('userbase')
File "/usr/lib/python3.3/sysconfig.py", line 610, in get_config_var
return get_config_vars().get(name)
File "/usr/lib/python3.3/sysconfig.py", line 560, in get_config_vars
_init_posix(_CONFIG_VARS)
File "/usr/lib/python3.3/sysconfig.py", line 432, in _init_posix
from _sysconfigdata import build_time_vars
File "/usr/lib/python3.3/_sysconfigdata.py", line 6, in <module>
from _sysconfigdata_m import *
ImportError: No module named '_sysconfigdata_m'
Eventually, update-manager silently exited.
Now when I try to start it again from gnome-terminal, I see the above,
and update-manager immediately exits.
In fact, python3.3 doesn't run, with the same error, and
apt-get install python3.3
Results in the same error repeatedly
_sysconfigdata_m.py is in
http://packages.ubuntu.com/raring/amd64/libpython3.3-minimal/filelist
But it wasn't installed, so I installed it by hand using dpkg.
python3.3 still doesn't run, but now I
apt-get install python3.3
without seeing this error, and all the unconfigured packages from the
upgrade get configured.
The reporting guidelines don't seem to apply to upgrade issues, but
for completeness
$ lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04
What I expected: I expected update-manager to upgrade my system, or to report
that it had failed
What happened: update-manager exited, without reporting failure, leaving my
system in an unusable state
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1192890/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
