Using Error Tracker data for SRUs

[Daniel van Vugt]

Another example is trying to figure out which version of libmutter is causing 
crashes in gnome-shell when all you can see is a table of gnome-shell binary 
versions.

My workaround is to dig into a bunch of individual incident reports and check 
the package versions of each. It's not efficient so I think library searches 
would be helpful.

- Daniel


On 1/7/22 5:03 am, Brian Murray wrote:
> I was recently looking at an SRU[1] which fixes a crash which was
> reported about gnome-remote-desktop in the Ubuntu Error Tracker but the
> crash was actually in freerdp2. Subsequently, there isn't an easy to
> confirm that there are not crashes with the new version of the package
> because the problem page[2] in the Error Tracker only shows the
> gnome-remote-desktop version of the package.
> 
> However, the information is in the Error Tracker as gnome-remote-desktop
> depends on libfreerdp2-2 and apport collects version information about a
> package's dependencies. While this information isn't yet easily
> accessible I was able to write a database query to find the versions of
> libfreerdp2-2 installed and confirm that the version of the package in
> -proposed didn't appear in any of the crashes.
> 
> I mention it as having the database queried may be useful for
> verification of other SRUs. So let me know if you could use some
> more data.
> 
> [1]
> https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970994
> [2]
> https://errors.ubuntu.com/problem/77f41623474304919ac793c6665505547b583b60
> 
> Thanks,
> --
> Brian Murray
>