I had been using 11.4 as factory-tested until November/December.
After switching form to the ‘real’ 11.4 via zypper dup and zypper ref, most of the (graphical) YaST modules are not startable via graphical YaST>[YaST Module]
But the problem seems to me only the starting in that way.
E. g. I could use the module “Software Repositories” if I start it via Main Menue (“Computer”) > “Install/Remove Software”=Software Mangager > /[Repositories] > Edit Repositories
I am wondering if this may be connected to:
Bug 677678 - upgrading from opensuse 11.3 to 11.4 repo with zypper dup fails: shared libraries: liblzma.so.0: cannot open shared object file: No such file or directory https://bugzilla.novell.com/show_bug.cgi?id=677678
Do you think that may be worth the effort to invest the cause?
Otherwise I would just do a new install of openSUSE 11.4 after official release and forget about it.
I have just come across the very same issue. Have you had any luck solving this? I tried updating everything with patches, but nothing seemed to address this issue.
On 2011-03-12 01:06, pistazienfresser wrote:
>
> I am able to start a single YaST module via
>
> Code:
> --------------------
> gnomesu [name of the YaST module]
>
> --------------------
How are you calling yast? After doing su? because it is reported not to
work, you need “su -”.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Hello - Also having this same problem with nothing starting under root, additionally the Yast menu itself will not come up on the GUI desktop. Text mode yast from a terminal window does work. I also saw the following one time in a terminal window starting yast from command line, but do not recall how I created it - kind of a long night…
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
I did gnomesu [name of the YaST module]
for example
gnomesu /sbin/yast2 sw_single
or
gnomesu /sbin/yast2 users
. That seems to work.
I copied the YaST symbol from my main menu and accroding to that
my graphical system does by default
/usr/bin/xdg-su -c /sbin/yast2
. I did copy that term to the GNOME terminal and got the text cited above and the same behavior as when I did start the YaST Menu directly form the main menu. But the same as I do
gnomesu /sbin/yast2
** (y2controlcenter-gnome:13198): WARNING **: key not found [/apps/yast-control-center/cc_actions_list]
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
Failed to load x11 FrontEnd module.
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Invalid MIT-MAGIC-COOKIE-1 keyCannot open display:
Is gnomesu a graphical equivalent of "su "? I thought it would be more a equivalent of "su - " . And is there anywhere a manpage or infopage for gnomesu?
And if I did understand the manual page under
man xdg-su
the right way xdg-su is an equivalent of su in the way that you are really becoming root and not only getting root previleges.
whyever that may be a used in my main menu -> adding a new one or the traditional menu did not anything different.
By the way:
I think the common graphical equivalent for su would be gksu and for sudo would be gksudo .
On 2011-03-13 00:36, mschlawin wrote:
>
> I just updated from 11.3 to 11.4 and have this same issue. The error
> output is the same. Does anyone have a solution?
Use su dash.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
> Is gnomesu a graphical equivalent of "su "? I thought it would be more
> a equivalent of "su - " . And is there anywhere a manpage or infopage
> for gnomesu?
It is easy to know: run “gnomesu xterm” and see what you get. No dash.
It has a “–help” response. Also a
“/usr/share/doc/packages/libgnomesu/README”. No more in the rpm.
> By the way:
> I think the common graphical equivalent for -su- would be -gksu- and
> for -sudo- would be -gksudo- .
I don’t have gksu nor gksudo, and I don’t see them in the standard repos.
> Why is this in openSUSE (still) different?
Different from what? :-?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
~/Desktop # gnomesu xterm
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can’t open display: %s
On 2011-03-13 02:06, zseries1 wrote:
>
> Logged in as root.
>
> ~/Desktop # gnomesu xterm
This will not work, nor is neccesary. You are already root, so neither su
or its derivatives will do anything useful - unless you specify a user.
The idea I wrote about, of using “gnomesu xterm” assumes that you are
logged as user (not root as you did), and was intended to learn something
about the command.
The thing is that when done that way, the xterm has the path of the user,
not that of root; thus gnomesu acts as “su” and not as “su -”, which
explains why it doesn’t work with YaST.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Ether I have misunderstood you or it does not help (apart from delivering slide different - maybe more interesting - failure messages).
username@linux-abcd:~> su -
Password:
linux-abcd:~ # /sbin/yast2
** (y2controlcenter-gnome:19619): WARNING **: key not found [/apps/yast-control-center/cc_actions_list]
Invalid MIT-MAGIC-COOKIE-1 keyxprop: unable to open display ':0.0'
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
Invalid MIT-MAGIC-COOKIE-1 keyxprop: unable to open display ':0.0'
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
Invalid MIT-MAGIC-COOKIE-1 keyxprop: unable to open display ':0.0'
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
Invalid MIT-MAGIC-COOKIE-1 keyxprop: unable to open display ':0.0'
Invalid MIT-MAGIC-COOKIE-1 keyWarning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s
linux-abcd:~ #
Had the same problem using the DVD to update a Gnome 64 bit ATI 11.3 system. Decided to install KDE to take a look at it and, low and behold, Yast2 modules load fine in the KDE desktop. Haven’t had time to do any more troubleshooting, but just wanted to let y’all know.
ASUS Motherboard M4A89GTD USB3 AMD 890GX Chipset Integrated ATI Radeon™ HD 4290 GPU
On 2011-03-14 00:33, Carlos E. R. wrote:
> On 2011-03-13 12:36, pistazienfresser wrote:
> In my 11.4 rc2 it works. I’m upgrading to GM now, I’ll check again.
Works fine.
When clicking on a module, I see that it first fires xdg-su, which being
already root, doesn’t ask for a password. This is new for me.
I noticed something strange, after the dup: there are several packages that
were not upgraded, because the factory version was newer than the GM final
version, and show in red in YaST. People having problems after dup should
check all those in red, if they exist. I’m unsure if relevant.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Maybe my fault was that I changed a ‘red’ package to the version of 11.4 GM ?
Or I missed something and changed not completely?
I thought about making one or more “Switch installed versions to the versions in this repository” towards the 11.4 oss repository but with packages from Packman already installed (and some kernels on multiversion) this will in my view make more fuss than a new install.
But as there are some other members of the forums in this thread having equal problems - may be I will try to be altruistic and file a bug report (if there is not one already existing).
But sorry, this would probably take some time - today I have pressing issues in the real live;)
