GNOME Bugzilla – Bug 568429
Entering UNC path crashes file chooser on Windows
Last modified: 2018-02-10 03:34:05 UTC
Steps to reproduce: 1. Open the file menu 2. Select Open 3. Select button for 'Type File Name' 4. Enter URI (ie \\10.1.1.39\d$\) and hit enter Stack trace: Other information: This is for WinGIMP. My OS is XP Pro SP3 x86 32 bit. System is dual Xeon 2.8 (HP Pro Workstation xw6000) with 3GB RAM. Error dialog as follows: Title: Microsoft Visual C++ Runtime Library Program: C:\Program Files\GIMP-2.0\bin\gimp-2.6.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
\\10.1.1.39\d$\ is not a URI, it's a normal file name on Windows (that happens to point to a share on a server, in a format usually called a "UNC path"). That said, the GTK+ file chooser shouldn't crash of course. The bug is in GTK+, not GIMP.
*** Bug 578065 has been marked as a duplicate of this bug. ***
The seems to not crash for me (Vista32) Gimp 2.6: Saving in a UNC location, threw away the UNC part silently and saved somewhere similar on C: \\bokka\projects\test.xcf saved to c:\projects\test.xcf Gedit 2.28.0 Typing \\bokka\projects and hitting enter or tab does nothing. Adding an extra slash: \\bokka\projects\ and hitting enter in the save dialog shows: Save in folder projects (\\bokka) And a single button at the top 'projects' with no initial '\' button (correctly). In the open dialog: \\bokka\projects\ + Enter I have a button 'projects', no '\' button correctly. However theres nothing to show that I'm on server '\\bokka' It might be worth having the network neighborhood as the initial level (button, followed by the server name) Testing Vista notepad, save-as dialog they in face do this and have these levels: Network > BOKKA > Projects
Heres a tutorial with code to list computers in the network neighbourhood: http://support.codegear.com/article/34701
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue for it.