Launchpad itself

One of packages names lacks

Bug #3957 reported by Jib
2
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Medium
Unassigned

Bug Description

When a reporter don't know about which package the problem is, the "unknown" package name should be available.

Perhaps, the possibility to write "unknown the_theme_of_the_bug" would suit better. So the available package name would be "unknown *"

Tags: lp-bugs
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Jib, this bug report is rather hard to understand. Is this bug the same as bug 794? If not, please give the URL of the page you are talking about that should have an "unknown" option. Thanks.

Revision history for this message
Jib (moramarth-deactivatedaccount) wrote :

Yes it the same bug. I apologize. I don't understand why my researchs were useless...

Reject my report and thanks to pay attention to me.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Actually, this bug can't be the same as bug 794, because that one was fixed before you reported this one. So I guess the problem is that it's not *obvious* enough that you can't leave the package field blank, right? (Bug 4470 may be complaining about the same thing.)

Revision history for this message
Jib (moramarth-deactivatedaccount) wrote : What a cautious guy !

You're right.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.