00:10 ian|: with the function `wl_registry_bind(state.wl_registry, id, &zxdg_decoration_manager_v1_interface, 1)` what do i pass as `id`?
03:32 karenw: The 'name' recieved in your wl_registry::global callback that had the interface string "zxdg_decoration_manager_v1".
03:32 karenw: Oh, they aren't here any more, oh well
03:34 soreau: Yes, everyone looses
03:34 soreau: loses*
10:28 EggBap: Hey there, i'm running Debian Trixie. I have some core dumps appearing in my home directory. When I use File it says they are from /usr/bin/Xwayland. I'd like to try and help, but not sure where to go next :)
10:30 MrCooper: EggBap: coredumpctl from the systemd-coredump package allows getting backtraces from core dumps easily
10:48 EggBap: MrCooper: that program tells me that no core dumps have been found
10:50 MrCooper: did you just install the package?
10:51 MrCooper: if so, it'll collect core dumps from now on
11:57 EggBap: ahhh, okay, makes sense. I'll remove the current ones and wait for some future crashes :D
11:59 ofourdan: EggBap: also check the journalctl logs at the time of the issue, that might give a hint on what happened
12:00 EggBap: will do, thank you both
12:01 ofourdan: also important, please make sure to have the debug packages installed so we can make sense of the backtraces. With that, and the codedump (as you mentioned you have code dumps in your home directory), you can get the backtrace using gdb.
12:02 ofourdan: (I do not remember how to install debug packages in Debian though)
12:03 ofourdan: https://wiki.debian.org/DebugPackage
12:03 EggBap: lol, that was going to be my next question, i'll have a look.
12:03 EggBap: ^ awesome thx
12:04 ofourdan: better even: https://wiki.debian.org/HowToGetABacktrace
12:21 kode54: not sure how debug packages work there
12:22 kode54: at least on Arch, there's debuginfod which fetches debug packages at debug time
12:22 kode54: oh, damn, they left
12:26 plouto: teh faek Arsch® LieUNIX™ copyWrite©2002
12:27 plouto: ^ not a distribution, just a couple of non-important "pacman" frontends
12:29 plouto: https://en.wikipedia.org/w/index.php?limit=20&offset=0&search=pacman+package&useskin=vector&ns0=1
13:21 kode54: does nobody else use debuginfod?
13:22 ofourdan: fedora does, and I think debian as well, and suse most likely
13:29 kode54: nice
13:29 kode54: I only mentioned the btw distro because it's what I use
13:30 kode54: I wasn't aware of its spread among other distributions
13:38 DemiMarie: I don't like debuginfod.
13:39 DemiMarie: If clients checked the hash of files they downloaded I would be fine.
13:40 kennylevinsen: open an issue against the clients then?
13:47 Ermine: opensuse uses debuginfod too, but debuginfo there is not for every package
15:29 Arnavion: OpenSUSE used to use debuginfod but they shut down the service a long time ago
16:51 DemiMarie: kennylevinsen: not sure if they have enough information
18:00 ericonr: Yeah, I think all the available info is build-id...
18:00 ericonr: DemiMarie: would you like something like a signed catalog of debuginfo?
18:00 ericonr: Ro
18:01 ericonr: Or have the debug package splitting include the hash of debuginfo files into the binaries
18:22 DemiMarie: ericonr: Binaries should have the hash of the debuginfo built-in. That allows trivially validating the debuginfo.
18:28 DemiMarie: It also allows content-addressed storage, with all the nice properties that brings, such as infinite cacheability.
21:23 ericonr: DemiMarie: sounds like a valid improvement proposal to binutils/elfutils/lld
21:24 ericonr: They got json into ELF, you can get better security