|
Bugzilla – Full Text Bug Listing |
| Summary: | gnomesu hangs often | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Wolfgang Rosenauer <wolfgang.rosenauer> |
| Component: | GNOME | Assignee: | Stanislav Brabec <sbrabec> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P1 - Urgent | CC: | security-team |
| Version: | RC 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Wolfgang Rosenauer
2005-09-30 08:16:09 UTC
It looks like the .Xauthority file is getting corrupted somehow. "xauth list" probably fails for you, which is what libgnomesu hangs on reading. It should be a little smarter than hanging too. Removing .Xauthority should work around the issue. This turned out to be gnome-su's xauth invocation doing DNS lookup. Patch submitted to build. Re-opening for submission to sl 10.0 Really reopening Swamp ID please. I have copied your patch libgnomesu-1.0.0-xauth-nolookup.patch from STABLE to 10.0 and tried. gnomesu does not work for me at all: sbrabec@hammer:~> gnomesu /sbin/YaST2 Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key y2controlcenter: cannot connect to X server :0.0 Same problem here. I submitted a patch for bug 98627 to gdm STABLE, and it works for me with these two patches applied. The gdm patch may be necessary for this patch to work. Also, remove your old .Xauthority file. Please try this and let me know if it's still broken for you. I just submitted a new libgnomesu to STABLE and PLUS, with an updated patch. The previous one was broken. Does it mean, that we have to release both fixes for 10.0 via YOU at once? Without gdm patch, it seems to work, but shows following error: cat: write error: Broken pipe Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed Second one is OK, first one is not OK. First one was probably a random message from YaST (I have seen it 3 times) and does not occur now. I will provide a package for YOU. Is it necessary to remove the old .Xauthority hpj? To hpj: I am now preparing YOU. Do we need special message to users? What can be in POST: - Nothing. - "You may need to re-login." - "You may need to remove ~/.Xauthority file and re-login to complete the fix." please don't use a popup for that. Just state it in the description. Patchinfo created. Text "You may need to remove ~/.Xauthority file and re-login to complete the fix." was added only to description instead of pop-up. released |