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!
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!
FS#28595 - sudo 1.8.4-1 causes sudo/gksudo to fail
Attached to Project:
Arch Linux
Opened by Douglas McFadzean (ninian) - Wednesday, 22 February 2012, 22:37 GMT
Last edited by Allan McRae (Allan) - Friday, 24 February 2012, 12:11 GMT
Opened by Douglas McFadzean (ninian) - Wednesday, 22 February 2012, 22:37 GMT
Last edited by Allan McRae (Allan) - Friday, 24 February 2012, 12:11 GMT
|
DetailsDescription:
Sudo and gksudo from the sudo-1.8.4-1 package fail with me, often producing a 'cannot open display' error, regardless of whether I have 'Defaults env_keep += "HOME"' in /etc/sudoers or not. Happens with any program I'm trying to run. Downgrading to sudo-1.8.3.p2-2 makes everything work again as expected. Additional info: * sudo-1.8.4-1-i686.pkg.tar.xz fails * sudo-1.8.3.p2-2-i686.pkg.tar.xz works |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 24 February 2012, 12:11 GMT
Reason for closing: Fixed
Additional comments about closing: sudo 1.8.4.p1-1
Friday, 24 February 2012, 12:11 GMT
Reason for closing: Fixed
Additional comments about closing: sudo 1.8.4.p1-1
Since the upgrade, neither yaourt nor "sudo pacman" were able to reach the network when invoked from my regular account, although they worked fine when invoked from the root account. I eventually tracked the issue to the fact that the proxy environment variable were ignored (sudo sh -c "export | grep -i proxy" didn't show anything).
For me too, downgrading to 1.8.3.p2-2 fixed the issue.