system-config-printer.py crashed with SIGSEGV in g_object_freeze_notify()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I tried to rename an existing network IPP printer, and the printer configurator crashes.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: system-
ProcVersionSign
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
Date: Thu Sep 26 09:34:48 2013
ExecutablePath: /usr/share/
InstallationDate: Installed on 2013-09-10 (15 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha amd64 (20130909)
InterpreterPath: /usr/bin/python2.7
Lpstat:
device for laserjet4250: http://
device for laserjet4250@
device for Samsung_
MachineType: Dell Inc. OptiPlex 755
MarkForUpload: True
PackageArchitec
Papersize: letter
PpdFiles: laserjet4250: HP LaserJet 4250 - CUPS+Gutenprint v5.2.9
ProcCmdline: /usr/bin/python /usr/share/
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f07e16cac81 <g_object_
PC (0x7f07e16cac81) ok
source "$0x50" ok
destination "(%rax)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: system-
StacktraceTop:
g_object_
?? () from /usr/lib/
g_hash_
?? () from /usr/lib/
?? () from /usr/lib/
Title: system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo
dmi.bios.date: 08/04/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0GM819
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: OptiPlex 755
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 #1229337, 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.