You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Is anyone else having this problem? Is it likely to be a temporary problem with the repo? I have had a similar error sometime in the past which resolved itself.
The thing is, last time I used suse my baby son got to the reset button and when I came to boot up next it did a filesystem check because the filesystem was not clean so maybe something is corrupted.
If this is the case does anyone know how to fix it?

Well, day two and I'm still getting the error.
Yast has worked fine on the odd occasion I've used it. I tend to forget I have yast at all cos I'm so used to smart now. I've always found yast to be too slow for my liking.

I'm getting the error now too as well. I basically can't update anything involving KDE. Smart told me it wanted to delete it when I started it earlier this evening, and I stupidly allowed it to do so. Now I can't add it back. Using smart channel --add http://software.opensuse.org/downloa...SE_Linux_10.0/ pretends to add the channel, but it doesn't. Using the GUI results in the same problem. Nothing is actually added. Adding it manually via the GUI results in the error described in the OP.

OnEdit: Prior to this taking place, I had updated smart itself to .42-10. I reverted back to .42-9, and the problem went away.

I've had the problem on and off since I first posted. What I have noticed is some mirrors seem to get back up and running before others so I added a few different mirros to the suse-kde source so if it does keep going, at least it will keep trying the other mirrors to make sure I can use the repo again as soon as.