oneconf-service crashed with IOError in update(): [Errno 2] No such file or directory: u'/home/pimpom/.cache/oneconf/6e3a694924188906d4093c6702696be1/package_list_6e3a694924188906d4093c6702696be1'

[jan noth]

oneconf-service crashed with IOError in update(): [Errno 2] No such file or directory: u'/home/pimpom/.cache/oneconf/6e3a694924188906d4093c6702696be1/package_list_6e3a694924188906d4093c6702696be1'

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: oneconf 0.2.6.7
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Sep 30 08:28:47 2011
ExecutablePath: /usr/share/oneconf/oneconf-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/oneconf/oneconf-service
PythonArgs: ['/usr/share/oneconf/oneconf-service']
SourcePackage: oneconf
Title: oneconf-service crashed with IOError in update(): [Errno 2] No such file or directory: u'/home/pimpom/.cache/oneconf/6e3a694924188906d4093c6702696be1/package_list_6e3a694924188906d4093c6702696be1'
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/oneconf/packagesethandler.py", line 61, in update
     with open(os.path.join(self.hosts.get_currenthost_dir(), '%s_%s' % (PACKAGE_LIST_PREFIX, hostid)), 'w') as f:
 IOError: [Errno 2] No such file or directory: u'/home/User Name/.cache/oneconf/6e3a694924188906d4093c6702696be1/package_list_6e3a694924188906d4093c6702696be1'
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #842198, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.