🤦🤦🤦🙄🙄🙄
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this bug go to:
https://bugs.launchpad.n
The issue should be resolved in oracular with wsdd being installed by
default now (launchpad bug #2081735)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from sm
I politely concur that this bug is really an annoyance and totally understand
why some people are losing patience. People do work in corporate environments
using Ubuntu or other linux distros and this bug totally prevents accessing
work shares.
I've been trying to fiddle with protocol versions
Can we PLEASE get this fixed already? I have to deal with this problem
EVERY DAY, and it's now over 5 years old!
I AM SICK AND TIRED OF HAVE TO BEG FOR THIS 30 MINUTE FIX TO BE
IMPLEMENTED
It is CLEAR that restarting the service provides a work-around, and a
VERY RUDIMENTARY CODE CHANGE COULD
five years to fix an smb login error. And here I thought my company dev cycle
is slow.
I am also affected by this bug on Linux Mint 20 with Thunar as file manager.
Just came here to get a bit shocked and to let people know the bug is still out
there.
--
You received this bug notification becau
If anyone understand the probably and could write a patch and submit it
upstream for review that would be great. I can handle getting the fix in
Ubuntu once available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
WS Discovery is irrelevant for storage systems that don't even have WS
capabilities at all. Please take note that the relevant component gvfsd-
smb-browse already clearly has the capability to work here but
_requires_ a kill/restart of the component after a fresh reboot to fix.
This could easily be
Sorry for the lack of activity there, we are just short on resources and
have other priorities, we will try to get to check the status of things
again here and fix what we can.
Note that upstream also working on a new WS discovery backend which should help
resolving some of those cases
https://on
I can confirm that on latest LTS (22.04.4) this is still present.
This is a major usability issue. I remember having this problem for many year
now.
Workaround is clear(killing gvfsd-smb-browse). Even a patch is released
that although not solving the root cause shows that the problem is gvfs
le
I am still having this issue every time I reboot, on Ubuntu Desktop
v23.10.
The "gvfs" package installed is version "1.52.0-1".
This issue is 100% reproducible, and my work-around still demonstrates
that the package itself (gvfs) has the capabilities of solving this
itself. Instead of failing, pr
Oh if that matters: gvfs is currently version amd64/mantic 1.52.0-1 on
my side, and Nautilus is version amd64 1:45~rc-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't
For what it's worth, I *think* I have the same bug. Recently set up a
home server with vanilla Ubuntu 23.10, up to date, using Samba
(currently samba:amd64 2:4.18.6+dfsg-1ubuntu2.1). To access the shares
from Windows 10 machines, for some reason I had to activate CIFS/SMB1.0
client functionality. O
@seb128 just booted into a live ISO for Ubuntu 23.10, just to test
without installing etc, and still getting the "Failed to retrieve share
list from server: Invalid argument" that I get on other systems :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
The change to try is probably
https://gitlab.gnome.org/GNOME/gvfs/-/commit/293365f6
The fix is already in the version which is in Ubuntu 23.10, could you
try from a iso if that's resolved there for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Yeah I've confirmed with the release notes (
https://gitlab.gnome.org/GNOME/gvfs/-/commit/ca9c22c4c41afe8ce4cc4a0bae376e9d2850f0a5
) that the fix (hopefully the one that actually solves this properly) is
in gvfs v1.50.5! "smbbrowse: Fix empty device listing after unrelated
mount failure (Ondrej Hol
** Changed in: gvfs
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SM
Ondrej actually means if we see issues with gvfs v1.50.5 that we should
open a new issue, to clarify. That suggests (implicitly, not explicitly)
that v1.50.5 of gvfs has (might?) an appropriate fix.
I have no idea when this will hit a version of Ubuntu I can test this
on. But it sounds promising!
The upstream ticket got closed and Ondrej asked someone to open a new
ticket if they still get the issue, could anyone do that on gitlab?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.
** Changed in: gvfs
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
T
@deisi , That certainly is something for valid consideration. In my use-
case there is no network bridging going on, just to clear that up. The
NAS and the client are on the same network (two non-routing switches
exist between them), on the same CIDR IP range, same DHCP server
involved, same DNS, s
Given that a restart of the application is helping and fixes this
temporarily. This reminds be of a known issue in rygel, where disable
IGMP snooping is the solution if network bridges are involved and rygel
can only be discovered after a restart.
https://wiki.gnome.org/Projects/Rygel/FAQ
Not sayi
It's looking like maybe the most relevant GNOME issue thread is :
https://gitlab.gnome.org/GNOME/gvfs/-/issues/307
(Holy cow! 6 years originally posted! Yikes!)
Also, there looks to be two open MRs in #307 (linked above) which might
help. One is for use of WSD (which as demonstrated isn't relevan
STILL having this problem! Also, the gnome issue of #506 is NOT
RELEVANT! As this issue PREDATED WSD IN TOTALITY.
Like, how more clear do I REEAALLL need to make this? I kill the
gvfsd-smb-browse process, and IMMEDIATELY I can browse SMB shares when
SMB1 is disabled. CLEARLY the application is
SMB1 is disabled on the server/NAS end. And I'm using the out of the box
experience for Ubuntu 23.04. The UX of this whole situation is
effectively broken. And while I know that I can just "killall gvfsd-smb-
browse" to trigger it to restart, that's not the whole point of why this
needs to be fixed
The SMB1 code should be entirely removed from the stack. It’s insecure and
deprecated everywhere.
On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net>
wrote:
> Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
> fixed? This is now over 4 years old.
>
> --
>
Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
fixed? This is now over 4 years old.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs
@ BloodyIron It looks like the problem you are experiencing is the same
issue as I have had. I think the reason that it works after you kill
gvfsd-smb-browse is that your FreeNAS server is advertising itself via
mDNS, and gvfsd will see that. You don't need SMB1 or WSDD for gvfsd to
discover your
This is about a bug in this piece of software, and not about finding
another piece of software to take its place. wsdd, as you proposed, is
not included by default in Ubuntu.
The point of seeking a fix for this issue is so that the UX, out of the
box, is better than it is now.
Users should not ha
@BloodyIron, please see: https://github.com/christgau/wsdd
I suggest you install as it is a significantly better work-around than
constantly killing the daemon. It is intended to be released in the next
Debian (bookworm) release as a package, I do not know if Ubuntu will
also be including it in th
Fresh install of Ubuntu 22.04 and still happening
WILL THIS EVER GET
FIXED
The attachment "Disable broken workgroup discovery/browsing" seems to be
a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad
Inspired by BloodyIron's comments above, I investigated this issue and
was able to develop a patch that solves this problem for my use case:
browsing NAS devices running TrueNAS and OpenMediaVault. It appears
that the gvfsd-smb-browse process is left in a bad state after
attempting to mount a work
Sill present in Ubuntu 22.04.
Cannot browse samba shares from my NAS. Can connect if I provide the full path
without browsing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).
https://bugs.launchpad.net/bugs/1
Xubuntu 22.04.1 after upgrading from 20.04
In order to get multiple Windows 10 systems to "discover" the samba
shares on two different Xubuntu systems, I had to re-enable SMB1
protocol on all the Windows systems. Microsoft apparently keeps
disabling this on system updates.
As reported above, old
** Changed in: gvfs
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications abo
> I can browse to my SMB shares just by killing and restarting the
gvfsd-smbd process
This magic solution has fixed my problems connecting my 21.04 Ubuntu
clients to a Synology NAS, thank you @BloodyIron (wasting ~60 minutes of
time trying to find a work around).
While waiting for the proper upst
Hi all, just wondering if there is any update on this at all? I would
just like to add that this is a big issue. I am in an environment where
I wish to disable SMB1 but this bug makes it extremely inconvenient for
users browsing the network. Given that having SMB1 enabled is a security
risk, I woul
Regarding my previous comment, disregard the issue about Windows 10
having problems accessing the Samba shares. This turned out to be a
strange password problem with samba. Resetting the user's password to
the same value that it already was immediately cleared the issue and all
windows machines c
Just to add another voice to the crowd, I'm on Xubuntu 20.04 and I just
ran across this problem myself.
I am using the Nemo file browser, but the same thing occurs with
Nautilus and Thunar. I didn't notice the problem for a long while
because I had three legacy Windows machines on the network (al
My apologies for sidetracking this far trying to explain differences
between discovery and browsing but there seems to be a lot of mixing the
2 as one. The fact that you have "discovered" a server you wish to
"browse" is irrelivant for this bug (afaik you shouldn't have been able
to discover it as
I don't use Windows for serving SMB, I was simply linking the reason for
deprecation. FreeNAS, and other non-windows systems serve SMB v2 and
higher for network shares, and WSD is not present, relevant, or desired
in those configurations. WSD is not the solution, nor replacement, and
SMB v2 and v3
In the very same article you linked: https://docs.microsoft.com/en-us
/windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by-
default-in-windows
With SMBv1 being removed, Network Browser (which depended on SMBv1) was
removed, all of which relied on NetBios being used for discovery
> I can browse to my SMB shares just by killing and restarting the
gvfsd-smbd process
you should register a new bug then because that's not what that one is about,
quoting the title
'gvfs can't list shares from smb servers that disabled SMB1'
--
You received this bug notification because you ar
Um, no. Microsoft did not deprecate SMB v1 for WSD, they did it because
it has a blatant security flaw in it :
https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-
smb1/ba-p/425858
Furthermore, SMB v2 and v3.x has been out for years, as modern
implementations of the protocol, _n
Not to put too fine a point on it, but actually that is exactly what
this requires. Microsoft phased out the SMBv1 protocol, (NetBios is
dead, long live NetBios), in favour of their new protocol: Web Services
Dynamic Discovery (WSD). There has been a lot of discussion and work as
to exactly HOW WS
There's no way the solution to this is implementing a new protocol to
replace SMB, that would be absurd. The discoverability and connectivity
works when the process is terminated and restarted. Clearly this is
achievable.
--
You received this bug notification because you are a member of Ubuntu
Bu
The bug isn't ignored but implementing a new protocol is not trivial,
also you are commenting on the wrong place, Ubuntu isn't writting that
software. Stating that volunteers or companies not doing work for you
for free is unacceptable is probably not going to bring you far
though...
On the bug st
Getting frustrated because a bug that has existed so long and is key to
network security (connection with SMB1), and has gone ignored for over
1.5 years, is not bad conduct. SMB1 was disabled because of it's
egregious security issues, and having no solution for things like this
as a result is unacc
To maintain a respectful atmosphere, please follow the code of conduct -
http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are
handled by humans, the majority of whom are volunteers, so please bear
this in mind.
There is no fix available at the moment there, unsure why it worked for
I second that!!
This is pathetic.
On November 24, 2020 3:58:16 PM EST, BloodyIron <1828...@bugs.launchpad.net>
wrote:
>I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED?
>This
>issue was reported over 1.5 YEARS ago and a fix was already made, but
>HAS NOT BEEN RELEASED TO UBUNT
I AM STILL GETTING THIS ISSUE TO THIS DAY. WILL THIS EVER BE FIXED? This
issue was reported over 1.5 YEARS ago and a fix was already made, but
HAS NOT BEEN RELEASED TO UBUNTU 20.04 WHICH IS THE LONG TERM SUPPORT
VERSION. WHEN WILL THIS BE FIXED?
--
You received this bug notification because you a
The issue went away for me in 19.10 not long after I saw reports that a
fix was released. And same system, the issue came back when I upgraded
to 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Ignore the comment about the duplicate status,
https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 is about a request to
implement a new protocol which is what is needed, updating the reference
so the status is correct
** Changed in: gvfs
Status: Fix Released => Unknown
** Changed in: gvfs
R
The upstream bug closing seems buggy since they pointed it as a
duplicate of https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 and that
doesn't make much sense. Unsure also there was anything solved in 19.10,
it's just that the situation is confusing and comments don't always
speak about the same is
Oh I dunno, maybe the "Fix Released" part? You do realise there is code
out there that fixes this that hasn't hit 20.04, right? It was solved in
later 19.10, now broken in 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Which change do you expact to be made availble? The issue there is due
to clients not handling the fact that the old unsecure protocal is
disabled by default now, that's not coming back though...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
When is this expected to hit main repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this b
** Changed in: gvfs
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notification
Why has this STILL not been rolled out to 20.04??? It was fixed for
19.10, but still not for 20.04...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb ser
This Bug is embarrassing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this bug go to:
https
Can confirm the bug is still present in Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications
STILL getting this error in Ubuntu 20.04. Just upgraded to 19.10 and I
get this error immediately. How exactly is this not already upstreamed
and fixed already??? >:|
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Really hope this gets solved soon, have to kill the process after
browsing shares every time I reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb se
I believe the real issue is that libsmbclient is still using the
SMB1/NT1 protocol as the maximum, the issue should be solved upstream
since SMB1 is deprecated (disabled by default in newer Samba server
versions).
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
But once I nicely kill the process, I not only can connect to the share,
I can still discover network shares. So, I don't really know how to
explain that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This will only get better once another discovery service is used, since
SMB1 won't come back.
https://github.com/christgau/wsdd is something we could look into
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Can we please get this addressed already? This issue persists in 19.10
(haven't tested in 20.04 yet due to unrelated reasons)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't
** Tags added: desktop-lts-wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this bug go
And as a reminder, my "solution" is to:
1. trigger the error by trying to browse to an SMB share with SMB1 disabled on
the server-side
2. "pidof gvfsd-smb-browse"
3. "kill $PID" from above (regular kill, not -9)
It then works, I can actually get to shares.
I have to do this after _every_ reboot
So I just upgraded to 19.10 and I am _STILL_ having this issue. I have
had this issue now through two whole major releases! SMB1 being turned
off _SHOULD NOT BREAK THIS_. SMB1 is a _MAJOR_ security threat, and this
really needs to get fixed!
I've been reporting this failure since April of 2019 :/
Looks like I missed a notification in
https://gitlab.gnome.org/GNOME/gvfs/issues/307, I'll followup there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb
So... any word on this bug? :S Still getting it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications abou
I too am experiencing this in Ubuntu 19.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about thi
** Changed in: gvfs (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage no
** Changed in: gvfs
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications abo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs
76 matches
Mail list logo
