On ubuntu 13.04, problem appear again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/86843
Title:
modifying PAM configuration could break gksu
To manage notifications about this bug go to:
with
gksu 2.0.2-6ubuntu2
fprintd 0.4.1-5-g73eda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/86843
Title:
modifying PAM configuration could break gksu
To manage notifications about this bug go
** Tags added: patch-forwarded-upstream
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As per a discussion with David Jurenka, the underlying problems
associated with this bug are still there. ThinkFinger does mostly work
(although gksu will only ask for your password, your fingerprint can
also be given), but it has to violate PAM's policy against threading.
Other fingerprint
I use karmic, should I update some unstable packages for to have the fix?
Like mr_tijn for some admin tools started from menu (see update-manager,
synaptic,..) the credential panel is not shown
Note I use fprint libraries for fingerprint
thanks
--
modifying PAM configuration could break gksu
@jedioetzi you still experience this bug? What does your /etc/pam.d
/auth-common look like? You shouldn't have to update to any unstable
packages, just the latest version of Karmic works for me.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received
Yeah this is fixed for me in Karmic. Marking as fix released. If anyone
else still gets this bug, feel free to reopen.
** Changed in: gksu (Ubuntu)
Status: Triaged = Fix Released
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug
I think this issue has been solved in the current version of gksu and the bug
could be closed
For the interested the details can be found here:
http://www.sudo.ws/bugs/show_bug.cgi?id=180
This bug is not an issue for me any more, can someone else confirm this?
--
modifying PAM configuration
** Changed in: gksu (Ubuntu)
Status: Confirmed = Triaged
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: glob2-bugs #19132
http://savannah.nongnu.org/bugs/?19132
** Also affects: gksu via
http://savannah.nongnu.org/bugs/?19132
Importance: Unknown
Status: Unknown
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received
i can confirm it does not work out of the box
i am using a rather fresh hardy install on a thinkpad r52, and installed
thinkfinger using procedure for hardy from thinkwiki
(ie using ubuntu provided packages)
same results as Adrian:
it will work from command line eg sudo update-manager
but not
Using Hardy's sudo, gksu and thinkfinger packages, it's working out-of-
the-box. I think, this bug report can be closed.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Whoopie : This working with another laptop different one to thinkpad?
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can anyone duplicate this using the ubuntu provided thinkfinger
packages?
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It seems a little worse in hardy. For me, when the gksu just did not
work when the PAM configuration was modified. No matter how many times i
tried to launch synaptic from the menu it just would not launch. When I
launched it from the command prompt using sudo it worked. I tried
Uzahnd's solution
I guess I really should mention that I grabbed and installed Erik's deb,
and it started working, even without the change to the Defaults.
Thanks, Erik, for supplying the deb.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification
I have the same problem using fprint (http://reactivated.net/fprint) on Hardy
Heron RC.
Pending a solution, I restored the original common-auth and use the login
through fingerprint reader only for the GDM (no sudo or gksu).
--
modifying PAM configuration could break gksu
Can anyone duplicate this problem in hardy? I'm fairly sure this is
fixed now.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I went ahead and compiled sudo 1.6.9p14 from source, and created a deb
using checkinstall. Then, I simply installed it, updating the current
sudo version from the repository. Then, I changed the Defaults in my
sudoers file by typing `sudo visudo`:
Defaults
After a couple of difficulties in editing the sudoers file, (basically
learning vim) I got it working according to the directions posted.
Thanks for the fix. One thing to note: although the gksu password
prompt does not ask for a fingerprint, it will accept the fingerprint.
Hope they update this
I've been wanting a solution for this for some time, since it would be
nice to be able to not only log in by swiping my finger, but get to the
network management dialog with it - since I use my laptop at home and at
work, needing to change network profiles between the two.
I've just been looking
+1
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I am experiencing the problem as well. Hopefully a fix can be found for
this, because the fingerprint functionality is quite useful, and this is
a major annoyance.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because
I'm just commenting to raise the importance of the bug (instead of
reporting a duplicate). Let's hope it gets fixed soon.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I can confirm this fails under Gutsy as well when using pam_winbind.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
That's a nice and simple patch - however, the fact remains that the
whole implementation of gksu is flawed: it is a wrapper around sudo,
under the assumption that sudo does not use any other PAM but the
default. For example, gdm correctly shows Password or swipe finger -
as gksudo should. This
One idea is that every program is free to set its prompt for the terminal (e.g.
Password or swipe your finger: ) but use the traditional Password: elsewhere
(e.g. for graphical environment).
You can find a patch for the pam_thinkfinger.c attached.
** Attachment added: Different promtpt for
The underlying problem is still with sudo/gksu - it should be able to
take into account prompts other than Password:!
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
This problem can be solved by changing the password prompt in
/pam/pam_thinkfinger.c from Password or swipe finger: to a simple
Password: (Tested on Ubuntu feisy with thinkfinger0.3).
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug
I would also like to add that I've been trying with the bioapi implementation -
with the UBEK binary driver and pam_bioapi - which seems to be slightly more
successful.
The UBEK binary driver implements a (ugly, but functional) fingerprint dialog
(rather than relying on the user application to
I am also experiencing this bug. I have a IBM Thinkpad X41, and running
the latest version of Feisty, clean installed, and using thinkfinger,
following the guide on the Ubuntu wiki.
Logging in via gdm works fine.
sudo from a terminal works fine.
gksudo does not appear - and even after swiping a
Bug #52018 might be a duplicate of this bug.
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
On my installation of Feisty, gksu is unusable as well as invisible,
e.g. if I scan my finger when invisible, things won't start at all. In
fact I have to do killall gksu for things to happen, and if I then try
again to start things, I either get a password-prompt (not with or scan
your finger -
I can confirm this too. But starting a application which starts gksu
such as synaptic will prompt up gksu and ask you for the password
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs,
starting a application twice!! ... sorry for that
--
modifying PAM configuration could break gksu
https://bugs.launchpad.net/bugs/86843
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gksu (Ubuntu)
Importance: Undecided = Medium
--
modifying PAM configuration could break gksu
https://launchpad.net/bugs/86843
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Upstream bug: http://savannah.nongnu.org/bugs/?19132
Unfortunately, Launchpad doesn't yet support Savannah.
--
modifying PAM configuration could break gksu
https://launchpad.net/bugs/86843
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can confirm this.
dpkg -l gksu
ii gksu 1.9.3-1ubuntu2
** Changed in: gksu (Ubuntu)
Status: Unconfirmed = Confirmed
--
modifying PAM configuration could break gksu
https://launchpad.net/bugs/86843
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
38 matches
Mail list logo
