Dolphin causing kioslave5 to crash system

As Mirror176 suggested: add a user to the system, log in as the new user.

Is the issue reproducible for the new user?

(From what I see in an openSUSE discussion, I doubt that it will make a difference, but do please try.)

Zagzigger said:
kf.kio.core: "/usr/local/bin/dolphin is a file, but a folder was expected."
Click to expand...

A folder should not be expected, because truly, it's a file.

Code: 
% file /usr/local/bin/dolphin
/usr/local/bin/dolphin: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 15.0 (1500023), FreeBSD-style, stripped
% freebsd-version -kru ; uname -aKU
15.0-CURRENT
15.0-CURRENT
15.0-CURRENT
FreeBSD mowa219-gjp4-zbook-freebsd 15.0-CURRENT FreeBSD 15.0-CURRENT main-n272200-299175f2e52e GENERIC-NODEBUG amd64 1500023 1500023
%
 
Given up and gone to GhostBSD as said elsewhere.
I won't annoy people any more by writing about it until I've run it as a workstation for a couple of weeks.
BTW, it's FreeBSD all the way - pkg system, repositories and all.
 
Zagzigger said:
SirDice, that must be the fastest reply ever.
Unfortunately, although it did stop those /net/ errors, it created the following (seen on dmesg)
============================================================
da0: <Generic USB SD Reader 1.00> Removable Direct Access SCSI device
da0: Serial Number 058F312D81B
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
da0: quirks=0x2<NO_6_BYTE>
da1 at umass-sim0 bus 0 scbus10 target 0 lun 1
da1: <Generic USB CF Reader 1.01> Removable Direct Access SCSI device
da1: Serial Number 058F312D81B
da1: 40.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present
da1: quirks=0x2<NO_6_BYTE>
da2 at umass-sim0 bus 0 scbus10 target 0 lun 2
da2: <Generic USB SM Reader 1.02> Removable Direct Access SCSI device
da2: Serial Number 058F312D81B
da2: 40.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
da2: quirks=0x2<NO_6_BYTE>
da3 at umass-sim0 bus 0 scbus10 target 0 lun 3
da3: <Generic USB MS Reader 1.03> Removable Direct Access SCSI device
da3: Serial Number 058F312D81B
da3: 40.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
================================================================
There must be something more basic wrong in some other configuration path. And my very basic level of knowledge doesn't help me.
I thought at one stage it was something to do with Polkit (as that's been patched three times without explanation - see pkg polkit-124_3. But that's as far as I go.


My /etc/auto_master: now looks like
# Automounter master map, see auto_master(5) for details.
#
# /net -hosts -nobrowse,nosuid,intr
# When using the -media special map, make sure to edit devd.conf(5)
# to move the call to "automount -c" out of the comments section.
#/media -media -nosuid,noatime,autoro
#/- -noauto

Thanks again for such a prompt reply, I'll now try and understand devd.conf - but more advice would be most welcome.
Click to expand...
Y'know, when I see that kind of stuff in dmesg, my first reaction is to check how well my USB sticks are seated. It does look like not plugging them in tightly causes FreeBSD to stop seeing those sticks. And in your case, Dolphin crashes when the USB connection is lost... Not that unusual, I've had that happen to me, too.
 
astyle said:
Y'know, when I see that kind of stuff in dmesg, my first reaction is to check how well my USB sticks are seated. It does look like not plugging them in tightly causes FreeBSD to stop seeing those sticks. And in your case, Dolphin crashes when the USB connection is lost... Not that unusual, I've had that happen to me, too.
Click to expand...
Thanks will do. The machine has been moved from Australia to the UK, but as the main system boots from a NVMe and worked straight off, it never occurred to me.
Thanks; even if that's not the reason. Will come back and report.
====================================================
You were probably right. The disks inside the case were loose and one completely unconnected - so that's what probably started the whole mess.
However, the system is probably now not worth salvaging. But just for those still interested, after reconnecting the loose and unconnected disks, I now get:
===================================
Security policy loaded: MAC/ntpd (mac_ntpd)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1953 (dolphin)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1953 (dolphin)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1953 (dolphin)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1953 (dolphin)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1953 (dolphin)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1953 (dolphin)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1977 (kioslave5)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1977 (kioslave5)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1977 (kioslave5)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1977 (kioslave5)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1977 (kioslave5)
WARNING: autofs_trigger_one: request for /net/ completed with error 5, pid 1977 (kioslave5)
===============================================
And then from the console where I ran dolphin, I get
====================================================
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
kf.kio.core: "The file or folder /usr/home/murf/todo.txt does not exist."
kf.kio.core: "/usr/local/bin/dolphin is a file, but a folder was expected."
kf.kio.core: "The file or folder /preferences does not exist."
=====================================================
So after all that, you were probably right, it was due to disconnected drives to begin with, then after adjusting some of dolphin's config files, it's probably not worth digging around any more.
As said, I've moved over to GhostBSD - and, so far, it is a much more understandable and smoother experience.
Thanks again; at least I learnt something from this experience.
 
You must log in or register to reply here.
Back
Top