[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=391609

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   Keywords||usability
 CC||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[Méven Car]

https://bugs.kde.org/show_bug.cgi?id=391609

Méven Car  changed:

   What|Removed |Added

 CC||meven@enioka.com

--- Comment #7 from Méven Car  ---
A shell script is a shell script when it starts with "#!/bin/sh" or
"#!/bin/bash"..

The autostart kcm should show a warning when the file is text and its content
does not start with "#!/bin/" or has not the executable rights to prevent such
issues.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[francisco_t]

https://bugs.kde.org/show_bug.cgi?id=391609

--- Comment #6 from francisco_t  ---
(In reply to Arek Guzinski from comment #5)
> 
> @francisco_t: many of the things xmodmap does, would be overwritten when kde
> sets the keyboard layout. are you sure that's not happening? (i don't think
> it should, but.. maybe..)
> as a workaround, you could try a script with the line
> (sleep 5; xmodmap ~/.xmodmaprc)&

It's working! Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[Arek Guzinski]

https://bugs.kde.org/show_bug.cgi?id=391609

--- Comment #5 from Arek Guzinski  ---
> Maybe there are some particularities in the script that are causing the 
> problem?

damn it!

yes, actually there was something.. 

after some more experimenting, i found that the "Session Autostart Manager
Control Panel Module" -> "Add Script" was adding the
"#!/bin/sh
"
header to every script, which seems to be mandatory now...

since my script was from the old days, it did not have that header.
adding it, fixed this problem :)

would be nice if kde would have told me, my script can't start because of that.
maybe "Session Autostart Manager Control Panel Module" could make a quick check
when it's opened?


the multiple execution issue with scripts that run "Before session start-up"
still remains. should i open another bug for that?


@Alexander Mentyu: thanks for motivating me to look closer!

@francisco_t: many of the things xmodmap does, would be overwritten when kde
sets the keyboard layout. are you sure that's not happening? (i don't think it
should, but.. maybe..)
as a workaround, you could try a script with the line
(sleep 5; xmodmap ~/.xmodmaprc)&

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[Alexander Mentyu]

https://bugs.kde.org/show_bug.cgi?id=391609

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #4 from Alexander Mentyu  ---
Cannot reproduce, autostart script is always starting

echo '123' >> /home/user/123

Maybe there are some particularities in the script that are causing the
problem?

Plasma: 5.13.2
Apps: 18.04.2
Frameworks: 5.47.0
Qt: 5.11.1
Kernel: 4.18.0-1-MANJARO
OS: Netrunner Rolling
Video: Intel 4400
Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1
Mesa 3D: 18.1.3
Screen: 1600x900
Xorg: 1.20
Wayland: 1.15.0-1
Wayland Protocols: 1.14-1

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[Arek Guzinski]

https://bugs.kde.org/show_bug.cgi?id=391609

--- Comment #3 from Arek Guzinski  ---
okay...
I just tried this with KUbuntu 18.04 LTS in VirtualBox and autostart works fine
there.
So maybe this will be fixed when Neon finally switches to 18.04.
Upgrading to 5.13 on Neon at least, did not change anything... :(
The question is: do i want to wait that long? It's really annoying to start all
the stuff manually on login.

Are there any known workarounds?

If not, is there a guide on how to run ksmserver in gdb?
I imagine it's not simple, as it should start a clean X/Wayland session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[francisco_t]

https://bugs.kde.org/show_bug.cgi?id=391609

francisco_t  changed:

   What|Removed |Added

 CC||leviat...@gmx.com

--- Comment #2 from francisco_t  ---
I have a "command" in autostart. It's a .desktop file:

[Desktop Entry]
Comment[es_ES]=
Comment=
Exec=xmodmap ~/.xmodmaprc
GenericName[es_ES]=
GenericName=
Icon=system-run
MimeType=
Name[es_ES]=
Name=
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=

And doesn't work too in 5.12.x

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 391609] autostart script is not executed, log claims it is

[Arek Guzinski]

https://bugs.kde.org/show_bug.cgi?id=391609

--- Comment #1 from Arek Guzinski  ---
i experimented with running myxinit.sh from noblink.sh as a workaround and
discovered that noblink.sh is executed twice at login and once at logout (i
expected it to run only once at login). Is this wanted behaviour or another
(possibly related) bug?

-- 
You are receiving this mail because:
You are watching all bug changes.