Ubuntu

libc6 update fails: stack smashing detected : /usr/bin/perl

Reported by FriedChicken on 2008-09-15
8
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Undecided
Unassigned
glibc (Ubuntu)
Undecided
Unassigned
libqt-perl (Ubuntu)
Undecided
Unassigned
linux-restricted-modules-envy-2.6.24 (Ubuntu)
Undecided
Unassigned
perl (Ubuntu)
Undecided
Unassigned

Bug Description

I couldn't update libc6-i686:

$ sudo apt-get install -f
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Reading state information... Fertig
Abhängigkeit werden korrigiert... Fertig
Die folgenden zusätzlichen Pakete werden installiert:
  libc6-i686
Die folgenden Pakete werden aktualisiert:
  libc6-i686
1 aktualisiert, 0 neu installiert, 0 zu entfernen und 50 nicht aktualisiert.
11 nicht vollständig installiert oder entfernt.
Es müssen noch 0B von 1243kB Archiven geholt werden.
After this operation, 0B of additional disk space will be used.
Möchten Sie fortfahren [J/n]?
*** stack smashing detected ***: /usr/bin/perl terminated
Segmentation fault
Richte libc6 ein (2.7-10ubuntu4) ...
*** stack smashing detected ***: /usr/bin/perl terminated
dpkg: Fehler beim Bearbeiten von libc6 (--configure):
 Unterprozess post-installation script mit Signal (Segmentation fault) getötet
Fehler traten auf beim Bearbeiten von:
 libc6
E: Sub-process /usr/bin/dpkg returned an error code (1)

Maybe this bug is related to bug #205079. I had used nvidia-glx-new-envy but after a reboot (with not updated libc6) I had some trouble with the driver and used "nv" instead.

Kees Cook (kees) wrote :

Can you try enabling Apport to get the perl crash details? Edit /etc/default/apport to have "enabled=1", and then:

  sudo /etc/init.d/apport restart

And try the upgrade again.

Changed in glibc:
status: New → Incomplete
FriedChicken (domlyons) wrote :

Apport didn't open automatically but I've attached files from /var/crash.

FriedChicken (domlyons) on 2008-09-16
Changed in glibc:
status: Incomplete → Confirmed
FriedChicken (domlyons) wrote :

As this seems to be not fixed till now or is even unfixable(?), I'd like to know if there's a way to make upgrades for the other packages leaving this one out. This package blocks 80 other updates.

FriedChicken (domlyons) wrote :

I found a fix (or is it just a workaround?). I've done the same as in bug #205079 because the nvidia-glx-new-envy package doesn't seem to be fixed yet.

What I've done:
sudo mv /usr/lib/libnvidia-tls.so.173.14.12 /usr/lib/libnvidia-tls.so.173.14.12.delete
sudo mv /usr/lib/libnvidia-tls.so.1 /usr/lib/libnvidia-tls.so.1.delete
sudo ln /usr/lib/tls/libnvidia-tls.so.1 /usr/lib/libnvidia-tls.so.173.14.12
sudo ln /usr/lib/tls/libnvidia-tls.so.1 /usr/lib/libnvidia-tls.so.1

After that the libc6 package was installable, but 2 other packages could not be configured:
*** stack smashing detected ***: /usr/bin/perl terminated
Segmentation fault (core dumped)
(Lese Datenbank ... 459580 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereiten zum Ersetzen von kdm 4:3.5.10-0ubuntu1~hardy1 (durch .../kdm_4%3a3.5.10-0ubuntu1~hardy2_i386.deb) ...
*** stack smashing detected ***: /usr/bin/perl terminated
dpkg: Warnung - altes pre-removal-Skript wurde getötet durch Signal (Segmentation fault), Speicherabbild erzeugt
dpkg - probiere stattdessen Skript aus dem neuen Paket ...
*** stack smashing detected ***: /usr/bin/perl terminated
dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/kdm_4%3a3.5.10-0ubuntu1~hardy2_i386.deb (--unpack):
 Unterprozess neues pre-removal-Skript mit Signal (Segmentation fault), Speicherabbild erzeugt getötet
*** stack smashing detected ***: /usr/bin/perl terminated
dpkg: Fehler beim Aufräumen:
 Unterprozess post-installation script mit Signal (Segmentation fault), Speicherabbild erzeugt getötet
Vorbereiten zum Ersetzen von samba 3.0.28a-1ubuntu4.5 (durch .../samba_3.0.28a-1ubuntu4.6_i386.deb) ...
Entpacke Ersatz für samba ...
*** stack smashing detected ***: /usr/bin/perl terminated
Segmentation fault (core dumped)
dpkg: Warnung - altes post-removal-Skript wurde mit Fehler-Status 139 beendet
dpkg - probiere stattdessen Skript aus dem neuen Paket ...
*** stack smashing detected ***: /usr/bin/perl terminated
Segmentation fault (core dumped)
dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/samba_3.0.28a-1ubuntu4.6_i386.deb (--unpack):
 Unterprozess neues post-removal-Skript gab den Fehlerwert 139 zurück
*** stack smashing detected ***: /usr/bin/perl terminated
Segmentation fault (core dumped)
dpkg: Fehler beim Aufräumen:
 Unterprozess post-removal script gab den Fehlerwert 139 zurück
Fehler traten auf beim Bearbeiten von:
 /var/cache/apt/archives/kdm_4%3a3.5.10-0ubuntu1~hardy2_i386.deb
 /var/cache/apt/archives/samba_3.0.28a-1ubuntu4.6_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

So I guess the real problem behind that is somewhere in perl or libqt-perl.

Changed in glibc:
status: Confirmed → Invalid
FriedChicken (domlyons) on 2008-09-21
Changed in perl:
status: New → Invalid
FriedChicken (domlyons) wrote :

I've edited /var/cache/debconf/config.dat manually because "sudo dpkg-reconfigure debconf" didn't work anymore, too. I've changed
   Name: debconf/frontend
   Template: debconf/frontend
   Value: Kde
   Owners: debconf
   Flags: seen
to
   [...]
   Value: Dialog
   [...]

That worked, so the problem seems to be in libqt-perl or the qt-frontend of debconf.

Changed in linux-restricted-modules-envy-2.6.24:
status: New → Invalid
aftertaf (david-wooffindin) wrote :

I confirm the workaround above...

modify the debconf/frontend to use Dialog instead of KDE and this enables a "dpkg -i" to work:

1st try without change:
root@ubuntu:/# dpkg -i /var/cache/apt/archives/debconf_1.5.23ubuntu1_all.deb
(Reading database ... 273978 files and directories currently installed.)
Preparing to replace debconf 1.5.23ubuntu1 (using .../debconf_1.5.23ubuntu1_all.deb) ...
Unpacking replacement debconf ...
Setting up debconf (1.5.23ubuntu1) ...
*** stack smashing detected ***: /usr/bin/perl terminated
dpkg: error processing debconf (--install):
 subprocess post-installation script killed by signal (Segmentation fault)
Errors were encountered while processing:
 debconf

Here I followed the fix mentioned above:
root@ubuntu:/# vim /var/cache/debconf/config.dat

And 2nd try for installing debconf:
root@ubuntu:/# dpkg -i /var/cache/apt/archives/debconf_1.5.23ubuntu1_all.deb
(Reading database ... 273978 files and directories currently installed.)
Preparing to replace debconf 1.5.23ubuntu1 (using .../debconf_1.5.23ubuntu1_all.deb) ...
Unpacking replacement debconf ...
Setting up debconf (1.5.23ubuntu1) ...

Now i hope the beta of intrepid will install, because a lot of dependencies were stuck with this same error or because of packages concerned.....

79 upgraded, 67 newly installed, 3 to remove and 62 not upgraded.
1272 not fully installed or removed.
Need to get 0B/75.2MB of archives.
After this operation, 193MB of additional disk space will be used.
Do you want to continue [Y/n]?

Say YES !!!
:)

Kees Cook (kees) wrote :

I can't reproduce the crash (I'm on amd64), but Kde does not load for me (the fix for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481642 fixes that for me).

Does anyone who is seeing this crash have a simple way to reproduce it?

Changed in debconf:
status: New → Invalid
Changed in libqt-perl:
status: New → Incomplete

a similar problem (maybe same cause) was discussed in bug 283942
the debconf kde frontend is dysfunctional partway through the kde3->kde4 transition

Jean-Baptiste Lallement (jibel) wrote :

Yes, I think so. From this report and duplicates, this bugs only happens with the kde frontend. Thanks you.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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