[kdenlive] [Bug 415731] New: Feature request: drag and drop videos from the file browser to timeline directly
https://bugs.kde.org/show_bug.cgi?id=415731 Bug ID: 415731 Summary: Feature request: drag and drop videos from the file browser to timeline directly Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: of.se...@hotmail.com Target Milestone: --- I did not know where to submit a request, so I thought I would do it here. I wanted to be able to insert videos directly from the file browser into the timeline. As this would speed up the editing process. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415730] New: Calendar won't sync with Fruux
https://bugs.kde.org/show_bug.cgi?id=415730 Bug ID: 415730 Summary: Calendar won't sync with Fruux Product: kontact Version: 5.13.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: de...@stojicevic.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Made Calendar 2. New Appointments and changed old ones in the GUI 3. OBSERVED RESULT No update on the server, no error message EXPECTED RESULT Update on the server. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, freshly updated, 5.4.6-arch3-1 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415729] New: Calendar won't sync with Fruux
https://bugs.kde.org/show_bug.cgi?id=415729 Bug ID: 415729 Summary: Calendar won't sync with Fruux Product: kontact Version: 5.13.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: de...@stojicevic.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Made Calendar 2. New Appointments and changed old ones in the GUI 3. OBSERVED RESULT No update on the server, no error message EXPECTED RESULT Update on the server. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, freshly updated, 5.4.6-arch3-1 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415424] sms send, historic refresh fails
https://bugs.kde.org/show_bug.cgi?id=415424 laurela...@gmail.com changed: What|Removed |Added Platform|openSUSE RPMs |Archlinux Packages CC||laurela...@gmail.com --- Comment #3 from laurela...@gmail.com --- Exactly the same problem. Refreshing constantly. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415728] New: Konsole crashed when moving the cursor over another tab immediately after launching an application
https://bugs.kde.org/show_bug.cgi?id=415728 Bug ID: 415728 Summary: Konsole crashed when moving the cursor over another tab immediately after launching an application Product: konsole Version: 19.08.1 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: davidebeatr...@gmail.com Target Milestone: --- Application: konsole (19.08.1) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-3-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: I had 4 tabs open in a single Konsole process in order to test a project composed by two applications, client and server. Tabs allow me to switch instantly from one application's output to the other's. A few minutes ago I experienced my very first Konsole crash: as soon as I run the command to start the server, I wanted to switch to another tab and run the client. I'm pretty sure I moved the cursor over the tab and clicked on it when the server's one was being resized (due to the text on it changing from the current directory's name to the executable's). Konsole freezed for ~2 seconds and then crashed. Unfortunately I didn't manage to reproduce the crash, but hopefully the backtrace should suffice. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7faa9c05e800 (LWP 25341))] Thread 10 (Thread 0x7faa85489700 (LWP 25351)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d17635dde0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d17635dd90, cond=0x55d17635ddb8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d17635ddb8, mutex=0x55d17635dd90) at pthread_cond_wait.c:655 #3 0x7faa92eb2bcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7faa92eb27e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7faa9f39bfb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7faaa1f892cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7faa85c8a700 (LWP 25350)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d17635dde0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d17635dd90, cond=0x55d17635ddb8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d17635ddb8, mutex=0x55d17635dd90) at pthread_cond_wait.c:655 #3 0x7faa92eb2bcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7faa92eb27e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7faa9f39bfb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7faaa1f892cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7faa8648b700 (LWP 25349)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d17635d6e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d17635d690, cond=0x55d17635d6b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d17635d6b8, mutex=0x55d17635d690) at pthread_cond_wait.c:655 #3 0x7faa92eb2bcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7faa92eb27e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7faa9f39bfb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7faaa1f892cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7faa86c8c700 (LWP 25348)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d17635d6e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d17635d690, cond=0x55d17635d6b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d17635d6b8, mutex=0x55d17635d690) at pthread_cond_wait.c:655 #3 0x7faa92eb2bcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7faa92eb27e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7faa9f39bfb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7faaa1f892cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7faa8748d700 (LWP 25347)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55d17635d6e0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d17635d690, cond=0x55d17635d6b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55d17635d6b8, mutex=0x55d17635d690) at pthread_cond_wait.c:655 #3 0x7faa92eb2bcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7faa92eb27e7 in
[elisa] [Bug 405192] audio playback not working
https://bugs.kde.org/show_bug.cgi?id=405192 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414657] No aparece manejo de key frame
https://bugs.kde.org/show_bug.cgi?id=414657 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414664] System settings randomly crashes each time.
https://bugs.kde.org/show_bug.cgi?id=414664 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415227] Crashes when I right click
https://bugs.kde.org/show_bug.cgi?id=415227 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415244] Windows laptop pen not recognized
https://bugs.kde.org/show_bug.cgi?id=415244 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414722] System failure
https://bugs.kde.org/show_bug.cgi?id=414722 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415703] panel clock configuration tool has misleading labels
https://bugs.kde.org/show_bug.cgi?id=415703 --- Comment #2 from Philip Webb --- 'ls -l /etc/localtime' : -rw-r--r-- 1 root root 3503 Sep 28 2015 /etc/localtime My bug is intended to get the label 'UTC' changed to something more helpful. If it is in fact generated by KDE from system information, perhaps it's looking in the wrong place. There are no problems with any other software re localtime or clock settings. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414034] Extra .desktop file present in okular snap
https://bugs.kde.org/show_bug.cgi?id=414034 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com --- Comment #2 from Guilherme Silva --- FYI, this secondary desktop file appears in the official okular package on Arch Linux as well. The "main" desktop file of Okular is located here: /usr/share/applications/org.kde.okular.desktop And the one you mentioned, which is meant for the "/usr/bin/okularkirigami" binary, sits here: /usr/share/applications/org.kde.okular.kirigami.desktop Also worth mentioning that desktop file for Okular Kirigami _does not_ have a "Categories" section in it, so when you open the Application Launcher in Plasma, the Okular Kirigami program shows under the "Lost & Found" section instead of "Graphics". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415727] New: a6f7aaa67aca9864f7802d170ec6a408176c6870 causes crash when visiting Settings page
https://bugs.kde.org/show_bug.cgi?id=415727 Bug ID: 415727 Summary: a6f7aaa67aca9864f7802d170ec6a408176c6870 causes crash when visiting Settings page Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- https://cgit.kde.org/discover.git/commit/?id=a6f7aaa67aca9864f7802d170ec6a408176c6870 causes Discover to reproducibly crash for me when visiting the Settings page on OpenSUSE Tumblweeed (with Qt 5.13.1). Reverting that commit fixes the issue. Here's the very long and scary backtrace: #0 0x7669643e in markChildQObjectsRecursively(QObject*, QV4::MarkStack*) (parent=parent@entry=0x326c600, markStack=markStack@entry=0x7fff9b80) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1125 #1 0x76696478 in markChildQObjectsRecursively(QObject*, QV4::MarkStack*) (parent=parent@entry=0x3e890f0, markStack=markStack@entry=0x7fff9b80) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1130 #2 0x76696478 in markChildQObjectsRecursively(QObject*, QV4::MarkStack*) (parent=parent@entry=0x3550380, markStack=markStack@entry=0x7fff9b80) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1130 #3 0x76696478 in markChildQObjectsRecursively(QObject*, QV4::MarkStack*) (parent=parent@entry=0x6370d0, markStack=markStack@entry=0x7fff9b80) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1130 #4 0x7669652d in QV4::Heap::QObjectWrapper::markObjects(QV4::Heap::Base*, QV4::MarkStack*) (that=0x7fffea27b2e0, markStack=) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:1148 #5 0x7658d12f in QV4::MarkStack::drain() (this=this@entry=0x7fff9b80) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:73 #6 0x7658db39 in QV4::MemoryManager::mark() (this=this@entry=0x5cdfd0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/memory/qv4mm.cpp:914 #7 0x7658f5fa in QV4::MemoryManager::runGC() (this=0x5cdfd0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/memory/qv4mm.cpp:1047 #8 0x765916c8 in QV4::MemoryManager::allocate(QV4::BlockAllocator*, unsigned long) (size=256, allocator=0x5cdfe0, this=0x5cdfd0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/memory/qv4mm_p.h:328 #9 0x765916c8 in QV4::MemoryManager::allocData(unsigned long) (this=0x5cdfd0, size=size@entry=256) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/memory/qv4mm.cpp:797 #10 0x7665b853 in QV4::MemoryManager::allocManaged(unsigned long, QV4::Heap::InternalClass*) (ic=, size=256, this=) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/memory/qv4mm_p.h:163 #11 0x7665b853 in QV4::MemoryManager::allocManaged(unsigned long, QV4::InternalClass*) (ic=, size=, this=) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/memory/qv4mm_p.h:177 #12 0x7665b853 in QV4::MemoryManager::allocManaged(unsigned long) (size=, this=) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/memory/qv4mm_p.h:185 #13 0x7665b853 in QV4::MemberData::allocate(QV4::ExecutionEngine*, unsigned int, QV4::Heap::MemberData*) (e=e@entry=0x5feea0, n=, old=old@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/jsruntime/qv4memberdata.cpp:88 #14 0x76747bea in QQmlVMEMetaObject::QQmlVMEMetaObject(QV4::ExecutionEngine*, QObject*, QQmlRefPointer const&, QQmlRefPointer const&, int) (this=0x2f7cbf0, engine=0x5feea0, obj=, cache=..., qmlCompilationUnit=..., qmlObjectId=) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/qml/qqmlvmemetaobject.cpp:334 #15 0x767e637d in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) (this=this@entry=0x7fffa160, index=-1, index@entry=0, instance=0x0, bindingTarget=0x0, valueTypeProperty=valueTypeProperty@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/qml/qqmlobjectcreator.cpp:1480 #16 0x767e6e2c in QQmlObjectCreator::createInstance(int, QObject*, bool) (this=0x7fffa160, index=, parent=,
[kig] [Bug 401512] kig crashes with simple python script with a failing assertion
https://bugs.kde.org/show_bug.cgi?id=401512 --- Comment #10 from Maurizio Paolini --- (In reply to David E. Narvaez from comment #8) > (In reply to Kevin Kofler from comment #7) > > The patch from comment #2 prevents the tuple from being de-refcounted all > > the way down to 0 (because it adds a bogus unowned reference), so the tuple > > is leaked, and its continued existence also keeps the arguments referenced. > > (It is the destruction of the tuple that decreases the reference count of > > each argument.) > > Ah, makes sense. > > > On the other hand, the patch from comment #5 looks like the correct fix to > > me. > > I agree. Franco, can you post your patch to Phabricator? Against the > release/19.12 branch please. On behalf of Franco I created a task on phabricator: https://phabricator.kde.org/T12453 however I am new to phabricator, so I don't know how to proceed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415666] On settings page, native distro software sources button is missing (git master)
https://bugs.kde.org/show_bug.cgi?id=415666 Aleix Pol changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/a6f7aaa67aca9864f7802 ||d170ec6a408176c6870 Resolution|--- |FIXED --- Comment #5 from Aleix Pol --- Git commit a6f7aaa67aca9864f7802d170ec6a408176c6870 by Aleix Pol. Committed on 31/12/2019 at 01:38. Pushed by apol into branch 'master'. sources: fix source actions in older versions of Qt QList is not iterable over there, so we had to turn it into a QVariantList. M +2-2libdiscover/backends/DummyBackend/DummySourcesBackend.cpp M +1-1libdiscover/backends/DummyBackend/DummySourcesBackend.h M +4-3libdiscover/backends/FlatpakBackend/FlatpakSourcesBackend.cpp M +1-1libdiscover/backends/FlatpakBackend/FlatpakSourcesBackend.h M +1-1libdiscover/backends/FlatpakBackend/tests/FlatpakTest.cpp M +1-1libdiscover/backends/FwupdBackend/FwupdSourcesBackend.cpp M +1-1libdiscover/backends/FwupdBackend/FwupdSourcesBackend.h M +2-2 libdiscover/backends/PackageKitBackend/PackageKitSourcesBackend.cpp M +2-2 libdiscover/backends/PackageKitBackend/PackageKitSourcesBackend.h M +1-1libdiscover/backends/SnapBackend/SnapBackend.cpp M +2-2libdiscover/resources/AbstractSourcesBackend.h https://commits.kde.org/discover/a6f7aaa67aca9864f7802d170ec6a408176c6870 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415258] Kontact crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=415258 Gary L. Greene, Jr. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Gary L. Greene, Jr. --- Disregard. This appears to be resolved with recent updates from Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 415726] New: SMB4K unexpected crash after resume
https://bugs.kde.org/show_bug.cgi?id=415726 Bug ID: 415726 Summary: SMB4K unexpected crash after resume Product: Smb4k Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: dasfr...@gmail.com Target Milestone: --- Application: smb4k (3.0.2) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Was waking from a suspend. Issue with eno1 (dhcp problem) so switched to wifi. smb4k reported it had crashed. Possibly related to restoring previous mounts. -- Backtrace: Application: Smb4K (smb4k), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9de1860840 (LWP 25908))] Thread 8 (Thread 0x7f9d9a787700 (LWP 5662)): #0 0x7f9ddd5660b4 in __GI___libc_read (fd=35, buf=0x7f9d9a786b9e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f9d9b354021 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f9d9b5d2a2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f9d9b5d34a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f9d9b5d3560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f9d9b5e13c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f9d9b383318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f9dd90846db in start_thread (arg=0x7f9d9a787700) at pthread_create.c:463 #8 0x7f9ddd57788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f9d9bfff700 (LWP 25916)): #0 0x7f9ddd56abf9 in __GI___poll (fds=0x55b107e70ec0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9dd6f125c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9dd6f12962 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9da19060e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f9dd6f3a195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9dd90846db in start_thread (arg=0x7f9d9bfff700) at pthread_create.c:463 #6 0x7f9ddd57788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f9da0f65700 (LWP 25915)): #0 0x7f9ddd56abf9 in __GI___poll (fds=0x55b107e56a30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9dd6f125c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9dd6f126dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9dd6f12721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9dd6f3a195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9dd90846db in start_thread (arg=0x7f9da0f65700) at pthread_create.c:463 #6 0x7f9ddd57788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f9dabbee700 (LWP 25913)): #0 0x7f9dd908a9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b107c58388) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b107c58338, cond=0x55b107c58360) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b107c58360, mutex=0x55b107c58338) at pthread_cond_wait.c:655 #3 0x7f9db47c32cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f9db47c2ff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f9dd90846db in start_thread (arg=0x7f9dabbee700) at pthread_create.c:463 #6 0x7f9ddd57788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f9db79d7700 (LWP 25912)): #0 0x7f9ddd5660b4 in __GI___libc_read (fd=18, buf=0x7f9db79d6b50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f9dd6f572d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9dd6f120b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9dd6f12570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9dd6f126dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9dddebdb9b in QEventDispatcherGlib::processEvents (this=0x7f9dac000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f9ddde5e06a in QEventLoop::exec (this=this@entry=0x7f9db79d6d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f9dddc793aa in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f9dddc7ab52 in QThreadPrivate::start (arg=0x55b107a53290)
[dolphin] [Bug 408919] "open externally called folder in new tab" feature should take virtual Desktops and Activities into account
https://bugs.kde.org/show_bug.cgi?id=408919 Nate Graham changed: What|Removed |Added CC||ericsbinarywo...@gmail.com --- Comment #6 from Nate Graham --- *** Bug 415725 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415725] When Dolphin is set to open new folders in tabs it produces undesirable behavior with activities
https://bugs.kde.org/show_bug.cgi?id=415725 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- Workaround is to disable the feature for now. :( *** This bug has been marked as a duplicate of bug 408919 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408919] "open externally called folder in new tab" feature should take virtual Desktops and Activities into account
https://bugs.kde.org/show_bug.cgi?id=408919 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390086] Option to move widgets via simple drag-and-drop anywhere on the widget
https://bugs.kde.org/show_bug.cgi?id=390086 Nate Graham changed: What|Removed |Added Version Fixed In||5.18.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Nate Graham --- Global edit mode got in with https://phabricator.kde.org/D24265 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381551] With a vertical panel, Digital Clock's Long Date is truncated
https://bugs.kde.org/show_bug.cgi?id=381551 --- Comment #2 from Nate Graham --- Submitted a patch to fix this: https://phabricator.kde.org/D26312 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 397817] kpat crash when switching games
https://bugs.kde.org/show_bug.cgi?id=397817 --- Comment #22 from Brian Kaye --- Correction to comment 20. Should be 'after' the cards are dealt. Occasionally it will just quit when kpat first started. Usually does not matter the order of games. Most of the time freecell to another game crashes. Rarely does not crash first time after Freecell. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376333] KMail crashed while opening on KDE Neon distribution (fresh install)
https://bugs.kde.org/show_bug.cgi?id=376333 Joshua J. Kugler changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #1 from Joshua J. Kugler --- This bug is going on three years, and I'm still hitting it. I just installed Neon (neon-user-20191226-1116.iso). Logged in. Installed Kmail. Started it. New profile dialog came up, and then it put up a dialog box: The Email program encountered a fatal error and will terminate now. The error was: Invalid parent Letting KMail die, and starting it again seems to let it proceed, but it did fail on both fresh installs I tried. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415725] New: When Dolphin is set to open new folders in tabs it produces undesirable behavior with activities
https://bugs.kde.org/show_bug.cgi?id=415725 Bug ID: 415725 Summary: When Dolphin is set to open new folders in tabs it produces undesirable behavior with activities Product: dolphin Version: 19.08.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ericsbinarywo...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Previous behavior: if I open Dolphin (either from taskbar or from folderview plasmoid) in an activity, it opens a new window in that activity. Current behavior: switches me to whatever activity already has Dolphin open and opens it there. (Basically, the same way that KDE/Plasma handles opening a web browser link) STEPS TO REPRODUCE 1. Have dolphin open in activity 1 2. Open dolphin via taskbar or folderview in activity 2 3. The screen is switched to activity 1 and the folder is opened there. OBSERVED RESULT Switches me to an activity that already has Dolphin open EXPECTED RESULT Should, at the least, search for another Dolphin window in the same activity. But, probably, if it's on another workspace (virtual desktop), the user wants a new copy of Dolphin opened. I'd prefer the latter, but be happy with the former. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION Was told to file a bug by someone who (according to reddit) is a KDE Contributor: https://www.reddit.com/r/kde/comments/ehmhv4/what_options_toggle_gets_me_back_to_the_previous/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415213] Transform Tool Crashing Program After resizing
https://bugs.kde.org/show_bug.cgi?id=415213 --- Comment #5 from Stacey --- Just wondering if theres any update on this as I haven't heard anything? I appreciate it's been the holiday period though. I'm a very regular user of Krita and currently can't use the program due to this issue. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415724] Feature Requests
https://bugs.kde.org/show_bug.cgi?id=415724 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #1 from Jack --- I suspect you selected the wrong Product. Did you mean konsole instead of kmymoney? It also sounds like you want the Importance to be wishlist instead of normal. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396151] Edit option disappeared from the context menu/regression (?)
https://bugs.kde.org/show_bug.cgi?id=396151 stefan.schwar...@gmx.net changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415724] New: Feature Requests
https://bugs.kde.org/show_bug.cgi?id=415724 Bug ID: 415724 Summary: Feature Requests Product: kmymoney Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: usability Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: wefev64...@mailer9.net Target Milestone: --- Add mouse actions to be able to right click and split konsole and yakuake terminals like tilix , and also add funtion to be able to move the terminals around/swap that have been split about by dragging and dropping with the mouse -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 56184] Support loading of foreign XMI file formats
https://bugs.kde.org/show_bug.cgi?id=56184 --- Comment #90 from Ralf Habacker --- Git commit cc799cb6efffbd18fce4678932846703603ef6a7 by Ralf Habacker. Committed on 30/12/2019 at 23:15. Pushed by habacker into branch 'master'. Add check for loading an unsupported xmi version This helps to identify why zargo test cases cannot be loaded. With this commit class UMLDoc gets a private class to hold loading errors and Import_Argo::loadFromArgoFile returns error state in all cases. M +12 -9umbrello/import_argo.cpp M +32 -5umbrello/umldoc.cpp M +5-0umbrello/umldoc.h https://invent.kde.org/kde/umbrello/commit/cc799cb6efffbd18fce4678932846703603ef6a7 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415717] UI Blown up
https://bugs.kde.org/show_bug.cgi?id=415717 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 415616 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415616] Install problem on Windows 10. GUI severely corrupted
https://bugs.kde.org/show_bug.cgi?id=415616 Patrick Silva changed: What|Removed |Added CC||gamedude1...@gmail.com --- Comment #6 from Patrick Silva --- *** Bug 415717 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415718] close windows by double clicking the menu button not working
https://bugs.kde.org/show_bug.cgi?id=415718 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- Works here. Please post both a screenshot and your ~/.config/kwinrc -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415715] Fails to build with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=415715 --- Comment #4 from Wolfgang Bauer --- (In reply to Michail Vourlakos from comment #3) > can you please check that now compiles fine without any other issues? Yes, it compiles fine now with Qt 5.9.4 and 5.9.7, also tested 5.12.6, 5.13.1, and 5.14.0. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 405973] Volume bar in JuK resets to the maximum after closing
https://bugs.kde.org/show_bug.cgi?id=405973 abogi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||juk/commit/50559afaa50d1a28 ||01e71f3d791e679ee80930a6 Resolution|--- |FIXED --- Comment #2 from abogi...@gmail.com --- Git commit 50559afaa50d1a2801e71f3d791e679ee80930a6 by Abdel-Rahman Abdel-Rahman. Committed on 29/12/2019 at 16:14. Pushed by mpyne into branch 'release/19.12'. PlayerManager: Unify volume slots slotVolumeChanged and setVolume should have the same effect but are effectively different. One propagates the signal, and one sets the actual volume. Both are used separately and thus the volume value doesn't become synchronized throughout the application. This commit unifies both functions into a single slot. M +3-7playermanager.cpp M +1-2playermanager.h M +1-1volumepopupbutton.cpp https://invent.kde.org/kde/juk/commit/50559afaa50d1a2801e71f3d791e679ee80930a6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 415722] Add Audacity project mime type icon
https://bugs.kde.org/show_bug.cgi?id=415722 Kai Uwe Broulik changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 --- Comment #5 from Roger Larsson --- Created attachment 124796 --> https://bugs.kde.org/attachment.cgi?id=124796=edit Another update (zypper history) After update problems reappeared in force... (unusable the day after) But after I changed from Plasma (Wayland or Full Wayland - don't remember) to pure Plasma (without Wayland) it works again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 Roger Larsson changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 415723] New: Ark doesn't preserve symlinks in zip files
https://bugs.kde.org/show_bug.cgi?id=415723 Bug ID: 415723 Summary: Ark doesn't preserve symlinks in zip files Product: ark Version: 19.04.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: jman012...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY After unpacking a zip file with symlinks using Ark, the symlinks appear as regular files and don't point anywhere. STEPS TO REPRODUCE 1. Create a test directory 2. Create any file within the directory 3. Create a symlink to the file 4. Create a zip archive (I did this with the `zip` utility, not sure if results are different when using Ark) 5. Delete the original files 6. Extract the zip archive using Ark OBSERVED RESULT Symlinks appear as regular files instead of symlinks. EXPECTED RESULT Symlinks should be preserved as links to their target files. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31, kernel 5.3.16 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION I tested extracting the same archive with the `unzip` utility and the GNOME archive manager on an Ubuntu 18.04 virtual machine and symlinks were preserved in both cases. I've used previous versions of Ark on zip files with symlinks successfully. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 415722] New: Add Audacity project mime type icon
https://bugs.kde.org/show_bug.cgi?id=415722 Bug ID: 415722 Summary: Add Audacity project mime type icon Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: k...@privat.broulik.de CC: kain...@gmail.com Target Milestone: --- SUMMARY There should be a mime type icon for Audacity projects. There is already an Audacity app icon, so there should also be one for Audacity project files of mime type application/x-audacity-project. Probably some generic audio file icon with the Audacity icon in it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415605] Full Screen toolbar item is shown in French while my config is in English
https://bugs.kde.org/show_bug.cgi?id=415605 --- Comment #11 from Maik Qualmann --- Note: KStandardAction automatically adds an additional "View" menu. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415605] Full Screen toolbar item is shown in French while my config is in English
https://bugs.kde.org/show_bug.cgi?id=415605 --- Comment #10 from Maik Qualmann --- Git commit 0cbbd5a6392c00c95876b0d08cd4cf4b35141e9d by Maik Qualmann. Committed on 30/12/2019 at 22:23. Pushed by mqualmann into branch 'master'. Revert "next try to fix fullscreen translation" M +3-3core/app/main/digikamui5.rc M +3-4core/libs/widgets/mainview/dxmlguiwindow.cpp M +2-2core/utilities/imageeditor/main/imageeditorui5.rc M +3-3core/utilities/import/main/importui5.rc M +3-3core/utilities/lighttable/lighttablewindowui5.rc M +3-3core/utilities/queuemanager/main/queuemgrwindowui5.rc https://invent.kde.org/kde/digikam/commit/0cbbd5a6392c00c95876b0d08cd4cf4b35141e9d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415720] switches to pan tool randomly and gets constatly stuck holding the canvas, the only way to exit it is to click another tool.
https://bugs.kde.org/show_bug.cgi?id=415720 --- Comment #1 from Suzan --- Created attachment 124795 --> https://bugs.kde.org/attachment.cgi?id=124795=edit video of the pan tool bug -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415721] New: extract footage in - out to projekt-filesystem
https://bugs.kde.org/show_bug.cgi?id=415721 Bug ID: 415721 Summary: extract footage in - out to projekt-filesystem Product: kdenlive Version: 19.12.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: peter.kagerer.a...@gmail.com Target Milestone: --- Created attachment 124794 --> https://bugs.kde.org/attachment.cgi?id=124794=edit extract menu settings SUMMARY STEPS TO REPRODUCE 1. open footage video and audio 2. set in and out marker 3. use menu extract and export to folder-structure OBSERVED RESULT 1. seconds and frame-unit problematic 2. ffmpeg -acodec copy -vcodec copy no doing (except audio) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: appimage KDE Frameworks Version: appimage Qt Version: appimage ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415605] Full Screen toolbar item is shown in French while my config is in English
https://bugs.kde.org/show_bug.cgi?id=415605 --- Comment #9 from Maik Qualmann --- Git commit 439852f3396020728de20a43b7dd660fb7e05636 by Maik Qualmann. Committed on 30/12/2019 at 22:15. Pushed by mqualmann into branch 'master'. next try to fix fullscreen translation M +3-3core/app/main/digikamui5.rc M +4-3core/libs/widgets/mainview/dxmlguiwindow.cpp M +2-2core/utilities/imageeditor/main/imageeditorui5.rc M +3-3core/utilities/import/main/importui5.rc M +3-3core/utilities/lighttable/lighttablewindowui5.rc M +3-3core/utilities/queuemanager/main/queuemgrwindowui5.rc https://invent.kde.org/kde/digikam/commit/439852f3396020728de20a43b7dd660fb7e05636 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415720] New: switches to pan tool randomly and gets constatly stuck holding the canvas, the only way to exit it is to click another tool.
https://bugs.kde.org/show_bug.cgi?id=415720 Bug ID: 415720 Summary: switches to pan tool randomly and gets constatly stuck holding the canvas, the only way to exit it is to click another tool. Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: z.maszew...@gmail.com Target Milestone: --- SUMMARY switches to pan tool randomly and gets constatly stuck holding the canvas, the only way to exit it is to click another tool. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm using a huion tablet (new 1060 plus) with the latest drivers but it doesn't seem to be the tablet's fault, since it also happens when i'm using a mouse. I have to manually switch to other tools since the shortcuts for the pan tool don't work while it's stuck (both on my laptop's keyboard and tablet). I attached a video where I tried to show the bug occuring. It switched and was stuck holding the canvas (I wasn't pressing anything), then I tried to turn it off by pressing shortcuts but it didn't do anything. I switched it but then it was stuck again and this time I couldn't hold the canvas and then it got stuck holding the canvas again. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415715] Fails to build with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=415715 --- Comment #3 from Michail Vourlakos --- (In reply to Wolfgang Bauer from comment #0) > lattedock 0.9.6 fails to build with Qt 5.9, although 5.9.0 is specified as > minimum version in CMakeLists.txt (and 0.9.5 built fine). > > Compiler error: > /home/abuild/rpmbuild/BUILD/latte-dock-0.9.6/app/view/panelshadows.cpp: In > member function 'void* PanelShadows::Private::createPixmap(const QPixmap&)': > /home/abuild/rpmbuild/BUILD/latte-dock-0.9.6/app/view/panelshadows.cpp:265: > 15: error: 'class QImage' has no member named 'sizeInBytes' > image.sizeInBytes(), image.constBits()); >^~~ > > QImage::sizeInBytes() was introduced in Qt 5.10 according to the > documentation. can you please check that now compiles fine without any other issues? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415715] Fails to build with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=415715 Michail Vourlakos changed: What|Removed |Added Latest Commit||https://commits.kde.org/lat ||te-dock/3108a73533a51b9818c ||2fb2fa7d62e6f241190ba Version Fixed In||0.9.7 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Michail Vourlakos --- Git commit 3108a73533a51b9818c2fb2fa7d62e6f241190ba by Michail Vourlakos. Committed on 30/12/2019 at 21:57. Pushed by mvourlakos into branch 'master'. fixed compile with qt 5.9 FIXED-IN:0.9.7 M +1-1app/view/panelshadows.cpp https://commits.kde.org/latte-dock/3108a73533a51b9818c2fb2fa7d62e6f241190ba -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415715] Fails to build with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=415715 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/3108a73533a51b9818c |te-dock/ca8aadf1a9ad7218655 |2fb2fa7d62e6f241190ba |37183bfed66bb7d9c2b6f --- Comment #2 from Michail Vourlakos --- Git commit ca8aadf1a9ad721865537183bfed66bb7d9c2b6f by Michail Vourlakos. Committed on 30/12/2019 at 21:58. Pushed by mvourlakos into branch 'v0.9'. fixed compile with qt 5.9 FIXED-IN:0.9.7 M +1-1app/view/panelshadows.cpp https://commits.kde.org/latte-dock/ca8aadf1a9ad721865537183bfed66bb7d9c2b6f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415719] New: Digikam cannot save images in heic or heif format.
https://bugs.kde.org/show_bug.cgi?id=415719 Bug ID: 415719 Summary: Digikam cannot save images in heic or heif format. Product: digikam Version: 7.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-FilesIO-HEIF Assignee: digikam-bugs-n...@kde.org Reporter: tlteebken-...@outlook.com Target Milestone: --- SUMMARY Digikam cannot save images in heic/heif format. STEPS TO REPRODUCE 1. Try to save as, or export an open image in Digikam in the heic/heif format. OBSERVED RESULT Error: "Failed to save [input file] to [output path]." EXPECTED RESULT File would save normally like it does from any other format. SOFTWARE/OS VERSIONS Windows: 10 x64, v. 1909. macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Digikam 7.0.0-beta 1 x64 (Dec 27 build) ADDITIONAL INFORMATION I have tested on my Win10 machine, I can open, and save, heic/heif files normally in other applications. There are two applications on my machine that can OPEN heic/heif files normally, but throw an error when you try to save in heic/heif format: 1. GIMP 2.10.14 2. Digikam 7.0.0-beta 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415718] New: close windows by double clicking the menu button not working
https://bugs.kde.org/show_bug.cgi?id=415718 Bug ID: 415718 Summary: close windows by double clicking the menu button not working Product: kwin Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: swipe...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enable close windows by double clicking the menu button not working from Window Decorations \ Titlebar Buttons 2. Double click titlebar menu button to close 3. OBSERVED RESULT Menu is displayed EXPECTED RESULT Window should close SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 5.4.6-arch3-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION Also observable on my other Arch Linux laptop (Plasma 5.17.4) but I'm told it works fine in KDE Neon with Plasma 5.17.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415700] "Welcome to" screen still mentions v5.0
https://bugs.kde.org/show_bug.cgi?id=415700 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/f53d229b4129 ||26407d7a0121b06cfbf15272691 ||d Resolution|INTENTIONAL |FIXED --- Comment #2 from Maik Qualmann --- Git commit f53d229b412926407d7a0121b06cfbf15272691d by Maik Qualmann. Committed on 30/12/2019 at 21:26. Pushed by mqualmann into branch 'master'. change compared to digiKam 6.x FIXED-IN: 7.0.0 M +1-1core/app/views/stack/welcomepageview.cpp https://invent.kde.org/kde/digikam/commit/f53d229b412926407d7a0121b06cfbf15272691d -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405030] Start search with CTRL+F
https://bugs.kde.org/show_bug.cgi?id=405030 --- Comment #3 from Nate Graham --- Took another look and figured out how to fix this: https://phabricator.kde.org/D26305 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415605] Full Screen toolbar item is shown in French while my config is in English
https://bugs.kde.org/show_bug.cgi?id=415605 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #8 from Maik Qualmann --- Unfortunately not fixed yet... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415702] Cannot abort or stop find Duplicate process
https://bugs.kde.org/show_bug.cgi?id=415702 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- I will rebuild all windows bundles tomorrow morning... Gilles -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415717] New: UI Blown up
https://bugs.kde.org/show_bug.cgi?id=415717 Bug ID: 415717 Summary: UI Blown up Product: kdenlive Version: 19.08.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gamedude1...@gmail.com Target Milestone: --- Created attachment 124793 --> https://bugs.kde.org/attachment.cgi?id=124793=edit UI out of wack Every time I go to open kdenlive, all the ui elements are blown up off the screen. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 415716] New: Cannot find the setting for default LivePreview compiler
https://bugs.kde.org/show_bug.cgi?id=415716 Bug ID: 415716 Summary: Cannot find the setting for default LivePreview compiler Product: kile Version: 2.9.92 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: yannl35...@gmail.com Target Milestone: --- I can choose a compiler in Build/LivePreview, but cannot find a setting in Settings/Configure Kile > Kile/LivePreview for a default compiler, yet I would like the default compiler to be LuaLaTeX. On a side note, is there a way to set this in a settings file, and where can I find them? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411100] Valgrind does not provide a solution in the error message when an mmap error is detected.
https://bugs.kde.org/show_bug.cgi?id=411100 --- Comment #5 from João M. S. Silva --- I'm not sure it also solves it for Valgrind because Valgrind had an additional issue with Ada elaboration / stack unwinding or so (don't understand enough about it) that I could never solve. Anyway, it could be: * by making your executable be position-independent, so it can be loaded anywhere. You can do that by compiling with switch -fPIE and linking with switch -pie. You should also pass -shared to the binder, but I believe this is only applicable to Ada code? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415715] New: Fails to build with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=415715 Bug ID: 415715 Summary: Fails to build with Qt 5.9 Product: lattedock Version: 0.9.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: wba...@tmo.at Target Milestone: --- lattedock 0.9.6 fails to build with Qt 5.9, although 5.9.0 is specified as minimum version in CMakeLists.txt (and 0.9.5 built fine). Compiler error: /home/abuild/rpmbuild/BUILD/latte-dock-0.9.6/app/view/panelshadows.cpp: In member function 'void* PanelShadows::Private::createPixmap(const QPixmap&)': /home/abuild/rpmbuild/BUILD/latte-dock-0.9.6/app/view/panelshadows.cpp:265:15: error: 'class QImage' has no member named 'sizeInBytes' image.sizeInBytes(), image.constBits()); ^~~ QImage::sizeInBytes() was introduced in Qt 5.10 according to the documentation. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415714] New: Settings can't close
https://bugs.kde.org/show_bug.cgi?id=415714 Bug ID: 415714 Summary: Settings can't close Product: lattedock Version: 0.9.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: psd...@msn.com Target Milestone: --- Created attachment 124792 --> https://bugs.kde.org/attachment.cgi?id=124792=edit screenshot of bug reproduced on my system, with system info Sorry for bad english grammar SUMMARY Setting area mark (the highlight area under dock and at settings dock's bottom) of latte once i opened it. Only way to close it is to kill latte job STEP TO REPRODUCE 1. open latte-dock 2. open settings 3. close settings OBSERVED RESULT settings window close but area still not EXPECTED RESULT settings window and area close EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux, kernel 5.4.6 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65 Qt Version: 5.14 ADDITIONAL INFORMATION bug reproduced on 3 different pc (archlinux all the three) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415702] Cannot abort or stop find Duplicate process
https://bugs.kde.org/show_bug.cgi?id=415702 --- Comment #3 from Alexandre Belz --- Thank you Maik, Will test at next windows build. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415702] Cannot abort or stop find Duplicate process
https://bugs.kde.org/show_bug.cgi?id=415702 --- Comment #2 from Maik Qualmann --- Git commit ca19063c05507c42603989d381163042157d164c by Maik Qualmann. Committed on 30/12/2019 at 20:28. Pushed by mqualmann into branch 'master'. try to enable C++11 support for MinGW (untested) M +3-0core/CMakeLists.txt https://invent.kde.org/kde/digikam/commit/ca19063c05507c42603989d381163042157d164c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415707] fedora31/plasma 5.17.4 subPixelRendering RGB not taken into account after logoff/login
https://bugs.kde.org/show_bug.cgi?id=415707 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415711] Snap installed Okular (v1.72 or v 19.04.2?) does not open files with filenames containing blancs
https://bugs.kde.org/show_bug.cgi?id=415711 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||j...@jriddell.org, ||sit...@kde.org --- Comment #2 from Albert Astals Cid --- Adding people that take care of the snap -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415711] Snap installed Okular (v1.72 or v 19.04.2?) does not open files with filenames containing blancs
https://bugs.kde.org/show_bug.cgi?id=415711 --- Comment #1 from adalbert.hans...@gmx.de --- Since the snap-installed Okular showed several bugs I uninstalled it and installed the albeit older version 1.3.3 instead, which came with sudo apt install okular. Version 1.3.3 came up which does not have this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415332] [Snap] Okular does not show the dialogue to let me load a file
https://bugs.kde.org/show_bug.cgi?id=415332 --- Comment #8 from adalbert.hans...@gmx.de --- Now I have uninstalled the snap-installed version (`sudo snap remove okular`) and replaced it by one installed with `sudo apt install okular`. Version 1.3.3 came up which does not have this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #5 from Bob --- Created attachment 124791 --> https://bugs.kde.org/attachment.cgi?id=124791=edit text report from force quit of hung import DigiKam not responding -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 398323] Add gocryptfs support
https://bugs.kde.org/show_bug.cgi?id=398323 soredake changed: What|Removed |Added CC||fds...@krutt.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415708] Okular shows another version than shown during installation
https://bugs.kde.org/show_bug.cgi?id=415708 Luigi Toscano changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||luigi.tosc...@tiscali.it --- Comment #1 from Luigi Toscano --- The correct version is the one shows in the about dialog. The version used by the distribution is an unintended side effect of the way Okular is distributed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 --- Comment #14 from jochen --- Forgot to mention: I was starting with a new .aqbanking profile, did not migrate. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 --- Comment #13 from jochen --- Not sure whether this helps: I build gwenhywfar, aqbanking and kmymoney in (archlinux) docker image. All three fresh from git/master. Getting now same behaviour (#41518 & this ticket) than using appimage. Reverted back to previous docker build (kmymoney 5.0.3). At least shortcuts working again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415553] Don't work Ctrl-a in project bin
https://bugs.kde.org/show_bug.cgi?id=415553 emohr changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415553] Don't work Ctrl-a in project bin
https://bugs.kde.org/show_bug.cgi?id=415553 emohr changed: What|Removed |Added Version Fixed In||19.12.1 Latest Commit||https://invent.kde.org/kde/ ||kdenlive/commit/cf2deea58b4 ||e3d2aaaccdc5504ca41ad47f0c8 ||8f --- Comment #2 from emohr --- Implemented. Commit https://invent.kde.org/kde/kdenlive/commit/cf2deea58b4e3d2aaaccdc5504ca41ad47f0c88f -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 405709] [Feature request] Printing to PDF - remember last used location
https://bugs.kde.org/show_bug.cgi?id=405709 ikidd3...@gmail.com changed: What|Removed |Added CC||ikidd3...@gmail.com --- Comment #3 from ikidd3...@gmail.com --- As above, though I would prefer if it just kept the last save location permanently, but I'd be happy with per-session even. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415666] On settings page, native distro software sources button is missing (git master)
https://bugs.kde.org/show_bug.cgi?id=415666 --- Comment #4 from Rik Mills --- (In reply to Aleix Pol from comment #3) > I couldn't reproduce as is. Can you check that you have > /usr/share/applications/software-properties-qt.desktop? I do. If I did not, I would not be able to identify in a git bisect which commit make it vanish. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399530] Display which backends/sources are represented in the ApplicationDelegate
https://bugs.kde.org/show_bug.cgi?id=399530 --- Comment #9 from Nate Graham --- Yep, that's the idea. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399530] Display which backends/sources are represented in the ApplicationDelegate
https://bugs.kde.org/show_bug.cgi?id=399530 --- Comment #8 from Walter Lapchynski --- If you mean the source would be shown on each item on the list, rather than solely within the individual metadata when you select an item, that sounds like a great upgrade. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] [qt 5.14] - dock background and rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 --- Comment #21 from Petros --- I installed (again) latte-dock-git just to see this fixed! Fix confirmed! Thanks a lot Michalis. Happy new year!! -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 415713] New: Print dialog wants to read every file in $HOME
https://bugs.kde.org/show_bug.cgi?id=415713
Bug ID: 415713
Summary: Print dialog wants to read every file in $HOME
Product: print-manager
Version: 18.12
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dantt...@gmail.com
Reporter: luke-jr+kdeb...@utopios.org
Target Milestone: ---
SUMMARY
Whenever I go to print, the print dialog blocks for a minute or two while it
tries to read every file in my home directory (which is annoyingly slow and
big, but that's an unrelated issue)
STEPS TO REPRODUCE
1. Open Print dialog in any KDE program
OBSERVED RESULT
Minutes go by with the dialog non-responsive.
strace shows it stat'ing, opening, and reading every file in $HOME
EXPECTED RESULT
Print dialog is immediately usable, and doesn't try to read my files in $HOME
without good reason.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.14.5.1
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
#0 statx (fd=-100, path=0x55a32dc77008 "/home/luke-jr/print.pdf", flags=0,
mask=mask@entry=4095, buf=0x7fff55e7a0e0) at
../sysdeps/unix/sysv/linux/statx.c:29
resultvar = 0
ret =
#1 0x7fc3fa4fe378 in qt_real_statx (fd=,
pathname=, flags=, statxBuffer=)
at io/qfilesystemengine_unix.cpp:319
ret =
#2 0x7fc3fa4ff1f7 in qt_statx (statxBuffer=0x7fff55e7a0e0,
pathname=) at io/qfilesystemengine_unix.cpp:325
No locals.
#3 QFileSystemEngine::fillMetaData (entry=..., data=..., what=...,
what@entry=...) at io/qfilesystemengine_unix.cpp:988
nativeFilePath = {d = 0x55a32dc76ff0}
entryErrno = 0
statBuffer = {st_dev = 17592186048511, st_ino = 0, st_nlink =
4294967296001, st_mode = 1000, st_uid = 33188, st_gid = 67334240, __pad0 = 0,
st_rdev = 19566453, st_size = 38216, st_blksize = 116, st_blocks = 1569385784,
st_atim = {tv_sec = 46848817, tv_nsec = 1540957529}, st_mtim = {tv_sec =
680182368, tv_nsec = 1540957553}, st_ctim = {tv_sec = 266299013, tv_nsec =
1540957553}, __glibc_reserved = {266299013, 0, 206158430208}}
statxBuffer = {stx_mask = 4095, stx_blksize = 4096, stx_attributes = 0,
stx_nlink = 1, stx_uid = 1000, stx_gid = 1000, stx_mode = 33188, __statx_pad1 =
{0}, stx_ino = 67334240, stx_size = 19566453, stx_blocks = 38216,
stx_attributes_mask = 116, stx_atime = {tv_sec = 1569385784, tv_nsec =
46848817, __statx_timestamp_pad1 = {0}}, stx_btime = {tv_sec = 1540957529,
tv_nsec = 680182368, __statx_timestamp_pad1 = {0}}, stx_ctime = {tv_sec =
1540957553, tv_nsec = 266299013, __statx_timestamp_pad1 = {0}}, stx_mtime =
{tv_sec = 1540957553, tv_nsec = 266299013, __statx_timestamp_pad1 = {0}},
stx_rdev_major = 0, stx_rdev_minor = 0, stx_dev_major = 0, stx_dev_minor = 48,
__statx_pad2 = {0 }}
statResult =
#4 0x7fc3fa49fd4b in QFileInfoPrivate::checkAttribute, QFileInfo::isDir() const:: >
(defaultValue=false, engineLambda=..., fsLambda=..., fsFlags=...,
this=0x55a32dc7d270) at
../../include/QtCore/../../src/corelib/global/qflags.h:144
No locals.
#5 QFileInfoPrivate::checkAttribute, QFileInfo::isDir() const:: > (engineLambda=...,
fsLambda=..., fsFlags=..., this=0x55a32dc7d270) at io/qfileinfo_p.h:201
No locals.
#6 QFileInfo::isDir (this=this@entry=0x7fff55e7a390) at io/qfileinfo.cpp:1013
d = 0x55a32dc7d270
#7 0x7fc3fa6056ab in QMimeDatabase::mimeTypeForFile (this=0x7fff55e7a490,
fileInfo=..., mode=QMimeDatabase::MatchDefault) at
mimetypes/qmimedatabase.cpp:552
locker = {val = 140479700068001}
file = { = { = { = {_vptr.QObject =
0x22, static staticMetaObject = {d = {superdata = 0x0, stringdata =
0x7fc3fa6e0220 , data = 0x7fc3fa6e0100
, static_metacall = 0x7fc3fa58a070
,
relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x5d46ca662f6cbf00},
static staticQtMetaObject = {d = {superdata = 0x0, stringdata = 0x7fc3fa6e2fe0
, data = 0x7fc3fa6e0340 ,
static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static
staticMetaObject = {d = {superdata = 0x7fc3fa9df140
, stringdata = 0x7fc3fa6cba20
, data = 0x7fc3fa6cb920 ,
static_metacall = 0x7fc3fa4a2a70 , relatedMetaObjects = 0x0, extradata = 0x0}}},
static staticMetaObject = {d = {superdata = 0x7fc3fa9e3f80
, stringdata = 0x7fc3fa6cb880
, data = 0x7fc3fa6cb840
, static_metacall = 0x7fc3fa49bef0
,
relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d =
{superdata = 0x7fc3fa9e3de0 , stringdata =
0x7fc3fa6cb6c0 , data = 0x7fc3fa6cb680
, static_metacall = 0x7fc3fa498850
,
relatedMetaObjects = 0x0, extradata = 0x0}}}
nativeFilePath = {d = 0x13}
statBuffer = {st_dev = 140479693343258, st_ino = 94159336100472,
st_nlink = 94159336100496, st_mode = 1441243872, st_uid = 32767, st_gid =
1441244144, __pad0 = 32767, st_rdev = 94159336100472, st_size =
140479693343258, st_blksize = 140479694772543, st_blocks = 8, st_atim = {tv_sec
= 0,
[Discover] [Bug 415666] On settings page, native distro software sources button is missing (git master)
https://bugs.kde.org/show_bug.cgi?id=415666 --- Comment #3 from Aleix Pol --- I couldn't reproduce as is. Can you check that you have /usr/share/applications/software-properties-qt.desktop? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 --- Comment #16 from Subin --- (In reply to Erasmo Caponio from comment #14) > After removing Snapd from my system (that honestly I find quite useless and > full of problems) everything works fine with Apparmor. Now Akonadi starts > without any problem Is snapd really related to this ? This is a KDE Neon issue. Any confirmed workarounds to fix it ? I can't access KMail :( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415712] GUI Load-Failure Upon Opening (Most of the time)
https://bugs.kde.org/show_bug.cgi?id=415712 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Severity|grave |normal Status|REPORTED|NEEDSINFO --- Comment #1 from Tymond --- Try to reset your configuration: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration - make sure to remove kritadisplayrc file as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415712] New: GUI Load-Failure Upon Opening (Most of the time)
https://bugs.kde.org/show_bug.cgi?id=415712 Bug ID: 415712 Summary: GUI Load-Failure Upon Opening (Most of the time) Product: krita Version: 4.2.7.1 Platform: Other OS: other Status: REPORTED Severity: grave Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: seanbanksbl...@gmail.com Target Milestone: --- Created attachment 124790 --> https://bugs.kde.org/attachment.cgi?id=124790=edit Failure To Open GUI -- screenshot SUMMARY Krita used to open fine with no problems, one day it started failing to load the interface at the proper resolution. For a while, I was able to get it to open after 2 or 3 tries. These days I give up each time I open it because it always seems to fail to load now. STEPS TO REPRODUCE 1. Open the Krita Program 2. Observe Failure to Load 3. Close Krita OBSERVED RESULT Cannot see GUI in a usable fashion. EXPECTED RESULT Can see GUI in a usable fashion. OpenGL Info Vendor: "Intel" Renderer: "Intel(R) HD Graphics 620" Version: "3.0.0 - Build 21.20.16.4550" Shading language: "1.30 - Build 21.20.16.4550" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false == log == Supported renderers: QFlags(0x2|0x4|0x8) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 4 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) 4 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profile QSurfaceFormat::CompatibilityProfile) 4 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 8 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace
[systemsettings] [Bug 405030] Start search with CTRL+F
https://bugs.kde.org/show_bug.cgi?id=405030 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #2 from Thiago Sueto --- As an addendum, currently pressing Ctrl+F on System Settings will show: >Ambiguous shortcut detected >The key sequence 'Ctrl+F' is ambiguous. Use 'Configure Shortcuts' >from the 'Settings' menu to solve the ambiguity. >No action will be triggered. I'm using Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411970] Extract and save zone not working
https://bugs.kde.org/show_bug.cgi?id=411970 --- Comment #5 from emohr --- "Save zone" and "Extract zone" in project monitor still not working. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] [qt 5.14] - dock background and rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/80ed729fcf0700adf6b |te-dock/32bcf26eaf75068c112 |afb534014f20ef26d78c3 |548645e5638b5e1f824ab --- Comment #20 from Michail Vourlakos --- Git commit 32bcf26eaf75068c112548645e5638b5e1f824ab by Michail Vourlakos. Committed on 30/12/2019 at 17:24. Pushed by mvourlakos into branch 'v0.9'. [qt5.14] - restore editVisual to normal --when the view settings window is closed then the View must return to normal mode and disable the editMode. In qt 5.14 default states that have a "when" property do not play well M +2-1containment/package/contents/ui/editmode/Visual.qml https://commits.kde.org/latte-dock/32bcf26eaf75068c112548645e5638b5e1f824ab -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415333] [qt 5.14] - Long pressing on Latte dock icon makes it unusable
https://bugs.kde.org/show_bug.cgi?id=415333 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/1e433767812340928f5 |te-dock/d8e9a5688bb4ea6b0e6 |79e672b9ef51a5033a42b |51fdd9e5774d005b077e2 --- Comment #3 from Michail Vourlakos --- Git commit d8e9a5688bb4ea6b0e651fdd9e5774d005b077e2 by Michail Vourlakos. Committed on 30/12/2019 at 17:25. Pushed by mvourlakos into branch 'v0.9'. [qt5.14]-restore dragged task to normal in the end after dragging a task, the task should return to normal state. In qt 5.14 default states that have a "when" property do not play well FIXED-IN:0.9.6 M +5-3plasmoid/package/contents/ui/task/IconItem.qml https://commits.kde.org/latte-dock/d8e9a5688bb4ea6b0e651fdd9e5774d005b077e2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 415333] [qt 5.14] - Long pressing on Latte dock icon makes it unusable
https://bugs.kde.org/show_bug.cgi?id=415333 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lat ||te-dock/1e433767812340928f5 ||79e672b9ef51a5033a42b Version Fixed In||0.9.6 Status|REPORTED|RESOLVED --- Comment #2 from Michail Vourlakos --- Git commit 1e433767812340928f579e672b9ef51a5033a42b by Michail Vourlakos. Committed on 30/12/2019 at 17:19. Pushed by mvourlakos into branch 'master'. [qt5.14]-restore dragged task to normal in the end after dragging a task, the task should return to normal state. In qt 5.14 default states that have a "when" property do not play well FIXED-IN:0.9.6 M +5-3plasmoid/package/contents/ui/task/IconItem.qml https://commits.kde.org/latte-dock/1e433767812340928f579e672b9ef51a5033a42b -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] [qt 5.14] - dock background and rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/80ed729fcf0700adf6b ||afb534014f20ef26d78c3 Resolution|--- |FIXED --- Comment #19 from Michail Vourlakos --- Git commit 80ed729fcf0700adf6bafb534014f20ef26d78c3 by Michail Vourlakos. Committed on 30/12/2019 at 17:13. Pushed by mvourlakos into branch 'master'. [qt5.14] - restore editVisual to normal --when the view settings window is closed then the View must return to normal mode and disable the editMode. In qt 5.14 default states that have a "when" property do not play well M +2-1containment/package/contents/ui/editmode/Visual.qml https://commits.kde.org/latte-dock/80ed729fcf0700adf6bafb534014f20ef26d78c3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415698] VCS plugin function calls redundant
https://bugs.kde.org/show_bug.cgi?id=415698 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- Patches welcome ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #4 from Bob --- Activity Monitor reports create apparently garbage pdf files which are too big to attach. I'll pursue this one with Apple, hopefully in parallel with Digikam fix process. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356711] XembedSNIProxy prevents KWin from unredirecting fullscreen SDL2 apps
https://bugs.kde.org/show_bug.cgi?id=356711 --- Comment #11 from Danni H --- > Don't be antagonistic. My bad. I shouldn't have let my frustration get to me. I'm happy that there is awareness of these issues among the KWin developers. > xwininfo -tree -root would be the most useful, I can't see why our z-stack > would be rasied when a game is in focus. This issue seems to be fixed but regardless I have attached the output of xwininfo while running hexchat and GZDoom, with GZDoom fullscreen and in the foreground. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356711] XembedSNIProxy prevents KWin from unredirecting fullscreen SDL2 apps
https://bugs.kde.org/show_bug.cgi?id=356711 --- Comment #10 from Danni H --- Created attachment 124789 --> https://bugs.kde.org/attachment.cgi?id=124789=edit xwininfo output -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 398257] Weird Black Line Appears Above the Dock On Startup
https://bugs.kde.org/show_bug.cgi?id=398257 tr...@yandex.com changed: What|Removed |Added Platform|Neon Packages |unspecified CC||tr...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #3 from Bob --- I've also had this bug consistently over the last 2 versions of Digikam and MacOS. I let it try to comp[lete for 2 days, and no progress. After the 2-day test, my OS was corrupted, Safari and Apple App Store (and possibly other apps) caused system exceptions (attempt to execute invalid instruction). Reinstall of MaxOS fixed Safari and App Store, but Digikam, and Digikam after reinstall failed as before. This is my first bug report, but I'll try to attach Activity force quit reports. I have also consistently filed reports with Apple when offered. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 Bob changed: What|Removed |Added CC||jenne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399530] Display which backends/sources are represented in the ApplicationDelegate
https://bugs.kde.org/show_bug.cgi?id=399530 --- Comment #7 from Nate Graham --- Ideally, when an application is available from multiple sources, Discover groups them all into one entry. It already does this for many apps. However this grouping requires that Discover be able to identify all of the different sources of the same app as in fact the same app. To do this, it matches on the app's AppStream ID. When multiple apps have the same ID, Discover understands that they're the same app, and groups them. Unfortunately, many app sources don't provide quality AppStream data, or override the app's own AppStream ID with a made-up one of their choice. Some apps don't provide quality metadata either. And so on. This bug report is requesting a fallback mode that shows the source on each list item so that confused users can see for themselves where the app comes from even when the grouping functionality didn't work because of any of the above issues. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415711] New: Snap installed Okular (v1.72 or v 19.04.2?) does not open files with filenames containing blancs
https://bugs.kde.org/show_bug.cgi?id=415711 Bug ID: 415711 Summary: Snap installed Okular (v1.72 or v 19.04.2?) does not open files with filenames containing blancs Product: okular Version: 1.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: adalbert.hans...@gmx.de Target Milestone: --- Created attachment 124788 --> https://bugs.kde.org/attachment.cgi?id=124788=edit Error message shown in the GUI SUMMARY STEPS TO REPRODUCE 1. I double click in the file browser Thunar on a pdf file 2. I try to open the file like this: $/snap/bin/okular "~/Downloads/2017-11-29_Richard Chimera, Ben Shneiderman_An Exploratory Evaluation of Three Interfaces for Browsing Large Hierarchical Tables of Contents.pdf" 2019/12/30 16:04:26.798673 cmd_run.go:889: WARNING: cannot copy user Xauthority file: open ~/.Xauthority: permission denied No protocol specified qt.qpa.xcb: could not connect to display :0.0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Abgebrochen $ 3. OBSERVED RESULT 1. Okular opens with its GUI but ti tells that it could not open the file whose name contains blancs. 2. Error messages see above. What do all the other messages mean and what has to be done to fix them. Something must be utterly wrong with this snap installed Okular! BTW: in the GUI, Open>File does not work. This error has been reported esarlier as bug 415332. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: KDE Frameworks 5.61.0 Qt Version: Qt 5.12.3 (kompiliert gegen 5.12.3) ADDITIONAL INFORMATION this happens on a snap installed version of okular under Xubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415710] New: plasma-discover crush when reinstall inkscape by inkscape-0.92.2.flatpak file
https://bugs.kde.org/show_bug.cgi?id=415710 Bug ID: 415710 Summary: plasma-discover crush when reinstall inkscape by inkscape-0.92.2.flatpak file Product: Discover Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: a44881...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.17.4) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.4.6-arch3-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Because inkscape something wrong, I remove and reinstall from plasma-discover at first. However, the problem didn't solve, thus, I downloaded inkscape-0.92.2.flatpak from inkscape official website and installed, then, the plasma-discover poped up and installed inkscape. After installing, the plasma-discover quit soon every time I open it. It seems relate to GPG verification, which pop up when I start plasma-discover. The crash can be reproduced every time. -- Backtrace: Application: 探詢 (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4254c6d840 (LWP 2942))] Thread 26 (Thread 0x7f41917fa700 (LWP 2990)): #0 0x7f4254d649ef in poll () at /usr/lib/libc.so.6 #1 0x7f4253634120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42536341f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4255324cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f42552cb39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f42550f0e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f42550f1fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7f42540494cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f4254d6f2d3 in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f4191ffb700 (LWP 2989)): #0 0x7f4254d6042c in read () at /usr/lib/libc.so.6 #1 0x7f42535e49f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42536329e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f42536340c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f42536341f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f4255324cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f42552cb39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f42550f0e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f42550f1fd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f42540494cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f4254d6f2d3 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f41927fc700 (LWP 2988)): #0 0x7f4254d6042c in read () at /usr/lib/libc.so.6 #1 0x7f42535e49f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42536329e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f42536340c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f42536341f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f4255324cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f42552cb39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f42550f0e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f42550f1fd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f42540494cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f4254d6f2d3 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f4192ffd700 (LWP 2987)): #0 0x7f4254d649ef in poll () at /usr/lib/libc.so.6 #1 0x7f4253634120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42536341f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f4255324cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f42552cb39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f42550f0e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f42550f1fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7f42540494cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f4254d6f2d3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f41beffd700 (LWP 2979)): [KCrash Handler] #6 0x7f423056ac0f in () at /usr/lib/libflatpak.so.0 #7 0x7f4230574ba4 in flatpak_installation_list_installed_refs_for_update () at /usr/lib/libflatpak.so.0 #8 0x7f4230638f76 in () at /usr/lib/qt/plugins/discover/flatpak-backend.so #9 0x7f42550f5202 in () at /usr/lib/libQt5Core.so.5 #10 0x7f42550f1fd6 in () at /usr/lib/libQt5Core.so.5 #11 0x7f42540494cf in start_thread () at
