sudo segmentation fault [ubuntu 8.10]

Bug #309325 reported by jarondl
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
Invalid
Undecided
Rolf Leggewie

Bug Description

Binary package hint: sudo

I'm using ubuntu 8.10
Sudo version 1.6.9p17-1ubuntu2

When using sudo it returns "Segmentation fault" after entering the password.
If I don't enter any password it goes to prompt without even saying "Sorry, try again"
However, if do I enter a wrong password, it does go "Sorry, try again"

It doesn't matter what command I'm entering (i.e even 'sudo ls')
gksudo doesn't work, and returns nothing at all.

Please help, I'm stuck without rights on my own computer

EDIT:
It turns out the problem is with pam. After rebooing I couldn't login at all.. purging samba and samba-common solved the problem for now.
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/292791/comments/27

jarondl (jarondl)
description: updated
jarondl (jarondl)
description: updated
Revision history for this message
Bryce Anderson (bryce--anderson) wrote :

Im still pretty now to this, but how did you purge samba without being able to do a sudo command? I'm having the same trouble...

Revision history for this message
jarondl (jarondl) wrote :

That's a good point.
You have to restart, and get to the GRUB menu (mostly done by hitting ESC during boot)
Then you choose the entry that has (Recovery) on it.
When asked what you wish to do, choose "get Root shell" or something like that.
Well, that should give your root rights, and then you can "apt-get purge samba samba-common"
Good luck!

Revision history for this message
Matthias Blümel (blaimi) wrote :

Thanks! I wouldn't search the error at samba.... but its not a problem with samba, its only a problem with libpam-smbpass. After uninstalling with 'apt-get purge libpam-smbpass' it worked.

sorry for bad english

Blaimi

Revision history for this message
Matthias Blümel (blaimi) wrote :

if you are purging samba, samba-common, samba-client and libpam-smbpass, you can install it again, and it works:

boot into recovery mode and type
"apt-get purge -y samba samba-common samba-client libpam-smbpass && apt-get install -y samba libpam-smbpass"

now it should work again.

Revision history for this message
Michael Gefen (gefenm11) wrote :

latest update of sudo, caused this issue to reappear.
thank for the solution

Revision history for this message
Charles Albert MArtins dos Anjos (charles-ccomp) wrote :

Hello! At first i've started having segfaults when trying to sudo, then i've restarted my machine and could not login at all. To solve this i've entered recovery mode, opened the root prompt and used this command "apt-get purge -y samba samba-common samba-client libpam-smbpass && apt-get install -y samba libpam-smbpass". The problem its gone, but now i have another error: when i log using gdm, after entering my password, a dialog box appears with the word "Error!" and a "OK" button, and when i click "OK" the system starts just fine. Also, when trying to sudo, i get an "Error", but it still works. Yet also, there is the app System->Administration->Users and Groups which have a error: when trying to unlock it, it locks the window for some seconds, then appears with the dialog box: "Coud not authenticate - An unexpected error has occured" with a Close button. When closing it, the window locks and freezes, and the "Wait or Force Close" dialog appears. Anyone else with these problems?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

does this ever occur in trusty or later?

Changed in sudo (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in sudo (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.