Bug 420162

Summary: System Settings crashes when viewing Application Styles
Product: [Applications] systemsettings Reporter: kde
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: crash CC: groot, kde
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.18.4   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description kde 2020-04-16 14:49:53 UTC
Application: systemsettings5 (5.18.4)
 (Compiled from sources)
Qt Version: 5.14.2
Frameworks Version: 5.69.0
Operating System: FreeBSD 12.1-RELEASE amd64
Windowing system: X11
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
- What I was doing when the application crashed:

I looked at "Application Style" in System Settings. I scrolled down past "MS Windows 9x" and "Oxygen", but not too far: three mouse wheel clicks will do it. I can see the top of the styles that would be showed next (although I can't name them, since the names don't become visible until one scrolls further). Then, System Settings crashes.

- Unusual behavior I noticed:

System Settings should not crash when viewing Application Styles.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Abort trap
(lldb) process attach --pid 23068
(lldb) settings set term-width 200
(lldb) thread info
(lldb) bt all
(lldb) detach

Possible duplicates by query: bug 420146, bug 420134, bug 420093, bug 420063, bug 420024.

Reported using DrKonqi
Comment 1 Kai Uwe Broulik 2020-04-16 14:52:04 UTC
It would be useful if you included the output of those commands, especially the backtrace.
Comment 2 kde 2020-04-16 14:57:32 UTC
(In reply to Kai Uwe Broulik from comment #1)
> It would be useful if you included the output of those commands, especially
> the backtrace.

I've run the command from the terminal to see if we get any better error logging.

$ systemsettings5
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
Cannot mix incompatible Qt library (version 0x50d02) with this library (version 0x50e02)
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings5 path = /usr/local/bin pid = 79708
KCrash: Arguments: /usr/local/bin/systemsettings5 
KCrash: Attempting to start /usr/local/lib/libexec/drkonqi from kdeinit
sock_file=/var/run/user/1001/kdeinit5__0

$


The backtrace included in the auto-generated report is probably not what you are after. I'll go read up how to make a decent backtrace and come back.

Thanks for the help!
Comment 3 kde 2020-04-16 14:58:53 UTC
Ah, looks like I have some inconsistency in my built packages, based on the console output so far.

"Cannot mix incompatible Qt library (version 0x50d02) with this library (version 0x50e02)"

I'll rebuild all the Qt stuff to get it on the same version and see if this goes away.
Comment 4 groot 2020-04-16 15:02:56 UTC
Qt 5.14 landed in ports this week, so it's possible you have mixed ports (if you didn't upgrade all the packages). I can't reproduce with an all-5.14.2 system, although I don't have more than the four default themes installed -- which makes me think that perhaps one of your themes is built against an older Qt?
Comment 5 kde 2020-04-16 15:24:50 UTC
(In reply to groot from comment #4)
> Qt 5.14 landed in ports this week, so it's possible you have mixed ports (if
> you didn't upgrade all the packages). I can't reproduce with an all-5.14.2
> system, although I don't have more than the four default themes installed --
> which makes me think that perhaps one of your themes is built against an
> older Qt?

Yes, that makes sense. If you can't reproduce with an all-5.14.2 system, this is just a screw-up on my side with using ports.

Let me know if we need any further investigation into this. Otherwise, I'm fine with this being closed as PEBKAC.

Thanks again for the quick response!
Comment 6 kde 2020-04-25 09:19:57 UTC
Rebuilt all packages from scratch. No issues anymore.