ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.NetworkManager.Device.Wireless” on object at path /org/freedesktop/NetworkManager/Devices/47

Bug #1843412 reported by Ray Chen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Medium
Unassigned

Bug Description

Was during installation, this crashed was interrupt the whole install process no matter at beginning or OOBE.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.9 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
Uname: Linux 5.2.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CasperVersion: 1.415
Date: Tue Sep 10 10:10:31 2019
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash ---
InterpreterPath: /usr/bin/python3.7
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/1768/environ'
Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
PythonDetails: N/A
SourcePackage: ubiquity
Title: ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.NetworkManager.Device.Wireless” on object at path /org/freedesktop/NetworkManager/Devices/47
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Ray Chen (ray.chen) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1676647, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
information type: Private → Public
Jerry Kao (jerry.kao)
tags: added: ce-qa-concern
Revision history for this message
Will Cooke (willcooke) wrote :

I'm not 100% convinced this is a dupe. The crash in Ubiquiuty might be the same, but the root causes are different.

Sep 10 10:11:40 username kernel: iwlwifi 0000:02:00.0: LED command failed: -5
Sep 10 10:11:40 username kernel: dump_stack+0x63/0x8a
Sep 10 10:11:40 username kernel: iwl_pcie_send_hcmd_sync+0x497/0x4b0 [iwlwifi]

This one seems to be a kernel issue?

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.