crash while using the add printer wizard
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
note : worked fine when ran it a second time.
Ubuntu oneiric (development branch) Release: 11.10
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
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: Tue Oct 4 17:41:51 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111003)
InterpreterPath: /usr/bin/python2.7
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Acer Veriton M490G
PackageArchitec
Papersize: a4
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANGUAGE=en_AU:en
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f2c7da9cbb3: mov %al,(%rdi)
PC (0x7f2c7da9cbb3) ok
source "%al" ok
destination "(%rdi)" (0x7f2c6f75b497) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: system-
StacktraceTop:
?? () from /lib/x86_
_IO_file_xsputn () from /lib/x86_
fwrite () from /lib/x86_
?? ()
?? ()
Title: system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/25/2010
dmi.bios.vendor: Acer
dmi.bios.version: P01-B0
dmi.board.
dmi.board.name: Veriton M490G
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Veriton M490G
dmi.sys.vendor: Acer
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #863123, 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.