[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #7 from Szőts Ákos --- On a second thought, I've decided zst is good enough, especially even after 220 GB it was still decompressing... I could've piped into xz but then you'd have to convert it again back for heaptrack_gui so I decided I leave it untouched. You can find the file on the link in the original post. It can take some time until it's loaded into the program. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423510] Riot's SNI has no title in the main view; works in the tooltip
https://bugs.kde.org/show_bug.cgi?id=423510 Konrad Materka changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Konrad Materka --- The same for me. I've done quick check, the issue is probably not in System Tray - somewhere in between or in Riot itself. I will investigate. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.
https://bugs.kde.org/show_bug.cgi?id=418758 --- Comment #8 from David Hurka --- Maybe Explorer passes the # as #, and Dolphin passes it as %35? Code is here: https://invent.kde.org/graphics/okular/-/blob/master/part.cpp#L1736 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423530] Kate tabs shrunk in size
https://bugs.kde.org/show_bug.cgi?id=423530 Fabian Vogt changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #4 from Fabian Vogt --- Confirmed to be fixed: https://openqa.opensuse.org/tests/1319235#step/kate/22 The tab is actually the full width now instead of half the width, but that's arguably even better. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423632] Segfault when scanning faces
https://bugs.kde.org/show_bug.cgi?id=423632 --- Comment #2 from Maik Qualmann --- My guess is that the crash in OpenCV is triggered by OpenCL hardware acceleration. You are using AMD hardware. OpenCV has an environment variable to disable OpenCL. Maik -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423260] Changing graph title and pressing cancel in the dialog changes the name anyway
https://bugs.kde.org/show_bug.cgi?id=423260 Matej Mrenica changed: What|Removed |Added Resolution|WAITINGFORINFO |--- CC||matejm98m...@gmail.com Status|NEEDSINFO |REPORTED --- Comment #2 from Matej Mrenica --- This is ksysguard application. Step by step: 1. create a new tab 2. add a graph from the right 3. right-click on the y axis 4. select "Properties" 5. Dialog opens, on the first tab there is "Title" field 6. change the title to something else 7. Press "Cancel" 8. The graph title shown in Bold has changed -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423632] Segfault when scanning faces
https://bugs.kde.org/show_bug.cgi?id=423632 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- There is nothing at the crash point that should trigger a crash. Can you please create a new backtrace? Can you please post the output of "opencv_version --hw --opencl"? Can you also test whether the problem with the AppImage can be reproduced? >From here: https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421210] digiKam 5.9.0-1+b1 refuses to start since LMDE4 Debbie upgrade
https://bugs.kde.org/show_bug.cgi?id=421210 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423633] can not access latte global settings
https://bugs.kde.org/show_bug.cgi?id=423633 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/latte-dock/commit/78159c ||3f9e9db886a8e3a83c03380a199 ||b607171 Resolution|--- |FIXED --- Comment #3 from Michail Vourlakos --- Git commit 78159c3f9e9db886a8e3a83c03380a199b607171 by Michail Vourlakos. Committed on 29/06/2020 at 05:29. Pushed by mvourlakos into branch 'master'. update presets to proper contextmenu plugin --at first run, preset settings should be already configured to work properly; in other case the right click context menu does not show the correct entries for latte/docks/panels configuration windows M +1-1shell/package/contents/presets/Default.layout.latte M +1-1shell/package/contents/presets/Extended.layout.latte M +1-1shell/package/contents/presets/Plasma.layout.latte M +1-1shell/package/contents/presets/Unity.layout.latte https://invent.kde.org/plasma/latte-dock/commit/78159c3f9e9db886a8e3a83c03380a199b607171 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 423640] New: Wrong diagnostic with multi-lines Q_PROPERTY
https://bugs.kde.org/show_bug.cgi?id=423640 Bug ID: 423640 Summary: Wrong diagnostic with multi-lines Q_PROPERTY Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: chg...@gmail.com CC: smart...@kde.org Target Milestone: --- SUMMARY Wrong diagnostic with multi-lines Q_PROPERTY STEPS TO REPRODUCE 1. Use QtCreator with built in clazy 2. Multi-line Q_PROPERTY, eg: Q_PROPERTY(QString controllerFirmwareCrc READ controllerFirmwareCrc NOTIFY controllerFirmwareCrcChanged) OBSERVED RESULT /home/chgans/Projects/neon-factory-support/task/NTA-108-touchscreen-module/sources/Testing/Modules/TouchscreenModule.h:79:5: warning: Q_PROPERTY should have either NOTIFY or CONSTANT [-Wclazy-qproperty-without-notify] EXPECTED RESULT No issue reported SOFTWARE/OS VERSIONS Ubuntu 18.04, 64 bits Qt Version: 5.12 Unknown version of clazy ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420869] Certain Tray icons using wrong color from system color scheme
https://bugs.kde.org/show_bug.cgi?id=420869 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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 422108] RGBA Brush Lightness Mask Lag at start of stroke - git d2047f0
https://bugs.kde.org/show_bug.cgi?id=422108 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kmahjongg] [Bug 422069] when i open the game i fined it blank
https://bugs.kde.org/show_bug.cgi?id=422069 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #14 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.
[Bluedevil] [Bug 421160] No funciona el bluetooth
https://bugs.kde.org/show_bug.cgi?id=421160 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.
[frameworks-kio] [Bug 376679] chaning mimeapps.list is not respected by folderview unless you restart Xorg
https://bugs.kde.org/show_bug.cgi?id=376679 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[ark] [Bug 420220] bigger zip archives (>~3.2 GB) can't be opened
https://bugs.kde.org/show_bug.cgi?id=420220 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kdenlive] [Bug 422049] Kdenlive freezes when inserting image into timeline
https://bugs.kde.org/show_bug.cgi?id=422049 --- 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.
[frameworks-kio] [Bug 388471] Open in file manager doesn't work for superfloppies
https://bugs.kde.org/show_bug.cgi?id=388471 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[okular] [Bug 419675] okular crashes when opening a menu if invoked from auctex
https://bugs.kde.org/show_bug.cgi?id=419675 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #16 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.
[korganizer] [Bug 75047] replace simple "add URI dialog" with normal fileselector dialog
https://bugs.kde.org/show_bug.cgi?id=75047 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 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 421889] Kdenlive crashing on start
https://bugs.kde.org/show_bug.cgi?id=421889 --- 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 422781] Kdenlive não inicializa
https://bugs.kde.org/show_bug.cgi?id=422781 --- Comment #3 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 422019] Crash when zooming or scrolling in the timeline
https://bugs.kde.org/show_bug.cgi?id=422019 --- 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.
[frameworks-kio] [Bug 377686] Installed name of kio_http_cache_cleaner conflicts with related KDE4 installation
https://bugs.kde.org/show_bug.cgi?id=377686 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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 421003] Cannot process to h264, h265 or mp3 using latest git version of ffmpeg
https://bugs.kde.org/show_bug.cgi?id=421003 --- Comment #3 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 422475] how to update kdenlive verson 19.12.3
https://bugs.kde.org/show_bug.cgi?id=422475 --- 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 421721] Transform effect displays 100% image size, even when it was changed with "fit to width"
https://bugs.kde.org/show_bug.cgi?id=421721 --- 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.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #50 from bruce.samha...@samhaber.ca --- Comment on attachment 129731 --> https://bugs.kde.org/attachment.cgi?id=129731 Today's /var/log/cups/error_log file I need to remove this file. I submitted it to the wrong Bug. -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 423639] New: Fails to remember device setting
https://bugs.kde.org/show_bug.cgi?id=423639 Bug ID: 423639 Summary: Fails to remember device setting Product: pulseaudio-qt Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: devguy...@gmail.com Target Milestone: --- Created attachment 129752 --> https://bugs.kde.org/attachment.cgi?id=129752&action=edit Fiio BTR5 Pulse Audio setting SUMMARY I have a FiiO BTR5 DAC+AMP, each time I reboot, or unplug or replug the device to USB, my selection seems to be forgotten. Sometimes Fiio BTR5 (with headphone icon) will change, I've seen it also change on it's on from "OFF" to one of the other settings. This result in no audio. Same for FiiO BTR5 (with hardware icon) it will sometime just mess up my selection. This is really getting frustrating for me to always home to open the Pulse Audio setting and have to manually re-set my setting so I can have working audio! What I like the system to be able to do is remember previous selected setting, even if the device has been shut off or unplugged with multiple reboots. If I unplug my FiiO BTR5 device and then have to change the setting for audio to work, I expect when I plug in my device the system is smart enough to understand I want the previous pulse audio setting as my current one, if I then unplug the device it smart enough to fallback to my previous working setting. I tend to get random results which result in no audio working. At first as a new User I was completely baffled by my audio failing to work when it was working and I had no idea how to fix this. This is really poor user experience. FYI: I have had the same issue with BlueYeti mic, which also allow a headphone to be connected to the mic as it also has a DAC+AMP, some mess up with device setting getting changed randomly. STEPS TO REPRODUCE (Case 1) 1. Plug in FiiO BTR5 to USB 2. Open Pulse Audio, configure setting to get audio working. 3. Unplug FiiO BTR5 device 4. Plug in FiiO BTR5 device OBSERVED RESULT (Case 1) Previous setting fail to be remember at times. STEPS TO REPRODUCE (Case 2) 1. Plug in FiiO BTR5 to USB 2. Open Pulse Audio, configure setting to get audio working. 3. Reboot system OBSERVED RESULT (Case 2) Previous setting fail to be remember at times. EXPECTED RESULT Previous setting for the device as remember and re-set properly after reboot or re-plugin of device or after device power is turned back on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleeweed KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] System settings crashes on selecting Account Details from side bar search results
https://bugs.kde.org/show_bug.cgi?id=423638 Syam changed: What|Removed |Added Summary|System settings crashes on |System settings crashes on |selecting Account Details |selecting Account Details |from built-in search|from side bar search |results |results -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] System settings crashes on selecting Account Details from built-in search results
https://bugs.kde.org/show_bug.cgi?id=423638 Syam changed: What|Removed |Added Summary|System settings crashes on |System settings crashes on |selecting Account Details |selecting Account Details ||from built-in search ||results -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] System settings crashes on selecting Account Details
https://bugs.kde.org/show_bug.cgi?id=423638 --- Comment #1 from Syam --- The crash occurs only when selecting Account Details from the search results list. If I open System Settings, and then directly open the Account Details item (under Personalization), it DOES NOT crash. Account Details item opens fine and I have two sub-items - KDE wallet and User Manager. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423638] New: System settings crashes on selecting Account Details
https://bugs.kde.org/show_bug.cgi?id=423638 Bug ID: 423638 Summary: System settings crashes on selecting Account Details Product: systemsettings Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: get.so...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.19-200.fc31.x86_64 x86_64 Distribution: Fedora 31 (KDE Plasma) -- Information about the crash: 1. Open System Settings 2. Search for 'accounts' to get two results - Account Details and Online Accounts 3. Select Account Details 4. System Settings crashes The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efe1c832800 (LWP 18196))] Thread 5 (Thread 0x7efdfbfff700 (LWP 18202)): #0 0x7efe209dea3f in poll () from /lib64/libc.so.6 #1 0x7efe1ec4986e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7efe1ec499a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7efe20f6f8a3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7efe20f1923b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7efe20d69cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7efe20013399 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7efe20d6ae26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7efe064d3700 (LWP 18201)): #0 0x7efe209dea3f in poll () from /lib64/libc.so.6 #1 0x7efe1ec4986e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7efe1ec499a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7efe20f6f8a3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7efe20f1923b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7efe20d69cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7efe20013399 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7efe20d6ae26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7efe076b9700 (LWP 18199)): #0 0x7efe1f5a5d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efe0c5fc19b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7efe0c5fbdab in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7efe0e584700 (LWP 18198)): #0 0x7efe1ec479f8 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7efe1ec491cf in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7efe1ec49812 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7efe1ec499a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7efe20f6f8a3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7efe20f1923b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7efe20d69cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7efe211f5f6a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7efe20d6ae26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7efe1f59f4e2 in start_thread () from /lib64/libpthread.so.0 #10 0x7efe209e96a3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7efe1c832800 (LWP 18196)): [KCrash Handler] #4 0x7efe20924625 in raise () from /lib64/libc.so.6 #5 0x7efe2090d8d9 in abort () from /lib64/libc.so.6 #6 0x7efe20d34b25 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x7efe220723a7 in KPluginInfo::service() const [clone .cold] () from /lib64/libKF5Service.so.5 #8 0x7efe224fa1e9 in KCModuleInfo::service() const () from /lib64/libKF5KCMUtils.so.5 #9 0x7efe2254aede in ModuleView::addModule(KCModuleInfo*) () from /lib64/libsystemsettingsview.so.3 #10 0x7efe2254b60d in ModuleView::loadModule(QModelIndex const&) () from /lib64/libsystemsettingsview.so.3 #11 0x7efe065a1bbf in SidebarMode::changeModule(QModelIndex const&) () from /usr/lib64/qt5/plugins/systemsettings_sidebar_mode.so #12 0x7efe065a1cb1 in SidebarMode::setActiveCategory(int) () f
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 --- Comment #17 from bruce.samha...@samhaber.ca --- Comment on attachment 129750 --> https://bugs.kde.org/attachment.cgi?id=129750 Testpage printed in Letter size When printing set the following options: PDF Option - Force Rasterization Option - GreyScale When printing set the following Properties: Page Tab: Page Size > Letter >> Width= 11" Height= 8.5" Advanced Tab: Shrink Page if necessary to Fit Borders >> Crop (preserve dimensions) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423633] can not access latte global settings
https://bugs.kde.org/show_bug.cgi?id=423633 --- Comment #2 from andresdor...@gmail.com --- OK I think I figured it out the latest latte git is not creating the .config files correctly it seems. I deleted the settings and tried installing 0.9.11. Then I ran it so it can create the configs. Then I uninstalled it and installed the latest git and everything was working fine. To test my theory I deleted all of latte configs again relaunched latte dock and once again i could not get the configure latte option to show instead showing an empty space in the context menu. also another issue that is probably related to this is if i configure the panels with widgets and stuff with the git created config and then exit latte the panels and docks will not load up upon starting latte. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 --- Comment #16 from bruce.samha...@samhaber.ca --- Comment on attachment 129751 --> https://bugs.kde.org/attachment.cgi?id=129751 Testpage printed Tabloid size 11x17" When printing set the following options: PDF Option - Force Rasterization Option - GreyScale When printing set the following Properties: Page Tab: Page Size > Tabloid >> Width= 17" Height= 11" Advanced Tab: Shrink Page if necessary to Fit Borders >> Crop (preserve dimensions) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 --- Comment #15 from bruce.samha...@samhaber.ca --- Created attachment 129751 --> https://bugs.kde.org/attachment.cgi?id=129751&action=edit Testpage printed Tabloid size 11x17" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 --- Comment #14 from bruce.samha...@samhaber.ca --- Created attachment 129750 --> https://bugs.kde.org/attachment.cgi?id=129750&action=edit Testpage printed in Letter size -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 --- Comment #13 from bruce.samha...@samhaber.ca --- Created attachment 129749 --> https://bugs.kde.org/attachment.cgi?id=129749&action=edit Today's /var/log/cups/error_log file This is the "/var/log/cups/error_log" file from the 2 printouts today. The last 2 printouts are the Letter 8.5x11" and lastly the Tabloid 11x17". Both printouts for the 2 sizes of PDFs are printing to an effective A4 size sheet of paper. In the case of the 11x17" paper the printer prints to most of the PDF information croping some at the end; printout size is 281mm x 195mm. In the case of the Letter 8.5x11" paper the printer stops printing 1/2" from the end of the paper, which is a printer limitation; printout height is 195mm and effective length based on the scale is 288mm. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 --- Comment #12 from bruce.samha...@samhaber.ca --- Created attachment 129748 --> https://bugs.kde.org/attachment.cgi?id=129748&action=edit The attachment requested /etc/cups/ppd/hpdeskjet1120c.ppd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423637] New: Krita & digikam
https://bugs.kde.org/show_bug.cgi?id=423637 Bug ID: 423637 Summary: Krita & digikam Product: krita Version: 4.3.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ebm2003...@gmail.com Target Milestone: --- On digikam 7.0.0-rc, is not possible to see the thumbnail and also the image from Krita 2.3.0 (.kra), but if the same file is saved with Krita 2.2.9, everything its ok. STEPS TO REPRODUCE 1. Add some file saved with Krita 2.3.0 on digikam 2. No thumbnail and image visualization 3. Add the same file as before but saved with Krita 2.2.9 4. Everything should be ok with it OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 10 2004 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423084] Keyboard binding breaks "4" key
https://bugs.kde.org/show_bug.cgi?id=423084 --- Comment #6 from Oussema Bouaneni --- So I had a little bit too much time on my hands and I may or may not have gone through all the layouts one by one to see which keys each one broke. Anyway, here's the list. These layouts cause the character "1" to not display properly: ir Persian These layouts cause the character "7" to not display properly: >fr French, >tg French(togo), >al Albanian, >me Montenegrin These layouts cause the character "v" to not display properly: >al Albanian, >ba Bosnian, >me Montenegrin, >si Slovenian These layouts cause the character "u" to not display properly: >ara Arabic, >my Malay(Jawi, Arabic Keyboard), >iq Iraqi These layouts cause the character "h" to not display properly: >cz Czech, >sk Slovak These layouts cause the character "'" to not display properly: >nl Dutch These layouts cause the character "\" to not display properly: >is Icelandic, >lv Latvian, >tr Turkish, >sn Wolof These layouts cause the character "[" to not display properly: >jp Japanese These layouts cause the character "." to not display properly: >la Lao These layouts cause the character "w" to not display properly: >mn Mongolian -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421565] WARNING – DANGEROUS : kdenlive creates broken archive files
https://bugs.kde.org/show_bug.cgi?id=421565 farid changed: What|Removed |Added CC||snd.no...@gmail.com --- Comment #4 from farid --- Probably it is also more compatible with windows, since it probably doesn't support tar. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 282137] Files get installed into / (root) directory
https://bugs.kde.org/show_bug.cgi?id=282137 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Plugin-WebService-Vkontakte CC||caulier.gil...@gmail.com Assignee|imaging-bugs-n...@kde.org |digikam-bugs-n...@kde.org Product|libkvkontakte |digikam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423632] Segfault when scanning faces
https://bugs.kde.org/show_bug.cgi?id=423632 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |7.0.0 CC||caulier.gil...@gmail.com Component|general |Faces-Detection -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423084] Keyboard binding breaks "4" key
https://bugs.kde.org/show_bug.cgi?id=423084 --- Comment #5 from Oussema Bouaneni --- (In reply to Henning from comment #4) > I am not 'looking into this', I don't have a build environment ready for KDE > and haven't written a single line for KDE. I am just providing help for the > analysis. I'm sorry if my meaning didn't get across well. English is my third language. By 'looking into this' I did not mean fixing this bug. I just meant it as in trying to pinpoint the cause of the bug with us and providing suggestions. Sorry for the confusion once again. > Do you have multiple keyboard layouts set up? If so can you still reproduce > the bug if you only leave one keyboard layout configured? Yes, I have three. And it depends on the one I leave: If only leave English or Arabic, the issue is not reproducible. If I only leave French, the "7" key doesn't work. While trying this, I noticed something interesting which was that if I move Arabic up to the top of the list of layouts, the "u" key works properly, whereas if it's it's in the second or third spot, the "u" key doesn't work. With French, as long as it's a configured layout, the "7" key won't work, no matter its position in the list of layouts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423554] x11-wm/plasma5-kwin kwin_rules_dialog closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=423554 Scott Loga changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Scott Loga --- *** This bug has been marked as a duplicate of bug 423436 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423436] kwin_rules_dialog closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=423436 Scott Loga changed: What|Removed |Added CC||scott.l...@me.com --- Comment #4 from Scott Loga --- *** Bug 423554 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423636] New: Crash when disconnecting a displays (the docking station)
https://bugs.kde.org/show_bug.cgi?id=423636 Bug ID: 423636 Summary: Crash when disconnecting a displays (the docking station) Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- SUMMARY Crash when disconnecting the docking station. It's asserting so it looks like an logical issue in our code. OBSERVED RESULT #0 0x7f651248a355 in raise () at /usr/lib/libc.so.6 #1 0x7f651247390b in abort () at /usr/lib/libc.so.6 #2 0x7f6512b42c51 in qt_message_fatal (message=..., context=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:1914 #3 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x72f235f8, msg=msg@entry=0x7f6512e40ea0 "ASSERT: \"%s\" in file %s, line %d") at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.cpp:893 #4 0x7f6512b4204a in qt_assert(char const*, char const*, int) (assertion=, file=, line=) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/global/qlogging.h:90 #5 0x7f650d03d08e in KWin::DrmOutput::~DrmOutput() (this=0x55a997c1d7a0) at /home/apol/devel/frameworks/kwin/plugins/platforms/drm/drm_output.cpp:61 #6 0x7f650d03d2cc in KWin::DrmOutput::~DrmOutput() (this=0x55a997c1d7a0) at /home/apol/devel/frameworks/kwin/plugins/platforms/drm/drm_output.cpp:60 #7 0x7f650d033560 in qDeleteAll(KWin::DrmOutput* const*, KWin::DrmOutput* const*) (begin=0x55a998560698, end=0x55a9985606a8) at /home/apol/devel/kde5/include/QtCore/qalgorithms.h:320 #8 0x7f650d02c3fe in qDeleteAll >(QVector const&) (c=...) at /home/apol/devel/kde5/include/QtCore/qalgorithms.h:328 #9 0x7f650d0266bb in KWin::DrmBackend::updateOutputs() (this=0x55a997a5ea40) at /home/apol/devel/frameworks/kwin/plugins/platforms/drm/drm_backend.cpp:522 #10 0x7f650d02852c in KWin::DrmBackend::openDrm()::$_2::operator()() const (this=0x55a997bc24c0) at /home/apol/devel/frameworks/kwin/plugins/platforms/drm/drm_backend.cpp:348 #11 0x7f650d0283b6 in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::DrmBackend::openDrm()::$_2>::call(KWin::DrmBackend::openDrm()::$_2&, void**) (f=..., arg=0x72f23c40) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:146 #12 0x7f650d028381 in QtPrivate::Functor::call, void>(KWin::DrmBackend::openDrm()::$_2&, void*, void**) (f=..., arg=0x72f23c40) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:256 #13 0x7f650d02832c in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x55a997bc24b0, r=0x55a997a5ea40, a=0x72f23c40, ret=0x0) at /home/apol/devel/kde5/include/QtCore/qobjectdefs_impl.h:443 #14 0x7f6512d95f06 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x72f23c40, r=0x55a997a5ea40, this=0x55a997bc24b0) at ../../include/QtCore/../../../../../devel/frameworks/qt5/qtbase/src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate(QObject*, int, void**) (sender=0x55a997bca310, signal_index=3, argv=argv@entry=0x72f23c40) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3886 #16 0x7f6512d8f260 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55a997bca310, m=m@entry=0x7f651302eb00 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x72f23c40) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qobject.cpp:3946 #17 0x7f6512d9933f in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x55a997bca310, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #18 0x7f6512d99b3b in QSocketNotifier::event(QEvent*) (this=0x55a997bca310, e=0x72f23d50) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qsocketnotifier.cpp:302 #19 0x7f651387111f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55a997bca310, e=0x72f23d50) at /home/apol/devel/frameworks/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3671 #20 0x7f6512d5fa3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a997bca310, event=0x72f23d50) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../../../../devel/frameworks/qt5/qtbase/src/corelib/thread/qthread_p.h:325 #21 0x7f6512db41eb in QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x55a997a3e330) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:304 #22 0x7f6512db464b in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at /home/apol/devel/frameworks/qt5/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:511 #2
[plasmashell] [Bug 411364] Text loses its opacity when fast switching applications categories
https://bugs.kde.org/show_bug.cgi?id=411364 --- Comment #3 from Andrey Kozlovskiy --- Can somebody confirm? Still have this issue on Plasma 5.19.2 Looks like 'to: 1.0' is missing on https://invent.kde.org/plasma/plasma-desktop/-/blob/master/applets/kickoff/package/contents/ui/ApplicationsView.qml#L162 (at least this fixes the issue for me). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423635] New: Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264
https://bugs.kde.org/show_bug.cgi?id=423635 Bug ID: 423635 Summary: Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264 Product: kdenlive Version: 20.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: vito...@gmail.com Target Milestone: --- SUMMARY The MP4 rendering format (H264 / AAC) states that the libx64 video codec is not supported. I use the Debian Bullseye version. O formato de renderização MP4 (H264/AAC) acusa que o codec de video libx64 não é suportado. Utilizo a versão Debian Bullseye. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423465] Wrong rendering when using "Destination Atop" blending mode
https://bugs.kde.org/show_bug.cgi?id=423465 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/401 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423602] kwin_wayland segmentation fault in std::__atomic_base::operator++ when using vlc
https://bugs.kde.org/show_bug.cgi?id=423602 --- Comment #1 from Matt Fagnani --- I've seen two more kwin_wayland segmentation faults when using Plasma 5.19.2, KF 5.71.0, Qt 5.14.2 while playing videos in vlc. The first such crash had the same trace as I reported here before. The second segmentation fault was in std::__atomic_base::load. Both traces involved QPointer::QPointer at /usr/include/qt5/QtCore/qpointer.h:62 operator() at /usr/src/debug/kwayland-server-5.19.2-1.fc33.x86_64/src/server/pointer_interface.cpp:241 When the mouse pointer is over the video in vlc without moving for a few seconds, the mouse pointer normally disappears. When the mouse is moved after the pointer disappeared, the mouse pointer reappeared. The problem might be related to this mouse pointer disappearing/appearing. Memory corruption might have led to invalid pointers involving the KWaylandServer::SurfaceInterface being passed to QPointer::QPointer. Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/libexec/st'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f97c432473e in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:741 warning: Source file is more recent than executable. 741 load(memory_order __m = memory_order_seq_cst) const noexcept [Current thread is 1 (Thread 0x7f97c473be00 (LWP 18029))] (gdb) thread apply all bt Thread 21 (Thread 0x7f9762a86680 (LWP 18109)): #0 0x7f97c3f2e31f in __GI___poll (fds=0x7f9754004630, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f97c1a6a1ce in g_main_context_poll (priority=, n_fds=1, fds=0x7f9754004630, timeout=, context=0x7f9754000c20) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f9754000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f97c1a6a303 in g_main_context_iteration (context=0x7f9754000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f97c44c5b73 in QEventDispatcherGlib::processEvents (this=0x7f9754000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f97c447891b in QEventLoop::exec (this=this@entry=0x7f9762a85be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f97c42e4427 in QThread::exec (this=this@entry=0x5601801df8b0) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f97c2fc77a9 in QQmlThreadPrivate::run (this=0x5601801df8b0) at qml/ftw/qqmlthread.cpp:155 #8 0x7f97c42e5690 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:342 #9 0x7f97c4f783f9 in start_thread (arg=0x7f9762a86680) at pthread_create.c:462 #10 0x7f97c3f393b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f974e346680 (LWP 22467)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x560180c037d0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560180c03780, cond=0x560180c037a8) at p--Type for more, q to quit, c to continue without paging--c thread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x560180c037a8, mutex=0x560180c03780) at pthread_cond_wait.c:638 #3 0x7f97acac12ab in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f97acac0d7b in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f97c4f783f9 in start_thread (arg=0x7f974e346680) at pthread_create.c:462 #6 0x7f97c3f393b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f9763fff680 (LWP 18105)): #0 0x7f97c3f2e31f in __GI___poll (fds=0x7f975c004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f97c1a6a1ce in g_main_context_poll (priority=, n_fds=1, fds=0x7f975c004e60, timeout=, context=0x7f975c000c20) at ../glib/gmain.c:4346 #2 g_main_context_iterate (context=context@entry=0x7f975c000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f97c1a6a303 in g_main_context_iteration (context=0x7f975c000c20, may_block=may_block@entry=1) at ../glib/gmain.c:4108 #4 0x7f97c44c5b73 in QEventDispatcherGlib::processEvents (this=0x7f975c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f97c447891b in QEventLoop::exec (this=this@entry=0x7f9763ffebe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f97c42e4427 in QThread::exec (this=this@entry=0x560180073040) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f97c2fc77a9 in QQmlThreadPrivate::run (this=0x560180073040) at qml/ftw/qqmlthread.cpp:155 #8 0x7f97c42e5690 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:342 #9 0x7f97c4f783f9 in start_thread (arg=0x7f9763fff680) at pthread_create.c:462 #10 0x7f97c3f393b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S
[systemsettings] [Bug 423634] New: System settings crash
https://bugs.kde.org/show_bug.cgi?id=423634 Bug ID: 423634 Summary: System settings crash Product: systemsettings Version: 5.19.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: paj...@tuta.io Target Milestone: --- Application: systemsettings5 (5.19.2) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-59-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: Nothing. just opened it. There is also problem with boot into GUI on computer startup. also i have problem to boot GUI on boot : I've found workaround. I have to login by tty then use startx command to run GUI. i have to do this on every boot-up. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7f9091da7801 in __GI_abort () at abort.c:79 #6 0x7f909256f68b in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7fff107e7b30, msg=msg@entry=0x7f9090d5eb6f "%s") at global/qlogging.cpp:893 #8 0x7f9090d5acc0 in QQuickWidgetPrivate::handleContextCreationFailure (this=this@entry=0x562d8a431070, format=..., isEs=isEs@entry=false) at qquickwidget.cpp:869 #9 0x7f9090d5b020 in QQuickWidgetPrivate::createContext (this=this@entry=0x562d8a431070) at qquickwidget.cpp:902 #10 0x7f9090d5d17e in QQuickWidget::resizeEvent (this=0x562d8ac94220, e=) at qquickwidget.cpp:1244 #11 0x7f9093943bde in QWidget::event (this=this@entry=0x562d8ac94220, event=event@entry=0x7fff107e8050) at kernel/qwidget.cpp:8823 #12 0x7f9090d5decb in QQuickWidget::event (this=0x562d8ac94220, e=0x7fff107e8050) at qquickwidget.cpp:1551 #13 0x7f90939029ac in QApplicationPrivate::notify_helper (this=this@entry=0x562d8a02a330, receiver=receiver@entry=0x562d8ac94220, e=e@entry=0x7fff107e8050) at kernel/qapplication.cpp:3685 #14 0x7f9093909bb0 in QApplication::notify (this=0x7fff107ea2a0, receiver=0x562d8ac94220, e=0x7fff107e8050) at kernel/qapplication.cpp:3431 #15 0x7f90927834a8 in QCoreApplication::notifyInternal2 (receiver=0x562d8ac94220, event=0x7fff107e8050) at kernel/qcoreapplication.cpp:1075 #16 0x7f909278367e in QCoreApplication::sendEvent (receiver=receiver@entry=0x562d8ac94220, event=event@entry=0x7fff107e8050) at kernel/qcoreapplication.cpp:1470 #17 0x7f909393bf76 in QWidgetPrivate::sendPendingMoveAndResizeEvents (this=this@entry=0x562d8a431070, recursive=recursive@entry=false, disableUpdates=, disableUpdates@entry=false) at kernel/qwidget.cpp:7727 #18 0x7f9093940303 in QWidgetPrivate::show_helper (this=this@entry=0x562d8a431070) at kernel/qwidget.cpp:7778 #19 0x7f9093943453 in QWidgetPrivate::setVisible (this=0x562d8a431070, visible=) at kernel/qwidget.cpp:8127 #20 0x7f9093940258 in QWidgetPrivate::showChildren (this=this@entry=0x562d8ac95410, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8197 #21 0x7f909394031f in QWidgetPrivate::show_helper (this=this@entry=0x562d8ac95410) at kernel/qwidget.cpp:7784 #22 0x7f9093943453 in QWidgetPrivate::setVisible (this=0x562d8ac95410, visible=) at kernel/qwidget.cpp:8127 #23 0x7f9093940258 in QWidgetPrivate::showChildren (this=this@entry=0x562d8a47ea20, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8197 #24 0x7f909394031f in QWidgetPrivate::show_helper (this=0x562d8a47ea20) at kernel/qwidget.cpp:7784 #25 0x7f909394012b in QWidgetPrivate::show_recursive (this=) at kernel/qwidget.cpp:7708 #26 0x7f9093940240 in QWidgetPrivate::showChildren (this=this@entry=0x562d8a37d3d0, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8195 #27 0x7f909394031f in QWidgetPrivate::show_helper (this=this@entry=0x562d8a37d3d0) at kernel/qwidget.cpp:7784 #28 0x7f9093943453 in QWidgetPrivate::setVisible (this=0x562d8a37d3d0, visible=) at kernel/qwidget.cpp:8127 #29 0x7f9093940258 in QWidgetPrivate::showChildren (this=this@entry=0x562d8a44fd50, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8197 #30 0x7f909394031f in QWidgetPrivate::show_helper (this=this@entry=0x562d8a44fd50) at kernel/qwidget.cpp:7784 #31 0x7f9093943453 in QWidgetPrivate::setVisible (this=0x562d8a44fd50, visible=) at kernel/qwidget.cpp:8127 #32 0x7f9093927ac7 in QStackedLayout::setCurrentIndex (this=0x562d8a357a20, index=1) at kernel/qstackedlayout.cpp:321 #33 0x7f9093927dd4 in QStackedLayout::setCurrentWidget (this=0x562d8a357a20, widget=widget@entry=0x562d8a37d5d0) at kernel/qstackedlayout.cpp:376 #34 0x7f9093aac121 in QStackedWidget::se
[frameworks-kio] [Bug 423412] Dolphin can't properly run script if there is space in the path
https://bugs.kde.org/show_bug.cgi?id=423412 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/69 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423633] can not access latte global settings
https://bugs.kde.org/show_bug.cgi?id=423633 --- Comment #1 from andresdor...@gmail.com --- this works on 0.9.11 by going into a docks settings and clicking on the latte logo. this same method doesn't work on the git either . something I should of added to the first post is that all this happened after I messed up my latte config and I did ```rm -rf latte*``` inside the config folder -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423633] New: can not access latte global settings
https://bugs.kde.org/show_bug.cgi?id=423633 Bug ID: 423633 Summary: can not access latte global settings Product: lattedock Version: git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andresdor...@gmail.com Target Milestone: --- SUMMARY I am unable to get to latte layout settings STEPS TO REPRODUCE 1. open latte dock 2. right click on a dock to get a configure latte option OBSERVED RESULT no, configure latte option EXPECTED RESULT for there to configure latte option Operating System: Arch Linux KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.6-12-tkg-pds OS Type: 64-bit Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #73 from sparkie --- SMS browse is working on S8+. You will need to enable side loading and uninstall the current version of KDE Connect. I still can not send messages from the SMS screen on my computer, but all of my messages loaded up. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423630] [Steam] Create Start Menu icon
https://bugs.kde.org/show_bug.cgi?id=423630 L. E. Segovia changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |wishlist OS|Other |Microsoft Windows Version|unspecified |4.3.0 Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423632] New: Segfault when scanning faces
https://bugs.kde.org/show_bug.cgi?id=423632 Bug ID: 423632 Summary: Segfault when scanning faces Product: digikam Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: toto...@yahoo.fr Target Milestone: --- Application: digikam (7.0.0-rc) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.4.2-gentoo x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Launching face detection scan I have this bug since Digikam v5, upgrade to v6 then v7-beta did not help The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef407bb5c0 (LWP 1210579))] Thread 44 (Thread 0x7fee3e4fe700 (LWP 1211906)): #0 0x7fef5ac27507 in getpid () at /lib64/libc.so.6 #1 0x7feeda20f7e9 in is_forked_child () at /var/tmp/portage/dev-libs/roct-thunk-interface-3.5.0/work/ROCT-Thunk-Interface-rocm-3.5.0/src/openclose.c:58 #2 0x7feeda20f842 in is_forked_child () at /var/tmp/portage/dev-libs/roct-thunk-interface-3.5.0/work/ROCT-Thunk-Interface-rocm-3.5.0/src/openclose.c:55 #3 0x7feeda20e449 in kmtIoctl (fd=44, request=request@entry=3222817548, arg=arg@entry=0x7fee3e4fd670) at /var/tmp/portage/dev-libs/roct-thunk-interface-3.5.0/work/ROCT-Thunk-Interface-rocm-3.5.0/src/libhsakmt.c:21 #4 0x7feeda2086fc in hsaKmtWaitOnMultipleEvents (Milliseconds=4294967294, WaitOnAll=false, NumEvents=, Events=0x7fee3e4fd8a0) at /var/tmp/portage/dev-libs/roct-thunk-interface-3.5.0/work/ROCT-Thunk-Interface-rocm-3.5.0/src/events.c:312 #5 hsaKmtWaitOnMultipleEvents (Events=0x7fee3e4fd8a0, NumEvents=2, WaitOnAll=, Milliseconds=4294967294) at /var/tmp/portage/dev-libs/roct-thunk-interface-3.5.0/work/ROCT-Thunk-Interface-rocm-3.5.0/src/events.c:286 #6 0x7fee840efeb1 in core::Signal::WaitAny(unsigned int, hsa_signal_s const*, hsa_signal_condition_t const*, long const*, unsigned long, hsa_wait_state_t, long*) () at /usr/lib64/libhsa-runtime64.so.1 #7 0x7fee840bb5bc in AMD::hsa_amd_signal_wait_any(unsigned int, hsa_signal_s*, hsa_signal_condition_t*, long*, unsigned long, hsa_wait_state_t, long*) () at /usr/lib64/libhsa-runtime64.so.1 #8 0x7fee840d7526 in core::Runtime::AsyncEventsLoop(void*) () at /usr/lib64/libhsa-runtime64.so.1 #9 0x7fee8405b387 in os::ThreadTrampoline(void*) () at /usr/lib64/libhsa-runtime64.so.1 #10 0x7fef54b00fa7 in start_thread () at /lib64/libpthread.so.0 #11 0x7fef5ac58d3f in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7fee3d0bd700 (LWP 1211905)): #0 0x7fef5ac53979 in syscall () at /lib64/libc.so.6 #1 0x7fef50b881ad in tbb::internal::futex_wait(void*, int) (comparand=2, futex=0x7feed8b05e2c) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/include/tbb/machine/linux_common.h:81 #2 tbb::internal::binary_semaphore::P() (this=0x7feed8b05e2c) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/semaphore.h:205 #3 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) (c=..., this=0x7feed8b05e20) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/../rml/server/thread_monitor.h:255 #4 tbb::internal::rml::private_worker::run() (this=0x7feed8b05e00) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/private_server.cpp:273 #5 0x7fef50b881e9 in tbb::internal::rml::private_worker::thread_routine(void*) (arg=) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/private_server.cpp:219 #6 0x7fef54b00fa7 in start_thread () at /lib64/libpthread.so.0 #7 0x7fef5ac58d3f in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7fee444f9700 (LWP 1211904)): #0 0x7fef5ac53979 in syscall () at /lib64/libc.so.6 #1 0x7fef50b881ad in tbb::internal::futex_wait(void*, int) (comparand=2, futex=0x7feed8b05f2c) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/include/tbb/machine/linux_common.h:81 #2 tbb::internal::binary_semaphore::P() (this=0x7feed8b05f2c) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/semaphore.h:205 #3 rml::internal::thread_monitor::commit_wait(rml::internal::thread_monitor::cookie&) (c=..., this=0x7feed8b05f20) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/../rml/server/thread_monitor.h:255 #4 tbb::internal::rml::private_worker::run() (this=0x7feed8b05f00) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/private_server.cpp:273 #5 0x7fef50b881e9 in tbb::internal::rml::private_worker::thread_routine(void*) (arg=) at /var/tmp/portage/dev-cpp/tbb-2019.8/work/tbb-2019_U8/src/tbb/private_server.cpp:2
[plasmashell] [Bug 423152] Plasma segmentation fault after boot up
https://bugs.kde.org/show_bug.cgi?id=423152 --- Comment #2 from just2fly --- Created attachment 129747 --> https://bugs.kde.org/attachment.cgi?id=129747&action=edit New crash information added by DrKonqi plasmashell (5.19.2) using Qt 5.14.2 - What I was doing when the application crashed: starting my system up as soon as it starts the menu taskpar and systray disappears and rePPERS TWICE THEN report bug option comes up -- Backtrace (Reduced): -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423152] Plasma segmentation fault after boot up
https://bugs.kde.org/show_bug.cgi?id=423152 just2fly changed: What|Removed |Added CC||joeflynn...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423148] Okular crashes every time when opening a random PDF in Dolphin
https://bugs.kde.org/show_bug.cgi?id=423148 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423148] Okular crashes every time when opening a random PDF in Dolphin
https://bugs.kde.org/show_bug.cgi?id=423148 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 394930] Dual monitor setup remembered correctly after reboot, but applied wrongly
https://bugs.kde.org/show_bug.cgi?id=394930 Adomas Jackevičius changed: What|Removed |Added CC||adomas@gmail.com --- Comment #4 from Adomas Jackevičius --- Happens on two out of three systems to me. 1) Arch Linux with Frameworks 5.71.0 and Plasma 5.19.2 - X11, nvidia binary, 2 monitor setup - not affected 2) Arch Linux with Frameworks 5.71.0 and Plasma 5.19.2 - X11, intel iGPU, 3 monitor setup - sometimes resets the arrangement 3) Void Linux with Frameworks 5.71.0 and Plasma 5.19.2 - X11, nouveau nvidia, 2 monitor setup - on every boot I need to rearrange the screens as it is reset -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 423603] Some app system tray context menus render in the wrong location
https://bugs.kde.org/show_bug.cgi?id=423603 Adomas Jackevičius changed: What|Removed |Added CC||adomas@gmail.com --- Comment #1 from Adomas Jackevičius --- Can't reproduce the issue with latest versions: Arch Linux KDE Frameworks 5.71.0 KDE Plasma 5.19.2 Qt 5.15.0 nextcloud-client 2.6.4 Tried with and without scaling, as at first look it seemed to be scaling related. Also tried with single and with multi monitor setups. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423631] New: can't save project
https://bugs.kde.org/show_bug.cgi?id=423631 Bug ID: 423631 Summary: can't save project Product: kdenlive Version: 20.04.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: lucanreisofic...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. I made a small project to test, and when I tried to save, nothing happened when click on "save as". 2. OBSERVED RESULT Not open a box to name, select format or folder to save. EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu 18.04 ADDITIONAL INFORMATION I made a lot of updates but this problem still remains -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423618] Slideshow controls are off screen on smaller screen with dual screen setup
https://bugs.kde.org/show_bug.cgi?id=423618 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Maik Qualmann --- Yes, with the arrangement on the bottom edges, I can reproduce it too. Maik -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 413164] Please tag a new release
https://bugs.kde.org/show_bug.cgi?id=413164 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com --- Comment #1 from andreas.sturmlech...@gmail.com --- +1 considering recent CVEs. -- You are receiving this mail because: You are watching all bug changes.
[ktuberling] [Bug 207162] I can`t save my project. App crash after open kde4 (not native, like in system settings!) save dialog
https://bugs.kde.org/show_bug.cgi?id=207162 Lucan changed: What|Removed |Added CC||lucanreisofic...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422755] Memory leak in plasmashell on opening activity manager sidebar repeatedly
https://bugs.kde.org/show_bug.cgi?id=422755 2012g...@web.de changed: What|Removed |Added CC||2012g...@web.de -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423260] Changing graph title and pressing cancel in the dialog changes the name anyway
https://bugs.kde.org/show_bug.cgi?id=423260 gr...@kde.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||gr...@kde.org --- Comment #1 from gr...@kde.org --- This bug report needs more details: - does this apply to ksysguard the application, or to widgets? - what sequence of actions do you take to get to "changing graph title"? That said, I end up with being *un*able to change the title of a widget after changing it once, but that's a different bug report entirely. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423630] New: [Steam] Create Start Menu icon
https://bugs.kde.org/show_bug.cgi?id=423630 Bug ID: 423630 Summary: [Steam] Create Start Menu icon Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kamika...@web.de Target Milestone: --- Since Krita from Steam runs just fine without Steam running and Steam is at most only capable to create an icon on the desktop, Krita from Steam should have an option to create a Start Menu icon. Under Windows that would be a link in "%appdata%\Microsoft\Windows\Start Menu\Programs" to "C:\Program Files (x86)\Steam\steamapps\common\Krita\krita\bin\krita.exe" (or wherever the Steam library is). Not sure what the best way under Linux would be. I suggest a checkbox in Settings > General that adds or removes the shortcut. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 403090] info:tooltip shown not neat
https://bugs.kde.org/show_bug.cgi?id=403090 --- Comment #9 from gr...@kde.org --- I should have been more clear: - the bug is not in ksysguard - the bug is not in the translations of ksysguard - the bug is in the translations inside the k18n framework svn://anonsvn.kde.org/home/kde/trunk/l10n-kf5/id/messages/ki18n/ki18n5.po has the bad translation. This is wrong: ``` #. i18n: KUIT pattern, see the comment to the first of these entries above. #: kuitmarkup.cpp:764 #, kde-format msgctxt "tag-format-pattern rich" msgid "%1" msgstr "%1" ``` It should be: ``` #. i18n: KUIT pattern, see the comment to the first of these entries above. #: kuitmarkup.cpp:764 #, kde-format msgctxt "tag-format-pattern rich" msgid "%1" msgstr "%1" ``` That is, do not change to in the translation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423629] New: no longer able to force headphones output
https://bugs.kde.org/show_bug.cgi?id=423629 Bug ID: 423629 Summary: no longer able to force headphones output Product: systemsettings Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: now...@gmail.com Reporter: paol...@dmf.unicatt.it CC: plasma-b...@kde.org Target Milestone: --- SUMMARY with version 5.17 audio settings presented a checkbox that allowed to force use of headphones (or internal speakers) independently of sensing insertion of audio jack. This was useful for me since I have a defective port. SOFTWARE/OS VERSIONS Linux fedora 32 distribution Linux/KDE Plasma: KDE Plasma Version: 5.18 KDE Frameworks Version: kf5, version 5.70 Qt Version: qt5, version 5.14 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423628] New: systemsettings5: Applications menu crashes systemsettings
https://bugs.kde.org/show_bug.cgi?id=423628 Bug ID: 423628 Summary: systemsettings5: Applications menu crashes systemsettings Product: systemsettings Version: 5.19.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: strypst...@posteo.net Target Milestone: --- SUMMARY Whenever I go to "Applications" in the systemsettings, systemsettings crashes. STEPS TO REPRODUCE 1. go to -> systemsettings 2. -> Personalization 3. -> applications OBSERVED RESULT systemsettings crashes. EXPECTED RESULT Getting access to the applications submenu SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.0 ADDITIONAL INFORMATION Executable: systemsettings5 PID: 2412 Signal: Segmentation fault (11) Time: 6/28/20 9:46:44 PM CEST -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #6 from Szőts Ákos --- Nice catch, debugging was on; turned it off. I'll recompress its default .zst (ZStandard) into .xz and upload it into the aforementioned mega.nz directory (just to have everything in one place). I'll try to enable parallel decompression ability so you can use -T0 for unxz. I'll notify you as soon as I've finished. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #5 from Daniel Vrátil --- Could you please check that you have the "Debugger" disabled in Akonadi Console? When the "Debugger" option is enabled, it causes the Server to generate a lots of debugging string data and send them over dbus. The "Debugger" option gets persisted in Akonadi Server for now, so even if you close Akonadi Console, the Akonadi Server will continue generating the data. I'll adjust the code to not persist the debugger accross Akonadi restarts. Anyway, that's what I see in the 20.04 screenshots, but that's just lots of temporary allocations, not the leaks. The leaks visible in the 18.04 heaptrack are related to QueryCache, which has been overhauled in 20.04. So I suspect what you are seeing on 18.04 is already fixed, and what you are seeing in 20.04 is either related to the Debugger being enabled and/or the real culprit is not shown on the screenshots. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 181437] Detailed view: for better clarity, rolling over an element should highlight the whole line, not just the name of the element
https://bugs.kde.org/show_bug.cgi?id=181437 Andrey Kozlovskiy changed: What|Removed |Added CC||andronon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423618] Slideshow controls are off screen on smaller screen with dual screen setup
https://bugs.kde.org/show_bug.cgi?id=423618 --- Comment #2 from Jens --- The images are not cropped. Just the buttons. I just played a bit with the screen config and it seems that this only happens if the screens are next to each other, the primary screen has the smaller (!) resolution of both, and the bottom (!) of both screens is aligned (no the top). If I arrange the screens to have the top aligned, Digikam's display is correct. Also with single screen config, in any case it works fine. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 Alexander Lohnau changed: What|Removed |Added Assignee|k...@privat.broulik.de |alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 422191] [ABI break] KAccountsDPlugin changes its API without bumping the libkaccount SONAME
https://bugs.kde.org/show_bug.cgi?id=422191 Nicolas Fella changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Nicolas Fella --- Merge request: https://invent.kde.org/network/kaccounts-integration/-/merge_requests/2 -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 422191] [ABI break] KAccountsDPlugin changes its API without bumping the libkaccount SONAME
https://bugs.kde.org/show_bug.cgi?id=422191 Nicolas Fella changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/kaccounts-integration/c ||ommit/839bce4ba5399fd5924f7 ||316f8df402a86cb4262 --- Comment #3 from Nicolas Fella --- Git commit 839bce4ba5399fd5924f7316f8df402a86cb4262 by Nicolas Fella. Committed on 28/06/2020 at 19:00. Pushed by nicolasfella into branch 'sobump'. Bump libkaccounts so version 27487ab9276ca3a9b6ef4e8145b2279b5e38cd25 broke ABI, increase the so version to reflect that M +1-1CMakeLists.txt https://invent.kde.org/network/kaccounts-integration/commit/839bce4ba5399fd5924f7316f8df402a86cb4262 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])
https://bugs.kde.org/show_bug.cgi?id=423575 --- Comment #4 from Daniel Vrátil --- I take it back, it would still be useful to get the 20.04 heaptrack data, from the screenshots it seems to have better quality. You could try changing the compression algo (use .xz instead of .gz for instance). If you need some place where to upload such a huge file, I can give you upload access directly to my server. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423627] New: Installation of KIO fail
https://bugs.kde.org/show_bug.cgi?id=423627 Bug ID: 423627 Summary: Installation of KIO fail Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: gear...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-106-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: clicked Discover link to install KIO and Discover crash every time The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0835437800 (LWP 30937))] Thread 10 (Thread 0x7f07e9457700 (LWP 30957)): #0 0x7f08309cb839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f08310db775 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f082e90df96 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7f082e90e835 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f082e8ea8cc in QSslSocket::startClientEncryption() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f082e8eb578 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7f082e8f3379 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f08312f1555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f082e8bdf09 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f082e8c0e78 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f082e8d17ed in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f08335bc83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f08335c4104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f08312c28d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f083131c4ed in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f082b13c417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f082b13c650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f082b13c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f083131b8ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f08312c090a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f08310df23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f08310e417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f082d2976db in start_thread (arg=0x7f07e9457700) at pthread_create.c:463 #23 0x7f08309d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f07ebb2f700 (LWP 30946)): #0 0x7f082d29d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f07e4043500) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f082d29d9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f07e40434b0, cond=0x7f07e40434d8) at pthread_cond_wait.c:502 #2 0x7f082d29d9f3 in __pthread_cond_wait (cond=0x7f07e40434d8, mutex=0x7f07e40434b0) at pthread_cond_wait.c:655 #3 0x7f08310e55ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f08310ddc1b in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f08312f1868 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f082e915df2 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f082e916d4c in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f08312f1555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f082e914eb2 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f082e87623f in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f082e8776cc in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f08312f1555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f082e8e9dd2 in QSslSocket::preSharedKeyAuthenticationRequired(QSslPreSharedKeyAuthenticator*) () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #14 0x7f082e90dcdc in () at /usr/lib/x86_64-l
[plasmashell] [Bug 423626] kdeinit5 failed when opening catalog active in torrent-client
https://bugs.kde.org/show_bug.cgi?id=423626 --- Comment #1 from antailyaq...@disroot.org --- Created attachment 129746 --> https://bugs.kde.org/attachment.cgi?id=129746&action=edit problem repeats after disabling qbittorrent Update: the problem isn't connected with qbittorrent, the folder fails itself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423626] New: kdeinit5 failed when opening catalog active in torrent-client
https://bugs.kde.org/show_bug.cgi?id=423626 Bug ID: 423626 Summary: kdeinit5 failed when opening catalog active in torrent-client Product: plasmashell Version: 5.19.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: antailyaq...@disroot.org Target Milestone: 1.0 Created attachment 129745 --> https://bugs.kde.org/attachment.cgi?id=129745&action=edit kdeinit5 failed SUMMARY kdeinit5 failed several times (from 4 to 8-10) if I open the folder in NTFS disk while torrent-client (qbittorrent latest) downloading this folder. STEPS TO REPRODUCE 1. Download folder in qbittorrent 2. Open folder OBSERVED RESULT kdeinit failed several times EXPECTED RESULT folder open normally. Works normally in 5.19.1 and earlier. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.2 (available in About System) KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION qbittorrent client 4.0.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423625] New: Clipboard is not working when clipboard tray icon disabled
https://bugs.kde.org/show_bug.cgi?id=423625 Bug ID: 423625 Summary: Clipboard is not working when clipboard tray icon disabled Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: galdra...@bk.ru Target Milestone: 1.0 OBSERVED RESULT Clipboard is not working when clipboard tray icon disabled EXPECTED RESULT Clipboard service must be always running independently on hidden/visible tray icon. I never use clipboard icon for many years. I assume most of peaple also never use it. But clipboard service is useful and must be running. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423233] Can't put audio into video track
https://bugs.kde.org/show_bug.cgi?id=423233 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #2 from emohr --- Put the waveform effect on the master effect and it will work. See here https://kdenlive.org/en/2020/04/kdenlive-20-04-is-out/ " Legacy features" -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 423624] New: Kontact (Kmail) crashes while marking bunch of emails as Read
https://bugs.kde.org/show_bug.cgi?id=423624 Bug ID: 423624 Summary: Kontact (Kmail) crashes while marking bunch of emails as Read Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: xandr...@protonmail.com Target Milestone: --- Application: kontact (5.13.3 (19.12.3)) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-39-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: Some folder had unread emails. I opened that folder, selected all emails and from a pop up manu selected "Mark all as read". -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f669968af00 (LWP 467483))] Thread 24 (Thread 0x7f65f7fff700 (LWP 467609)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f65f7ffe4a0, clockid=, expected=0, futex_word=0x7f65f7ffe5e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f65f7ffe4a0, clockid=, mutex=0x7f65f7ffe598, cond=0x7f65f7ffe5c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f65f7ffe5c0, mutex=0x7f65f7ffe598, abstime=0x7f65f7ffe4a0) at pthread_cond_wait.c:656 #3 0x7f66a60b9b2e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f66a60ba51f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f66a60ba615 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f66a607bda6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f66a607ec48 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f66a607eef8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f66a60bcb63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f66abb16609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f66acb2b103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f6611ec4700 (LWP 467608)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f6611ec34a0, clockid=, expected=0, futex_word=0x7f6611ec35e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f6611ec34a0, clockid=, mutex=0x7f6611ec3598, cond=0x7f6611ec35c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f6611ec35c0, mutex=0x7f6611ec3598, abstime=0x7f6611ec34a0) at pthread_cond_wait.c:656 #3 0x7f66a60b9b2e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f66a60ba51f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f66a60ba615 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f66a607bda6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f66a607ec48 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f66a607eef8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f66a60bcb63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f66abb16609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f66acb2b103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f66126c5700 (LWP 467607)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f66126c44a0, clockid=, expected=0, futex_word=0x7f66126c45e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f66126c44a0, clockid=, mutex=0x7f66126c4598, cond=0x7f66126c45c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f66126c45c0, mutex=0x7f66126c4598, abstime=0x7f66126c44a0) at pthread_cond_wait.c:656 #3 0x7f66a60b9b2e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f66a60ba51f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f66a60ba615 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f66a607bda6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f66a607ec48 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f66a607eef8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f66a60bcb63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f66abb16609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f66acb2b103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f6683fff700 (LWP 467604)): #0 0x7f66ab1cb368 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f66ab17dbd9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.
[kdenlive] [Bug 423208] Crash not able to recover
https://bugs.kde.org/show_bug.cgi?id=423208 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #3 from emohr --- Please update Ubuntu to 20.04 long term. It could be that you have incompatibility with QT. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 423491] Yakuake sometimes crashing when closing sessions
https://bugs.kde.org/show_bug.cgi?id=423491 Maximilian Schiller changed: What|Removed |Added Resolution|--- |DUPLICATE CC||manim...@outlook.de Status|REPORTED|RESOLVED --- Comment #1 from Maximilian Schiller --- *** This bug has been marked as a duplicate of bug 415762 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421565] WARNING – DANGEROUS : kdenlive creates broken archive files
https://bugs.kde.org/show_bug.cgi?id=421565 --- Comment #3 from had...@danisch.de --- Well, there's several revisions of tar to overcome this problem, but I don't think tar is the appropriate format for this task here, owners and permissions are not really useful here. It might be an option to use zip instead. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Maximilian Schiller changed: What|Removed |Added CC||raimund.macha...@rm-it.at --- Comment #32 from Maximilian Schiller --- *** Bug 423491 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #7 from Maximilian Schiller --- (In reply to Paul Brown from comment #6) Thank you for being this detailed in your bug report. Did you try removing you yakuakerc (Should be under ~/.config/)? If not please try that (but keep a backup of it). The snap version probably doesn't contain Konsole but that's unfortunately something the snap packager did wrong. The next step would be to either manually build yakuake with debug symbols or use a slightly modified version of the yakuake-git AUR package (since you are running Manjaro). If you need help with that I and others who can help are usually in the #yakuake:kde.org matrix channel. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413709] krunner searches for the text suggested by auto-completion before actually accepting the suggestion
https://bugs.kde.org/show_bug.cgi?id=413709 --- Comment #4 from Alexander Lohnau --- >If so, it could function as some kind of workaround I guess. Yes, this was the intention. Also because these bugs are related I thought it is a good idea to keep you up to date :-). >I'm in no way against offering auto-completion, just against suggestions being >automatically "accepted" and >searched for without user confirmation by pressing Tab (or right arrow maybe). This was clear to me and the suggestion sums up the concept of the fish shell completion pretty well. There you have the suggestion as a grey text and have to press → to apply the suggestion. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423570] GoPro Hero 8 Black H.264 + HEVC files will not import into project
https://bugs.kde.org/show_bug.cgi?id=423570 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #2 from emohr --- This is a bug in MLT. Please try with AppImage 19.12.3 to see if it's happened there as well. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420474] Can't connect to receiving imap server
https://bugs.kde.org/show_bug.cgi?id=420474 --- Comment #2 from Papadakos Panagiotis --- Hi Damian, can you send emails using the problematic account? In my case, the problem appears only while receiving emails. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423613] Adding 2 videos to Trek freezes.
https://bugs.kde.org/show_bug.cgi?id=423613 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Flags||timeline_corruption+ Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net --- Comment #3 from emohr --- Please try with the current Kdenlive AppImage version 20.04.1b to see if there are any packaging issues https://files.kde.org/kdenlive/release/ If the problem/issue doesn't occur when using the AppImage, then it's your configuration or packaging. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 418358] Tabs action don't work as expacted in particular situation
https://bugs.kde.org/show_bug.cgi?id=418358 Nikita Sirgienko changed: What|Removed |Added Latest Commit||afb5d04bd6787c81deae918b60b ||971425f8ded40 Resolution|--- |FIXED Version Fixed In||20.08 Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
