alarm-clock crashed with IOError in PreferencesDialog()

[Miloš Mandarić]

Binary package hint: alarm-clock

Went to Preferences, checked 'start minimized', 'start automatically' and clicked on Close.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/alarm-clock
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: alarm-clock 0.9.11.2-1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/alarm-clock
ProcEnviron:
 PATH=/usr/lib/jvm/java-6-sun-1.6.0.07/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/alarm-clock']
SourcePackage: alarm-clock
Title: alarm-clock crashed with IOError in PreferencesDialog()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.5/site-packages/alarmclock/MainClass.py", line 403, in PreferencesDialog
     self.SessionFile = file(os.getenv("HOME") + '/.config/autostart/alarm-clock.desktop', 'w')
 IOError: [Errno 2] No such file or directory: '/home/username/.config/autostart/alarm-clock.desktop'
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev root video

[Miloš Mandarić (mandzo18)]

Bug shows when Close button is clicked while 'start automatically' is checked.

[Ryan Niebur (ryan52)]

these bugs have most likely been fixed with newer upstream versions in
Debian, and the new version of the package will make it's way into the
release after karmic.

--
_________________________
Ryan Niebur
<email address hidden>

[Launchpad Janitor (janitor)]

This bug was fixed in the package alarm-clock - 1.2.4-1

---------------
alarm-clock (1.2.4-1) unstable; urgency=low

  * New Upstream Version
    - only change was already fixed in package,
      uploading anyway for updated email address
  * remove fix-duplicate-id patch, fixed upstream
  * update my email address and remove DMUA field

alarm-clock (1.2.3-2) unstable; urgency=low

  * don't do 'make check', it doesn't work right with quilt patches
  * add gtk-builder-proper-error-handling patch, used to debug LP 425163
  * add fix-duplicate-id, which fixes loading on Ubuntu (LP: #425163)

alarm-clock (1.2.3-1) unstable; urgency=low

  * New Upstream Version (LP: #400605, #419167)
    - has correct homepage link (LP: #375958)
  * add README.source
  * remove libglade2-dev from build deps, no longer needed
  * Debian Policy 3.8.3
  * fix some old ubuntu bugs in older versions (not yet synced) in the
    changelog

alarm-clock (1.2.1-1) unstable; urgency=low

  * New Upstream Version
    - fixes simple counters (Closes: #537791)
  * patch to fix the autostart exec path (Closes: #537793)

alarm-clock (1.1-2) unstable; urgency=low

  * upload to unstable

alarm-clock (1.1-1) experimental; urgency=low

  * New Upstream Version
    - no longer uses glade (LP: #375952)
  * Debian Policy 3.8.2
  * remove patching
  * remove config.{log,status} in d/clean, and add lintain overrides for
    configure-generated-file-in-source

alarm-clock (1.0~beta1-1) experimental; urgency=low

  * replace using the constantly changing ip address in debian/watch
    with using a script on my VPS
  * adopt packages (Closes: #521226)
  * New upstream release
  * remove all of the python and cdbs
    - this version is no longer in python
      (LP: #321795, #365079, #271489, #274121, #275090)
  * convert to dh7
  * convert to arch:any
  * add build deps and shlibs:depends
  * add a quilt patch to fix build
  * make changes to the menu and man page for the rename from alarm-
    clock to alarmclock
  * update man page, there is no longer any options
  * add DMUA header

 -- Ubuntu Archive Auto-Sync <email address hidden> Wed, 04 Nov 2009 01:45:04 +0000