Dolphin crashes when trying to access a samba share on the network

Support
1

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

**OpenMandriva Lx version:**Rome 25.04

Desktop environment (KDE, LXQT…):

KDE

Description of the issue (screenshots if relevant):

when clicking on the icon for my Truenas under the network tab in Dolphin , Dolphin locks up and crashes.

Relevant informations (hardware involved, software version, logs or output…):

ThinkPad P14s AMD Gen5 8840HS / 64GB Ram / 2TB nvme fresh install of Rome 25.04 using Balena Etcher

1 Like
2

What happens when you try to access that share from the command line? It should give you an error message telling you exactly what it needs.

3

I don’t know your skill level. So, if your skill level is low, don’t let that stop you. This place is about teaching and learning. If you want to step into the shallow end first, open a terminal and type dolphin and the terminal will remain open the whole time dolphin is open. Try to access the share. The terminal should show you messages as you do it.

1 Like
4

[nuclearrage@ThinkPad-P14s-OMLx ~]$ dolphin
QLayout: Cannot add a null widget to QHBoxLayout/
QLayout::removeWidget: Cannot remove a null widget.
smbXcli_negprot_smb1_done: No compatible protocol selected by server.
smbXcli_negprot_smb1_done: No compatible protocol selected by server.
org.kde.dolphin: could not find entry for charset= “Other encoding ()”
kf.kio.core: Internal error: itemsInUse did not contain QUrl(“smb://dlaursen@truenas/”)
kf.kio.core: Fatal Error: HUH? Lister KDirLister(0x556a43848b50) is supposed to be listing, but has no job!
KCrash: Application ‘dolphin’ crashing… crashRecursionCounter = 2
Aborted (core dumped)
[nuclearrage@ThinkPad-P14s-OMLx ~]$

thats a copy of the terminal output when trying to access the share.

5

Just out of curiosity, what happens when you manually type in something similar to this into Dolphin’s navigation bar at the top of Dolphin’s window?

smb://1.1.1.1/

Replacing that 1.1.1.1 IP address with the IP of your TrueNAS. I am assuming your NAS is using a static IP address.

6

file or folder does not exist. It does show up as “TRUENAS” in Dolphin under the “Network” Tab. I used to just click on it and then mount it (at least I thought thats what I did in Fedora KDE) and then could get in.

edit : on a t480s that i have running Rome 25.04 (thought it was an older version , must have updated) and this worked fine. maybe its because I ticked “save password”

7

Did you make any changes to your smb.conf file in OM?

I have always had my best luck in Dolphin by using the IP address of the server that I am connecting to. When I start using names, connections fail. But I never had Dolphin crash.

According to what I found online, it seems Dolphin is trying to use the SMB1 protocol and your server is set up for either SMB2 or SMB3 when using the server name instead of the IP address.

If you still have access to your Fedora installation, check to see what is in its smb.conf and compare the contents to OM’s smb.conf.

There is a way to force SMB2 or SMB3 on the client (Dolphin). I have never tried that. Don’t quote me, but I believe OM’s smb.conf needs min protocol = SMB2 or min protocol = SMB3 added somewhere in the file under [global].

8

I will chase that down. I fired up my other NAS (Fedora Workstation) and it see the NAS at
"smb://“nameofnas”.local … so I typed that in the address bar of Dolphin and it worked. I will try and figure out my smb.conf file , this is a new install (a few hours old) and I hadnt made it that far to change smb.conf .

9

I may have to kick myself after this. Especially if it works.

Check your /etc/hosts file on OM. It looks something like this inside the file:

# Standard host addresses
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

# This host address
127.0.1.1 OM-client-name

Try adding a line to the end of the /etc/hosts file:

# My Server
X.X.X.X your_server’s_name_goes_here

Changing the X.X.X.X to your server’s IP address followed by the name of your server.

I would also double-check your Fedora’s /etc/hosts file to see what it says. I suspect it may have the same line added somewhere in the file.
10

thanks I will give that a shot , the fedora install was toast , but i do have a working OM here to stare and compare with .

edit: working OM install and non working one have identical host files

11

nope , that didn’t work either

thanks for the help tho, I will just keep looking

12

Are you able to ping the server from OM’s terminal? Traceroute?

13

yes , can ping and traceroute (1hop). Also was able to copy 120GB of data off of the NAS , just have to manually type it in the address bar of dolphin. Just not sure why it does that on this machine , kinda screwey.

14

Would this be of any help?
sudo dnf install nss_wins --refresh

15

thanks for the suggestion , but unfortunately it didn’t solve the problem. Dolphin still crashes when trying to open the Truenas folder .

1 Like
16

You can ping the server. Connection to the server by Dolphin is possible when you type in the server’s IP address.

Is it possible that you have a password set on your server? Dolphin is not passing along the password when you try to connect using the server’s name. But when you try to connect using the IP address, the connection happens because the server’s password was stored inside the KWalletManager by Dolphin for that IP address.

I looked inside my KWalletManager and found the username and password for the IP address for my Samba server stored under Passwords/Maps. There was not an entry for the server name.

I went into the /etc/hosts file and added the name of my server with its IP address. Then I was able to go into Dolphin and connect to that server using its name. Dolphin prompted me to enter the username and password, completing the connection. Next, I went into KWalletManager. In Passwords/Maps, I found a new entry for smb-servername:-1, with values for the username and password.

Now, why is it working with the server’s name for me? All I did was add the server’s name and IP address to the /etc/hosts file. Before I added the server to my /etc/hosts file, I was unable to connect using the server’s name.

17

Another thought, because manually typing the IP address into Dolphin does work.

Method 1:

Instead of typing in the IP address of the server every time, it is possible to drag and drop the entry from Dolphin’s location bar to the Places panel. Once in Places, you should be able to right-click to manually edit an alias for its label name.

Method 2:

Right-click on the Places panel and add an entry. Type in your server’s address as smb://1.1.1.1, replacing 1.1.1.1. with your server’s IP address. Then in the label box, type in your server’s name.

18

Thanks again for all the help. So I kinda used your method , but i went to “smb://TRUENAS.local/” in the address bar , then put in name and password and selected save password. Then I clicked on the address bar to copy , then right click on the “Places” to get the “add entry” option and then filled out the box and now I have it permanently under the “Remote” section of the sidebar

1 Like