systemd service fails to run with "ConditionACPower=true was not met"
Fedora 36, plocate-1.1.15-3.fc36.x86_64, systemd-250.8-1.fc36.x86_64 /usr/lib/systemd/system/plocate-updatedb.service has ConditionACPower=true because they don't want updatedb to run when on a laptop battery. Now, my machine is an Intel NUC which has an Intel mobile chipset but is very definitely not a laptop. It doesn't have a battery and always runs off AC power. But ... $ sudo systemctl status plocate-updatedb.service |& cat ○ plocate-updatedb.service - Update the plocate database Loaded: loaded (/usr/lib/systemd/system/plocate-updatedb.service; static) Active: inactive (dead) TriggeredBy: ● plocate-updatedb.timer Condition: start condition failed at Fri 2022-08-05 10:29:57 BST; 5min ago └─ ConditionACPower=true was not met Aug 03 14:59:37 dev5 systemd[1]: plocate-updatedb.service - Update the plocate database was skipped because of a failed condition check (ConditionACPower=true). Aug 04 09:29:21 dev5 systemd[1]: plocate-updatedb.service - Update the plocate database was skipped because of a failed condition check (ConditionACPower=true). Aug 05 10:29:35 dev5 systemd[1]: plocate-updatedb.service - Update the plocate database was skipped because of a failed condition check (ConditionACPower=true). Aug 05 10:29:57 dev5 systemd[1]: plocate-updatedb.service - Update the plocate database was skipped because of a failed condition check (ConditionACPower=true). Looking at systemd sources it seems as if ConditionACPower is checked here: https://github.com/systemd/systemd/blob/14e7bc2e77d2699498a1f74d7e4f905f11eca335/src/shared/udev-util.c#L662 It's a bit hard to follow what the code is doing, but I think it's looking in /sys for power_supply devices. This hardware has two, both with type == USB. (I believe these are the two USB ports on the front panel that can provide power to other devices, they cannot power the machine itself.) $ ll /sys/devices/platform/USBC000:00/power_supply total 0 drwxr-xr-x. 5 root root 0 Aug 3 09:00 ucsi-source-psy-USBC000:001 drwxr-xr-x. 5 root root 0 Aug 3 09:00 ucsi-source-psy-USBC000:002 $ cat /sys/devices/platform/USBC000:00/power_supply/*/type USB USB $ cat /sys/devices/platform/USBC000\:00/power_supply/ucsi-source-psy-USBC000\:00*/device/typec/port*/power_role [sink] [sink] [sink] [sink] $ cat /sys/devices/platform/USBC000\:00/power_supply/ucsi-source-psy-USBC000\:00*/online 0 0 Anyway, I think this is a systemd bug, right? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: systemd service fails to run with "ConditionACPower=true was not met"
> On 5 Aug 2022, at 10:48, Richard W.M. Jones wrote: > > Fedora 36, plocate-1.1.15-3.fc36.x86_64, systemd-250.8-1.fc36.x86_64 > > /usr/lib/systemd/system/plocate-updatedb.service has > ConditionACPower=true because they don't want updatedb to run > when on a laptop battery. > > Now, my machine is an Intel NUC which has an Intel mobile chipset but > is very definitely not a laptop. It doesn't have a battery and always > runs off AC power. > > But ... > > $ sudo systemctl status plocate-updatedb.service |& cat > ○ plocate-updatedb.service - Update the plocate database > Loaded: loaded (/usr/lib/systemd/system/plocate-updatedb.service; > static) > Active: inactive (dead) > TriggeredBy: ● plocate-updatedb.timer >Condition: start condition failed at Fri 2022-08-05 10:29:57 BST; 5min ago > └─ ConditionACPower=true was not met > > Aug 03 14:59:37 dev5 systemd[1]: plocate-updatedb.service - Update the > plocate database was skipped because of a failed condition check > (ConditionACPower=true). > Aug 04 09:29:21 dev5 systemd[1]: plocate-updatedb.service - Update the > plocate database was skipped because of a failed condition check > (ConditionACPower=true). > Aug 05 10:29:35 dev5 systemd[1]: plocate-updatedb.service - Update the > plocate database was skipped because of a failed condition check > (ConditionACPower=true). > Aug 05 10:29:57 dev5 systemd[1]: plocate-updatedb.service - Update the > plocate database was skipped because of a failed condition check > (ConditionACPower=true). > > Looking at systemd sources it seems as if ConditionACPower is checked > here: > > > https://github.com/systemd/systemd/blob/14e7bc2e77d2699498a1f74d7e4f905f11eca335/src/shared/udev-util.c#L662 > > It's a bit hard to follow what the code is doing, but I think it's > looking in /sys for power_supply devices. This hardware has two, both > with type == USB. (I believe these are the two USB ports on the front > panel that can provide power to other devices, they cannot power the > machine itself.) > > $ ll /sys/devices/platform/USBC000:00/power_supply > total 0 > drwxr-xr-x. 5 root root 0 Aug 3 09:00 ucsi-source-psy-USBC000:001 > drwxr-xr-x. 5 root root 0 Aug 3 09:00 ucsi-source-psy-USBC000:002 > $ cat /sys/devices/platform/USBC000:00/power_supply/*/type > USB > USB > > $ cat > /sys/devices/platform/USBC000\:00/power_supply/ucsi-source-psy-USBC000\:00*/device/typec/port*/power_role > > [sink] > [sink] > [sink] > [sink] > > $ cat > /sys/devices/platform/USBC000\:00/power_supply/ucsi-source-psy-USBC000\:00*/online > 0 > 0 > > Anyway, I think this is a systemd bug, right? That code has lots of debug logs. Try running systemd with log level debug and see which of those logs is printed. Barry > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-top is 'top' for virtual machines. Tiny program with many > powerful monitoring features, net stats, disk stats, logging, etc. > http://people.redhat.com/~rjones/virt-top > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: systemd service fails to run with "ConditionACPower=true was not met"
On Fri, Aug 05, 2022 at 11:36:13AM +0100, Barry wrote: > > > > On 5 Aug 2022, at 10:48, Richard W.M. Jones wrote: > > > > Fedora 36, plocate-1.1.15-3.fc36.x86_64, systemd-250.8-1.fc36.x86_64 > > > > /usr/lib/systemd/system/plocate-updatedb.service has > > ConditionACPower=true because they don't want updatedb to run > > when on a laptop battery. > > > > Now, my machine is an Intel NUC which has an Intel mobile chipset but > > is very definitely not a laptop. It doesn't have a battery and always > > runs off AC power. > > > > But ... > > > > $ sudo systemctl status plocate-updatedb.service |& cat > > ○ plocate-updatedb.service - Update the plocate database > > Loaded: loaded (/usr/lib/systemd/system/plocate-updatedb.service; > > static) > > Active: inactive (dead) > > TriggeredBy: ● plocate-updatedb.timer > >Condition: start condition failed at Fri 2022-08-05 10:29:57 BST; 5min > > ago > > └─ ConditionACPower=true was not met > > > > Aug 03 14:59:37 dev5 systemd[1]: plocate-updatedb.service - Update the > > plocate database was skipped because of a failed condition check > > (ConditionACPower=true). > > Aug 04 09:29:21 dev5 systemd[1]: plocate-updatedb.service - Update the > > plocate database was skipped because of a failed condition check > > (ConditionACPower=true). > > Aug 05 10:29:35 dev5 systemd[1]: plocate-updatedb.service - Update the > > plocate database was skipped because of a failed condition check > > (ConditionACPower=true). > > Aug 05 10:29:57 dev5 systemd[1]: plocate-updatedb.service - Update the > > plocate database was skipped because of a failed condition check > > (ConditionACPower=true). > > > > Looking at systemd sources it seems as if ConditionACPower is checked > > here: > > > > > > https://github.com/systemd/systemd/blob/14e7bc2e77d2699498a1f74d7e4f905f11eca335/src/shared/udev-util.c#L662 > > > > It's a bit hard to follow what the code is doing, but I think it's > > looking in /sys for power_supply devices. This hardware has two, both > > with type == USB. (I believe these are the two USB ports on the front > > panel that can provide power to other devices, they cannot power the > > machine itself.) > > > > $ ll /sys/devices/platform/USBC000:00/power_supply > > total 0 > > drwxr-xr-x. 5 root root 0 Aug 3 09:00 ucsi-source-psy-USBC000:001 > > drwxr-xr-x. 5 root root 0 Aug 3 09:00 ucsi-source-psy-USBC000:002 > > $ cat /sys/devices/platform/USBC000:00/power_supply/*/type > > USB > > USB > > > > $ cat > > /sys/devices/platform/USBC000\:00/power_supply/ucsi-source-psy-USBC000\:00*/device/typec/port*/power_role > > > > [sink] > > [sink] > > [sink] > > [sink] > > > > $ cat > > /sys/devices/platform/USBC000\:00/power_supply/ucsi-source-psy-USBC000\:00*/online > > 0 > > 0 > > > > Anyway, I think this is a systemd bug, right? > > That code has lots of debug logs. Try running systemd with log level debug > and see which of those logs is printed. Good idea ... # systemd-analyze set-log-level debug # systemctl start plocate-updatedb.service # journalctl The relevant section is attached in full. It seems as if the code only finds the USB ports, they are all in "sink" mode, it doesn't find any other power_supply devices so it assumes battery? There seem to be at least two things wrong here - the USB ports are not "sinks" and there are no other power supply devices. I think this is a systemd bug. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org Aug 05 12:10:14 dev5 systemd[1]: Bus private-bus-connection: changing state UNSET → OPENING Aug 05 12:10:14 dev5 systemd[1]: sd-bus: starting bus private-bus-connection on fds 27/27 (socket:[382559], socket:[382559])... Aug 05 12:10:14 dev5 systemd[1]: Bus private-bus-connection: changing state OPENING → AUTHENTICATING Aug 05 12:10:14 dev5 systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1 iface=org.freedesktop.systemd1.Manager Aug 05 12:10:14 dev5 systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/job iface=org.freedesktop.systemd1.Job Aug 05 12:10:14 dev5 systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Unit Aug 05 12:10:14 dev5 systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Automount Aug 05 12:10:14 dev5 systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Device Aug 05 12:10:14 dev5 systemd[1]: Registering bus object implementation for path=/org/freedesktop/systemd1/unit iface=org.freedesktop.systemd1.Mount Aug 05 12:10:14 dev5 systemd[1]: R
Re: systemd service fails to run with "ConditionACPower=true was not met"
On Fri, Aug 05, 2022 at 12:16:46PM +0100, Richard W.M. Jones wrote: > I think this is a systemd bug. It seems like the source/sink check was added recently to fix: https://github.com/systemd/systemd/issues/21988 but that the fix is either wrong or incomplete. Here's another interesting related bug: https://github.com/systemd/systemd/issues/20964 I have filed a new bug for this: https://github.com/systemd/systemd/issues/24214 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
wireplumber running at 98% cpu
What is this and why is it eating my cpu? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
Join the conversation? https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/152 --- Best regards, Alex --- Original Message --- On Friday, August 5th, 2022 at 16:18, Robert Moskowitz wrote: > What is this and why is it eating my cpu? > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
I just checked dnf update, and I am current on it. Should I just kill it so it resets? On 8/5/22 10:20, Alex Gurenko via users wrote: Join the conversation? https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/152 --- Best regards, Alex --- Original Message --- On Friday, August 5th, 2022 at 16:18, Robert Moskowitz wrote: What is this and why is it eating my cpu? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
I am running F35 with Xfce. I just noticed my audio icon on the system tray 'vibrating'. I clicked on it and two things: It no longer shows my microphone setting. Speaker volume is jumping all over the place. ? On 8/5/22 10:24, Robert Moskowitz wrote: I just checked dnf update, and I am current on it. Should I just kill it so it resets? On 8/5/22 10:20, Alex Gurenko via users wrote: Join the conversation? https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/152 --- Best regards, Alex --- Original Message --- On Friday, August 5th, 2022 at 16:18, Robert Moskowitz wrote: What is this and why is it eating my cpu? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
Now I see panel-8-pulseau and pipewire-pulse each eating 40% (this is a quad cpu system). Kill them all? Like the Queen of Hearts? On 8/5/22 10:37, Robert Moskowitz wrote: I am running F35 with Xfce. I just noticed my audio icon on the system tray 'vibrating'. I clicked on it and two things: It no longer shows my microphone setting. Speaker volume is jumping all over the place. ? On 8/5/22 10:24, Robert Moskowitz wrote: I just checked dnf update, and I am current on it. Should I just kill it so it resets? On 8/5/22 10:20, Alex Gurenko via users wrote: Join the conversation? https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/152 --- Best regards, Alex --- Original Message --- On Friday, August 5th, 2022 at 16:18, Robert Moskowitz wrote: What is this and why is it eating my cpu? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: systemd service fails to run with "ConditionACPower=true was not met"
> On 5 Aug 2022, at 12:27, Richard W.M. Jones wrote: > > On Fri, Aug 05, 2022 at 12:16:46PM +0100, Richard W.M. Jones wrote: >> I think this is a systemd bug. > > It seems like the source/sink check was added recently to fix: > > https://github.com/systemd/systemd/issues/21988 > > but that the fix is either wrong or incomplete. > > Here's another interesting related bug: > > https://github.com/systemd/systemd/issues/20964 > > I have filed a new bug for this: > > https://github.com/systemd/systemd/issues/24214 > Sounds like it’s worth taking this to the systemd list. I think you have two questions: Why does the code no power surprise means battery and not mains power? Why is the the usb code getting the usb direction wrong? Barry > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > libguestfs lets you edit virtual machines. Supports shell scripting, > bindings from many languages. http://libguestfs.org > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
> On 5 Aug 2022, at 15:25, Robert Moskowitz wrote: > > I just checked dnf update, and I am current on it. > > Should I just kill it so it resets? Something like (unchecked) systemctl -user stop pipewire Barry > >> On 8/5/22 10:20, Alex Gurenko via users wrote: >> Join the conversation? >> >> https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/152 >> >> --- >> Best regards, Alex >> >> >> --- Original Message --- >> On Friday, August 5th, 2022 at 16:18, Robert Moskowitz >> wrote: >> >> >>> What is this and why is it eating my cpu? >>> ___ >>> users mailing list -- users@lists.fedoraproject.org >>> To unsubscribe send an email to users-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: >>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org >>> Do not reply to spam, report it: >>> https://pagure.io/fedora-infrastructure/new_issue >> ___ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
On 8/5/22 11:23, Barry wrote: On 5 Aug 2022, at 15:25, Robert Moskowitz wrote: I just checked dnf update, and I am current on it. Should I just kill it so it resets? Something like (unchecked) systemctl -user stop pipewire --user And it brought back my microphone! thanks Barry On 8/5/22 10:20, Alex Gurenko via users wrote: Join the conversation? https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/152 --- Best regards, Alex --- Original Message --- On Friday, August 5th, 2022 at 16:18, Robert Moskowitz wrote: What is this and why is it eating my cpu? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Switchdesk functionality has disappeared
On Tue, Aug 2, 2022 at 11:57 PM Robert McBroom wrote: > Fedora 36 booting mode 3 to a command line boot, the switchdesk entry > Plasma doesn't do anything > Looks like a bug fixed via https://bodhi.fedoraproject.org/updates/FEDORA-2022-42f46048de (refer to bugs tab) Rahul ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: New error message when selecting Windows Boot Loader from the GRUB menu
On 8/5/22 02:15, Scott Beamer wrote: On 8/4/22 7:28 PM, Chris Murphy wrote: On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote: Greetings, After a recent Fedora 36 update, I'm getting an error message when selecting "Windows Boot Manager" from the GRUB menu. Instead of booting like it had previously, it gives me an almost blank screen with the following text in the upper left: /EndEntire And all I can do at that point is shut down and restart my computer, go to it's boot menu, and sekect Windows Boot Manager, in order to boot into Windows. I've been dual-booting Fedora 36 and Windows for weeks prior to this one without issue. What version? Current is 2.06-45.fc36 and there are a few complaints. That version. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ffd58c713#comment-2667330 https://bugzilla.redhat.com/show_bug.cgi?id=2115202 I commented on the bug. Thanks for the link. dnf downgrade will get you the -29 version which is a ways back, but also easy and will get you working. But to avoid it getting updated and breaking again in the near future you'll need to add an exclude in the dnf.conf (man dnf.conf) for "grub2-*" Set a reminder though, you'll eventually want to update it and it might even prevent a system upgrade from getting a new version (or even failing, I'm not really sure). Thanks. I went with that and added the exclude ti dnf.conf An alternative is to: rpm -qa | grep grub2 That'll get you a list of all the grub2 packages you'lll need to download from here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1977609 That's the -42 version which should work. Then you have the packages locally and you can just put them in a directory and if you do an update that steps on this version again, you can just cd to that dir and do "dnf downgrade *rpm" and it'll use the local rpm files. I'm too lazy for that ish. I'll just hold on to the -29 version for a while and follow up in a week. If you have a Fedora account or RGBZ account you can add yourself to the bug. I'm too lazy for that ish. I'll just hold on to the -29 version for a while and follow up in a week. I do and I did. Thanks for your help. Much appreciated! :) Scott For me the enter key makes the process continue to the windows boot ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: wireplumber running at 98% cpu
On Fri, 2022-08-05 at 11:41 -0400, Robert Moskowitz wrote: > And it brought back my microphone! There's a roadie joke in there somewhere... -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
gstreamer pipeline directly using pipewire device
I am hoping for some guidance on if I should be using pipewiresrc (vs alsasrc) in my gstreamer pipeline. From my understanding we fully switched over to PipeWire for managing audio devices in Fedora. To me, this means all "non-pipewire" interfaces (PulseAudio, ALSA, OSS, etc) are now using compatibility layers to plumb the audio to PipeWire. I presume that the "most correct" pipeline source object type to use is pipewiresrc. If the answer is to use pipewiresrc, how can I inspect the pipewire "devices" seen by gstreamer? `gst-device-monitor-1.0` only shows the expected PipeWire devices via the ALSA api. The upstream documentation indicates the devices should be listed as of 2 years ago https://github.com/PipeWire/pipewire/blob/master/README.md#running-gstreamer-applications ➜ gst-device-monitor-1.0 | grep pipewire ➜ gst-device-monitor-1.0 | grep pw ➜ gst-launch-1.0 -v pipewiresrc ! audioresample ! autoaudiosink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: pipewireclock0 Interrupt: Stopping pipeline ... Execution ended after 0:00:05.618247799 Setting pipeline to NULL ... Freeing pipeline ... ➜ gst-launch-1.0 -v alsasrc ! audioresample ! autoaudiosink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstAudioSrcClock Interrupt: Stopping pipeline ... Execution ended after 0:00:06.362230774 Setting pipeline to NULL ... Freeing pipeline ... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
