|
Bugzilla – Full Text Bug Listing |
| Summary: | If the root .Xauthority key is bad, yast2 invisibly fails to launch | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Bryce Nesbitt <bryce2> |
| Component: | YaST2 | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P4 - Low | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| URL: | http://www.citycarshare.org/ | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bryce Nesbitt
2006-11-22 19:27:59 UTC
Did you turn on "high security" mode in yast? What are the permisions of gnomesu? ls -al /opt/gnome/bin/gnomesu Almost everything is at the defaults -I have no idea what "high security mode" is. # ls -al /opt/gnome/bin/gnomesu -rwxr-xr-x 1 root root 7748 2006-05-02 18:20 /opt/gnome/bin/gnomesu This is a problem for me too, although it was not an upgrade but a fresh install of 10.1, which as of this moment is also fully up-to-date. Yes, permissions mode 'secure' causes this problem, 'easy' does not. There needs to be a fix for this, kdesu works just fine with 'secure' but not gnomesu. Workaround: add the following line to /etc/permissions.local:
/opt/gnome/lib/libgnomesu/gnomesu-pam-backend root:root 4755
(taken from permissons.easy) and run SuSEconfig.
This is fixed on 10.2, for 10.1 it's a duplicate.
*** This bug has been marked as a duplicate of bug 175616 ***
My 10.2 settings are set to, and always were set to, "Easy". I see but cannot explain: bryce@hardhat:~> /opt/gnome/bin/gnomesu Xlib: connection to ":0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key (gnome-terminal:21485): Gtk-WARNING **: cannot open display: /etc/permissions.local contains: # example: #/usr/local/bin/mtr root.root 4755 /opt/gnome/lib/libgnomesu/gnomesu-pam-backend root:root 4755 Aha, there was a propsenity for bad keys in the X cookies at one point, try removing ~/.Xauthority and logging back in. Closing this out and commenting in the original bug. None of the above worked. Deleting the .Xauthority for root, and rebooting, did the trick. Please change the bug report to: "if the root .Xauthority key is bad, yast2 invisibly fails to launch after asking for the root password". This is unresolved as of OpenSUSE 10.2. *** This bug has been marked as a duplicate of bug 334382 *** |