On Mon, 2024-07-22 at 21:02 -0400, Jonathan Billings wrote:
> /dev/shm is a tmpfs filesystem. Anything placed there is wiped after
> shutdown. It doesn’t exist on the disk.
>
> Jack uses it for ephemeral files that only exist while it runs.
>
> While it’s possible to use %ghost in the rpm spec
On 7/22/24 11:27 PM, Javier Perez wrote:
Done.
Let's see if it works...
I was hoping to see what the output was. The only one that would have
affected anything was the last one. Did it do anything?
--
___
users mailing list -- users@lists.fedorap
Done.
Let's see if it works...
On Tue, Jul 23, 2024 at 12:51 AM Samuel Sieb wrote:
> On 7/22/24 10:35 PM, Javier Perez wrote:
> > Hi. I am getting SELINUX notifications about zram-generator.
> >
> > Should I report the bug?
> >
> > SELinux is preventing zram-generator from open access on the fil
On 7/22/24 10:35 PM, Javier Perez wrote:
Hi. I am getting SELINUX notifications about zram-generator.
Should I report the bug?
SELinux is preventing zram-generator from open access on the file
/usr/lib/systemd/zram-generator.conf.
Try running the following:
rpm -qV zram-generator
ls -lZ /us
Hi. I am getting SELINUX notifications about zram-generator.
Should I report the bug?
SELinux is preventing zram-generator from open access on the file
/usr/lib/systemd/zram-generator.conf.
* Plugin catchall (100. confidence) suggests
**
If you believe that zram-gen
On 7/22/24 7:20 PM, Alex wrote:
I've used fedora since it was called Red Hat, but this is the first time
I've seen disk compression and mounting the same partition on multiple
mount points.
Can someone help me understand what's happening here?
UUID=832cbf4d-a17f-457d-b768-bd5c1a26bf86 /
Hi,
I've used fedora since it was called Red Hat, but this is the first time
I've seen disk compression and mounting the same partition on multiple
mount points.
Can someone help me understand what's happening here?
UUID=832cbf4d-a17f-457d-b768-bd5c1a26bf86 / btrfs
subvol=r
On Jul 22, 2024, at 19:55, fed...@eyal.emu.id.au wrote:
>
> Yesterday I set up midi for a keyboard, so installed qjackctl/qsynth. This
> morning, in the rkhunter daily run report I see:
>
> Warning: Suspicious file types found in /dev:
> /dev/shm/jack-shm-registry: data
> /dev/s
Yesterday I set up midi for a keyboard, so installed qjackctl/qsynth. This
morning, in the rkhunter daily run report I see:
Warning: Suspicious file types found in /dev:
/dev/shm/jack-shm-registry: data
/dev/shm/jack_sem.500_default_qsynth: data
/dev/shm/jack_sem.0_def
On Mon, 2024-07-22 at 12:16 -0400, Jon LaBadie wrote:
> On Mon, Jul 22, 2024 at 01:53:56PM +0100, Patrick O'Callaghan wrote:
> > On Mon, 2024-07-22 at 08:41 -0400, Jeffrey Walton wrote:
> > > On Mon, Jul 22, 2024 at 8:36 AM Patrick O'Callaghan
> ...
> > >
> > > Here was your original question:
> >
Hi,
> This is on a PowerEdge R720, booting from a virtual DVD ISO.
>
>
> I used a USB stick with Fedora live image on it to install on a R720,
> likely it was f37 or f38 as after the first install I did dnf
> system-upgrade.
>
> I think booting an ISO was tried and failed, but its too long ago and
> On 22 Jul 2024, at 15:33, Paolo Galtieri wrote:
>
> I'm running syslog because that has what has always been running.
Unless you need specific syslog features journal is a big improvement.
The logs are records with fields, not just a string of text, that allows for
smarter searching for ex
On Mon, Jul 22, 2024 at 9:45 AM Richard Shaw wrote:
> On Mon, Jul 22, 2024 at 6:34 AM Neal Becker wrote:
>
>> After installing this morning's large set of updates I rebooted into
>> 6.9.9. Now chrome doesn't work, every process is crashing. After
>> rebooting, restarting chrome the problem per
On Mon, Jul 22, 2024 at 01:53:56PM +0100, Patrick O'Callaghan wrote:
On Mon, 2024-07-22 at 08:41 -0400, Jeffrey Walton wrote:
On Mon, Jul 22, 2024 at 8:36 AM Patrick O'Callaghan
...
Here was your original question:
Any suggestions? I've never seen this message before
doing the switch
I'm running syslog because that has what has always been running. This
was from before systemd. Why both rsyslog and syslog-ng were running I
have no idea. I did not intentionally start both, I assumed only one
would be running.
Paolo
On 7/21/24 01:15, Barry wrote:
On 21 Jul 2024, at 01
On Mon, Jul 22, 2024 at 6:34 AM Neal Becker wrote:
> After installing this morning's large set of updates I rebooted into
> 6.9.9. Now chrome doesn't work, every process is crashing. After
> rebooting, restarting chrome the problem persists. Finally I rebooted into
> 6.9.8 and chrome is fine.
On Mon, 2024-07-22 at 08:41 -0400, Jeffrey Walton wrote:
> On Mon, Jul 22, 2024 at 8:36 AM Patrick O'Callaghan
> wrote:
> >
> > On Mon, 2024-07-22 at 08:24 -0400, Jeffrey Walton wrote:
> > > On Mon, Jul 22, 2024 at 7:33 AM Patrick O'Callaghan
> > > wrote:
> > > >
> > > > I've installed a new mo
On Mon, Jul 22, 2024 at 8:36 AM Patrick O'Callaghan
wrote:
>
> On Mon, 2024-07-22 at 08:24 -0400, Jeffrey Walton wrote:
> > On Mon, Jul 22, 2024 at 7:33 AM Patrick O'Callaghan
> > wrote:
> > >
> > > I've installed a new motherboard and CPU, swapping an Intel i7 for
> > > an
> > > AMD Ryzen 5 7600
On Mon, 2024-07-22 at 08:24 -0400, Jeffrey Walton wrote:
> On Mon, Jul 22, 2024 at 7:33 AM Patrick O'Callaghan
> wrote:
> >
> > I've installed a new motherboard and CPU, swapping an Intel i7 for
> > an
> > AMD Ryzen 5 7600. So far all is well, except that hibernation
> > doesn't
> > work:
> >
>
On Mon, Jul 22, 2024 at 7:33 AM Patrick O'Callaghan
wrote:
>
> I've installed a new motherboard and CPU, swapping an Intel i7 for an
> AMD Ryzen 5 7600. So far all is well, except that hibernation doesn't
> work:
>
> Jul 22 01:01:13 Bree kernel: Lockdown: systemd-logind: hibernation is
> restrict
On Mon, 2024-07-22 at 13:00 +0100, Barry wrote:
>
>
> > On 22 Jul 2024, at 12:33, Patrick O'Callaghan
> > wrote:
> >
> > kernel: Lockdown: systemd-logind: hibernation is restricted
>
> I did a search for the message and there a number of explanations.
> Do they help?
I did read the man page,
> On 22 Jul 2024, at 12:33, Patrick O'Callaghan wrote:
>
> kernel: Lockdown: systemd-logind: hibernation is restricted
I did a search for the message and there a number of explanations.
Do they help?
Barry
--
___
users mailing list -- users@lists.f
On 22 Jul 2024, at 12:34, Neal Becker wrote:After installing this morning's large set of updates I rebooted into 6.9.9. Now chrome doesn't work, every process is crashing. After rebooting, restarting chrome the problem persists. Finally I rebooted into 6.9.8 and chrome is fine.You may find tha
After installing this morning's large set of updates I rebooted into
6.9.9. Now chrome doesn't work, every process is crashing. After
rebooting, restarting chrome the problem persists. Finally I rebooted into
6.9.8 and chrome is fine.
--
___
users mai
I've installed a new motherboard and CPU, swapping an Intel i7 for an
AMD Ryzen 5 7600. So far all is well, except that hibernation doesn't
work:
Jul 22 01:01:13 Bree kernel: Lockdown: systemd-logind: hibernation is
restricted; see man kernel_lockdown.7
Jul 22 01:01:18 Bree kernel: Lockdown: syst
When trying to start the NFS-server on a just installed F40 system it stops
immediately. What is wrong? Below I give the systemctl status and the relevant
part of the journalctl.
root@s185:~# systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib
26 matches
Mail list logo
