ubiquity kde frontend crash setting up wireless when ubiquity only or oem-config

Bug #1220193 reported by Jonathan Riddell
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Dimitri John Ledkov

Bug Description

on today's daily when setting up wireless from ubiquity kde frontend it crashes when in ubiquity only mode. this is not the case when running ubiquity from a full kde plasma session.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubiquity 2.15.16
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
CasperVersion: 1.336
Date: Tue Sep 3 11:15:16 2013
InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash -- oem-config/enable=true
LiveMediaBuild: Kubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130902.2)
MarkForUpload: True
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Jonathan Riddell (jr) wrote :
Changed in ubiquity (Ubuntu):
milestone: none → ubuntu-13.10
Revision history for this message
Jonathan Riddell (jr) wrote :

doing an install in oem mode from a kubuntu install today in virtualbox the install works fine, and the oem setup is fine but on reboot it crashes on running oem-config. The crash is due to NM not running I think. This was from virtualbox, I did not have this issue on a hardware install.

Revision history for this message
Jonathan Riddell (jr) wrote :
summary: - ubiquity kde frontend crash setting up wireless when ubiquity only
+ ubiquity and oem-config kde frontend crash setting up wireless when
+ ubiquity only
summary: - ubiquity and oem-config kde frontend crash setting up wireless when
- ubiquity only
+ ubiquity kde frontend crash setting up wireless when ubiquity only or
+ oem-config
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

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/1220193

tags: added: iso-testing
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
Jonathan Riddell (jr) wrote :

Still an issue in beta 2 candidate images.

The Ubuntu (unity) images have a similar issue where the install only mode freezes while connecting to a wifi network.

Changed in ubiquity (Ubuntu):
assignee: nobody → Dmitrijs Ledkovs (xnox)
status: Confirmed → In Progress
importance: Undecided → High
Revision history for this message
Jonathan Riddell (jr) wrote :

May be duplicate for bug 1178638 "Exception in GTK frontend when attempting to connect to wifi: no logind support" which xnox is fixing

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.15.20

---------------
ubiquity (2.15.20) saucy; urgency=low

  [ Colin Watson ]
  * (Build-)depend on python3-icu rather than transitional python3-pyicu.

  [ Howard Chan ]
  * Fix the new Ubuntu Studio wallpaper backdrop for ubiquity. (LP: #1229651)

  [ Dmitrijs Ledkovs ]
  * Add dependencies on python3-pam.
  * Establish a PAM session with logind "greeter" mode in ubiquity-dm,
    resolving the following bugs:
    - WiFi page not working (LP: #1178638) (LP: #1220193)
    - Sound system / a11y not available (LP: #1229416)
    - and maybe others.
  * Automatic update of included source packages: flash-kernel
    3.0~rc.4ubuntu41.

  [ Lars Uebernickel ]
  * Force ubiquity/panel to 28 pixels height. (LP: #1207890)
 -- Dmitrijs Ledkovs <email address hidden> Wed, 25 Sep 2013 13:36:05 +0100

Changed in ubiquity (Ubuntu):
status: In Progress → Fix Released
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.