On 04/10/2021 00:51, Roger Heflin wrote:
With 10 minute samples anything that happened gets averaged enough
that even the worst event is almost impossible to see.
Sar will report the same as date ie local time. And a 12:51 event
would be in the 13:00 sample (started at about 12:50 and ended a
On 04/10/2021 13:19, Robert McBroom via users wrote:
The setting to have the window focus follo the mouse cursor seems to have been
hidden away. Plasma and Xfce have very few of what used to be common optionx
for the mouse.
In Xfce run xfwm4-settings and choose "Focus"
In Plasma it is in Sys
The setting to have the window focus follo the mouse cursor seems to
have been hidden away. Plasma and Xfce have very few of what used to be
common optionx for the mouse.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an em
On 04/10/2021 09:43, Adi Pircalabu wrote:
Didn't have setroubleshoot-server, so I went and installed it. "sealert -b"
does nothing, or I don't know how to use it yet. Then I went and analyzed the
audit
log with "sealert -a /var/log/audit/audit.log" and here's the important
bit:
type=AVC msg=aud
> Didn't have setroubleshoot-server, so I went and installed it. "sealert -b"
> does nothing, or I don't know how to use it yet. Then I went and analyzed the
> audit
> log with "sealert -a /var/log/audit/audit.log" and here's the important
> bit:
>
> type=AVC msg=audit(1633309984.892:327): avc:
> On 04/10/2021 08:56, Adi Pircalabu wrote:
>
> If you run "sealert -b" what does it have for "troubleshooting"?
>
> I'm running KDE/F34 and not seeing any issues.
Didn't have setroubleshoot-server, so I went and installed it. "sealert -b"
does nothing, or I don't know how to use it yet. Then I
On 04/10/2021 08:56, Adi Pircalabu wrote:
ausearch -m AVC,USER_AVC
[...]
time->Sat Oct 2 13:35:30 2021
type=PROCTITLE msg=audit(1633145730.776:6604): proctitle="(systemd)"
type=SOCKADDR msg=audit(1633145730.776:6604): saddr=1000
type=SYSCALL msg=audit(1633145730.776:6604
ausearch -m AVC,USER_AVC
[...]
time->Sat Oct 2 13:35:30 2021
type=PROCTITLE msg=audit(1633145730.776:6604): proctitle="(systemd)"
type=SOCKADDR msg=audit(1633145730.776:6604): saddr=1000
type=SYSCALL msg=audit(1633145730.776:6604): arch=c03e syscall=46
success=yes exi
If I stop pipewire I lose sound, so if I run it in the foreground it ll be
closed if I close the terminal window before logout. It appears to be related
to selinux. If I boot the laptop with selinux=0 kernel argument sound works
fine. If I remove selinux=0 arg and reboot I lose sound again. It a
On 04/10/2021 08:08, Adi Pircalabu wrote:
$ systemctl --user status pipewire
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status pipewire-pulse.socket
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl
$ systemctl --user status pipewire
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status pipewire-pulse.socket
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
$ systemctl --user status pipewire-pulse.service
Failed
> On Sun, 03 Oct 2021 23:44:44 -
> Adi Pircalabu wrote:
>
>
> Check the dumb stuff first! I have forgotten I left mute on before :-).
> I've also had linux forget which sound device I told it to use.
> There's always booting off a live image and seeing if sound works
> there, if not, might be
With 10 minute samples anything that happened gets averaged enough that
even the worst event is almost impossible to see.
Sar will report the same as date ie local time. And a 12:51 event would be
in the 13:00 sample (started at about 12:50 and ended at 1300).
What I do see is that during that w
On Sun, 03 Oct 2021 23:44:44 -
Adi Pircalabu wrote:
> I'm very confused at this point :)
Check the dumb stuff first! I have forgotten I left mute on before :-).
I've also had linux forget which sound device I told it to use.
There's always booting off a live image and seeing if sound works
th
Hi, been running a fresh install of f34 on my laptop for about a week or so
with no sound issues and this morning after booting (previous state was shut
down) I discovered there's no sound in gnome. Worked perfectly fine last week.
Where do I start with the debugging?
rpm -qa kernel-\* | sort
ke
45 second event happened at: 2021-10-02T11:51:02 UTC. Not sure what sar
time is based on (maybe local time BST rather than UTC so would be
2021-10-02T12:51:02 BST.
Continuing info ...
sar -n NFSD on the server
11:00:01 24.16 0.00 24.16 0.00 24.16 0.00
0.00
45 second event happened at: 2021-10-02T11:51:02 UTC. Not sure what sar
time is based on (maybe local time BST rather than UTC so would be
2021-10-02T12:51:02 BST.
"sar -d" on the server:
11:50:02 dev8-0 4.67 0.01 46.62 0.00 9.99
0.12 14.03 5.75
11:50:0
17 matches
Mail list logo
