[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@ 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 NAS. But it is also looking for a "Windows Network" (i.e. the Windows "network neighborhood" or workgroup that shows up as a separate subfolder) using SMB1, and that fails if the server does not provide SMB1. Crucially, however, it fails in a way that leaves the gvfsd-smb-browse process in a bad state where it fails to allow browsing of the server even though it has been discovered via mDNS. I encourage you to take a look at my patch, or to use the PPA at https://launchpad.net/~wmaddox3rd/+archive/ubuntu/gvfs-smb-sharelist- patch. It does indeed look like there is a bug here in that attempting discovery via SMB1 somehow breaks browsing of the server discovered via mDNS. See also my remarks here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/307#note_1632096 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 workgroup, which occurs either when attempting to open an URL like smb://WORKGROUP/ or during network discovery in gvfsd- network. My patch simply disables workgroup discovery/browsing functionality, leaving *browsing* functionality intact for servers that are *discovered* via DNS-SD (mDNS). This does not address the issue of discovering Windows 10 servers that advertise themselves only via WS- Discovery, but appears to work fine for devices that advertise themselves using mDNS, allowing those devices to be successfully browsed. I note that workgroups are an obsolete concept in a post-NT1 (post-SMB1) world, so the offending code should eventually just be yanked out, along with the addition of support for WS-Discovery in Linux. My patch does not address the root cause, as whatever is going wrong while attempting to mount a workgroup should result in a recoverable error. I traced gvfsbackendsmbbrowse.c:do_mount() up to the point at which smbc_opendir() is called without any surprises, whereupon things went south. I did not investigate any further, but if I were to do so, I'd be inclined to take a look for an unreleased lock. ** Patch added: "Disable broken workgroup discovery/browsing" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107/+attachment/5639041/+files/smb-browse-patch.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
I experienced this problem when doing a *clean installation* of Ubuntu GNOME 16.04.3. I confirmed that the synaptics driver was in use. apt- get update; apt-get upgrade did not resolve the problem. I was able to get the touchpad settings working by uninstalling the synaptics driver and installing libinput. I had to upgrade a held-back dependency in order to do this, and I'm not sure if the result was entirely kosher. It seems like a clean installation should not have this problem, nor is it clear to me how the synaptics support got dropped in Ubuntu GNOME 16.04.3 when the upstream version affected was 3.20, and 16.04.3 is still documented as including GNOME 3.18. I can understand how these kinds of issues can occur in an upgrade to a new major version such as 17.10, but it's really a big boo-boo to have this sort of breakage in the routine updates to an LTS release. It would at least be helpful to mention this issue in the release notes for UG 16.04.3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Fix Released Status in xorg source package in Artful: Confirmed Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278437] Re: can't move link type .desktop files around on desktop
I am running Ubuntu 16.04.2 and still see the bug. I downloaded the source package nautilus_3.18.4.is.3.14.3-0ubuntu5 and observed that the upstream patch referenced in comment #19 was *not* present. I applied the patch, ran configure/make, and the resulting nautilus binary no longer exhibited the bug. Can we get an updated package for 16.04? It seems it would ease the pain for a lot of people and should be easy to do. I'm not an Ubuntu or Debian developer, and do not know the niceties of preparing a proper package for distribution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1278437 Title: can't move link type .desktop files around on desktop Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Xenial: Confirmed Bug description: * Impact links can't be moved on the desktop * Test case Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html * Regression potential Dnd should keep working -- If I have a .desktop file with Type=Link on my desktop and try to move it around it doesn't stay where I drop it but goes back where it was before and tries to download the URL it is referring to instead. Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html This affects at least 13.10 and 14.04. In 13.10 Nautilus crashes if the URL as a file:// URL referring to a file on your desktop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 14:06:24 2014 GsettingsChanges: InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2013-12-07 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1278437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278437] Re: can't move link type .desktop files around on desktop
Please note that this bug does not only affect links on the desktop, but appears to affect any *.desktop file of type "Link". When I drag the "Examples" link in my home directory to another folder, I get a copy of the the referenced directory "example-content". This kind of flaw in basic functionality looks really bad to new users coming from Windows, and made 14.04 a non-starter for me until I replaced nautilus with nemo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1278437 Title: can't move link type .desktop files around on desktop Status in Nautilus: New Status in “nautilus” package in Ubuntu: Triaged Bug description: If I have a .desktop file with Type=Link on my desktop and try to move it around it doesn't stay where I drop it but goes back where it was before and tries to download the URL it is referring to instead. Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html This affects at least 13.10 and 14.04. In 13.10 Nautilus crashes if the URL as a file:// URL referring to a file on your desktop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 14:06:24 2014 GsettingsChanges: InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2013-12-07 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1278437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
