[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
Each line now has user="*" or uses extended user control and the problem disappeared. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I have the very same problem using LDAP authentication (not Windows active directory. I have a few user="*" but user="" would disable the mount, wouldn't it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
Finally, I add the name of the user that can mount the shared folder and it works : With is the Windows user name and is the Active Directory domain name. (I tried with user="%(USER)" but it doesn't work at all) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I posted a bug report on https://sourceforge.net/p/pam-mount/bugs/123/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I found a (bad ?) solution. I keep pam_mount in /etc/pam.d/common- session file : session optional pam_mount.so and I add user="" in /etc/security/pam_mount.conf.xml file : And it works !??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
In fact, the problem doesn't appear since I added my Linux Mint MATE 18.2 computer into a Windows domain but since I added pam_mount in /etc/pam.d/common-session : session optional pam_mount.so If I remove this line, it works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
Same error when lauching Synaptic (synaptic-pkexec), since I added my Linux Mint MATE 18.2 computer into a Windows 2003 domain with realm (kerberos, sssd). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
Same problem on 16.04 LTS (Ubuntu Xenial). No clue except i am using pam_mount. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I 'm now having this problem on 16.04 (Mint 18.1), I suspect it may be related to adding ldap and sssd caching, but it's unclear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I'm also having the problem on Ubuntu 16.04 with kerberos authentication. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I got the same problem on Ubuntu 16.04, pkexec just doesn't work after entering password Exemple : pkexec gedit ** ERROR:pkexec.c:138:pam_conversation_function: code should not be reached Abandon ** Changed in: policykit (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I had the same problem, it looks like pexec is no more working on recent Ubuntu version. It was generating a lot of crash windows at startup. A quick and dirty fix (no more errors at least): # sudo mv /usr/bin/pkexec /usr/bin/pkexec.old # sudo ln -s /usr/bin/gksudo /usr/bin/pkexec Sincerely Technical Details: ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sat Nov 9 14:35:29 2013 DistroRelease: Ubuntu 13.10 ExecutablePath: /usr/bin/pkexec ExecutableTimestamp: 1379527177 ProcCmdline: pkexec /usr/lib/update-notifier/package-system-locked ProcCwd: /home/mystercoco ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.UTF-8 LANGUAGE=fr_FR XDG_RUNTIME_DIR= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
I had the same problem, it looks like pexec is no more working on recent Ubuntu version. It was generating a lot of crash windows at startup. A quick and dirty fix (no more errors at least): # sudo mv /usr/bin/pkexec /usr/bin/pkexec.old # sudo ln -s /usr/bin/sudo /usr/bin/pkexec Sincerely Technical Details: ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sat Nov 9 14:35:29 2013 DistroRelease: Ubuntu 13.10 ExecutablePath: /usr/bin/pkexec ExecutableTimestamp: 1379527177 ProcCmdline: pkexec /usr/lib/update-notifier/package-system-locked ProcCwd: /home/mystercoco ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.UTF-8 LANGUAGE=fr_FR XDG_RUNTIME_DIR= ** Changed in: policykit (Ubuntu) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875402] Re: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached
It seems only affected me, and I'm not using fprint now, so I'm not suffering this problem. No idea whether it is still an issue in new releases. ** Changed in: policykit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875402 Title: pkexec fails with ERROR:pkexec.c:138:pam_conversation_function: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/875402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
