cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups-filters (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
apport reported that this crashed on startup. This has happened since re-installation of 15.04 with systemd.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: cups-browsed 1.0.67-0ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
CupsErrorLog:
Date: Tue Mar 17 21:55:57 2015
ExecutablePath: /usr/sbin/
InstallationDate: Installed on 2015-03-15 (4 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150314)
Lpstat: device for PDF: cups-pdf:/
MachineType: TOSHIBA Satellite C55D-A
Papersize: letter
PpdFiles: PDF: Generic CUPS-PDF Printer
ProcAttrCurrent: /usr/sbin/
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f6b69f6b15a: movl $0x1,0xa8(%rax)
PC (0x7f6b69f6b15a) 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_
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/27/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: Satellite C55D-A
dmi.product.
dmi.sys.vendor: TOSHIBA
Related branches
Changed in cups-filters (Ubuntu): | |
importance: | Undecided → High |
Status changed to 'Confirmed' because the bug affects multiple users.