Laney reports that this is happening on the desktop. On a desktop,
/android/cache/recovery does not exist, so the error makes sense. When
I test s-i on a desktop, I always use a custom client.ini file, since
you have to specify paths that actually exist. Of course, desktops
aren't designed to do system image updates yet.
I'm not going to close this as invalid though (yet). Laney suggests we
could try to send an error signal in this case, and that might be a
reasonable thing to do. But this is not a critical bug - it's just
using s-i in a way it's not designed to work using the default
configuration files.
If the OP is *not* on a desktop and /android/cache/recovery/ *does*
exist, please follow up.
** Changed in: ubuntu-system-image
Importance: Critical => Low
** Changed in: system-image (Ubuntu)
Importance: High => Low
** Changed in: ubuntu-system-image
Milestone: 2.2 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286461
Title:
system-image-dbus crashed with FileNotFoundError in _mkstemp_inner():
[Errno 2] No such file or directory:
'/android/cache/recovery/jk23wk02.tmp'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1286461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
