[02:30] <FurretUber> Just got the third install to crash on upgrade
[02:31] <FurretUber> This time it's still running, so I may get something from it
[02:33] <FurretUber> Got signal 15 from process 1
[02:37] <FurretUber> Hmmm... I tried to use systemctl status lightdm and got "Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)"
[02:39] <FurretUber> Apparently when systemd updates, it crashes lightdm and then some commands stop working, as systemctl
[02:52] <FurretUber> I reported this, it is bug 1963600
[02:52] <ubottu> Bug 1963600 in systemd (Ubuntu) "On upgrade, systemctl and lightdm stop working, leaving the system in a degraded state" [Undecided, New] https://launchpad.net/bugs/1963600
[02:53] <tomreyn> process 1 is systemd itself
[02:54] <tomreyn> the "SystemdFailedUnits:" output attached to your bug report looks interesting
[02:55] <FurretUber> Is there a way I can get the same info without apport? I have one crashed machine here, with one tty I started before the upgrade
[02:55] <lotuspsychje> FurretUber: does that happen on xubuntu only, or other flavours/desktop aswell?
[02:55] <FurretUber> For now, I tested only with Xubuntu
[02:56] <lotuspsychje> and i didnt test lightdm on -desktop yet, maybe Maik ?
[02:56] <lotuspsychje> or guiverc ^
[02:57] <tomreyn> is that the default kernel version? "ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19"  https://packages.ubuntu.com/jammy/linux-image-generic seems to point elsewhere
[02:57]  * guiverc reading ^
[02:57] <tomreyn> (but it could be outdated)
[02:59] <FurretUber> I got this on 5.4.0-100 too
[02:59] <FurretUber> And on 5.13.0-19-generic
[03:00] <lotuspsychje> 5.15.0-18-generic here tomreyn 
[03:01] <tomreyn> lotuspsychje: right, that's the version p.u.c points to
[03:04] <guiverc> FurretUber, systemd-oomd can close down processes if it detects OOM (out-of-memory)  so I'd check journalctl ; but that's just a thought as I have no ideas from what I see sorry
[03:07] <lotuspsychje> being able to reproduce this, is interesting indeed
[03:09] <FurretUber> From journalctl (which gladly works), there are more services with the service_start_timeout=25000ms message
[03:51] <guiverc> I see 3 bugs (recent) bugs reported on lightdm on jammy with xubuntu/xfce
[09:17] <tarzeau> meh libpcl-dev not installable due to libtbb12 : Breaks: libtbb2 (< 2021) but 2020.3-1 is to be installed
=== jailbreak is now known as Star2023
=== Star2023 is now known as jailbreak
[13:16] <Maik> lotuspsychje: sorry, i only run Ubuntu 22.04 on the Pi and Kubuntu 22.04 on this machine
[13:25] <unixtippse> Hey everyone, any known issues with today's jammy-live-server-amd64.iso? My subiquity test environments download 98%/99% of the image, report "loop0 capacity change", "Unable to find a live filesystem on the network" and drop into an initramfs shell. SHA256 ending in -e4f85b1e double- and triple-checked.
=== kinghat3 is now known as kinghat
=== ChunkzZ is now known as jailbreak
[22:21] <jailbreak> Yeah so hearing Firefox is moving to a 'snap' version, can we still install the .deb with 22.04? please say yeah!!
[22:59] <PaulW2U> jailbreak: no, at Mozilla's request the deb is giving way to the snap - see bug 1962021
[22:59] <ubottu> Bug 1962021 in firefox (Ubuntu) "Make the deb package install the firefox snap" [High, In Progress] https://launchpad.net/bugs/1962021
[23:21] <kinghat> mozilla also publishing flatpaks too i think 🤔
[23:26] <Maik> so Mozilla decided to drop the deb package in favor of snap on Ubuntu and on the other hand they let Mint still use deb? Makes no sense to me