[Bug 1955542] Re: Kubuntu OEM Installer crash when clicking next

Chris Guiver 1955542 at bugs.launchpad.net
Wed Dec 22 11:40:25 UTC 2021


Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1955542

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

If you cannot run this from the installed system, please boot the
installation media on the machine you installed on and run `apport-
collect` from there (that will provide release details as well as the
relevant hardware details).  Please leave a comment if you do this, so
it's known how the details provided relate to your issue. Currently no
release details are known, nor what ISO was used to install, etc. so
it's difficult to evaluate the issue.

After running `apport-collect` the status can be returned to "New". If
you're unable to complete this; please leave a comment with details (and
the status can also be returned to "New").

** Changed in: ubiquity (Ubuntu)
       Status: New => Incomplete

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

Title:
  Kubuntu OEM Installer crash when clicking next

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  - Install Kubuntu as OEM installation
  - boot into installer, follow until account creation
  - enter account details, click next

  - clicking "next"  on the next screen crashes the installer

  
  Error message:
    Installer Crashed

  Traceback (most recent call last):
    File "/usr/lib/ubiquity/frontend/kde_ui.py", ;line 1076, in on_next_clicked
    ui=self.pages[self.pagesindex].ui
   IndexError: list index out of range

  
  Unfortunately I can't attach any other logs, as the "oem" password is unknown and a login via tty is therefore impossible

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




More information about the foundations-bugs mailing list