fixdep crashed with signal 7 in parse_dep_file()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
On update
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: linux-headers-
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Mon Mar 23 17:34:33 2015
ExecutablePath: /usr/src/
HibernationDevice: RESUME=
InstallationDate: Installed on 2015-02-25 (25 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150225)
MachineType: Dell Inc. Dell System XPS L702X
ProcEnviron:
TERM=linux
LC_COLLATE=C
PATH=(custom, no user)
LANG=en_US.UTF-8
LC_NUMERIC=C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.143
Signal: 7
SourcePackage: linux
Stacktrace:
#0 0x00000000004010f5 in parse_dep_file ()
No symbol table info available.
#1 0x0000000000400bdf in main ()
No symbol table info available.
StacktraceTop:
parse_dep_file ()
main ()
Title: fixdep crashed with signal 7 in parse_dep_file()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.
dmi.board.name: 0XN71K
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell System XPS L702X
dmi.sys.vendor: Dell Inc.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1436482, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.