Hi *, is there any documentation on how to configure rtkit-daemon for openSUSE? I found a few hints regarding pipewire, but they seem to be at least in part inconsistent with each other. And I couldn't find any more general doc. Especially I have the following questions: Do I have to put a user in the rtkit group, if he wants to run a program like Citrix, which requests realtime capabilites? Or do I have to create a config file in /usr/etc/security/limits.d/? Is so, what should it contain? Do I have to configure something else? TIA. Bye. Michael.
Hello, In the Message; Subject : rtkit-daemon Message-ID : <5671182.DvuYhMxLoT@transformer> Date & Time: Sun, 23 Apr 2023 13:02:13 +0200 mh@mike.franken.de has written:
Hi *,
is there any documentation on how to configure rtkit-daemon for openSUSE?
I don't know it. [...]
Especially I have the following questions:
Do I have to put a user in the rtkit group, if he wants to run a program like Citrix, which requests realtime capabilites?
Yes, add your own user to rtkit group. This configuration enables pipewire daemon priorities to change in real time.
Or do I have to create a config file in /usr/etc/security/limits.d/? Is so, what should it contain?
This is not necessary.
Do I have to configure something else?
Right. 0. Confirm installatin by $ pactl info Ex. this is mine; Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 77 Tile Size: 65472 User Name: masaru Host Name: localhost Server Name: PulseAudio (on PipeWire 0.3.70) Server Version: 15.0.0 [...] Cookie: fb04:87e4 Before you proceed, you should do the following as preparation; 1. if possible, uninstall the wireplumber and install pipewire-media-session The reason is that pipewire-media-session is obviously better sounding than wireplumber. 3. I assume this is done when pipewire is installed, but I'll mention it here. $ sudo cp /usr/share/doc/pipewire/examples/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/ 4. $ mkdir ~/.config/pipewire and. $ mkdir ~/.config/pipewire/media-session.d 5. 5-1. Change alsa API to pipewire-alsa $ touch ~/.config/pipewire/media-session.d/with-alsa 5-2. Enable bluez5 module $ touch ~/.config/pipewire/media-session.d/with-pulseaudio 6. for the pipewire's settings 6-1. $ cp /usr/share/pipewire/pipewire-pulse.conf ~/.config/pipewire $ cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire 6-2. edit conf files 6-2-1. for pipewire-pulse.conf [...] stream.properties = { #node.latency = 1024/48000 #node.autoconnect = true #resample.quality = 4 #channelmix.normalize = false [...] to [...] stream.properties = { #node.latency = 1024/48000 #node.autoconnect = true resample.quality = 15 #channelmix.normalize = false [...] where 15 is maximum number, which means best sound 6-2-2. for pipewire.conf ## Properties for the DSP configuration. #default.clock.rate = 48000 #default.clock.allowed-rates = [ 48000 ] #default.clock.quantum = 1024 #default.clock.min-quantum = 32 #default.clock.max-quantum = 2048 #default.clock.quantum-limit = 8192 #default.video.width = 640 #default.video.height = 480 #default.video.rate.num = 25 #default.video.rate.denom = 1 # #settings.check-quantum = false #settings.check-rate = false # # These overrides are only applied when running in a vm. vm.overrides = { default.clock.min-quantum = 1024 } to (in my case with USB-DAC) ## Properties for the DSP configuration. default.clock.rate = 384000 default.clock.allowed-rates = [ 44100 48000 96000 192000 352800 384000 ] default.clock.quantum = 1024 default.clock.min-quantum = 32 default.clock.max-quantum = 2048 default.clock.quantum-limit = 8192 default.video.width = 800 default.video.height = 600 #default.clock.rate = 48000 #default.clock.allowed-rates = [ 48000 ] #default.clock.quantum = 1024 #default.clock.min-quantum = 32 #default.clock.max-quantum = 2048 #default.clock.quantum-limit = 8192 #default.video.width = 640 #default.video.height = 480 #default.video.rate.num = 25 #default.video.rate.denom = 1 # #settings.check-quantum = false #settings.check-rate = false # # These overrides are only applied when running in a vm. vm.overrides = { default.clock.min-quantum = 1024 } Generally, when pipewire is installed, the sampling rate is 48KHz. To know the operating status; $ cat /proc/asound/HDAMP1/pcm0p/sub0/hw_params In my case: access: MMAP_INTERLEAVED format: S32_LE subformat: STD channels: 2 rate: 384000 (384000/1) period_size: 256 buffer_size: 32768 I am enjoying musics with mpd+cantata in this environment. If you use mpd, please let us know again. Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
Hi, thx for the detailed description, but probably I couldn't make clear, where my problem really is. Its not about pipewire - I only wanted to say, that for pipewire I found the only snippets of documentation for rtkit. Instead I wanted to know, how to configure rtkit for other applications like Citrix Workspace. Bye. Michael. On Sonntag, 23. April 2023 15:30:06 CEST Masaru Nomiya wrote:
Hello,
In the Message;
Subject : rtkit-daemon Message-ID : <5671182.DvuYhMxLoT@transformer> Date & Time: Sun, 23 Apr 2023 13:02:13 +0200
mh@mike.franken.de has written:
Hi *,
is there any documentation on how to configure rtkit-daemon for openSUSE?
I don't know it.
[...]
Especially I have the following questions:
Do I have to put a user in the rtkit group, if he wants to run a program like Citrix, which requests realtime capabilites?
Yes, add your own user to rtkit group.
This configuration enables pipewire daemon priorities to change in real time.
Or do I have to create a config file in /usr/etc/security/limits.d/? Is so, what should it contain?
This is not necessary.
Do I have to configure something else?
Right.
0. Confirm installatin by
$ pactl info
Ex. this is mine;
Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 77 Tile Size: 65472 User Name: masaru Host Name: localhost Server Name: PulseAudio (on PipeWire 0.3.70) Server Version: 15.0.0 [...] Cookie: fb04:87e4
Before you proceed, you should do the following as preparation;
1. if possible, uninstall the wireplumber and install pipewire-media-session
The reason is that pipewire-media-session is obviously better sounding than wireplumber.
3. I assume this is done when pipewire is installed, but I'll mention it here.
$ sudo cp /usr/share/doc/pipewire/examples/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/
4. $ mkdir ~/.config/pipewire
and.
$ mkdir ~/.config/pipewire/media-session.d
5.
5-1. Change alsa API to pipewire-alsa
$ touch ~/.config/pipewire/media-session.d/with-alsa
5-2. Enable bluez5 module
$ touch ~/.config/pipewire/media-session.d/with-pulseaudio
6. for the pipewire's settings
6-1. $ cp /usr/share/pipewire/pipewire-pulse.conf ~/.config/pipewire
$ cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire
6-2. edit conf files
6-2-1. for pipewire-pulse.conf
[...] stream.properties = { #node.latency = 1024/48000 #node.autoconnect = true #resample.quality = 4 #channelmix.normalize = false [...]
to
[...] stream.properties = { #node.latency = 1024/48000 #node.autoconnect = true resample.quality = 15 #channelmix.normalize = false [...]
where 15 is maximum number, which means best sound
6-2-2. for pipewire.conf
## Properties for the DSP configuration. #default.clock.rate = 48000 #default.clock.allowed-rates = [ 48000 ] #default.clock.quantum = 1024 #default.clock.min-quantum = 32 #default.clock.max-quantum = 2048 #default.clock.quantum-limit = 8192 #default.video.width = 640 #default.video.height = 480 #default.video.rate.num = 25 #default.video.rate.denom = 1 # #settings.check-quantum = false #settings.check-rate = false # # These overrides are only applied when running in a vm. vm.overrides = { default.clock.min-quantum = 1024 }
to (in my case with USB-DAC)
## Properties for the DSP configuration. default.clock.rate = 384000 default.clock.allowed-rates = [ 44100 48000 96000 192000 352800 384000 ] default.clock.quantum = 1024 default.clock.min-quantum = 32 default.clock.max-quantum = 2048 default.clock.quantum-limit = 8192 default.video.width = 800 default.video.height = 600 #default.clock.rate = 48000 #default.clock.allowed-rates = [ 48000 ] #default.clock.quantum = 1024 #default.clock.min-quantum = 32 #default.clock.max-quantum = 2048 #default.clock.quantum-limit = 8192 #default.video.width = 640 #default.video.height = 480 #default.video.rate.num = 25 #default.video.rate.denom = 1 # #settings.check-quantum = false #settings.check-rate = false # # These overrides are only applied when running in a vm. vm.overrides = { default.clock.min-quantum = 1024 }
Generally, when pipewire is installed, the sampling rate is 48KHz.
To know the operating status;
$ cat /proc/asound/HDAMP1/pcm0p/sub0/hw_params
In my case:
access: MMAP_INTERLEAVED format: S32_LE subformat: STD channels: 2 rate: 384000 (384000/1) period_size: 256 buffer_size: 32768
I am enjoying musics with mpd+cantata in this environment.
If you use mpd, please let us know again.
Regards & Good Night.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
On 23.04.2023 16:56, mh@mike.franken.de wrote:
Hi,
thx for the detailed description, but probably I couldn't make clear, where my problem really is. Its not about pipewire - I only wanted to say, that for pipewire I found the only snippets of documentation for rtkit. Instead I wanted to know, how to configure rtkit for other applications like Citrix Workspace.
You cannot "configure rtkit for other applications". rtkit-daemon listens on requests over D-Bus and fulfills (or denies) these requests. If your application does not talk to rtkit-daemon, there is nothing you can do from the rtkit side. If your application does request to become real time but request is denied, we could look why.
Bye. Michael.
On Sonntag, 23. April 2023 15:30:06 CEST Masaru Nomiya wrote:
Hello,
In the Message;
Subject : rtkit-daemon Message-ID : <5671182.DvuYhMxLoT@transformer> Date & Time: Sun, 23 Apr 2023 13:02:13 +0200
mh@mike.franken.de has written:
Hi *,
is there any documentation on how to configure rtkit-daemon for openSUSE?
I don't know it.
[...]
Especially I have the following questions:
Do I have to put a user in the rtkit group, if he wants to run a program like Citrix, which requests realtime capabilites?
Yes, add your own user to rtkit group.
This configuration enables pipewire daemon priorities to change in real time.
Or do I have to create a config file in /usr/etc/security/limits.d/? Is so, what should it contain?
This is not necessary.
Do I have to configure something else?
Right.
0. Confirm installatin by
$ pactl info
Ex. this is mine;
Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 77 Tile Size: 65472 User Name: masaru Host Name: localhost Server Name: PulseAudio (on PipeWire 0.3.70) Server Version: 15.0.0 [...] Cookie: fb04:87e4
Before you proceed, you should do the following as preparation;
1. if possible, uninstall the wireplumber and install pipewire-media-session
The reason is that pipewire-media-session is obviously better sounding than wireplumber.
3. I assume this is done when pipewire is installed, but I'll mention it here.
$ sudo cp /usr/share/doc/pipewire/examples/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/
4. $ mkdir ~/.config/pipewire
and.
$ mkdir ~/.config/pipewire/media-session.d
5.
5-1. Change alsa API to pipewire-alsa
$ touch ~/.config/pipewire/media-session.d/with-alsa
5-2. Enable bluez5 module
$ touch ~/.config/pipewire/media-session.d/with-pulseaudio
6. for the pipewire's settings
6-1. $ cp /usr/share/pipewire/pipewire-pulse.conf ~/.config/pipewire
$ cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire
6-2. edit conf files
6-2-1. for pipewire-pulse.conf
[...] stream.properties = { #node.latency = 1024/48000 #node.autoconnect = true #resample.quality = 4 #channelmix.normalize = false [...]
to
[...] stream.properties = { #node.latency = 1024/48000 #node.autoconnect = true resample.quality = 15 #channelmix.normalize = false [...]
where 15 is maximum number, which means best sound
6-2-2. for pipewire.conf
## Properties for the DSP configuration. #default.clock.rate = 48000 #default.clock.allowed-rates = [ 48000 ] #default.clock.quantum = 1024 #default.clock.min-quantum = 32 #default.clock.max-quantum = 2048 #default.clock.quantum-limit = 8192 #default.video.width = 640 #default.video.height = 480 #default.video.rate.num = 25 #default.video.rate.denom = 1 # #settings.check-quantum = false #settings.check-rate = false # # These overrides are only applied when running in a vm. vm.overrides = { default.clock.min-quantum = 1024 }
to (in my case with USB-DAC)
## Properties for the DSP configuration. default.clock.rate = 384000 default.clock.allowed-rates = [ 44100 48000 96000 192000 352800 384000 ] default.clock.quantum = 1024 default.clock.min-quantum = 32 default.clock.max-quantum = 2048 default.clock.quantum-limit = 8192 default.video.width = 800 default.video.height = 600 #default.clock.rate = 48000 #default.clock.allowed-rates = [ 48000 ] #default.clock.quantum = 1024 #default.clock.min-quantum = 32 #default.clock.max-quantum = 2048 #default.clock.quantum-limit = 8192 #default.video.width = 640 #default.video.height = 480 #default.video.rate.num = 25 #default.video.rate.denom = 1 # #settings.check-quantum = false #settings.check-rate = false # # These overrides are only applied when running in a vm. vm.overrides = { default.clock.min-quantum = 1024 }
Generally, when pipewire is installed, the sampling rate is 48KHz.
To know the operating status;
$ cat /proc/asound/HDAMP1/pcm0p/sub0/hw_params
In my case:
access: MMAP_INTERLEAVED format: S32_LE subformat: STD channels: 2 rate: 384000 (384000/1) period_size: 256 buffer_size: 32768
I am enjoying musics with mpd+cantata in this environment.
If you use mpd, please let us know again.
Regards & Good Night.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
On Sonntag, 23. April 2023 17:11:38 CEST Andrei Borzenkov wrote:
On 23.04.2023 16:56, mh@mike.franken.de wrote:
Hi,
thx for the detailed description, but probably I couldn't make clear, where my problem really is. Its not about pipewire - I only wanted to say, that for pipewire I found the only snippets of documentation for rtkit. Instead I wanted to know, how to configure rtkit for other applications like Citrix Workspace.
You cannot "configure rtkit for other applications". rtkit-daemon listens on requests over D-Bus and fulfills (or denies) these requests. If your application does not talk to rtkit-daemon, there is nothing you can do from the rtkit side.
the application is using rtkit according to the journal entries. I just wanted to know, if *I* can configure something to optimize this usage.
If your application does request to become real time but request is denied, we could look why.
This seems to indicate, that at least something is working: tkit-daemon[5215]: Successfully made thread 17006 of process 17002 owned by '10000' RT at priority 5. This is the only warning I get: "rtkit-daemon[5215]: Warning: Reached burst limit for user '10000', denying request." Thx and bye. Michael.
On 2023-04-23 17:20, mh@mike.franken.de wrote:
the application is using rtkit according to the journal entries. I just wanted to know, if*I* can configure something to optimize this usage.
The closest thing to a manual page is probably this. Look under DAEMON: /usr/share/doc/packages/rtkit/README -- /bengan
On Sonntag, 23. April 2023 17:26:48 CEST Bengt Gördén wrote:
On 2023-04-23 17:20, mh@mike.franken.de wrote:
the application is using rtkit according to the journal entries. I just wanted to know, if*I* can configure something to optimize this usage. The closest thing to a manual page is probably this. Look under DAEMON: /usr/share/doc/packages/rtkit/README
Thx. I already read that, but it doesn't give any clue, how to do this *the right way* on an openSUSE system. Edit the service file directly, modify/create a config file somewhere, ... Bye. Michael.
On 23.04.2023 18:20, mh@mike.franken.de wrote:
On Sonntag, 23. April 2023 17:11:38 CEST Andrei Borzenkov wrote:
On 23.04.2023 16:56, mh@mike.franken.de wrote:
Hi,
thx for the detailed description, but probably I couldn't make clear, where my problem really is. Its not about pipewire - I only wanted to say, that for pipewire I found the only snippets of documentation for rtkit. Instead I wanted to know, how to configure rtkit for other applications like Citrix Workspace.
You cannot "configure rtkit for other applications". rtkit-daemon listens on requests over D-Bus and fulfills (or denies) these requests. If your application does not talk to rtkit-daemon, there is nothing you can do from the rtkit side.
the application is using rtkit according to the journal entries. I just wanted to know, if *I* can configure something to optimize this usage.
You can set rtkit-daemon options that are described in README and you can change real time priority and/or allowed time before process get preempted via limits.conf for users and system.conf/service unit for services.
If your application does request to become real time but request is denied, we could look why.
This seems to indicate, that at least something is working:
tkit-daemon[5215]: Successfully made thread 17006 of process 17002 owned by '10000' RT at priority 5.
And process 17002 is your Citrix Workspace?
This is the only warning I get:
"rtkit-daemon[5215]: Warning: Reached burst limit for user '10000', denying request."
That can be changed by rtkit-daemon options (--actions-burst-sec/--actions-per-burts-max). Although the first question should probably be, why there are so many requests (default is 25 actions in 20 seconds).
Hi, On Sonntag, 23. April 2023 17:47:39 CEST Andrei Borzenkov wrote:
the application is using rtkit according to the journal entries. I just wanted to know, if *I* can configure something to optimize this usage. You can set rtkit-daemon options that are described in README and you can change real time priority and/or allowed time before process get
On 23.04.2023 18:20, mh@mike.franken.de wrote: [...] preempted via limits.conf for users and system.conf/service unit for services.
If your application does request to become real time but request is denied, we could look why.
This seems to indicate, that at least something is working:
tkit-daemon[5215]: Successfully made thread 17006 of process 17002 owned by '10000' RT at priority 5.
And process 17002 is your Citrix Workspace?
jepp.
This is the only warning I get:
"rtkit-daemon[5215]: Warning: Reached burst limit for user '10000', denying request."
That can be changed by rtkit-daemon options (--actions-burst-sec/--actions-per-burts-max). Although the first question should probably be, why there are so many requests (default is 25 actions in 20 seconds).
Do I have to edit the service file or is there any other place to modify this? This was one of the things, my original question was about. Not sure, what Citrix is doing here, but I guess it is the HDX engine: https://www.citrix.com/solutions/vdi-and-daas/hdx/what-is-hdx.html It is responsible for example for audio and video sessions in higher quality. Bye. Michael.
On 23.04.2023 19:24, mh@mike.franken.de wrote:
Hi,
On Sonntag, 23. April 2023 17:47:39 CEST Andrei Borzenkov wrote:
the application is using rtkit according to the journal entries. I just wanted to know, if *I* can configure something to optimize this usage. You can set rtkit-daemon options that are described in README and you can change real time priority and/or allowed time before process get
On 23.04.2023 18:20, mh@mike.franken.de wrote: [...] preempted via limits.conf for users and system.conf/service unit for services.
If your application does request to become real time but request is denied, we could look why.
This seems to indicate, that at least something is working:
tkit-daemon[5215]: Successfully made thread 17006 of process 17002 owned by '10000' RT at priority 5.
And process 17002 is your Citrix Workspace?
jepp.
This is the only warning I get:
"rtkit-daemon[5215]: Warning: Reached burst limit for user '10000', denying request."
That can be changed by rtkit-daemon options (--actions-burst-sec/--actions-per-burts-max). Although the first question should probably be, why there are so many requests (default is 25 actions in 20 seconds).
Do I have to edit the service file or is there any other place to modify this? This was one of the things, my original question was about.
You have to edit unit definition.
Not sure, what Citrix is doing here, but I guess it is the HDX engine: https://www.citrix.com/solutions/vdi-and-daas/hdx/what-is-hdx.html It is responsible for example for audio and video sessions in higher quality.
Bye. Michael.
On Sonntag, 23. April 2023 18:55:30 CEST Andrei Borzenkov wrote:
On 23.04.2023 19:24, mh@mike.franken.de wrote: [...]
That can be changed by rtkit-daemon options (--actions-burst-sec/--actions-per-burts-max). Although the first question should probably be, why there are so many requests (default is 25 actions in 20 seconds).
Do I have to edit the service file or is there any other place to modify this? This was one of the things, my original question was about.
You have to edit unit definition.
With --actions-per-burst-max=40 the burst limit warnings don't show again - for the moment. Thx. Bye. Michael.
Hello, In the Message; Subject : Re: rtkit-daemon Message-ID : <10264808.nUPlyArG6x@transformer> Date & Time: Sun, 23 Apr 2023 19:56:14 +0200 mh@mike.franken.de has written: [...]
You have to edit unit definition.
With --actions-per-burst-max=40 the burst limit warnings don't show again - for the moment.
Sorry for Michael, and Thanks fo Andrei. If someone are referring to the settings I wrote, don't forget to reboot after setting up (I think logout/login is fine, but just in case). After that, do the following: $ systemctl --user daemon-reload $ systemctl --user start pipewire pipewire-pulse pipewire-media-session I forgot to mention that. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "It should never be said that it is OK to ignore the theoretical as long as it becomes a tool." -- T. Mori (The original is in Japanese) --
On Montag, 24. April 2023 03:18:00 CEST Masaru Nomiya wrote:
Hello,
[...]
If someone are referring to the settings I wrote, don't forget to reboot after setting up (I think logout/login is fine, but just in case). After that, do the following:
$ systemctl --user daemon-reload $ systemctl --user start pipewire pipewire-pulse pipewire-media-session
or just edit the service file with systemctl edit [--full] rtkit-daemon.service and restart the service systemctl restart rtkit-daemon.service Login out isn't sufficiant in any case.
I forgot to mention that.
Regards.
Bye. Michael.
Hello, In the Message; Subject : Re: rtkit-daemon Message-ID : <12195061.O9o76ZdvQC@transformer> Date & Time: Mon, 24 Apr 2023 10:23:51 +0200 mh@mike.franken.de has written:
On Montag, 24. April 2023 03:18:00 CEST Masaru Nomiya wrote:
Hello,
[...]
If someone are referring to the settings I wrote, don't forget to reboot after setting up (I think logout/login is fine, but just in case). After that, do the following:
$ systemctl --user daemon-reload $ systemctl --user start pipewire pipewire-pulse pipewire-media-session
or just edit the service file with systemctl edit [--full] rtkit-daemon.service and restart the service systemctl restart rtkit-daemon.service
Login out isn't sufficiant in any case.
That's true, but doesn't it put on the threshold? BTW. I think you are the one I asked before if you are a musician, no? Regards & good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education." -- Washington Post --
On Montag, 24. April 2023 13:13:55 CEST Masaru Nomiya wrote: [...]
or just edit the service file with systemctl edit [--full] rtkit-daemon.service and restart the service systemctl restart rtkit-daemon.service
Login out isn't sufficiant in any case.
That's true, but doesn't it put on the threshold?
not sure, what you mean, sry.
BTW.
I think you are the one I asked before if you are a musician, no?
If so, I don't remember, but for sure I am not a musician :)
Regards & good Night.
Bye. Michael.
participants (4)
-
Andrei Borzenkov -
Bengt Gördén -
Masaru Nomiya -
mh＠mike.franken.de