update manager does not start anymore

Asked by Bram van Leeuwen on 2015-09-30

I have 14.04 LTS on the system.
Now update manager will not start from the dash nor with sudo update-manager.
I followed some suggestions from previous questions as:
sudo apt-get install --reinstall python3-distupgrade and in the end it says:

 from xml.parsers.expat import ParserCreate
ImportError: No module named 'xml.parsers'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
    from apport.fileutils import likely_packaged, get_recent_crashes
  File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in <module>
    from apport.report import Report
  File "/usr/lib/python3/dist-packages/apport/report.py", line 15, in <module>
    import xml.dom, xml.dom.minidom
ImportError: No module named 'xml.dom'

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/update-manager", line 37, in <module>
    from UpdateManager.UpdateManager import UpdateManager
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 43, in <module>
    import dbus
  File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 103, in <module>
    from dbus._dbus import Bus, SystemBus, SessionBus, StarterBus
  File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 39, in <module>
    from dbus.bus import BusConnection
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 39, in <module>
    from dbus.connection import Connection
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 37, in <module>
    from dbus.proxies import ProxyObject
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 34, in <module>
    from dbus._expat_introspect_parser import process_introspection_data
  File "/usr/lib/python3/dist-packages/dbus/_expat_introspect_parser.py", line 26, in <module>
    from xml.parsers.expat import ParserCreate
ImportError: No module named 'xml.parsers'

Can somebody help with this problem?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu update-manager Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
2015-09-30
Last query:
2015-09-30
Last reply:
2015-09-30
Best Manfred Hampl (m-hampl) said : #1

Try reinstalling libpython3.4-stdlib

Bram van Leeuwen (bramdod) said : #2

Thanks Manfred Hampl, that solved my question.

Jeroen de Bruijn (vidavidorra) said : #3

Hi Bram ,

I'm getting kind of the same error:
"[ 96%] Generating ../generated_src/configoptions.cpp
cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/src && /usr/bin/python /«PKGBUILDDIR»/src/configgen.py -cpp /«PKGBUILDDIR»/src/config.xml > /«PKGBUILDDIR»/obj-x86_64-linux-gnu/generated_src/configoptions.cpp
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/src/configgen.py", line 15, in <module>
    import xml.dom.minidom"
https://launchpadlibrarian.net/246895210/buildlog_ubuntu-precise-amd64.doxygen_1.8.11-1ppa2_BUILDING.txt.gz

May I ask how you reinstalled libpython?

Manfred Hampl (m-hampl) said : #4

@Jeroen:
Your problem seems to be different.
I assume you have a wrong or missing dependency (you need python2.7, but you have only python2.7-minimal).
If this does not solve your problem, please create a question document of your own.
There is no possibility to follow-up the status of your problem in the question document of somebody else that is alreadyin status 'solved'.

Bram van Leeuwen (bramdod) said : #5

In the meantime the problem has been solved; probably by subsequent updates.
Thanks anyhow!

Op 08-03-16 om 10:17 schreef Manfred Hampl:
> Your question #271945 on update-manager in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/update-manager/+question/271945
>
> Manfred Hampl posted a new comment:
> @Jeroen:
> Your problem seems to be different.
> I assume you have a wrong or missing dependency (you need python2.7, but you have only python2.7-minimal).
> If this does not solve your problem, please create a question document of your own.
> There is no possibility to follow-up the status of your problem in the question document of somebody else that is alreadyin status 'solved'.
>

--
groet, Bram