simple-scan doesn't start; starts only as guest user
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
none
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: simple-scan 3.12.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-53-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
CurrentDesktop: Unity
Date: Sat May 23 15:58:21 2015
DriverPackageVe
libsane 1.0.23-3ubuntu3.1
libsane-extras N/A
hplip 3.14.3-0ubuntu3.2
hpoj N/A
InstallationDate: Installed on 2012-05-31 (1086 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Latitude E5500
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=
SimpleScanLog:
SourcePackage: simple-scan
UpgradeStatus: Upgraded to trusty on 2014-08-17 (279 days ago)
dmi.bios.date: 07/30/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0DW634
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E5500
dmi.sys.vendor: Dell Inc.
Arnold van der Heijden, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing.
Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with: _my_crash_ report. crash
sudo ubuntu-bug /var/crash/
where _my_crash_ report. crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https:/ /wiki.ubuntu. com/ErrorTracke r .
However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal: crashdb. conf
sudo nano /etc/apport/
and comment out the line:
'problem_types': ['Bug', 'Package'],
by changing it to:
# 'problem_types': ['Bug', 'Package'],
Save, close, and file the crash report via: FILENAME. crash
sudo ubuntu-bug /var/crash/
Where FILENAME is the actual name of the file found in the folder.
However, this report is being closed since the process outlined above will deal with this issue more efficiently.
Also, please do not attach your crash report manually to this report and reopen it.
Thank you for your help.
Helpful bug reporting tips: /wiki.ubuntu. com/ReportingBu gs
https:/