[dolphin] [Bug 505969] New: Dolphin crash after trying to access smb-Server

[email protected]
Newsgroups gmane.comp.kde.devel.kfm
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=505969

            Bug ID: 505969
           Summary: Dolphin crash after trying to access smb-Server
    Classification: Applications
           Product: dolphin
      Version First 25.04.2
       Reported In:
          Platform: openSUSE
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

Application: dolphin (25.04.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.1
Frameworks Version: 6.15.0
Operating System: Linux 6.15.2-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.4.0 [CoredumpBackend]

-- Information about the crash:
After requesting the Password for the SMB-Server, Dolphin crashed to desktop.
openSuSE Tumbleweed, 25-06-22

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007f9ffb75539b in QArrayDataPointer<KFileItem>::data (this=0x30) at
/usr/include/qt6/QtCore/qarraydatapointer.h:120
#6  QArrayDataPointer<KFileItem>::constBegin (this=0x30) at
/usr/include/qt6/QtCore/qarraydatapointer.h:126
#7  QList<KFileItem>::begin (this=<optimized out>, this=<optimized out>) at
/usr/include/qt6/QtCore/qlist.h:659
#8  KCoreDirListerCache::slotUpdateResult (this=0x5648caa2e050, j=<optimized
out>) at /usr/src/debug/kio-6.15.0/src/core/kcoredirlister.cpp:1728
#9  0x00007f9ff92199a1 in QtPrivate::QSlotObjectBase::call (this=<optimized
out>, r=<optimized out>, a=<optimized out>, this=<optimized out>, r=<optimized
out>, a=<optimized out>) at
/usr/src/debug/qtbase-everywhere-src-6.9.1/src/corelib/kernel/qobjectdefs_impl.h:461
#10 doActivate<false> (sender=0x5648cb8058d0, signal_index=6,
argv=0x7ffc4528e980) at
/usr/src/debug/qtbase-everywhere-src-6.9.1/src/corelib/kernel/qobject.cpp:4146
[...]
#12 KJob::result (this=this@entry=0x5648cb8058d0, _t1=<optimized out>,
_t1@entry=0x5648cb8058d0, _t2=...) at
/usr/src/debug/kcoreaddons-6.15.0/build/src/lib/KF6CoreAddons_autogen/include/moc_kjob.cpp:475
#13 0x00007f9ffad9233b in KJob::finishJob (this=0x5648cb8058d0,
emitResult=<optimized out>) at
/usr/src/debug/kcoreaddons-6.15.0/src/lib/jobs/kjob.cpp:115
#14 0x00007f9ff92199a1 in QtPrivate::QSlotObjectBase::call (this=<optimized
out>, r=<optimized out>, a=<optimized out>, this=<optimized out>, r=<optimized
out>, a=<optimized out>) at
/usr/src/debug/qtbase-everywhere-src-6.9.1/src/corelib/kernel/qobjectdefs_impl.h:461
#15 doActivate<false> (sender=0x5648cb7aa050, signal_index=7,
argv=0x7ffc4528ea68) at
/usr/src/debug/qtbase-everywhere-src-6.9.1/src/corelib/kernel/qobject.cpp:4146
#16 0x00007f9ffb77ed3d in KIO::WorkerInterface::finished (this=0x5648cb7aa050)
at
/usr/src/debug/kio-6.15.0/build/src/core/KF6KIOCore_autogen/include/moc_workerinterface_p.cpp:341
#17 KIO::WorkerInterface::dispatch (this=0x5648cb7aa050, _cmd=104, rawdata=...)
at /usr/src/debug/kio-6.15.0/src/core/workerinterface.cpp:127
#18 0x00007f9ffb7774c4 in KIO::WorkerInterface::dispatch (this=0x5648cb7aa050)
at /usr/src/debug/kio-6.15.0/src/core/workerinterface.cpp:58
#19 0x00007f9ffb77aeb0 in KIO::Worker::gotInput (this=0x5648cb7aa050) at
/usr/src/debug/kio-6.15.0/src/core/worker.cpp:261
#20 0x00007f9ff92199a1 in QtPrivate::QSlotObjectBase::call (this=<optimized
out>, r=<optimized out>, a=<optimized out>, this=<optimized out>, r=<optimized
out>, a=<optimized out>) at
/usr/src/debug/qtbase-everywhere-src-6.9.1/src/corelib/kernel/qobjectdefs_impl.h:461
#21 doActivate<false> (sender=0x5648cb766d50, signal_index=3,
argv=0x7ffc4528ee68) at
/usr/src/debug/qtbase-everywhere-src-6.9.1/src/corelib/kernel/qobject.cpp:4146


Reported using DrKonqi

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.