!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

213 Members
57 Servers

Load older messages


SenderMessageTime
22 Nov 2024
@k900:0upti.meK900I am extremely overloaded right now07:17:25
@outfoxxed:outfoxxed.meoutfoxxedalright07:18:41
@k900:0upti.meK900Also re: Qt5, I want to at least drop Plasma and Gear07:27:04
@k900:0upti.meK900And then as much of Frameworks as is realistic07:27:18
@k900:0upti.meK900Qt5 itself can't go away yet07:28:05
@k900:0upti.meK900Sadly07:28:07
@emilazy:matrix.orgemilywhat are the main blockers for Qt 5 itself?07:35:01
@k900:0upti.meK900Lots08:23:45
@k900:0upti.meK900I don't have a list off the top of my head08:23:52
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/pull/35809108:27:14
@k900:0upti.meK900Speaking of, here's a Qt5 update08:27:18
@k900:0upti.meK900Also can we start with gkt208:33:32
@k900:0upti.meK900* Also can we start with gtk208:33:33
@k900:0upti.meK900I really, REALLY want gtk2 gone at this point08:33:45
@eliasp:kde.orgeliasp looking at the Sentry reports at https://crash-reports.kde.org/ I can't find any reports with os.name = NixOS - there should be at least some, since I had a few crashes recently and wanted to see, whether there are other reports of those as well or whether they're NixOS specific...
does anyone have some insight how kcrash handles all this, so I could dig into this and find out, why no reports are sent?
09:02:00
@eliasp:kde.orgeliasp ...and it would be also interesting to know, whether any of the kcrash tooling has a way to "simulate" crash to test all this? 09:07:49
@k900:0upti.meK900We don't have enough debug info to submit those currently09:09:29
@k900:0upti.meK900The next staging cycle should get us there09:09:37
@eliasp:kde.orgeliasp ah, because my backtraces looked quite complete, so I assumed they'd be good enough to be sent…
nonetheless, then the UI is misleading and doesn't tell me "Your crash data are bad - I'm not gonna send anything to KDE" :)
09:10:50
@eliasp:kde.orgeliaspScreenshot_20241122_101122.png
Download Screenshot_20241122_101122.png
09:12:09
@eliasp:kde.orgeliasp and I just found a few quite insightful blog posts by Harald:
  • https://planet.kde.org/harald-sitter-2024-08-20-plasma-crash-course-kcrash/
  • https://planet.kde.org/harald-sitter-2024-08-27-plasma-crash-course-coredumpd/
  • https://planet.kde.org/harald-sitter-2024-09-04-plasma-crash-course-drkonqi/
09:13:07
@numinit:matrix.orgMorgan (@numinit) joined the room.17:51:31
24 Nov 2024
@ixlun:matrix.org@ixlun:matrix.org changed their display name from Matthew Leach to Matthew L.00:43:18
@k900:0upti.meK900 @emily can you take a look at what we're actually breaking with qtwebengine5 08:14:53
@emilazy:matrix.orgemilylike if we tried to remove it now?08:15:09
@emilazy:matrix.orgemilyor if we don't get it fixed on Darwin for 24.11?08:15:21
@emilazy:matrix.orgemilythe hacky fix for Darwin is pretty simple so we can probably just go ahead with that for now08:15:32
@emilazy:matrix.orgemilybut it does seem like it's better to get rid of it sooner rather than later for 25.0508:15:43
@k900:0upti.meK900Like if we remove and/or knownVulnerabilities it08:16:03
@emilazy:matrix.orgemily I can try and just delete it and see what nixpkgs-review thinks 08:16:09

Show newer messages


Back to Room ListRoom Version: 9