Bug 1906546

Asked by corrado venturini

At each boot I see a crash in packagekit: ExecutablePath: /usr/libexec/packagekitd.
A message says the bug is already known and displayed on browser and it opens a page about Bug 1906546 saying i'm not authorized to see it.
I imagine the reason is the bug is flagged private so I can't confirm it.
should I open a new bug? or I have some way to confirm the bug? or just wait for fix?

ProblemType: Crash
Architecture: amd64
Date: Thu Dec 24 21:41:49 2020
DistroRelease: Ubuntu 21.04
ExecutablePath: /usr/libexec/packagekitd
ExecutableTimestamp: 1604917578
ProcCmdline: /usr/libexec/packagekitd
Title: packagekitd crashed with SIGSEGV in pk_dbus_get_uid()

Question information

English Edit question
Ubuntu packagekit Edit question
No assignee Edit question
Solved by:
Daniel Letzeisen
Last query:
Last reply:
Revision history for this message
Best Daniel Letzeisen (dtl131) said :

Often, crash/segafault bugs are automatically marked as private when first filed because the backtrace and other logs could contain sensitive information. Then they are set to public after a triager makes sure no such information is present.
So I would personally wait a few days (maybe longer since it's the holidays) to see if that bug report goes public.
If you do file a bug, note that it's probably a duplicate of 1906546. I think you can even make your bug report public (skim logs to make sure there's nothing identifiable in there) and mark 1906546 a duplicate of your bug.

Revision history for this message
corrado venturini (corradoventu) said :

Thanks Daniel Letzeisen, that solved my question.