[00:00] <xnox> will check how things are, i guess toolchainy things need to be pinned from the toolchain-r repository higher than the rebuild archive, or the fallback archive.
[00:01] <xnox> however it sounds odd that it has no installation candidate
[03:54] <tjaalton> Eickmeyer: sometimes, why?
[03:55] <Eickmeyer> tjaalton: Got a kernel issue involving framebuffers that has your name written all over it. Really, the email thread. Tested a patch that works perfectly on our OEM hardware.
[04:03] <tjaalton> ehich thread?
[04:15] <Eickmeyer> tjaalton: Apparently a gitlab issue for intel: https://gitlab.freedesktop.org/drm/intel/-/issues/272
[04:15]  * Eickmeyer had to look at his ticketing system
[04:16] <Eickmeyer> tjaalton: So, basically, there's tons of screen flickering on some of our hardware that the patch in question fixes.
[04:16] <Eickmeyer> And it's only if a certain display panel is used.
[04:16] <Eickmeyer> But, we can confirm that the patch fixes the problem 100%.
[04:32] <tjaalton> oh that, it's upstream now
[04:37] <Eickmeyer> tjaalton: Weird, because we're seeing the problem in 20.04, even tested Hirsute.
[04:47] <tjaalton> i meant intel drm tree
[04:47] <tjaalton> branch
[04:57] <Eickmeyer> Oh, so it just hasn't been merged into the kernel yet?
[05:39] <tjaalton> I don't think it was sent to stable@, so no
[05:39] <tjaalton> should be in 5.13 eventually
[05:44] <tjaalton> the commit was pushed yesterday, so it's quite fresh
=== alan_g_ is now known as alan_g
[11:35] <xnox> juliank:  in base tarball of hirsute, i see gpgv output
[11:35] <xnox> is that normal?
[11:35] <xnox> https://paste.ubuntu.com/p/tDgnFcWqHD/
[11:35] <xnox> should i open a bug about it?
[11:37] <juliank> xnox: Haven't seen that before, seems like a minor bug somewhere
[11:37] <juliank> xnox: do you see it outside riscv64 too?
[11:40] <xnox> juliank:  yes, same on s390x
[11:40] <xnox> it's this test case http://iso.qa.ubuntu.com/qatracker/milestones/423/builds/229833/testcases/1318/results
[11:41] <xnox> juliank:  which should be the same on all arches. Shall I open a bug about it?
[11:41] <xnox> oh
[11:41] <xnox> oh
[11:41] <juliank> oh?
[11:41] <xnox> i think /dev/pts is not mounted?
[11:41] <juliank> oh!
[11:41] <xnox> let me mount that
[11:42] <xnox> ok /dev is not mounted
[11:42] <xnox> the test case should be updated.
[11:42] <xnox> with /dev mounted it is fine.
[11:45] <juliank> ay!
=== zyga_ is now known as zyga
=== jchittum_ is now known as jchittum
[16:28] <TomyWork> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923670 I can confirm that this issue slipped into bionic now as well, as of linux-modules-5.4.0-72-generic_5.4.0-72.80~18.04.1_amd64. I reverted and rebuilt cifs.ko locally, and I can now use DFS again.
[16:28] <ubottu> Launchpad bug 1923670 in linux-oem-5.10 (Ubuntu) "CIFS DFS entries not accessible with 5.4.0-71.74-generic" [Undecided,Confirmed]
[16:32] <TomyWork> I hope this is the right place for this, since I'm not asking for support (my issue is solved) but reporting/confirming an issue
[16:33] <TomyWork> s/an issue/a bug/
=== Laney changed the topic of #ubuntu-devel to: Archive: Closed | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Groovy | If you can't send messages here, authenticate to NickServ first | Patch Pilots:
=== popey8 is now known as popey
=== tomreyn_ is now known as tomreyn
=== Unit193 changed the topic of #ubuntu-devel to: Archive: Closed | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Hirsute | If you can't send messages here, authenticate to NickServ first | Patch Pilots: