| 19 Jul 2024 |
 Ravi Jain | Yeah | 09:16:12 |
| Ravi Jain | A fixed period would make a lot of sense (ie 1 week or whatever) and then this gives people a clear benefit of sponsorship. One week "early access" to Iso's for their ongoing contribution | 09:17:11 |
 Reilly Brogan | Can I get a review of my eopkg PRs? | 17:46:30 |
| Reilly Brogan | Namely the ones fixing eopkg check? | 17:46:37 |
| Reilly Brogan | I'd like to get them into the sync | 17:46:47 |
| Reilly Brogan | Alright I'm just going to merge it I guess | 20:57:52 |
| Reilly Brogan | ¯\_(ツ)_/¯ | 20:58:05 |
| Ravi Jain | In reply to @reillybrogan:matrix.org
Alright I'm just going to merge it I guess Carpet diem | 21:36:36 |
| Ravi Jain | * Carpe diem | 21:36:47 |
| 21 Jul 2024 |
|  @ever_reddy:matrix.org changed their display name from ever_reddy to A108384. | 14:34:52 |
 Silke | Reilly Brogan: is it normal that these files don't usr merge?
$ find /lib64/ -not -type l -not -type d
/lib64/modules/6.9.10-295.current/modules.dep.bin
/lib64/modules/6.9.10-295.current/modules.alias.bin
/lib64/modules/6.9.10-295.current/modules.alias
/lib64/modules/6.9.10-295.current/modules.dep
/lib64/modules/6.6.41-249.lts/modules.dep.bin
/lib64/modules/6.6.41-249.lts/modules.dep
| 15:02:03 |
| Reilly Brogan | Did you run the usr-merge script? | 16:30:25 |
| Reilly Brogan | Or what is the context here? | 16:30:45 |
| Silke | In reply to @reillybrogan:matrix.org
Did you run the usr-merge script? Yeah, and these files are 'orphaned' | 16:48:24 |
| Reilly Brogan | It's not a big deal so long as depmod is ran after the usr-merge script | 17:00:01 |
| Reilly Brogan | The other way to do it would be to whitelist them to override their counterparts in /usr | 17:00:19 |
| Silke | Well, you do end up with orphaned files. Maybe special case them so they get removed? | 19:08:03 |
| Reilly Brogan | That would be problematic for anyone with add on kernel modules | 19:20:38 |
| Reilly Brogan | Who wouldn't be able to load any such modules until depmod was ran | 19:20:50 |
| Reilly Brogan | BTW, how long did the script take to run for you? Roughly? | 19:21:03 |
| Reilly Brogan | The simplest thing to do would probably be to add a global flag to the script and set to true if any usr-merge symlinks actually happen. Then at the end of the script run usysconf if true | 19:40:02 |
| 22 Jul 2024 |
| @ever_reddy:matrix.org left the room. | 00:03:18 |
| 23 Jul 2024 |
 TraceyC | Shenanigans in Packaging so I'm putting this here. When bringing up a terminal using the nVidia driver I see output after zsh initialization I didn't before.
-- console output produced during zsh initialization follows --
No backend specified, automatically choosing X11 because DISPLAY is set
Accepting client connections on sockets: QList("wayland-0")
kwin_wayland_x11windowed: X server supports SHM extension but not shared pixmaps
kf.globalaccel.kglobalacceld: Failed to register service org.kde.kglobalaccel
kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
kwin_xkbcommon: XKB: inet:325:58: unrecognized keysym "XF86CameraAccessEnable"
kwin_xkbcommon: XKB: inet:326:58: unrecognized keysym "XF86CameraAccessDisable"
kwin_xkbcommon: XKB: inet:327:58: unrecognized keysym "XF86CameraAccessToggle"
kwin_xkbcommon: XKB: inet:357:58: unrecognized keysym "XF86NextElement"
kwin_xkbcommon: XKB: inet:358:58: unrecognized keysym "XF86PreviousElement"
kwin_xkbcommon: XKB: inet:359:58: unrecognized keysym "XF86AutopilotEngageToggle"
kwin_xkbcommon: XKB: inet:360:58: unrecognized keysym "XF86MarkWaypoint"
kwin_xkbcommon: XKB: inet:361:58: unrecognized keysym "XF86Sos"
kwin_xkbcommon: XKB: inet:362:58: unrecognized keysym "XF86NavChart"
kwin_xkbcommon: XKB: inet:363:58: unrecognized keysym "XF86FishingChart"
kwin_xkbcommon: XKB: inet:364:58: unrecognized keysym "XF86SingleRangeRadar"
kwin_xkbcommon: XKB: inet:365:58: unrecognized keysym "XF86DualRangeRadar"
kwin_xkbcommon: XKB: inet:366:58: unrecognized keysym "XF86RadarOverlay"
kwin_xkbcommon: XKB: inet:367:58: unrecognized keysym "XF86TraditionalSonar"
kwin_xkbcommon: XKB: inet:368:58: unrecognized keysym "XF86ClearvuSonar"
kwin_xkbcommon: XKB: inet:369:58: unrecognized keysym "XF86SidevuSonar"
kwin_xkbcommon: XKB: inet:370:58: unrecognized keysym "XF86NavInfo"
kwin_core: Configured compositor not supported by Platform. Falling back to defaults
kwin_core: The used windowing system requires compositing
kwin_core: We are going to quit KWin now as it is broken
kwin_wayland_wrapper: no process found
| 15:36:00 |
| TraceyC | There are other weird problems. I had to log out so I could remove the Mudeer plugin lines from kglobalrc. Any TTY I logged into shows a black window with a mouse cursor instead of the TTY
Also, when I log into Plasma Wayland I get a window with the Wayland logo in the upper left, title "KDE Wayland Compositor WL-0 - Press right control key to grab pointer". If I close this window I am logged out of the Plasma session | 16:10:59 |
| TraceyC | Logged back into an X11 session because the mouse was laggy af on Wayland | 16:13:47 |
| TraceyC | (wayland was not laggy on the non-beta driver) | 16:14:05 |
| TraceyC | And now I'm getting notifications from Plasma Desktop Workspace "Filesystem is not reponding" for / and /home, while trying to move the Thunderbird window...wtf... it's like every step of window movement caused the system to hang for a few moments. and it looks like the windows are being redrawn every few monents. | 16:16:52 |
| TraceyC | Back on the non-beta drivers for current. journalctl showed kwin crashing over and over with the beta driver, it's OK with the non-beta driver. still have the above output spit out when I start a new terminal | 17:19:00 |
| 24 Jul 2024 |
| Silke | In reply to @reillybrogan:matrix.org
BTW, how long did the script take to run for you? Roughly? About 40 seconds with an old kernel installed, less than a second without. | 11:54:40 |
|  @scorpiontaj:matrix.org left the room. | 13:20:46 |
