screenshot crashed with IOError in ./screenshot: [Errno 32] Обрыв канала

Bug #954441 reported by Vadim Glyshkov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Epoptes
Fix Released
Low
Alkis Georgopoulos

Bug Description

bad work epoptes.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: epoptes-client 0.4.4-1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 14 03:44:22 2012
ExecutablePath: /usr/share/epoptes-client/screenshot
InstallationMedia: Edubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python ./screenshot 100 75
PythonArgs: ['./screenshot', '100', '75']
SourcePackage: epoptes
Title: screenshot crashed with IOError in ./screenshot: [Errno 32] Обрыв канала
Traceback:
 Traceback (most recent call last):
   File "./screenshot", line 53, in <module>
     stdout.write('%s\n%ix%i\n%s' %(rowst, width, height, pixels))
 IOError: [Errno 32] Обрыв канала
UpgradeStatus: Upgraded to precise on 2012-03-13 (0 days ago)
UserGroups:

Related branches

Revision history for this message
Vadim Glyshkov (vadim-nsk) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

That happens when the connection to the server is lost, but of course epoptes-client shouldn't cause an apport crash, it should just exit with an error message. It will be fixed for epoptes 0.5.0.

no longer affects: epoptes (Ubuntu)
Changed in epoptes:
status: New → Confirmed
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :
visibility: private → public
Changed in epoptes:
assignee: nobody → Alkis Georgopoulos (alkisg)
importance: Undecided → Low
status: Confirmed → Fix Committed
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Fix released in Epoptes 0.5.0.

Changed in epoptes:
status: Fix Committed → Fix Released
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.