Has anyone found the solution to Yast2 not working after upgrade to KDE 3.01? Art
On Monday 03 June 2002 17:13, Art Fore wrote:
Has anyone found the solution to Yast2 not working after upgrade to KDE 3.01?
Art ====================
Art, Mine didn't stop working after I upgraded to KDE 3.0.1 last evening. I have run several tests to check this out and have found no bugs yet from the upgrade! I have found many bug fixes though! ;o) Patrick -- --- KMail v1.4 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206 Magic Page Products -- Amiga-SuSE-PC Sales & Service URL: http://home.sprintmail.com/~tracerb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patrick, Are you on 8.0? If so, you're the first person I've heard of who has upgraded to KDE 3.0.1 without a subsequent Yast2 problem. Could you please give detailed instructions on how you upgraded to KDE 3.0.1 so that the rest of us chickens who were waiting for a bug-fix can join in on the 3.0.1 fun? Thanks! Patrick wrote: | On Monday 03 June 2002 17:13, Art Fore wrote: | |>Has anyone found the solution to Yast2 not working after upgrade to |>KDE 3.01? |> |>Art | | ==================== | | Art, | Mine didn't stop working after I upgraded to KDE 3.0.1 last evening. I | have run several tests to check this out and have found no bugs yet | from the upgrade! I have found many bug fixes though! ;o) | | Patrick - -- Brian Support EFF! http://www.eff.org/ They're defending YOUR rights online. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE8/Ai6ATQSaAIcWwsRAgfaAKDITP96MboM8Pn+2jkfu2AhUh8rsACgzq/4 LcG0KaGNnb3nEOHSW/J+5c8= =mJPO -----END PGP SIGNATURE-----
"Brian W. Carver"
Are you on 8.0? If so, you're the first person I've heard of who has upgraded to KDE 3.0.1 without a subsequent Yast2 problem. Could you please give detailed instructions on how you upgraded to KDE 3.0.1 so that the rest of us chickens who were waiting for a bug-fix can join in on the 3.0.1 fun? Thanks!
As I indicated earlier, I am running 8.0 and initially had problems with Yast2 - but they were problems with YOU not recognising gpg, it had no problems running in Graphics mode. Since I applied the updates dated 30 May (eg kdebase-3.0.1-36.rpm) Yast2 has run perfectly. The way I upgraded was not the way which has been mentioned here. I downloaded the complete contents of the update_for_8.0/base, development and applications directories to a single local directory. Then, as a user not root, I ran kpackage and applied all of the updated rpms. I restarted kde and have had no problems since.
I reinstalled SuSE 8.0 then used APT to update to KDE 3.0.1 as I had read on the list that this would work. Yast2 was working until I updated the Nvidia Kernel and GLX, which APT did not do. (I downloaded the drivers from Nvidia, then installed with Kpackager) After that, It is broken again. Now figure that one out! Art -----Original Message----- From: Brian W. Carver [mailto:bwcarver@earthlink.net] Sent: Monday, June 03, 2002 5:24 PM To: suse-linux-e Subject: Re: [SLE] Yast2 broken after upgrade to KDE 3.01 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patrick, Are you on 8.0? If so, you're the first person I've heard of who has upgraded to KDE 3.0.1 without a subsequent Yast2 problem. Could you please give detailed instructions on how you upgraded to KDE 3.0.1 so that the rest of us chickens who were waiting for a bug-fix can join in on the 3.0.1 fun? Thanks! Patrick wrote: | On Monday 03 June 2002 17:13, Art Fore wrote: | |>Has anyone found the solution to Yast2 not working after upgrade to |>KDE 3.01? |> |>Art | | ==================== | | Art, | Mine didn't stop working after I upgraded to KDE 3.0.1 last evening. I | have run several tests to check this out and have found no bugs yet | from the upgrade! I have found many bug fixes though! ;o) | | Patrick - -- Brian Support EFF! http://www.eff.org/ They're defending YOUR rights online. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE8/Ai6ATQSaAIcWwsRAgfaAKDITP96MboM8Pn+2jkfu2AhUh8rsACgzq/4 LcG0KaGNnb3nEOHSW/J+5c8= =mJPO -----END PGP SIGNATURE----- -- 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
1. open an xterm 2. start yast2 after typing sux. 3. Do what you have to do. This works for me. I've found that the .desktop shortcuts which prompt you for the passwd to start yast2 are having issues in KDE 3.0..so starting it from a command prompt after suing to root via sux is the way to go until a fix has been issued for the .desktop files. * Art Fore (art_fore@3mts.com) [020603 14:37]: ::Has anyone found the solution to Yast2 not working after upgrade to KDE ::3.01? :: ::Art -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--
On Monday 03 June 2002 19:17, Ben Rosenberg wrote:
1. open an xterm 2. start yast2 after typing sux. 3. Do what you have to do.
This works for me. I've found that the .desktop shortcuts which prompt you for the passwd to start yast2 are having issues in KDE 3.0..so starting it from a command prompt after suing to root via sux is the way to go until a fix has been issued for the .desktop files.
But how to show yast2 in graphical format? Only the text format is showed after KDE 3.01. Thadeu
* Jose Thadeu Cavalcante (thadeu@superig.com.br) [020603 22:11]: ::On Monday 03 June 2002 19:17, Ben Rosenberg wrote: ::> 1. open an xterm ::> 2. start yast2 after typing sux. ::> 3. Do what you have to do. ::> ::> This works for me. I've found that the .desktop shortcuts which prompt ::> you for the passwd to start yast2 are having issues in KDE 3.0..so ::> starting it from a command prompt after suing to root via sux is the way ::> to go until a fix has been issued for the .desktop files. ::> ::But how to show yast2 in graphical format? Only the text format is showed ::after KDE 3.01. I don't think this is the case for everyone. I think that if you use sux and not just su that it will come up in graphical mode. The sux script lets root execute X programs in your normal user X session while just using su will not let this happen. Because it can not use the display when just using su..it comes up in text format. I just tested my theory and I was correct. When I use sux I get the GUI YaST2 when I just use su I get the text version. Make sure your typeing sux and not just su. -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- If it's true that our species is alone in the universe, then I'd have to say that the universe aimed rather low and settled for very little. -GC --=====-----=====--
tisdagen den 4 juni 2002 09.32 wrote Ben Rosenberg:
I don't think this is the case for everyone. I think that if you use sux and not just su that it will come up in graphical mode. The sux script lets root execute X programs in your normal user X session while just using su will not let this happen. Because it can not use the display when just using su..it comes up in text format. I just tested my theory and I was correct. When I use sux I get the GUI YaST2 when I just use su I get the text version. Make sure your typeing sux and not just su.
I've been using sux and also xhost + but since upgrading to 3.01 I don't get the GUI. I've just dl'ed the latest builds from SuSE and stll the same problem. Yast2 works but only in console mode. As someone said before: "my tab key is getting worn out. It would be nice if someone from suse would let us know that they are aware of the problem. And better still give us a solution. Olle Viksten -- MicroSoft Network may not carry this message without license to do so. License to carry this message requires a fee of $1000, payable within 30 days to Olle Viksten. Appearance of this message on MicroSoft Network constitutes an agreement to terms.
On Tuesday 04 June 2002 04:32, Ben Rosenberg wrote:
I don't think this is the case for everyone. I think that if you use sux and not just su that it will come up in graphical mode. The sux script lets root execute X programs in your normal user X session while just using su will not let this happen. Because it can not use the display when just using su..it comes up in text format. I just tested my theory and I was correct. When I use sux I get the GUI YaST2 when I just use su I get the text version. Make sure your typeing sux and not just su.
Thanks for your tip about sux, it can be solve several problems that happens when I run some application from console, but with yast2, the problem continues. Thank you Thadeu
On Tue, 4 Jun 2002, Ben Rosenberg wrote:
::But how to show yast2 in graphical format? Only the text format is showed ::after KDE 3.01.
I don't think this is the case for everyone. I think that if you use sux and not just su that it will come up in graphical mode. The sux script lets root execute X programs in your normal user X session while just using su will not let this happen. Because it can not use the display when just using su..it comes up in text format. I just tested my theory and I was correct. When I use sux I get the GUI YaST2 when I just use su I get the text version. Make sure your typeing sux and not just su.
I'm another person that the only way YaST2 would come up was in ASCII mode. I did use sux, and for the heck of it I even logged into KDE as root to see if it would make any difference: it didn't. So I'm back down to 3.0 again for now. Neil -- Neil Palmer, B.Ed. palmern@compusmart.ab.ca ICQ#636657 http://www.fdisk.org neilp@fdisk.org Perl Developer, CSM Systems neilp@csm-systems.com I can resist anything but temptation. -someone
On Tuesday 04 June 2002 11:17 am, Neil Palmer wrote:
On Tue, 4 Jun 2002, Ben Rosenberg wrote:
::But how to show yast2 in graphical format? Only the text format is :: showed after KDE 3.01.
I don't think this is the case for everyone. I think that if you use sux and not just su that it will come up in graphical mode. The sux script lets root execute X programs in your normal user X session while just using su will not let this happen. Because it can not use the display when just using su..it comes up in text format. I just tested my theory and I was correct. When I use sux I get the GUI YaST2 when I just use su I get the text version. Make sure your typeing sux and not just su.
I'm another person that the only way YaST2 would come up was in ASCII mode. I did use sux, and for the heck of it I even logged into KDE as root to see if it would make any difference: it didn't.
So I'm back down to 3.0 again for now.
Neil Interestingly enough, all my menus still work as before after I updated. I can use YAST2 without any problem from KDE 3.0.1. I used the files that were on the kde site though instead of the files from the SuSE site.
On Tuesday 04 June 2002 12:32, Anthony Moulen wrote:
Interestingly enough, all my menus still work as before after I updated. I can use YAST2 without any problem from KDE 3.0.1. I used the files that were on the kde site though instead of the files from the SuSE site.
Please say what rpm command you apply to upgrade KDE3->KDE3.01, I use rpm -Uvh --nodeps --force *.rpm and after this when I try to open from System/YaST2 menu four processes are created (three y2base and one yast2), but nothing happens in the screen and YaST2 is not opened. To open YaST2 I need to go to console and enter su or sux and then enter yast or yast2 or YaST2, finally it is open using ncurses. Before to update KDE3 -> KDE3.01, typing yast or yast2 or YaST2 in console open it in graphic mode. Thanks for any information about this problem. Thadeu
On Tue, Jun 04, 2002 at 05:39:36PM -0300, Jose Thadeu Cavalcante wrote:
On Tuesday 04 June 2002 12:32, Anthony Moulen wrote:
Interestingly enough, all my menus still work as before after I updated. I can use YAST2 without any problem from KDE 3.0.1. I used the files that were on the kde site though instead of the files from the SuSE site.
Please say what rpm command you apply to upgrade KDE3->KDE3.01, I use rpm -Uvh --nodeps --force *.rpm and after this when I try to open from System/YaST2 menu four processes are created (three y2base and one yast2), but nothing happens in the screen and YaST2 is not opened. To open YaST2 I need to go to console and enter su or sux and then enter yast or yast2 or YaST2, finally it is open using ncurses. Before to update KDE3 -> KDE3.01, typing yast or yast2 or YaST2 in console open it in graphic mode.
Did you run SuSEconfig after each rpm command? It seems from your description you missed that step. -Kastus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 04 June 2002 18:11, Konstantin (Kastus) Shchuka wrote:
On Tue, Jun 04, 2002 at 05:39:36PM -0300, Jose Thadeu Cavalcante wrote:
On Tuesday 04 June 2002 12:32, Anthony Moulen wrote:
Interestingly enough, all my menus still work as before after I updated. I can use YAST2 without any problem from KDE 3.0.1. I used the files that were on the kde site though instead of the files from the SuSE site.
Please say what rpm command you apply to upgrade KDE3->KDE3.01, I use rpm -Uvh --nodeps --force *.rpm and after this when I try to open from System/YaST2 menu four processes are created (three y2base and one yast2), but nothing happens in the screen and YaST2 is not opened. To open YaST2 I need to go to console and enter su or sux and then enter yast or yast2 or YaST2, finally it is open using ncurses. Before to update KDE3 -> KDE3.01, typing yast or yast2 or YaST2 in console open it in graphic mode.
Did you run SuSEconfig after each rpm command? It seems from your description you missed that step.
-Kastus
That isn't it, because I got this too, and I did run SuSEconfig between base, devel, & apps. I was the first to ask on this list about this problem, and I now know how to fix it. But no one here helped me with it, and no one is helping me with my present (major) problems. Write me Anthony. - -- "Those who do not do politics will be done in by politics." -- French Proverb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjz9auoACgkQnQ18+PFcZJvH9QCePG5xo8WFa+lkMjGZLl6LJpG5 7JgAoIE37uVHq60n32nuOhJDaD1kVJ3E =I+QZ -----END PGP SIGNATURE-----
On Tuesday 04 June 2002 04:39 pm, Jose Thadeu Cavalcante wrote:
On Tuesday 04 June 2002 12:32, Anthony Moulen wrote:
Interestingly enough, all my menus still work as before after I updated. I can use YAST2 without any problem from KDE 3.0.1. I used the files that were on the kde site though instead of the files from the SuSE site.
Please say what rpm command you apply to upgrade KDE3->KDE3.01, I use rpm -Uvh --nodeps --force *.rpm and after this when I try to open from System/YaST2 menu four processes are created (three y2base and one yast2), but nothing happens in the screen and YaST2 is not opened. To open YaST2 I need to go to console and enter su or sux and then enter yast or yast2 or YaST2, finally it is open using ncurses. Before to update KDE3 -> KDE3.01, typing yast or yast2 or YaST2 in console open it in graphic mode.
Thanks for any information about this problem.
Thadeu
I never force an RPM unless absolutely necessary. Which means I spent a little time correcting a few problems when I installed. I don't run anything after installing, although in this case I did reboot (I also updated NVidia drivers on the same day and wanted to get the new kernel modules loaded). I haven't had any problems so far, and won't be installing the updated RPMs from SuSE's site unless I run into a bug that was fixed.
participants (12)
-
Anthony Moulen -
Art Fore -
Ben Rosenberg -
Brian W. Carver -
Carl -
Fergus Wilde -
Graham Murray -
Jose Thadeu Cavalcante -
Konstantin (Kastus) Shchuka -
Neil Palmer -
Olle Viksten -
Patrick