[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#823829: marked as done (sddm: SDDM login hangs with keyring unless you enter passphrase in the console)

Your message dated Mon, 20 Feb 2017 14:28:21 +0100
with message-id <20170220132821.2ajupeqah533ulgt@gnuservers.com.ar>
and subject line Re: Bug#823829: sddm: SDDM login hangs with keyring unless you enter passphrase in the console
has caused the Debian Bug report #823829,
regarding sddm: SDDM login hangs with keyring unless you enter passphrase in the console
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
823829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823829
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sddm
Version: 0.13.0-1
Severity: important

Dear Maintainer,

I noticed that if you are running keychain to store your SSH keys in
memory, unless you log in to the user account in the console and enter
your ssh key passphrase, the login from sddm hangs and fails to log the
user in. The associated snippet from my .bashrc is as follows:

/usr/bin/keychain $HOME/.ssh/id_rsa
. $HOME/.keychain/$HOSTNAME-sh > /dev/null

--b

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sddm depends on:
ii  adduser                           3.114
ii  debconf [debconf-2.0]             1.5.59
ii  libc6                             2.22-7
ii  libgcc1                           1:5.3.1-11
ii  libpam0g                          1.1.8-3.2
ii  libqt5core5a                      5.5.1+dfsg-16+b1
ii  libqt5dbus5                       5.5.1+dfsg-16+b1
ii  libqt5gui5                        5.5.1+dfsg-16+b1
ii  libqt5network5                    5.5.1+dfsg-16+b1
ii  libqt5qml5                        5.5.1-3
ii  libqt5quick5                      5.5.1-3
ii  libstdc++6                        5.3.1-11
ii  libsystemd0                       229-5
ii  libxcb-xkb1                       1.11.1-1
ii  libxcb1                           1.11.1-1
ii  qml-module-qtquick2               5.5.1-3
ii  sddm-theme-breeze [sddm-theme]    4:5.4.3-2
ii  sddm-theme-maldives [sddm-theme]  0.13.0-1
ii  sddm-theme-maui [sddm-theme]      0.13.0-1

Versions of packages sddm recommends:
ii  libpam-systemd  229-5

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.4.3-1

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm


--- End Message ---
--- Begin Message --- 
¡Hola Brad!

El 2016-05-09 a las 08:09 -0400, Brad Alexander escribió:
Package: sddm Version: 0.13.0-1 Severity: important
I noticed that if you are running keychain to store your SSH keys in memory, unless you log in to the user account in the console and enter your ssh key passphrase, the login from sddm hangs and fails to log the user in. The associated snippet from my .bashrc is as follows:
/usr/bin/keychain $HOME/.ssh/id_rsa . $HOME/.keychain/$HOSTNAME-sh > /dev/null
sddm starts a user shell to set the "desired" enviroment variables (see https://anonscm.debian.org/cgit/pkg-kde/kde-std/sddm.git/tree/debian/Xsession). This will fail if you are using an interactive program in it.
You need to check if you are in an interactive shell before calling an interactive prompt. 

Consider adding a:
[ -z "$PS1" ] && return

Before the parts that assume an interactive shell.
I'm closing the issue, please reopen if you can still reproduce it after adding the recommended snippet. 

Happy hacking,
--
"First, solve the problem. Then, write the code." -- John Johnson
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: