Without an apt cache, packages are not considered "genuine Ubuntu packages"

[bhood]

When trying to report an unrelated bug in alacarte, Apport repeatedly failed with the error message: "This bug cannot be reported: This is not a genuine Ubuntu package." I have attached a screenshot of this occurring on a fresh install of Lucid alpha 1 (x86 version).

Just to ensure that this was not a random fluke, I also ran "ubuntu-bug apport" from the command-line and received the same error. Indeed, apport appears to regard every program as not a "genuine Ubuntu program."

I would also include the contents of /var/log/apport.log, but no such file exists on my system. The directory /var/crash is empty. The output of uname -a is "Linux [HOSTNAME] 2.6.32-7-generic #10-Ubuntu SMP Sun Dec 6 13:43:20 UTC 2009 i686 GNU/Linux".

[Martin Pitt (pitti)]

Was this a very fresh installation? In this case I suspect that the daily "apt-get update" cron job did not run yet. Does this vm guest have network access?

It should work after "sudo apt-get update", can you confirm?

[bhood (byron-phareware)]

Yes, this was a very fresh install. I suspect that this was failing as my VM did not yet have proper Internet access. It works now (at least running `ubuntu-bug apport` in the terminal did not pop up any errors.

Is there any way to "pre-load" the appropriate data from the Ubuntu servers so that networkless installations don't run into problems with apport? I understand that reporting bugs without a network connection is somewhat difficult regardless, but in the case that an Ubuntu program *does* crash, it might be better for the user to ask about filing a bug, rather than apport failing as well.

[Martin Pitt (pitti)]

> Is there any way to "pre-load" the appropriate data from the Ubuntu servers

The apt cache from the live system could be copied to the installed system in ubiquity.

Alternatively we could add this as a special case to the apt frontend, to consider packages "native distro" if there are no apt lists at all.

[dino99 (9d9)]

few minutes ago i've tried to report against gnome-panel (which is a genuine package, not from ppa or else: lucid package), and apport complaint about a non genuine: what is the mechanism based on ? packages database not updated ?

[dino99 (9d9)]

hi Martin,

please change the "importance" of this bug: actualy it is difficult to report, as :

- ubuntu-bug ALWAYS complaint that "genuine packages" are not genuine.
- apport-collect refuse to report if we are not the owner of that number's bug.
- there is a lot "silent problem" not detected by apport.

So it is neither "Low" or "whishlist" but "severe show stopper"

All these comments are about Lucid A3 updated and are regression (A2 was working without these problems)

[dino99 (9d9)]

the latest Lucid's updates have resolved this problem. Now working fine.

[svaens (svaens)]

I noticed a plymouth crash, and as I went to report it (via the gui) It came back at me with the message "the problem cannot be reported: This is not a genuine Ubuntu package". Not nice.

[John Vivirito (gnomefreak)]

I guess this bug is strictly an official package being reported an not genuine, or is it about being able to report a bug on PPA package

[Scott Moser (smoser)]

The bug is about the official package being reported as "not genuine". If a user has installed off of official media, removed the cache files (or changed their mirror) they are then told that the bug they found is in a package that is "not a genuine Ubuntu package". Its at very least confusing, worse, it could be scary as the un-knowledgeable user may believe something is wrong with their system.

[Scott Moser (smoser)]

The explicit point of the message is tell the user that PPA packages or other 3rd party software packages cannot be reported by apport. I do not think that that is a bug at all, but only in identifying something that *is* a genuine package as *not* a genuine package.

[Jānis Kangarooo (kangarooo)]

Instead after changing sources there should be made that ubuntu-bug still works.. otherwise after changing sources why something is lost so ubuntu-bug doenst think package isnt genuine?
look my Bug #610458:
"used ubuntu-bug packagename (to be exact apt and apt-utils) and got messege This package isnt original ubuntu package.
after apt-get update ubuntu-bug again worked."
and is there reason for such behaviour?

[Greg A (etulfetulf)]

This bug is quite troublesome. I am looking to report a bug on a new Maverick installation where the wireless internet connection is not working. I can't do so because of this bug!

[Martin Pitt (pitti)]

Closing upstream task, this is a distro-level bug, and we already have a distro task.

[Jānis Kangarooo (kangarooo)]

THis exist in 10.04 UNR latest updates
cant bug about packages witch installed from ubuntu souces
Gimp
Meld
VLC

BTW i found i have some strange packages see picture
How i was able to obtain them?
Dropbox link i understand came with installation of dropbox
Firefox link i added maybe couse wanted latest FF
but what is lucid bleed and why would i need it?

in lucid bleed i found thouse what i cant report are in its list.

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[Launchpad Janitor (janitor)]

[Expired for apport (Ubuntu) because there has been no activity for 60 days.]