cups-browsed crashed with SIGSEGV in timeout_free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avahi (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
cups-filters (Ubuntu) |
Fix Released
|
High
|
Till Kamppeter | ||
glib2.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
happened during update.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-8-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
CupsErrorLog:
Date: Wed Mar 11 22:46:42 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2015-03-01 (10 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
Lpstat: device for WF-2530: dnssd:/
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Papersize: a4
PpdFiles: WF-2530: Epson WF-2530 Series - epson-inkjet-
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f03e1e4815a: movl $0x1,0xa8(%rax)
PC (0x7f03e1e4815a) ok
source "$0x1" ok
destination "0xa8(%rax)" (0x000000a8) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: cups-filters
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Title: cups-browsed crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 04/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: 970DE3/U3S3
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
Related branches
tags: | added: bugpattern-needed |
information type: | Private → Public |
Changed in avahi (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in glib2.0 (Ubuntu): | |
status: | Incomplete → Invalid |
This crash has the same stack trace characteristics as bug #1427344. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.