[Bug 1868646] Re: "Try it" installs kwallet differently than "Install now"

Ubuntu QA Website 1868646 at bugs.launchpad.net
Tue Mar 24 03:00:06 UTC 2020


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

** Tags added: iso-testing

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

Title:
  "Try it" installs kwallet differently than "Install now"

Status in ubiquity package in Ubuntu:
  New

Bug description:
  ISO testing 20.04 Kubuntu daily image (20200323). Something involving
  Kwallet & wifi is installed differently depending on whether I take
  the path "try it" (and install from Live desktop), or "install now."

  1. When I install from the Live Desktop (after clicking "try it," and
  then reboot the installed system, wifi doesn't automatically connect
  (as other Ubuntu desktop flavors do after wifi was used during the
  install). I have to manually connect, at which point Kwallet makes me
  set up a password (with no indication a null password is acceptable).

  2. When I install from "Install now," and reboot, wifi automatically
  connects. I don't have to mess around with Kwallet. Apparently
  everything is working with a null Kwallet password.

  The #1 behavior has bothered me for awhile. It hasn't felt normal to
  me. It took a month to learn that I could enter a null password and
  never be bothered by it again. I've been debating opening a bug about
  it (because it doesn't seem inviting to new users who have no idea why
  it works this way, or null is a valid password).

  I just tried "Install now" and it worked different. I think that's a
  valid bug. They should work the same, I'm sure. IMO, #2 is the proper
  behavior. If it worked that way, I would have much less concern with
  Kwallet creating an unpleasantness for new users. With #2, everything
  works the way a new user would expect it to work. (So, if/when those
  two paths to install work the same: I hope #2 is the way they both
  work.).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar 23 18:59:13 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2020-03-24 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200323)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868646/+subscriptions



More information about the foundations-bugs mailing list