Description of problem: I ran with up2date --nosig from a recent version of up2date it told me there was a new version in the channel and offered to just update that version of up2date, and I said yes when it tried to restart up2date, I got the help message $ up2date --nosig New Up2date available Restarting up2date $ Xlib: connection to ":0.0" refused by server Xlib: No protocol specified No interactive mode available Please specify either -l, -u, --nox, or package names as command line arguments.usage: up2date [OPTIONS] [<packages>] (blah blah blah) ... yes, I am going through userhelper Version-Release number of selected component (if applicable): updating from up2date-3.9.24-1 -> up2date-3.9.25-2 How reproducible: reliably Steps to Reproduce: 1. install up2date-3.9.24-1 2. run up2date --nosig as a normal user (--nosig may not be required) 3. accept updating to new version of up2date from RHN 4. profit!
fixed in cvs, should land in 3.1.26 or so
Presumably ^3.1.26^3.9.26^. Also this bug is a duplicate of Bug 103185.
Happened again this morning up2dateing (again, with --nosig) to up2date-3.9.26-2
<aol>Me too, though I didn't use --nosig</aol>
up2dating to 3.9.26 will still break (bug is in <= 3.9.25). Should go away updating 3.9.26 to anything newer.
This appears fixed -- worked for me going to up2date-3.9.28-2