I have been trying to get suse to work for a few days, and i’m sorry, but Yast breaking on me is the deal breaker. Searching around on google, I have learned that this is a relatively common occurance, even on the latest version. I cannot tolerate something which functions so unreliably, especially with respect to something so core to the OS such as package management and software updates.
If I had several spare hours? days? to troubleshoot and tweak, maybe I’d stick with it…but no… on to Ubuntu now. Suse, I hope you sort yourself out eventually, but I’m just gonna let the sickly lizard die.
I have been trying to get suse to work for a few days, and i’m sorry, but Yast breaking on me is the deal breaker. Searching around on google, I have learned that this is a relatively common occurance, even on the latest version. I cannot tolerate something which functions so unreliably, especially with respect to something so core to the OS such as package management and software updates.
If I had several spare hours? days? to troubleshoot and tweak, maybe I’d stick with it…but no… on to Ubuntu now. Suse, I hope you sort yourself out eventually, but I’m just gonna let the sickly lizard die.
Too much rant, no accurate description of the problem. You should have posted this in the soapbox forum if you didn’t want or require help. Many yast issues have been solved here.
Well i don’t understand your problem with yast and you don’t even declare your os. So is it a flame? Even if i don’t like os11 (i am still sitting on os10.3) yast is my north star, the reason that made me switch to suse when it was at version 7.3. And: this is opensource so freedom. If you prefer Ubuntu, why not?
Just a few hours ago there was a thread from another user new to openSUSE having a problem with YaST working right. A reinstall remedied the problem, and another happy member. If this user had just given it half-a-chance . . .
I’m sometimes amused at the “go back to Ubuntu” schtick. I had used all the main distros by when Ubuntu came along and I gave it serious go - stayed with it abt a year. Nice little distro, fantastic community, but a royal pain to do any serious sysadmin work. I came back to openSUSE for the polish, the integration, the cutting-edge, the sharp community . . . and, to a large extent, for YaST, which IMHO is the best desktop linux sysadmin suite.
My point is the update manager should not break like this, immediately after a fresh install. If there was a possibility that I had somehow misconfigured something, then fair enough, but this occured 30 minutes after the operating system was installed!!
After the first automatic update, Opensuse would not let me install any other software, as it seemed to think that YAST was already running… having checked all running processes I ensured that it wasn’t, however, regardless what I tried, nothing fixed it.
Here are a couple of the many pages I sifted through in an attempt to sort this out before just throwing in the towel:
Those 2 links are not relevant. The first ref’s an issue related to Novell’s Zen package management system added in 10.2 which was, admittedly, a disaster; subsequently remedied and replaced by a more robust system in 10.3 which has been fine-tuned in 11.0. The second link refs a situation where a program has opened the package management database, was closed, but the lock on the file was not released. YaST package management, for database integrity reasons, insures that it not attempt to open it if it is opened by another process. So, for example, if you have Software Repositories open and you try to start the Printer module, it will not do so, because that module besides configuring the printer will also load drivers from the repository. Or, the applet updater may be checking for updates (the timing is configurable) which will (and should) temporarily lock the package database. It’s like in Ubuntu trying to run apt and Synaptic at the same time; not allowed.
Links that are old or non-applicable certainly don’t qualify as “relatively common.” Actually, YaST is extremely reliable. And it provides a great deal more sysadmin functionality than in Debian, Fedora, Ubuntu, and Slax; where most of which is done from the command line. There are a lot of users here that have used YaST for years like myself, finding it to be extremely reliable as well as functionally rich.
What confuses me is that these links are totally out of proportion to your initial post, which at least to me sounded like YaST was crashing left and right. Perhaps you have more specific examples. Another new user just today had a problem with YaST modules crashing; for a undetermined reason there had been a problem in the installation. A reinstall resolved everything. Interestingly, quite a few users have been experiencing media related problems causing strangeness in the installation; I as well had this problem with files not being written correctly from the media - a reburn and reinstall remedied everything.
We’d be glad to help you get set up on openSUSE, if you’re actually interested. And, I should add, after having heavily worked the Ubuntu forums myself in the past, the same applies here as there regarding being polite and respectful.
Well, yes, a reinstall would resolve everything, but that is what one would do when the problem is completely unresolvable. The links I provided are an example of the sort of problem I have been having with Yast (that it claims that it is already running when it is in fact, not).
This error is compounded by the fact that in previous installations (all of these 10.3 by the way), usually by the 10th time (or so) SUSE has been rebooted, it will not take me all the way to my desktop. Instead, I am presented with blank screen from which I can do nothing. I thought that I would persevere and eventually find a solution to that, but encountering another entirely new problem to which the the only solution seems to be a complete reinstall of the operating system really does it for me.
My apologies if you find me rude and disrespectful…I don’t believe I have been. I’m just exasperated. I may disagree with your opinion of SUSE, and certainly that is allowed. If for any reason, I decide to use SUSE in the future and find it to be as extremely reliable as well as functionally rich as you do, I’ll gladly eat my hat.
Although you are rather strong in expressing I don’t think you’ve been rude. I do wonder how your experience with Ubuntu will fall as there are as many pitfalls you can come across adventuring there.
But for one distro A works better, for the other distro B.
Other than that I suspect the YaST lock errors are due to the updater locking the database.
As you have your mind set I won’t try to delve into your other mentioned issue but hope you find a smoother ride on your next run.
May you want to express again, the soapbox is the place!
Nothing is unresolvable. You just don’t have the necessary knowledge to perform it.
Well that certainly never happens with Ubuntu - shall I search the UbuntuForums for instances of ATI driver / NVidia driver dropping people to black screens or freezes?
If I was an admin here - you’d already be banned.
Your posts are in the wrong area (they’re supposed to be in SoapBox or rather call it TrollBox) and all links you’ve presented so far are irrelevant and outdated, only affecting some people - usually people who have no concept of what they’re doing.
What I mean is… Re-installing the operating system is quite a drastic step…and not a “solution” per se… If i am told that the best solution is to completely re-install the operating system, then I would regard the problem which led to such a drastic action as unresolvable.
I never said that it never happens in Ubuntu, but I have never encountered either of the two major problems I have encountered in OpenSuse in Ubuntu. And the two examples you state are completely unrelated to the problems I have experienced… If you start with a specific example which DON’T have anything to do with conflicts while using propietary drivers, I may just agree with you.
I am not heralding Ubuntu as a superior operating system to OpenSuse, I just have never encountered the brick walls I have with Opensuse in Unbuntu.
My apologies for that, but I see no way to move this thread to the proper location? And my apologies for, in your words, “having no concept of what * doing”. I will endeavour from now on to only utilise these forums when I am 100% certain of what I’m doing.
Concerning the links I provided, I would have provided an exhaustive list of the forums I have been through looking for a solution to this problem, however, unfortunately I have already reformatted the computer which held the internet history of said searches.
The links I provided in this thread were to demonstrate examples of the problem I was having with Opensuse… As I don’t know why Yast was behaving in the way it was, I can’t provide you a link to a page which states exactly what was happening. It just surprised me that such an integral part of the operating system broke with no interference from me on a freshly installed system.
Because no one should think differently from you? I’m not sure which ban-able offense I have committed? Please list them.
I’m surprised that you would go of your way to be so unpleasant. I will strive to keep my opinion of you separate from the favourable opinion I have of the Opensuse community as a whole.*
@Magic31 - I appreciate your diplomacy. And ofcourse, this is a subjective thing. I did not say the poster was “rude”, but I did diplomatically suggest that the posts should be polite and considerate. IMHO, “let the sickly lizard die” falls into the impolite category especially when couched in a post which is just a loud whiny complaint followed by supposedly-supportive but non-applicable out-of-date links. It wastes everyone’s valuable time, and that is inconsiderate. I would have taken a different view had the post been in the Soapbox.
In my experience, openSUSE can be flaky for one of these reasons:
The first is SUSE Linux 10.1 out-of-the-box - but everyone has moved on since then, plus the workarounds and advice on here saved the day, so I’m only mentioning this for completeness’ sake.
The second is dodgy or overclocked hardware. I’ve had two hard disks die on me and those gave weird symptoms that don’t make sense at the time, similarly for some RAM that couldn’t quite run at the rated speed, but has been rock-solid over several years when suitably underclocked.
The third is dodgy install media. openSUSE can’t work if you put corrupted bits on your hard disk.
So I’d ask the person with the problem to confirm that they’ve got stable hardware and quality install media.
>> O.K. i will move this to soap-box, if there are no objections ? will be
>> moved in 10mins
>
> no, please don’t move it!!
>
{Grin} No, please… move it. I don’t monitor the soap-box forum.
User is unwilling to try other methods as a temporary workaround. I’ve
provided help to other usres here on how to continue using yast and zypper
when the gui fails to work, and it does begin operating again after a bit,
no idea really why it’s failing… but life CAN go on by learning a teensy
bit more and being flexible.
Hi all,
I am having similar issues at the moment. I did the first round of updates after my install and since then the automatic updater has been broken with the message “Failed to update system : Authorisation could not be obtained”.
This is a problem because the install is still a bit flakey. About half of the time on boot Network Manager fails to initiate my Huawei modem and sometimes the Network Manager locks up the system. I tried KDE 4 and was well impressed, however it resets my X-system ever time I boot up which is a bit of a pain as it also resets the 3D effects. Not a big problem as I am using Gnome and I like it.
I know what the poster is on about. Using the early release distro’s always leads to large amounts of bugs and I personally feel the distros are not tested enough before “stable” releases. This is just compounded if the updater fails to work. I have used Suse since 10.0 and have generally been more than happy with it. I think the Yast system is the best system tool out there. However Opensuse went through a very low patch with 10.1 and 10.2 (I seem to remember USB flash support been deliberately switched off - that made me move to Mandriva for a while). I suppose we should all wait and spend up for the Stable Enterprise versions. I get no fun out of command line hacking, but all to often that is the only solution to technically difficult problems that shouldn’t be there - Linux is doing itself no favours and will never step into the mainstream at this rate. we are not all computer geek, and most of us never want to be.
Still can anyone point me to a solution to my update problem ??
If you are looking for help solving a problem, I suggest that you create a new thread perhaps in the Installation sub-forum. This thread is 3 months old and is in Soapbox - your problem won’t get much attention here.
