Hi, all,
I'm having an odd problem. On two of my laptops, on which I've just done
fresh installs, I cannot get the external monitor to work. Using either
the XFCE display configuration tool, it shows up, but it's marked as
'disabled'. I do not seem to have the usual such tool under KDE, which
On Apr 27, 2022, at 07:25, Justin Moore wrote:
>
>
>> On Tue, Apr 26, 2022 at 6:06 PM Jonathan Billings
>> wrote:
>
>> [snip] Could systemd do a better job saying what it was waiting on? Yes.
>> Is it so horribly broken it doesn’t know how to exit? No.
>
> This kind of blanket dismissal
On Wed, 2022-04-27 at 19:10 +, Cătălin George Feștilă wrote:
> I read this article
> https://www.theregister.com/2022/04/27/fedora_starts_to_simplify_linux/
> The question is whether we can still use old laptops. I have an HP
> 6710b and it works very well at the moment with Fedora 36.
I think
On Wed, 2022-04-27 at 08:05 -0400, Sam Varshavchik wrote:
> The only reason systemd-resolved exists is because glibc caches
> /etc/resolv.conf when a process performs its first DNS lookup. Having
> the means to have an existing process become aware that its been
> changed, and it should reread it
I read this article
https://www.theregister.com/2022/04/27/fedora_starts_to_simplify_linux/.
The question is whether we can still use old laptops. I have an HP 6710b and it
works very well at the moment with Fedora 36.
In this case, my opinion is that the development team will release a special
> On 27 Apr 2022, at 13:05, Sam Varshavchik wrote:
>
> The only reason systemd-resolved exists is because glibc caches
> /etc/resolv.conf when a process performs its first DNS lookup. Having the
> means to have an existing process become aware that its been changed, and it
> should reread it
Justin Moore writes:
This kind of blanket dismissal of user feedback and refusal to believe *even
the possibility* that systemd could be broken in obvious ways contributes to
the sense from the community that negative feedback about systemd has been
and will be ignored.
Had the response
On Tue, Apr 26, 2022 at 6:06 PM Jonathan Billings
wrote:
> >> The systemd --user daemon does hang around though, and it is likely it
> is waiting on terminating some pesky user process that wasn’t terminating
> properly. It isn’t the blocking process, it is the daemon trying to
> terminate it.
>
