[01:49] <guiverc> DarkTrick, PITA = most printers, lots of crap gadgets, pain in the ar...
[01:49] <DarkTrick> 👍️
[01:49] <guiverc> you got the answer from the source anyway...
[01:50] <sarnold> hahaha
[01:51] <DarkTrick> Maybe I should move the discussion here: I imagine "Ubuntu" is comparably strong. Why doesn't Ubuntu go through with defining a clear mechanism and let others adapt / make others adapt?
[01:51] <DarkTrick> "legacy support"?
[01:51] <daftykins> sounds like you're starting in the middle
[01:51] <daftykins> mechanism for what?
[01:53] <DarkTrick> daftykins, sorry, the rest was from #ubuntu.
[01:53] <DarkTrick> sec
[01:54] <DarkTrick> Systemd has a lot of paths regarding starting of units (https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Unit%20File%20Load%20Path)
[01:54] <DarkTrick> They are "all over the place" (/etc/run/usr/).
[01:55] <DarkTrick> "it'd be so much nicer to have a well-defined override mechanism, or an add-in mechanism, like systemd's designed. "
[03:35] <lotuspsychje> good morning
[05:06] <ducasse> good morning
[09:55] <lotuspsychje> mgedmin: from this morning; <jmspeex> mgedmin: FYI, my two-line patch worked. My battery indicator hw is still misbehaving, but at least it no longer shuts down my machine. Thanks for the tips.
 Do you know if it's worth trying to upstream my fix (or something similar)? And if so, where?
[09:56] <mgedmin> ah, I saw the first msg but not the second
[12:50] <lotuspsychje> !ubuntu+1 is Hirsute Hippo is the codename for Ubuntu 21.04. For technical support, see #ubuntu+1. For testing and QA feedback and help, see #ubuntu-quality.
[12:58] <lotuspsychje> !21.04 is <reply> Ubuntu 21.04 (Hirsute Hippo) will be the 34rd release of Ubuntu, scheduled for release April 2021 ( https://discourse.ubuntu.com/t/hirsute-hippo-release-schedule/18539 ). Join #ubuntu+1 for support and questions.
[13:01] <lotuspsychje> !hirsute is <reply> Ubuntu 21.04 (Hirsute Hippo) will be the 34rd release of Ubuntu, scheduled for release April 2021 ( https://discourse.ubuntu.com/t/hirsute-hippo-release-schedule/18539 ). Join #ubuntu+1 for support and questions.
[13:45] <TJ-> Hairy Hippo!?!
[13:45] <TJ-> get a shave!
[13:47] <xMeia> what you say man
[13:48] <xMeia> no
[13:49] <lotuspsychje> lol
[13:49] <xMeia> yo
[13:49] <xMeia> yo
[13:51] <xMeia> ok
[13:52] <xMeia> lets just
[13:52] <TJ-> there's always one
[13:53] <xMeia> testing irc colors
[13:53] <xMeia> haha
[13:58] <Maik> test in #test instead of here
[13:59] <xMeia> I'm done
[14:01] <Maik> good
[16:53] <TJ-> that feeling you have after 4 months tracking down an obscure kernel or hardware bug only to discover it isn't a bug and it is self-inflicted!
[18:01] <ceed^> Gotta love the bot! Solved my firmware install problem after 20.10 upgrade. All good now. I wonder if this is a bug in the upgrade process?
[18:03] <TJ-> ceed^: the bot didn't solve it; I did... I commanded the bot to tell you
[18:05] <ceed^> TJ-: I know that a bot needs to input to output, but it came from the bot so I love it :) Thank you though for solving this for me
[18:06] <ceed^> I still wonder why that package was missing after the upgrade to 20.10. Seems like some sort of bug to me.
[18:08] <TJ-> ceed^: possibly due to the reverse-dependencies, or a package not marked as 'automatic'
[18:09] <ceed^> TJ-: Does that mean it will happen to others also, or was is just me hitting on a snag?
[18:10] <TJ-> ceed^: hard to say but I don't see any glaring problems with the packages so I suspect it was unique to your config
[18:15] <ceed^> TJ-: I hope so. Thank you so much though.
[18:16] <mgedmin> somebody who knows how to read apt logs could probably figure it out from the upgrade logs
[18:17] <mgedmin> fwupd-signed is Recommended: by fwupd and by ubuntu-desktop-minimal (and many other desktop metapackages)
[18:18] <mgedmin> I think do-release-upgrade likes to ensure the right desktop metapackage is installed, which should also pull in everything Recommended by it
[18:18] <mgedmin> unless you disabled auto-installing of recommends in an apt config file somewhere?
[18:19] <TJ-> it shouldn't have been removed though, that is the strange part, but yes, the apt log would reveal all (in /var/log/apt/ )
[18:27] <mgedmin> or /var/log/dist-upgrade/, which is where do-release-upgrade keeps its logs (in a very confusing hierarchy)
[18:28] <ceed^> mgedmin: Confusing to the OS itself it seems.
[19:56] <ducasse> TJ-: have you used the zfs backing store for lxc?
[19:56] <TJ-> ducasse: no
[19:56] <ducasse> the lxc-create man page mentuions it exists, but has no details
[19:56] <ducasse> i'll go google