[Bug 1156501] New: Regression: can not use OSC without kwallet
http://bugzilla.suse.com/show_bug.cgi?id=1156501 Bug ID: 1156501 Summary: Regression: can not use OSC without kwallet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Keywords: dogfood Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: werner@suse.com QA Contact: qa-bugs@suse.de CC: fabian@ritter-vogt.de, tchvatal@suse.com Found By: --- Blocker: --- Latest Tumbleweed cause that osc triggers the start of kwalletd5 and this leads to an error | Error when attempting to decrypt the wallet kdewallet using GPG. If you're | using a SmartCard, please ensure it's inserted then try again. | | GPG error was Inappropriate ioctl for device That is I can not set my passphrase anymore. I'm not using KDE, I'm a fvwm2+lsxession user. Without passphrase I can not work on my Tumblweed workstation anymore hence this is critical -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c1 --- Comment #1 from Dr. Werner Fink <werner@suse.com> --- Any way to use gnome-keyring ? This had worked in past whereas kwalletd5 does not -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c2 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |marco.strigl@suse.com |ovo.novell.com | --- Comment #2 from Tomáš Chvátal <tchvatal@suse.com> --- Try changing 'use_keyring = 0' in the oscrc, maybe it would help. Assigning to Marco as he is the owner of osc. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Development Assignee|marco.strigl@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c3 --- Comment #3 from Dr. Werner Fink <werner@suse.com> --- I know that use_keyring = 0 would help but this is a noop! I'ds like to use my keyring. And I guess that it would work even with kwallted5 if this daemon would not try to read a none existing device -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |marco.strigl@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1156518 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c4 Marco Strigl <marco.strigl@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|1156518 | --- Comment #4 from Marco Strigl <marco.strigl@suse.com> --- I am trying to reproduce this. Can you provide your oscrc? (of course without passwords) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c5 --- Comment #5 from Dr. Werner Fink <werner@suse.com> --- Created attachment 823913 --> http://bugzilla.suse.com/attachment.cgi?id=823913&action=edit ~/.oscrc ... without passwords as keyring is used anywhere (In reply to Marco Strigl from comment #4)
I am trying to reproduce this.
Can you provide your oscrc? (of course without passwords)
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c6 --- Comment #6 from Marco Strigl <marco.strigl@suse.com> --- Are you using gnome-keyring as a keyring manager? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c7 --- Comment #7 from Dr. Werner Fink <werner@suse.com> --- (In reply to Marco Strigl from comment #6)
Are you using gnome-keyring as a keyring manager?
Indeed is up and running:
px | grep key werner 13226 0.0 0.0 3564 732 pts/0 S+ 11:52 0:00 grep key werner 10830 0.0 0.1 383948 9448 ? SLl 10:45 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
I can also list passwords with secret-tool(1) on the command line and also use seahorse(1) to list and change my passwords -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c8 --- Comment #8 from Dr. Werner Fink <werner@suse.com> --- Removing kwallted5 cause that osc asks for the password instead of using gnome-keyring -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c9 --- Comment #9 from Dr. Werner Fink <werner@suse.com> --- Installing python3-keyrings.alt does not help either -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c10 --- Comment #10 from Marco Strigl <marco.strigl@suse.com> --- This is fixed with https://github.com/openSUSE/osc/commit/5227e357bcd681e0cc4fc10bce868a4477584... Is released with 0.166.2 (already in openSUSE:Tools) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c11 --- Comment #11 from Swamp Workflow Management <swamp@suse.de> --- This is an autogenerated message for OBS integration: This bug (1156501) was mentioned in https://build.opensuse.org/request/show/748323 Factory / osc -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c18 Michal Koutný <mkoutny@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoutny@suse.com Flags|needinfo?(systemd-maintaine |needinfo?(werner@suse.com) |rs@suse.de) | --- Comment #18 from Michal Koutný <mkoutny@suse.com> --- IIUC, you're missing the a) the socket to session dbus daemon b) the enviroment variable telling the path to that socket. The a) is realized by dbus.socket of the user systedm instance. For other user units b) is done also by dbus.socket. I can't find where is DBUS_SESSION_BUS_ADDRESS set for user sessions though (I guess somewhere in PAM or by display manager (ancestor of user session processes)). Ad a) Is your user systemd instance running? And is dbus.socket active? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c19 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | --- Comment #19 from Dr. Werner Fink <werner@suse.com> --- (In reply to Michal Koutný from comment #18)
IIUC, you're missing the a) the socket to session dbus daemon b) the enviroment variable telling the path to that socket.
The a) is realized by dbus.socket of the user systedm instance. For other user units b) is done also by dbus.socket. I can't find where is DBUS_SESSION_BUS_ADDRESS set for user sessions though (I guess somewhere in PAM or by display manager (ancestor of user session processes)).
Ad a) Is your user systemd instance running? And is dbus.socket active?
On this Tumbleweed I have within the local X11 session printenv | grep BUS DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ynt2mEliSD,guid=db35f32753f024fe55f960705dcab5a0 whereas on Leap I see printenv | grep BUS DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/223/bus well ... now trying ove ssh to Tumbleweed without X11 forward printenv | grep DBUS returns exactly nothing, the same with X11 fowarding. Using a VNC dispaly on the Tumbleweed and an xterm therein I see printenv | grep DBUS DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Q3EYajjIpk,guid=a0fb6beb58aa37222a7682c25dce4d33 but the execution of secret-tool runs into a timeout secret-tool lookup imaps gwmail.nue.novell.com secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached and indeed there is a user systemd running but only for the local X11 display. Not for the ssh nor the VNC login. I'm using for the VNC connection a socjet and serive unit file where in the serivce unit file the PAMName=login and User=werner is used. For ssh connection the /etc/pam.d/sshd includes common-session which starts with the line session optional pam_systemd.so -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c20 --- Comment #20 from Dr. Werner Fink <werner@suse.com> --- I should mention that dbus-launch requires X11 $DISPLAY ... and I really like to know *Why* a dbus launch depend on X11 screen? With ssh secret-tool lookup imaps gwmail.nue.novell.com secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY btw forwarding the X11 display secret-tool lookup imaps gwmail.nue.novell.com secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached Clear as the remote DISPLAY does not provide services on the actual system. Using dbus-run-session with ssh: exec dbus-run-session -- /bin/tcsh -l secret-tool lookup imaps gwmail.nue.novell.com dbus-daemon[17204]: [session uid=223 pid=17204] Activating service name='org.freedesktop.secrets' requested by ':1.0' (uid=223 pid=17225 comm="secret-tool lookup imaps gwmail.nue.novell.com ") gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used secret-tool: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached ... actual no way to work from at home on the current Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c21 --- Comment #21 from Dr. Werner Fink <werner@suse.com> --- The XDG values for the sessions: local display: printenv | grep -E 'XDG_(CURRENT|SESSION)' XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session10 XDG_SESSION_DESKTOP=KDE XDG_SESSION_TYPE=x11 XDG_CURRENT_DESKTOP=FVWM XDG_SESSION_CLASS=user XDG_SESSION_ID=11 ssh without X11 forwarding printenv | grep -E 'XDG_(CURRENT|SESSION)' XDG_SESSION_ID=63 XDG_SESSION_TYPE=tty XDG_SESSION_CLASS=user and with X11 forwarding printenv | grep -E 'XDG_(CURRENT|SESSION)' XDG_SESSION_ID=64 XDG_SESSION_TYPE=tty XDG_SESSION_CLASS=user last but not least a VNC display: printenv | grep -E 'XDG_(CURRENT|SESSION)' XDG_SESSION_TYPE=unspecified XDG_SESSION_CLASS=background XDG_SESSION_COOKIE=noether XDG_SESSION_ID=62 ... is there a way to overwrite session type and class within the vnc service/socket units? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c22 --- Comment #22 from Dr. Werner Fink <werner@suse.com> --- Beside this on the local console (not X11 but /dev/tty1): printenv | grep -E 'XDG_(CURRENT|SESSION)' XDG_SESSION_ID=66 XDG_SESSION_TYPE=tty XDG_SESSION_CLASS=user secret-tool lookup imaps gwmail.nue.novell.com secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY tty /dev/tty1 even on the local system a user is not able to use dbus without X11 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c23 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com --- Comment #23 from Fabian Vogt <fvogt@suse.com> --- (In reply to Dr. Werner Fink from comment #20)
I should mention that dbus-launch requires X11 $DISPLAY ... and I really like to know *Why* a dbus launch depend on X11 screen?
It is meant only for X11. The man page explicitly states:
To start a D-Bus session within a text-mode session, do not use dbus-launch. Instead, see dbus-run-session(1).
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c24 --- Comment #24 from Dr. Werner Fink <werner@suse.com> --- (In reply to Fabian Vogt from comment #23)
(In reply to Dr. Werner Fink from comment #20)
I should mention that dbus-launch requires X11 $DISPLAY ... and I really like to know *Why* a dbus launch depend on X11 screen?
It is meant only for X11. The man page explicitly states:
To start a D-Bus session within a text-mode session, do not use dbus-launch. Instead, see dbus-run-session(1).
I'm aware ... nevertheless, at login regardless if X11 or tty a user local known should be able to do his/her work without calling dbus-run-session(1). And even with dbus-run-session(1) is does currently not work. IMHO this is simply broken by design. Is there a way to cause pam_system(.so) to use path=/run/user/<pid>/bus for dbus connections regardless what interface is used, that for X11 *and* tty. And, if not running on path=/run/user/<pid>/bus, simply start the dbus for any user session regardless what type is used. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c25 --- Comment #25 from Michal Koutný <mkoutny@suse.com> --- I'm getting slightly lost. Can this be pinpointed to a particular (pam, systemd, dbus,...) update or it only became visible because of the osc client update? (In reply to Dr. Werner Fink from comment #24)
Is there a way to cause pam_system(.so) to use path=/run/user/<pid>/bus for dbus connections regardless what interface is used, that for X11 *and* tty. On my TW it works (I use gdm). The socket itself is started by the user instance and the environment variable is (likely) set by pam_systemd [1].
Such a socket is recognizable by residing under /run/user/$UID/bus. I guess the /tmp placed socket is created by display manager in xinitrc. [1] https://github.com/openSUSE/systemd/blob/SUSE/v243/src/login/pam_systemd.c#L... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c26 --- Comment #26 from Dr. Werner Fink <werner@suse.com> --- (In reply to Michal Koutný from comment #25)
I'm getting slightly lost. Can this be pinpointed to a particular (pam, systemd, dbus,...) update or it only became visible because of the osc client update?
I had done a `zypper dup' and ru into this problem with osc on local X11 display ... and lateron I noticed that I can not work from at home on the same Tumbleweed system anymore. Only the Leap system is usable.
(In reply to Dr. Werner Fink from comment #24)
Is there a way to cause pam_system(.so) to use path=/run/user/<pid>/bus for dbus connections regardless what interface is used, that for X11 *and* tty. On my TW it works (I use gdm). The socket itself is started by the user instance and the environment variable is (likely) set by pam_systemd [1].
Such a socket is recognizable by residing under /run/user/$UID/bus. I guess the /tmp placed socket is created by display manager in xinitrc.
I'm talking on ssh and VNC connections as well as login on /dev/tty1, not local X11 display. Can you access your keyring (gnome or kwalletd) with login over ssh, VNC or simply on local console tty1?
[1] https://github.com/openSUSE/systemd/blob/SUSE/v243/src/login/pam_systemd.c#L...
Yep ... I have read this also ... and pam_sm_open_session() -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c27 --- Comment #27 from Dr. Werner Fink <werner@suse.com> --- Hmmm ... I've added a line echo "Xsession: $DBUS_SESSION_BUS_ADDRESS" 1>&2 very first in /etc/X11/xdm/Xsession and a line echo "~/.xsession: $DBUS_SESSION_BUS_ADDRESS" 1>&2 very first in my ~/.xsession aka ~/.xinitrc and see Xsession: ~/.xsession: unix:abstract=/tmp/dbus-jG9lBsTQkx,guid=d755e5ba6e52c8e3e109d6155dce6f9b in ~/.local/share/sddm/xorg-session.log ... that is that the sddm comes without dbus connection and this triggers the script /etc/X11/xdm/scripts/20-dbus I guess. -- You are receiving this mail because: You are on the CC list for the bug.
I'm talking on ssh and VNC connections as well as login on /dev/tty1, not local X11 display. I know, AFAIU, all these logins/sessions should ensure dbus session running
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c28 --- Comment #28 from Michal Koutný <mkoutny@suse.com> --- (In reply to Dr. Werner Fink from comment #26) through pam_systemd :-/
Can you access your keyring (gnome or kwalletd) with login over ssh, VNC or simply on local console tty1? I can "access" gnome-keyring-daemon on tty1. Also if I `systemctl --user stop dbus.service`, I can see it gets reactivated, i.e. DBus communication works fine. The keyring is locked though (perhaps to lack of pam_gnome_keyring in tty PAM stack).
Idea: you see a timeout message, what if you connect to keyring daemon just fine but the unlock prompt displays on X server that you don't see. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c29 --- Comment #29 from Dr. Werner Fink <werner@suse.com> --- Ohmm ... systemctl --user status dbus.socket * dbus.socket - D-Bus User Message Bus Socket Loaded: loaded (/usr/lib/systemd/user/dbus.socket; static; vendor preset: disabled) Active: inactive (dead) Listen: /run/user/223/bus (Stream) ... that seems to be a part of the problem, but dbus.socket is linked below /usr/lib/systemd/user/sockets.target.wants/ Also set debug on pam_systemd.so in common-session to see more: Nov 15 10:51:01 noether sddm-helper[23902]: [PAM] Starting... Nov 15 10:51:01 noether sddm-helper[23902]: [PAM] Authenticating... Nov 15 10:51:01 noether sddm-helper[23902]: gkr-pam: unable to locate daemon control file Nov 15 10:51:01 noether sddm-helper[23902]: [PAM] Preparing to converse... Nov 15 10:51:01 noether sddm-helper[23902]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate Nov 15 10:51:01 noether sddm-helper[23902]: [PAM] Conversation with 1 messages Nov 15 10:51:01 noether sddm-helper[23902]: [PAM] returning. Nov 15 10:51:01 noether sddm[2224]: Authenticated successfully Nov 15 10:51:01 noether sddm-greeter[23827]: Message received from daemon: LoginSucceeded Nov 15 10:51:01 noether sddm-helper[23902]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Nov 15 10:51:01 noether sddm-helper[23902]: pam_systemd(sddm:session): pam-systemd initializing Nov 15 10:51:01 noether sddm-helper[23902]: pam_systemd(sddm:session): Asking logind to create session: uid=223 pid=23902 service=sddm type=x11 class=user desktop=KDE seat=seat0 vtnr=7 tty= display=:0 remote=no remote_user= remote_host= Nov 15 10:51:01 noether sddm-helper[23902]: pam_systemd(sddm:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a Nov 15 10:51:01 noether systemd[1]: Created slice User Slice of UID 223. Nov 15 10:51:01 noether systemd[1]: Starting User Runtime Directory /run/user/223... Nov 15 10:51:01 noether systemd-logind[2163]: New session 71 of user werner. Nov 15 10:51:01 noether systemd[1]: Started User Runtime Directory /run/user/223. Nov 15 10:51:01 noether systemd[1]: Starting User Manager for UID 223... Nov 15 10:51:01 noether sddm-helper[23819]: [PAM] Closing session Nov 15 10:51:01 noether sddm-helper[23819]: pam_unix(sddm-greeter:session): session closed for user sddm Nov 15 10:51:01 noether sddm-helper[23819]: pam_kwallet5(sddm-greeter:session): pam_kwallet5: pam_sm_close_session Nov 15 10:51:01 noether sddm-helper[23819]: [PAM] Ended. Nov 15 10:51:01 noether sddm[2224]: Auth: sddm-helper exited successfully Nov 15 10:51:01 noether sddm[2224]: Greeter stopped. Nov 15 10:51:01 noether systemd-logind[2163]: Session 70 logged out. Waiting for processes to exit. Nov 15 10:51:01 noether systemd[23907]: pam_systemd(systemd-user:session): pam-systemd initializing Nov 15 10:51:01 noether systemd[23907]: pam_unix(systemd-user:session): session opened for user werner(uid=223) by (uid=0) Nov 15 10:51:01 noether systemd[23907]: pam_kwallet5(systemd-user:session): (null): pam_sm_open_session Nov 15 10:51:01 noether systemd[23907]: pam_kwallet5(systemd-user:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. Nov 15 10:51:01 noether systemd[23907]: Reached target Paths. Nov 15 10:51:01 noether systemd[23907]: Reached target Timers. Nov 15 10:51:01 noether systemd[23907]: dbus.socket: Socket service dbus.service not loaded, refusing. Nov 15 10:51:01 noether systemd[23907]: Failed to listen on D-Bus User Message Bus Socket. Indeed: systemctl --user status dbus.service Unit dbus.service could not be found. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c30 --- Comment #30 from Dr. Werner Fink <werner@suse.com> --- Found the culprit ... it was a leftover of a test for dbus-broker now two years back: ll /etc/systemd/user/dbus.service lrwxrwxrwx 1 root root 41 Oct 10 2018 /etc/systemd/user/dbus.service -> /usr/lib/systemd/user/dbus-broker.service and /usr/lib/systemd/user/dbus-broker.service had not exist anmymore after the zypper dup. And new systemd had not ignored the broken link but marked the dbus.service as not loaded (but without hinting why it has not loaded). After removing the dangling symlink and reboot (as a simple daemon-reload had not helpd out), things are now working ... OK I had also removed the crediential lines from my ~/.oscrc so that it use the gnome-keyring (btw. the error message of kwalletd5 still remains with the not existing SmartCard). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c32 jun wang <junguo.wang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |junguo.wang@suse.com --- Comment #32 from jun wang <junguo.wang@suse.com> --- Created attachment 832176 --> http://bugzilla.suse.com/attachment.cgi?id=832176&action=edit osc config for the test case got a errer to run "osc ls" or "osc build" after updating osc to 0.167.2 on SLES15SP1. test case: ========================================================================== $ osc ls No user found in section https://api.opensuse.org Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 No user found in section https://api.suse.de Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python3.6/site-packages/osc/babysitter.py", line 62, in run return prg.main(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 418, in do_list for prj in meta_get_project_list(apiurl, opts.deleted): File "/usr/lib/python3.6/site-packages/osc/core.py", line 3490, in meta_get_project_list u = makeurl(apiurl, ['source'], query) File "/usr/lib/python3.6/site-packages/osc/core.py", line 3307, in makeurl if conf.config['verbose'] > 1: TypeError: '>' not supported between instances of 'str' and 'int' $ osc -A extern build --download-api-only --root /abuild/oscbuild/openSUSE_Leap_15.1 openSUSE_Leap_15.1 --local-package No user found in section https://api.opensuse.org Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 No user found in section https://api.suse.de Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python3.6/site-packages/osc/babysitter.py", line 62, in run return prg.main(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 6479, in do_build args = self.parse_repoarchdescr(args, opts.noinit or opts.offline, opts.alternative_project, False, opts.vm_type, opts.multibuild_package) File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 6142, in parse_repoarchdescr repositories = list(get_repos_of_project(apiurl, project)) File "/usr/lib/python3.6/site-packages/osc/core.py", line 5665, in get_repos_of_project f = show_project_meta(apiurl, prj) File "/usr/lib/python3.6/site-packages/osc/core.py", line 3518, in show_project_meta url = makeurl(apiurl, ['source', prj, '_meta']) File "/usr/lib/python3.6/site-packages/osc/core.py", line 3307, in makeurl if conf.config['verbose'] > 1: TypeError: '>' not supported between instances of 'str' and 'int' howerver, running the above commands again, they both work well. based on the above error, I think this bug was NOT fixed completely. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c33 --- Comment #33 from Marco Strigl <marco.strigl@suse.com> --- (In reply to jun wang from comment #32)
Created attachment 832176 [details] osc config for the test case
got a errer to run "osc ls" or "osc build" after updating osc to 0.167.2 on SLES15SP1.
test case: ==========================================================================
$ osc ls
No user found in section https://api.opensuse.org Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 No user found in section https://api.suse.de Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python3.6/site-packages/osc/babysitter.py", line 62, in run return prg.main(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 418, in do_list for prj in meta_get_project_list(apiurl, opts.deleted): File "/usr/lib/python3.6/site-packages/osc/core.py", line 3490, in meta_get_project_list u = makeurl(apiurl, ['source'], query) File "/usr/lib/python3.6/site-packages/osc/core.py", line 3307, in makeurl if conf.config['verbose'] > 1: TypeError: '>' not supported between instances of 'str' and 'int'
$ osc -A extern build --download-api-only --root /abuild/oscbuild/openSUSE_Leap_15.1 openSUSE_Leap_15.1 --local-package No user found in section https://api.opensuse.org Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 No user found in section https://api.suse.de Please enter new credentials. Username: jgwang Password: 1) SecretService Keyring (Backend provided by python-keyring) 2) fail Keyring (Backend provided by python-keyring) 3) kwallet DBusKeyring (Backend provided by python-keyring) 4) kwallet DBusKeyringKWallet4 (Backend provided by python-keyring) 5) Config file credentials manager (Store the credentials in the config file (plain text)) 6) Obfuscated Config file credentials manager (Store the credentials in the config file (obfuscated)) 7) Transient password store (Do not store the password and always ask for the password) Select credentials manager: 7 Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python3.6/site-packages/osc/babysitter.py", line 62, in run return prg.main(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python3.6/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 6479, in do_build args = self.parse_repoarchdescr(args, opts.noinit or opts.offline, opts.alternative_project, False, opts.vm_type, opts.multibuild_package) File "/usr/lib/python3.6/site-packages/osc/commandline.py", line 6142, in parse_repoarchdescr repositories = list(get_repos_of_project(apiurl, project)) File "/usr/lib/python3.6/site-packages/osc/core.py", line 5665, in get_repos_of_project f = show_project_meta(apiurl, prj) File "/usr/lib/python3.6/site-packages/osc/core.py", line 3518, in show_project_meta url = makeurl(apiurl, ['source', prj, '_meta']) File "/usr/lib/python3.6/site-packages/osc/core.py", line 3307, in makeurl if conf.config['verbose'] > 1: TypeError: '>' not supported between instances of 'str' and 'int'
howerver, running the above commands again, they both work well. based on the above error, I think this bug was NOT fixed completely.
This has nothing to do with the original bug. Please open a new bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c34 --- Comment #34 from jun wang <junguo.wang@suse.com> --- (In reply to Marco Strigl from comment #33)
(In reply to jun wang from comment #32)
This has nothing to do with the original bug. Please open a new bug.
OK, I see. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c35 --- Comment #35 from jun wang <junguo.wang@suse.com> --- (In reply to jun wang from comment #34)
(In reply to Marco Strigl from comment #33)
This has nothing to do with the original bug. Please open a new bug.
I have reported a new bug https://bugzilla.suse.com/show_bug.cgi?id=1166051 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c36 --- Comment #36 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2020:0627-1: An update that has 5 recommended fixes can now be installed. Category: recommended (important) Bug References: 1136584,1137477,1154972,1155953,1156501 CVE References: Sources used: SUSE Linux Enterprise Module for Development Tools 15-SP1 (src): osc-0.167.2-3.12.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1156501 http://bugzilla.suse.com/show_bug.cgi?id=1156501#c37 --- Comment #37 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-RU-2020:0344-1: An update that has 5 recommended fixes can now be installed. Category: recommended (important) Bug References: 1136584,1137477,1154972,1155953,1156501 CVE References: Sources used: openSUSE Leap 15.1 (src): osc-0.167.2-lp151.2.9.1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1156501 https://bugzilla.suse.com/show_bug.cgi?id=1156501#c39 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- OS|openSUSE Factory |All --- Comment #39 from Swamp Workflow Management <swamp@suse.de> --- SUSE-SU-2022:4351-1: An update that solves two vulnerabilities, contains one feature and has 22 fixes is now available. Category: security (important) Bug References: 1089025,1097996,1122675,1125243,1126055,1126058,1127932,1129757,1129889,1131512,1136584,1137477,1138165,1138977,1140697,1142518,1142662,1144211,1154972,1155953,1156501,1160446,1166537,1173926 CVE References: CVE-2019-3681,CVE-2019-3685 JIRA References: OBS-203 Sources used: SUSE Linux Enterprise Software Development Kit 12-SP5 (src): osc-0.182.0-15.12.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com