Bug 381121

Summary:	kdialog raise segment fault
Product:	[Applications] kdialog	Reporter:	Dorian Han <tunghsu>
Component:	general	Assignee:	Brad Hards <bradh>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	tunghsu
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dorian Han 2017-06-12 09:56:49 UTC

Kdialog always got segment fault when trying to open/upload file in chromium-based browser

Steps to Reproduce:
1. Open Chrome/Chromium/Vivaldi or any other Chromium-based browser
2. Try Ctrl+O to open a file, then it's reported that Kdialog got segment fault

Actual Results:
Kdialog crashed without showing up

Expected Results:
Open a dialog to choose file

Build Date & Platform: 
05/20/2017 on Kubuntu 17.04

Additional Information: 
For browsers does not rely on Kdialog, like firefox, there's no issue on opening a file dialog 

Possible related report: 
https://bugs.kde.org/show_bug.cgi?id=380165
Almost the same issue, however it's related to vlc and that issue had already been fixed on debian releases 2 years ago. FYI I have latest version of vlc installed but without the phonon-backend-vlc pkg.

Crash report 1:
Application: KDialog (kdialog), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f277ed03b79 in KFileDialog::KFileDialog (this=0x7fff7c88c630, startDir=..., filter=..., parent=<optimized out>, customWidget=0x0) at ./kio/kfile/kfiledialog.cpp:266
#7  0x00005634be3a2970 in directCommand (args=<optimized out>) at ./kdialog/kdialog.cpp:562
#8  main (argc=<optimized out>, argv=<optimized out>) at ./kdialog/kdialog.cpp:914

Crash report 2:
Application: KDialog (kdialog), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9e70effd80 (LWP 6395))]

Thread 2 (Thread 0x7f9e5e042700 (LWP 6396)):
#0  0x00007f9e6dd09f73 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f9e6f1b55cf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x00007f9e6f0cae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x00007f9e6bf376da in start_thread (arg=0x7f9e5e042700) at pthread_create.c:456
#4  0x00007f9e6dd1417f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f9e70effd80 (LWP 6395)):
[KCrash Handler]
#6  0x00007f9e7083cb79 in KFileDialog::KFileDialog (this=0x7ffc449aa6f0, startDir=..., filter=..., parent=<optimized out>, customWidget=0x0) at ./kio/kfile/kfiledialog.cpp:266
#7  0x00005583264ba970 in directCommand (args=<optimized out>) at ./kdialog/kdialog.cpp:562
#8  main (argc=<optimized out>, argv=<optimized out>) at ./kdialog/kdialog.cpp:914

Comment 1 Christoph Feck 2017-06-19 23:06:58 UTC

Please ask in a forum of your distribution if you are still using the kdelibs4 version of 'kdialog', or the KF5-based version.

There is no 'directCommand()' function in the current kdialog sources, nor in kdialog from KDE Applications 16.12.0

Comment 2 Dorian Han 2017-06-19 23:28:22 UTC

(In reply to Christoph Feck from comment #1)
> Please ask in a forum of your distribution if you are still using the
> kdelibs4 version of 'kdialog', or the KF5-based version.
> 
> There is no 'directCommand()' function in the current kdialog sources, nor
> in kdialog from KDE Applications 16.12.0

It seems it's based on a KDE 4 version of kdialog. The binary comes from the pkg named kde-baseapps-bin 4:16.04.3-0ubuntu1. There's also a standalone kdialog pkg which provides kdialog_16.12.3-0ubuntu1 however it conflicts with the previous one. Seems a compatibility issue rather than a bug. I'm going to look for answers from distro community. Thanks.

Comment 3 Dorian Han 2017-06-20 00:03:09 UTC

This got fixed by replacing the kde-baseapps-bin 4:16.04.3-0ubuntu1 pkg with kdialog_16.12.3-0ubuntu1 pkg.

Comment 4 Christoph Feck 2017-06-20 00:10:41 UTC

The kde-baseapps package was split into its separate applications (konqueror, kfind, kdialog, keditbookmarks). Usually the distribution automatically deletes obsolete packages and recommends the newer replacements. If this was not the case, it is indeed worth a bug report to the bug tracker of your distribution.

https://community.kde.org/Applications/16.12_Release_Notes