[Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
Launchpad has imported 9 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=392447. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-03-28T11:37:42+00:00 Suse wrote: Dolphin doesn't show any samba share. smb:// and smb://workgroup/ are empty. However, smbtree is always working. If made all test with deactivated firewall. Entering a specific share like smb://twvm1/ is always working. I've made many test with different distributions and software versions: DOES NOT WORK: Tumbleweed with: Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba: 4.7.6 Fedora 27 with Plasma: 5.12.2 Framework: 5.44.0 Applications: 17.12.2 Samba: 4.7.6 Neon with Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba 4.3.11-Ubuntu extra file: ~/.smb/smb.conf [global] client max protocol = SMB2 -- WORKS: Neon with Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba 4.3.11-Ubuntu Tumbleweed with: Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba: 4.6.16 (Downgraded with repo home:j-engel) Tumbleweed with: Plasma: 5.12.3 Framework: 5.44.0 Applications: 17.12.3 Samba: 4.7.6 extra file: ~/.smb/smb.conf [global] client max protocol = NT1 === Conclusion: As soon as the samba protocol newer NT1 (e.g. SMB2) is used, then dolphin doesn't show the samba shares. You can force the usage of NT1 via: - Samba < 4.7 or adding the extra file ~/.smb/smb.conf [global] client max protocol = NT1 You can force the usage of SMB2 or SMB3 via: - Samba >= 4.7 or adding the extra file ~/.smb/smb.conf [global] client max protocol = SMB3 Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/0 On 2018-03-28T11:40:01+00:00 Suse wrote: Created attachment 111699 journalctl of samba 4.7.6 This log is from a samba 4.7.6 machine where the SMB2 or SMB3 protocol is used. I've clicked on "samba shares" in dophin (= smb://). Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/1 On 2018-04-30T15:58:54+00:00 ben van 't ende wrote: I added the extra file ~/.smb/smb.conf [global] client max protocol = NT1 For Kubuntu 18.04 (Samba version 4.7.6-Ubuntu) to get it to work Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/10 On 2018-05-05T18:01:15+00:00 Strangiato Xanadu wrote: I can not confirm. My two computers run Arch Linux pc A: kde plasma 5.12.5, frameworks 5.45, dolphin 18.04, samba 4.8.1 pc B: Gnome 3.28.1, nautilus 3.28.1, samba 4.8.1 Both computers have "[global] client max protocol = SMB2" in their smb.conf file. Dolphin from pc A shows the samba shares from pc B. Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/21 On 2018-05-06T00:32:32+00:00 Strangiato Xanadu wrote: *** Bug 393880 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/22 On 2018-06-23T10:08:22+00:00 Y-dev-4 wrote: I can confirm this behavior with openSUSE Leap 15.0 (Plasma 5.12.5, Frameworks 5.45.0) on the client and Samba 4.6.14 on the server. Dolphin shows nothing with smb:// if I go to the share directly in Dolphin it works. With smbtree the shares are showing correctly. The following file on the client helps, thank you: ~/.smb/smb.conf [global] client max protocol = NT1 But it would be better do solve this issue in the smb kio plugin directly. Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/25 On 2018-07-20T21:06:01+00:00 Nate-b wrote: *** Bug 392803 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/26 On 2018-07-20T21:06:02+00:00 Nate-b wrote: *** Bug 388000 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767454/comments/27 On 2018-07-20T21:14:38+00:00 Nate-b wrote: Migrating information from a duped bug: The SMB1 protocol is deprecated and Microsoft strongly urges people not to use it. Windows 2016 server does not
[Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
** Bug watch added: KDE Bug Tracking System #392447 https://bugs.kde.org/show_bug.cgi?id=392447 ** Also affects: nautilus via https://bugs.kde.org/show_bug.cgi?id=392447 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1766652] Re: sidebar view - second subcategory list you navigate to has incorrect colors for the top entry
** Changed in: systemsettings Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to systemsettings in Ubuntu. https://bugs.launchpad.net/bugs/1766652 Title: sidebar view - second subcategory list you navigate to has incorrect colors for the top entry To manage notifications about this bug go to: https://bugs.launchpad.net/systemsettings/+bug/1766652/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1766652]
does this still happen with Kirigmai master from 20th july 2018 or more recent? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to systemsettings in Ubuntu. https://bugs.launchpad.net/bugs/1766652 Title: sidebar view - second subcategory list you navigate to has incorrect colors for the top entry To manage notifications about this bug go to: https://bugs.launchpad.net/systemsettings/+bug/1766652/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1718911] Re: Pop-up notification position: ubuntu-desktop notification settings conflicting with plasma-desktop notification settings
Hello Anuszka, Thank you for submitting this bug and reporting a problem with notifications in Kubuntu. You made this bug report some time ago and Ubuntu and Kubuntu have been updated since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you let us know and, run the following (only once): apport-collect 1718911 and upload the updated logs and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu and Kubuntu better. G ** Changed in: plasma-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1718911 Title: Pop-up notification position: ubuntu-desktop notification settings conflicting with plasma-desktop notification settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1718911/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1766652]
Nope, seems fixed now. Thanks! -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to systemsettings in Ubuntu. https://bugs.launchpad.net/bugs/1766652 Title: sidebar view - second subcategory list you navigate to has incorrect colors for the top entry To manage notifications about this bug go to: https://bugs.launchpad.net/systemsettings/+bug/1766652/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
:D Well I most certainly hope people can *think* when they see the lines are active by default. Good luck to anyone who's trying to fix this bug ! Cheers. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Except I can't, so it has to stay there. Hopefully everybody who runs into this reads on... -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
@MibuKyoshiro True, sorry I seem to have been overly tired when writing this. I'm correcting it in my original comment. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1768649] Re: [CVE] Access to privileged files
I don't plan on fixing this for Trusty. Trusty has a very early upstream commit, and it goes EOL in a few months. In my personal opinion, it's not worth the many hours it'll take to properly backport and test it. ** Changed in: pam-kwallet (Ubuntu Trusty) Assignee: Simon Quigley (tsimonq2) => (unassigned) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to pam-kwallet in Ubuntu. https://bugs.launchpad.net/bugs/1768649 Title: [CVE] Access to privileged files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1768649/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
