qtparted seems to crash on some setups; deal with this better?

Bug #47194 reported by Christophe
456
This bug affects 10 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Medium
Colin Watson

Bug Description

When trying to install Kubuntu Dapper RC, the installer crashes at partitionning steps.
After choosing "Modify partition table manually" and clicking next buton, the installer does the task of getting information about partitions and filesystems but on the next screen, the partition table and the corresponding menu are not displayed. First click on the "next" button does nothing and a second click displays the following error message:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 120, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 54, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 726, in process_step
    self.gparted_to_mountpoints()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 799, in gparted_to_mountpoints
    print >>self.qtparted_subp.stdin, "apply"
AttributeError: 'NoneType' object has no attribute 'stdin'

**************************************************************************************************************
Below is "syslog" file contents:
**************************************************************************************************************

Ubiquity 1.0.7
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
/usr/bin/iceauth: creating new authority file /root/.ICEauthority
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
kio (KSycoca): ERROR: No database available!
Invalid entry (missing '=') at /tmp/kde-root/kconf_update2Ccova.tmp:1
ubiquity: Starting up '['/usr/lib/ubiquity/localechooser/localechooser']' for ubiquity.components.language.Language
ubiquity: Watching for question patterns ^languagechooser/language-name
Mon, 29 May 2006 21:12:30 INFO Step_before = stepLanguage
Mon, 29 May 2006 21:12:31 INFO Step_after = stepLocation
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: Starting up '['/usr/share/ubiquity/tzsetup']' for ubiquity.components.timezone.Timezone
ubiquity: Watching for question patterns ^time/zone$
ubiquity: ['/usr/share/ubiquity/tzsetup'] exited with code 10
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: Starting up '['/usr/lib/ubiquity/localechooser/localechooser']' for ubiquity.components.language.Language
ubiquity: Watching for question patterns ^languagechooser/language-name
lun, 29 mai 2006 21:12:53 INFO Step_before = stepLanguage
lun, 29 mai 2006 21:12:54 INFO Step_after = stepLocation
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: Starting up '['/usr/share/ubiquity/tzsetup']' for ubiquity.components.timezone.Timezone
ubiquity: Watching for question patterns ^time/zone$
lun, 29 mai 2006 21:13:06 INFO Step_before = stepLocation
lun, 29 mai 2006 21:13:06 INFO Step_after = stepKeyboardConf
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: kbd-chooser prepare
ubiquity: Starting up '['/bin/sh', '-c', '. /usr/share/debconf/confmodule; exec /usr/lib/ubiquity/kbd-chooser/kbd-chooser']' for ubiquity.components.kbd_chooser.KbdChooser
ubiquity: Watching for question patterns ^kbd-chooser/method$, ^console-keymaps.*/keymap$, ERROR
ubiquity: apply_keyboard: fr-latin9
ubiquity: apply_keyboard: layout fr, variant latin9
ubiquity: Display map: {u'Bulgare (bg)': u'bg', u'Turc (trfu)': u'trfu', u'Suisse romand (fr_CH-latin1)': u'fr_CH-latin1', u'Britannique (uk)': u'uk', u'Suisse al\xe9manique (sg-latin1)': u'sg-latin1', u'Br\xe9silien (br-latin1)': u'br-latin1', u'H\xe9breu (hebrew)': u'hebrew', u'Belge (be2-latin1)': u'be2-latin1', u'Croate (croat)': u'croat', u'Japonais (jp106)': u'jp106', u'Turc (trqu)': u'trqu', u'Fran\xe7ais (fr-latin9)': u'fr-latin9', u'Serbe cyrillique (sr-cy)': u'sr-cy', u'Letton (lv-latin4)': u'lv-latin4', u'N\xe9erlandais (nl)': u'nl', u'Roumain (ro)': u'ro', u'Canadien fran\xe7ais (cf)': u'cf', u'\xc9tats-Unis (us)': u'us', u'Dvorak': u'dvorak', u'Am\xe9rique latine (la-latin1)': u'la-latin1', u'Br\xe9silien (br-abnt2)': u'br-abnt2', u'Islandais (is-latin1)': u'is-latin1', u'Ukrainien (ua)': u'ua', u'Norv\xe9gien (no-latin1)': u'no-latin1', u'Su\xe9dois (se-latin1)': u'se-latin1', u'Allemand (de-latin1-nodeadkeys)': u'de-latin1-nodeadkeys', u'Mac\xe9donien (mk)': u'mk', u'Slovaque (sk-qwerty)': u'sk-qwerty', u'Polonais (pl)': u'pl', u'Tch\xe8que Latin-2 (cz-lat2)': u'cz-lat2', u'B\xe9larusse (by)': u'by', u'Danois (dk-latin1)': u'dk-latin1', u'Grec (gr)': u'gr', u'Lithuanien (lt)': u'lt', u'Finnois (fi-latin1)': u'fi-latin1', u'Russe (ru)': u'ru', u'Espagnol (es)': u'es', u'Italien (it)': u'it', u'Estonien (et)': u'et', u'Slov\xe8ne (slovene)': u'slovene', u'Hongrois (hu)': u'hu', u'Portugais (pt-latin1)': u'pt-latin1'}
ubiquity: Untranslated choices: [u'by', u'bg', u'croat', u'cz-lat2', u'sg-latin1', u'de-latin1-nodeadkeys', u'dk-latin1', u'us', u'uk', u'dvorak', u'et', u'es', u'la-latin1', u'fi-latin1', u'fr-latin9', u'be2-latin1', u'cf', u'fr_CH-latin1', u'gr', u'hebrew', u'hu', u'is-latin1', u'it', u'lt', u'lv-latin4', u'jp106', u'mk', u'no-latin1', u'nl', u'pl', u'pt-latin1', u'br-abnt2', u'br-latin1', u'ro', u'ru', u'sk-qwerty', u'slovene', u'sr-cy', u'se-latin1', u'trfu', u'trqu', u'ua']
ubiquity: Choices: [u'B\xe9larusse (by)', u'Bulgare (bg)', u'Croate (croat)', u'Tch\xe8que Latin-2 (cz-lat2)', u'Suisse al\xe9manique (sg-latin1)', u'Allemand (de-latin1-nodeadkeys)', u'Danois (dk-latin1)', u'\xc9tats-Unis (us)', u'Britannique (uk)', u'Dvorak', u'Estonien (et)', u'Espagnol (es)', u'Am\xe9rique latine (la-latin1)', u'Finnois (fi-latin1)', u'Fran\xe7ais (fr-latin9)', u'Belge (be2-latin1)', u'Canadien fran\xe7ais (cf)', u'Suisse romand (fr_CH-latin1)', u'Grec (gr)', u'H\xe9breu (hebrew)', u'Hongrois (hu)', u'Islandais (is-latin1)', u'Italien (it)', u'Lithuanien (lt)', u'Letton (lv-latin4)', u'Japonais (jp106)', u'Mac\xe9donien (mk)', u'Norv\xe9gien (no-latin1)', u'N\xe9erlandais (nl)', u'Polonais (pl)', u'Portugais (pt-latin1)', u'Br\xe9silien (br-abnt2)', u'Br\xe9silien (br-latin1)', u'Roumain (ro)', u'Russe (ru)', u'Slovaque (sk-qwerty)', u'Slov\xe8ne (slovene)', u'Serbe cyrillique (sr-cy)', u'Su\xe9dois (se-latin1)', u'Turc (trfu)', u'Turc (trqu)', u'Ukrainien (ua)']
ubiquity: console-keymaps-at/keymap db: fr-latin9
lun, 29 mai 2006 21:13:18 INFO Step_before = stepKeyboardConf
ScimInputContextPlugin()
lun, 29 mai 2006 21:13:19 INFO Step_after = stepUserInfo
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: Starting up '['/usr/lib/ubiquity/user-setup/user-setup-ask', '/target']' for ubiquity.components.usersetup.UserSetup
ubiquity: Watching for question patterns ^passwd/user-fullname$, ^passwd/username$, ^passwd/user-password$, ^passwd/user-password-again$, ERROR
ON STATE: 1
ON STATE: 2
ON STATE: 3
ON STATE: 4
ON STATE: 5
ON STATE: 6
ON STATE: 7
ON STATE: 8
lun, 29 mai 2006 21:13:42 INFO Step_before = stepUserInfo
lun, 29 mai 2006 21:13:42 INFO Step_after = stepPartDisk
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: Starting up '/bin/partman' for ubiquity.components.partman.Partman
ubiquity: Watching for question patterns ^partman-auto/select_disk$, ^partman-auto/.*automatically_partition$, ^partman-partitioning/new_size$, ^partman/choose_partition$, ^partman/confirm.*, type:boolean, ERROR, PROGRESS
unsupported
kernelmodules_basicfilesystems
kernelmodules_ext3
kernelmodules_jfs
kernelmodules_reiserfs
kernelmodules_xfs
umount_target
parted
dump
update_partitions
filesystems_detected
auto_mountpoints
autouse_swap
backup
ubiquity: /bin/partman exited with code 10
lun, 29 mai 2006 21:13:59 INFO Step_before = stepPartDisk
lun, 29 mai 2006 21:13:59 INFO gparted_loop()
lun, 29 mai 2006 21:13:59 INFO Disabling swap on /dev/hda7
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
ScimInputContextPlugin()
No Implementation: Le support pour l'ouverture du système de fichiers ntfs n'est pas encore implémenté.
No Implementation: Le support pour l'ouverture du système de fichiers ntfs n'est pas encore implémenté.
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x3000001
lun, 29 mai 2006 21:14:07 INFO Step_after = stepPartAdvanced
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 25
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 12
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 12
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 8
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 12
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 12
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 8
  Minor opcode: 0
  Resource id: 0x3000001
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 25
  Minor opcode: 0
  Resource id: 0x3000001
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
lun, 29 mai 2006 21:14:16 INFO Step_before = stepPartAdvanced
lun, 29 mai 2006 21:14:16 INFO Step_after = stepPartAdvanced
lun, 29 mai 2006 21:14:19 INFO Step_before = stepPartAdvanced
Exception in KDE frontend (invoking crash handler):
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 120, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 54, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 726, in process_step
    self.gparted_to_mountpoints()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 799, in gparted_to_mountpoints
    print >>self.qtparted_subp.stdin, "apply"
AttributeError: 'NoneType' object has no attribute 'stdin'

**************************************************************************************************************************
Partman log is quite long , but I can join it if necessary...

Revision history for this message
Jonathan Riddell (jr) wrote :

Seems like a qtparted issue, does qtparted work when run standalone? What filesystems do you have on your hard disk?

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Christophe (cmonget) wrote :

You're right, qtparted run standalone is closing suddenly when trying to read hard disk partition contents

My hard disk contains:

1 primary partition (NTFS)
1 extented partition (NTFS)

Any idea about the problem?

Revision history for this message
ik80 (ik80-deactivatedaccount) wrote :

i have the same problem, QTParted closes as i try to load the HDA. i have 2 HDs and want to install KUBUNTU dapper on HDB. I posted my bug as 47937.
gonna keep track of it here. thanks.

Revision history for this message
Christophe (cmonget) wrote :

I solved my problem using Partition Magic (I spent a lot of time to find out the cause)
I checked all my NTFS filesystems using the "check for errors" functionality.
PM reported the following error message on a NTFS Filesystem:
error 1529: Information mismatch in directory entry
So I moved all my data to an other partition and I deleted defective partition using the "secure erase" option
Then I created a new partition in the unlocated space, checked for errors again and everything was ok...
QParted works after that...
Hope this will be able to solve your problem...
If this is the case, many similar bugs could be closed...

Revision history for this message
ik80 (ik80-deactivatedaccount) wrote :

yes, same problem here (bug 47937): error on NTFS partition (my C:\) using CHKDSK. Will format it ASAP. thanks!

Revision history for this message
Colin Watson (cjwatson) wrote :

ubiquity (1.1.1) edgy; urgency=low

  * Use 'replace' Unicode error handling when dealing with data coming from
    debconf (closes: Malone #44595, #48732).
  * Fix ubiquity/install/apt_error_install and
    ubiquity/install/apt_error_remove templates to be of type 'error'
    (closes: Malone #53258).
  * Install more defence against gparted/qtparted crashing (closes: Malone
    #47194, #48856).
  * If gparted or qtparted crashes, put up a dialog allowing the user to try
    again, return to autopartitioning, or quit the installer. This is a
    pretty awful hack, but hopefully we won't be using gparted/qtparted for
    all that much longer ...
  * Fix crash in KDE frontend while translating widgets (closes: Malone
    #53367).

 -- Colin Watson <email address hidden> Tue, 18 Jul 2006 22:09:21 +0100

Further bugs about qtparted crashing should be in the form of bug reports against qtparted. It would be ideal if you could manage to reproduce them by running qtparted standalone (i.e. not via the installer).

Changed in ubiquity:
assignee: nobody → kamion
status: Needs Info → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :
Download full text (3.3 KiB)

This will also be fixed in the first Dapper point release.

ubiquity (1.0.13) dapper-updates; urgency=low

  * Don't require entering a full name (see
    http://www.hermann-uwe.de/blog/os-install-experiences-part-4-ubuntu).
  * GTK frontend:
    - Return None from location_from_point if point is None (thanks to Chris
      Moore for the idea; closes: Malone #48885).
  * KDE frontend:
    - Add slightly more paranoia in case getNearestCity returns None.
  * Don't show hw-detect/modprobe_error, and make it non-fatal (closes:
    Malone #48524).
  * Make it clear in the crash dialog that you should file a new bug, not
    attach your details to an existing bug.
  * Take a copy of the supplied choice map in set_keyboard_choices.
  * Save tracebacks from install.py and slurp them back into the traceback
    displayed if install.py exits non-zero.
  * Warn in the partitioner if you try to use XFS for /boot (closes: Malone
    #47848).
  * Warn in the partitioner if system filesystems are not reformatted
    (closes: Malone #47046).
  * Use os._exit() rather than sys.exit() in the apt install progress child
    process after forking, fixing a lot of strange "PROGRESS STOP" messages
    in /var/log/installer/syslog and bizarre debconf exceptions. See also
    Malone #53298.
  * Use 'replace' Unicode error handling when dealing with data coming from
    debconf (closes: Malone #44595, #48732).
  * Fix ubiquity/install/apt_error_install and
    ubiquity/install/apt_error_remove templates to be of type 'error'
    (closes: Malone #53258).
  * Install more defence against gparted/qtparted crashing (closes: Malone
    #47194, #48856).
  * If gparted or qtparted crashes, put up a dialog allowing the user to try
    again, return to autopartitioning, or quit the installer. This is a
    pretty awful hack, but hopefully we won't be using gparted/qtparted for
    all that much longer ...
  * Fix crash in KDE frontend while translating widgets (closes: Malone
    #53367).
  * When an error occurs with the install progress bar up, only return to
    autopartitioning if the partitioner is still running.
  * Turn DebconfInstallProgress upside-down so that the main process handles
    apt installation and the subprocess handles the translation of apt
    status messages into debconf protocol messages, rather than the other
    way round. The previous approach resulted in exceptions from apt ending
    up in the wrong process.
  * Silence apt errors while installing language packs, since we ignore them
    anyway.
  * Point apt at /target/var/lib/dpkg/status rather than
    /var/lib/dpkg/status (closes: Malone #47859).
  * Display grub-installer/install_to_xfs question if it's asked.
  * Fix get_filesystems() not to assume ext3 in quite so many situations.
  * Detect XFS for validation purposes even when it wasn't just formatted by
    gparted/qtparted (closes: Malone #53642).
  * Fix all mentions of gparted in the KDE frontend.
  * Leave existing newworld boot partitions alone when committing manual
    partitioning changes.
  * Always set mirror/country to the country selected on the timezone page,
    regardless of what localechooser does thereafter (closes: Ma...

Read more...

Revision history for this message
rseaward (rseaw) wrote : Re: [Bug 47194] Re: qtparted seems to crash on some setups; deal with this better?

How do I get my name off of this thread?

Thanks.

--- Colin Watson <email address hidden> wrote:

> ** Bug 61736 has been marked a duplicate of this bug
>
> --
> qtparted seems to crash on some setups; deal with this better?
> https://launchpad.net/bugs/47194
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Revision history for this message
Nikoo (nikoolinux) wrote : Re: [Bug 47194] Re: qtparted seems to crash on some setups; deal with this better?

Yes me too, because the bug of this thread is mentioned by tons of
people and is getting on my nerves too :-)

rseaward a écrit :
> How do I get my name off of this thread?
>
> Thanks.
>
> --- Colin Watson <email address hidden> wrote:
>
>
>> ** Bug 61736 has been marked a duplicate of this bug
>>
>> --
>> qtparted seems to crash on some setups; deal with this better?
>> https://launchpad.net/bugs/47194
>>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>

Revision history for this message
saads (shakhshir) wrote : Re: [Bug 47194] Re: qtparted seems to crash on some setups; deal with this better?

There's an unsubscribe button on launchpad (top left of the page). If
you're still getting messages then it's because you're subscribed to a
duplicate. The duplicates are also listed on the left side. Unfortunately
the only way I know to get off the duplicates is to search through them and
then take yourself off.

Revision history for this message
Nikoo (nikoolinux) wrote :

Selon saads <email address hidden>:

> There's an unsubscribe button on launchpad (top left of the page). If
> you're still getting messages then it's because you're subscribed to a
> duplicate. The duplicates are also listed on the left side. Unfortunately
> the only way I know to get off the duplicates is to search through them and
> then take yourself off.
>
> --
> qtparted seems to crash on some setups; deal with this better?
> https://launchpad.net/bugs/47194
>

On my personal details webpage, it is said that I'm not subscribed to any bug.
Therefore I shouldn't receive any report.

Strange.

Revision history for this message
Manuel López-Ibáñez (manuellopezibanez) wrote :

@Nikoo

You are completely right, I have filed bug #65736 for Malone describing this problem.

Revision history for this message
Nick Webb (webbn) wrote :

I've got the same issue a year later using Dapper (6.06.1). This was on a brand new server, but perhaps the OEM setup NTFS partitions. Not sure. I went ahead and kicked off a rebuild of the 2TB disk array... I'm guessing this is fixed in Edgy (or whatever is after Dapper)?

Nick

Revision history for this message
Colin Watson (cjwatson) wrote :

Nick: While at this point I don't remember exact details of further manifestations of problems like this bug, I can say that this entire issue has gone away for good with the advanced partitioner rewrite in 7.04. (Of course, as always, rewrites introduce new issues, but I believe they're generally less severe and more tractable than the problems with using qtparted.)

Revision history for this message
Nick Webb (webbn) wrote :

Thanks Colin -

I'm pretty sure the issue with this was on a server with a newer 3ware card (9650) that was not supported in dapper. Fix was to copy over a pre-compiled driver before this spot in the installation, then compiling the same after upgrading the kernel.

The 8.04 installer works fine as the kernel includes the module for the 3ware 9650 card.

Still, the installer shouldn't crash without any information in this situation. How about a "no disks were found, aborting" message? Anyway, I certainly wouldn't fix this in dapper, but if 8.04 has the same issue with unsupported controllers, a better message and a more graceful exit should be added.

Thanks!

To post a comment you must log in.