The VideoLAN Forums

Hi,

I reopened the bug #2960 about drag and dropping files from smb shares. This bug was yet reopened multiple times because successive fixes seem to resolve part of the problem. So it looks to me like a good place to let the team know it is still not fixed for (my) ubuntu 10.10.

The thread was closed with the following comment.

No. This was fixed and that can be verified by entering the URL directly in VLC.

which didn't answer the question. The bug is about drag and dropping files not about entering url in file dialog.

So I filled a test case showing the bug is still present.
Bug report was closed again and I was warned about being banned if I reopened the bug once again.

So what should I do next ? Reopen the bug with another id ?

Vlc is great and until now I don't have to fill up bug reports. But If all posters are welcome the same, I don't think I'll come back anymore.
If I've done something wrong one could explain why without being so rude.
"Strange this particular bug is supposed to be fixed. Your problem looks like something new. For now I closed this bug report because [xyz] but please [...verify prerequisites, generate log, test case...] then if the bug is still present then open a new report."

You've been told the bug was fixed in recent versions and yet you've reopened it. That's inappropriate, annoying and disingenous.

If you have a NEW bug you file NEW bug...

Hi,

So I posted a new bug #4399 that's 90% the same as #2960.
So that we (I) could know :
If it is really fixed ;
Since when (which version)[*] ;
And what has been fixed. (viewtopic.php?f=13&t=85951 tells smb folder scanning doesn't work which is not what I understand from #2960)

* I know I could SVN the last version to test if the bug has gone but #2960 tells it should be fixed since 1.1.0 [from what I understand] and I run 1.1.4. You must understand that we don't all have time/skills to SVN/recompile every software. So when I fill a bug report I like to get a CLEAR statement telling 'fixed since x.y.z' so that I could decide what to do (report as "still not fixed for me", download/svn latest version to test or wait for the next upgrade to stable release).

#2960 was a windows bug fixed by http://git.videolan.org/?p=vlc.git;a=co ... 85a5fe78ff as the ticket says it.

If you have a new bug, then, write a clean and correct bug report. Do not reopen a bug report, that is closed, but not the same.

Hi,

> #2960 was a windows bug fixed by as the ticket says it.

Yeah, didn't see it , but :
in #2960, it would be nice to have A LINK to the GIT reference instead of just plain text so that newbies could follow it (and maybe understand/comment what has been fixed).
[OK I could ask what was this ref about before posting]

the bug was reopened since and there's no reference on how the fixing was done after #644185a5fe78ff so it's difficult for followers to understand if their bug is related to the previous and I'm not the only "complaining" about it https://bugs.launchpad.net/vlc/+bug/664030?comments=all

I presume this behaviour has the same underlying cause as discussed in that old bug I mentioned. Unfortunately in the old bug discussion does not state what was actually done and how the old bugfix was actually achieved.

[Yes I know this comment is about launchpad not vlctracker, it's just to show how frustrating it could be not knowing what has been done.]

There seems to be lot of issues with smb support so closing a bug report with clear comment about it was fixed will help clarify situation so that we don't end up with users telling Vlc behaves better than it is supposed to do according to Devs
viewtopic.php?f=13&t=85951

PS: As you stated it, my bug
https://bugs.launchpad.net/vlc/+bug/664030?comments=all
https://trac.videolan.org/vlc/ticket/4399
has nothing to do with fix git commit 644185a5fe78ff which was for win32. My bug rather looks like a nautilus (maybe gfvs) bug (it works if you drag files onto a desktop shortcut but not in an already opened vlc)