I did a complete wipe and rebuild of my computer yesterday. This included a major hardware shuffle to rid my system of that annoying DNS/DriveSeek error. That worked, but now I have new problems that i ave never had before with SuSE7.3 (or any other release for that matter) 1. Mounting vfat drives. This has worked very smoothly in the past. Now when I try to mount/view a vfat drive using Konqueror, Konqueror starts up and does a websearch for ListDir, then returns the error message, Unsupported action ListDir. A second attempt at using Konq. to open the /windows/D drive gives this error: -=-=-=-=-=-=-=-=-= Could not mount device. The reported error was: mount: /devhdb5 already mounted or /windows/D busy mount: according to mtab, /dev/hdb5 is already mounted on /windows/D -=-=-=-=-=-=-=-=-= OK.. that's nice, the drive is already mounted. I can unmount the drive using umount /dev/hdb5 and I am back where I started. Manual mount seems to work fine... I can switch to root, type mount /dev/hdb5 /windows/D and browse the drive from a Terminal window fine. If I attempt to use Konq. after am manual mount I get the same error messages. This is new... any ideas what went wrong here? This is usually something that is a no-brainer... unfortuantely I seem to have no brain when it comes to figuring this out. 2. KMail refuses to save an option. I like using threaded messages in KMail. Makes reading the SuSE list so much easier. I set KMail up to use threaded messsages in all folders. When I start KMail, it remembers this setting for all folders except the Inbox and the SuSE List folders. I have to reset these manually to Threaded. To top it off, while KMail is running it will periodically forget the Threaded setting - the scenario is kind of like this.... Startup Kmail, set Threading on to SuSE List and Inbox, view SuSE List folder, click on Inbox, read a couple messages, click back on SuSE List and threading is off. Click back to Inbox, and threading is off there too. Click to other folders, and threading is on. Got me puzzled. Any idea what finger problems I mght be having? Later C.
On Mon, 2002-02-04 at 06:59, Clayton Cornell wrote:
I did a complete wipe and rebuild of my computer yesterday. (...)
OK.. that's nice, the drive is already mounted. I can unmount the drive using umount /dev/hdb5 and I am back where I started. Manual mount seems to work fine... I can switch to root, type mount /dev/hdb5 /windows/D and browse the drive from a Terminal window fine. If I attempt to use Konq. after am manual mount I get the same error messages.(...)
If you can do as root, but cannot as user ... This is normally a permission problem isn't it? On my box, the windoze partition seems to belong to the one who is next right now, I mean if I right-click the Windoze icon on the desktop it's wolfi users 644 What is it on your system? Cheers ... Wolfi ============================================= mailto:wolfi_z@yahoo.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Monday 04 February 2002 09:18, wolfi wrote:
On Mon, 2002-02-04 at 06:59, Clayton Cornell wrote:
I did a complete wipe and rebuild of my computer yesterday. (...)
OK.. that's nice, the drive is already mounted. I can unmount the drive using umount /dev/hdb5 and I am back where I started. Manual mount seems to work fine... I can switch to root, type mount /dev/hdb5 /windows/D and browse the drive from a Terminal window fine. If I attempt to use Konq. after am manual mount I get the same error messages.(...)
If you can do as root, but cannot as user ... This is normally a permission problem isn't it? On my box, the windoze partition seems to belong to the one who is next right now, I mean if I right-click the Windoze icon on the desktop it's wolfi users 644 What is it on your system?
The permissions for hda1 are exactly the same as for hdb5 and hdb6, both on the icons, and on the dirs they point to. I can click the desktop icon for hda1 and Konq. is able to automount that drive and display the contents. Exactly as I would expect it to for hdb5 and hdb6.... except for hdb5 and 6 it launches Konq. in it's web browser config and attempts a web search for ListDir. Here is where it gets quite surreal. If I use KDiskFree (as a regular user, not as root) I can mount the hdb5 and 6 drives, and open a Konq. filemanager to browse the drives... no errors.. nothing out of the ordinary. If I leave the drive mounted (from KDiskFree) and click the desktop icon it pops up with error messages about the drive already being mounted. The desktop icons are essentially useless to me as they are. So, as an experiment I deleted the icon for Windows_E. I copied the icon for Windows_C (the working link), and adjusted the Properties so that it points to the hdb5 drive. It works as it should. So, what could go so wrong in a fresh install that would cause this odd behavior? C.
participants (2)
-
Clayton Cornell -
wolfi