Installation chrashed | Kubuntu installer prompted all of this.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Lenovo T540P 20BE0085US
So, when the Kubuntu installer crashed it said run ubuntu-bug ubiquity and here we are.
Installed from USB drive loaded with Kubuntu nightly build by UNetbootin.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.43
ProcVersionSign
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CasperVersion: 1.366
CurrentDesktop: KDE
Date: Fri Feb 5 02:28:21 2016
InstallCmdLine: BOOT_IMAGE=
LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
Just looking at the last few lines of attached file UbiquitySyslog.txt show where the installation exited:
> Feb 5 02:27:21 kubuntu ubiquity[3148]: Exception in KDE frontend (invoking crash handler): ubiquity/ ubiquity/ frontend/ kde_ui. py", line 1068, in on_next_clicked ok_handler( ) ubiquity/ plugins/ ubi-prepare. py", line 344, in ok_handler get_secureboot_ key() _key'
Feb 5 02:27:21 kubuntu ubiquity[3148]: Traceback (most recent call last):
Feb 5 02:27:21 kubuntu ubiquity[3148]: File "/usr/lib/
Feb 5 02:27:21 kubuntu ubiquity[3148]: self.dbfilter.
Feb 5 02:27:21 kubuntu ubiquity[3148]: File "/usr/lib/
Feb 5 02:27:21 kubuntu ubiquity[3148]: secureboot_key = self.ui.
Feb 5 02:27:21 kubuntu ubiquity[3148]: AttributeError: 'PageKde' object has no attribute 'get_secureboot
> Feb 5 02:27:21 kubuntu ubiquity[3148]:
===
Thank you for taking the time to report this bug and helping to make Ubuntu better.
This particular bug has already been reported and is a duplicate of bug #1529450, so it 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.
Feel free to continue to report any other bugs you may find.