Ubuntu 18.04. I connect my NAS by typing \\mynas into dolphin's location bar. I am prompted for the login credentials. After typing them in, dolphin crashes. This happens everytime I try it. After logging in and after the crash when I open another dolphin window, I am not prompted again for the login (probably KDE has cached it somewhere), but on opening \\mynas again, it crashes directly. The crash reporting tool tells me that the report is useless as I do not have the debug symbols installed. But which package do I have to install to get them? The crash assistant does not find the package.
(In reply to g111 from comment #0) > Ubuntu 18.04. I connect my NAS by typing \\mynas into dolphin's location > bar. I am prompted for the login credentials. After typing them in, dolphin > crashes. > > This happens everytime I try it. > > After logging in and after the crash when I open another dolphin window, I > am not prompted again for the login (probably KDE has cached it somewhere), > but on opening \\mynas again, it crashes directly. > > The crash reporting tool tells me that the report is useless as I do not > have the debug symbols installed. But which package do I have to install to > get them? The crash assistant does not find the package. Hi, You can find more information about how to install the debug packages for your install here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 Are you able to install the relevant packages and reproduce the issue you're experiencing?
We still need a backtrace to do anything about this.
With kubuntu 19/10 and KDE 5.18 from ppa dolphin still is crashing. I have no idea which dbg package I need to install. Do you have a hint for me?
If you paste the un-symbolicated crash report anyway, we can probably help you find the relevant debug packages.
Hm, trying to reproduce the crash again, dolphin connected the NAS without crashing!? But this time I was not asked for my password. It seems to be stored since the last try in the same session. Probably I have to log out and in again?
So I have logged out and in again. Opened dolphin. Ctrl+l to focus the location bar. Entered "\\mynas". And again dolphin crashed. Here is the developer report: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2efe075e80 (LWP 14909))] Thread 5 (Thread 0x7f2eeffff700 (LWP 14913)): #0 0x00007f2f0064bc30 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f2f005ffa24 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f2f005ffb73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f2f02682653 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f2f026295cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f2f02462a45 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f2f02463c92 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007f2f00ef8669 in start_thread (arg=<optimized out>) at pthread_create.c:479 #8 0x00007f2f0476e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f2ef5fc7700 (LWP 14912)): #0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x564a1ccdddf8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564a1ccddda8, cond=0x564a1ccdddd0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564a1ccdddd0, mutex=0x564a1ccddda8) at pthread_cond_wait.c:638 #3 0x00007f2ef660dabb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x00007f2ef660d6db in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x00007f2f00ef8669 in start_thread (arg=<optimized out>) at pthread_create.c:479 #6 0x00007f2f0476e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2ef7fff700 (LWP 14911)): #0 0x00007f2f04761c2f in __GI___poll (fds=0x7f2ef00029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f2f005ffa3e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f2f005ffb73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f2f02682653 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f2f026295cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f2f02462a45 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f2f02903efa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007f2f02463c92 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f2f00ef8669 in start_thread (arg=<optimized out>) at pthread_create.c:479 #9 0x00007f2f0476e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2efd16c700 (LWP 14910)): #0 0x00007f2f04761c2f in __GI___poll (fds=0x7f2efd16bca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f2f00eb5917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007f2f00eb753a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007f2efd96b288 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007f2f02463c92 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f2f00ef8669 in start_thread (arg=<optimized out>) at pthread_create.c:479 #6 0x00007f2f0476e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2efe075e80 (LWP 14909)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x00007f2f04671899 in __GI_abort () at abort.c:79 #8 0x00007f2f03f3de0d in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #9 0x00007f2f04052cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #10 0x00007f2f02656558 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f2f037d95a0 in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #12 0x00007f2f037da0ab in KJob::finishJob(bool) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #13 0x00007f2f03ff43a8 in KIO::SimpleJob::slotFinished() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x00007f2f03feb91e in KIO::ListJob::slotFinished() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x00007f2f02656558 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f2f03fc4932 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #17 0x00007f2f03fc262f in KIO::SlaveInterface::dispatch() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #18 0x00007f2f03fcb832 in KIO::Slave::gotInput() () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #19 0x00007f2f02656558 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007f2f02656e4a in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x00007f2f03115a86 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x00007f2f0311ee00 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x00007f2f0262aa2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007f2f0262d6a8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007f2f02683037 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007f2f005ff84d in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f2f005ffad0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f2f005ffb73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f2f02682635 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007f2f026295cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x00007f2f02631336 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x00007f2f048896f5 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #33 0x00007f2f046731e3 in __libc_start_main (main=0x564a1b95c060, argc=1, argv=0x7ffff0392a78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff0392a68) at ../csu/libc-start.c:308 #34 0x0000564a1b95c09e in _start () [Inferior 1 (process 14909) detached]
Looks like you'll want the debug package for kio. It might be called something like libkf5kio-dbg. If not, try `apt search kio` to find it. I am also noticing that you're using software that's almost two years old. Dolphin is now on version 19.12.2. Is there a chance you could upgrade to a newer version of Kubuntu to gain access to a newer Dolphin version and verify that the problem is still happening?
Sorry, but I still cannot find such a debug symbol package: root@flupp:~# apt search kio debug Sorting... Done Full Text Search... Done libclutter-imcontext-0.1-0-dbg/eoan 0.1.4-3build1 amd64 Open GL based interactive canvas library IMContext framework (debug files) libghc-iospec-dev/eoan 0.3.1.1-1 amd64 Pure specification of the IO monad libghc-iospec-doc/eoan,eoan 0.3.1.1-1 all Pure specification of the IO monad; documentation libghc-iospec-prof/eoan 0.3.1.1-1 amd64 Pure specification of the IO monad; profiling libraries root@flupp:~# apt search kio dbg Sorting... Done Full Text Search... Done libclutter-imcontext-0.1-0-dbg/eoan 0.1.4-3build1 amd64 Open GL based interactive canvas library IMContext framework (debug files) root@flupp:~# root@flupp:~# apt search kf5 dbg Sorting... Done Full Text Search... Done root@flupp:~# apt search kf5 debug Sorting... Done Full Text Search... Done libkf5akonadisearchdebug5/eoan,now 4:19.04.3-0ubuntu1 amd64 [installed,automatic] Akonadi search debug library libkf5notifications-dev/eoan 5.67.0-0ubuntu1~ubuntu19.10~ppa2 amd64 Framework for desktop notifications Why do you think that I have an old version of dolphin installed? Here is the version information: dolphin: 19.12.2 Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-29-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 7,7 GiB of RAM
You might need to enable a repo or something: https://wiki.ubuntu.com/Debug%20Symbol%20Packages
I think it does not help to add standard ubuntu repos. It has to be a repo with debug symbols that matches the kde-ppa-backports repository with KDE 5.18.
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!
Does not anybody know how to install the debug symbols in kubuntu? How can I contact the dolphin or kio maintainer who build the packages for kubuntu?
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!
This bug still happens in kubuntu 20.10. Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-33-generic OS Type: 64-bit I have installed the package kubuntu-debug-installer that should help to find the debug packages in drkonqi, but it cannot find them fpr dolphin, so I think there are none available.
Unfortunately we can't do anything without a complete trace. You might want to check with a kubuntu support forum of sorts to figure out what to do to get debug symbols for your dolphin.
Just as info: I have updated to kubuntu 21.04. The crash still happens. And I still cannot find any debug symbols ;) Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-17-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 3000