I've noticed what appears to be a severe problem with Zen. On at least 4 or 5 occasions, on 3 different systems, after running an update, the desktop can no longer be started. Sax2 -r doesn't correct the problem and I've only been able to recover by reinstalling. This occurs on both 32 & 64 bit versions, running KDE Any idea how to recover from this, without reinstalling? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
James Knott wrote:
I've noticed what appears to be a severe problem with Zen. On at least 4 or 5 occasions, on 3 different systems, after running an update, the desktop can no longer be started. Sax2 -r doesn't correct the problem and I've only been able to recover by reinstalling. This occurs on both 32 & 64 bit versions, running KDE
Any idea how to recover from this, without reinstalling?
Hi James, might be that the ZEN update updated your kernel(s). If you have NVidia cards, just read this note from NVidia: IMPORTANT: You need to recompile and install the nvidia kernel module after each kernel update. sh NVIDIA-Linux-x86-1.0-8762-pkg1.run -K You do this at runlevel 3 (where you seem to be), in the path where you have your NVidia .run (The driver you downloaded (?) from NVidia) There might be other solutions, but try at least on one machine and see if this works. HTH, Cheers, PatrickM -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
PatrickM wrote:
James Knott wrote:
I've noticed what appears to be a severe problem with Zen. On at least 4 or 5 occasions, on 3 different systems, after running an update, the desktop can no longer be started. Sax2 -r doesn't correct the problem and I've only been able to recover by reinstalling. This occurs on both 32 & 64 bit versions, running KDE
Any idea how to recover from this, without reinstalling?
Hi James,
might be that the ZEN update updated your kernel(s).
If you have NVidia cards, just read this note from NVidia:
IMPORTANT: You need to recompile and install the nvidia kernel module after each kernel update.
sh NVIDIA-Linux-x86-1.0-8762-pkg1.run -K
You do this at runlevel 3 (where you seem to be), in the path where you have your NVidia .run (The driver you downloaded (?) from NVidia)
There might be other solutions, but try at least on one machine and see if this works.
It did on the system with an Nvidia card, but I doubt it would work on my ThinkPad, with the Intel video chipset. tnx -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 29 July 2006 03:59, James Knott wrote:
I've noticed what appears to be a severe problem with Zen. On at least 4 or 5 occasions, on 3 different systems, after running an update, the desktop can no longer be started. Sax2 -r doesn't correct the problem and I've only been able to recover by reinstalling. This occurs on both 32 & 64 bit versions, running KDE
Any idea how to recover from this, without reinstalling?
I've noticed the same thing. I finally un-installed zen and rug completely. I'll be manually doing Yast updates from now on, until this is fixed. Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us. It it wasn't broke, why fix it? -- _____________________________________ John Andersen
Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us.
It it wasn't broke, why fix it?
They need a reason for Mono to exist.... -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday, 29 July 2006 12:44, ianseeks wrote:
Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us.
It it wasn't broke, why fix it?
They need a reason for Mono to exist....
<rollin' on da floor> That is THE BEST line of the year on the list. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 29 July 2006 14:16, Sargon wrote:
On Saturday, 29 July 2006 12:44, ianseeks wrote:
Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us.
It it wasn't broke, why fix it?
They need a reason for Mono to exist....
<rollin' on da floor>
That is THE BEST line of the year on the list. ========
May be the best line Sargon, but it's very true! -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday, 29 July 2006 16:35, BandiPat wrote:
That is THE BEST line of the year on the list.
========
May be the best line Sargon, but it's very true!
No arguments from me. I am in complete agreement. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 30 July 2006 01:00, Sargon wrote:
On Saturday, 29 July 2006 16:35, BandiPat wrote:
That is THE BEST line of the year on the list.
========
May be the best line Sargon, but it's very true!
No arguments from me. I am in complete agreement.
They also need reasons to stuff up KDE to make it a nightmare to update/use so they can stop supporting it, as that was their original plan until they back-tracked. So they'll start shoving more Gnome/Mono stuff into the system. Why can't hey give us YaST back and let Gnome suffer their own ZMD nonsense and stop using KDE as a test bed? YaST worked. Its about time the person who made this stupid decision put their head above the parapet and explained what the hell is going on. I've not seen any updates to libzypp/rug etc for ages. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 29 July 2006 13:44, ianseeks wrote:
Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us.
It it wasn't broke, why fix it?
They need a reason for Mono to exist....
MOD THAT UP! Because Zen is the worst piece of cr*p I have _ever_ seen come from SuSE... -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 29 July 2006 11:55, Mike wrote:
Because Zen is the worst piece of cr*p I have _ever_ seen come from SuSE...
Seriously! The whole zen rug mono chain of trash is virtually un-intelligible, totally obscure, poorly documented, and simply fails to work. The excuse of needing to work with other repositories is nonsense. It doesn't even work with OpenSuse repositories anymore. If some fool convinced Novel that Yast and You were broken and needed replacement, then why not drop in apt or something else mainstream? Ubuntu now works BETTER then SuSE in this regard. Does anybody know where Hubert Mantel is now? -- _____________________________________ John Andersen
On Saturday 29 July 2006 20:55, Mike wrote:
On Saturday 29 July 2006 13:44, ianseeks wrote:
Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us.
It it wasn't broke, why fix it?
They need a reason for Mono to exist....
MOD THAT UP!
Because Zen is the worst piece of cr*p I have _ever_ seen come from SuSE...
Unless my memory is defective, I believe Novell got into bed with mono prior to purchasing SuSE. My feeling is that this change was dictated to the guys in the SuSE division after the buyout. We all have to grin and bear it sometimes at work sometimes, and I think privately a number of the old guard are wincing at the damage that Zen has done to the SuSE reputation. Generally SuSE is an excellent (if not the best) distro. It's just tragic that it was saddled with Zen so late in the day, when it was so obviously not ready. Hopefully this is not an omen of Novell's attitude to openSUSE nee SuSE Linux. How 10.2, 10.3 and 11.0 (numbers based on historical evidence) are planned, built, _tested_ and delivered will be crucial to the future of what is now called openSUSE. If there are more instances of the Zen farce ilk, I can see openSUSE dying as people move in favour of a more robust platform. -- Steve Boddy -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
John Andersen wrote:
On Saturday 29 July 2006 03:59, James Knott wrote:
I've noticed what appears to be a severe problem with Zen. On at least 4 or 5 occasions, on 3 different systems, after running an update, the desktop can no longer be started. Sax2 -r doesn't correct the problem and I've only been able to recover by reinstalling. This occurs on both 32 & 64 bit versions, running KDE
Any idea how to recover from this, without reinstalling?
I've noticed the same thing. I finally un-installed zen and rug completely. I'll be manually doing Yast updates from now on, until this is fixed.
Yast and You worked perfectly for many releases. I can't imagine what possessed Novel to foist this zen crap on us.
It it wasn't broke, why fix it?
Even beyond this, I've noticed other problems with it, such as getting error messages and dependency failures. Often switching to run level 1 and back clears the problems. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (8)
-
BandiPat -
ianseeks -
James Knott -
John Andersen -
Mike -
PatrickM -
Sargon -
Stephen Boddy