Comment 93 for bug 286828

As usual in the Linux world we see a lot of dodging and ducking and passing the buck and pretending that something other than Ubuntu is the problem. The bug ticket has been marked as "Invalid", and yet the problem is clearly still here and has not been fixed.

If you try to use smbmount (ie- mount.cifs) in Jaunty it still fails when trying to save files.

Notice the solutions offered by the people who said it was fixed. They had to change their configuration or upgrade their SAMBA server to get it to work! That's a kludge to their system to work around a bug in Ubuntu. No-one should have to change any parameters to smbmount or fstab or upgrade the SAMBA server to get their SMB shares mounted properly when the same commands worked fine in Hardy.

My (former) Hardy and (present) Jaunty configuration uses this Sessions startup command:
  smbmount '\\192.168.1.2\public' /home/andrew/naspublic -o guest

This worked fine in Hardy Heron, but now in Jaunty neither GEdit nor OpenOffice nor Audacious can save changes to files opened from the mountpoint.
The firmware on my QNAP NAS has not changed, and the command I use to mount the share has not changed since Hardy, but after the "upgrade" to Jaunty none of my apps can save back to the share. The idea that an upstream kernel patch in 2.6.27-11.25 has fixed this is absurd : I'm booting 2.6.28-14 and my machine still has the problem.

So it's not the kernel, and it's not the user application, and it's not the user-supplied commands, it's a bug in one of the Ubuntu distribution packages. Clearly a bug has been written between Hardy and Intrepid and is still here in Jaunty.

Downgrading the kernel is not an option since then GDM no longer starts up and without graphics OOo can't run.

There's three short-term workarounds, none of which are nice:
A) Uninstall Jaunty and go back to Hardy, or
B) Switch to using Windows XP, or
C) Copy to local drive, edit, copy back.

Option B actually is the easiest since I dual boot Windows anyway and could install Microsoft Windows version of OOo if i had to. At least in Windows when you mount the share as a drive letter it just plain works.

Would prefer it if Ubuntu programmers could just fix the bug.
Get those smbfs guys inspecting the code they changed between Hardy and Intrepid and they will find the defect. It has to be there, that's only logical.