sorry,I’m not really sure how to answer that. There are just the two ways to launch it in the Hyprland version.
https://gitlab.com/garuda-linux/themes-and-settings/settings/garuda-hyprland-settings/-/blob/main/etc/skel/.config/hypr/hyprland.conf?ref_type=heads
line 150 152
When you run /usr/lib/garuda/pkexec-gui garuda-boot-options in a terminal, what is the output you see in the terminal and does the program run successfully?
hi,
i didnt checked that too much yet sry and used not a long time. I was busy with other stuff too.
Yeah its in the wofi launcher. I did test this in the launcher and the dbus command in the terminal few minutes ago again and closed it . Ive installed yesterday some XFCE stuff and with pacseek qt5-styleplugins. I cant reproduce it like yesterday so there was a package in what solved it.
I see the Updates with those both apps and few more didnt do it actually .
is this output
full output before update
/usr/lib/garuda/pkexec-gui garuda-boot-options
garuda-boot-options version: 0.1
Exec #1: "logname"
Exit #1: 0 QProcess::NormalExit
Exec #2: "mountpoint -q /live/aufs"
** (garuda-boot-options:9720): WARNING **: 05:33:33.526: AT-SPI: Could not obtain desktop path or name
Exit #2: 1 QProcess::NormalExit
Exec #3: "pacman -Qq plymouth"
** (garuda-boot-options:9720): WARNING **: 05:33:33.530: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.530: atk-bridge: GetRegisteredEvents returned message with unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.534: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:9720): WARNING **: 05:33:33.534: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:9720): WARNING **: 05:33:33.537: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:9720): WARNING **: 05:33:33.537: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.537: atk-bridge: GetRegisteredEvents returned message with unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.537: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.538: atk-bridge: GetRegisteredEvents returned message with unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.541: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:9720): WARNING **: 05:33:33.541: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:9720): WARNING **: 05:33:33.541: atk-bridge: GetRegisteredEvents returned message with unknown signature
SErr #3: "error: package 'plymouth' was not found\n"
Exit #3: 1 QProcess::NormalExit
Exec #4: "pacman -Qq plymouth"
SErr #4: "error: package 'plymouth' was not found\n"
Exit #4: 1 QProcess::NormalExit
Exec #5: "test -z \"$(lspci -d 80ee:beef)\""
Exit #5: 0 QProcess::NormalExit
Exec #6: "df -T / |tail -n1 |awk '{print $2}'"
Exit #6: 0 QProcess::NormalExit
Running GarudaBO cleanup code
after the Update
/usr/lib/garuda/pkexec-gui garuda-boot-options
qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_combo_theme_currentIndexChanged(QString)
** (garuda-boot-options:1734): WARNING **: 05:53:19.120: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:1734): WARNING **: 05:53:19.133: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.133: atk-bridge: GetRegisteredEvents returned message with unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.138: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:1734): WARNING **: 05:53:19.138: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:1734): WARNING **: 05:53:19.143: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:1734): WARNING **: 05:53:19.143: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.143: atk-bridge: GetRegisteredEvents returned message with unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.143: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.143: atk-bridge: GetRegisteredEvents returned message with unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.147: AT-SPI: Could not obtain desktop path or name
** (garuda-boot-options:1734): WARNING **: 05:53:19.147: atk-bridge: get_device_events_reply: unknown signature
** (garuda-boot-options:1734): WARNING **: 05:53:19.147: atk-bridge: GetRegisteredEvents returned message with unknown signature
╭─duke@duke in ~ took 19s
apprecate your work if i would be more familar with that kind of coding i would volunteer 
1 Like
Just tested it myself. The latest version of garuda-libs (1.6.2) solves this. It seems to launch correctly again now. Please confirm that you don’t get logged out after a bit.
Also, please confirm that it launches correctly on hyprland. @tr1es
1 Like
Everything’s working perfectly now. Great job! 
1 Like
As the minor issues get resolved, I’m really starting to enjoy Garuda’s Hyprland version. After a bit more time learning it, I could probably ditch Windows entirely.
2 Likes
@BluishHumility just to keep you in the loop (since your fix to another problem has caused this problem), this was fixed by removing the dbus-run-session and instead detecting if the parent process is going to disappear/has disappeared and avoiding the exec, which allows pkexec to function correctly.
There is probably some merit to removing the exec entirely, but I like removing one process from the process tree where possible.
This seems to be a no compromise solution. No launcher I’ve tried so far actually ever gets to the parent_exe checks, so that’s just acting as a fallback.
3 Likes
There are only a few minor issues left, mainly in the configuration files: some settings do not take effect and some are redundant.
I have already adjusted them myself, but would you consider fixing them before the next major release?
windowrule = float, title:(^(kitty)$)
windowrule = float, title:(^(garuda-assistant)$)
windowrule = float, title:(^(garuda-boot-options)$)
windowrule = float, title:(^(garuda-boot-repair)$)
windowrule = float, title:(^(garuda-gamer)$)
windowrule = float, title:(^(garuda-network-assistant)$)
windowrule = float, title:(^(garuda-settings-manager)$)
windowrule = float, title:(^(garuda-welcome)$)
windowrule = float, title:(^(calamares)$)
now hyprctl clients is this output
Window 55d66aa89240 -> Garuda Network Assistant:
mapped: 1
hidden: 0
at: 80,50
size: 1440,900
workspace: 3 (3)
floating: 1
pseudo: 0
monitor: 0
class: garuda-network-assistant
title: Garuda Network Assistant
initialClass: garuda-network-assistant
initialTitle: Garuda Network Assistant
pid: 20948
xwayland: 0
pinned: 0
fullscreen: 0
fullscreenClient: 0
grouped: 0
tags:
swallowing: 0
focusHistoryID: 1
inhibitingIdle: 0
xdgTag:
xdgDescription:
Window 55d66aa89240 -> Garuda Setup Assistant:
mapped: 1
hidden: 0
at: 369,267
size: 862,466
workspace: 3 (3)
floating: 1
pseudo: 0
monitor: 0
class: setup-assistant
title: Garuda Setup Assistant
initialClass: setup-assistant
initialTitle: Garuda Setup Assistant
pid: 21814
xwayland: 0
pinned: 0
fullscreen: 0
fullscreenClient: 0
grouped: 0
tags:
swallowing: 0
focusHistoryID: 1
inhibitingIdle: 0
xdgTag:
xdgDescription:
I’d appreciate it if you could make a merge request on gitlab! That’d be wonderful!
Oops, sorry everyone! 
It’s odd this issue would crop up five months later, but then again I guess Hyprland is still changing a lot so c’est la vie.
Looks good, thanks @TNE! I just tested on Garuda Sway with the Fuzzel launcher (where the original issue was mentioned back in March, Fuzzel Launch Issue in Sway: Programs Not Opening, But Working Fine in Nwg-Drawer) and it works great with the new pkexec-gui script from garuda-libs 1.6.2-1! 
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.