https://bugzilla.novell.com/show_bug.cgi?id=447932 User wstephenson@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=447932#c1 Will Stephenson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wstephenson@novell.com Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #1 from Will Stephenson 2008-11-24 08:07:58 MST --- It's a deliberate policy change from KDE 3 (automount) to KDE 4 (mount on demand), because with automount and multiple logins, all sessions race to mount the volume. leading to the "Huh, why can't I write my USB disk - oh, i started a new session and my wife's KDE session mounted it first" scenario. Instead you have 'mount on demand' so you should be able to cause the device to mount from any app where you need to access it. Unfortunately, KDE 3 apps like k3b don't know anything about the new 'mount on demand' policy. You should use the New Device Notifier that pops up on plug to mount the usb disk, then it will be visible in k3b's filedialog. It's a little clumsy but we don't have a better solution from upstream - it would require rewriting kde3's file dialog to detect when it is running in a KDE 4 session and request a mount via HAL as Solid does in KDE 4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.