touch-packages team mailing list archive

[LukeKendall <luke@xxxxxxxxxxx>]

This one, the bug 'ubuntu-bug can't always report bugs against "no
particular package"',
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/902714.
Unfortunately, no mention of an ID for the above transferred apparently
to apport appears in the above note by micahg in 2011, so I can't follow
up to see what actions occurred in the intervening years.

Since the same problem happened to me yesterday with Ubuntu 14.04, I saw
that the error in the documentation remains or else in ubuntu-bug, as
once again I tried to follow the instructions at
https://help.ubuntu.com/community/ReportingBugs:

"Filing a general bug against no particular package

If you’re not sure which package is affected by the bug, type ubuntu-bug
in the “Run Command” screen and press Enter. This will guide you through
a series of questions to gather more information about the bug and help
you assign it to the appropriate package. "

However, if you do try this, and then select the category Other in the
first panel, ubuntu-bug just pops up a warning that you must specify a
particular package, and exits.  This contradicts the topic itself:
"Filing a general bug against no particular package".

In my case I was trying to report a problem in the printing area when I
discovered this problem of reporting bugs of uncertain origin was
unchanged.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/902714

Title:
  ubuntu-bug can't always report bugs against "no particular package"

Status in “apport” package in Ubuntu:
  New

Bug description:
  If you choose the option in ubuntu-bug to report a bug against "no particular package", if you follow the instructions at https://help.ubuntu.com/community/ReportingBugs you will fail if the bug is not within a currently-running process.
  In my case, I wanted to report a bug in whatever it is that handles an Ubuntu upgrade.
  When started as recommended on the above web page, ubuntu-bug demands a PID, and without one, it won't work.

  I suggest adding some text to the ReportingBugs page to explain that if you can't provide a process ID, you can provide a package name.  And that if you don't know the package name (e.g. if you were trying to report a bug against ubuntu-bug itself), you can do a search to find what package the command comes from, like so:
  apt-cache search ubuntu-bug (which tells you that ubuntu-bug is in the reportbug package, therefore you would have to run ubuntu-bug reportbug).

  lsb_release -rd:
  Description:	Ubuntu 10.04.3 LTS
  Release:	10.04

  apt-cache policy reportbug
  reportbug:
    Installed: 4.10.2ubuntu1
    Candidate: 4.10.2ubuntu1
    Version table:
   *** 4.10.2ubuntu1 0
          500 http://archive.ubuntu.com/ubuntu/ lucid/universe Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: reportbug 4.10.2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-36.79-generic-pae 2.6.32.46+drm33.20
  Uname: Linux 2.6.32-36-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sun Dec 11 17:18:22 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   LC_COLLATE=C
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: reportbug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/902714/+subscriptions