Yes.

There are 2 Directories there, AUDIO_TS and VIDEO_TS. I can open niether of the two types of file there, *.VOB and *.IFO.

I didn't mean that you should browse the dvd disc. When you right click on the dvd icon on the desktop, there should be a service menu that asks you what app you want to use to play the dvd. If thats available, then select xine as the app and it should automatically start playing the disc.

Another option would be reconfigure your Xine settings and point it to the right dvd device. On my system I had to change /dev/dvd to /dev/hdc.

My Dvd is on /dev/hda and I have set this in xine under settings->Setup, media tab->device used for CD audio (no option for dvd device).

When I select 'DVD' on the console I get 1 error message "No plugin for dvd:/", however, I believe that this is becaus the second error message says "the source can't be read (/dev/dvd)"

If I type "ls -l /dev/dvd" I get an error message "No such file or directory".

It WAS working, the upgrade has borked it (along with a heap of other stuff)

No, it just opens up a file browser.

If you changed the dvd device to /dev/hda in your xine settings, the error message should not refer to /dev/dvd. Also do you have libdvdcss installed because sometimes the plugin error is due to missing libdvdcss.

I couln't find a setting to change the dvd media. I eventually changed it in ~/.xine/config

I suspect the error which says that the plugin doesn't exist is probably be cause it can't read the media (otherwise how would it know that the plugin doesn't exist?).

In any case I do have the libdvdcss and the win32 codecs installed.

Out of curiosity, are you using Xine UI, Kaffeine or Totem?

Xine-gui and Kaffeine.

I'm currently stripping xine and libxine etc out of my system and reinstalling.

Hi Reddazz,

regarding audio failure upon return from suspend, I now notice the two following lines of text when waking up from suspend state, just after the counter reaches 100%:

pnp: device 0b disabled
pnp: device 0c disabled

That flashes on the screen for a second, to be replaced with:

pnp: failed to activate device 08
pnp: failed to activate device 09

After another second, we go forward to login.

What's going on? Is pnp plugnplay? How do I find what these device labels are?

regards.... andrew.

I've done a bit of searching and it seems like that problem is caused by a bug in the Linux kernel. I am not sure how to resolve it since the Suse mailing lists I found on google that dealt with this issue were in German which unfortunately I do not understand.

A really unpleasant feeling. However, with all due respect, if your brother-in-law attempted an incremental upgrade between major releases in windows (i.e. assuming he could do that in the first place) it is unlikely anything would work afterwards.

Extra power comes with extra responsibility.

I've been wondering whether linux's incremental upgrades aren't a bridge too far, and I think you've helped answer that question, so thanks for that.

regards.... andrew.

Yeah, what he said was "you don't go to an amateur doctor for an operation, why use a operating system built by amateurs?"

There were probably plenty of things I could say but I didn't exactly have a position of strength. In the end we didn't see the movie, he went home smug and I ended up in the dog house.

What a disappointment this thread has been so far. It starts with such a wonderful premise, and ends (so far) with myriad reports of kernel-errors and dependency failures.

And so it has been with me too. Lord knows, all I want to do is play an MP3 file. Thankfully, Windows saved the day, though, and I got my work done in the end.

Yast has been a virtual joke from the start, so I took the thread-originator's advice and proceeded to install Smart.

He was right - the install failed for want of Rpm-Python, which was not available on the website he recommended for Smart, and it took some assiduous digging to find a recent version of Rpm-Python anywhere.

I love the originator's casual suggestion that we just install that first. This, of course, leads to dependency reports requiring five other programs, including Elfutils.

For fun, I downloaded a copy of Elfutils and tried to install it, just for fun, like I say, but that led to further failure reports.

Did I say that all I wanted to do was play an MP3 file?

Dear God, people! What sort of nonsense is this? My Windows copy of Audacity has been playing MP3s for a year now!

My only distribution, by the way, is Suse 10.1, and reinstallation is not an option. My RPMs are all up to date.

Anyway, as you all know, reinstallation is for Windows-users.

Peoples hardware and software configurations differ a lot from one another, so the problems experienced are bound to to be also different.

YAST worked really well in 10.0 and works fine in SLED/SLES 10. In Suse 10.1 though, they released a buggy version of the package manager that caused problems for so many people.

Myself and other people never had elfutils dependencies (or the other 4 you mention), so I am not sure what was different about your configuration. I would have thought that packages like elfutils would be installed by default (this is the case on most distros). rpm-python is part of the main Suse distro, so thats on your installation discs as well.

To me, this does not seem like its all Suses fault. Unfortunately when I wrote the article, I didn't write it for complete Suse newbies, but in the future, I will change the way I write so that both newbies and pros can work through the articles without much hassle.

With the greatest respect, I must lay the blame for this squarely at the feet of SuSE, and at nobody else's. Having done a full, complete install of Suse 10.1 (a supposedly stable version), I would expect to have Rpm-Python and Elfutils on my system. That I don't certainly isn't my fault.

Your guide is a model of clarity, and refreshingly free of the unnecessary jargon that too often clutters these fora. You should feel no need to simplify it further.

Honestly, I don't think Novell could do a better job of discouraging use of Linux if they tried. So many "configurations"; so many supposedly "stable" versions of their operating system that are virtually unusable; so little reliable support.

Is this really how the Linux community intends to challenge Microsoft? Since when did it take expertise just to install a codec?