| valorie | I updated last night, got a new kernel, which would not boot | 00:52 |
|---|---|---|
| valorie | "error: load kernel first | 00:52 |
| valorie | hit any key" | 00:52 |
| valorie | could only shut down with the power button | 00:52 |
| valorie | was able to update with zero issues with this travel laptop so I dunno if it is nvidia or what.... any other reports of this? | 00:53 |
| valorie | was unable to file a BR yet, because it's taking forever to memtest, and I wanted to go down the options that grub is offering | 00:54 |
| valorie | there appears to be a former kernel and I'm hopeful I can login with that whenever it's done memtesting | 00:55 |
| IrcsomeBot | <sgmoore> I also had boot failures, I hit this https://askubuntu.com/questions/1392141/running-scripts-init-premount-delays-ubuntu-20-04-3-boot and the fix worked. Not sure if it's related. Same laptop that hit the blackscreen bug. | 07:36 |
| RikMills | sgmoore: arraybolt3: it looks as it stands that we won't be able to land plasma6 discover or plasma-systemmonitor until KDE PIM is also KF6 based | 09:47 |
| RikMills | reason being that disover and plasma-sytemmonotor need kf6 kirigami addons and Qt5 PIM need KF5 kirigami-addons, and a dul build is not possible | 09:48 |
| RikMills | *dual build | 09:49 |
| RikMills | so I would suggest a new kf5-kirigami-addons source, and then sync the existing kirigami-addons with the KF6 one in experimental | 09:50 |
| RikMills | does that sound sensible? | 09:50 |
| sgmoore | seems reasonable | 09:50 |
| BluesKaj | Hi all | 11:35 |
| IrcsomeBot | <RikMills> So looks like all KF6 is though NEW, built for all arches, and migrated. | 13:46 |
| IrcsomeBot | <RikMills> kf6-purpose had to have its optional kaccounts build dep disabled, but that can come back when signond and kaccounts-* can be synced from experiemntal | 13:48 |
| arraybolt3 | RikMills: Are you sure KF6 is through and migrated? libkf6screen isn't there | 18:06 |
| arraybolt3 | Pretty sure it's a thing too - lxqt-config requires it (aaaand now you know my ulterior motive for asking about it) | 18:07 |
| arraybolt3 | and yeah it exists in Debian | 18:07 |
| arraybolt3 | and isn't on LP AFAICT | 18:09 |
| RikMills | arraybolt3: libkf6screen is part of plasma 6 not frameworks 6 | 18:10 |
| arraybolt3 | ah fun :( | 18:12 |
| arraybolt3 | why on earth does it start with "kf6" then XD | 18:12 |
| arraybolt3 | but yeah, I think I vaguely remember that now that you mention it. | 18:13 |
| RikMills | indicates it is a lib based on the kf6 Qt extensions | 18:13 |
| arraybolt3 | usually I see "libkf6" and parse it as "library - KDE Frameworks 6", indicating it's a kf component. | 18:14 |
| arraybolt3 | but ok, that makes sense | 18:14 |
| RikMills | most kf5 based libs follow the same convention | 18:14 |
| RikMills | e.g. libkf5screen8 | 18:15 |
| RikMills | from the KF5 release of plasma libkscreen | 18:16 |
| RikMills | arraybolt3: so really your lxqt things depend on plasma 6 landing :( | 18:19 |
| RikMills | unless you do your testing via a ppa | 18:19 |
| arraybolt3 | I'll probably go that route, yeah | 18:19 |
| arraybolt3 | but once I have some spare time, I want to try to help with plasma 6 - I tried to take a swing at it once earlier, but got too busy | 18:20 |
| RikMills | all help appreciated. 7 weeks to feature freeze! | 18:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!