Bug 395702 - Plasmashell crashes with installing plasma-discover-flatpak-backend
Summary: Plasmashell crashes with installing plasma-discover-flatpak-backend
Status: RESOLVED NOT A BUG
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (other bugs)
Version First Reported In: 5.11.1
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-21 19:14 UTC by Lays Rodrigues
Modified: 2018-07-18 22:16 UTC (History)
1 user (show)

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


Attachments
Backtrace from gdb (12.42 KB, text/plain)
2018-06-22 15:29 UTC, Lays Rodrigues
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lays Rodrigues 2018-06-21 19:14:30 UTC
Environment:
KDE Neon 5.13
Plasma Version: 5.13.1
KDE Frameworks version: 5.47.0
Qt: 5.11.0

Install:
plasma-discover-flatpak-backend
Reboot: PlasmaShell dont start.

Try to start from konsole, gets the following output:

➜  ~ plasmashell 
kf5.karchive: bzDecompress returned -5
org.kde.plasmaquick: Applet preload policy set to 1
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.plasma.calculator/contents/ui/calculator.qml:261:5: QML Connections: Cannot assign to non-existent property "onPopupEvent"
file:///usr/share/plasma/plasmoids/org.kde.plasma.calculator/contents/ui/calculator.qml:48:31: Unable to assign [undefined] to QString
qml: Reading resources from configuration: [{"alias":"Disk","childSourceObjects":{"acpi/Thermal_Zone/0-acpitz/Temperature":{"temperature":0},"acpi/Thermal_Zone/1-x86_pkg_temp/Temperature":{"temperature":0},"lmsensors/acpitz-virtual-0/temp1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_0":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_2":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_3":{"temperature":0},"lmsensors/coretemp-isa-0000/Physical_id_0":{"temperature":0},"lmsensors/dell_smm-virtual-0/Ambient":{"temperature":0},"lmsensors/dell_smm-virtual-0/CPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/GPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/Processor_Fan":{"temperature":0},"lmsensors/dell_smm-virtual-0/SODIMM":{"temperature":0},"lmsensors/nouveau-pci-0100/temp1":{"temperature":0},"udisks/HGST_HTS725050A7E630_TF755AWHKDXP9M":{"temperature":0},"udisks/HL_DT_ST_DVD_2b_2f_RW_GU70N_M3AD72E2519":{"temperature":0},"udisks/Linux_File_Stor_Gadget_c493eedd":{"temperature":0}},"meltdownTemperature":90,"overrideLimitTemperatures":false,"sourceName":"udisks/HGST_HTS725050A7E630_TF755AWHKDXP9M","virtual":false,"warningTemperature":70},{"alias":"Core","childSourceObjects":{"acpi/Thermal_Zone/0-acpitz/Temperature":{"temperature":0},"acpi/Thermal_Zone/1-x86_pkg_temp/Temperature":{"temperature":0},"lmsensors/acpitz-virtual-0/temp1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_0":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_2":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_3":{"temperature":0},"lmsensors/coretemp-isa-0000/Physical_id_0":{"temperature":0},"lmsensors/dell_smm-virtual-0/Ambient":{"temperature":0},"lmsensors/dell_smm-virtual-0/CPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/GPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/Processor_Fan":{"temperature":0},"lmsensors/dell_smm-virtual-0/SODIMM":{"temperature":0},"lmsensors/nouveau-pci-0100/temp1":{"temperature":0},"udisks/HGST_HTS725050A7E630_TF755AWHKDXP9M":{"temperature":0},"udisks/HL_DT_ST_DVD_2b_2f_RW_GU70N_M3AD72E2519":{"temperature":0},"udisks/Linux_File_Stor_Gadget_c493eedd":{"temperature":0}},"meltdownTemperature":90,"overrideLimitTemperatures":false,"sourceName":"lmsensors/coretemp-isa-0000/Physical_id_0","virtual":false,"warningTemperature":70}]
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
qml: disabling redshift
qml: disabling redshift
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
qml: onLoaded
trying to show an empty dialog
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
file:///home/lays/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/TimerView.qml:31:13: QML ToolButton: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
file:///home/lays/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/TimerView.qml:87:13: QML ColumnLayout: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
trying to show an empty dialog
qml: process exited with code 0. sourceName: killall redshift; redshift -x, data: Usando o método `randr'.

qml: clearing connected sources
qml: enabling redshift with command: redshift -l -22.8864:-43.2037 -t 6500:4000 -b 1:1 -g 1:1:1
org.kde.plasmaquick: New Applet  "Calculadora" with a weight of 0
org.kde.plasmaquick: New Applet  "Redshift Control" with a weight of 0
KActivities: Database connection:  "kactivities_db_resources_140270623709504_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Closing SQL connection:  "kactivities_db_resources_140270623709504_readonly"
KActivities: Database connection:  "kactivities_db_resources_140270623709504_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
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
trying to show an empty dialog
qml: fetchWeatherForecast
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 6957
KCrash: Arguments: /usr/bin/plasmashell 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
**
OSTree:ERROR:./libglnx/glnx-local-alloc.h:73:glnx_close_fd: assertion failed: (errno != EBADF)
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
[1]    6957 abort (core dumped)  plasmashell


Try Again:
➜  ~ plasmashell
kf5.karchive: bzDecompress returned -5
org.kde.plasmaquick: Applet preload policy set to 1
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.plasma.calculator/contents/ui/calculator.qml:261:5: QML Connections: Cannot assign to non-existent property "onPopupEvent"
file:///usr/share/plasma/plasmoids/org.kde.plasma.calculator/contents/ui/calculator.qml:48:31: Unable to assign [undefined] to QString
qml: Reading resources from configuration: [{"alias":"Disk","childSourceObjects":{"acpi/Thermal_Zone/0-acpitz/Temperature":{"temperature":0},"acpi/Thermal_Zone/1-x86_pkg_temp/Temperature":{"temperature":0},"lmsensors/acpitz-virtual-0/temp1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_0":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_2":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_3":{"temperature":0},"lmsensors/coretemp-isa-0000/Physical_id_0":{"temperature":0},"lmsensors/dell_smm-virtual-0/Ambient":{"temperature":0},"lmsensors/dell_smm-virtual-0/CPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/GPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/Processor_Fan":{"temperature":0},"lmsensors/dell_smm-virtual-0/SODIMM":{"temperature":0},"lmsensors/nouveau-pci-0100/temp1":{"temperature":0},"udisks/HGST_HTS725050A7E630_TF755AWHKDXP9M":{"temperature":0},"udisks/HL_DT_ST_DVD_2b_2f_RW_GU70N_M3AD72E2519":{"temperature":0},"udisks/Linux_File_Stor_Gadget_c493eedd":{"temperature":0}},"meltdownTemperature":90,"overrideLimitTemperatures":false,"sourceName":"udisks/HGST_HTS725050A7E630_TF755AWHKDXP9M","virtual":false,"warningTemperature":70},{"alias":"Core","childSourceObjects":{"acpi/Thermal_Zone/0-acpitz/Temperature":{"temperature":0},"acpi/Thermal_Zone/1-x86_pkg_temp/Temperature":{"temperature":0},"lmsensors/acpitz-virtual-0/temp1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_0":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_1":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_2":{"temperature":0},"lmsensors/coretemp-isa-0000/Core_3":{"temperature":0},"lmsensors/coretemp-isa-0000/Physical_id_0":{"temperature":0},"lmsensors/dell_smm-virtual-0/Ambient":{"temperature":0},"lmsensors/dell_smm-virtual-0/CPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/GPU":{"temperature":0},"lmsensors/dell_smm-virtual-0/Processor_Fan":{"temperature":0},"lmsensors/dell_smm-virtual-0/SODIMM":{"temperature":0},"lmsensors/nouveau-pci-0100/temp1":{"temperature":0},"udisks/HGST_HTS725050A7E630_TF755AWHKDXP9M":{"temperature":0},"udisks/HL_DT_ST_DVD_2b_2f_RW_GU70N_M3AD72E2519":{"temperature":0},"udisks/Linux_File_Stor_Gadget_c493eedd":{"temperature":0}},"meltdownTemperature":90,"overrideLimitTemperatures":false,"sourceName":"lmsensors/coretemp-isa-0000/Physical_id_0","virtual":false,"warningTemperature":70}]
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
qml: disabling redshift
qml: disabling redshift
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
qml: onLoaded
trying to show an empty dialog
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
file:///home/lays/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/TimerView.qml:31:13: QML ToolButton: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
file:///home/lays/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/TimerView.qml:87:13: QML ColumnLayout: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property "preferredWidth"
trying to show an empty dialog
qml: process exited with code 0. sourceName: killall redshift; redshift -x, data: Usando o método `randr'.

qml: clearing connected sources
qml: enabling redshift with command: redshift -l -22.8864:-43.2037 -t 6500:4000 -b 1:1 -g 1:1:1
org.kde.plasmaquick: New Applet  "Calculadora" with a weight of 0
org.kde.plasmaquick: New Applet  "Redshift Control" with a weight of 0
KActivities: Database connection:  "kactivities_db_resources_140475091601728_readonly" 
    query_only:          QVariant(qlonglong, 1) 
    journal_mode:        QVariant(QString, "wal") 
    wal_autocheckpoint:  QVariant(qlonglong, 100) 
    synchronous:         QVariant(qlonglong, 0)
Closing SQL connection:  "kactivities_db_resources_140475091601728_readonly"
KActivities: Database connection:  "kactivities_db_resources_140475091601728_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
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
trying to show an empty dialog
qml: fetchWeatherForecast
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 7081
KCrash: Arguments: /usr/bin/plasmashell 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
[1]  + 7081 suspended (signal)  plasmashell
Comment 1 Aleix Pol 2018-06-22 11:16:53 UTC
Please provide a backtrace or a way to reproduce.

If it happens every time, execute with gdb to get the backtrace.
Comment 2 Lays Rodrigues 2018-06-22 15:29:46 UTC
Created attachment 113510 [details]
Backtrace from gdb
Comment 3 Aleix Pol 2018-06-22 17:02:39 UTC
Can you please include debug symbols to the backtrace? At least discover ones. (You can find them with "apt search discover dbgsym")

There's not much I can do with this backtrace.
Comment 4 Christoph Feck 2018-07-18 16:30:54 UTC
If you can provide the information requested in comment #3, please add it.
Comment 5 Lays Rodrigues 2018-07-18 17:06:36 UTC
Apparently was a package problem on Neon. Because the Discover version that I had installed wasn't up to date that Neon delivers. So we can close this.
Sorry that I didn't update here.
Also, I wasn't able at the time to get any new backtrace using gdb. =/
Comment 6 Aleix Pol 2018-07-18 22:16:43 UTC
Don't worry, thanks for taking your time! :)