cupsd crashed with SIGSEGV - apparmor?

Bug #1049418 reported by Marshall Davis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 12.10 Beta 1 x64
Cups: 1.6.1-0ubuntu5

Seems to be related to apparmor
Apparmor: 2.8.0-0ubuntu2

 Sep 11 08:03:26 ubuwks kernel: [215872.551432] type=1400 audit(1347365006.793:6
0): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=117
17 comm="apparmor_parser"

May be related to Bug 160092?

In my case, printing is shared to my wife's and son's laptops (Ubuntu 12.04 x64, and LinuxMint 12 x86, resp). I have had no issues with printing, just an occasional system crash message. Can provide any additional info requested.

Files manually modified from defaults:
cupsd.conf - added remote web access, and:
PreserveJobHistory On
PreserveJobFiles On
MaxJobs 500

I don't know enough about apparmor to muck with it's settings, so they are at default.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: cups 1.6.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
CupsErrorLog:
 W [11/Sep/2012:08:03:26 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-LaserJet-1022-Gray..' already exists
 W [11/Sep/2012:08:03:26 -0400] CreateDevice failed: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-HP-LaserJet-1022' already exists
 W [11/Sep/2012:08:03:26 -0400] AddProfile failed: org.freedesktop.DBus.Error.UnknownMethod:No such interface `org.freedesktop.ColorManager' on object at path /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1022
Date: Tue Sep 11 08:03:26 2012
ExecutablePath: /usr/sbin/cupsd
Lpstat: device for HP-LaserJet-1022: hp:/usb/HP_LaserJet_1022?serial=JM0W5KT
MachineType: System manufacturer System Product Name
Papersize: letter
PpdFiles: HP-LaserJet-1022: HP LaserJet 1022 Foomatic/foo2zjs-z1 (recommended)
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=903e828f-60cd-492f-8b41-e05752f2779e ro quiet splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=903e828f-60cd-492f-8b41-e05752f2779e ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fa5f4243458: movzbl (%rdi),%eax
 PC (0x7fa5f4243458) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: cupsd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/21/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.cups.cupsd.conf: 2012-09-08T22:11:21.218083

Revision history for this message
Marshall Davis (mpdavis73) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1046982, 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.

visibility: private → public
tags: removed: need-amd64-retrace
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.