[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 Windows mapped drive assignments made to Ubuntu samba shares have continued to work over time, but new shares cannot be seen unless SMB1 is enabled. of course, this should all just work using newer secure protocols. For a significant piece of server software, the fact that this hasn't been addressed long ago is a real mystery. -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 could once again see the shares. -- 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/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
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 (all running
Windows 10 at this point) and had made file browser bookmarks to the
important shares long ago. These bookmarks have continued to work to
this day without issue. I got a new Windows 10 machine a few weeks ago
and was having the problem everyone reports of not being able to connect
("Failed to retrieve share list from server") on the new machine, even
though all the existing bookmarks were still functioning file. All of
the Windows 10 machines were able to see one another without problem.
Then I ran across this thread and tried Bloodyiron's suggestion of
killing the gvfsd-smb-browse process. Immediately I was able to connect
to the new machine using Nemo. I quickly created some needed bookmarks
to the important shares and now I can communicate using the file browser
and expect the new bookmarks to be as reliable as the others. So I
would suggest this bookmark method to others as a workaround.
This supports Craig W's comment about the difference between discovery
and browsing. When I run "smbclient -L // -U ", it
reports all of the shares on the target, whether Windows or Linux, with
the closing message: "SMB1 disabled -- no workgroup available" as
expected.
Unfortunately, this is only a one-way solution. All of the legacy
Windows 10 machines can see and access the Samba shares on the Xubuntu
box, but I haven't yet figured out a way to get the new Windows machine
to access these same shares, with or without gvfsd-smb-browse running.
Every connection attempt is rejected and I haven't found useful messages
in the logs. If I figure out a solution, I'll post here, and I'm open
to suggestions.
I agree with the general sentiment that for a service as important as
this, there isn't any real excuse for this thing dragging out for two
years as it has.
--
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/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1406735] [NEW] package udev 208-8ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 102
Public bug reported: A few weeks ago I installed Ubuntu 10.10 server with the addition of the xubuntu-desktop packages. Everything started out alright until i tried to install sendmail in place of postfix. That installaton failed, reporting a similar error: subprocess installed post-installation script returned error exit status 102 From there, things went from bad to worse. I was now unable to finish the install of sendmail nor could I remove it fully and reinstall postfix. Spamassassin seemed to be one critical package that hept reporting errors. As I tried to install or remove packages using synaptic, the system most of the time refused to act due to dascading errors and partially removed packages that could not be removed, even by force. Today I threw up my hands and did a complete fresh install of the system. Everything went well for the basic packages until I ran software updater. A few packages were scheduled to be updated, including udev and it has now faild in the exact same manner. Could someone look at this and provide a quick reply as to what can be done to rectify this situation. I am afraid to install or remove any other software for fear of corrupting the system further and I currently do not have a usable system. Let me know if additional information is required. Thanks. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: udev 208-8ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CustomUdevRuleFiles: .70-persistent-net.rules Date: Wed Dec 31 01:40:11 2014 DuplicateSignature: package:udev:208-8ubuntu8.1:subprocess installed post-installation script returned error exit status 102 ErrorMessage: subprocess installed post-installation script returned error exit status 102 InstallationDate: Installed on 2014-12-31 (0 days ago) InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release amd64 (20141022.2) MachineType: ASUSTeK COMPUTER INC. Z9PE-D8 WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=d7121d57-8cf9-42a5-b7c3-75f414ce3e09 ro nomdmonddf nomdmonisw SourcePackage: systemd Title: package udev 208-8ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 102 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z9PE-D8 WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5503:bd05/06/2014:svnASUSTeKCOMPUTERINC.:pnZ9PE-D8WS:pvr1.0x:rvnASUSTeKCOMPUTERINC.:rnZ9PE-D8WS:rvr1.0x:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.name: Z9PE-D8 WS dmi.product.version: 1.0x dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1406735 Title: package udev 208-8ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1406735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.
I also have this problem. I recently installed 14.04.1 on a new Xeon system and did not see this for a few days. However, as I have done system configuration, I now find that every time I log in, I get a pop- up window with a title Document Not Found and the above message at the content. The yelp package is installed, but I didn't do this manually. I assume it was part of the initial installation or else was installed as a dependency by some other package that I installed. When I select help from the pull-down menu, it accesses the following url without problem: file:///usr/share/xubuntu-docs/about/xubuntu-index.html When I search the filesystem for ubuntu-help/index, the only hits are: /usr/share/help-langpack/en_AU/ubuntu-help/index.page /usr/share/help-langpack/en_CA/ubuntu-help/index.page /usr/share/help-langpack/en_GB/ubuntu-help/index.page Solving the problem would be great. As a workaround, stopping the pop-up at login would be nice. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1360756 Title: The URI ‘help:ubuntu-help/index’ does not point to a valid page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1360756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
