long launch of the first application

wzhxycl · 2023-10-15 16:32:10

Hi. I use gnome (kde plasma has no such problems), after launching in a gnome session, if you start an application it will take a very long time to launch, if you start another one at the same time, it will launch at the same time as the first one. I am ready to provide additional information if you can help me with a tip on what to show.

seth · 2023-10-15 18:43:57

Please specify "an application" and "a very long time"
25s would be the dbus timeout, the cause more or less likely xdg-portal (and I'm not sure about that dbus-run-session invocation in teh wiki)

=> Check the system journal for the relevant time ("sudo journalctl -b", xdg-portral errors will flare up there) and

echo $DBUS_SESSION_BUS_ADDRESS

wzhxycl · 2023-10-16 04:35:04

in the wiki it is true that it is running via dbus. the only error I see in journalctl is this.

Oct 16 07:30:49 archbtw dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.

output of the environment variable you wrote me

unix:path=/tmp/dbus-47RsNizgJV,guid=29db0dd80a312ee23b83f13f652cbbcf

I also have a video, here's the link https://www.youtube.com/watch?v=1Zg503eahe0

wzhxycl · 2023-10-16 04:35:43

seth wrote:

Please specify "an application" and "a very long time"
25s would be the dbus timeout, the cause more or less likely xdg-portal (and I'm not sure about that dbus-run-session invocation in teh wiki)
=> Check the system journal for the relevant time ("sudo journalctl -b", xdg-portral errors will flare up there) and
echo $DBUS_SESSION_BUS_ADDRESS

in the wiki it is true that it is running via dbus. the only error I see in journalctl is this.

Oct 16 07:30:49 archbtw dbus-daemon[490]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.

output of the environment variable you wrote me

unix:path=/tmp/dbus-47RsNizgJV,guid=29db0dd80a312ee23b83f13f652cbbcf

I also have a video, here's the link https://www.youtube.com/watch?v=1Zg503eahe0

wzhxycl · 2023-10-16 04:37:21

I first accidentally replied without replying to a post. then I edited and now I have these 2 posts here that I don't know how to delete

seth · 2023-10-16 06:45:24

You cannot delete posts, you can edit them and mark them as accidental double or report them for deletion (but that's pointless)
And likewise, please don't power post but edit your previous posts to mend/extend them if nobody has yet replied.

On topic: videos of nothing happening are nor really helpful, but the dbus-variable there isn't promising so please get rid of the dbus-session-run and test the behavior and value of $DBUS_SESSION_BUS_ADDRESS

If that doesn't fix it, please post your complete system journal after such delay:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

wzhxycl · 2023-10-16 11:47:05

seth wrote:

You cannot delete posts, you can edit them and mark them as accidental double or report them for deletion (but that's pointless)
And likewise, please don't power post but edit your previous posts to mend/extend them if nobody has yet replied.
On topic: videos of nothing happening are nor really helpful, but the dbus-variable there isn't promising so please get rid of the dbus-session-run and test the behavior and value of $DBUS_SESSION_BUS_ADDRESS
If that doesn't fix it, please post your complete system journal after such delay:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

I tried running gnome-session without dbus but it didn't work.

seth · 2023-10-16 11:58:37

seth wrote:

If that doesn't fix it, please post your complete system journal after such delay

wzhxycl · 2023-10-16 12:23:55

seth wrote:

seth wrote:
If that doesn't fix it, please post your complete system journal after such delay

Sorry. I thought I needed the output if I could run it without dbus, here you go http://0x0.st/HJrQ.txt.

seth · 2023-10-16 12:36:27

окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Could not check if unit gnome-session-wayland@gnome.target is active: Ошибка вызова StartServiceByName для org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Could not check if unit gnome-session-wayland@gnome.target is active: Ошибка вызова StartServiceByName для org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.

There's certainly an ongoing dbus issue.

loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS

окт 16 15:20:42 archbtw gnome-shell[754]: Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist

https://bbs.archlinux.org/viewtopic.php … 5#p2126475

wzhxycl · 2023-10-16 16:10:00

seth wrote:

окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Could not check if unit gnome-session-wayland@gnome.target is active: Ошибка вызова StartServiceByName для org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Could not check if unit gnome-session-wayland@gnome.target is active: Ошибка вызова StartServiceByName для org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
окт 16 15:20:42 archbtw gnome-session[697]: gnome-session-binary[697]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
окт 16 15:20:42 archbtw gnome-session-binary[697]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.

There's certainly an ongoing dbus issue.

loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS

окт 16 15:20:42 archbtw gnome-shell[754]: Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist

https://bbs.archlinux.org/viewtopic.php … 5#p2126475

I looked at the post on your link and the links in the post and from the solutions I noticed only adding the environment variable, but after adding it nothing changed, can you please point me in the direction of what to do?

The outputs of the commands you gave me:
http://0x0.st/HJzN.txt
http://0x0.st/HJzq.txt

seth · 2023-10-16 16:17:57

DBUS is still off, b/c

		  ├─ 932 dbus-run-session gnome-session

wzhxycl · 2023-10-16 16:37:01

seth wrote:

DBUS is still off, b/c

		  ├─ 932 dbus-run-session gnome-session

So what should I do? I'm running it just like you said.

seth · 2023-10-16 16:51:05

seth wrote:

please get rid of the dbus-session-rundbus-run-session

What does your bash_profile look like?

wzhxycl · 2023-10-16 17:12:16

seth wrote:

seth wrote:
please get rid of the dbus-session-rundbus-run-session
What does your bash_profile look like?

bash_profile: http://0x0.st/HJzY.txt
start.sh: http://0x0.st/HJzg.txt

seth · 2023-10-16 18:50:13

if lsusb | grep -q mouse; then
    startplasma-wayland
else
    if [ "$XDG_SESSION_TYPE" != "wayland" ]; then
        XDG_SESSION_TYPE=wayland gnome-session
    fi
fi

wzhxycl · 2023-10-17 11:39:29

seth wrote:

if lsusb | grep -q mouse; then
    startplasma-wayland
else
    if [ "$XDG_SESSION_TYPE" != "wayland" ]; then
        XDG_SESSION_TYPE=wayland gnome-session
    fi
fi

it doesn't work. no output, millisecond delay.

seth · 2023-10-17 14:56:49

Just recalled that we recently had that: https://bbs.archlinux.org/viewtopic.php … 5#p2110485
"gnome"…

wzhxycl · 2023-10-18 06:15:38

seth wrote:

Just recalled that we recently had that: https://bbs.archlinux.org/viewtopic.php … 5#p2110485
"gnome"…

Yeah. That helped, but what about the fact that I have a plasma frame?
Edit: and also the menu on the top left where the charge is located has lost a lot of panels.....

Last edited by wzhxycl (2023-10-18 06:16:33)

seth · 2023-10-18 06:26:59

What plasma frame, what menu and what panels?
Remember that only you can see your monitor, references to your visual perception are meaninless to everyone else.

I'd look at the process list.

Arch Linux

#1 2023-10-15 16:32:10

long launch of the first application

#2 2023-10-15 18:43:57

Re: long launch of the first application

#3 2023-10-16 04:35:04

Re: long launch of the first application

#4 2023-10-16 04:35:43

Re: long launch of the first application

#5 2023-10-16 04:37:21

Re: long launch of the first application

#6 2023-10-16 06:45:24

Re: long launch of the first application

#7 2023-10-16 11:47:05

Re: long launch of the first application

#8 2023-10-16 11:58:37

Re: long launch of the first application

#9 2023-10-16 12:23:55

Re: long launch of the first application

#10 2023-10-16 12:36:27

Re: long launch of the first application

#11 2023-10-16 16:10:00

Re: long launch of the first application

#12 2023-10-16 16:17:57

Re: long launch of the first application

#13 2023-10-16 16:37:01

Re: long launch of the first application

#14 2023-10-16 16:51:05

Re: long launch of the first application

#15 2023-10-16 17:12:16

Re: long launch of the first application

#16 2023-10-16 18:50:13

Re: long launch of the first application

#17 2023-10-17 11:39:29

Re: long launch of the first application

#18 2023-10-17 14:56:49

Re: long launch of the first application

#19 2023-10-18 06:15:38

Re: long launch of the first application

#20 2023-10-18 06:26:59

Re: long launch of the first application

Board footer