In gnome desktop, the latest kernel upgrades on opensuse 11.1 cause dbus errors and prevent the dvd from auto mounting.
Nautilus and, consequently, other gnome apps are unable to read the disk.
Dbus gives the following message:
Unable to mount DISK_NAME
DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
There was no problem with the original release kernel.
I can force a mount via root using the mount command and then read the data on the dvd.
The other way is to put an entry into /etc/fstab allowing the device to be user mountable.
These solutions are less than ideal.
Any ideas?
As a follow-up to this:
The frustrating thing is that it only happens on my boxes with gigabyte
motherboards.
The identical install on my box with an asrock motherboard has no
problems.
On Fri, 24 Jul 2009 16:04:45 +0000, Malcolm wrote:
> Hi
> All strange, especially if only on gigabyte. Might be time to create a
> bug report?
>
> Although on this machine I’m using the same kernel and module (except
> SLED) it’s all working ok…
It happens on both SLED11 and opensuse 11.1(/2) and the latest kernel.
If I add an fstab entry like:
Malcolm,
What section do you think is the best for the bug report? Since it is in all 11…1(2) and sled latest kernels?
Not heard anything back from sled support yet since I posted a support query a few weeks ago. (So much for sled support- … and to think I paid and registered it because I thought I’d give something back to suse because don’t need the bells and whistles opensuse gives!
Kj44
Thanks, but I tried all of the suggestions, including those on google and they don’t work for me.
There is something in the latest kernel updates that mess it up.
The simple solution is to make an fstab entry for the drive to mount to whatever mountpoint you choose, e.g:
Excuse me if this seems impolite, but did you implement the workaround I supplied in the aforementioned thread? It might help narrow things down even if it doesn’t work, because we’ll see some diagnostics. I think its premature to blame the kernel update.
KJ44
As I said in the post above, I tried your workaround/changes and it never worked.
The simple solution (though not ideal) was to create an fstab entry as described.
This is quick to apply and works in all variants of 11.x opensuse/sled with the latest kernel (including the 11.2 milestones).
There is something in the latest (open)suse dbus / kernel updates that we are missing to give the problem. the same hardware and kernel, etc on Mint or ubuntu is fine with the same versions of kernel and dbus. My gut feel is that is something in the security setting that have changed in the suse updates that isn’t applied in the other linux flavours. But then that’s the joy of using linux - I’ll put up with some of the minor problems in the distro but like the distro as a whole so will keep using it!
I’ve backed out the changes that I previously thought had fixed the problem, and yes, I still have the dbus errors. So I must have had my success in a small window of opportunity before the kernel got updated.
Also, once I get those dbus errors, the machine becomes incredibly flaky and unstable, muttering about a stale lock file during a reboot, so it take two reboots to recover.
I’m going to insert the line in /etc/fstab - what I didn’t appreciate before, which I suspect, is that gnome will not attempt to mount devices listed explicitly in fstab. Can anyone confirm this please?
As you say whych, it’s all part of the fun finding workarounds (to the sound of my hair going grey).