ubiquity crashed with permission error on NetworkManager GetDevices() call

Bug #1495017 reported by Henk Terhell
118
This bug affects 23 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Wily
Fix Released
High
Mathieu Trudel-Lapierre

Bug Description

Lubuntu Wily i386 20150911 fails to install on disk.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: ubiquity 2.21.29
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic i686
ApportVersion: 2.18.1-0ubuntu1
Architecture: i386
CasperVersion: 1.364
Date: Sat Sep 12 06:11:40 2015
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python3.4
LiveMediaBuild: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150911)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/1733/environ'
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
SourcePackage: ubiquity
Title: ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 7 matched rules; type="method_call", sender=":1.18" (uid=999 pid=1733 comm="/usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --") interface="(unset)" member="GetDevices" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1437 comm="/usr/sbin/NetworkManager --no-daemon ")
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Related branches

Revision history for this message
Henk Terhell (hterhell) wrote :
tags: removed: need-duplicate-check
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Henk Terhell (hterhell)
summary: - ubiquity crashed with dbus.exceptions.DBusException in call_blocking():
- org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 7
- matched rules; type="method_call", sender=":1.18" (uid=999 pid=1733
- comm="/usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --")
- interface="(unset)" member="GetDevices" error name="(unset)"
- requested_reply="0" destination=":1.6" (uid=0 pid=1437
- comm="/usr/sbin/NetworkManager --no-daemon ")
+ ubiquity crashed with dbus.exceptions
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote : Re: ubiquity crashed with dbus.exceptions

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1495017

tags: added: iso-testing
Henk Terhell (hterhell)
description: updated
Tim Lunn (darkxst)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Bruce Pieterse (octoquad) wrote :

Also occurring on Ubuntu GNOME daily image for 2015-09-11.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :
Revision history for this message
Kev Bowring (flocculant) wrote :

Broken in Xubuntu, Lubuntu appears to fail at ubiquity but gives no error output.

In Vbox I also get Ubuntu failing.

Revision history for this message
Paul Stimpson (dangerjunkie2002) wrote :

I'm seeing this in the daily build I downloaded on 12 Sep 2015 at about 2200 BST (GMT+1).

The machine is a UEFI laptop with a Broadwell i7-5700HQ. Model is an MSI GT72 2QD

Revision history for this message
sudodus (nio-wiklund) wrote :

affects Lubuntu i386 too

Revision history for this message
junior0 (igor-travov-gmail) wrote :

I try to install daily build 15.10 (20150913) and i cannot do it because this error, but at july and august I have this system
on my notebook and it was rather well.....
My notebook always in legasy mode (not UEFFI) (Aspire S7, Intel® Core™ i7-3517U CPU @ 1.90GHz × 4 , Intel® Ivybridge Mobile
64-bit)

Revision history for this message
Henk Terhell (hterhell) wrote :

@junior0 what type of ubuntu are you on? This bug has now been reported for Ubuntu, Xubuntu and Lubuntu.

Revision history for this message
Doug McMahon (mc3man) wrote :

As a tmp workaround am installing ubuntu-gnome now using todays image using from terminal (from live session/try option-
sudo -H bash -c 'ubiquity gtk_ui'

Revision history for this message
Henk Terhell (hterhell) wrote :

Thanks, that does work for me with Lubuntu.

Martin Pitt (pitti)
summary: - ubiquity crashed with dbus.exceptions
+ ubiquity crashed with permission error on NetworkManager GetDevices()
+ call
Revision history for this message
volker kempter (v-kempter) wrote :

error occurs with daily build of lubuntu 15.10 (20150914) when booting with usb made with unetbootin.

Revision history for this message
Martin Pitt (pitti) wrote :

Mathieu, can you please have a look? Thank you!

Changed in ubiquity (Ubuntu Wily):
importance: Medium → High
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
milestone: none → ubuntu-15.09
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This appears to be "bad" code for calling up NetworkManager -- for some reason dbus-python now doesn't like the fact that we call up the object directly, not through a specified interface. Fixing this right now...

Changed in ubiquity (Ubuntu Wily):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.21.30

---------------
ubiquity (2.21.30) wily; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * Fix access denied crashes in calling GetDevices() for NM integration: this
    happened because we didn't specify a DBus interface for the call.
    (LP: #1495017)
  * Automatic update of included source packages: grub-installer
    1.78ubuntu29.

  [ Dan Chapman ]
  * Multiple autopilot fixes:
    - Add workaround for 'Write changes to disk' dialog. (LP: #1480430)
    - Update the use_device_desc string in generated config file use for
      english install tests.
    - Fix handling of globalRect mismatches. (LP: #1479064)
    - Fixup string comparisons to properly match Ubuntu-MATE for the english
      install tests.
    - Fix the autopilot test runner for Ubuntu-GNOME and Ubuntu-MATE.

 -- Mathieu Trudel-Lapierre <email address hidden> Tue, 15 Sep 2015 17:04:57 -0400

Changed in ubiquity (Ubuntu Wily):
status: In Progress → Fix Released
Revision history for this message
notreallyhere (notreallyhere-deactivatedaccount) wrote :

If you are unable to install image with this bug use this workaround:

1) Make sure your PC is connected to LAN or Wifi (There should be icon at top panel in right)
you can just type this command in another tty to enable network:
 # systemctl start NetworkManager

2) Run these commands in tty1
# apt-get update
# apt-get upgrade
# pkill ubiquity

3) when login appears username is ubuntu without password

Hope it works!

Revision history for this message
janne47j (janne47j) wrote : Re: [Bug 1495017] Re: ubiquity crashed with permission error on NetworkManager GetDevices() call

Works, thank you

> 16 sep 2015 kl. 22:06 skrev Marek Doležel <email address hidden>:
>
> If you are unable to install image with this bug use this workaround:
>
> 1) Make sure your PC is connected to LAN or Wifi (There should be icon at top panel in right)
> you can just type this command in another tty to enable network:
> # systemctl start NetworkManager
>
> 2) Run these commands in tty1
> # apt-get update
> # apt-get upgrade
> # pkill ubiquity
>
> 3) when login appears username is ubuntu without password
>
> Hope it works!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1495017
>
> Title:
> ubiquity crashed with permission error on NetworkManager GetDevices()
> call
>
> Status in ubiquity package in Ubuntu:
> Fix Released
> Status in ubiquity source package in Wily:
> Fix Released
>
> Bug description:
> Lubuntu Wily i386 20150911 fails to install on disk.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 15.10
> Package: ubiquity 2.21.29
> ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
> Uname: Linux 4.2.0-7-generic i686
> ApportVersion: 2.18.1-0ubuntu1
> Architecture: i386
> CasperVersion: 1.364
> Date: Sat Sep 12 06:11:40 2015
> ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
> InterpreterPath: /usr/bin/python3.4
> LiveMediaBuild: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150911)
> ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --only
> ProcEnviron: Error: [Errno 13] Permission denied: '/proc/1733/environ'
> PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
> SourcePackage: ubiquity
> Title: ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 7 matched rules; type="method_call", sender=":1.18" (uid=999 pid=1733 comm="/usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --") interface="(unset)" member="GetDevices" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1437 comm="/usr/sbin/NetworkManager --no-daemon ")
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1495017/+subscriptions

Revision history for this message
Danny Werner (tehwerner) wrote :

A workaround similar to Doug McMahon´s #11: installing ubuntu studio (Ubuntu Wily Werewolf (development branch)15.10 daily build downloaded Sept 19 2015) from terminal (from live session) worked for me:

$ sudo -i
# sh -c 'ubiquity gtk_ui'

I have two questions.

1. I did NOT
# systemctl start NetworkManager
# apt-get update
# apt-get upgrade
# pkill ubiquity
as advised by Marek in #17. Will this cause me trouble? I am writing this in the installed 15.10 Beta. Maybe NetworkManager had already started correctly in another code branch - I had checked the option ¨download updates while installing¨.

2. When I wanted to add Ubuntu Studio to the affected distributions, it was not in the dropdown choices. Shouldn ´t it?

HTH, thank you Mathieu for looking into this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.