Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 533040 - [kde overlay] kde-apps/dolphin-5.9999 crashes every time I use Shift-Delete.
Summary: [kde overlay] kde-apps/dolphin-5.9999 crashes every time I use Shift-Delete.
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-19 16:58 UTC by Petros
Modified: 2014-12-19 18:00 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (info,9.28 KB, text/plain)
2014-12-19 16:58 UTC, Petros
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petros 2014-12-19 16:58:51 UTC
Created attachment 392036 [details]
emerge --info

Dolphin (5.9999) seems to be problematic with the option to permanetely delete a file or a directory. Each and every time I press Shift and Delete it crashes. 

Kcrash:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa80a88f800 (LWP 3031))]

Thread 4 (Thread 0x7fa808848700 (LWP 3033)):
#0  0x00007fa80cffbc0f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fa808d23fc3 in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x00007fa808d238d7 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x00007fa80cff6446 in start_thread () from /lib64/libpthread.so.0
#4  0x00007fa8100c6b6d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fa803219700 (LWP 3034)):
#0  0x00007fa80c79c7ca in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x00007fa80c79cba9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fa80c7542db in g_main_context_query () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fa80c754af2 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x00007fa80c754cad in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#5  0x00007fa80e1aaa4b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6  0x00007fa80e14c64a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7  0x00007fa80df3713b in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x00007fa80df3c3ac in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x00007fa80cff6446 in start_thread () from /lib64/libpthread.so.0
#10 0x00007fa8100c6b6d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fa7eeffc700 (LWP 3048)):
#0  0x00007fa80cffbfb8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fa80c79cfc8 in g_cond_wait_until () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fa80c727741 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fa80c727def in g_async_queue_timeout_pop () from /usr/lib64/libglib-2.0.so.0
#4  0x00007fa80c77e7af in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x00007fa80c77dc35 in ?? () from /usr/lib64/libglib-2.0.so.0
#6  0x00007fa80cff6446 in start_thread () from /lib64/libpthread.so.0
#7  0x00007fa8100c6b6d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fa80a88f800 (LWP 3031)):
[KCrash Handler]
#5  0x00007fa80f60f664 in KNotification::id() () from /usr/lib64/libKF5Notifications.so.5
#6  0x00007fa80f610599 in ?? () from /usr/lib64/libKF5Notifications.so.5
#7  0x00007fa80f611a9c in ?? () from /usr/lib64/libKF5Notifications.so.5
#8  0x00007fa80e180c49 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#9  0x00007fa80f6339ef in KNotificationPlugin::finished(KNotification*) () from /usr/lib64/libKF5Notifications.so.5
#10 0x00007fa80f626f89 in ?? () from /usr/lib64/libKF5Notifications.so.5
#11 0x00007fa80f634813 in ?? () from /usr/lib64/libKF5Notifications.so.5
#12 0x00007fa80e3c1e82 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x00007fa80e182784 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#14 0x00007fa80eb549ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#15 0x00007fa80eb5a740 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#16 0x00007fa80e14ef4b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#17 0x00007fa80e15117e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#18 0x00007fa80e1aa613 in ?? () from /usr/lib64/libQt5Core.so.5
#19 0x00007fa80c7548e3 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fa80c754bd8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fa80c754cad in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fa80e1aaa34 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#23 0x00007fa80e14c64a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#24 0x00007fa80e15466f in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#25 0x00007fa8104cb091 in kdemain () from /usr/lib64/libkdeinit5_dolphin.so
#26 0x00007fa80fffbf90 in __libc_start_main () from /lib64/libc.so.6
#27 0x000000000040072e in _start ()
Comment 1 Michael Palimaka (kensington) gentoo-dev 2014-12-19 17:15:24 UTC
Looks like upstream bug #222324. Not much we can do about it.
Comment 2 Petros 2014-12-19 17:24:34 UTC
Sorry for any inconvenience, should I report these problems upstream? I was told tha bug reports are filtered and forwarded properly by developers.
Comment 3 Michael Palimaka (kensington) gentoo-dev 2014-12-19 17:49:27 UTC
No problem, we're always happy to get bug reports and certainly appreciate your interest and testing efforts.

Bug reports here definitely are good as sometimes it's a downstream issue and we can avoid bothering upstream. Even if it definitely is an upstream issue, in certain cases it's worth tracking here too to help better identify the issue or backport any patches that appear etc.

In this particular case, the issue looks to be the same as a long-running unresolved upstream crash bug. Given the little activity there, I don't think on this occasion there's much value tracking downstream. Still appreciate the report though. :)
Comment 4 Petros 2014-12-19 18:00:53 UTC
Oh nice! We also appreciate the effort and politeness of yours. Have a nice day Mr Palimaka.