Bug 384771 - Error when move a file from my home dir, to a windows partition
Summary: Error when move a file from my home dir, to a windows partition
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.3
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2017-09-16 13:00 UTC by regis.carles
Modified: 2018-10-29 02:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description regis.carles 2017-09-16 13:00:35 UTC
Application: kdeinit5 (16.12.3)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.50-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
I was moving a file from my home dir, to one of my NTFS disk directory.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4bdfbc1800 (LWP 9180))]

Thread 2 (Thread 0x7f4bc4ead700 (LWP 9182)):
#0  0x00007f4bde18200d in poll () at /lib64/libc.so.6
#1  0x00007f4bdad6fc94 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f4bdad6fd9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f4bde70ce2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#4  0x00007f4bde6b849a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007f4bde4f23bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x00007f4bdfadd635 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#7  0x00007f4bde4f6ff9 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#8  0x00007f4bdbabe66d in start_thread () at /lib64/libpthread.so.0
#9  0x00007f4bde18de4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4bdfbc1800 (LWP 9180)):
[KCrash Handler]
#6  0x00007f4bde0cb818 in raise () at /lib64/libc.so.6
#7  0x00007f4bde0ccf2a in abort () at /lib64/libc.so.6
#8  0x00007f4bde10a43a in  () at /lib64/libc.so.6
#9  0x00007f4bde113879 in _int_free () at /lib64/libc.so.6
#10 0x00007f4bde116db8 in free () at /lib64/libc.so.6
#11 0x00007f4bde6e2abc in QMetaCallEvent::~QMetaCallEvent() () at /lib64/libQt5Core.so.5
#12 0x00007f4bde6e2b19 in QMetaCallEvent::~QMetaCallEvent() () at /lib64/libQt5Core.so.5
#13 0x00007f4bde6bcb97 in QCoreApplication::removePostedEvents(QObject*, int) () at /lib64/libQt5Core.so.5
#14 0x00007f4bde6e4d2a in QObjectPrivate::~QObjectPrivate() () at /lib64/libQt5Core.so.5
#15 0x00007f4bde6e4ed9 in QObjectPrivate::~QObjectPrivate() () at /lib64/libQt5Core.so.5
#16 0x00007f4bde6ec98c in QObject::~QObject() () at /lib64/libQt5Core.so.5
#17 0x00007f4bc97c4049 in QXcbConnection::~QXcbConnection() () at /lib64/libQt5XcbQpa.so.5
#18 0x00007f4bc97c57c6 in QXcbIntegration::~QXcbIntegration() () at /lib64/libQt5XcbQpa.so.5
#19 0x00007f4bc97c58c9 in QXcbIntegration::~QXcbIntegration() () at /lib64/libQt5XcbQpa.so.5
#20 0x00007f4bde9f38a7 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () at /lib64/libQt5Gui.so.5
#21 0x00007f4bdcf6df69 in QApplicationPrivate::~QApplicationPrivate() () at /lib64/libQt5Widgets.so.5
#22 0x00007f4bde6ec98c in QObject::~QObject() () at /lib64/libQt5Core.so.5
#23 0x00007f4bde6bbfd4 in QCoreApplication::~QCoreApplication() () at /lib64/libQt5Core.so.5
#24 0x00007f4bdcf6f904 in QApplication::~QApplication() () at /lib64/libQt5Widgets.so.5
#25 0x00007f4bd31de46e in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#26 0x000000000040818f in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#27 0x0000000000409437 in handle_launcher_request(int, char const*) [clone .isra.26] ()
#28 0x0000000000409bd6 in handle_requests(int) ()
#29 0x0000000000404dd3 in main ()

Reported using DrKonqi
Comment 1 Julian Steinmann 2018-06-09 16:19:18 UTC
The version of Dolphin you are using is very old. Please update Dolphin & and try to reproduce the crash if possible. Thanks!
Comment 2 Julian Steinmann 2018-06-23 08:50:55 UTC
Have you been able to update Dolphin & test this again? It'd be great if we knew the current status of the report. Thanks!
Comment 3 regis.carles 2018-06-23 12:32:47 UTC
I precise, I use the dolphin split window : on the left side my linux folder partition, on the right side the win32 partition.

After upgrade, when I cut a file from home system in order to paste it in a win32 partition, I have a new message (I translate from french to english) :

" access refused to " my file name.

And I have 4 buttons below :
"try again", "ignore", "ignore always", "cancel"

I'm used to click on "ignore", and then dolphin windows crashes closing itself automatically... I don't have a bug report window to copy/paste here.

If I reopen my linux folder the file has been deleted, and in my win32 folder the file is present : so in despite of the crash window, the file has been cut/pasted.

Note :
The contrary cut/paste (from win32 partition to linux folder) works fine.

Let me know if you need more information.
Comment 4 Andrew Crouthamel 2018-09-28 03:25:07 UTC
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 set the bug status 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!
Comment 5 Andrew Crouthamel 2018-10-29 02:19:11 UTC
Dear Bug Submitter,

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!