frontend crashed with SIGSEGV in abort()

Bug #131236 reported by Sebastian Schack
122
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: debconf

I seriously don't know under which circumstances this error occured... sorry.

ProblemType: Crash
Architecture: i386
Date: Sat Aug 4 10:16:00 2007
Disassembly: 0x40745640:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/share/debconf/frontend
InterpreterPath: /usr/bin/perl
NonfreeKernelModules: nvidia
Package: debconf 1.5.14
PackageArchitecture: all
ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/tmp.ci/preinst upgrade 1:7.2-5ubuntu2
ProcCwd: /
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: debconf
StacktraceTop:
 ?? ()
 ?? () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
Title: frontend crashed with SIGSEGV in abort()
Uname: Linux multimedia 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups:
SegvAnalysis:
 Segfault happened at: 0x40745640:
 PC (0x40745640) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA

Tags: apport-crash
Revision history for this message
Sebastian Schack (sschack) wrote :
Revision history for this message
Alexey Ermakov (strangebrew) wrote :

Same problem. Occurred today (not for the first time). It happens only when upgrading with adept and not always.
Ubuntu Gutsy, 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux

Revision history for this message
einfach (freu-dich) wrote :

I had that problem today while updating with adept (Kubuntu Gutsy i386 on amd64)
it happened on every Computer i tried to update.
The Update-process stopped pressing the "ok" button. (..there was an error...)
 after "sudo apt-get -f install" everything seemed to be ok.

Revision history for this message
einfach (freu-dich) wrote :

this was the shown error: *** stack smashing detected ***: /usr/bin/perl terminated

Revision history for this message
Daniel Cordey (dc-mjt) wrote :

I've experienced thsi crash several time. I wonder if this is due to a missing package needed by frontend... The frontend seems to be called by adept when a question needs to be answered, but this is not always the case. This time, runing 'apt-get dist-upgrade' didn't ask any question and the upgrade ran till the end withoutr any trouble.

Revision history for this message
Hasse Bylov (hassebylov) wrote :

This happend at the same time as another error - "twistd crashed with OperationalError in __init__()". I don't know if it has anything to do with it... Pre the bug, I installed new firmware (internal modem on HP Pavilion) and upgraded the system.

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote :

Happened while Adept Updater was updating in the background.

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote :

... and as always when Adept Updater fails on Gutsy Tribe 5, sudo aptitude dist-upgrade works perfectly.

Hey! What if Adept would launch a terminal with aptitude (!) -- jk

Revision history for this message
Alexander B. (sysctl) wrote :

Same for me. When configuring debconf: *** stack smashing detected ***: /usr/bin/perl terminated

Revision history for this message
plusplus (strosset) wrote :

Same error here while upgrading kubuntu to gutsy with adept_manager

Revision history for this message
Nick Coghlan (ncoghlan) wrote :

The automatic upgrade broke for me as well, and I'm not about to restart the machine without some assurance it is in a vaguely sane state :)

Running the following in a terminal window appears to resolve the issue:

sudo apt-get -f install
sudo apt-get dist-upgrade

(As I recall, I had to do the same thing with the Edy->Feisty upgrade)

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote : Re: [Bug 131236] Re: frontend crashed with SIGSEGV in abort()

I don't know what's wrong, some people say that Adept doesn't handle
dependencies as well as apt-get, or as well as aptitude, but I never upgrade
my system using a graphical application. :)

Adept Notifier is good OTOH.

On 10/23/07, Nick Coghlan <email address hidden> wrote:
>
> The automatic upgrade broke for me as well, and I'm not about to restart
> the machine without some assurance it is in a vaguely sane state :)
>
> Running the following in a terminal window appears to resolve the issue:
>
> sudo apt-get -f install
> sudo apt-get dist-upgrade
>
> (As I recall, I had to do the same thing with the Edy->Feisty upgrade)
>
> --
> frontend crashed with SIGSEGV in abort()
> https://bugs.launchpad.net/bugs/131236
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
http://obsidianlake.blogspot.com/

Revision history for this message
megabug (megabug-autistici-deactivatedaccount) wrote :

I had the same problem.
I noticed that crash appear when the upgrate tool try to configure perl package after unpacking.

IMHO the problem is that, in this particular situation, the installed libraries and the running perl doesn't match, causing the stack corruption.

Bye

Changed in debconf:
importance: Undecided → Medium
Kees Cook (kees)
description: updated
Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote : Paul-Sebastian Manole wants to stay in touch on LinkedIn

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Paul-Sebastian Manole

Paul-Sebastian Manole
Electronic Security Systems Technician at SHIFT 3 SECURITY S.R.L.
Romania

Confirm that you know Paul-Sebastian Manole
https://www.linkedin.com/e/isd/1040409542/JJkNGnsh/

------
(c) 2010, LinkedIn Corporation

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed that the version of Ubuntu your using is in End of Life status. More information may be found at: https://wiki.ubuntu.com/Releases As well, the package version your bugging is updated in Maverick. Please update via www.ubuntu.com repost a detailed error report, and update the bug status. Thanks!

Changed in debconf (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for debconf (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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