The crash happens after boot. I have hplip systray enabled at startup. This also crashes whenever I try to print. I wonder why ugrade.py should run at all.
I can provide more info if needed...
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: hplip-data 3.12.11-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_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: Sat Feb 2 19:38:20 2013
ExecutablePath: /usr/share/hplip/upgrade.py
InstallationDate: Installed on 2013-01-31 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130130)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Deskjet-F4200-series: hp:/usb/Deskjet_F4200_series?serial=CN95E5912M05BR
MarkForUpload: True
PackageArchitecture: all
Papersize: a4
PpdFiles: Deskjet-F4200-series: HP Deskjet f4200 Series, hpcups 3.12.11
ProcCmdline: /usr/bin/python /usr/bin/hp-upgrade --check
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic root=UUID=adbd6972-e0ac-4725-9572-8d2a04dc199b ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/hp-upgrade', '--check']
SourcePackage: hplip
Title: upgrade.py crashed with '<html>\r\n' in _read()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lp sudo
dmi.bios.date: 02/25/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: IDG4510H.86A.0135.2011.0225.1100
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG45ID
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27729-308
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrIDG4510H.86A.0135.2011.0225.1100:bd02/25/2011:svn:pn:pvr:rvnIntelCorporation:rnDG45ID:rvrAAE27729-308:cvn:ct3:cvr:
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.