You are not logged in.
HoaS was saying it wouldn't need to be specifically a bash shebang; a /bin/sh shebang would suffice. I suspect like me he wants to break the trend of scripts being arbitrarily started with bash for no reason. Though for your own personal use on a stock arch system this makes no difference whatsoever.
On a bit of an odd hunch, can you try logging the output of "env" instead of the params (or in addition to them)?
Last edited by Trilby (2023-01-01 22:37:50)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
On a bit of an odd hunch, can you try logging the output of "env" instead of the params (or in addition to them)?
Here it is:
SHELL=/bin/bash
SESSION_MANAGER=local/amd:@/tmp/.ICE-unix/1054,unix/amd:/tmp/.ICE-unix/1054
QT_SCREEN_SCALE_FACTORS=DisplayPort-0=1;HDMI-A-0=1;DVI-D-0=1;
XDG_CONFIG_DIRS=/home/katy/.config/kdedefaults:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
DESKTOP_SESSION=plasma
GTK_RC_FILES=/etc/gtk/gtkrc:/home/katy/.gtkrc:/home/katy/.config/gtkrc
XCURSOR_SIZE=24
EDITOR=nano
GTK_MODULES=canberra-gtk-module
XDG_SEAT=seat0
PWD=/zork/WinExt/Wallpaper
XDG_SESSION_DESKTOP=KDE
LOGNAME=katy
XDG_SESSION_TYPE=x11
SYSTEMD_EXEC_PID=1183
XAUTHORITY=/home/katy/.Xauthority
DESKTOP_STARTUP_ID=amd;1672612214;55524;11167_TIME18802445
MOTD_SHOWN=pam
GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/katy/.gtkrc-2.0:/home/katy/.config/gtkrc-2.0
HOME=/home/katy
LANG=en_US.UTF-8
XDG_CURRENT_DESKTOP=KDE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
INVOCATION_ID=5bde0281f65846aa8e7cb305a4c314ec
MANAGERPID=992
KDE_SESSION_UID=1000
XDG_SESSION_CLASS=user
USER=katy
KDE_SESSION_VERSION=5
DISPLAY=:0
SHLVL=1
LC_MEASUREMENT=ro_RO.UTF-8
XDG_VTNR=1
XDG_SESSION_ID=1
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org
QT_AUTO_SCREEN_SCALE_FACTOR=0
JOURNAL_STREAM=8:31849
XCURSOR_THEME=Breeze_Snow
KDE_FULL_SESSION=true
PATH=/home/katy/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
KDE_APPLICATIONS_AS_SCOPE=1
MAIL=/var/spool/mail/katy
_=/usr/bin/envOffline
Thanks, that all looks good for what I was interested in (DISPLAY, XAUTHORITY, and the dbus variables are set).
If I were you, I'd next log all the stdout / stderr from the attempt to launch dolphin in the script.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Nothing comes out. This is how I modified the script:
/usr/bin/dolphin -stylesheet /zork/WinExt/Dolphin/folder-background.qss "$@" 2>&1 > /zork/output.txtOffline
Just noticed an oddity: if Dolphin is already running, then FF will successfully launch a second instance via my script.
Last edited by mdcclxv (2023-01-01 22:51:18)
Offline
That depends entirely on dolphin. Do you want a "--new-window"?
EDIT: sorry, I think I read your previous post to suggest the opposite of what it does. Please check and describe the actual behavior of the script run manually vs from firefox when dolphin is either already running vs not (note that's four conditions).
Last edited by Trilby (2023-01-01 23:31:21)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
That depends entirely on dolphin. Do you want a "--new-window"? If so, you may want to use that flag. Does firefox work with the script when dolphin isn't already running? Does it actually also work with dolphin running, you just didn't notice because it changes the directory displayed in an already existing dolphin window?
This is the whole point of this thread: I have no idea where FF gets that command line from. I'm not adding that flag. My script is listed several post before this one.
It doesn't work if Dolphin is not running. It does work with Dolphin already running, opens a new window.
Offline
That depends entirely on dolphin. Do you want a "--new-window"?
EDIT: sorry, I think I read your previous post to suggest the opposite of what it does. Please check and describe the actual behavior of the script run manually vs from firefox when dolphin is either already running vs not (note that's four conditions).
We already know how the script behaves when used via FF:
It doesn't work if Dolphin is not running. It does work with Dolphin already running, opens a new window.
Manual run works the same in both scenarios, that is, opens a new Dolphin window.
Last edited by mdcclxv (2023-01-01 23:51:09)
Offline
Simplify the script to establish a baseline:
#!/bin/sh
exec /usr/bin/dolphinsee what FF does.
Then
#!/bin/sh
exec /usr/bin/dolphin "$@"Offline
Simplify the script to establish a baseline:
#!/bin/sh exec /usr/bin/dolphinsee what FF does.
Then#!/bin/sh exec /usr/bin/dolphin "$@"
No difference of behavior: in both cases if Dolphin is running then it works, if not then nope.
Offline
Please keep in mind that Edge has exactly the same behavior, so the dirty trick is somewhere in KDE's guts.
Offline
#!/bin/sh
date >> /tmp/ffdolph.dbg
echo "$*" >> /tmp/ffdolph.dbg
exec /usr/bin/dolphin "$@" > /tmp/ffdolph.dbg 2>&1Make it fail and post /tmp/ffdolph.dbg
Offline
#!/bin/sh date >> /tmp/ffdolph.dbg echo "$*" >> /tmp/ffdolph.dbg exec /usr/bin/dolphin "$@" > /tmp/ffdolph.dbg 2>&1Make it fail and post /tmp/ffdolph.dbg
Not much ![]()
Tue Jan 3 18:06:28 EET 2023
--new-window --select /zork/WinExt/Wallpaper/Kay-3840x2160.pngOffline
…
unset KDE_APPLICATIONS_AS_SCOPE
exec /usr/bin/dolphin "$@" > /tmp/ffdolph.dbg 2>&1Offline
It's working now, even with my qss parameter. You rock!
The ffdolph file has no content now.
What's the catch with this KDE_APPLICATIONS_AS_SCOPE? I tried a quick googling, but only issues came up, no explanation.
Thanks a million.
Last edited by mdcclxv (2023-01-03 20:29:41)
Offline
"pIdS ArE VeRy yEsTeRyEaR" - https://phabricator.kde.org/D27883
I wasn't aware of that either and rather randomly stumbled over it revisiting your environment - looked suspicious, so I googled and found that commit.
Sufficiently annoyed by the sentiment, super-suspicious because of the cgroup affiliation I looked at the commit and was ~99.5% sure that it's the cause.
Ftr, there's also https://bugs.kde.org/show_bug.cgi?id=425982
I guess yesteryear means "when stuff just used to work because we didn't add layers of useless complexity to it"… ![]()
Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Last edited by seth (2023-01-03 21:01:02)
Offline