[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Joel Koreth changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth --- Hey I can't reproduce this on my end. If a device is dragged to the file window, on my machine at least, dolphin has a menu asking the user whether the user wants to copy it over, link it, or cancel. Possibly fixed? Environment info Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO CC||elvis.angelac...@kde.org --- Comment #2 from Elvis Angelaccio --- Please provide a backtrace with debug symbols or a valgrind log. See also https://community.kde.org/Dolphin/FAQ/Crashes -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #3 from Carlos Quiros --- Created attachment 102608 --> https://bugs.kde.org/attachment.cgi?id=102608&action=edit Device causing the eror This now happens when I drag the OS device to the right Window. All other devices work ok. Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe09e4d57c0 (LWP 3382))] Thread 3 (Thread 0x7fe074d05700 (LWP 3394)): #0 0x7fe09591f30d in poll () at /lib64/libc.so.6 #1 0x7fe09048b954 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe09048ba5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe09674656b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe0966f22ca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe09652b2cc in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe09652feb9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fe092557684 in start_thread () at /lib64/libpthread.so.0 #8 0x7fe09592aefd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fe07fb6e700 (LWP 3390)): #0 0x7fe09591f30d in poll () at /lib64/libc.so.6 #1 0x7fe09048b954 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe09048ba5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe09674656b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe0966f22ca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe09652b2cc in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe096b55295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fe09652feb9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe092557684 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe09592aefd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe09e4d57c0 (LWP 3382)): [KCrash Handler] #6 0x01e0b6b0 in () #7 0x7fe096719758 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe09671a81d in QMimeData::data(QString const&) const () at /usr/lib64/libQt5Core.so.5 #9 0x7fe09c7f21e1 in KIO::isClipboardDataCut(QMimeData const*) () at /usr/lib64/libKF5KIOWidgets.so.5 #10 0x7fe09c81673e in () at /usr/lib64/libKF5KIOWidgets.so.5 #11 0x7fe09c816a91 in () at /usr/lib64/libKF5KIOWidgets.so.5 #12 0x7fe09671f801 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7fe09790fe8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7fe097915016 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7fe0966f3ff8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #16 0x7fe0966f5dda in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #17 0x7fe096746143 in () at /usr/lib64/libQt5Core.so.5 #18 0x7fe09048b787 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #19 0x7fe09048b9b8 in () at /usr/lib64/libglib-2.0.so.0 #20 0x7fe09048ba5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #21 0x7fe09674654f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7fe0966f22ca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #23 0x7fe0966fa38d in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #24 0x7fe09e0beea6 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so #25 0x7fe0958447d0 in __libc_start_main () at /lib64/libc.so.6 #26 0x00400af9 in _start () -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #4 from Christoph Feck --- The backtrace from comment #3 still lacks debug symbols for qt and kio. If https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports does not help, please ask in a forum of your distribution. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Resolution|BACKTRACE |WAITINGFORINFO --- Comment #5 from Julian Schraner --- Works fine for me. Can you still reproduce this crash with Dolphin 17.12.3? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #6 from Julian Schraner --- It would be great if you could add a complete backtrace by following the steps described in comment 4. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #7 from Julian Schraner --- If we do not get a response in the next two weeks, I'll close this bug as WORKSFORME because despite various attempts I have not been able to reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Julian Schraner --- No response -> closing. Please reopen the report if you can still reproduce this crash with an updated version of Dolphin. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Resolution|BACKTRACE |WAITINGFORINFO --- Comment #5 from Julian Schraner --- Works fine for me. Can you still reproduce this crash with Dolphin 17.12.3? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #6 from Julian Schraner --- It would be great if you could add a complete backtrace by following the steps described in comment 4. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #7 from Julian Schraner --- If we do not get a response in the next two weeks, I'll close this bug as WORKSFORME because despite various attempts I have not been able to reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Julian Schraner --- No response -> closing. Please reopen the report if you can still reproduce this crash with an updated version of Dolphin. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Joel Koreth changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth --- Hey I can't reproduce this on my end. If a device is dragged to the file window, on my machine at least, dolphin has a menu asking the user whether the user wants to copy it over, link it, or cancel. Possibly fixed? Environment info Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO CC||elvis.angelac...@kde.org --- Comment #2 from Elvis Angelaccio --- Please provide a backtrace with debug symbols or a valgrind log. See also https://community.kde.org/Dolphin/FAQ/Crashes -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #3 from Carlos Quiros --- Created attachment 102608 --> https://bugs.kde.org/attachment.cgi?id=102608&action=edit Device causing the eror This now happens when I drag the OS device to the right Window. All other devices work ok. Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe09e4d57c0 (LWP 3382))] Thread 3 (Thread 0x7fe074d05700 (LWP 3394)): #0 0x7fe09591f30d in poll () at /lib64/libc.so.6 #1 0x7fe09048b954 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe09048ba5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe09674656b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe0966f22ca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe09652b2cc in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe09652feb9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fe092557684 in start_thread () at /lib64/libpthread.so.0 #8 0x7fe09592aefd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fe07fb6e700 (LWP 3390)): #0 0x7fe09591f30d in poll () at /lib64/libc.so.6 #1 0x7fe09048b954 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe09048ba5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe09674656b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe0966f22ca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe09652b2cc in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe096b55295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fe09652feb9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe092557684 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe09592aefd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe09e4d57c0 (LWP 3382)): [KCrash Handler] #6 0x01e0b6b0 in () #7 0x7fe096719758 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fe09671a81d in QMimeData::data(QString const&) const () at /usr/lib64/libQt5Core.so.5 #9 0x7fe09c7f21e1 in KIO::isClipboardDataCut(QMimeData const*) () at /usr/lib64/libKF5KIOWidgets.so.5 #10 0x7fe09c81673e in () at /usr/lib64/libKF5KIOWidgets.so.5 #11 0x7fe09c816a91 in () at /usr/lib64/libKF5KIOWidgets.so.5 #12 0x7fe09671f801 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7fe09790fe8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7fe097915016 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7fe0966f3ff8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #16 0x7fe0966f5dda in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #17 0x7fe096746143 in () at /usr/lib64/libQt5Core.so.5 #18 0x7fe09048b787 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #19 0x7fe09048b9b8 in () at /usr/lib64/libglib-2.0.so.0 #20 0x7fe09048ba5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #21 0x7fe09674654f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7fe0966f22ca in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #23 0x7fe0966fa38d in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #24 0x7fe09e0beea6 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so #25 0x7fe0958447d0 in __libc_start_main () at /lib64/libc.so.6 #26 0x00400af9 in _start () -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 --- Comment #4 from Christoph Feck --- The backtrace from comment #3 still lacks debug symbols for qt and kio. If https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports does not help, please ask in a forum of your distribution. -- You are receiving this mail because: You are watching all bug changes.
