[plasmashell] [Bug 482548] Pinned Icons change places when app launched, some icons disappear
https://bugs.kde.org/show_bug.cgi?id=482548 --- Comment #1 from Armando --- Created attachment 166481 --> https://bugs.kde.org/attachment.cgi?id=166481=edit Screenshot of icon duplicate in this case, I launched an app and two Google Calendar icons are visible as a result. Sometimes, if one of the icons is clicked, it launches a different app whose icon is missing (as if the connection between what is visible and what is being launched has been broken) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482548] New: Pinned Icons change places when app launched, some icons disappear
https://bugs.kde.org/show_bug.cgi?id=482548 Bug ID: 482548 Summary: Pinned Icons change places when app launched, some icons disappear Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: armandogarci...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY (Not a crash) Since KDE 6 update, icons-only taskbar behavior has changed. Pinned icons move around the list if launched, sometimes creating a duplicate icon for themselves. I have seen duplicate instances of an app running somehow and have not been able to reproduce that reliably. Sometimes, if something is launched another icon might disappear from the taskbar. More specifically: Most of my pinned icons are Google Chrome web apps. (examples are GMail, Google Calendar, Drive, a few other web apps for SaaS tools I use.) The pinned icon for Google Chrome most often disappears when launching one of these web apps. However, there are other things happening that are hard for me to track and observe as well. I unpinned and repinned these icons, I removed the applet and replaced it adding all the icons again, I've taken updates and restarted, I've looked at settings to see if any are relevant (doesn't appear so). Discover indicates I'm totally up to date. STEPS TO REPRODUCE (I had icons on it already, but it's the same if they are removed and added back) 1. Launch an application by single clicking an icon on task manager OBSERVED RESULT Observe strange behaviors: disappearing icons, icons jumping around, duplicate application instances etc. EXPECTED RESULT application launch with no other results SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Very similar to previously-resolved, year old bug 385594 launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around: https://bugs.kde.org/show_bug.cgi?id=385594 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 Armando S. Araujo changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 468712] Setting Kirigami.FormData.buddyFor to a null item crashes the calling app
https://bugs.kde.org/show_bug.cgi?id=468712 --- Comment #10 from Armando S. Araujo --- The issue has been resolved with this week's update. Updated system data: Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-41-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU W3520 @ 2.67GHz Memory: 7.7 GiB of RAM Graphics Processor: GeForce GT 610/PCIe/SSE2 Manufacturer: Apple Inc. Product Name: MacPro4,1 System Version: 0.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468712] Configurações do sistema fecha iniesperado
https://bugs.kde.org/show_bug.cgi?id=468712
--- Comment #2 from Armando S. Araujo ---
Created attachment 158395
--> https://bugs.kde.org/attachment.cgi?id=158395=edit
New crash information added by DrKonqi
systemsettings (5.27.4) using Qt 5.15.9
armando@florest-1:/home$ systemsettings
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
QML MouseArea: Binding loop detected for property "width"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9:
QML MouseArea: Binding loop detected for property "width"
kf.activitiesstats: [Error at ResultSetPrivate::initQuery]: QSqlError("11",
"Não foi possível obter a linha", "database disk image is malformed")
kf.activitiesstats: [Error at ResultSetPrivate::initQuery]: QSqlError("11",
"Não foi possível obter a linha", "database disk image is malformed")
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/share/kpackage/kcms/kcm_landingpage/contents/ui/main.qml:197:13:
Unable to assign [undefined] to
QQuickItem*
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings path = /usr/bin pid = 36617
KCrash: Arguments: /usr/bin/systemsettings
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
[1]+ Parado systemsettings
armando@florest-1:/home$ Unable to find file for pid 36617 expected at
"kcrash-metadata/36617.ini"
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
-- Backtrace (Reduced):
#7 0x7f37c0fdf2f7 in QAccessibleQuickItem::role() const () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#11 0x7f37c0e61dbb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7f37c0e69686 in QQuickItem::setParentItem(QQuickItem*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f37c0e69bd1 in QQuickItem::~QQuickItem() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
[...]
#15 0x7f37c1ed04ba in KDeclarative::QmlObject::~QmlObject() () from
/lib/x86_64-linux-gnu/libKF5Declarative.so.5
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 468712] Configurações do sistema fecha iniesperado
https://bugs.kde.org/show_bug.cgi?id=468712 Armando S. Araujo changed: What|Removed |Added CC||aee_eletron...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468712] New: Configurações do sistema fecha iniesperado
https://bugs.kde.org/show_bug.cgi?id=468712 Bug ID: 468712 Summary: Configurações do sistema fecha iniesperado Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aee_eletron...@hotmail.com Target Milestone: --- Application: systemsettings (5.27.4) (Compiled from sources) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 5.19.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: A ja nela abre, mas nenhuma configuração pode ser clicada. Ao clicar numa opção a aplicação fecha completamente. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Configurações do sistema (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f9b4665377b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f9b466537ed in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f9b467df2f7 in QAccessibleQuickItem::role() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f9b4257387a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f9b425765f8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7f9b42577e22 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7f9b46661dbb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f9b46669686 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f9b46669bd1 in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f9b30172609 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #15 0x7f9b471a14ba in KDeclarative::QmlObject::~QmlObject() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #16 0x7f9b471a222d in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #17 0x7f9b471b69b2 in KQuickAddons::ConfigModule::~ConfigModule() () from /lib/x86_64-linux-gnu/libKF5QuickAddons.so.5 #18 0x7f9b300a0b67 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_landingpage.so #19 0x7f9b48fc85c7 in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #20 0x7f9b48fc85ed in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #21 0x7f9b48fcd998 in KCModuleProxy::deleteClient() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #22 0x7f9b48fce353 in KCModuleProxy::~KCModuleProxy() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #23 0x7f9b48fce52d in KCModuleProxy::~KCModuleProxy() () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #24 0x7f9b484e722e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f9b491ab056 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f9b491ab3ad in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f9b484e722e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f9b491ab056 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f9b4931267d in QScrollArea::~QScrollArea() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f9b49a32968 in KPageWidgetItem::~KPageWidgetItem() () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #31 0x7f9b49a34519 in ?? () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #32 0x7f9b49a37a61 in KPageWidgetModel::removePage(KPageWidgetItem*) () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #33 0x7f9b49f06995 in ModuleView::closeModules() () from /lib/x86_64-linux-gnu/libsystemsettingsview.so.3 #34 0x7f9b38d86ed6 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #35 0x7f9b38d89c51 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #36 0x7f9b38d8a593 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #37 0x7f9b460d0755 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #38 0x7f9b45faaa16 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #39 0x7f9b45fac8da in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #40 0x7f9b45fc9f23 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #41 0x7f9b45fccc2f in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #42 0x7f9b45f5eb0e in QV4::Function::call(QV4::Value const*, QV4::Value
[neon] [Bug 451315] Recent updates to libwayland-server0 et al break i386 support.
https://bugs.kde.org/show_bug.cgi?id=451315 --- Comment #13 from Armando Ota --- Updated latest wayland libs available by discover. Can confirm bug is gone. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 451328] New: Lock screen broken showiing black screen with details how to unlock from terminal
https://bugs.kde.org/show_bug.cgi?id=451328 Bug ID: 451328 Summary: Lock screen broken showiing black screen with details how to unlock from terminal Product: kscreenlocker Version: 5.24.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: armando@dropchop.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Whenever I lock screen or screen is auto locked, I get black screen with text "The lock screen is broken and unlocking is not possible anymore ... " STEPS TO REPRODUCE 1. Login to KDE 2. press win + L to lock screen 3. black screen with text describing how to unlock from terminal using lockctl unlock-session OBSERVED RESULT black screen with details how to unlock through terminal (ALT+CTRL+F2) EXPECTED RESULT Unlock screen SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440661] Reverting global scale back to 100% in settings does not change DPIs back to normal
https://bugs.kde.org/show_bug.cgi?id=440661 --- Comment #2 from Armando Ota --- I can confirm. Removing [XDisplay] ServerArguments=-dpi 96 from sddm.conf and system settings -> login screen -> sync settings did help to reset SDDM layout. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440661] New: Reverting global scale back to 100% in settings does not change DPIs back to normal
https://bugs.kde.org/show_bug.cgi?id=440661 Bug ID: 440661 Summary: Reverting global scale back to 100% in settings does not change DPIs back to normal Product: plasmashell Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: armando@dropchop.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I changed global scale in display configuration to 125%. Rebooted. After a test I changed it back to 100%. Rebooted. Then the problems occured. SDDM login screen and KDE apps did not change scale back to 100%. After googling I found out that I had to froce fonts DPI size to 96 and add following lines to /etc/sddm.conf [XDisplay] ServerArguments=-dpi 96 to make things as they were. STEPS TO REPRODUCE 1. Display settings > Change global scale to 125% 2. Press APPLY 3. REBOOT 4. Login 5. Display settings > Change global scale to 100% 6. Press APPLY 7. REBOOT OBSERVED RESULT everything is still scaled up! EXPECTED RESULT default as before 125% global scale shange SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-25-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz Memory: 31,3 GiB of RAM Graphics Processor: GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFO: I've got 3 monitors setup with 2 of them 2560x1600 resolution and 1 monitor with 2560x1440 resolution -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 --- Comment #42 from Armando Ota --- Another update and problem is gone. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz Memory: 31,3 GiB of RAM Graphics Processor: GeForce GTX 1060 3GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438670] Discover notifies about updates whereas there are none
https://bugs.kde.org/show_bug.cgi?id=438670 --- Comment #40 from Armando Ota --- Problem is back ... just updated 5.22.1 do 5.22.2 and Discover shows empty updates again. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-59-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1080 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433960] Cannot detach Chrome tab when draging to new window
https://bugs.kde.org/show_bug.cgi?id=433960 --- Comment #4 from Armando Ota --- thank you for explanation ... you might as well close this issue then -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433960] Cannot detach Chrome tab when draging to new window
https://bugs.kde.org/show_bug.cgi?id=433960 --- Comment #2 from Armando Ota --- who handles drag event then ? Google chrome ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433960] New: Cannot detach Chrome tab when draging to new window
https://bugs.kde.org/show_bug.cgi?id=433960 Bug ID: 433960 Summary: Cannot detach Chrome tab when draging to new window Product: kwin Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: armando@dropchop.com Target Milestone: --- Created attachment 136372 --> https://bugs.kde.org/attachment.cgi?id=136372=edit video of draging tab into new window SUMMARY I drag chrome tab out of current chrome window tab row to create a new chrome window. After I realease my mouse button, the release does not happen and as I move mouse around my newly created window with chrome tab follows my mouse. If my move my mouse to original chrome window tab row, it attaches it back. If i press space key when outside of the original chrome window, the new window is released and I get new window with my dragged chrome tab in it. STEPS TO REPRODUCE 1. Open Chrome 2. Open 3 tabs in chrome 3. Drag one tab out of current chrome tab row to create new chrome window with dragged tab OBSERVED RESULT after releasing mouse button (to end drag) window is not released and follows mouse cursor. EXPECTED RESULT Drag should stop and new window with dragged chrome tab is created. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1080 Ti/PCIe/SSE2 ADDITIONAL INFORMATION attacking video -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #43 from Armando Ota --- I can cofirm .. fixed it for me -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #36 from Armando Ota --- tried it after yesterdays update ... no joy ;) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 430388] Custom Shortcuts cannot record key presses
https://bugs.kde.org/show_bug.cgi?id=430388 --- Comment #32 from Armando Ota --- when can we expect the fix to be released? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 --- Comment #19 from Armando --- (In reply to Antonio Rojas from comment #18) > (In reply to Armando from comment #13) > > > I can't tell what the fix is from this thread. Could someone help reiterate > > what needs to be done here? > > You'll have to ask your distribution to backport the fix Thank you, Antonio. But my distribution is KDE Neon, which I assume has already made this update available, and all of my software is up to date on that distro. Still have the problem, crashes on start. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 --- Comment #14 from Armando --- More information: when trying to run Dolphin from terminal, I get this: :~$ dolphin KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = dolphin path = /usr/bin pid = 6055 KCrash: Arguments: /usr/bin/dolphin KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... [1]+ Stopped dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 Armando changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 Armando changed: What|Removed |Added CC||armandogarci...@gmail.com --- Comment #13 from Armando --- Hello, Drkonqi Crash Handler didn't allow automatically submitting a bug report on this because it suggested that my crash was the same as this bug report. Dolphin crashes on launch. Every time. Under any circumstances. Two recent changes that may be related: -I have been downloading and experimenting with global themes. -I recently installed Nautilus, Gnome Command Center, and Gnome Online Accounts in order to integrate access to my Google Drive (KIO-Google is completely broken) I can't tell what the fix is from this thread. Could someone help reiterate what needs to be done here? Backtrace of the crash I experienced: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 3543] [New LWP 3544] [New LWP 3545] [New LWP 3546] [New LWP 3547] [New LWP 3548] [New LWP 3549] [New LWP 3550] [New LWP 3551] [New LWP 3552] [New LWP 3553] [New LWP 3554] [New LWP 3555] [New LWP 3556] [New LWP 3557] [New LWP 3558] [New LWP 3559] [New LWP 3560] [New LWP 3561] [New LWP 3562] [New LWP 3567] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc1d242baff in __GI___poll (fds=0x7ffedb58a5e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fc1cb4de8c0 (LWP 3541))] Thread 22 (Thread 0x7fc16d7fa700 (LWP 3567)): #0 __GI___libc_read (nbytes=16, buf=0x7fc16d7f9ad0, fd=24) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=24, buf=0x7fc16d7f9ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fc1cdf2a89f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc1cdee1cfe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc1cdee2152 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc1cdee22e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc1d0172fbb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc1d01171ab in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc1cff31a12 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc1cff32bac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc1ce8b1609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fc1d2438293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7fc16700 (LWP 3562)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55d34dbea5f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d34dbea5a8, cond=0x55d34dbea5d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d34dbea5d0, mutex=0x55d34dbea5a8) at pthread_cond_wait.c:638 #3 0x7fc1c258062b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc1c258023b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc1ce8b1609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc1d2438293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fc18cff9700 (LWP 3561)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55d34dbea5f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d34dbea5a8, cond=0x55d34dbea5d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d34dbea5d0, mutex=0x55d34dbea5a8) at pthread_cond_wait.c:638 #3 0x7fc1c258062b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc1c258023b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc1ce8b1609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc1d2438293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fc18d7fa700 (LWP 3560)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55d34dbea5f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d34dbea5a8, cond=0x55d34dbea5d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d34dbea5d0, mutex=0x55d34dbea5a8) at pthread_cond_wait.c:638 #3 0x7fc1c258062b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc1c258023b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc1ce8b1609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc1d2438293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fc18dffb700 (LWP 3559)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55
[systemsettings] [Bug 430495] Custom shortcuts: cannot set shortcut
https://bugs.kde.org/show_bug.cgi?id=430495 --- Comment #2 from Armando Ota --- Search did not show the linked bug report. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430495] New: Custom shortcuts: cannot set shortcut
https://bugs.kde.org/show_bug.cgi?id=430495 Bug ID: 430495 Summary: Custom shortcuts: cannot set shortcut Product: systemsettings Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: armando@dropchop.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 134136 --> https://bugs.kde.org/attachment.cgi?id=134136=edit Screenshot of the problem SUMMARY I cannot set shortcut for K-Menu Entry in Custom Shortcuts -> KMenuEdit -> Trigger Pressing the "Shortcut button" does nothing. STEPS TO REPRODUCE 1. Open Kmenu 2. type shortcuts 3. select Custom shortcuts 4. Add new K-Menu Entry 5. Switch to tab Trigger 6. press "None" button to set trigger. OBSERVED RESULT Nothing happens and shortcut cannot be set. EXPECTED RESULT Open shortcut window to set shortcut SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: KDE Neon 5.20 (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 427683] Discover notification icon allways showing updates
https://bugs.kde.org/show_bug.cgi?id=427683 Armando Ota changed: What|Removed |Added CC||armando@dropchop.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 427683] New: Discover notification icon allways showing updates
https://bugs.kde.org/show_bug.cgi?id=427683 Bug ID: 427683 Summary: Discover notification icon allways showing updates Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: armando@dropchop.com CC: aleix...@kde.org Target Milestone: --- Created attachment 132342 --> https://bugs.kde.org/attachment.cgi?id=132342=edit notification icon and discover window SUMMARY Discover notification icon always showing that updates are available, but discover does not show any new packages to update. STEPS TO REPRODUCE 1. Wait for new packages. 2. Update packages. 3. Check notification icon OBSERVED RESULT Icon still present, even though packages were updated and Discover does not show any packages for update. EXPECTED RESULT Icon should only become visible if any packages are to be updated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 Armando Ota changed: What|Removed |Added CC||armando@dropchop.com --- Comment #151 from Armando Ota --- Problem still present ... some applications like System settings, google chrome, viber have meesed up display. System settings are missing the whole left list of categories. Even application restart does not help. Chrome does not display pages normaly (blank white screen or parts of screen) and it has to be restarted to display them again Viber has images messed up. KDE Neon 5.19 KDE Plasma version: 5.19.5 KDE Frameworks: 5.73.0 QT version 5.14.2 KErnel 5.4.0-47-generic OS type: 64 bit GPU: Geforce GTX 1080 Ti Added [QtQuickRendererSettings] GraphicsResetNotifications=true to kdeglobals Regards Armando -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408247] [Dual monitor, powersave] taskbar showing windows from the wrong screen
https://bugs.kde.org/show_bug.cgi?id=408247 Armando Ota changed: What|Removed |Added CC||armando@dropchop.com --- Comment #5 from Armando Ota --- same problem here ... computer with 2 or 3 monitors. After wakeup ot lock screen all taskbars show only application windows from one screen my taskbar settings: Group : Do not group Sort: manualy On middle-click: new instance Mouse wheel: Cycle through tasks Show only [X] From current screen [X] From current desktop [X] From current activity [ ] That are minimized -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 404420] Immediate Crash upon Bootup
https://bugs.kde.org/show_bug.cgi?id=404420 --- Comment #2 from Armando --- (In reply to Nate Graham from comment #1) > Crashing in KFileMetaData::TagLibExtractor::extract(). > > Do you by any chance have any .spx files and/or can you pinpoint the file > that causes the crash by using `balooctl monitor`? Thank you for responding. I am unfamiliar with Baloo or its role on my system, but I do have some .spx files on my system (packaged into .gdb files). These files are associated with ESRI ArcMaps. Running 'balooctl monitor' indicates that it has indexed one of the .spx files: :~$ balooctl monitor Press ctrl+c to stop monitoring File indexer is running Indexing file content Indexing: /home/[folder]/Documents/Records/Academic/Coursework/[folder]/Final/Shapefiles 2/[private]/Census_Income_Tracts.gdb/a0004.spx Thank you, I'll await any further questions or instructions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404420] New: Immediate Crash upon Bootup
https://bugs.kde.org/show_bug.cgi?id=404420 Bug ID: 404420 Summary: Immediate Crash upon Bootup Product: frameworks-baloo Version: 5.55.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: armandogarci...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.55.0) Qt Version: 5.12.0 Frameworks Version: 5.55.0 Operating System: Linux 4.15.0-45-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: this application crashed immediately upon boot-up. As soon as I logged into my user account with sddm and the Plasma 5 desktop environment loaded, this crash message popped up. Before rebooting, I had created a script and added it to my autostart list of scripts to run at boot-up. It is the first and only attempt I have made at this, and it is a simple script intended to call up conky at boot up. I'm including this bit of info because it's been the only change between this and other boot ups. Conky did not start. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd983150c80 (LWP 1527))] Thread 3 (Thread 0x7fd95b6a0700 (LWP 1539)): #0 0x7fd97fc57bf9 in __GI___poll (fds=0x7fd95401a9e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd97c324539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd97c32464c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd98059a15b in QEventDispatcherGlib::processEvents (this=0x7fd954000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fd98053b64a in QEventLoop::exec (this=this@entry=0x7fd95b69fd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fd98036341a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fd981f2f015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fd980364bc2 in QThreadPrivate::start (arg=0x7fd9821a6d80) at thread/qthread_unix.cpp:361 #8 0x7fd97e85e6db in start_thread (arg=0x7fd95b6a0700) at pthread_create.c:463 #9 0x7fd97fc6488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd974f0a700 (LWP 1532)): #0 0x7fd97fc57bf9 in __GI___poll (fds=0x7fd974f09cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd97beb3747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fd97beb536a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fd977accd4a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fd980364bc2 in QThreadPrivate::start (arg=0x55a56664d3c0) at thread/qthread_unix.cpp:361 #5 0x7fd97e85e6db in start_thread (arg=0x7fd974f0a700) at pthread_create.c:463 #6 0x7fd97fc6488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd983150c80 (LWP 1527)): [KCrash Handler] #6 0x7fd95bab90ab in KFileMetaData::TagLibExtractor::extract (this=, result=0x77fe25c0) at ./src/extractors/taglibextractor.cpp:857 #7 0x55a5645ff23b in Baloo::App::index (this=this@entry=0x77fe2d60, tr=0x55a5666f3430, url=..., id=id@entry=101900504279287825) at ./src/file/extractor/app.cpp:191 #8 0x55a5645ffb7e in Baloo::App::processNextFile (this=0x77fe2d60) at ./src/file/extractor/app.cpp:111 #9 0x7fd980579d04 in QtPrivate::QSlotObjectBase::call (a=0x77fe2710, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 QSingleShotTimer::timerEvent (this=0x7fd970006c20) at kernel/qtimer.cpp:318 #11 0x7fd98056d94b in QObject::event (this=0x7fd970006c20, e=) at kernel/qobject.cpp:1271 #12 0x7fd98133383c in QApplicationPrivate::notify_helper (this=this@entry=0x55a56662b0f0, receiver=receiver@entry=0x7fd970006c20, e=e@entry=0x77fe2a50) at kernel/qapplication.cpp:3752 #13 0x7fd98133add0 in QApplication::notify (this=0x77fe2d30, receiver=0x7fd970006c20, e=0x77fe2a50) at kernel/qapplication.cpp:3499 #14 0x7fd98053d328 in QCoreApplication::notifyInternal2 (receiver=0x7fd970006c20, event=0x77fe2a50) at kernel/qcoreapplication.cpp:1061 #15 0x7fd9805995a9 in QTimerInfoList::activateTimers (this=0x55a56667aac0) at kernel/qtimerinfo_unix.cpp:643 #16 0x7fd980599da9 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #17 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:229 #18 0x7fd97c324387 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fd97c3245c0 in ?? () from
[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue
https://bugs.kde.org/show_bug.cgi?id=402328 --- Comment #52 from Armando --- Created attachment 117959 --> https://bugs.kde.org/attachment.cgi?id=117959=edit New crash information added by DrKonqi plasma-discover (5.14.5) using Qt 5.12.0 - What I was doing when the application crashed: Started up KDE Neon, proceeded to open Discover through menu. Crash. Attempted opening via terminal. Crash. Crashes consistently every single time. As another user reported in a comment, I was able to avoid a crash by removing the file fwupd-backend.so. Replacing the file to the /usr/lib/x86_64-linux-gnu/qt5/plugins/discover directory reproduced consistent crashes at every effort to open Discover. As some others have expressed in comments, after running fwupdmgr refresh && fwupdmgr update, Discover does not crash. -- Backtrace (Reduced): #6 0x7fadc73b1d62 in AbstractResource::reportNewState (this=0x564d4e978170) at ./libdiscover/resources/AbstractResource.cpp:143 #7 0x7fadc41faf3f in QtPrivate::QSlotObjectBase::call (a=0x7ffeb8717940, r=0x564d4e978170, this=0x564d4e978990) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 [...] #10 0x7fadc73c2cf3 in AbstractResource::stateChanged (this=this@entry=0x564d4e978170) at ./obj-x86_64-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResource.cpp:430 #11 0x7fad7d5a1a2d in FwupdResource::setState (this=this@entry=0x564d4e978170, state=state@entry=AbstractResource::Upgradeable) at ./libdiscover/backends/FwupdBackend/FwupdResource.cpp:141 #12 0x7fad7d5a6cb5 in FwupdBackend::createApp (this=this@entry=0x564d4d09f430, device=device@entry=0x7fad74002d90) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:235 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue
https://bugs.kde.org/show_bug.cgi?id=402328 Armando changed: What|Removed |Added CC||armandogarci...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373873] New: KDE plasma application style
https://bugs.kde.org/show_bug.cgi?id=373873 Bug ID: 373873 Summary: KDE plasma application style Product: systemsettings Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zuk...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I lunc the application and after changing some settings and close it, it show the error. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb9c82661c0 (LWP 2093))] Thread 6 (Thread 0x7fb990fa9700 (LWP 2106)): #0 0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6 #1 0x7fb9be34a786 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fb9be34a89c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fb9c488a2db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb9c4833d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fb9c3f707df in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fb992fe6700 (LWP 2102)): #0 0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6 #1 0x7fb9be34a786 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fb9be34a89c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fb9c488a2db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb9c4833d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fb9c3f707df in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb26700 (LWP 2100)): #0 0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6 #1 0x7fb9be34a786 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fb9be34a89c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fb9c488a2db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb9c4833d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fb9c29a9e75 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fb9c3f707df in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb9ac1c9700 (LWP 2096)): #0 0x7fb9be38fdd4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7fb9be34a8a6 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #2 0x7fb9c488a2db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #3 0x7fb9c4833d3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fb9c4656063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #5 0x7fb9c519fde5 in ?? () from /usr/lib/libQt5DBus.so.5 #6 0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7fb9c3f707df in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb9b4acd700 (LWP 2095)): #0 0x7fb9c3f6748d in poll () from /usr/lib/libc.so.6 #1 0x7fb9c08b88e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fb9c08ba679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fb9b6c1f789 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fb9c465acf8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fb9c0035454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fb9c3f707df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fb9c82661c0 (LWP 2093)): [KCrash Handler] #6 0x7fb9c287acc0 in QV4::PersistentValueStorage::freePage(void*) () from /usr/lib/libQt5Qml.so.5 #7 0x7fb9c287b3a2 in QV4::WeakValue::free() () from /usr/lib/libQt5Qml.so.5 #8 0x7fb9c28ebe42 in QV4::QObjectWrapper::destroyObject(bool) () from /usr/lib/libQt5Qml.so.5 #9 0x7fb9c278263f in QV4::MemoryManager::sweep(bool) () from /usr/lib/libQt5Qml.so.5 #10 0x7fb9c2783a4c in QV4::MemoryManager::~MemoryManager() () from
