Bug 362273

Summary: kate seg-faults on opening small newly created gpg file
Product: [Applications] kate Reporter: rlaggren
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cullmann, rlaggren
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: test file that crashes kate on opening

Description rlaggren 2016-04-26 01:32:16 UTC 
Create new encrypted file from sample small text file.  Run Kate, open new file. Kate dies,  Complete output when kate is started in a terminal:

Phonon::GStreamer::Backend: Failed to initialize GStreamer
QTimeLine::start: already running
Segmentation fault

"About kate" info window shows:

Version 15.12.3
Using:
KDE Frameworks 5.20.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

Reproducible: Always

Steps to Reproduce:
1.Create new encrypted file from sample small text file.  
2.Run Kate,
3. open new file

Actual Results:  
kate dies. When running from a terminal, output says

"Phonon::GStreamer::Backend: Failed to initialize GStreamer
QTimeLine::start: already running
Segmentation fault
"

Expected Results:  
kate displays open file, probably read only, and complains about a binary file

Tried a couple of small gpg files. Same result. Kate has not shown this behavior w/any other files. Normally I use kate to review any/all files, some very large, binary has never been a problem. But I only use kate two or three times a week for this purpose. Not a kate power user.
Comment 1 rlaggren 2016-04-26 01:38:16 UTC 
Created attachment 98598 [details]
test file that crashes kate on opening

I created  couple of these using gpg. All crashed kate.
Comment 2 Christoph Cullmann 2016-05-28 19:34:09 UTC 
Autor: Dominik Haumann <dhaumann@kde.org>  2016-03-29 17:52:02
Eintragender: Dominik Haumann <dhaumann@kde.org>  2016-03-29 17:52:02
Eltern: 1e8b5370ddd2751d00ef823840077ae1562faf52 (fix crash due to uninitialized variable (bug #357341))
Kind:  1596261e68c2665f143e95e44dc666398761daed (Simplify code (qCount -> std::count, homegrown isprint -> QChar::isPrint))
Zweig: master, remotes/origin/master
Folgt auf: v4.100.0-rc1
Vorgänger von: 

    encoding detection: fix crash in wrong usage of isprint
    
    If the first characters was negative, we always hit a crash in the
    encoding detection. This patch fixes this.
    
    BUG: 357341
    REVIEW: 127488
    CHANGELOG: encoding detection: fix crash in wrong usage of isprint (bug #357341)
Comment 3 Dominik Haumann 2016-05-29 10:24:19 UTC 

*** This bug has been marked as a duplicate of bug 357341 ***