apport no longer attaches dmesg, as dmesg is restricted in groovy

Bug #1896095 reported by Julian Andres Klode
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
High
Brian Murray

Bug Description

I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy.

This means you can't report complete kernel bugs, and the instructions provided by the kernel bot are wrong.

Not sure what the solution is - read journalctl, do it as root, idk?

description: updated
tags: added: rls-gg-incoming
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

It's just a matter of switching from command_output to root_command_output.

Changed in apport (Ubuntu):
assignee: nobody → Brian Murray (brian-murray)
importance: Undecided → High
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 2.20.11-0ubuntu47

---------------
apport (2.20.11-0ubuntu47) groovy; urgency=medium

  [ Tiago Stürmer Daitx ]
  * apport/ui.py: improve message when origin check fails as it can be
    caused by empty apt list - candidate is limited to dpkg and we can't
    tell where it came from. (LP: #1775219)

 -- Brian Murray <email address hidden> Mon, 21 Sep 2020 15:02:17 -0700

Changed in apport (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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