http://bugzilla.opensuse.org/show_bug.cgi?id=1117236 Bug ID: 1117236 Summary: displaycal: Unknown problem downloading profiles Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- DisplayCal is asking for a password when I want to install the sensor profiles for all users. However it does not tell me which password it actually wants. I tried my own password, then it says it failed and asks again. If I enter the root password, it says it failed, and does not ask again. It's not obvious from the syslog what happens. However when I open the protocol windows, I see some messages that seem unexpected: 17:55:26,908 displaycal 3.5.3.0 2018-04-25T13:36:17.988513Z 17:55:26,911 x86_64 17:55:26,911 Python 2.7.14 (default, Oct 12 2017, 15:50:02) [GCC] 17:55:26,911 ImportError: No module named faulthandler 17:55:26,931 /usr/lib64/python2.7/site-packages/wx-3.0-gtk2/wx/_core.py:16629: UserWarning: 17:55:26,931 wxPython/wxWidgets release number mismatch 17:55:26,988 wxPython 3.0.2.0 gtk2 (classic) [...] Possibly the command sudo is trying to execute is "COMMAND=list /usr/bin/oeminst -?", and that returns an error staus. Maybe that's the reason why things do not work. The other odd thing are these messages: Nov 25 17:45:27 i7.site sudo[4570]: windl : TTY=pts/0 ; PWD=/home/windl ; USER=root ; COMMAND=/usr/bin/true Nov 25 17:45:27 i7.site sudo[4570]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice Nov 25 17:45:27 i7.site sudo[4570]: pam_unix(sudo:session): session opened for user root by (uid=0) Nov 25 17:45:27 i7.site sudo[4570]: pam_unix(sudo:session): session closed for user root Nov 25 17:45:27 i7.site sudo[4573]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/1 ruser=windl rhost= user=windl Nov 25 17:45:29 i7.site sudo[4573]: gkr-pam: couldn't get the password from user: Kommunikationsfehler Nov 25 17:45:29 i7.site sudo[4573]: pam_unix(sudo:auth): auth could not identify password for [windl] Nov 25 17:45:29 i7.site sudo[4573]: windl : 1 incorrect password attempt ; TTY=pts/1 ; PWD=/home/windl ; USER=root ; COMMAND=list /usr/bin/oeminst -? [...] Nov 25 18:08:10 i7.site sudo[6813]: windl : TTY=pts/2 ; PWD=/home/windl ; USER=root ; COMMAND=/usr/bin/true Nov 25 18:08:10 i7.site sudo[6813]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice Nov 25 18:08:10 i7.site sudo[6813]: pam_unix(sudo:session): session opened for user root by (uid=0) Nov 25 18:08:10 i7.site sudo[6813]: pam_unix(sudo:session): session closed for user root Nov 25 18:08:10 i7.site sudo[6864]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/3 ruser=windl rhost= user=windl Nov 25 18:08:12 i7.site sudo[6864]: gkr-pam: couldn't get the password from user: Kommunikationsfehler Nov 25 18:08:12 i7.site sudo[6864]: pam_unix(sudo:auth): auth could not identify password for [windl] Nov 25 18:08:12 i7.site sudo[6864]: windl : 1 incorrect password attempt ; TTY=pts/3 ; PWD=/home/windl ; USER=root ; COMMAND=list /usr/bin/oeminst -? And earlier: Nov 25 18:05:51 i7.site gnomesu-pam-backend[6479]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control Which is (IMHO) nonsense: # ll /run/user/1000/keyring/control srwxr-xr-x 1 windl users 0 25. Nov 17:06 /run/user/1000/keyring/control windl@i7:~> id uid=1000(windl) gid=100(users) Gruppen=100(users),20(cdrom),468(vboxusers) windl@i7:~> stat /run/user/1000/keyring/control Datei: /run/user/1000/keyring/control Größe: 0 Blöcke: 0 EA Block: 4096 Socket Gerät: 2dh/45d Inode: 32645 Verknüpfungen: 1 Zugriff: (0755/srwxr-xr-x) Uid: ( 1000/ windl) Gid: ( 100/ users) Zugriff : 2018-11-25 17:06:38.144582874 +0100 Modifiziert: 2018-11-25 17:06:35.856582844 +0100 Geändert : 2018-11-25 17:06:35.856582844 +0100 Geburt : - Sorry, if this may be different issues leading to the result I'm experiencing, but I'm somewhat clueless. Another message that is not directly related to this issue is: Nov 25 18:12:03 i7.site /usr/lib/gdm/gdm-x-session[3025]: Window manager warning: Window 0x4200647 (Colorimete) sets an MWM hint indicating it isn't resizable, but sets min size 393 x 181 and max size 134217727 x 134217727; this doesn't make much sense. -- You are receiving this mail because: You are on the CC list for the bug.