Re: Using kernel 5.19.8 does not boot

2022-09-21 Thread Sam Varshavchik
George N. White III writes: « HTML content follows » On Tue, Sep 20, 2022 at 8:57 PM Roger Heflin rogerhef...@gmail.com> wrote: Someone also reported nosound after 5.19.8 so it sounds like a lot of the modules either weren't built (at all or correct) or

Re: Using kernel 5.19.8 does not boot

2022-09-21 Thread George N. White III
On Tue, Sep 20, 2022 at 8:57 PM Roger Heflin wrote: > Someone also reported nosound after 5.19.8 so it sounds like a lot of > the modules either weren't built (at all or correct) or were not > included in the install rpms. > > a "find /lib/modules/kernelversion -name "*ko*" -ls | wc -l against it

Re: replacement for RLA Assist?

2022-09-21 Thread ToddAndMargo via users
On 9/21/22 11:44, Alex wrote: On Wed, 21 Sep 2022 11:41:30 -0700 ToddAndMargo via users wrote: Hi All, I have a customer on RLA Assist. http://www.rla-assist.com RLA is shutting it doors. It is basically a point of sale software. Anyone have an opinion for a replacement? Many thanks

Re: replacement for RLA Assist?

2022-09-21 Thread Alex
On Wed, 21 Sep 2022 11:41:30 -0700 ToddAndMargo via users wrote: > Hi All, > > I have a customer on RLA Assist. > http://www.rla-assist.com > RLA is shutting it doors. > > It is basically a point of sale software. > > Anyone have an opinion for a replacement? > > Many thanks, > -T > ___

replacement for RLA Assist?

2022-09-21 Thread ToddAndMargo via users
Hi All, I have a customer on RLA Assist. http://www.rla-assist.com RLA is shutting it doors. It is basically a point of sale software. Anyone have an opinion for a replacement? Many thanks, -T ___ users mailing list -- users@lists.fedoraproject.

Re: Restarting pipewire

2022-09-21 Thread Patrick O'Callaghan
On Wed, 2022-09-21 at 22:19 +0800, yanq...@fedoraproject.org wrote: > AFAIK pipewire is activated by systemd.socket, so > > $ systemctl --user stop pipewire pipewire-pulse > will work. Just stop current instance and systemd user daemon will > create a new one when needed. > > (using systemctl -

Re: Restarting pipewire

2022-09-21 Thread Patrick O'Callaghan
On Wed, 2022-09-21 at 07:01 -0700, Doug Herr wrote: > > > On Wed, Sep 21, 2022, at 4:26 AM, Patrick O'Callaghan wrote: > > After a recent update, tracer said I should restart pipewire: > > > > $ sudo tracer -a > > You should restart: > >   * These applications manually: > >   pipewire > >   

Re: Restarting pipewire

2022-09-21 Thread yanqiyu
AFAIK pipewire is activated by systemd.socket, so $ systemctl --user stop pipewire pipewire-pulse will work. Just stop current instance and systemd user daemon will create a new one when needed. (using systemctl --user restart [...] should also work) 在 2022-09-21星期三的 12:26 +0100，Patrick O'Call

Re: Restarting pipewire

2022-09-21 Thread Doug Herr
On Wed, Sep 21, 2022, at 4:26 AM, Patrick O'Callaghan wrote: > After a recent update, tracer said I should restart pipewire: > > $ sudo tracer -a > You should restart: > * These applications manually: > pipewire > pipewire-pulse > > Logging out and in had no effect, nor does there a

Restarting pipewire

2022-09-21 Thread Patrick O'Callaghan
After a recent update, tracer said I should restart pipewire: $ sudo tracer -a You should restart: * These applications manually: pipewire pipewire-pulse Logging out and in had no effect, nor does there appear to be a systemd unit installed: $ systemctl |grep pipewire $ Although t