> this is an extremely easy fix in code to make
As this is a long bug, with many comments and different scenarios at
play, I'm a bit lost by now.
What is the easy code fix you are referring to, do you have a link to a
patch?
Also, please restate what is the scenario we are talking about here.
CAN WE PLEASE GET THIS FIXED ALREADY? I have to deal with this EVERY DAY
and this is an extremely easy fix in code to make. But I do not have any
approval for code commitment or anything like that.
THIS PROBLEM IS NOW 6 YEARS OLD and could probably be fixed in HALF AN
HOUR.
I am fed up having to
Still having to kill gvfsd-smb-browse each time I reboot just so I can
browse network shares. Clearly the fix didn't actually fix this. This is
going on 4-ish years now.
Additional thread:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107
--
You received this bug notification because
No worries, thanks for following up
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this bug
@andreas oops I think I got muddled up, sorry about that! I'm going to
unsub from this bug (which I should have done earlier).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
@bloodyiron, you said in
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/81
that you had SMB1 disabled in your network, and I confirmed that with
SMB1 disabled there is still a bug, and that bug is
https://bugs.launchpad.net/gvfs/+bug/1828107, and it affects all ubuntu
The bug still exists for me on Disco, so I don't see how you arrive at
the position that it "works" out of the box. It does not "work" for me,
the bug exists on Disco for me. And I've regularly kept my system up to
date. I've reported this multiple times in this thread and seem to be
ignored.
--
In fact I literally just tried it again, and get the same issue, where
it does not prompt for login, and the related gvfs process needs to be
killed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
** Attachment added: "disco-connect-to-pub.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272829/+files/disco-connect-to-pub.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Disco works out of the box wrt this bug specifically. Which is expected
since it has the same fix.
windows network tab is populated (see disco-windows-network-
populated.png)
Connecting to the pub share (see disco-connect-to-pub.png).
smbstatus shows smb3.11 in the pub connection, and NT1 for
This bug was fixed in the package gvfs - 1.36.1-0ubuntu1.3.2
---
gvfs (1.36.1-0ubuntu1.3.2) bionic; urgency=medium
* No change rebuild to pick up the current samba version.
The patch git_smb_nt1.patch added to fix smb browsing requires a new
libsmb api to work and that's
This bug was fixed in the package gvfs - 1.38.1-0ubuntu1.3.1
---
gvfs (1.38.1-0ubuntu1.3.1) cosmic; urgency=medium
* No change rebuild to pick up the current samba version.
The patch git_smb_nt1.patch added to fix smb browsing requires a new
libsmb api to work and that's
** Tags removed: browse browsing verification-needed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage
Can we also get this bug marked as Disco to? Not just Bionic and Cosmic?
I'm _still_ getting the issue with a fully updated Disco (19.04).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
** Attachment added: "cosmic-connecting-to-pub-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272234/+files/cosmic-connecting-to-pub-after-test.png
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received
** Attachment added: "cosmic-empty-windows-network-before-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272232/+files/cosmic-empty-windows-network-before-test.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Attachment added: "cosmic-populated-windows-network-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272233/+files/cosmic-populated-windows-network-after-test.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Cosmic verification
First reproducing the bug with these packages:
Version table:
*** 1.38.1-0ubuntu1.2 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64
Packages
windows network tab is empty (see screenshot
cosmic-empty-windows-network-before-test.png)
Now
** Attachment added: "empty-windows-network-before-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272225/+files/empty-windows-network-before-test.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Attachment added: "connecting-to-pub-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272227/+files/connecting-to-pub-after-test.png
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
Bionic desktop verification
With gvfs-backends from the release pocket:
ubuntu@bionic-desktop:~$ apt-cache policy gvfs-backends
gvfs-backends:
Installed: 1.36.1-0ubuntu1.3
Candidate: 1.36.1-0ubuntu1.3
Version table:
*** 1.36.1-0ubuntu1.3 500
500 http://br.archive.ubuntu.com/ubuntu
** Attachment added: "populated-windows-network-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272226/+files/populated-windows-network-after-test.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Bug watch added: Samba Bugzilla #12876
https://bugzilla.samba.org/show_bug.cgi?id=12876
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=12876
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=780958
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
** Bug watch removed: gitlab.gnome.org/GNOME/gvfs/issues #307
https://gitlab.gnome.org/GNOME/gvfs/issues/307
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
Well I know for a fact it has SMB1 disabled, as I disabled it myself.
Ran the test you asked, didn't output any info that seemed to
conclusively say which protocols were visible. I'm intentionally
disabling SMB1 for the very public security concerns. In this case, the
"server" has a minimum
@Bloodyiron, please run "nmblookup -M " and check if
the machine that is listed has SMB1 disabled or not. If it has SMB1
disabled, then it's https://bugs.launchpad.net/gvfs/+bug/1828107
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** No longer affects: nautilus (Ubuntu)
** Changed in: samba (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
I'm using Disco as my daily driver and I still have this issue every
time I reboot. I also update nearly daily from the main repos, so any
fixes that may have rolled out, thus-far, aren't fixing it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hello Sebastian, or anyone else affected,
Accepted gvfs into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gvfs/1.38.1-0ubuntu1.3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Try the test case in a disco vm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this bug
Okay but it isn't fixed in Dingo. I still get it. What more do you want
me to do, not say it's happening for me in Disco Dingo? Because it is...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
The "windows network" tab depends on an election to happen between the
smb servers, and a master browser being elected. It's the master browser
that is contacted for the list of machines in the network. If that
machine has smb1 disabled, for example, then this won't work, because it
will hit
Cosmic uploaded as well
** Changed in: gvfs (Ubuntu Cosmic)
Status: Triaged => Fix Committed
** Changed in: gvfs (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
The bug should be fixed in Disco, samba 2.4.10 includes the function and
gvfs there has the patch and was rebuilt with it
** Changed in: gvfs (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
(bionic rebuild SRU in the queue now)
** Changed in: gvfs (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
I have the issue in Disco... and have since I upgraded to it, as I
mentioned
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/35.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
I filed https://bugs.launchpad.net/gvfs/+bug/1828107 for the remaining
issue of connecting to machines in the windows network tab that have
disabled SMB1. Note that a connection made specifically to the
machine/ip still works (smb:///)
--
You received this bug notification because you are a
I found an upstream issue about not being able to get a share list from
a machine that has SMB1 disabled:
https://gitlab.gnome.org/GNOME/gvfs/issues/307
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #307
https://gitlab.gnome.org/GNOME/gvfs/issues/307
--
You received this bug
Disco shouldn't have this bug. It (gvfs) will have issues connecting to
smb servers that have disabled SMB1, just like bionic and everything in
between.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Um, what about Disco Dingo? 19.04, still having the bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage
It is, that's all that's needed now. I heard another, unrelated, gvfs
SRU was in the works and was hitting problems, though.
I have a no-change rebuild in this PPA for bionic:
https://launchpad.net/~ahasenack/+archive/ubuntu/gvfs-rebuild-1778322/
--
You received this bug notification because
> Is a rebuild/version-bump planned for gvfs Bionic?
Yes, that was blocked by another SRU which was accepted but turned out
to be problematic (building the nfs backend which requires libnfs
promoted). The other SRU has been deleted for now so we are going to
move forward with this rebuild
--
Is a rebuild/version-bump planned for gvfs Bionic?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage
@morbius1, how did you disable smb1 on your test samba server? "server
min protocol = SMB2"?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't
Ah, you said so, sorry
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this bug go to:
@seb128, If the samba share was created on Ubuntu Server and not on
Ubuntu Desktop then without the fix you will not see the samba server
through Nautilus.
That's because Ubuntu Server does not install avahi-daemon by default.
Once installed it's visible outside of "Windows Network" because of
@seb128, the test case uses a localhost samba server, with a non-guest
pub share pointing at /tmp. Not even that was visible in gnome before
this fix.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
@Morbius1, the testcase from Andreas showed empty nautilus views though
@Andreas, what sort of shares did you use for your testcase?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Nice, that's good to know, thanks for pointing it out.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage
I understand.
I would however like to make a final note about Linux to Linux samba use
- at least in a home network.
If the server is running Ubuntu 17.10 or later ( with avahi-daemon
installed ) this bug is not relevant because the samba client isn't
using gvfsd-smb-browse. The sever
> The original issue was you couldn't get a listing of samba hosts in Nautilus
> so
> yes that issue is fixed.
The original problem also affected linux samba boxes, which do allow
smb1 by default still. You couldn't even see them in nautilus. Now you
can, and you can browse their shares and
A new rebuild is needed. To verify in another way, check the Depends
line of the gvfs-backends package:
$ dpkg -s gvfs-backends|grep Depends|grep smbclient
Depends: libarchive13 (>= 3.0.4), , libsmbclient (>= 2:4.0.3+dfsg1)
versus
$ dpkg -s gvfs-backends|grep Depends|grep smbclient
Do we need a new rebuild of gvfs in bionic or did the 1.36.1-0ubuntu1.3
update pick up the samba change when it was built?
Using samba 4.7.6+dfsg~ubuntu-0ubuntu2.9, I rebuilt gvfs
1.36.1-0ubuntu1.3 locally.
I then restarted gvfsd-smb-browse without success..
killall gvfsd-smb-browse &&
Thanks Andreas and sorry for posting it here. I was hoping it could be
related. Here's the new bug report:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1827041.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
Yes, please open a separate bug report, and attach your smb.conf there
please.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse
I don't know if it's related, it probably isn't, but I'll mention it
just in case.. I noticed a regression in smbclient and I'm wondering if
that's affecting gvfs as well.
After setting up an open share (RW access to everyone, no password) on
the Windows 10 box, I can access it with Ubuntu 16.04
I think it's exactly getting the share list using NT1 that is failing. I
will look at this tomorrow, see what smbclient -L is doing wrt NT1
temporary downgrade.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Here's a different perspective. Accessing the Win10 machine again:
tester@vub1904:~$ smbclient -L vwin10 -U smbuser
Unable to initialize messaging context
Enter WORKGROUP\smbuser's password:
Sharename Type Comment
- ---
ADMIN$
smbclient -L, "gio mount smb://server/share ', even just specifying
smb://server/share in the location bar in Nautilus works just like you
would expect.
It's only the gvfsd-smb-browse process that's messed up.
As far as it being a related but different problem Well I reckon it
all depends
I indeed think interacting with a server that has disabled SMB1 entirely
is a related, but different problem. Can you get smbclient -L to work
with such a server, using the netbios hostname, or does it fail when
listing the shares?
--
You received this bug notification because you are a member
Your reference to the Linux Samba Server command: smbstatus got me
thinking what would happen if I disabled NT1 on a Linux Samba server by
stipulating "server min protocol = SMB2" and using Windows Network > ...
to connect.
The exact same thing happens as when trying to connect to a Win10
machine
My post concerns Ubuntu Disco. I'm guessing Win10 sees the SMBv1
connection, rejects it outright, and never gets to the protocol
negotiation phase.
As I said this only involves the gvfsd-smb-browse process: Nautilus >
Other Locations > Windows Network > Workgroup
If I use Connect to Server
Does this also happen with Ubuntu Disco? I checked upstream and there
were no other changes following this one in that file:
commit 6c8bc39f570ea82cf14e83ce7d1dbdbe569d09d1
Author: Ondrej Holy
Date: Wed Sep 12 15:28:51 2018 +0200
smbbrowse: Force NT1 protocol version for workgroup support
There is an issue with this fix that makes it impossible to access a
Windows 10 machine that has disabled SMB1 ( NT1 ):
smb-network: g_vfs_backend_smb_browse_init: default workgroup = 'NULL'
smb-network: Added new job source 0x55ebe2dd53d0 (GVfsBackendSmbBrowse)
smb-network: Queued new job
Checked smb.conf so far only seeing "client min protocol = SMB2" which
should not be causing this problem...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
Check your smb.conf, maybe you have some overriding setting in there.
The default disco install I tested had no config file.
With gvfsd running in debug mode, there is also a specific message you
can look for which will tell you if your gvfsd was rebuilt with the
right samba version: "Forcing NT1
@Andreas , I already have those installed. Still seeing the same effect
each reboot.
Not sure why my result is different. I do have two workgroups in play
though, so I wonder if that's it...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
It worked just fine on a disco desktop default install.
I brought up a bionic vm, which has samba running and set to a workgroup
called "workgroup" and has a /pub share. On disco, I click on "other
locations", then "windows network", and I see "WORKGROUP". I can click
on "WORKGROUP", which then
I checked disco when I prepared these updates for bionic and cosmic, and
it was allright. Let me re-check with a default install using the CD
this time, now that it is released.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus
Also, since samba package isn't installed by default (at least in my
18.10 to 19.04 upgrade), how do we fix this without the samba package
installed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
I'm seeing this issue with Disco Dingo 19.04
Using samba/disco,now 2:4.10.0+dfsg-0ubuntu2 amd64 [installed]
Upgrade didn't install samba by default, and nautilus is still having
issues with network share being SMB2 minimum
Solved by:
1. Killing PID of gvfsd-smb-browse
2. Running
This bug was fixed in the package samba - 2:4.7.6+dfsg~ubuntu-0ubuntu2.9
---
samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.9) bionic-security; urgency=medium
* SECURITY UPDATE: save registry file outside share as unprivileged user
- debian/patches/CVE-2019-3880.patch: remove
This bug was fixed in the package samba - 2:4.8.4+dfsg-2ubuntu2.3
---
samba (2:4.8.4+dfsg-2ubuntu2.3) cosmic-security; urgency=medium
* SECURITY UPDATE: save registry file outside share as unprivileged user
- debian/patches/CVE-2019-3880.patch: remove implementations of
Cosmic verification (continued)
Now installing the updated samba packages, and rebuilding gvfs locally:
samba:
Installed: 2:4.8.4+dfsg-2ubuntu2.2
Candidate: 2:4.8.4+dfsg-2ubuntu2.2
Version table:
*** 2:4.8.4+dfsg-2ubuntu2.2 500
500 http://br.archive.ubuntu.com/ubuntu
I think I mixed the verification-done tags, but both are done now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To
Cosmic verification
Confirming the bug:
ubuntu@ubuntu:~$ apt-cache policy samba gvfs-backends
samba:
Installed: 2:4.8.4+dfsg-2ubuntu2.1
Candidate: 2:4.8.4+dfsg-2ubuntu2.1
Version table:
*** 2:4.8.4+dfsg-2ubuntu2.1 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main
Bionic:
full smbstatus output, showing the connection to the pub share as well:
root@ubuntu:~# smbstatus
Samba version 4.7.6-Ubuntu
PID Username GroupMachine
Protocol Version Encryption Signing
Bionic verification (continued)
Now installing the new samba packages. Since I need a gvfs rebuild with
the new samba packages, I'm doing that locally.
So in the end I now have:
samba from proposed:
*** 2:4.7.6+dfsg~ubuntu-0ubuntu2.8 500
500 http://br.archive.ubuntu.com/ubuntu
Bionic verification
Bug reproduced with the following packages:
ubuntu@ubuntu:~$ apt-cache policy samba gvfs-backends
samba:
...
*** 2:4.7.6+dfsg~ubuntu-0ubuntu2.7 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
...
For anyone wanting to test this bug, please note you will also have to
wait for a gvfs rebuild with this new samba package.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Hello Sebastian, or anyone else affected,
Accepted samba into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg
~ubuntu-0ubuntu2.8 in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Sebastian, or anyone else affected,
Accepted samba into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/samba/2:4.8.4+dfsg-
2ubuntu2.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
The so called "browsing a windows network" made use of an SMB1 protocol
version feature. Recent versions of samba, including the one released with
bionic, default to a higher versions of the protocol which lacks this feature.
As a result, the "other
Does the samba task need fixing in disco at all?
** Changed in: samba (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
** Description changed:
[Impact]
The so called "browsing a windows network" made use of an SMB1 protocol
version feature. Recent versions of samba, including the one released with
bionic, default to a higher versions of the protocol which lacks this feature.
As a result, the "other
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/365298
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/365297
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
** Description changed:
- * Impact
- On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that
Nautilus displays "Empty Folder" when clicking "Windows Network"
+ [Impact]
+ The so called "browsing a windows network" made use of an SMB1 protocol
version feature. Recent
It worked with the updated patch. Packages rebuilt in the PPA. I'll
prepare a merge proposal and SRU this into bionic. We will have to
rebuild gvfs there, though, after samba lands in proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The original samba patch had a typo/error, this is the fix for that:
https://github.com/samba-
team/samba/commit/885435e8a4dc561749b880f8be7a32041fa954ec
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
I just tried with my build from the ppa, but it's not working. When
enabling debugging in gvfsd, I can see it setting the protocol to NT1:
network: Added new job source 0x559ce1b3e070 (GVfsBackendNetwork)
network: Queued new job 0x559ce1b4cab0 (GVfsJobMount)
smb-network:
Builds in a ppa look good:
...
Native dependency smbclient found: YES 0.2.3
Checking for function "smbc_setOptionProtocols": YES
...
Checking for real with a bionic desktop now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
Looking at this next.
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: samba (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs
** Changed in: gvfs (Ubuntu Cosmic)
Assignee: (unassigned) => Sebastien Bacher (seb128)
** Changed in: gvfs (Ubuntu Bionic)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gvfs (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse
** Changed in: gvfs (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: gvfs (Ubuntu Cosmic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
Reopening, the fix isn't working until we get the samba change
** Changed in: gvfs (Ubuntu Bionic)
Status: Fix Released => Triaged
** Changed in: gvfs (Ubuntu Cosmic)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop
This bug was fixed in the package gvfs - 1.36.1-0ubuntu1.2
---
gvfs (1.36.1-0ubuntu1.2) bionic; urgency=medium
* debian/patches/git_smb_writing.patch:
- Use O_RDWR to fix fstat when writing (lp: #1803158)
* debian/patches/git_invalid_autorun.patch:
- common: Prevent
This bug was fixed in the package gvfs - 1.38.1-0ubuntu1.1
---
gvfs (1.38.1-0ubuntu1.1) cosmic; urgency=medium
* debian/patches/series:
- include git_invalid_autorun.patch which was mentioned in
the previous upload but not added to the serie
gvfs (1.38.1-0ubuntu1)
1 - 100 of 114 matches
Mail list logo
