For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
BTW in terms of F34 I have two other small nags. The first is that some windows forget their placement and are sent to the first desktop when booting.
The other issue is that, at least for this account, plasma (wayland) freezes the machine while gnome (wayland) works. Although it had some issues there was no freeze in Fedora 33.
Where can I find further informations to debug these issues?
Best regards,
On Thu, 2021-04-15 at 21:53 +0100, José Abílio Matos wrote:
For a long time I have a script in ~/.config/autostart- scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
BTW in terms of F34 I have two other small nags. The first is that some windows forget their placement and are sent to the first desktop when booting.
The other issue is that, at least for this account, plasma (wayland) freezes the machine while gnome (wayland) works. Although it had some issues there was no freeze in Fedora 33.
Where can I find further informations to debug these issues?
You could ask on the Test list, where this post belongs. F34 has not yet been released.
poc
On Thu, Apr 15, 2021 at 5:45 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Thu, 2021-04-15 at 21:53 +0100, José Abílio Matos wrote:
For a long time I have a script in ~/.config/autostart- scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
BTW in terms of F34 I have two other small nags. The first is that some windows forget their placement and are sent to the first desktop when booting.
The other issue is that, at least for this account, plasma (wayland) freezes the machine while gnome (wayland) works. Although it had some issues there was no freeze in Fedora 33.
Where can I find further informations to debug these issues?
You could ask on the Test list, where this post belongs. F34 has not yet been released.
Discussing development releases of Fedora is totally on-topic for this list. This list is *primarily* for the discussions by the KDE SIG for the development of the KDE spin, though it does somewhat function as a user discussion list too.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Thu, 2021-04-15 at 18:01 -0400, Neal Gompa wrote:
You could ask on the Test list, where this post belongs. F34 has not yet been released.
Discussing development releases of Fedora is totally on-topic for this list. This list is *primarily* for the discussions by the KDE SIG for the development of the KDE spin, though it does somewhat function as a user discussion list too.
Yes, I realise that. For some reason I mistakenly thought I was looking at the Fedora Users list.
Apologies for the confusion.
poc
On Thu, Apr 15, 2021 at 4:53 PM José Abílio Matos jamatos@fc.up.pt wrote:
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
I've been doing this with a systemd user unit. There's some good detail on how to make and use systemd user units on the Arch Wiki: https://wiki.archlinux.org/index.php/systemd/User
BTW in terms of F34 I have two other small nags. The first is that some windows forget their placement and are sent to the first desktop when booting.
Can you file bug reports upstream on the KDE Bugzilla? I know there's a whole bunch of quality-of-life fixes coming with the next bug fix release and even more with 5.22 coming in June.
The other issue is that, at least for this account, plasma (wayland) freezes the machine while gnome (wayland) works. Although it had some issues there was no freeze in Fedora 33.
Where can I find further informations to debug these issues?
The major change between F33 and F34 is the newer Mesa. There may be details in the systemd journal of the nature of the freezes, as most of the logging goes into there.
On 4/15/21 11:57 PM, Neal Gompa wrote:
On Thu, Apr 15, 2021 at 4:53 PM José Abílio Matos jamatos@fc.up.pt wrote:
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
I've been doing this with a systemd user unit. There's some good detail on how to make and use systemd user units on the Arch Wiki: https://wiki.archlinux.org/index.php/systemd/User
Would you mind sharing your user service file for this?
Best regards,
Robert-André
On 4/21/21 6:10 PM, Robert-André Mauchin wrote:
On 4/15/21 11:57 PM, Neal Gompa wrote:
On Thu, Apr 15, 2021 at 4:53 PM José Abílio Matos jamatos@fc.up.pt wrote:
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
I've been doing this with a systemd user unit. There's some good detail on how to make and use systemd user units on the Arch Wiki: https://wiki.archlinux.org/index.php/systemd/User
Would you mind sharing your user service file for this?
Best regards,
Robert-André
I've used:
~/.config/systemd/user/ssh-add.service [Unit] Description=ssh-add service Requires=ssh-agent.service After=ssh-agent.service
[Service] ExecStart=ssh-add -q %h/.ssh/id_rsa
[Install] WantedBy=xdg-desktop-autostart.target
with:
~/.config/environment.d/60-ssh-add.conf export SSH_ASKPASS='/usr/bin/ksshaskpass' export GIT_ASKPASS='/usr/bin/ksshaskpass
and it works. Let me know if there is a better way to do it.
On 4/15/21 10:53 PM, José Abílio Matos wrote:
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
I have the same issue since F34, I thought this was a Wayland issue but I have not looked further. I thought my startup scripts in Plasma were not working but even adding them to my .profile or .bashrc it doesn't work. I wonder if this is because the ssh-agent is not yet started.
Hi,
I'm still on F33 at the moment, but for a long time now I haven't needed to use a startup script as such for SSH. I have configured a startup task by going to System Settings->startup and Shutdown->Autostart.
In there by selecting the '+ Add' button I have created a desktop config file simply by putting 'ssh-add' in the box (under the 'General' tab). This is just the name of the task. The location is '/home/xxx/.config/autostart' (where xxx is your userid). Click on the 'Application' tab, and enter '/usr/bin/ssh-add' in the 'Command:' box. then click on 'Okay'.
As far as I remember that was it. When I start up my laptop it auto logs me in, and runs the SSH askpass program for my secret. It has worked for a long time now, but I admit that I won't know if it still works under F34 until I update.
John.
On Tue, 2021-04-20 at 17:08 +0200, Robert-André Mauchin wrote:
On 4/15/21 10:53 PM, José Abílio Matos wrote:
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
It almost looks like that kwallet it is not opened when the autostart script runs.
I have the same issue since F34, I thought this was a Wayland issue but I have not looked further. I thought my startup scripts in Plasma were not working but even adding them to my .profile or .bashrc it doesn't work. I wonder if this is because the ssh-agent is not yet started.
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]http://www.plymouth.ac.uk/worldclass
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
On Tuesday, April 20, 2021 11:26:30 AM EDT John Horne wrote:
In there by selecting the '+ Add' button I have created a desktop config file simply by putting 'ssh-add' in the box (under the 'General' tab). This is just the name of the task. The location is '/home/xxx/.config/autostart' (where xxx is your userid). Click on the 'Application' tab, and enter '/usr/bin/ssh-add' in the 'Command:' box. then click on 'Okay'.
I had problems after upgrading to F34 and this procedure (after deleting the script that I used to use to accomplish this) restored the original function.
I would just clarify that the procedure is
System Settings -> Startup and Shutdown -> Autostart
then
+ Add -> Add Application
then type /usr/bin/ssh-add <ENTER>
José Abílio Matos wrote:
For a long time I have a script in ~/.config/autostart-scripts/ksshaskpass
#!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add xxxxx_key < /dev/null
For F34 this is not working out of the box.
That is after entering the plasma session using ssh always asks for the pass phrase. On the other hand if I run the last line directly, after the startup stage, then the agent is added and it works from there.
ssh-agent on f34/plasma-wayland runs a little different than prior releases.
Prior releases run ssh-agent as part of the xinit process, but not too surprising, that mechanism is for X only.
In f34, I worked with fedora's openssh maintainer to run ssh-agent as a systemd user service (for plasma wayland sessions), per /usr/lib/systemd/user/ssh-agent.service
(This method inspired by other distros that already do this)
Unfortunately, systemd services cannot themselves export environment, so we needed one more piece /etc/xdg/plasma-workspace/env/ssh-agent.sh which contains just: if [ "$SSH_AUTH_SOCK" = "" ]; then SSH_AUTH_SOCK="$XDG_RUNTIME_DIR/ssh-agent.socket" export SSH_AUTH_SOCK fi
So that SSH_AUTH_SOCK env variable gets set for the plasma wayland session.
It's quite possible this new mechanism may make some legacy setups not work anymore, especially if those mechanisms try to access ssh-agent before SSH_AUTH_SOCK gets set (workaround there is to just set SSH_AUTH_SOCK yourself to match the env snippet above).
Hope this helps...
-- Rex
-
Garry T. Williams -
John Horne -
José Abílio Matos -
Neal Gompa -
Patrick O'Callaghan -
Rex Dieter -
Robert-André Mauchin