dpkg crashed with SIGABRT in __assert_fail_base()

Bug #953595 reported by timesarehard4dreamers
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Tried to report a bug in ManDB and dpkg crashed while it was reporting

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: dpkg 1.16.1.2ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sat Mar 10 04:18:19 2012
ExecutablePath: /usr/bin/dpkg
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/dpkg --status-fd 77 --unpack --auto-deconfigure /var/cache/apt/archives/apparmor_2.7.100-0ubuntu1_amd64.deb /var/cache/apt/archives/libcurl3-gnutls_7.22.0-3ubuntu3_amd64.deb /var/cache/apt/archives/pciutils_1%3a3.1.8-2ubuntu5_amd64.deb /var/cache/apt/archives/libpci3_1%3a3.1.8-2ubuntu5_amd64.deb /var/cache/apt/archives/chromium-browser-l10n_17.0.963.78~r125577-0ubuntu1_all.deb /var/cache/apt/archives/gconf-defaults-service_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/libgconf2-dev_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/gconf2_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/gconf-service_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/libgconf2-4_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/libgconf-2-4_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/gconf2-common_3.2.4-0ubuntu2_all.deb /var/cache/apt/archives/gir1.2-gconf-2.0_3.2.4-0ubuntu2_amd64.deb /var/cache/apt/archives/chromium-codecs-ffmpeg_17.0.963.78~r125577-0ubuntu1_amd64.deb /var/cache/apt/archives/chromium-browser_17.0.963.78~r125577-0ubuntu1_amd64.deb /var/cache/apt/archives/language-pack-en_1%3a12.04+20120308_all.deb /var/cache/apt/archives/language-pack-gnome-en_1%3a12.04+20120308_all.deb /var/cache/apt/archives/libcurl3_7.22.0-3ubuntu3_i386.deb /var/cache/apt/archives/libcurl3_7.22.0-3ubuntu3_amd64.deb
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 SHELL=/bin/bash
Signal: 6
SourcePackage: dpkg
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: dpkg crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-03 (9 days ago)
UserGroups:

Revision history for this message
timesarehard4dreamers (timesarehard4dreamers) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x42a013 "(*pointerp)->name[0] == '/'", file=0x429fff "../../src/filesdb.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=0x42a013 "(*pointerp)->name[0] == '/'", file=0x429fff "../../src/filesdb.c", line=683, function=0x42a3bc "findnamenode") at assert.c:103
 findnamenode (name=0x320c469 "usr/src/linux-headers-3.2.0-17/include/linux/sunrpc/svc.h", flags=fnn_nocopy) at ../../src/filesdb.c:683
 pkg_files_add_file (file_tail=0x346eee0, filename=0x320c468 "/usr/src/linux-headers-3.2.0-17/include/linux/sunrpc/svc.h", pkg=0x902b40, flags=<optimized out>) at ../../src/filesdb.c:250
 ensure_packagefiles_available (pkg=0x902b40) at ../../src/filesdb.c:369

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in dpkg (Ubuntu):
importance: Undecided → Medium
summary: - dpkg crashed with SIGABRT in raise()
+ dpkg crashed with SIGABRT in __assert_fail_base()
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dpkg (Ubuntu):
status: New → Confirmed
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.