I cannot raise a defect if I do not know the package name explicitly.

Bug #885661 reported by Bracken on 2011-11-03
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Low
Unassigned

Bug Description

This documentation: https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package
Says that I can open a bug against "No particular package".

This is untrue, if you run ubuntu-big and select other it says you must specify a PID. This is blocking me from raising another defect, I have diagnosed the root cause of the other bug but I am unable to report it as I cannot work out what package it is in!! There needs to be a way to raise a defect against no particular package, preferably from a web browser, what if the defect is in grub and I'm using another machine, maybe a Windows machine?

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: reportbug (not installed)
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Thu Nov 3 13:00:36 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: reportbug
UpgradeStatus: No upgrade log present (probably fresh install)

Bracken (abdawson) wrote :
affects: reportbug (Ubuntu) → apport (Ubuntu)
Alessandro Menti (elgaton) wrote :

I was able to reproduce the bug in Ubuntu 11.10 i386, but NOT in KUbuntu 11.10 amd64. Perhaps the problem occurs only in some Ubuntu versions. I'm marking this bug report as "Confirmed" so that developers will be able to look at it and fix it.

There is a way to report bugs without using apport: go to <https://bugs.launchpad.net/ubuntu/>, log in and select "Report a bug" on the right. After you have completed filing the bug, if a triager finds the correct package and asks you to provide further information, you can run the command "apport-bug number" (where "number" is the bug number) to collect and send it.

Sorry for the inconvenient this problem has caused to you.

Changed in apport (Ubuntu):
status: New → Confirmed
summary: - I cannot raise a defect if I do not know the packae name explicityly.
+ I cannot raise a defect if I do not know the package name explicitly.
Dave Gilbert (ubuntu-treblig) wrote :

Medium suggested by Elgaton ; moderate impact on core app.
(Although it's an interesting question if this is the intended behaviour and the docs are wrong, but sometimes it is difficult to work out the package of a bug)

Changed in apport (Ubuntu):
importance: Undecided → Medium
Bracken (abdawson) wrote :

Sorry about the summary, I'd have corrected the typos myself if I knew I could.

I think it only goes to show how hard it is to get the right package by my failure to get the right package for this defect too, and I was quite sure about this one...

Alessandro Menti (elgaton) wrote :

Don't worry - it's difficult even for us triagers.

Changed in apport (Ubuntu):
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Bug attachments