Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30152 - [pam] 1.1.5-4 break sudo?

Attached to Project: Arch Linux
Opened by Yichao Yu (yuyichao) - Wednesday, 06 June 2012, 11:10 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 09 June 2012, 00:23 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
after upgrade to 1.1.5-4, sudo stop working and keep telling me the password is incorrect (which is not true.)

(plz tell me if I can provide any other information (don't know where to look at))


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 09 June 2012, 00:23 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Wednesday, 06 June 2012, 11:55 GMT
Stop using --force with upgrades and you won't have files missing afterwards. Reinstall pambase.
Comment by Yichao Yu (yuyichao) - Friday, 08 June 2012, 23:47 GMT
  • Field changed: Percent Complete (100% → 0%)
I never use -f option if not necessary and reinstall pam/pambase does NOT solve the problem. (reinstall-> downgrade to -3, remove pambase and reinstall both.)
Comment by Dave Reisner (falconindy) - Friday, 08 June 2012, 23:47 GMT
Sure, I'll humor you. The only reason this has come up before is because people nuked their /etc/pam.d/other in the upgrade due to usage of --force.

Post your pacman.log and the output of 'pacman -Qk pam pambase' if you still can't figure it out.
Comment by Yichao Yu (yuyichao) - Saturday, 09 June 2012, 00:18 GMT
THX and it's fine just now. I checked my pacman.log and found out I have to use -f due to filesystem upgrade~~~

and somehow after doing EXACTLY the same thing this morning (reinstall both) it starts working. (I did notice 'other' is missing but adding it back doesn't work last time either~)

Is this a bug of pacman that -f will cause files missing that is not really conflict?

Sorry for the noise =D

Loading...