[apport] dpkg-preconfigure crashed with SIGSEGV in xcall_QGroupBox()

Bug #87641 reported by cowboy777
338
This bug affects 3 people
Affects Status Importance Assigned to Milestone
debconf (Debian)
Fix Released
Unknown
debconf (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: debconf

I had started the updates that were available today from adpet_notifier.
At one point en error popped up stating "incorrect nice value. Please enter an integer between -20 and 19.
There was no place to enter the value. The only options available were <Help>, <Next> and <Cancel>.
I click on <Next> and the crash occurred.

ProblemType: Crash
Date: Sat Feb 24 13:48:49 2007
Disassembly: 0x2f736576:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/dpkg-preconfigure
InterpreterPath: /usr/bin/perl
Package: debconf 1.5.11ubuntu1
ProcCmdline: /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt
ProcCwd: /home/kharris
ProcEnviron:
 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: debconf
StacktraceTop:
 ?? ()
 xcall_QGroupBox () from /usr/lib/libsmokeqt.so.1
 smokeperl_free () from /usr/lib/perl5/auto/Qt/Qt.so
 Perl_mg_free ()
 Perl_sv_clear ()
Uname: Linux pc-kharris 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
cowboy777 (kharris) wrote :
Revision history for this message
cowboy777 (kharris) wrote :

After submitting this bug report I closed adept_notifier and ran "apt-get update" then "apt-get upgrade".
There was on error that occurred in that process:
"Preparing to replace kubuntu-default-settings 1:7.04-21 (using .../kubuntu-default-settings_1%3a7.04-23_all.deb) ..."
"Unpacking replacement kubuntu-default-settings ..."
"Unknow argument for /var/lib/dpkg/info/kubuntu-default-settings.postrm"
Don't really know if this is related.

Revision history for this message
Marco Maini (maini10) wrote :

The problem described in this bug report was happened also in my Pc during the updates of yesterday.

Revision history for this message
Ian Hollander (arcaneninja) wrote :

Running Kubuntu 7.04 kernel 2.20.8-386
Apport just reported the "frontend" had crashed while apps were initializing during KDE start up. Debconf package was selected by Apport as the offending package.

Changed in debconf:
status: Unconfirmed → Confirmed
Revision history for this message
plaa (plaa-deactivatedaccount) wrote :

Happened to me also, I`m using Kubuntu 7.04.
But for me it didn`t really crash, i couldn´t press next, so i pressed cancel,
after that adept updater said "Could not commit changes" and so on,
and stopped installing.

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

After posting my comment I closed adept and upgraded using console, it worked fine, didn`t give any errors or anything like that.

Revision history for this message
marcmpub (marcmpub) wrote :

happened to me too, I can't use anymore adept update cause a few days ago as it was never ending stopping and crashing I lost totally control of my PC and it wasn't possible to stop it the right way. I had to switch off wrong way (power down) and then the fils system refused to start-up any more. i had tyo resintall again averything. I use the alternate amd64 6.10 that after hand I UPGRADE to feisty (editing source list). Reason is from the live cd rom it refuses to format and install in teh partition I want it goes to. BUT with the 6.10 alternate cdrom it does what I want then I just need to update. It goes fine and I can do some upgrade untill it complains for thoses missing values.

Revision history for this message
cowboy777 (kharris) wrote : RE: [Bug 87641] Re: [apport] dpkg-preconfigure crashed with SIGSEGV inxcall_QGroupBox()

try this to get past the problem:
Open konsole
sudo apt-get update
sudo apt-get upgrade

The first will fetch the list of updatable packages.
The second will download and install them.
This will fix adept for you.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>]On Behalf Of
marcmpub
Sent: Tuesday, March 06, 2007 10:23 AM
To: Kelvin Harris
Subject: [Bug 87641] Re: [apport] dpkg-preconfigure crashed with SIGSEGV
inxcall_QGroupBox()

happened to me too, I can't use anymore adept update cause a few days
ago as it was never ending stopping and crashing I lost totally control
of my PC and it wasn't possible to stop it the right way. I had to
switch off wrong way (power down) and then the fils system refused to
start-up any more. i had tyo resintall again averything. I use the
alternate amd64 6.10 that after hand I UPGRADE to feisty (editing source
list). Reason is from the live cd rom it refuses to format and install
in teh partition I want it goes to. BUT with the 6.10 alternate cdrom it
does what I want then I just need to update. It goes fine and I can do
some upgrade untill it complains for thoses missing values.

--
[apport] dpkg-preconfigure crashed with SIGSEGV in xcall_QGroupBox()
https://launchpad.net/bugs/87641

Revision history for this message
Jonathan 'Naithin' McFarlane (naithin) wrote : DebConf db Locked

When Adept raised the Nice error, cancelling didn't seem to totally remove the debconf prompt.. Or rather, it possibly did, but the subsequent attempts to test Adept brought the issue up again, only the Nice warnings were no longer shown.

Trying command line apt-get upgrade complains that debconf was still locking the db. So I restarted PC, and during shutdown, the nice error then re-appeared from whereever it had been hiding.

Upon restart, apt-get upgrade worked without issue.

Revision history for this message
K Mi (k-misfit) wrote : Nice value error: x11-common

I ran apt-get upgrade from the command line as suggested and the nice error persisted, but now in a ncurses-like CLI (see attachment).

Therefore it has nothing to do with adept but with the package *x11-common*. If I de-select it, the upgrade runs just fine. Kubuntu Herd 5 here.

Revision history for this message
Jan-Erik van de Pol (pollypicasso-deactivatedaccount) wrote :

Here the same.

Feisty 7.04 Herd 5 (upgraded from 7.04 Herd 2)

Revision history for this message
Oscar (osh-nbit) wrote :

Same here. Atleast I think it's the same.

Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN1> line 4.
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN1> line 9.
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN1> line 17.
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN1> line 25.

Revision history for this message
Asraniel (asraniel) wrote :

i think i have the same. here is the last output of adept i get:

X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Extrahiere Templates aus Paketen: 100%
DESTROY created new reference to dead object ' Qt::VBoxLayout', <> line 35 during global destruction.
Vorkonfiguration der Pakete ...
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN3> line 4.
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN3> line 9.
DESTROY created new reference to dead object ' Qt::VBoxLayout' during global destruction.
(Lese Datenbank ... 89334 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereiten zum Ersetzen von x11-common 1:7.2-0ubuntu6 (durch .../x11-common_1%3a7.2-0ubuntu7_i386.deb) ...
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN1> line 4.
Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, <GEN1> line 9.

Revision history for this message
Marco Maini (maini10) wrote :

This bug is also reported in Debian bug tracker as #413716.

Revision history for this message
Marco Maini (maini10) wrote :

Sorry, Debian bugs #413716 is a clone of #413509. According to Debian developers bug #413509 is fixed with a patch in the version 1.5.13 of debconf included in Debian unstable.

Changed in debconf:
status: Unknown → Fix Released
Revision history for this message
Paul Dufresne (paulduf) wrote :

This is also bug #68267 which is now fixed in feisty (was a bug in x11-common configuration script).
In my opinion, the fact that it caused debconf to SIGSEGV have not enough been examined enough however.

Now, I am not too sure how to handle this (I means bug #68267 is considered close with 10 duplicates, this one have 38, still open on libqt-perl, which is not clear to me what it does have to do with the bug, Debian fixing one way and Ubuntu an other).

Revision history for this message
Marco Maini (maini10) wrote :

Latest version of debconf 1.5.14 claims to fix this.

Changed in libqt-perl:
status: Confirmed → Fix Released
To post a comment you must log in.