apport-comment instructions when not the submitter are confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
I found an existing bug which I am also experiencing, and the submitter was asked to run apport-comment. The submitter was unable to because they no longer have the hardware that has the bug.
I attempted to run apport-comment myself, specifying the bug id, but apport-comment told me that since I was not the submitter then it would be best if I submitted a new bug and merged them.
I submitted a new bug and merged them, and then repeated apport-comment with my new bug id. Unfortunately apport-comment then repeated the same instructions, because my new bug was merged.
In my opinion apport-comment either shouldn't care that I'm not the bug submitter, or else it should make clear that I should run it BEFORE merging the new bug with the existing one.
Cheers,
Andy
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: apport 1.13.3-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelMo
ApportLog:
Architecture: i386
Date: Sun May 23 09:14:19 2010
EcryptfsInUse: Yes
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: apport
Closing that outdated report as EOL has been reached long time ago