apport --save option does not recognise ~ as home folder

[Jack Leigh]

Binary package hint: apport

If I attempt to use --save=~/filename I get an error
[Errno 2] No such file or directory: '~/filename'
a) what is the Errno 2?
b) ~ should be recognised as the home folder

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: apport 1.13.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
Architecture: i386
Date: Fri Oct 8 15:21:16 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: apport

[Vish (vish)]

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

 - Bug reporting is not an end-user task. Ideally, we should not need apport ;-) . Not a papercut.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.
Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

[Philip Muškovac (yofel)]

Python doesn't replace '~' with the home folder by default bug has to be told to do so.

[Martin Pitt (pitti)]

This works fine for me; usually the shell already expands ~, ~USERNAME, and similar. How did you call this?

[Philip Muškovac (yofel)]

This works fine as long as you call it with
--save ~/...
if you use
--save=~/...
then bash sees that as one expression and doesn't expand the ~

[Martin Pitt (pitti)]

Merged into trunk, thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package apport - 1.15-0ubuntu1

---------------
apport (1.15-0ubuntu1) natty; urgency=low

  [ Martin Pitt ]
  * New upstream release. Changes since to our previous trunk snapshot:
    - Order symptom descriptions alphabetically. Thanks to Javier Collado.
    - Check $APPORT_SYMPTOMS_DIR environment variable for overriding the
      system default path. Thanks to Javier Collado.
    - testsuite: Check that crashdb.conf can have dynamic code to determine DB
      names and options.
    - ui.py test suite: Rewrite _gen_test_crash() to have the test process
      core dump itself, instead of using gdb to do it. The latter fails in
      ptrace restricted environments, such as Ubuntu 10.10.
    - launchpad.py: Use launchpadlib to file a bug instead of screen scraping.
      The latter was completely broken with current Launchpad, so this makes
      the test suite actually work again. Thanks to Diogo Matsubara!
    - launchpad.py: Change $APPORT_STAGING to $APPORT_LAUNCHPAD_INSTANCE, so
      that you can now specify "staging", "edge", or "dev" (for a local
      http://launchpad.dev installation). Thanks to Diogo Matsubara!
    - backends/packaging-apt-dpkg.py: Fix crash on empty lines in ProcMaps
      attachment.
    - doc/symptoms.txt: Fix typo, thanks Philip Muskovac. (LP: #590521)
    - apport/hookutils.py: rename ProcCmdLine to ProcKernelCmdLine to not wipe
      wipe out /proc/$pid/cmdline information. (LP: #657091)
    - apport/hookutils.py: attach_file() will not overwrite existing report
      keys, instead appending "_" until the key is unique.
    - Fix --save option to recognise ~, thanks Philip Muškovac. (LP: #657278)
    - Remove escalation_subscription from Ubuntu bug DB definition, turned out
      to not be useful; thanks Brian Murray.
    - launchpad.py: Fix APPORT_LAUNCHPAD_INSTANCE values with a https://
      prefix.
    - apt backend: Opportunistically try to install a -dbg package in addition
      to -dbgsym, to increase the chance that at least one of it exists.
      Thanks Daniel J Blueman!
  * debian/control: Switch Vcs-Bzr: to natty branch.

  [ Brian Murray ]
  * data/package-hooks/source_linux.py: Drop regression-potential tag. We are
    moving away from using regression-potential as a tag in the management of
    regression bug reports. Instead we will tag bugs regression-release and
    then create series, release, tasks for the release affected if the bug is
    in fact a regression.
 -- Martin Pitt <email address hidden> Fri, 12 Nov 2010 14:59:01 +0100