[Notes] NotesScreenlet.py crashed with NameExistsException in __new__()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Individual Screenlets |
Invalid
|
Undecided
|
Unassigned | ||
screenlets (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: screenlets
1. Hardy Beta
2. Screenlets .12
3. Screenlets functioning properly
4. Frequent crashing
Is there a global way to manage/control all screenlets? Or, does each screenlets have to be setup individually (i.e. start at login, on top/bottom, etc.)?
ProblemType: Crash
Architecture: amd64
Date: Fri Mar 21 21:06:30 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.5
Package: screenlets 0.0.12-0ubuntu1
PackageArchitec
ProcCmdline: python /usr/share/
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: screenlets
Title: NotesScreenlet.py crashed with NameExistsException in __new__()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
Changed in screenlets: | |
importance: | Undecided → Medium |
status: | New → Triaged |
affects: | screenlets → indiv-screenlets |
summary: |
- NotesScreenlet.py crashed with NameExistsException in __new__() + [Notes] NotesScreenlet.py crashed with NameExistsException in __new__() |
Changed in indiv-screenlets: | |
status: | New → Invalid |
I haven't experienced any crashes after upgrading to version 0.0.14 from www.getdeb.net.