Hi, Having run tracer after a system update how do I determine what it is referring to with the following messages:
You should restart: * These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensions
Additionally, there are: - 1 processes requiring restart of your session (i.e. Logging out & Logging in again)
regards, Steve
On Mon, 17 Mar 2025 at 21:54, Stephen Morris steve.morris.au@gmail.com wrote:
Having run tracer after a system update how do I determine what it isreferring to with the following messages:
You should restart:
- These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensions
Does:
# tracer --helpers
... make things clearer? Or, for example
# tracer -s 'Privileged Cont'
Always check the --help for a command and/or its man page.
On 18/3/25 09:20, Will McDonald wrote:
On Mon, 17 Mar 2025 at 21:54, Stephen Morris steve.morris.au@gmail.com wrote:
Having run tracer after a system update how do I determine what it is referring to with the following messages: You should restart: * These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensionsDoes:
# tracer --helpers
... make things clearer? Or, for example
# tracer -s 'Privileged Cont'
Always check the --help for a command and/or its man page.
Issuing tracer -s 'Utility Process' now tells me that application Utility Process is not running, so how do I determine what it was?
Also having just done an update now tracer tells me that goa-daemon and plasmashell should be manually restarted. Tracer -s goa-daemon tells me it is package gnome-online-accounts, and from its name I'm assuming it can be restarted via systemctl, but as I'm using KDE I can potentially ignore the restart suggestion, would that be correct? With the suggestion to manually restart plasmashell how do I do that without shutting the system down or is the KDE environment not running under Plasmashell?
regards, Steve
On Wed, 2025-03-19 at 09:36 +1100, Stephen Morris wrote:
On 18/3/25 09:20, Will McDonald wrote:
On Mon, 17 Mar 2025 at 21:54, Stephen Morris steve.morris.au@gmail.com wrote:
Having run tracer after a system update how do I determine what it is referring to with the following messages: You should restart: * These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensionsDoes:
# tracer --helpers
... make things clearer? Or, for example
# tracer -s 'Privileged Cont'
Always check the --help for a command and/or its man page.
Issuing tracer -s 'Utility Process' now tells me that application Utility Process is not running, so how do I determine what it was?
If it's not running, why does it matter? (almost certainly it's a worker process under Firefox)
Also having just done an update now tracer tells me that goa-daemon and plasmashell should be manually restarted. Tracer -s goa-daemon tells me it is package gnome-online-accounts, and from its name I'm assuming it can be restarted via systemctl, but as I'm using KDE I can potentially ignore the restart suggestion, would that be correct?
No, because you may be running some Gnome (or GTK) app under KDE, which is why tracer detected goa-daemon. However the man page for goa-daemon says that it starts automatically on demand, so there's no harm in just killing it, e.g., with pkill.
With the suggestion to manually restart plasmashell how do I do that without shutting the system down or is the KDE environment not running under Plasmashell?
I have a tiny script for that, thanks to Rex Dieter:
$ cat bin/replasma #!/bin/sh
# KDE list 06/01/2019 Rex Dieter rdieter@gmail.com
systemctl restart --user plasma-plasmashell $
poc
*From:* Patrick O'Callaghan pocallaghan@gmail.com
*Sent:* Wednesday, 19 March 2025 at 10:20 UTC+11
*To:* users@lists.fedoraproject.org
*Subject:* RE: Tracer Messages
On Wed, 2025-03-19 at 09:36 +1100, Stephen Morris wrote:
On 18/3/25 09:20, Will McDonald wrote:
On Mon, 17 Mar 2025 at 21:54, Stephen Morris steve.morris.au@gmail.com wrote:
Having run tracer after a system update how do I determine what it is referring to with the following messages: You should restart: * These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensionsDoes:
# tracer --helpers
... make things clearer? Or, for example
# tracer -s 'Privileged Cont'
Always check the --help for a command and/or its man page.
Issuing tracer -s 'Utility Process' now tells me that application Utility Process is not running, so how do I determine what it was?
If it's not running, why does it matter? (almost certainly it's a worker process under Firefox)
Also having just done an update now tracer tells me that goa-daemon and plasmashell should be manually restarted. Tracer -s goa-daemon tells me it is package gnome-online-accounts, and from its name I'm assuming it can be restarted via systemctl, but as I'm using KDE I can potentially ignore the restart suggestion, would that be correct?
No, because you may be running some Gnome (or GTK) app under KDE, which is why tracer detected goa-daemon. However the man page for goa-daemon says that it starts automatically on demand, so there's no harm in just killing it, e.g., with pkill.
With the suggestion to manually restart plasmashell how do I do that without shutting the system down or is the KDE environment not running under Plasmashell?
I have a tiny script for that, thanks to Rex Dieter:
$ cat bin/replasma #!/bin/sh # KDE list 06/01/2019 Rex Dieter<rdieter@gmail.com> systemctl restart --user plasma-plasmashell $poc
Thankyou for that script, but I've seen instructions for switching between DM's that specify to disable the existing DM before enabling the new DM, which when you do that the disabling of the existing DM displays a black screen that it never comes back from to be able to enable the new DM, hence would this restart do the same thing, or do you need to use ctrl-alt-F2 to switch to a command line interface, login and issue the restart from there, and then when you logout of that interface or use ctrl-alt-F1 the gui your switching to is the restarted gui?
regards, Steve
On Thu, 2025-03-20 at 08:55 +1100, Stephen Morris wrote:
*From:* Patrick O'Callaghan pocallaghan@gmail.com
*Sent:* Wednesday, 19 March 2025 at 10:20 UTC+11
*To:* users@lists.fedoraproject.org
*Subject:* RE: Tracer Messages
On Wed, 2025-03-19 at 09:36 +1100, Stephen Morris wrote:
On 18/3/25 09:20, Will McDonald wrote:
On Mon, 17 Mar 2025 at 21:54, Stephen Morris steve.morris.au@gmail.com wrote:
Having run tracer after a system update how do I determine what it is referring to with the following messages: You should restart: * These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensionsDoes:
# tracer --helpers
... make things clearer? Or, for example
# tracer -s 'Privileged Cont'
Always check the --help for a command and/or its man page.
Issuing tracer -s 'Utility Process' now tells me that application Utility Process is not running, so how do I determine what it was?
If it's not running, why does it matter? (almost certainly it's a worker process under Firefox)
Also having just done an update now tracer tells me that goa-daemon and plasmashell should be manually restarted. Tracer -s goa-daemon tells me it is package gnome-online-accounts, and from its name I'm assuming it can be restarted via systemctl, but as I'm using KDE I can potentially ignore the restart suggestion, would that be correct?
No, because you may be running some Gnome (or GTK) app under KDE, which is why tracer detected goa-daemon. However the man page for goa-daemon says that it starts automatically on demand, so there's no harm in just killing it, e.g., with pkill.
With the suggestion to manually restart plasmashell how do I do that without shutting the system down or is the KDE environment not running under Plasmashell?
I have a tiny script for that, thanks to Rex Dieter:
$ cat bin/replasma #!/bin/sh # KDE list 06/01/2019 Rex Dieter<rdieter@gmail.com> systemctl restart --user plasma-plasmashell $poc
Thankyou for that script, but I've seen instructions for switching between DM's that specify to disable the existing DM before enabling the new DM, which when you do that the disabling of the existing DM displays a black screen that it never comes back from to be able to enable the new DM, hence would this restart do the same thing, or do you need to use ctrl-alt-F2 to switch to a command line interface, login and issue the restart from there, and then when you logout of that interface or use ctrl-alt-F1 the gui your switching to is the restarted gui?
Don't confuse DM (Display Manager) with DE (Desktop Environment). The DM is the thing that presents the login GUI and then invokes a DE, which may be KDE, Gnome, Xfce etc. The preferred DM for KDE is SDDM, but it can invoke the Gnome DE if you like. Gnome normally uses GDM and the same applies in reverse. If switching between DMs then yes, you do need to log out and run a script, but there's normally no need. You can switch between DEs from the login screen.
Plasma is not the whole DE. You can restart it at any time without logging out if you have a working terminal emulator.
poc
*From:* Patrick O'Callaghan pocallaghan@gmail.com
*Sent:* Friday, 21 March 2025 at 01:50 UTC+11
*To:* users@lists.fedoraproject.org
*Subject:* RE: Tracer Messages
On Thu, 2025-03-20 at 08:55 +1100, Stephen Morris wrote:
*From:* Patrick O'Callaghanpocallaghan@gmail.com
*Sent:* Wednesday, 19 March 2025 at 10:20 UTC+11
*To:*users@lists.fedoraproject.org
*Subject:* RE: Tracer Messages
On Wed, 2025-03-19 at 09:36 +1100, Stephen Morris wrote:
On 18/3/25 09:20, Will McDonald wrote:
On Mon, 17 Mar 2025 at 21:54, Stephen Morris steve.morris.au@gmail.com wrote:
Having run tracer after a system update how do I determine what it is referring to with the following messages: You should restart: * These applications manually: DiscoverNotifier Isolated Web Co Privileged Cont RDD Process Socket Process Utility Process Web Content WebExtensionsDoes:
# tracer --helpers
... make things clearer? Or, for example
# tracer -s 'Privileged Cont'
Always check the --help for a command and/or its man page.
Issuing tracer -s 'Utility Process' now tells me that application Utility Process is not running, so how do I determine what it was?
If it's not running, why does it matter? (almost certainly it's a worker process under Firefox)
Also having just done an update now tracer tells me that goa-daemon and plasmashell should be manually restarted. Tracer -s goa-daemon tells me it is package gnome-online-accounts, and from its name I'm assuming it can be restarted via systemctl, but as I'm using KDE I can potentially ignore the restart suggestion, would that be correct?
No, because you may be running some Gnome (or GTK) app under KDE, which is why tracer detected goa-daemon. However the man page for goa-daemon says that it starts automatically on demand, so there's no harm in just killing it, e.g., with pkill.
With the suggestion to manually restart plasmashell how do I do that without shutting the system down or is the KDE environment not running under Plasmashell?
I have a tiny script for that, thanks to Rex Dieter:
$ cat bin/replasma #!/bin/sh # KDE list 06/01/2019 Rex Dieter<rdieter@gmail.com> systemctl restart --user plasma-plasmashell $poc
Thankyou for that script, but I've seen instructions for switching between DM's that specify to disable the existing DM before enabling the new DM, which when you do that the disabling of the existing DM displays a black screen that it never comes back from to be able to enable the new DM, hence would this restart do the same thing, or do you need to use ctrl-alt-F2 to switch to a command line interface, login and issue the restart from there, and then when you logout of that interface or use ctrl-alt-F1 the gui your switching to is the restarted gui?
Don't confuse DM (Display Manager) with DE (Desktop Environment). The DM is the thing that presents the login GUI and then invokes a DE, which may be KDE, Gnome, Xfce etc. The preferred DM for KDE is SDDM, but it can invoke the Gnome DE if you like. Gnome normally uses GDM and the same applies in reverse. If switching between DMs then yes, you do need to log out and run a script, but there's normally no need. You can switch between DEs from the login screen.
Plasma is not the whole DE. You can restart it at any time without logging out if you have a working terminal emulator.
poc
Thanks Patrick, I thought that when, in my current case, SDDM starts up Plasma it was starting up a Plasmashell which Plasma was running inside of, hence how do you restart Plasmashell without that shutting down the gui. I'll also need to look up the instructions again for switching between DM's again as I'm thinking of switching away from SDDM as it's start up performance is atrocious, but then the start up performance of KDE/Plasma is not much better.
regards, Steve
regards, Steve
On Fri, 2025-03-21 at 08:33 +1100, Stephen Morris wrote:
[Lots of stuff deleted. It's neither necessary not desireable to quote the wntire previous history of a message in order to reply to it. See the Guidelines.]
[...]
Plasma is not the whole DE. You can restart it at any time without logging out if you have a working terminal emulator.
poc
Thanks Patrick, I thought that when, in my current case, SDDM starts up Plasma it was starting up a Plasmashell which Plasma was running inside of, hence how do you restart Plasmashell without that shutting down the gui. I'll also need to look up the instructions again for switching between DM's again as I'm thinking of switching away from SDDM as it's start up performance is atrocious, but then the start up performance of KDE/Plasma is not much better.
The processes run from plasmashell don't die when it crashes or is restarted. The processes it starts run asynchronously. If you look at 'pstree' for example, you'll see lots of GUI-related processes running under systemd, including plasmasehll itself.
poc
*From:* Patrick O'Callaghan pocallaghan@gmail.com
*Sent:* Friday, 21 March 2025 at 09:28 UTC+11
*To:* users@lists.fedoraproject.org
*Subject:* RE: Tracer Messages
On Fri, 2025-03-21 at 08:33 +1100, Stephen Morris wrote:
[Lots of stuff deleted. It's neither necessary not desireable to quote the wntire previous history of a message in order to reply to it. See the Guidelines.]
[...]
Plasma is not the whole DE. You can restart it at any time without logging out if you have a working terminal emulator.
poc
Thanks Patrick, I thought that when, in my current case, SDDM starts up Plasma it was starting up a Plasmashell which Plasma was running inside of, hence how do you restart Plasmashell without that shutting down the gui. I'll also need to look up the instructions again for switching between DM's again as I'm thinking of switching away from SDDM as it's start up performance is atrocious, but then the start up performance of KDE/Plasma is not much better.
The processes run from plasmashell don't die when it crashes or is restarted. The processes it starts run asynchronously. If you look at 'pstree' for example, you'll see lots of GUI-related processes running under systemd, including plasmasehll itself.
Thanks Patrick, I didn't realise Plasmashell was multi-threading. I'd never heard of pstree, so I'll have to check that out. regards, Steve
poc
-
Patrick O'Callaghan -
Stephen Morris -
Will McDonald