Summary: | When browse to smb location using smb:// got kioworker crash | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Gilberto Ferreira <gilberto.nunes32> |
Component: | bars: location | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | crash | CC: | fanzhuyifan, graeme.merrall, kdedev, kfm-devel, lukasz.tolwinski, virnik |
Priority: | NOR | Keywords: | qt6 |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=482502 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Gilberto Ferreira
2024-03-18 13:02:16 UTC
What version of Dolphin was this reproduced with? Might I ask you to re-test with the latest version of Dolphin? I am not able to reproduce this on Dolphin on Solus or Neon When I type "smb://" in Dolphin, and hit Enter, after a few moments I see the samba shares on my network. Operating System: Solus 4.5 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.3 Kernel Version: 6.8.9-289.current (64-bit) Graphics Platform: Wayland Dolphin 24.02.2 Operating System: KDE Neon 6.0 (VM) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic Graphics Platform: Wayland Dolphin 24.02.2 I also tested going to Network - Shared Folders (smb) in both Solus and Neon. Neither crashed. (In reply to TraceyC from comment #1) > What version of Dolphin was this reproduced with? > Might I ask you to re-test with the latest version of Dolphin? I am not able > to reproduce this on Dolphin on Solus or Neon > When I type "smb://" in Dolphin, and hit Enter, after a few moments I see > the samba shares on my network. > > Operating System: Solus 4.5 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.6.3 > Kernel Version: 6.8.9-289.current (64-bit) > Graphics Platform: Wayland > Dolphin 24.02.2 > > > Operating System: KDE Neon 6.0 (VM) > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.5.0-28-generic > Graphics Platform: Wayland > Dolphin 24.02.2 As you can see for my first report, I was used what follow below KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Perhaps now it's work with Plasma 6.0.4 and Framework 6.1.0 I will check it ou. I think I do have the same issue. I can browse network (samba) neighborhood just fine, I do see all computers with samba enabled. But due to testparm's warning of 'Week' crypto being used, kio sees this warning as an error, and exit with non-zero exit code. https://gist.github.com/virnik0/da7b7fd8f76f40c9492d05cec07eae39 (In reply to Vojtěch Weiss from comment #4) > I think I do have the same issue. > > I can browse network (samba) neighborhood just fine, I do see all computers > with samba enabled. But due to testparm's warning of 'Week' crypto being > used, kio sees this warning as an error, and exit with non-zero exit code. > > https://gist.github.com/virnik0/da7b7fd8f76f40c9492d05cec07eae39 Forgot to add system details: https://gist.github.com/virnik0/5d542bf8fc8bb15301062a92141d03fb Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! There are now two users (one of them me) who are seeing this problem with Solus Plasma. It was reported in [this issue](https://github.com/getsolus/packages/issues/2677) in the Solus bug tracker I ran the same command with gdb - here is the [full output](https://bpa.st/4LRQ) That was from a Dell XPS laptop. On a Flex with the same repo, version of Plasma, Dolphin and same kernel, there is no problem browsing the same samba shares. Kernel 6.8.11-292.current Dolphin 24.02.2 On the machine where the bug is present, Nemo is able to browse the samba shares. The issue seen by Vojtěch about "Weak crypto is allowed by GnuTLS" looks different. In the gdb output I captured, I see the same crash but nothing about an error due to weak crypto. You might search through open bugs for that and open a new issue if there isn't one already. (In reply to TraceyC from comment #7) > There are now two users (one of them me) who are seeing this problem with > Solus Plasma. > It was reported in [this > issue](https://github.com/getsolus/packages/issues/2677) in the Solus bug > tracker > > I ran the same command with gdb - here is the [full > output](https://bpa.st/4LRQ) > That was from a Dell XPS laptop. On a Flex with the same repo, version of > Plasma, Dolphin and same kernel, there is no problem browsing the same samba > shares. > > Kernel 6.8.11-292.current > Dolphin 24.02.2 > > On the machine where the bug is present, Nemo is able to browse the samba > shares. > > The issue seen by Vojtěch about "Weak crypto is allowed by GnuTLS" looks > different. In the gdb output I captured, I see the same crash but nothing > about an error due to weak crypto. You might search through open bugs for > that and open a new issue if there isn't one already. May I ask how your SMB is configured? The complains from testparm are based simply on GnuTLS and its ability to serve 'weak crypto' - it doesn't necessarily means that you do allow NT auth. I am not certain whether it is related or not, but I found it interesting. The fact is that kio crashes while accessing smb share. Maybe your testparm binary or gnutls version differs? I am especially intriqued by the fact that one of your systems doesn't crash while browsing smb shares....why is that so? *** Bug 491196 has been marked as a duplicate of this bug. *** (In reply to cwo from comment #9) > *** Bug 491196 has been marked as a duplicate of this bug. *** I believe that the problem comes from some forgotten library, which gets loaded althought it shouldn't. I tried fresh install in separate ZFS dataset, and it works there without an issue. The same for my freshly installed son's gaming rig (he purchased completely new HW with the same setup as I have). But, another system which was upgraded recently the same way like my own was (from Ubuntu 23.10 to 24.04), experiences identical issue, which leads me to assumption that the upgrade process, or better some package post/pre-install script didn't do the cleanup properly. But if this assumption is correct, how can I find out? How can I pin-point the right file which was supposed to be removed and wasn't? I don't think it is SMB config issue. Can't comment on TraceyC's problem, but as both looks very similar, here is my config: [global] workgroup = home.lan server string = Family Desktop PC netbios name = Mainframe interfaces = lo enp5s0 enp6s0 virbr0 wlx74da38e226e3 hosts allow = 127. 10. 172. 10.43. 192.168.1. 192.168.254. hosts deny = 192.168.254.11 remote announce = 10.43.16.63/HOME.LAN 10.43.16.127/HOME.LAN 10.43.16.159/HOME.LAN remote browse sync = 10.43.16.2 client min protocol = SMB2_02 client max protocol = SMB3 server min protocol = SMB3 server max protocol = SMB3 msdfs root = no ; ntlm auth = ntlmv2-only ; client ntlmv2 auth = yes browsable = yes log file = /var/log/samba/%m.log max log size = 50 security = user passdb backend = tdbsam obey pam restrictions = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . pam password change = yes guest account = guest map to guest = Bad User case sensitive = yes hostname lookups = yes socket options = TCP_NODELAY domain master = no local master = no preferred master = no time server = no os level = 32 wins support = yes dns proxy = yes load printers = no cups options = raw name resolve order = bcast wins lmhosts host ; map archive = no ; map hidden = no ; map read only = no ; map system = no store dos attributes = yes unix charset = utf8 dos charset = cp1250 invalid users = root #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes valid users = %S guest ok = no create mask = 700 directory mask = 700 [public] path = /home/guest/Public browsable = yes read only = no guest ok = yes force user = guest force group = users create mask = 770 directory mask = 770 https://bugs.kde.org/show_bug.cgi?id=487834 and it just happened now again. The samba config on both my machines, where I can reproduce and where it works properly is identical Both machines have the warning about weak crypto. While that may make other code unhappy, it is not the cause of the crash ``` ❯ testparm -l -s Load smb config files from /usr/share/defaults/samba/smb.conf Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback) Server role: ROLE_STANDALONE # Global parameters [global] client ipc max protocol = SMB3 client ipc min protocol = SMB2_02 client max protocol = SMB3 disable spoolss = Yes guest account = sambaguest load printers = No log file = /var/log/samba/log.%m map to guest = Bad User max log size = 500 printcap name = /dev/null server role = standalone server server string = Samba server (version: %v, protocol: %R) usershare allow guests = Yes usershare max shares = 100 usershare owner only = No usershare path = /var/lib/samba/usershare idmap config * : backend = tdb create mask = 0644 hosts allow = 127.0.0. 10. 172.16.0.0/255.240.0.0 192.168. 169.254. ::1 fd00::/8 fe80::/10 hosts deny = ALL include = /etc/samba/smb.conf printing = bsd [homes] browseable = No comment = Home Directories hosts allow = hosts deny = include = lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j print command = lpr -r -P'%p' %s read only = No ❯ testparm -l -s > ~/Nextcloud/testparm_xps.txt Load smb config files from /usr/share/defaults/samba/smb.conf Loaded services file OK. Weak crypto is allowed by GnuTLS ``` |