[Mono-bugs] [Bug 78152][Wis] Changed - FileDialog freezes temporarily when directory is mounted via samba

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by xenomorph2 at onlinehome.de.

http://bugzilla.ximian.com/show_bug.cgi?id=78152

--- shadow/78152	2006-04-20 18:37:35.000000000 -0400
+++ shadow/78152.tmp.11563	2006-04-21 10:52:45.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 78152
 Product: Mono: Class Libraries
 Version: 1.0
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: Windows.Forms
 AssignedTo: xenomorph2 at onlinehome.de                            
 ReportedBy: peter at novonyx.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -21,6 +21,34 @@
 When clicking the button that opens the dialog, the terminal session from 
 where the app was started will appear to be frozen and no dialog will 
 show. 
 Wait for a minute or so, the following error will appear on the console:
 ** Message: Unknown errno: Text file busy
 and the dialog will finally appear.
+
+------- Additional Comments From xenomorph2 at onlinehome.de  2006-04-21 10:52 -------
+Well, this is a samba/smbfs bug.
+
+This happens if you try to open a file on a samba share and someone is
+still working on that file (for example someone is hacking a file with
+wordpad). This sets a file lock and doesn't remove the lock and samba
+keeps the lock alive (caching). 
+
+The Mime class opens a file to get the mime type for that file and
+that may cause the delay if the file is locked. It uses FileStream to
+open a file:
+
+file_stream = new FileStream( current_file_name, FileMode.Open,
+FileAccess.Read );
+
+(I don't think that adding FileShare would solve the problem)
+
+The dialog itself does show up after it has read the contents of a
+directory. See FileDialog.RunDialog. So if it has to wait for Mime
+before it is visible.
+
+I have never encountered that error so it's hard to reproduce. smbfs
+is maintained in the kernel so maybe it got fixed already in newer
+kernels (I'm using 2.6.15).
+
+What kernel are you using ?
+