.xsession-errors UPower? Anybody else get this with openSUSE Firefox build?
All, After the last sound crash (uptime 2 days 20 hours), checking .xsession-errors I ran across the following warning (not sound related): [Parent 10088, Main Thread] WARNING: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable : 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-130.0.1/toolkit/xre/nsSigHandlers.cpp:187 ** (firefox:10088): WARNING **: 01:48:08.287: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable It's firefox and not kde3, but is there some new signal handler we need to add? Or should we just ignore this warning? This is firefox from OSS. -- David C. Rankin, J.D.,P.E.
On 2024-09-26 00:43, David C. Rankin wrote:
All,
After the last sound crash (uptime 2 days 20 hours), checking .xsession-errors I ran across the following warning (not sound related):
I no longer have that file: cer@Telcontar:~> l .xsession-errors* -rw------- 1 cer users 0 Jan 7 2019 .xsession-errors -rw------- 1 cer users 180042 Jan 7 2019 .xsession-errors-:0 -rw------- 1 cer users 6886 Dec 28 2016 .xsession-errors-:1 -rw------- 1 cer users 0 Dec 30 2018 .xsession-errors.old cer@Telcontar:~> Maybe this is peculiar to kde3 :-? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-09-27 15:09, Carlos E. R. wrote:
On 2024-09-26 00:43, David C. Rankin wrote:
All,
After the last sound crash (uptime 2 days 20 hours), checking .xsession-errors I ran across the following warning (not sound related):
I no longer have that file:
cer@Telcontar:~> l .xsession-errors* -rw------- 1 cer users 0 Jan 7 2019 .xsession-errors -rw------- 1 cer users 180042 Jan 7 2019 .xsession-errors-:0 -rw------- 1 cer users 6886 Dec 28 2016 .xsession-errors-:1 -rw------- 1 cer users 0 Dec 30 2018 .xsession-errors.old cer@Telcontar:~>
Maybe this is peculiar to kde3 :-? Hi,
to my eye it seems that some power related feature is just missing or maybe deprecated? "org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable" --- https://talk.brave.com/ https://signal.org/ https://jami.net/download/
On 9/27/24 8:58 AM, Kirjavainen Tero wrote:
Hi,
to my eye it seems that some power related feature is just missing or maybe deprecated?
"org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable"
Searching "org.freedesktop.DBus.Error.ServiceUnknown" turns up many, many different settings when this error is thrown. None very specific. It doesn't seem to hurt anything, so it looks like this is just something dbus isn't responding to anymore. As firefox port ever further into Gtk4, we will probably see more of this type warning. Anybody find anything specific, please add to the conversions. Of the 10 or so links I went through from Debian, Ubuntu, Gentoo, etc.. it seems browser related (with konqueror, vivaldi, chromium, and firefox), but no answer as to what or why. -- David C. Rankin, J.D.,P.E.
Oops forgot to reply to the list... -------- Forwarded Message -------- Subject: Re: .xsession-errors UPower? Anybody else get this with openSUSE Firefox build? Date: Fri, 27 Sep 2024 18:07:39 -0500 From: David C. Rankin <drankinatty@gmail.com> To: kde3@lists.opensuse.org CC: David C. Rankin <drankinatty@gmail.com> On 9/27/24 8:58 AM, Kirjavainen Tero wrote:
Hi,
to my eye it seems that some power related feature is just missing or maybe deprecated?
"org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable"
Searching "org.freedesktop.DBus.Error.ServiceUnknown" turns up many, many different settings when this error is thrown. None very specific. It doesn't seem to hurt anything, so it looks like this is just something dbus isn't responding to anymore. As firefox port ever further into Gtk4, we will probably see more of this type warning. Anybody find anything specific, please add to the conversions. Of the 10 or so links I went through from Debian, Ubuntu, Gentoo, etc.. it seems browser related (with konqueror, vivaldi, chromium, and firefox), but no answer as to what or why. -- David C. Rankin, J.D.,P.E. -- David C. Rankin, J.D.,P.E.
On 9/27/24 7:09 AM, Carlos E. R. wrote:
On 2024-09-26 00:43, David C. Rankin wrote:
All,
After the last sound crash (uptime 2 days 20 hours), checking .xsession-errors I ran across the following warning (not sound related):
I no longer have that file:
cer@Telcontar:~> l .xsession-errors* -rw------- 1 cer users 0 Jan 7 2019 .xsession-errors -rw------- 1 cer users 180042 Jan 7 2019 .xsession-errors-:0 -rw------- 1 cer users 6886 Dec 28 2016 .xsession-errors-:1 -rw------- 1 cer users 0 Dec 30 2018 .xsession-errors.old cer@Telcontar:~>
Maybe this is peculiar to kde3 :-?
It looks like your desktop has gone to a .xsession-errors-:0 and .xsession-errors-:1 scheme to preserve the last error file through the next desktop start (smart). Like the scheme for Xorg.0.log ... If you see the error I posted, it would likely be in one of those two file. Try a $ grep 'org.freedesktop.UPower' .xsessions-errors* and see if anything turns up (or maybe grep 'firefox' .xsessions-errors*) -- David C. Rankin, J.D.,P.E.
On 2024-09-27 22:41, David C. Rankin wrote:
On 9/27/24 7:09 AM, Carlos E. R. wrote:
On 2024-09-26 00:43, David C. Rankin wrote:
All,
After the last sound crash (uptime 2 days 20 hours), checking .xsession-errors I ran across the following warning (not sound related):
I no longer have that file:
cer@Telcontar:~> l .xsession-errors* -rw------- 1 cer users 0 Jan 7 2019 .xsession-errors -rw------- 1 cer users 180042 Jan 7 2019 .xsession-errors-:0 -rw------- 1 cer users 6886 Dec 28 2016 .xsession-errors-:1 -rw------- 1 cer users 0 Dec 30 2018 .xsession-errors.old cer@Telcontar:~>
Maybe this is peculiar to kde3 :-?
It looks like your desktop has gone to a .xsession-errors-:0 and .xsession-errors-:1 scheme to preserve the last error file through the next desktop start (smart). Like the scheme for Xorg.0.log ...
Notice the dates ;-) -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 9/28/24 6:29 AM, Carlos E. R. wrote:
It looks like your desktop has gone to a .xsession-errors-:0 and .xsession-errors-:1 scheme to preserve the last error file through the next desktop start (smart). Like the scheme for Xorg.0.log ...
Notice the dates ;-)
Hmmm..., Fell right into that one -- didn't I :) -- David C. Rankin, J.D.,P.E.
On 2024-09-28 14:55, David C. Rankin wrote:
On 9/28/24 6:29 AM, Carlos E. R. wrote:
It looks like your desktop has gone to a .xsession-errors-:0 and .xsession-errors-:1 scheme to preserve the last error file through the next desktop start (smart). Like the scheme for Xorg.0.log ...
Notice the dates ;-)
Hmmm...,
Fell right into that one -- didn't I :)
So, I wonder why I don't have the file. I can not believe there are no errors in that time. Maybe because I do not use startx? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 9/28/24 1:58 PM, Carlos E. R. wrote:
So, I wonder why I don't have the file. I can not believe there are no errors in that time.
Maybe because I do not use startx?
I'll have to check. I don't use startx either on openSUSE (I do on Arch with fluxbox), instead I use kdm3 on openSUSE. I've never thought about what start logging errors to .xsession-errors, it's always just been there. It's not with startx, but is with lightdm, kdm3, etc.. so it may be the display manager that is responsible for it. -- David C. Rankin, J.D.,P.E.
On 2024-09-29 01:34, David C. Rankin wrote:
On 9/28/24 1:58 PM, Carlos E. R. wrote:
So, I wonder why I don't have the file. I can not believe there are no errors in that time.
Maybe because I do not use startx?
I'll have to check. I don't use startx either on openSUSE (I do on Arch with fluxbox), instead I use kdm3 on openSUSE. I've never thought about what start logging errors to .xsession-errors, it's always just been there. It's not with startx, but is with lightdm, kdm3, etc.. so it may be the display manager that is responsible for it.
It occurred to me to try this, but no hits: journalctl | grep "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown" | less but cer@Telcontar:~> journalctl | grep "GDBus.Error" | less Jun 21 14:24:48 Telcontar xdg-desktop-por[32550]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Jun 21 19:22:35 Telcontar xdg-desktop-por[5528]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Aug 17 23:05:40 Telcontar xdg-desktop-por[17489]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Aug 26 12:17:57 Telcontar xdg-desktop-por[5416]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Sep 01 15:42:51 Telcontar xdg-desktop-por[8460]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Sep 07 16:54:38 Telcontar xdg-desktop-por[5450]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Sep 10 20:14:26 Telcontar xdg-desktop-por[9211]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list Sep 10 20:51:03 Telcontar xdg-desktop-por[5415]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list But not what you are looking for. Sorry. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 9/28/24 7:18 PM, Carlos E. R. wrote:
On 2024-09-29 01:34, David C. Rankin wrote:
On 9/28/24 1:58 PM, Carlos E. R. wrote:
So, I wonder why I don't have the file. I can not believe there are no errors in that time.
Maybe because I do not use startx?
I'll have to check. I don't use startx either on openSUSE (I do on Arch with fluxbox), instead I use kdm3 on openSUSE. I've never thought about what start logging errors to .xsession-errors, it's always just been there. It's not with startx, but is with lightdm, kdm3, etc.. so it may be the display manager that is responsible for it.
It occurred to me to try this, but no hits:
journalctl | grep "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown" | less
but
cer@Telcontar:~> journalctl | grep "GDBus.Error" | less
Jun 21 14:24:48 Telcontar xdg-desktop-por[32550]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list <snip>
Apparently .xsession-errors (while still used widely) has been deprecated for more than a decade: https://stackoverflow.com/questions/10222449/what-is-xsession-errors Docs from the gnome side (link referenced in SO Answer): https://help.gnome.org/admin/system-admin-guide/stable/session-debug.html.en -- David C. Rankin, J.D.,P.E.
On 9/28/24 8:34 PM, David C. Rankin wrote:
Apparently .xsession-errors (while still used widely) has been deprecated for more than a decade:
https://stackoverflow.com/questions/10222449/what-is-xsession-errors
Docs from the gnome side (link referenced in SO Answer):
https://help.gnome.org/admin/system-admin-guide/stable/session-debug.html.en
Ahah!, For openSUSE it is started in: /usr/etc/X11/xdm/Xsession # # Redirect errors to the standard user log files. # for errfile in "${HOME}/.xsession-errors" \ "${TMPDIR:-/tmp}/xerr-${USER}-${DISPLAY}" do ... So if however you start your desktop invokes /usr/etc/X11/xdm/Xsession, the redirect of errors to ${HOME}/.xsession-errors occurs. -- David C. Rankin, J.D.,P.E.
On 2024-09-29 05:12, David C. Rankin wrote:
On 9/28/24 8:34 PM, David C. Rankin wrote:
Apparently .xsession-errors (while still used widely) has been deprecated for more than a decade:
https://stackoverflow.com/questions/10222449/what-is-xsession-errors
Docs from the gnome side (link referenced in SO Answer):
https://help.gnome.org/admin/system-admin-guide/stable/session-debug.html.en
Ahah!,
For openSUSE it is started in: /usr/etc/X11/xdm/Xsession
I don't have this script. I have "/etc/X11/xdm/Xsession" instead.
# # Redirect errors to the standard user log files. # for errfile in "${HOME}/.xsession-errors" \ "${TMPDIR:-/tmp}/xerr-${USER}-${DISPLAY}" do ...
So if however you start your desktop invokes /usr/etc/X11/xdm/Xsession, the redirect of errors to ${HOME}/.xsession-errors occurs.
I see the script, but I don't really understand what it does, where are the errors actually written to. But I am using sddm. I suspect they go to syslog. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 9/29/24 7:37 AM, Carlos E. R. wrote:
I don't have this script. I have "/etc/X11/xdm/Xsession" instead.
Yes, I can't stand openSUSE deciding to squirrel configs away under /usr/etc, that makes no sense. /etc is FHS and proper. Now you have configs split between /etc/ and /usr/etc/
# # Redirect errors to the standard user log files. # for errfile in "${HOME}/.xsession-errors" \ "${TMPDIR:-/tmp}/xerr-${USER}-${DISPLAY}" do ...
So if however you start your desktop invokes /usr/etc/X11/xdm/Xsession, the redirect of errors to ${HOME}/.xsession-errors occurs.
I see the script, but I don't really understand what it does, where are the errors actually written to. But I am using sddm. I suspect they go to syslog.
My understanding is that while when you start a process from the console, you have stderr output to the console on error. However, your user session/X session isn't started from the console, it's started by another process. So to capture any error on stderr from your session they redirect the output to a file, .xsession-errors in this case. (it is also captured in the journal for the most part as well) There is likely some of what X does whose errors are not captured in the journal which is likely why .xsession-errors has been deprecated for more than a decade, but is still with us. -- David C. Rankin, J.D.,P.E.
participants (3)
-
Carlos E. R. -
David C. Rankin -
Kirjavainen Tero