>Do you get any log messages in /var/log/auth.log that match up with this segfault?
No, nothing in auth.log
> If not, can you reproduce it when running 'sudo -s' from a root shell? (This would let us get a backtrace from sudo using gdb)
I'm not sure if I've got you right, here is what I did:
- Open terminal -> sudo -s -> got a root shell
- Change common-auth and common-password back to the "old" version
- went back to the root shell and typed 'sudo -s'
Here is what I got in the root shell:
root@my_username_desktop:~# sudo -s
root@my_username-desktop:~#
This is the corresponding entry in auth.log
Nov 19 18:31:09 my_username-desktop sudo: root : TTY=pts/0 ; PWD=/home/my_username ; USER=root ; COMMAND=/bin/bash
No problem :)
>Do you get any log messages in /var/log/auth.log that match up with this segfault?
No, nothing in auth.log
> If not, can you reproduce it when running 'sudo -s' from a root shell? (This would let us get a backtrace from sudo using gdb)
I'm not sure if I've got you right, here is what I did:
- Open terminal -> sudo -s -> got a root shell
- Change common-auth and common-password back to the "old" version
- went back to the root shell and typed 'sudo -s'
Here is what I got in the root shell: username_ desktop: ~# sudo -s username- desktop: ~#
root@my_
root@my_
This is the corresponding entry in auth.log my_username ; USER=root ; COMMAND=/bin/bash
Nov 19 18:31:09 my_username-desktop sudo: root : TTY=pts/0 ; PWD=/home/