Hi,
I've crashed update-manager and when trying to report using ubuntu-bug my crash 
was marked as duplicate of this bug.
And, indeed, traceback is the same.

This is how i got it:
1. Logged to unity as user1.
2. In terminal I relogged to user2 using: su user2
3. As user2 I run update-manager from terminal and got crash:

$ update-manager 
No protocol specified

** (update-manager:4253): WARNING **: Could not open X display
No protocol specified,
Traceback (most recent call last):
  File "/usr/bin/update-manager", line 28, in <module>
    from gi.repository import Gtk
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 76, in load_module
    dynamic_module._load()
  File "/usr/lib/python3/dist-packages/gi/module.py", line 244, in _load
    overrides_modules = __import__('gi.overrides', fromlist=[self._namespace])
  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1624, in 
<module>
    raise RuntimeError("Gtk couldn't be initialized")
RuntimeError: Gtk couldn't be initialized

Now, I understand it is not exactly the same path as people above, but maybe 
this gives some kind of hint.
Also, maybe some friendlier message for this case?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053292

Title:
  update-manager crashed with RuntimeError in /usr/lib/python3/dist-
  packages/gi/overrides/Gtk.py: Gtk couldn't be initialized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1053292/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to