[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Ruth Ivimey-Cook changed: What|Removed |Added CC|r...@ivimey.org | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427738] New: "POP3 Account" stays as the name for each email I set up; have to check setting each time to tell which it is!
https://bugs.kde.org/show_bug.cgi?id=427738 Bug ID: 427738 Summary: "POP3 Account" stays as the name for each email I set up; have to check setting each time to tell which it is! Product: kmail2 Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: ruthesro...@zoho.com Target Milestone: --- SUMMARY I've used KMail for over 13 years, and always preferred it for the multiple accounts I could set up and check ALL my emails in about 2 hours a day. Today I installed LEAP 15.2 and the new KMail2 (vs.5.14.2 (20.04.2)) is frustrating me no end. I don't really care for IMAP, but I've even tried that. When I set up the outgoing account for a domain email, I give it my abbreviated code names, but all of them now show in the drop-down list as "POP3 Account" - so to find out which one it is, I have to go back into the settings to check. I've changed some of them to IMAP, which solves this problem, but this will be a near learning curve. I dread having to go often to each email in their Cpanel, to sweep out the emails I've deleted in KMail. Is this a permanent feature now, or am I just lacking some setup info? If it's a bug, I'd sure like it cleared up. I've already lost several days to computer issues, and need to get back to my work routines! STEPS TO REPRODUCE 1. Tried it dozens of times tonight, both for POP3, and IMAP 2. 3. OBSERVED RESULT The generic term, "POP3 Account" is still always the menu/list name for the emails. EXPECTED RESULT to be able to name each email for the Check Mail dropdown list by name. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.18.5 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #218 from Ruth Ivimey-Cook --- Ryan, you are correct. The 'lines' are actually areas of the window that are transparent, and when the compositor then does its thing, those transparent areas show whatever is behind the konsole window. My investigations (see previous comments) suggest this is a maths error (probably inappropriate rounding) in the Qt drawing code, probably exacerbated by the way Konsole does its painting. Just for the record, I *have* seen the same problems in other places, though they are much rarer. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 425917] New: Mac Labplot crashes whenever I try to name something
https://bugs.kde.org/show_bug.cgi?id=425917 Bug ID: 425917 Summary: Mac Labplot crashes whenever I try to name something Product: LabPlot2 Version: 2.7.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: malen...@moravian.edu Target Milestone: --- Created attachment 131250 --> https://bugs.kde.org/attachment.cgi?id=131250=edit LabPlotCrashReport SUMMARY Whenever I try to name something, the system crashes STEPS TO REPRODUCE 1. create a worksheet 2. plot a function 3. click on the "Name" box to name the function OBSERVED RESULT: Labplot2 quits unexpectedly EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #216 from Ruth Ivimey-Cook --- On 16/08/2020 13:16, Christoph Cullmann wrote: > https://bugs.kde.org/show_bug.cgi?id=373232 > > --- Comment #215 from Christoph Cullmann --- > I still think is: > > https://bugreports.qt.io/browse/QTBUG-78963 > > See for more details > > https://cullmann.io/posts/kde-qt-highdpi-scaling/ > > I traced down the paint stuff, too, and think we paint the "right" rectangles > but that is then afterwards not properly "clipped". > > If you can provide them with some way to reproduce, that would be nice, I did > fail. > Well it's not too hard to demonstrate that at least some of the QRects are correct with my debug patches. I find vim is quite good at reliably producing and erasing extraneous lines, so I'll give it a go. Ruth -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #213 from Ruth Ivimey-Cook --- Created attachment 130908 --> https://bugs.kde.org/attachment.cgi?id=130908=edit Patchfile of debugging code intended to assist finding terminal display bugs. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #214 from Ruth Ivimey-Cook --- I did some more work trying to understand the issue yesterday and as part of that created some debug prints to show what is happening. Note that the debug includes a macro "delay()" which was intended to slow things down enough to watch what happens. Change the delay amount or remove the call to delay() as appropriate. I had previously presumed the bug was an 'off-by-one' error but the debug code indicates that updates do happen on the appropriate pixel areas. I no longer think this explains it. However the lines do appear more reliably when the drawTextFragments() call isn't followed by anything else. I think, though at present this is a guess, that the problem is a rounding error. If internally the scaling code is rounding down rather than up, a fractional half or third of a pixel could be reduced to 0, and that when then scaled up that results in whole rows or columns of pixels not written. I say this is a guess because I haven't yet found the evidence for it. What is also obvious from the resulting trace is that there is a lot of apparently unnecessary repainting going on. Partly this is because ::paintEvent is being called with a damage rectangle equal to the terminal widget size, for reasons I cannot yet explain. It would be good to eliminate the excessive repainting because it partly masks the actual issues, and partly because it is just making everything slower. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Ruth Ivimey-Cook changed: What|Removed |Added CC||r...@ivimey.org --- Comment #201 from Ruth Ivimey-Cook --- I have been seeing the problem as well, using a 4K screen, Ubuntu Focal / x11 on Intel gpu, with scale=1.7 set in kde display settings. AFAIK it doesn't matter much which scale is used if it's fractional. I noticed the mention of qt5.15 earlier and so have built qt(head 5.15) and kde(head master) from latest sources to see if this fixes the problem. I eventually built the whole of qt except Krita and SignonD. This build is better compared to kubuntu focal, slightly, but does not fix it (kubuntu shows many more places with damage, not just konsole). I did a test just now: in dark-background vim with the cursor at the bottom of the screen, autorepeat-uparrow to the screen top results in multiple horizontal lines under the cursor. autorepeat down-arrow tends to clear them, though not always. I also often see a vertical line to the right of the cursor when typing at a prompt, though for some reason this tends not to remain afterwards. It sort of looks like I've got both a horizontal underline cursor and a vertical one, though the vertical is one char offset. With a white window (new firefox tab) behind Konsole, the lines in the konsole window are white. iconising the window behind means the lines in konsole change colour to the desktop wallpaper -- i.e. the lines are actually transparent, not opaque. I had a look at the relevant code, particularly TerminalDisplay.cpp. There are a few uses of QRectF in there, which IIRC is a floating point rectangle. I'm not sure how hidpi works -- does it result in fractional pixel addresses, which might require floats? Is the problem possibly that more QRects and QPoints in the code should be QRectF? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416318] As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!
https://bugs.kde.org/show_bug.cgi?id=416318 --- Comment #5 from Ruth --- Thank you, Laurent, I've found that file, however I'm not able to delete it in Dolphin. Is that something I need to do at the command line? What is the exact command to give? Oh, wait. I could try the Super User file manager because this is down in the root area. I paused to try that and sure enough, I've been able to delete that plugin. Then I went into KMail, and it took two tries, but now I've been able to delete that email! Wonderful! Thanks ever so much! I will save this information in case I ever need it again - hopefully not, eh? Blessings & Thanks, Ruth On Thu, 16 Jan 2020 23:57:49 -0600 Laurent Montel wrote https://bugs.kde.org/show_bug.cgi?id=416318 --- Comment #4 from Laurent Montel <mailto:mon...@kde.org> --- You can remove this plugin /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so => it will not crash. it was fixed in new version but for your version the better workaround is removing it. Regards -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416318] As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!
https://bugs.kde.org/show_bug.cgi?id=416318 --- Comment #3 from Ruth --- I was asked for a back trace, and just now when Kmail crashed, I did get a popup offering me a backtrace. It said it was not of any help, but I'll paste it here in case it tells you anything. Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2e13a67980 (LWP 1860))] Thread 28 (Thread 0x7f2cdd724700 (LWP 6987)): #0 0x7f2e060578ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2dfa65dc45 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2dfa65e127 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2dfa65eec1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2dfa65b55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2e06051569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2e10ae39ef in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f2cea32e700 (LWP 6980)): #0 0x7f2df3f154b0 in pa_mainloop_dispatch () from /usr/lib64/libpulse.so.0 #1 0x7f2df3f158be in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #2 0x7f2df3f15940 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #3 0x7f2df3f237a9 in ?? () from /usr/lib64/libpulse.so.0 #4 0x7f2dec255428 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #5 0x7f2e06051569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2e10ae39ef in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f2d767cc700 (LWP 6956)): #0 0x7f2e060578ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2dfa65dc45 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2dfa65e127 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2dfa65eec1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2dfa65b55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2e06051569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2e10ae39ef in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f2daa7fc700 (LWP 6953)): #0 0x7f2e060578ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2df62c9574 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f2df62c95b9 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f2e06051569 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2e10ae39ef in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f2daaffd700 (LWP 6950)): #0 0x7f2e10ad4c98 in read () from /lib64/libc.so.6 #1 0x7f2e041dcc80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2e04197cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2e04198150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f2e041982bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2e1141e96b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f2e113c390a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f2e111e1daa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f2e111e6ced in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f2e06051569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f2e10ae39ef in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f2d7affd700 (LWP 2150)): #0 0x7f2e10af0b5c in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f2e10af28b4 in __fprintf_chk () from /lib64/libc.so.6 #2 0x7f2df1d80ffd in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #3 0x7f2df1d81194 in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7f2df1d82abc in ?? () from /usr/lib64/libevent-2.1.so.6 #5 0x7f2df1d78764 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6 0x7f2dfa62eb2d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f2dfa62adc8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f2dfa64785b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f2dfa65f486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f2dfa65b55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f2e06051569 in start_thread () from /lib64/libpthread.so.0 #12 0x7f2e10ae39ef in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f2d7b7fe700 (LWP 2149)): #0 0x7f2e060578ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2dfa653699 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2dfa6536c7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2dfa62e4fb in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2dfa62adc8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2dfa64785b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f2dfa65f486 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f2dfa65b55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f
[kmail2] [Bug 416318] As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!
https://bugs.kde.org/show_bug.cgi?id=416318 --- Comment #2 from Ruth --- ahm... I am a little naive when it comes to these technical things. In the past there was a notice inviting a backtrace, but since this crash happens so quickly, I'm not sure how I would get a backtrace. Is that something I have to do at commandline? That's my weak spot. But if you tell me what to do, I'm willing to try. Thanks, Ruth On Wed, 15 Jan 2020 23:51:20 -0600 Laurent Montel wrote https://bugs.kde.org/show_bug.cgi?id=416318 Laurent Montel <mailto:mon...@kde.org> changed: What|Removed |Added CC||mailto:mon...@kde.org --- Comment #1 from Laurent Montel <mailto:mon...@kde.org> --- Hi, Could you paste backtrace ? Regards -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416318] New: As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!
https://bugs.kde.org/show_bug.cgi?id=416318 Bug ID: 416318 Summary: As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time! Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: ruthesro...@zoho.com Target Milestone: --- SUMMARY some months ago (2019) this happened and I finally just avoided touching that one message line. It came to the top and I just worked around it. Finally I re-installed my system, openSUSE LEAP 15.1, and the problem was gone. I set up my 2 dozen emails and all was fine until tonight. A different email with an attachment came in, as soon as I click on it, KMail vanishes! over and over again! I really hope I don't have to reinstall my whole system to clear this up! STEPS TO REPRODUCE 1. Just click on that one email with a newsletter attachment. 2. The whole KMail program closes too fast to click on any Report Bug link. 3. OBSERVED RESULT KMail crashes instantly EXPECTED RESULT I see and read the email, and the attached newsletter. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Email Client Copyright © 1997–2018, KMail authors http://userbase.kde.org/KMail (available in About System) KDE Plasma Version: KDE Frameworks 5.55.0 The xcb windowing system KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 (built against 5.9.7) ADDITIONAL INFORMATION I would be grateful to know how to delete the culprit email. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358229] New: KDE Crash on startup
https://bugs.kde.org/show_bug.cgi?id=358229 Bug ID: 358229 Summary: KDE Crash on startup Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mar...@buffalo.edu CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Powered up computer for the first time today. Plasma crashes right after login. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb199940800 (LWP 1924))] Thread 6 (Thread 0x7fb17b337700 (LWP 1942)): #0 0x7fb18f5b5cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb18f5734b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb18f573d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb18f573f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb1937bbd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb193762d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb19358461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fb19686fdf8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fb19358932f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb19269b0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb192e9a04d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb16f3bc700 (LWP 1943)): #0 0x7fb192ea661f in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7fb192e91c12 in poll () at /lib64/libc.so.6 #2 0x7fb18f573e64 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb18f573f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb1937bbd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb193762d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb19358461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fb19686fdf8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fb19358932f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb19269b0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb192e9a04d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb16d928700 (LWP 1946)): #0 0x7fb18f57348b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb18f573d80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb18f573f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb1937bbd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb193762d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb19358461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb19686fdf8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fb19358932f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb19269b0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb192e9a04d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb167df7700 (LWP 1947)): #0 0x7fb19269f05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb19902486b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fb199024899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fb19269b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb192e9a04d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb0dbfff700 (LWP 2139)): #0 0x7fb192e91c1d in poll () at /lib64/libc.so.6 #1 0x7fb18f573e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb18f573f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb1937bbd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb193762d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb19358461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb197404282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fb19358932f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb19269b0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb192e9a04d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb199940800 (LWP 1924)): [KCrash Handler] #6 0x7fb192dea187 in raise () at /lib64/libc.so.6 #7 0x7fb192deb538 in abort () at /lib64/libc.so.6 #8 0x7fb1935777ce in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb197471f01 in () at /usr/lib64/libQt5Quick.so.5 #10 0x7fb197472e85 in () at /usr/lib64/libQt5Quick.so.5 #11
