I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode. I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding). Any ideas? Is this a common problem? -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Wednesday 24 July 2002 04.31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
One idea, if you're using "sux" to run yast. If you're running it some other way it could be other reasons, but I found a problem with sux. There is a bug somewhere I can't quite track down, but for some reason, the X server loses the XDM authentication protocol at some stage. This causes sux to fail with "Protocol not supported by server". It tried the first protocol it can find in the cookie list, this happens to be XDM, and it fails. Reason: no clue. Quick fix: log out of all instances of X and remove .Xauthority both from your home directory and from /root/ After the next login, sux should work again. I know this isn't a real fix, but it's the best one I can think of since I don't fully understand the X authentication mechanism. If anyone has a better idea I'd be interested. //Anders
On Wed, Jul 24, 2002 at 05:48:20AM +0200, Anders Johansson wrote:
On Wednesday 24 July 2002 04.31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
One idea, if you're using "sux" to run yast. If you're running it some other way it could be other reasons, but I found a problem with sux.
I don't think it's sux since I have the same problem when I log into X as root.
There is a bug somewhere I can't quite track down, but for some reason, the X server loses the XDM authentication protocol at some stage. This causes sux to fail with "Protocol not supported by server". It tried the first protocol it can find in the cookie list, this happens to be XDM, and it fails.
Reason: no clue.
Quick fix: log out of all instances of X and remove .Xauthority both from your
Made no difference. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
"Robert C. Paulsen Jr."
On Wed, Jul 24, 2002 at 05:48:20AM +0200, Anders Johansson wrote:
On Wednesday 24 July 2002 04.31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
One idea, if you're using "sux" to run yast. If you're running it some other way it could be other reasons, but I found a problem with sux.
I don't think it's sux since I have the same problem when I log into X as root.
"strace -f yast2" may give some hints (missing files, ...). Also, try to view the YaST2 window on a different machine to check it's not an X-server related problem: good_machine# ssh -X -l root bad_machine yast2 -- Alexandr.Malusek@imv.liu.se
On Wed, Jul 24, 2002 at 09:28:05PM +0200, Alexandr Malusek wrote:
"Robert C. Paulsen Jr."
writes: On Wed, Jul 24, 2002 at 05:48:20AM +0200, Anders Johansson wrote:
On Wednesday 24 July 2002 04.31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
One idea, if you're using "sux" to run yast. If you're running it some other way it could be other reasons, but I found a problem with sux.
I don't think it's sux since I have the same problem when I log into X as root.
"strace -f yast2" may give some hints (missing files, ...).
Strace shows that it goes to ncurses mode almost immediately: avalon:~ # strace yast2 execve("/sbin/yast2", ["yast2"], [/* 52 vars */]) = 0 uname({sys="Linux", node="avalon", ...}) = 0 brk(0) = 0x80bca6c open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=57251, ...}) = 0 old_mmap(NULL, 57251, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40017000 close(3) = 0 open("/lib/libreadline.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\252\0"..., 1024) = 1024 fstat64(3, {st_mode=S_IFREG|0755, st_size=199592, ...}) = 0 old_mmap(NULL, 171856, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40025000 mprotect(0x4004a000, 20304, PROT_NONE) = 0 old_mmap(0x4004a000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x24000) = 0x4004a000 close(3) = 0 open("/lib/libhistory.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\27\0"..., 1024) = 1024 fstat64(3, {st_mode=S_IFREG|0755, st_size=29819, ...}) = 0 old_mmap(NULL, 26908, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4004f000 mprotect(0x40055000, 2332, PROT_NONE) = 0 old_mmap(0x40055000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x5000) = 0x40055000 close(3) = 0 open("/lib/libncurses.so.5", O_RDONLY) = 3
Also, try to view the YaST2 window on a different machine to check it's not an X-server related problem:
good_machine# ssh -X -l root bad_machine yast2
Same results -- goes straight inti ncurses mode. Maybe I don't have some rpm installed. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
I did see this problem, and I found a solution, which worked for me. Here is a copy of it, I posted it some time ago here. Did you take the kde3.02 from SuSE? I think the kde3.01 from SuSE introduced the problem (at my system), and the kde3.02 from kde.org (for SuSE 8.0) did fix it again. HTH, Matt T. On Friday 05 July 2002 20:26, Matt T. wrote:
Hi all,
Some of us had /have the problem of yast2 running in ncurses only. I never saw a solution, so I think you like this:
I just upgraded to kde3.02 from kde.org, and now yast2 is back in in graphic mode. You cant't imagine how happy my tab key is!
SuSE 8 prof new install -> yast2 in graphic mode was ok upgrade to kde3.01 form SuSE ftp -> yast2 only in ncurses mode upgrade to kde3.02 form kde.org (the RPMs for SuSE) -> yast2 in graphic mode is ok again.
But not if starting the modules directly at Preferences->Yast2 modules->choose-one.
Starting yast2 after sux in terminal is ok, and using SuSE->System->Yast2 as well.
HTH, Matt T.
On Wednesday 24 July 2002 10:48, Anders Johansson wrote:
On Wednesday 24 July 2002 04.31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
One idea, if you're using "sux" to run yast. If you're running it some other way it could be other reasons, but I found a problem with sux.
There is a bug somewhere I can't quite track down, but for some reason, the X server loses the XDM authentication protocol at some stage. This causes sux to fail with "Protocol not supported by server". It tried the first protocol it can find in the cookie list, this happens to be XDM, and it fails.
Reason: no clue.
Quick fix: log out of all instances of X and remove .Xauthority both from your home directory and from /root/ After the next login, sux should work again.
I know this isn't a real fix, but it's the best one I can think of since I don't fully understand the X authentication mechanism. If anyone has a better idea I'd be interested.
//Anders
On Tue, 2002-07-23 at 22:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
I have had the same problem for some time. I have done the updates as well, and have tried a few fixes suggested here, but it seems to be a permanent feature in my system. In my case the YAST2 menu will open,but there is a segmentation fault when I try to load any of the modules. You can check if this is the same error you get by starting yast2 from a console window instead of the menu, after running sux. The error I get is: /sbin/yast2: line 154: 4987 Segmentation fault /usr/lib/YaST2/bin/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" -style="$Y2_STYLE" -fn $Y2_XFONT It turns out yast2 is a script file in /sbin, and the above line is executed from that script. That's about as much as I've been able to figure out. Maybe someone else can provide a suggestion to help both of us. I've sort of gotten used to the ncurses version, but the interface is one of the more annoying I've seen so I would really like to get the graphics mode version working. Bernie Gardner w1az@arrl.net
On Wed, Jul 24, 2002 at 12:08:29AM -0400, Bernie Gardner wrote:
On Tue, 2002-07-23 at 22:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
I have had the same problem for some time. I have done the updates as well, and have tried a few fixes suggested here, but it seems to be a permanent feature in my system. In my case the YAST2 menu will open,but there is a segmentation fault when I try to load any of the modules. You can check if this is the same error you get by starting yast2 from a console window instead of the menu, after running sux. The error I get is:
/sbin/yast2: line 154: 4987 Segmentation fault /usr/lib/YaST2/bin/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" -style="$Y2_STYLE" -fn $Y2_XFONT
Probably not the same problem because when I start yast2 that way the ncurses version starts up and runs OK. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Wednesday 24 July 2002 04:08, Bernie Gardner wrote:
On Tue, 2002-07-23 at 22:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
I have had the same problem for some time. I have done the updates as well, and have tried a few fixes suggested here, but it seems to be a permanent feature in my system. In my case the YAST2 menu will open,but there is a segmentation fault when I try to load any of the modules. You can check if this is the same error you get by starting yast2 from a console window instead of the menu, after running sux. The error I get is:
/sbin/yast2: line 154: 4987 Segmentation fault /usr/lib/YaST2/bin/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" -style="$Y2_STYLE" -fn $Y2_XFONT
It turns out yast2 is a script file in /sbin, and the above line is executed from that script. That's about as much as I've been able to figure out. Maybe someone else can provide a suggestion to help both of us. I've sort of gotten used to the ncurses version, but the interface is one of the more annoying I've seen so I would really like to get the graphics mode version working.
Bernie Gardner w1az@arrl.net
I have kde3.02 on SuSE 8.0 and I get gui yast2. I think you need to install qt3-non-mt3.0.4. I got it from SuSE packages on kde.org. Mike
On Wed, Jul 24, 2002 at 06:20:40PM +0000, michael norman wrote:
On Wednesday 24 July 2002 04:08, Bernie Gardner wrote:
On Tue, 2002-07-23 at 22:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
I have had the same problem for some time. I have done the updates as well, and have tried a few fixes suggested here, but it seems to be a permanent feature in my system. In my case the YAST2 menu will open,but there is a segmentation fault when I try to load any of the modules. You can check if this is the same error you get by starting yast2 from a console window instead of the menu, after running sux. The error I get is:
/sbin/yast2: line 154: 4987 Segmentation fault /usr/lib/YaST2/bin/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" -style="$Y2_STYLE" -fn $Y2_XFONT
It turns out yast2 is a script file in /sbin, and the above line is executed from that script. That's about as much as I've been able to figure out. Maybe someone else can provide a suggestion to help both of us. I've sort of gotten used to the ncurses version, but the interface is one of the more annoying I've seen so I would really like to get the graphics mode version working.
Bernie Gardner w1az@arrl.net
I have kde3.02 on SuSE 8.0 and I get gui yast2. I think you need to install qt3-non-mt3.0.4. I got it from SuSE packages on kde.org.
Thanks. I tried that, but no luck. What is the difference between qt3 and qt3-non-mt? qt3-non-mt is not listed on SuSE's KDE web page, but it is on their ftp site, in the experimental directory. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Wed, Jul 24, 2002 at 06:20:40PM +0000, michael norman wrote:
On Wednesday 24 July 2002 04:08, Bernie Gardner wrote:
On Tue, 2002-07-23 at 22:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
I have had the same problem for some time. I have done the updates as well, and have tried a few fixes suggested here, but it seems to be a permanent feature in my system. In my case the YAST2 menu will open,but there is a segmentation fault when I try to load any of the modules. You can check if this is the same error you get by starting yast2 from a console window instead of the menu, after running sux. The error I get is:
/sbin/yast2: line 154: 4987 Segmentation fault /usr/lib/YaST2/bin/y2base $module "$@" qt -geometry "$Y2_GEOMETRY" -style="$Y2_STYLE" -fn $Y2_XFONT
It turns out yast2 is a script file in /sbin, and the above line is executed from that script. That's about as much as I've been able to figure out. Maybe someone else can provide a suggestion to help both of us. I've sort of gotten used to the ncurses version, but the interface is one of the more annoying I've seen so I would really like to get the graphics mode version working.
Bernie Gardner w1az@arrl.net
I have kde3.02 on SuSE 8.0 and I get gui yast2. I think you need to install qt3-non-mt3.0.4. I got it from SuSE packages on kde.org.
Despite my earlier reply to the contrary, this does work. Not sure why it didn't seem to work before. What I did was reinstall everything (except qt3-non-mt3.0.4) and yast2 still insisted on using ncurses. So I nvestigated a little and saw that the yast2 script checked for needed libraries and found libqt.so.3 missing. Looking around I saw libqt-mt.so.3 *was* there so I reinstalled qt3-non-mt3.0.4 and it all started working again. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Tue, 2002-07-23 at 20:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
-- Robert C. Paulsen, Jr. robert@paulsenonline.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
Have you tried removing all the Yast stuff from /tmp? Peter Akre
On Wed, Jul 24, 2002 at 10:27:23AM -0600, Peter Akre wrote:
On Tue, 2002-07-23 at 20:31, Robert C. Paulsen Jr. wrote:
I just noticed that YaST2 no longer runs in graphics mode. I only runs in it ncurses mode.
I am on SuSE 8.0 with KDE 3.02 with all the latest updates (except ssh since the update breaks X forwarding).
Any ideas? Is this a common problem?
-- Robert C. Paulsen, Jr. robert@paulsenonline.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
Have you tried removing all the Yast stuff from /tmp?
Thanks for the idea. I gave it a try, but it didn't help. -- Robert C. Paulsen, Jr. robert@paulsenonline.net
participants (7)
-
Alexandr Malusek
-
Anders Johansson
-
Bernie Gardner
-
Matt T.
-
michael norman
-
Peter Akre
-
Robert C. Paulsen Jr.