Hi All,
Fedora 34
bind-chroot-9.16.16-1.fc34.x86_64
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.
On 6/23/21 12:59 AM, Gordon Messmer wrote:
On 6/22/21 8:55 PM, Robert McBroom via users wrote:
On 6/21/21 11:41 PM, Gordon Messmer wrote:
On 6/21/21 6:17 AM, Robert McBroom via users wrote:
@RobertPC ~]# mount -v -t nfs
[fd2e:cb3b:f005::ec1]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: tim
Hi All,
Fedora 34
Xfce 4.14
redshift-1.12-11.fc34.x86_64
redshift-gtk-1.12-11.fc34.x86_64
Hi All,
Red Shift is all screwed up again:
Unable to connect to GeoClue. Unable to get location from provider:
https://github.com/jonls/redshift/issues/318#issuecomment-865667340
is back in full force.
On 24/06/2021 19:59, Robert McBroom via users wrote:
With ipv4 the mount is successful with apparently trying alternate port and
protocol automatically.
mount.nfs: trying text-based options 'addr=192.168.1.239'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: trying 192.168.1.239 pro
On 2021-06-24 at 12:00:40 Samuel Sieb wrote:
> On 6/24/21 11:57 AM, Erik P. Olsen wrote:
> > I don't believe I am using qemu for anything and would therefore prefer to
> > remove it
> > entirely. Is it doable?
>
> I don't see any reason why not. Did you try? It's installed by default
> for
On 6/24/21 11:57 AM, Erik P. Olsen wrote:
I don't believe I am using qemu for anything and would therefore prefer to
remove it
entirely. Is it doable?
I don't see any reason why not. Did you try? It's installed by default
for gnome-boxes.
___
use
Hello,
I don't believe I am using qemu for anything and would therefore prefer to
remove it
entirely. Is it doable?
Thanks.
--
Erik P. Olsen - Copenhagen, Denmark
Fedora 34/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 11.0.5
___
users mailing list
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 24/06/2021 19:59, Robert McBroom via users wrote:
With ipv4 the mount is successful with apparently trying alternate port and
protocol automatically.
mount.nfs: trying text-based options 'addr=192.168.1.239'
mount.nfs: prog 13, trying vers=3, prot=6
mount.nfs: trying 192.168.1.239 prog
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
>
On 6/23/21 12:59 AM, Gordon Messmer wrote:
On 6/22/21 8:55 PM, Robert McBroom via users wrote:
On 6/21/21 11:41 PM, Gordon Messmer wrote:
On 6/21/21 6:17 AM, Robert McBroom via users wrote:
@RobertPC ~]# mount -v -t nfs
[fd2e:cb3b:f005::ec1]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy
mount.nfs: tim
On 24/06/2021 12:20, Patrick O'Callaghan wrote:
On Thu, 2021-06-24 at 11:42 +0100, Christopher Ross wrote:
How can I go about diagnosing and fixing that?
In 2021 i7 machines should not be taking literally minutes to boot.
On my system (also an i7) that takes only 5s. Presumably something is
h
On Thu, 2021-06-24 at 11:42 +0100, Christopher Ross wrote:
>
>
> On 12/06/2021 20:45, Joe Zeff wrote:
> > On 6/12/21 11:54 AM, Patrick O'Callaghan wrote:
> > > Not my case. I don't have systemd-udev-settle.service. This is a
> > > fresh
> > > install of F34.
> >
> > Ok, you can still use systemd
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
On Thu, 24 Jun 2021 at 07:42, Christopher Ross
wrote:
>
>
> On 12/06/2021 20:45, Joe Zeff wrote:
>
> On 6/12/21 11:54 AM, Patrick O'Callaghan wrote:
>
> Not my case. I don't have systemd-udev-settle.service. This is a fresh
> install of F34.
>
>
> Ok, you can still use systemd-analyze blame to fi
On 24/06/2021 18:42, Christopher Ross wrote:
On 12/06/2021 20:45, Joe Zeff wrote:
On 6/12/21 11:54 AM, Patrick O'Callaghan wrote:
Not my case. I don't have systemd-udev-settle.service. This is a fresh
install of F34.
Ok, you can still use systemd-analyze blame to find out what's causing the
On 12/06/2021 20:45, Joe Zeff wrote:
On 6/12/21 11:54 AM, Patrick O'Callaghan wrote:
Not my case. I don't have systemd-udev-settle.service. This is a fresh
install of F34.
Ok, you can still use systemd-analyze blame to find out what's causing
the delay.
On my F34 boot systemd-udev-settle.
21 matches
Mail list logo
