[dolphin] [Bug 486896] New: Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78

[Hugh Phoenix-Hulme]

https://bugs.kde.org/show_bug.cgi?id=486896

            Bug ID: 486896
           Summary: Browsing SMB causes kioslave5 to throw errors in
                    libnvidia-tls.550.78
    Classification: Applications
           Product: dolphin
           Version: 23.08.5
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: hugh at webnet.org.uk
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Install nvidia driver 550.78
2. Open Dolphin
3. Browse to SMB

OBSERVED RESULT

The Dolphin tab displays the message "The process for the smb://a.b.c.d
protocol died unexpectedly."
Crash report appears in systray: "kioslave5 Closed Unexpectedly."
KDE Crash Handler reports this Developer Information:

Application: kioslave5 (kioslave5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007a932e25c618 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-tls.so.550.78
#5  0x732e36312d465455 in ?? ()
#6  0x00007a9331e3006f in __gconv_transform_internal_ascii
(step=0xec81481574d3d1, data=0x48f0e08348ca2918, inptrp=0x89480000098be8e7,
inend=0x7ffc9caa2290 "@#\252\234\374\177", outbufstart=0xffff24b1e8e78948,
irreversible=0x8948ffff2723e8c7, do_flush=1401505809,
consume_incomplete=726164680) at ../iconv/skeleton.c:547
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
[Inferior 1 (process 1552475) detached]


EXPECTED RESULT

None of the above.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13

ADDITIONAL INFORMATION

libnvidia-tls.so is for Thread Local Storage. Renaming it to prevent it being
loaded solves the problem, but why is it being loaded?

This seems like a pretty terrible scenario. Some external component is causing
undesirable behaviour, but when that component is unavailable, everything
works. So literally anything has the potential to break kioslave5. Should
kioslave5 be ignoring exceptions while trying to load libraries at this point?
Is there a way to blacklist libraries so kioslave5 doesn't try to load them? (I
doubt I can get away with removing the thread local storage lib systemwide - I
could try it, but I don't expect it'll be pretty.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.