Bug 397925 - Flicker and crash
Summary: Flicker and crash
Status: RESOLVED DUPLICATE of bug 397894
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.13.4
Platform: Manjaro Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-27 11:36 UTC by leimuraittinen
Modified: 2018-08-27 15:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leimuraittinen 2018-08-27 11:36:25 UTC
When opening Launch feedback section of the systemsettings, the window title will start to flicker. When entered, changing settings category crashes the app. Pressing the < button from top left corner will freeze everything from the window except the category menu. Running systemsettings5 from terminal gives:

QCoreApplication::arguments: Please instantiate the QApplication object first
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
KActivities: Database connection:  "kactivities_db_resources_139958011861056_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
org.kde.kcoreaddons: Error loading plugin "kcm_launchfeedback" "The shared library was not found." 
Plugin search paths are ("/usr/lib/qt/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
KActivitiesStats( 0x560e050bfbf0 ) ResultModelPrivate::onResultScoreUpdated  result added: "kcm:componentchooser.desktop" score: 34.3539 last: 1535369700 first: 1535301869
KActivitiesStats( 0x560e050bfbf0 ) ResultModelPrivate::onResultScoreUpdated  result added: "kcm:kcm_launchfeedback.desktop" score: 30.3866 last: 1535369701 first: 1535220838
Segmentation fault (core dumped).
Comment 1 Kai Uwe Broulik 2018-08-27 11:38:47 UTC
Can you please run it through gdb and get a backtrace of the crash, thanks.
Comment 2 leimuraittinen 2018-08-27 15:20:43 UTC
Starting program: /usr/bin/systemsettings5 systemsettings5
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
QCoreApplication::arguments: Please instantiate the QApplication object first
[New Thread 0x7fffec9a7700 (LWP 1822)]
[New Thread 0x7fffe5247700 (LWP 1823)]
[New Thread 0x7fffdde99700 (LWP 1824)]
[New Thread 0x7fffd5ef8700 (LWP 1826)]
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
[New Thread 0x7fffcf973700 (LWP 1828)]
KActivities: Database connection:  "kactivities_db_resources_140737205303360_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
org.kde.kcoreaddons: Error loading plugin "kcm_launchfeedback" "The shared library was not found." 
Plugin search paths are ("/usr/lib/qt/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
[New Thread 0x7fffcc99d700 (LWP 1830)]
KActivitiesStats( 0x555555fc3700 ) ResultModelPrivate::onResultScoreUpdated  result added: "kcm:componentchooser.desktop" score: 40.3539 last: 1535383123 first: 1535301869

Thread 1 "systemsettings5" received signal SIGSEGV, Segmentation fault.
0x00007ffff7bfebc0 in KQuickAddons::ConfigModule::needsSave() () from /usr/lib/libKF5QuickAddons.so.5

If this isnt what you wanted then please tell me how since I am very new linux user.
Comment 3 Kai Uwe Broulik 2018-08-27 15:26:25 UTC
Thanks for providing the the information!
Ideally you would want to provide the entire backtrace, not just the first line, but in this instance that was sufficient, I have seen a similar bug report in the same component. Marking as duplicate.

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