On 6/24/21 5:15 AM, Christopher Ross wrote:
The top part of systemd-analyze-blame is
1min 23.232s plymouth-quit-wait.service
53.077s cs-firewall-bouncer.service
52.219s dovecot.service
26.525s crowdsec.service
26.075s libvirtd.service
25.910s
On Thu, 2021-06-24 at 14:21 +0100, Christopher Ross wrote:
> > I was under the impression that GDM + KDE didn't work well, maybe
> > try
> > using a KDE-friendly login manager like sddm?
>
>
> I only recently changed from sddm to gdm because the "switch user"
> functionality has been removed fro
On 24/06/2021 14:05, Jonathan Billings wrote:
On Thu, Jun 24, 2021 at 01:34:27PM +0100, Christopher Ross wrote:
I should have mentioned that I'm running KDE not Gnome, but at this stage it
hasn't run. The 3½ minutes is the time it takes from power on to bring up
the GDM login screen.
I can't
On Thu, Jun 24, 2021 at 01:34:27PM +0100, Christopher Ross wrote:
> I should have mentioned that I'm running KDE not Gnome, but at this stage it
> hasn't run. The 3½ minutes is the time it takes from power on to bring up
> the GDM login screen.
>
> I can't remember the exact message from abrtd. I
On 24/06/2021 13:11, Jonathan Billings wrote:
On Thu, Jun 24, 2021 at 12:15:48PM +0100, Christopher Ross wrote:
Fedora 34 on my i7 with 32G RAM and nvidia RTX2060 card takes minutes to
boot, and when it finally does there are a number of "something went wrong"
notifications. How best can I dia
On Thu, Jun 24, 2021 at 12:15:48PM +0100, Christopher Ross wrote:
> Fedora 34 on my i7 with 32G RAM and nvidia RTX2060 card takes minutes to
> boot, and when it finally does there are a number of "something went wrong"
> notifications. How best can I diagnose and fix this so that it boots quickly
>
Dear fellow Fedorans,
Fedora 34 on my i7 with 32G RAM and nvidia RTX2060 card takes minutes to
boot, and when it finally does there are a number of "something went
wrong" notifications. How best can I diagnose and fix this so that it
boots quickly and without errors?
CPU: Quad Core Intel Co
