Well yeah, same here. In your case HAL/ KDE was trying to access the VCD. In my case, I was trying to access the VCD by mounting it.
Had the error been one on Fedora/ openSUSE or distros like that, I would have blamed it on the desktop side. But in Slackware, I wasn't running KDE, and it doesn't even have GNOME or HAL -- so how then can it be one of those? I was trying to do a simple mount of the VCD (as I've always done over these years, to copy the .dat movie files across) -- and that itself failed! ----- Original Message ---- From: S.Çağlar Onur <[EMAIL PROTECTED]> To: Rakhesh Sasidharan <[EMAIL PROTECTED]> Cc: Ismail Donmez <[EMAIL PROTECTED]>; Alan <[EMAIL PROTECTED]>; linux-kernel@vger.kernel.org Sent: Sunday, December 10, 2006 3:19:14 AM Subject: Re: VCD not readable under 2.6.18 But i cannot reproduce the problem that way, in my case dmesg flooded as soon as somebody trying to _access_ to VCD. I disabled hal and closed KDE to test and that problem no longer reproducible for me. So its really seems a userspace problem and i think all of them (KDE's cdpolling backend, hal, mplayer and xine-lib) has problems with kernels >= 2.6.17 -- S.Çağlar Onur <[EMAIL PROTECTED]> http://cekirdek.pardus.org.tr/~caglar/ Linux is like living in a teepee. No Windows, no Gates and an Apache in house! __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
