cups-browsed crashed with SIGSEGV in g_slist_foreach()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashes on boot.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CupsErrorLog:
Date: Sat Mar 28 11:39:03 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2015-03-27 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Acer Aspire XC-603
Papersize: letter
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f0b35ef0cd0 <g_slist_
PC (0x7f0b35ef0cd0) ok
source "0x8(%rdi)" (0x00000009) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
g_slist_foreach () from /lib/x86_
g_slist_free_full () from /lib/x86_
?? () from /lib/x86_
g_main_
?? () from /lib/x86_
Title: cups-browsed crashed with SIGSEGV in g_slist_foreach()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 08/28/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11-B2
dmi.board.name: Aspire XC-603
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmerican
dmi.product.name: Aspire XC-603
dmi.sys.vendor: Acer
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 #1435287, 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.