| Summary: | Dolphin crashes while accessing remote folders (samba) | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Gaël Bonithon <trash.paradise> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | 2012gdwu+k2, andalexo, elvis.angelaccio, ivan.pessotto, justin.zobel, mauricio.torres.ma |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 16.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Gaël Bonithon
2018-04-12 16:01:30 UTC
*** Bug 393889 has been marked as a duplicate of this bug. *** Created attachment 114915 [details]
New crash information added by DrKonqi
dolphin (18.08.0) using Qt 5.11.1
- What I was doing when the application crashed:
Trying to access a samba share on a Windows PC for the first time. I think it crashed right after I entered the password.
-- Backtrace (Reduced):
#6 std::__atomic_base<int>::load (__m=std::memory_order_relaxed, this=<error reading variable: Cannot access memory at address 0x20>) at /usr/include/c++/8/bits/atomic_base.h:390
#7 QAtomicOps<int>::load<int> (_q_value=<error reading variable: Cannot access memory at address 0x20>) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227
#8 QBasicAtomicInteger<int>::load (this=<error reading variable: Cannot access memory at address 0x20>) at /usr/include/qt5/QtCore/qbasicatomic.h:103
#9 QtPrivate::RefCount::isShared (this=<error reading variable: Cannot access memory at address 0x20>) at /usr/include/qt5/QtCore/qrefcount.h:101
[...]
#11 0x00007f558304cb89 in QList<NonMovableFileItem>::begin (this=0x20) at /usr/include/qt5/QtCore/qlist.h:322
*** Bug 403414 has been marked as a duplicate of this bug. *** Created attachment 119420 [details]
New crash information added by DrKonqi
dolphin (18.12.3) using Qt 5.11.3
- What I was doing when the application crashed:
Exploring samba shares with password authentication
- Custom settings of the application:
Saved username and password on systemsettings
-- Backtrace (Reduced):
#9 0x00007f71254829ac in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib64/libKF5CoreAddons.so.5
#10 0x00007f7125483541 in KJob::finishJob(bool) () from /usr/lib64/libKF5CoreAddons.so.5
#11 0x00007f71280df6c8 in KIO::SimpleJob::slotFinished() () from /usr/lib64/libKF5KIOCore.so.5
#12 0x00007f71280d399b in KIO::ListJob::slotFinished() () from /usr/lib64/libKF5KIOCore.so.5
[...]
#14 0x00007f71280b5604 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib64/libKF5KIOCore.so.5
Thanks for the bug report. I'm often using samba folders from my server and I haven't seen this crash. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks. Sorry but I haven't been using KDE for a while, let alone Samba, so I don't really have a way to test if this bug still exists. I see that other people are following this bug report: if they can answer for me, don't hesitate to do so. Thanks! (In the meantime, I leave the status of the report as is) 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |