[02:53] <michel> hi all. uh, if my Ubuntu Discourse account somehow got unlinked from my Ubuntu One SSO, who can I ask for help?
[03:02] <tomreyn> michel: i'd say if you can still write on it, use https://discourse.ubuntu.com/c/site-feedback/3
[03:05] <michel> tomreyn: I can't unfortunately, if I try to log in it prompts me to create a new account :(
[03:10] <tomreyn> michel: hopefully then going through SSO support can help https://help.ubuntu.com/community/SSO/FAQs
[03:29] <michel> tomreyn: thank you!
[03:39] <michel> I emailed them
[14:06] <lotuspsychje> tomreyn: wanna take a look at that apport bug i filed, bug #2018128
[14:06] -ubottu:#ubuntu-discuss- Bug 2018128 in apport (Ubuntu) "Apport does not collect all logs when the package is HWE kernel" [Medium, Triaged] https://launchpad.net/bugs/2018128
[14:06] <lotuspsychje> not sure if that new comment is for me? and why is it being triaged?
[14:10] <tomreyn> lotuspsychje: it's in "triaged" status for the "apport" package". which is probably actually unaffected, since, as brian murray said, apport hooks ("what files do we want included in reports?") are handled by the very packages bugs are to be reported against (so the hew kernel ones).
[14:11] <tomreyn> brian murray retargeted this bug as (also) affecting the linux package, and pointed out the kernel maintainers (#ubuntu-kernel) actually need to provide the apport hooks with their packages.
[14:12] <tomreyn> then, however, bdrung said that there's an exception to this rule (packages provide their own apport hooks and thus define what files to include in apport reports) for linux packages. their hooks are actually directly in the apport package.
[14:13] <lotuspsychje> so nothing is wanted from my (user) side here?
[14:13] <tomreyn> I guess bdrung did not really think about whom he's asking the question - it is clearly geared towards the kernel package maintainers.
[14:14] <lotuspsychje> allrighty tnx for the elaborate tomreyn 
[14:16] <tomreyn> so effectively this is now waiting for  input from the kernel team (which i assume juergh represents here) on which files / symlinks should be added to the apport team (which I assume bdrung would manage)
[14:16] <tomreyn> err, the apport *package*
[14:17] <lotuspsychje> lets hope they find the culprit
[14:17] <tomreyn> lotuspsychje: what you could answer is thbdrung's first question, this might actually let him continue already.
[14:17] <tomreyn> *bdrung's
[14:17] <tomreyn> How is the HWE kernel package named?
[14:18] <lotuspsychje> tomreyn: the case is in my description, linux-signed-hwe-5.19
[14:18] <tomreyn> oh, and he may actually be asking you, i am still waking up and may not have understood that part
[14:18] <lotuspsychje> but i filed against 'linux' like we usualy do
[14:19] <tomreyn> linux-signed-hwe-5.19 is the source package name, right
[14:20] <tomreyn> is there anything like linux-signed-hwe* in /usr/share/apport/package-hooks/ ?
[14:20] <tomreyn> is there anything like source_linux_signed*hwe* in /usr/share/apport/package-hooks/ ?
[14:20] <tomreyn> this rather
[14:21] <tomreyn> is there anything like source_linux-signed-hwe* in /usr/share/apport/package-hooks/ ?
[14:21] <tomreyn> actually this :)
[14:21] <tomreyn> lotuspsychje: ^
[14:22] <lotuspsychje> i got a source linux and a linux-meta
[14:22] <lotuspsychje> but i dont see HWE variant there
[14:23] <tomreyn> so, after reading this again i think that bdrung is actually asking *you* to see if you can add such a symlink in this directory and see how apport behaves then when you try to file a bug against the signed hwe kernel
[14:24] <tomreyn> sudo ln -s source_linux.py /usr/share/apport/package-hooks/source_linux-signed-hwe.py
[14:25] <lotuspsychje> no output tomreyn 
[14:25] <lotuspsychje> source_linux and a source_linux-meta
[14:26] <tomreyn> okay, but this command adds a symlink, after running it      ls -l /usr/share/apport/package-hooks/source_linux*      should additionally say      /usr/share/apport/package-hooks/source_linux-signed-hwe.py -> source.linux.py
[14:26] <lotuspsychje> tomreyn: https://imgur.com/a/4aALd9b
[14:27] <tomreyn> 2nd row, 4th icon, it's there
[14:27] <lotuspsychje> https://dpaste.org/sPHmF
[14:27] <lotuspsychje> ah
[14:28] <tomreyn> now try if you can run the original apport command again and whether it would now gather the right logs.
[14:29] <tomreyn> if needed to test this, create a fully bug report, we can set it to "invalid" later
[14:30] <tomreyn> *full
[14:32] <lotuspsychje> lets c
[14:33] <lotuspsychje> tomreyn: it files to linux image generic 5.19
[14:34] <tomreyn> but    cat /proc/version     says you're on the hwe currently?
[14:35] <lotuspsychje> yeah im on jammy HWE thus 5.19
[14:35] <lotuspsychje> should i file the bug to see if it imports info?
[14:35] <tomreyn> okay, and the report you're filing now, does it include all the files that should be included?
[14:35] <tomreyn> yes please
[14:37] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020268
[14:37] -ubottu:#ubuntu-discuss- Launchpad bug 2020268 in linux-signed-hwe-5.19 (Ubuntu) "test bug against HWE" [Undecided, New]
[14:37] <lotuspsychje> same thing tomreyn 
[14:39] <tomreyn> okay, thanks for trying. i suggest you report back that you ran    sudo ln -s source_linux.py /usr/share/apport/package-hooks/source_linux-signed-hwe.py     and this created the symlink     /usr/share/apport/package-hooks/source_linux-signed-hwe.py -> source_linux.py    and that you then used apport command ... again but the resulting bug report was again missing the expected files (add a link to that bug report).
[14:39] <lotuspsychje> allrighty tnx tomreyn 
[14:40] <tomreyn> lotuspsychje: ^   if you would like to undo the symlink, run    sudo rm /usr/share/apport/package-hooks/source_linux-signed-hwe.py
[14:40] <lotuspsychje> ok done
[14:41] <lotuspsychje> ill add a new comment in a bit
[14:41] <tomreyn> great! :)
[14:55] <lotuspsychje> updated bug #2018128 tomreyn 
[14:55] -ubottu:#ubuntu-discuss- Bug 2018128 in apport (Ubuntu) "Apport does not collect all logs when the package is HWE kernel" [Medium, Triaged] https://launchpad.net/bugs/2018128
[15:06] <tomreyn> 👍️
=== deepSleep is now known as Guest9998