Ubiquity kde_ui crashes with TypeError: QLabel.setText(QString): argument 1 has unexpected type 'NoneType'

Bug #717222 reported by Glenn Miller Jr.
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Linux Mint
Invalid
Undecided
Unassigned
ubiquity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: ubiquity

Traceback (most recent call last):
  File "/usr/lib/ubiquity/plugins/ubi-language.py", line 528, in check_returncode_release_notes
    self.update_release_notes_label()
  File "/usr/lib/ubiquity/plugins/ubi-language.py", line 642, in update_release_notes_label
    self.page.release_notes_label.setText(text)
TypeError: QLabel.setText(QString): argument 1 has unexpected type 'NoneType'

It crashes or loops endlessly when trying to pick the partition to install. It does the same thing for both 32 bit and 64 bit linux mint 10 kde rc.

Revision history for this message
giev (vagelis-giannadakis) wrote :

Just wanted to add that in my case the installer crashed right after the first "Next" button (language). I was trying to install Linux Mint 10 KDE inside a VirtualBox VM with 1GB memory. It is probably the point when the installer enters the Disk Partitioning section.

I'm using VirtualBox 3.2.12 on an openSUSE 11.3 64bit install.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Also affect Ubuntu Maverick

Ubiquity 2.4.8

tags: added: amd64 i386 kubuntu maverick natty
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

ubiquity 2.5.4 affected

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Assign to kdebase because all this report are referred to kde env.
Fabio

affects: ubiquity (Ubuntu) → kdebase (Ubuntu)
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Why would that mean it's a KDE bug?

affects: kdebase (Ubuntu) → ubiquity (Ubuntu)
summary: - Installer crashed
+ Ubiquity kde_ui crashes with TypeError: QLabel.setText(QString):
+ argument 1 has unexpected type 'NoneType'
Changed in ubiquity (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
tags: added: ubiquity-2.4.8
Revision history for this message
Rich Johnson (nixternal) wrote :

I am unfortunately able to reproduce this error with 10.04.4 LTS, 11.10, and 12.04 installs. I have done numerous installs in a VM this evening working on other reports, and not once has it crashed by trying any of the responses in this report. Is this still occurring for those who commented in this report or others? If so, any other info to help reproduce this would be more than welcomed. Thank you.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

natty have reached EOL now

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
Changed in linuxmint:
status: New → Incomplete
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.