Bug 392156 - Konqueror does not start when I click "show in folder" on google-chrome
Summary: Konqueror does not start when I click "show in folder" on google-chrome
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-03-22 00:25 UTC by Marcelo Jimenez
Modified: 2018-12-20 18:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Jimenez 2018-03-22 00:25:35 UTC
Application: kdeinit5 (5.0.97)

Qt Version: 5.10.0
Frameworks Version: 5.43.0
Operating System: Linux 4.15.7-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to open konqueror in the directory where I downloaded a PDF document, but Konqueror did not start when I click "show in folder" on google-chrome.

-- Backtrace:
Application: Konqueror (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
28	  return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7f560b7548c0 (LWP 6712))]

Thread 3 (Thread 0x7f55df5f8700 (LWP 6715)):
#0  0x00007f5609830d9f in __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x00007f5609819166 in __GI___poll (fds=0x7f55d80049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#2  0x00007f5605d05109 in g_idle_add () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f55d8001e80 in  ()
#4  0x0000000105d2203d in  ()
#5  0xffffffff7fffffff in  ()
#6  0xb9e490d9c162ff00 in  ()
#7  0x0000000000000005 in  ()
#8  0x00007f55d8000bf0 in  ()
#9  0x0000000000000001 in  ()
#10 0x0000000000000004 in  ()
#11 0x00007f55d8000b20 in  ()
#12 0x0000000000000000 in  ()

Thread 2 (Thread 0x7f55f2506700 (LWP 6714)):
#0  0x00007f5609814bf4 in __GI___libc_read (fd=8, buf=0x7f55f2505ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007f5605d49420 in g_unix_fd_add_full () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f55e4000bf0 in  ()
#3  0x00007f55e4000bf0 in  ()
#4  0x00007f55e4000bf0 in  ()
#5  0xb9e490d9c162ff00 in  ()
#6  0x0000000000000000 in  ()

Thread 1 (Thread 0x7f560b7548c0 (LWP 6712)):
[KCrash Handler]
#6  0x000000000000b716 in  ()
#7  0x00007f55d3231901 in  () at /usr/lib64/libgobject-2.0.so.0
#8  0x00007f560b5aa40a in call_init (l=<optimized out>, argc=argc@entry=5, argv=argv@entry=0x7ffc90c54e08, env=env@entry=0x5625d5d0cda0) at dl-init.c:72
#9  0x00007f560b5aa516 in call_init (env=0x5625d5d0cda0, argv=0x7ffc90c54e08, argc=5, l=<optimized out>) at dl-init.c:118
#10 0x00007f560b5aa516 in _dl_init (main_map=main_map@entry=0x5625d646f680, argc=5, argv=0x7ffc90c54e08, env=0x5625d5d0cda0) at dl-init.c:119
#11 0x00007f560b5ae67f in dl_open_worker (a=a@entry=0x7ffc90c52420) at dl-open.c:511
#12 0x00007f560985fe5f in __GI__dl_catch_exception (exception=exception@entry=0x7ffc90c52400, operate=operate@entry=0x7f560b5ae2c0 <dl_open_worker>, args=args@entry=0x7ffc90c52420) at dl-error-skeleton.c:196
#13 0x00007f560b5adf1a in _dl_open (file=0x5625d6402338 "/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so", mode=-2147479551, caller_dlopen=0x7f5609d7324c, nsid=<optimized out>, argc=5, argv=<optimized out>, env=0x5625d5d0cda0) at dl-open.c:594
#14 0x00007f5608d06f96 in dlopen_doit (a=a@entry=0x7ffc90c52650) at dlopen.c:66
#15 0x00007f560985fe5f in __GI__dl_catch_exception (exception=exception@entry=0x7ffc90c525f0, operate=operate@entry=0x7f5608d06f40 <dlopen_doit>, args=args@entry=0x7ffc90c52650) at dl-error-skeleton.c:196
#16 0x00007f560985feef in __GI__dl_catch_error (objname=objname@entry=0x5625d5c75ae0, errstring=errstring@entry=0x5625d5c75ae8, mallocedp=mallocedp@entry=0x5625d5c75ad8, operate=operate@entry=0x7f5608d06f40 <dlopen_doit>, args=args@entry=0x7ffc90c52650) at dl-error-skeleton.c:215
#17 0x00007f5608d07685 in _dlerror_run (operate=operate@entry=0x7f5608d06f40 <dlopen_doit>, args=args@entry=0x7ffc90c52650) at dlerror.c:162
#18 0x00007f5608d07051 in __dlopen (file=<optimized out>, mode=<optimized out>) at dlopen.c:87
#19 0x00007f5609d7324c in  () at /usr/lib64/libQt5Core.so.5
#20 0x00007f5609d6ca75 in  () at /usr/lib64/libQt5Core.so.5
#21 0x00007f55fbe01052 in  () at /usr/lib64/libphonon4qt5.so.4
#22 0x00007f55fbe02c2c in  () at /usr/lib64/libphonon4qt5.so.4
#23 0x00007f55fbe030ae in  () at /usr/lib64/libphonon4qt5.so.4
#24 0x00007f55fbe03a2c in Phonon::Factory::backend(bool) () at /usr/lib64/libphonon4qt5.so.4
#25 0x00007f55fbe03fb3 in  () at /usr/lib64/libphonon4qt5.so.4
#26 0x00007f55fbdf9331 in  () at /usr/lib64/libphonon4qt5.so.4
#27 0x00007f55fbdf6820 in  () at /usr/lib64/libphonon4qt5.so.4
#28 0x00007f55fc4f729a in  () at /usr/lib64/libKF5Notifications.so.5
#29 0x00007f55fc4d1b51 in  () at /usr/lib64/libKF5Notifications.so.5
#30 0x00007f55fc4ce764 in KNotification::sendEvent() () at /usr/lib64/libKF5Notifications.so.5
#31 0x00007f5609da5c52 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#32 0x00007f560843001c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#33 0x00007f5608437314 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#34 0x00007f5609d77148 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#35 0x00007f5609d79b25 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#36 0x00007f5609dcf393 in  () at /usr/lib64/libQt5Core.so.5
#37 0x00007f5605d04f57 in g_timeout_add_seconds_full () at /usr/lib64/libglib-2.0.so.0
#38 0x00007ffc90c53220 in  ()
#39 0x00005625d5d7a680 in  ()
#40 0x0000000000000000 in  ()

Reported using DrKonqi
Comment 1 Christoph Feck 2018-12-20 18:53:56 UTC
Crash is caused by dlopen library loader error, possibly because of a broken ldconfig setup. If this is reproducible with all packages updated from consistent repositories, please report this issue directly to the bug tracker of your distribution.