[digikam] [Bug 402021] face recognition not working
https://bugs.kde.org/show_bug.cgi?id=402021 --- Comment #4 from achatssur...@yahoo.fr --- Hello Thank you for your support I Will test this new version when i Will cime jack to my home. I Will give you a feedback. Laurent -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 415499] Cannot build on latest Ubuntu
https://bugs.kde.org/show_bug.cgi?id=415499 Alexander Potashev changed: What|Removed |Added Latest Commit||https://commits.kde.org/kti ||metracker/202c072dc5194b4ed ||cd9ee52c8db91ce93e82c82 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Alexander Potashev --- Git commit 202c072dc5194b4edcd9ee52c8db91ce93e82c82 by Alexander Potashev. Committed on 24/12/2019 at 06:20. Pushed by aspotashev into branch 'master'. Fix build with pre-KF5 versions of KCalendarCore M +1-3CMakeLists.txt M +1-1src/export/csvhistory.cpp M +9-9src/file/filecalendar.cpp M +7-7src/file/filecalendar.h M +9-8src/file/icalformatkio.cpp M +4-4src/file/icalformatkio.h M +1-1src/ktimetrackerutility.cpp M +2-2src/ktimetrackerutility.h M +2-2src/model/event.cpp M +3-3src/model/event.h M +3-3src/model/eventsmodel.cpp M +2-2src/model/eventsmodel.h M +2-2src/model/projectmodel.cpp M +6-6src/model/task.cpp M +4-4src/model/task.h M +6-6src/tests/storagetest.cpp M +1-1src/timetrackerstorage.cpp M +3-3src/timetrackerstorage.h https://commits.kde.org/ktimetracker/202c072dc5194b4edcd9ee52c8db91ce93e82c82 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415448] Proxy error with Image Sequence
https://bugs.kde.org/show_bug.cgi?id=415448 --- Comment #3 from Jean-Baptiste Mardelle --- Yes we have a daily AppImage build for the master branch that can be used to check if bugs have been fixed. Wait gor todays build (around 13h30 CET) and get it here: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ Just download the file, make it executable and run it. Feedback welcome -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415502] Searching spinner is blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=415502 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- That is what is fixed in https://invent.kde.org/kde/okular/merge_requests/71, right? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 398460] Screen hotplug not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=398460 --- 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.
[kwin] [Bug 414317] Crash in Workspace::clientArea after reboot
https://bugs.kde.org/show_bug.cgi?id=414317 --- Comment #6 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.
[kate] [Bug 415384] LaTeX braces matching in \input is off
https://bugs.kde.org/show_bug.cgi?id=415384 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #3 from Nibaldo G. --- Fixed in KDE Frameworks 5.66 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415384] LaTeX braces matching in \input is off
https://bugs.kde.org/show_bug.cgi?id=415384 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.66.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415514] Feature Request: Include Balance Transfers in Budget
https://bugs.kde.org/show_bug.cgi?id=415514 Levi Neely changed: What|Removed |Added CC||lne...@sdf.lonestar.org -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415514] New: Feature Request: Include Balance Transfers in Budget
https://bugs.kde.org/show_bug.cgi?id=415514 Bug ID: 415514 Summary: Feature Request: Include Balance Transfers in Budget Product: kmymoney Version: 5.0.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: lne...@sdf.lonestar.org Target Milestone: --- SUMMARY I want to budget balance transfers. RATIONALE One of my financial goals is debt elimination, so I keep detailed track of my loan, mortgage, and credit card balances. For efficiency, when I make payments to my these accounts, I track them as split balance transfers rather than expenses. If I'm not able to track these transactions in the budget as if they were expenses, then I do not have a useful budget because it is incomplete. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.16-300.fc31.x86_64 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415477] Drag and drop files left of the tree view, dropes it into the non highlighted subfolder of the same line
https://bugs.kde.org/show_bug.cgi?id=415477 --- Comment #1 from Nate Graham --- Sorry, I'm having a hard time understanding the issue. Do you think you could attach a screen recording, maybe? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415492] Plasma crashes after login with any user
https://bugs.kde.org/show_bug.cgi?id=415492 --- Comment #3 from ano...@protonmail.ch --- (In reply to David Edmundson from comment #2) > Please check your locale is set correctly Yes! I deleted ~/.config/plasma-locale-settings.sh, in which the values were different from /etc/locale.conf, restarted sddm, the problem was solved. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 414854] Ark's overwrite dialog shows for both a size of "0 B" instead of real sizes
https://bugs.kde.org/show_bug.cgi?id=414854 Nate Graham changed: What|Removed |Added CC||kdelibs-b...@kde.org Product|ark |frameworks-kio Component|general |Overwrite dialog Assignee|elvis.angelac...@kde.org|fa...@kde.org Version|19.12.0 |5.65.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415448] Proxy error with Image Sequence
https://bugs.kde.org/show_bug.cgi?id=415448 --- Comment #2 from tonton --- Wow thanks that s was quick! Is there a build somewhere to try the commit? I don't have any experience to build it myself but I can try if there is not! Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415472] The software was working fine. But when I opened it today, the UI was completly distorted or unusable. Some kind of crash.
https://bugs.kde.org/show_bug.cgi?id=415472 --- Comment #2 from varun --- (In reply to emohr from comment #1) > Your Intel graphic card driver was updated. Move the mouse to the top. The > menus are showing up. Try to reach settings -> openGL backend -> enable > OpenGLES. Restart Kdenlive. This should solve your Intel graphic driver > issue. Maybe this statement helps: > https://forum.kde.org/viewtopic.php?f=265=161309#p425882 Thanks. This solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415513] New: Falkon crashes after disabling Hello Python (Hola Python) extension
https://bugs.kde.org/show_bug.cgi?id=415513 Bug ID: 415513 Summary: Falkon crashes after disabling Hello Python (Hola Python) extension Product: Falkon Version: 3.1.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: now...@gmail.com Reporter: gens...@disroot.org Target Milestone: --- Application: falkon (3.1.0) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.4.5-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Tried to disable the "Hello Python" extension - Custom settings of the application: "Hello Python"/"Hola Python" was enabled. Adblock and GreaseMonkey were too. Also, Falkons 2/3 of the time fails to launch, giving this in the logs: Icon theme "Numix-Circle" not found. Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/8x8/legacy/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/16x16/legacy/" Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/16x16/ui/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/22x22/legacy/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/24x24/legacy/" Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/24x24/ui/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/32x32/legacy/" Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/32x32/ui/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/48x48/legacy/" Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/48x48/ui/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/256x256/legacy/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/512x512/legacy/" Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/scalable/legacy/" Invalid Context= "UI" line for icon theme: "/usr/share/icons/Adwaita/scalable/ui/" (I have changed themes on KDE previously) The crash can be reproduced every time. -- Backtrace: Application: Falkon (falkon), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f830134db40 (LWP 1319571))] Thread 24 (Thread 0x7f82956a8700 (LWP 1319613)): #0 0x7f83128ca9ef in poll () at /usr/lib/libc.so.6 #1 0x7f83099f9120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f83099f91f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f8312e83cc0 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f8312e2a39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f8312c4fe62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f830ae93249 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f8312c50fd6 in () at /usr/lib/libQt5Core.so.5 #8 0x7f830a2e44cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f83128d52d3 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f8296bfd700 (LWP 1319610)): #0 0x7f830a2eac45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f830df5658c in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x in () Thread 22 (Thread 0x7f82977fe700 (LWP 1319599)): #0 0x7f830a2eac45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f830df5658c in () at /usr/lib/libQt5WebEngineCore.so.5 #2 0x in () Thread 21 (Thread 0x7f8297fff700 (LWP 1319598)): #0 0x7f83128d560e in epoll_wait () at /usr/lib/libc.so.6 #1 0x7f830915087b in () at /usr/lib/libevent-2.1.so.7 #2 0x7f8309146915 in event_base_loop () at /usr/lib/libevent-2.1.so.7 #3 0x7f830df5b03a in () at /usr/lib/libQt5WebEngineCore.so.5 #4 0x00010077007c in () #5 0x7f8297ffe8d0 in () #6 0x7f8297ffe8c8 in () #7 0x00049436039c in () #8 0x0008 in () #9 0x01c9bfd1 in () #10 0x001d in () #11 0x000f3e91 in () #12 0x7f8297ffea30 in () #13 0x564c3b308f60 in () #14 0x7fff in () #15 0x0001 in () #16 0x7f8297ffe9a8 in () #17 0x7f8297ffea30 in () #18 0x7f8297ffe950 in () #19 0x7f830deff04f in () at /usr/lib/libQt5WebEngineCore.so.5 #20 0x7f8297ffe9a8 in () #21 0x7fff in () #22 0x7f8297ffe950 in () #23 0x7f8297ffea30 in () #24 0x7fff in () #25 0x7f8297ffe9a0 in () #26 0x7f8297ffea10 in () #27 0x7f830dee29c9 in () at /usr/lib/libQt5WebEngineCore.so.5 #28 0x0077007c in () #29 0x005b006e in () #30 0x7f82c80c2778 in () #31 0x in () Thread 20 (Thread
[krusader] [Bug 415512] New: Krusader fails to copy files to "full" btrfs filesystem but with enough unallocated space
https://bugs.kde.org/show_bug.cgi?id=415512 Bug ID: 415512 Summary: Krusader fails to copy files to "full" btrfs filesystem but with enough unallocated space Product: krusader Version: 2.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: disk-usage Assignee: krusader-bugs-n...@kde.org Reporter: linux2...@plntyk.name CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY Krusader fails to copy file to a btrfs filesystem that reports 0 byte free STEPS TO REPRODUCE 1. use a btrfs filesystem until metablocks are full on a large disk (example: 8 terabyte filesystem) - it reports 0 bytes free 2. try to copy a file with Krusader that fits on the disk (smaller than unallocated chunks on btrfs) OBSERVED RESULT copy fails with popup error message EXPECTED RESULT copy is successful SOFTWARE/OS VERSIONS Linux: Kernel 5.4.6 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION - Copying files with "cp" on commandline is successful - btrfs fi usage shows enough unallocated space - this happened twice on a large disk (8 terabyte) - once at ~4TB unallocated space and now at "almost full" - Dolphin fails to copy to that btrfs filesystem too btrfs fi usage output: Overall: Device size: 7.28TiB Device allocated: 7.13TiB Device unallocated: 148.00GiB Device missing:7.28TiB Used: 7.13TiB Free (estimated):153.85GiB (min: 79.85GiB) Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 512.00MiB (used: 0.00B) Data,single: Size:7.12TiB, Used:7.11TiB (99.92%) Metadata,DUP: Size:8.00GiB, Used:7.78GiB (97.27%) System,DUP: Size:8.00MiB, Used:784.00KiB (9.57%) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415511] New: System settings crash
https://bugs.kde.org/show_bug.cgi?id=415511 Bug ID: 415511 Summary: System settings crash Product: systemsettings Version: 5.17.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ian.cass...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.4) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Exploring System Settings. One window was open. No applications were running. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a801c0800 (LWP 1262))] Thread 9 (Thread 0x7f6a2bd8c700 (LWP 1282)): #0 0x7f6a7b6eabf9 in __GI___poll (fds=0x7f6a24004860, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a74d9f5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a74d9f6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a7c03db9b in QEventDispatcherGlib::processEvents (this=0x7f6a24000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6a7bfde06a in QEventLoop::exec (this=this@entry=0x7f6a2bd8bd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f6a7bdf93aa in QThread::exec (this=this@entry=0x55e748325420) at thread/qthread.cpp:531 #6 0x7f6a79b9c815 in QQmlThreadPrivate::run (this=0x55e748325420) at qml/ftw/qqmlthread.cpp:152 #7 0x7f6a7bdfab52 in QThreadPrivate::start (arg=0x55e748325420) at thread/qthread_unix.cpp:360 #8 0x7f6a7715e6db in start_thread (arg=0x7f6a2bd8c700) at pthread_create.c:463 #9 0x7f6a7b6f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f6a39679700 (LWP 1280)): #0 0x7f6a74de5664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6a74d9e4b7 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a74d9f485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a74d9f6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a7c03db9b in QEventDispatcherGlib::processEvents (this=0x7f6a3412c440, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f6a7bfde06a in QEventLoop::exec (this=this@entry=0x7f6a39678d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f6a7bdf93aa in QThread::exec (this=this@entry=0x55e746f0d7b0) at thread/qthread.cpp:531 #7 0x7f6a79b9c815 in QQmlThreadPrivate::run (this=0x55e746f0d7b0) at qml/ftw/qqmlthread.cpp:152 #8 0x7f6a7bdfab52 in QThreadPrivate::start (arg=0x55e746f0d7b0) at thread/qthread_unix.cpp:360 #9 0x7f6a7715e6db in start_thread (arg=0x7f6a39679700) at pthread_create.c:463 #10 0x7f6a7b6f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f6a41522700 (LWP 1272)): #0 0x7f6a7b6eabf9 in __GI___poll (fds=0x7f6a3c003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a74d9f5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a74d9f6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a7c03db9b in QEventDispatcherGlib::processEvents (this=0x7f6a3c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f6a7bfde06a in QEventLoop::exec (this=this@entry=0x7f6a41521d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f6a7bdf93aa in QThread::exec (this=this@entry=0x55e746584830) at thread/qthread.cpp:531 #6 0x7f6a79b9c815 in QQmlThreadPrivate::run (this=0x55e746584830) at qml/ftw/qqmlthread.cpp:152 #7 0x7f6a7bdfab52 in QThreadPrivate::start (arg=0x55e746584830) at thread/qthread_unix.cpp:360 #8 0x7f6a7715e6db in start_thread (arg=0x7f6a41522700) at pthread_create.c:463 #9 0x7f6a7b6f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6a49f6a700 (LWP 1270)): #0 0x7f6a7b6e60b4 in __GI___libc_read (fd=23, buf=0x7f6a49f69b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f6a74de42d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a74d9f0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a74d9f570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a74d9f6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a7c03db9b in QEventDispatcherGlib::processEvents (this=0x7f6a44000b20,
[ktimetracker] [Bug 415499] Cannot build on latest Ubuntu
https://bugs.kde.org/show_bug.cgi?id=415499 Alexander Potashev changed: What|Removed |Added Summary|Some instructions for |Cannot build on latest |building KTimeTracker...|Ubuntu |would be good! | -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 414149] Ark crash on close while loading archive
https://bugs.kde.org/show_bug.cgi?id=414149 jimbo1qaz changed: What|Removed |Added CC||jimbo1...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 415499] Some instructions for building KTimeTracker... would be good!
https://bugs.kde.org/show_bug.cgi?id=415499 --- Comment #2 from Alexander Potashev --- Thanks for the feedback on the blog! Should be fixed now. The current version of KTimeTracker needs at least KCalendarCore-5.63.0, thus the building error on latest Ubuntu as it only ships KF5.62.0. Will try to fix it, should be easy. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 415510] New: "terminal Options" dropdown in KOpenWith should hide when both options are hidden too
https://bugs.kde.org/show_bug.cgi?id=415510 Bug ID: 415510 Summary: "terminal Options" dropdown in KOpenWith should hide when both options are hidden too Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: bluescreenaven...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 124681 --> https://bugs.kde.org/attachment.cgi?id=124681=edit Screenshot of KOpenWith SUMMARY STEPS TO REPRODUCE This is how I call a KOpenWith dialog right now, a patch to kde-cli-tool setting + dlg.hideNoCloseOnExit(); + dlg.hideRunInTerminal(); OBSERVED RESULT Note the "Terminal Options" dropdown still shows "Terminal Options" even though it is empty. I could not figure out a way to hide it 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.
[plasma-nm] [Bug 415509] New: autoconnect not set in nm configuration file
https://bugs.kde.org/show_bug.cgi?id=415509 Bug ID: 415509 Summary: autoconnect not set in nm configuration file Product: plasma-nm Version: 5.17.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: p...@free.fr Target Milestone: --- SUMMARY Connection manager does not put the option "autoconnect=true" in the configuration file of nm for a LAN cabled interface when we want an automated connexion of the interface at boot. If we unselect the option "automatic connection with priority", then connection manager removes the "autoconnect-priority=n" and put "autoconnect=false" in the "/etc/NetworkManager/system-connections/LAN.nmconnection" configuration file If we select the option "automatic connection with priority", then connection manager only put "autoconnect-priority=n" but DOES NOT PUT THE REQUIRED "autoconnect=true" in the "/etc/NetworkManager/system-connections/LAN.nmconnection" configuration file It might be the same for ALL interface types supporting the "autoconnect" option. STEPS TO REPRODUCE 1. edit a LAN cabled interface connection 2. unselect then autoconnect option 3. save 4. select then autoconnect option and put priority 98 5. save 6. examine the autoconnect* directive in /etc/NetworkManager/system-connections/LAN.nmconnection OBSERVED RESULT there is no "autoconnect=true" directive in /etc/NetworkManager/system-connections/LAN.nmconnection there is ONLY an "autoconnect-priority=98" directive in this file EXPECTED RESULT there should be an "autoconnect=true" directive in the LAN configuration file otherwise NM will not start this interface at boot. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7700T CPU @ 2.90GHz Memory: 15,4 Gio ADDITIONAL INFORMATION root@minipc:~# dpkg -l plasma-nm Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ NomVersionArchitecture Description +++-==-==--= ii plasma-nm 4:5.17.4-0ubuntu1~ubuntu19.10~ppa1 amd64Plasma5 networkmanager library. root@minipc:~# dpkg -l Display all 61599 possibilities? (y or n) root@minipc:~# dpkg -l network-manager Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-===-===--= ii network-manager 1.20.4-2ubuntu2 amd64network management framework (daemon and userspace tools) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 415509] autoconnect=true missing in nm configuration file
https://bugs.kde.org/show_bug.cgi?id=415509 p...@free.fr changed: What|Removed |Added Summary|autoconnect not set in nm |autoconnect=true missing in |configuration file |nm configuration file -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415467] Can't circumvent Google's browser blocking with user agent manager
https://bugs.kde.org/show_bug.cgi?id=415467 Juraj changed: What|Removed |Added CC||sgd.or...@gmail.com --- Comment #1 from Juraj --- The best advice I can give you is to move away from Google. Apart from changing user agent I do not know of any other way. Sure, there might be a way to block it or reverse engeneer their detection system but in such company as Google they can change it anytime they want. I also read about it, the best solution is to contact Google to remove it, or to contact some other influential organization to force them to disable it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415262] KWin compositing freezes under certain circumstances since recent overhaul
https://bugs.kde.org/show_bug.cgi?id=415262 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/ba2c0324d2ef21a5c42ec182e ||851a435180b51ac --- Comment #10 from Roman Gilg --- Git commit ba2c0324d2ef21a5c42ec182e851a435180b51ac by Roman Gilg. Committed on 23/12/2019 at 22:55. Pushed by romangilg into branch 'master'. Reset buffer swap state on stop Summary: When the compositor is stopped there might still be a buffer swap ongoing, in particular when a client blocks compositing on X11. Depending on the backend the next buffer swap event might be handled in bufferSwapComplete (Wayland) or not be handled (X11 GLX, since a new GLX window will be created while the swap event is sent for the old one). With this patch the buffer swap state is reset on stop such that on later start no outdated data might create errors and instead a new repaint can be triggered with updated data. Test Plan: Manually on X11 and Wayland. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D26090 M +5-6composite.cpp https://commits.kde.org/kwin/ba2c0324d2ef21a5c42ec182e851a435180b51ac -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 412872] KDE becomes unresponsive after connecting keyboard with US internal layout.
https://bugs.kde.org/show_bug.cgi?id=412872 --- Comment #1 from akendo --- I've updated to the latest version of KDE. The problem persist. However, on another laptop a similar defect exists. On the affected system the issue can be observe when the system returns out of memory (suspend-to-memory). Current tested system: Operating System: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.4.2-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,4 GiB of RAM the other system is: Operating System: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 4.19.91-1-lts OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2820QM CPU @ 2.30GHz Memory: 15.6 GiB of RAM I might should add that the systems have modified key-bindings that might related / cause the issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377456] Please add "eraser"
https://bugs.kde.org/show_bug.cgi?id=377456 Nate Graham changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- So in other words this works as intended. Okular is not an image manipulation app, so it doesn't make sense for you to be able to erase its contents. However you can add an opaque annotation to cover up content (for example to redact sensitive text) which is different and already supported. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 415429] Thunderbird: Hanging part of font truncated when (not) hovered
https://bugs.kde.org/show_bug.cgi?id=415429 --- Comment #5 from Nate Graham --- Any of them. :) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] Scrollbar set to 'hidden' reappears sometimes when zooming then scrolling
https://bugs.kde.org/show_bug.cgi?id=415508 --- Comment #1 from Ferdinand B --- Relevant Konsole Settings: Initial Size: 270 x 68 Scrollback: Fixed size 1 lines -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 401512] kig crashes with simple python script with a failing assertion
https://bugs.kde.org/show_bug.cgi?id=401512 --- Comment #9 from Maurizio Paolini --- (In reply to David E. Narvaez from comment #6) > (In reply to Kevin Kofler from comment #4) > > So, after looking at the code and the documentation, I suspect the issue is > > not really the reference count of the tuple itself, but of the individual > > arguments, which would explain why you do not hit this assertion if the > > function has no arguments. > > I agree that the issue seems to be the refcount of the arguments, but how > would you explain that the patch in comment #2 works around the issue? > > On a separate note, the assertion was added 3 years ago here > > https://github.com/boostorg/python/commit/ > bc2f77a3db0b3b428ef7bc205804ce5625e46001 > > so it seems this has been broken since Boost 1.63 or so? Yes, indeed! I am no longer an active user, so I realized the presence of the problem after some time; then I posted the report only downstream for fedora. In any case I opened this bug report more than one year ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415496] plasmashell starting then crashing
https://bugs.kde.org/show_bug.cgi?id=415496 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #3 from David Edmundson --- >#6 0x7f52797a17b6 in () at >/usr/lib/qt/qml/org/kde/plasma/calendar/libcalendarplugin.so The crash is in here, I don't know where. I fixed a crash inside libcalendar plugin very recently which you would hit if your system locale is not set up correctly. That fix is merged, but not released. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 --- Comment #8 from Maik Qualmann --- Ok, if MinGW uses C++03 by default, then it is clear. I cannot reproduce the crash with the test image in a Windows 10 VM. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411599] Open/Save dialog is much too small by default
https://bugs.kde.org/show_bug.cgi?id=411599 Nate Graham changed: What|Removed |Added Latest Commit||https://cgit.kde.org/plasma ||-integration.git/commit/?id ||=2e9f96847432c707a9dfbfe074 ||8f0524a128abb7 Version Fixed In||5.17.5 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Nate Graham --- Ah yes, thanks for finding the bug report for this. I missed it before. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 392778] Elisa should better handle being scaled down to a small size
https://bugs.kde.org/show_bug.cgi?id=392778 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||20.04.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||elisa/commit/53aea328d0d162 ||c60b83c6d2f389405a2d0c4b33 --- Comment #7 from Nate Graham --- Git commit 53aea328d0d162c60b83c6d2f389405a2d0c4b33 by Nate Graham. Committed on 23/12/2019 at 21:45. Pushed by ngraham into branch 'master'. Make the "Show Playlist" action more obvious, and hide the playlist at small window sizes See merge request kde/elisa!47 FIXED-IN: 20.04.0 https://invent.kde.org/kde/elisa/commit/53aea328d0d162c60b83c6d2f389405a2d0c4b33 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 --- Comment #7 from caulier.gil...@gmail.com --- MXE use G++ 5.5.0 and is compatible with C++11. We just need to force compiler to use C++11 in CMake at configuration stage. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 414831] cant focus embedded terminal with ctrl+down
https://bugs.kde.org/show_bug.cgi?id=414831 mischiew changed: What|Removed |Added CC||misch...@gmail.com --- Comment #2 from mischiew --- Same. Actually I can't focus on the embedded terminal at all, even trying other shortcuts either in the main or secondary shortcut. Most of the shortcuts shown in the Krusader Handbook seem out-of-date. (Not sure this project is still alive though, just posting this for reference) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 --- Comment #6 from caulier.gil...@gmail.com --- Maik, look this : https://forum.qt.io/topic/35638/issue-with-new-signal-slot-mechanism-in-mingw-qt5-2/2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] Scrollbar set to 'hidden' reappears sometimes when zooming then scrolling
https://bugs.kde.org/show_bug.cgi?id=415508 Ferdinand B changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415508] New: Scrollbar set to 'hidden' reappears sometimes when zooming then scrolling
https://bugs.kde.org/show_bug.cgi?id=415508 Bug ID: 415508 Summary: Scrollbar set to 'hidden' reappears sometimes when zooming then scrolling Product: konsole Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: theferdi...@gmail.com Target Milestone: --- SUMMARY Sometimes the scrollbar reappears on the left side of the screen even when the scrollbar is set to 'hidden'. This happens when scrolling in a zoomed view. STEPS TO REPRODUCE 1. open konsole 2. set scrollbar to 'hidden' 3. get some lines into the scroll buffer (e.g. `yes | head -n100`) 4. scroll a bit 5. zoom a bit 6. scroll a bit 7. scrollbar appears on the left side of the window OBSERVED RESULT The scrollbar appears on the left side of the window when scrolling in a zoomed view (and previously having scrolled). Also, the reappearing scrollbar obstructs view of the leftmost column(s) of the terminal (depending on zoom level) EXPECTED RESULT The scrollbar doesn't appear because it is set to 'hidden' SOFTWARE/OS VERSIONS Linux: Arch Linux with Linux 5.4.6 KDE Plasma Version: N/A (using sway-git) KDE Frameworks Version: 5.65.0-2 Qt Version: 5.14.0-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415496] plasmashell starting then crashing
https://bugs.kde.org/show_bug.cgi?id=415496 Garrett Weber changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #2 from Garrett Weber --- Hey David Edmundson, I saw you commented on one of the bugs, that is this bug is a duplicate to, "Please check your locale is set correctly Your backtrace misses symbols, but this is probably fixed in the next framework by 6756d00fba11ca2af921a67acdb5e3c92e23bb8a in p-f" Mind explaining what you meant by this because I am very confused. Thank you so much, Garrett -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 --- Comment #5 from Maik Qualmann --- This new type of signal/slot connection can probably not be processed by MinGW. It is not relevant for this crash, but maintenance tasks cannot currently be canceled in the Windows version. connect(this, static_cast (::progressItemCanceled), this, ::slotCancel); Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 414564] Update of bank account data aborted
https://bugs.kde.org/show_bug.cgi?id=414564 --- Comment #11 from Stefan Hohrein --- I was not able with this version to read back the last saved data completely. Bank account data was missing. ==> New setup of bank account not successfully (I don't know why)==> no mapping to online banking acoount possible. I am using mobileTAN and I was never asked for my mobile phone number ==> it can't work. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #41 from Jarosław Staniek --- Time flies and KDE is kept apart from the standard because of a single person decission to "fix" a word in just KDE. NSLW wrote (I'd be happy if you unhide your name in these records as a minimum attitude for a maintainer, and a way to somehow connecting to the KDE project - you seem very much disconnected in a me-vs-others way? other persons even on this bug page keep the names in the public): > In German, one translates "cancel" as "abbrechen" and not as "annullieren". > Both words exist in German though. It's not the topic in hand. Correct question is how many translations perform the same type of revolution/deviating from other vendors by such one-sided change you did without a review request of any kind. In other words, if we had `Zaniechaj` originally in PL computing dictionary (say, in the government committee I've been working for) and in so large percentage of installations out there (including the web), there would be exact the same discussion if changed to 'Anuluj' without prior discussion on what's best for the community project's goals. Do you know that preserving the Polish language (and reinventing sometimes at all costs) is a not primary goal of the KDE project but at most secondary goal? Primary goal is delivering useful Free software to the users. To make that possible requirement is to preserve community of creators and contributors in order to keep the project alive and in a good shape to achieve the first goal. Distancing from the mainstream is against of all that. In the adult world secondary goal is the one that is abandoned as a compromise when primary goal is harm in any way otherwise. Secondly, how about the "OK" word? How is that different from Anuluj. It is a fact that it's not even English term but Americanism, yet it is generally adopted by so many translations for ultimate compatibility with translation standards across vendors. So your position is unchanged as if you ignored dozens of contributors telling you're wrong; despite of that, there is your own fork of translations proposed on the table, what shows extraordinary good will I think. It is close to last chance for you to keep your ideas published within the project, so let's say, last day of 2019 is a deadline for this proposal. Otherwise I'd only wait to the Community working group's verdict, which is unfortunate choice given how confusing the problem is (the said absurd, I'll repeat, is best word for that). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #4 from Maik Qualmann --- Can you choose something else in the sidebars for testing than the map. We may also have a crash in Marble. This message is also strange, which does not occur under Linux: QObject::connect: signal not found in Digikam::MaintenanceTool Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415507] Equity prediction is blurry and has graphical glitches with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=415507 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415507] New: Equity prediction is blurry and has graphical glitches with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=415507 Bug ID: 415507 Summary: Equity prediction is blurry and has graphical glitches with fractional scaling Product: kmymoney Version: 5.0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124680 --> https://bugs.kde.org/attachment.cgi?id=124680=edit Screenshot of the issue. SUMMARY The rendering text is blurry and the labels are stacked as in the screenshot. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Scaling: 1.5 Both forced dpi (144) and non forced (96) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415506] Text of KMyMoney Banner blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=415506 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415506] New: Text of KMyMoney Banner blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=415506 Bug ID: 415506 Summary: Text of KMyMoney Banner blurry on HiDPI Product: kmymoney Version: 5.0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124679 --> https://bugs.kde.org/attachment.cgi?id=124679=edit Screenshot of the issue. SUMMARY The text "KMyMoney" on the right side of the banner is blurry on HiDPI as seen in the screenshot. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Scaling: 1.5 -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 401512] kig crashes with simple python script with a failing assertion
https://bugs.kde.org/show_bug.cgi?id=401512 --- Comment #8 from David E. Narvaez --- (In reply to Kevin Kofler from comment #7) > The patch from comment #2 prevents the tuple from being de-refcounted all > the way down to 0 (because it adds a bogus unowned reference), so the tuple > is leaked, and its continued existence also keeps the arguments referenced. > (It is the destruction of the tuple that decreases the reference count of > each argument.) Ah, makes sense. > On the other hand, the patch from comment #5 looks like the correct fix to > me. I agree. Franco, can you post your patch to Phabricator? Against the release/19.12 branch please. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415505] New: Kdenlive to cannot import files or open projects when jack is running.
https://bugs.kde.org/show_bug.cgi?id=415505 Bug ID: 415505 Summary: Kdenlive to cannot import files or open projects when jack is running. Product: kdenlive Version: 18.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: k...@dharty.com Target Milestone: --- SUMMARY Importing a video clip or opening a previous project causes kdenlive (18.12.3) to hang when using the JACK audio server. DETAILS: After a recent upgrade of Opensuse, from 15.0 to 15.1, I created a new project in kdenlive (18.12.3) and tried to import a video clip which cased kdenlive to hang. I also tried with the 19.12.0a and 18.12.1b appimages from the kdenlive site, with the same issue, i.e. hanging when trying to import video clips. I also tried opening some previously created projects, with similar hangs. When importing clips, I will see the clip name appear in the Project Bin window along with a grey thumbnail and a partially completed project bar just underneath. On one occasion when starting the kdenlive-18.12.1b-x86_64.appimage, I noticed the following line in the console output: 'Switching audio backend to: "sdl2_audio" ' I normally run the jack server for audio applications, with the pulse audio passthrough (JACK D-Bus intrrface to allow pulse applications to go through jack), so I stopped jack, and kdenlive ran correctly. Then, I restarted jack followed by kdenlive and saw kdenlive hang when trying to import a clip. Then, in pavucontrol, I assigned kdenlive to the "Jack sink (PulseAudio JACK sink)" audio device instead of the direct device, and kdenlive un-hung. STEPS TO REPRODUCE 1. start JACK audio server with QJackCTL with the D-Bus Interaface and JACK D-Bus interface options enabled. Otherwise the jackd command line is: /usr/bin/jackd -dalsa -r44100 -p256 -n2 -Xseq -D -Chw:CODEC -Phw:CODEC,0 2. Start kdenlive 3. try to import a video clip OBSERVED RESULT kdenlive becomes unresponsive and must be terminated unless the audio device assignment in pavucontrol is changed to jack sink. EXPECTED RESULT Kdenlive successfully imports the video clip. SOFTWARE/OS VERSIONS OpenSuse 15.1 Linux/KDE Plasma: KDE Frameworks 5.55.0 Qt 5.9.7 (built against 5.9.7) The xcb windowing system ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415504] New: Error when trying open djvu file on windows
https://bugs.kde.org/show_bug.cgi?id=415504 Bug ID: 415504 Summary: Error when trying open djvu file on windows Product: okular Version: 1.8.2 Platform: unspecified OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: life...@yandex.ru Target Milestone: --- SUMMARY Unable to open djvu files in windows build from Microsoft store. Pdf works fine. STEPS TO REPRODUCE 1. Select "Open" window from "File" menu 2. Choose djvu file 3. Press "Open" OBSERVED RESULT Error message: Could not open file:///D:/.../.../.../filename.djvu EXPECTED RESULT File has opened SOFTWARE/OS VERSIONS Windows: 10 Pro -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 415503] New: Crash on close of KSysGuard after prolonged period of monitoring
https://bugs.kde.org/show_bug.cgi?id=415503 Bug ID: 415503 Summary: Crash on close of KSysGuard after prolonged period of monitoring Product: ksysguard Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: dark...@nearce.com Target Milestone: --- Application: ksysguard (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: This crash occurs on close of ksysguard. It happens somewhat sporadically, and I believe it may be related to long running KSysGuard processes. Possibly related to watching graphs. The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6404550bc0 (LWP 16688))] Thread 4 (Thread 0x7f63bd910700 (LWP 3115)): #0 0x7f6403e2ebf9 in __GI___poll (fds=0x7f63b8007030, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f63c24c1481 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f63c24b2e40 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f63c24b34d0 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f63c24b3560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f63c24c13c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f63c2263318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f63f30d76db in start_thread (arg=0x7f63bd910700) at pthread_create.c:463 #8 0x7f6403e3b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f63d4b10700 (LWP 16690)): #0 0x7f6403e2ebf9 in __GI___poll (fds=0x7f63c8004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f63f11575c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63f11576dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63ff540b9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f63ff4e106a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f63ff2fc3aa in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f63ffc570e5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f63ff2fdb52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f63f30d76db in start_thread (arg=0x7f63d4b10700) at pthread_create.c:463 #9 0x7f6403e3b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f63d8398700 (LWP 16689)): #0 0x7f6403e2ebf9 in __GI___poll (fds=0x7f63d83978e8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f63f3932747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f63f393436a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f63da2e3e10 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f63ff2fdb52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f63f30d76db in start_thread (arg=0x7f63d8398700) at pthread_create.c:463 #6 0x7f6403e3b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6404550bc0 (LWP 16688)): [KCrash Handler] #6 0x7f63ff385eaa in operator==(QString const&, QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6400948577 in QLabel::setText(QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f640417e460 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_ksysguard.so #9 0x7f64031c9bf2 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #10 0x7f64031d0cd4 in () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #11 0x7f63ff5139ef in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f63ff45167a in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f63ff458431 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f63ff458900 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f63ff5138d5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f63ff520028 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f63ff5203e2 in QSocketNotifier::event(QEvent*) () at
[Spectacle] [Bug 415153] Graphic glitches when taking a screenshot with the rectangle mode
https://bugs.kde.org/show_bug.cgi?id=415153 Postix changed: What|Removed |Added CC||subd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 415153] Graphic glitches when taking a screenshot with the rectangle mode
https://bugs.kde.org/show_bug.cgi?id=415153 Postix changed: What|Removed |Added Summary|When taking a screenshot|Graphic glitches when |with the rectangle mode,|taking a screenshot with |the taskbar may vanish |the rectangle mode |until the screenshot is | |taken | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 415153] When taking a screenshot with the rectangle mode, the taskbar may vanish until the screenshot is taken
https://bugs.kde.org/show_bug.cgi?id=415153 --- Comment #6 from Postix --- Created attachment 124678 --> https://bugs.kde.org/attachment.cgi?id=124678=edit Screenshot with severe glitches. The bug does not seem directly related to the task bar but rather to the rendering of the windows or grabbing the content from the graphics buffer. The windows in the screenshot I took yesterday are completely torn apart. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415502] New: Searching spinner is blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=415502 Bug ID: 415502 Summary: Searching spinner is blurry on HiDPI Product: okular Version: 1.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 124677 --> https://bugs.kde.org/attachment.cgi?id=124677=edit Screenshot of the issue. SUMMARY Searching something (Ctrl+F) displays a spinner right to the search input field. This spinner looks blurry on HiDPI as in the screenshot. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Scaling: 1.5 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415502] Searching spinner is blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=415502 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 --- Comment #3 from hardy.pub...@gmail.com --- The problem image is DSC_0017_1.JPG which is too large to attach but is accessible here: https://1drv.ms/u/s!AhmvR4JSJH8OkwwXmqk0n0yOBH7d?e=56RzXD -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415489] Win32 7.0.0 Beta 1 Crash On Opening Preview
https://bugs.kde.org/show_bug.cgi?id=415489 --- Comment #2 from hardy.pub...@gmail.com --- Created attachment 124676 --> https://bugs.kde.org/attachment.cgi?id=124676=edit Debug Log 2 I can't share those images, sorry, I should have checked before posting. I have an image which causes the same crash (IMG_20130825_170807.JPG) but it doesn't have the same debug log entry so there may be more than one problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415476] ctrl+click on canvas doesn't always disable eraser mode
https://bugs.kde.org/show_bug.cgi?id=415476 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- Setting to CONFIRMED I can confirm this for the 4.2.8 appimage as described in the initial report. It seems random and infrequent but not rare. It does not happen (as far as I can tell) with the Windows portable zip version 4.2.8 or the latest 4.3.0 prealpha portable zip running on Windows 10. It happens all the time on the Dec 17th 4.3.0-prealpha (git d0ced0f) and later 4.3.0 prealpha appimages. (I don't have any earlier ones to test.) It's when you Ctrl+click/tap on exactly the same colour that is already selected. If you pick a colour that has even +/-1 difference in the RGB value then erase mode switches off. Also, if you use the stylus/mouse to do an erase stroke and then Ctrl+click/tap on the same colour, the erase mode switches off. Also, if you do a Ctrl+click/tap again with less than about 0.5 seconds between clicks/taps, the erase mode switches off. Doing it more slowly leaves the erase mode still on. This does not happen if you select the Colour Selector Tool and use that instead, UNLESS you uncheck the Update Color option in the Tool Options docker, in which case it does happen. (The E key will still activate the erase mode and it will be indicated as such in the toolbar even though it's greyed out when the Color Selector Tool has been selected. After this, it becomes fully active again.) SYSTEM INFORMATION: Krita Version: 4.3.0-prealpha (git d0ced0f) Languages: en_GB, en, en, en_GB, en Hidpi: true Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.19.0-6-amd64 Pretty Productname: Debian GNU/Linux 10 (buster) Product Type: debian Product Version: 10 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 418.74" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 16039 Mb Number of Cores: 8 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 18 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 360 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415501] New: kate don't run because network resouce in recent files not avaliable
https://bugs.kde.org/show_bug.cgi?id=415501 Bug ID: 415501 Summary: kate don't run because network resouce in recent files not avaliable Product: kate Version: 19.08.2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: bes.inter...@gmail.com Target Milestone: --- SUMMARY kate don't load run most likely timeout for cheking recently opened files from network resource STEPS TO REPRODUCE 1. open file to edit on network resource like (smb \\192.0.2.0\path) 2. close kate 3. make resouce unavaliable 4. open kate OBSERVED RESULT start as expected EXPECTED RESULT process run, but nothing happens SOFTWARE/OS VERSIONS Windows: 10 1809 most likely independent of OS -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415500] New: CPU Load Monitor and Memory Status widgets don't display a graph
https://bugs.kde.org/show_bug.cgi?id=415500 Bug ID: 415500 Summary: CPU Load Monitor and Memory Status widgets don't display a graph Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: codingko...@gmail.com Target Milestone: 1.0 Created attachment 124675 --> https://bugs.kde.org/attachment.cgi?id=124675=edit Screenshot showing the two problematic widgets, as well as the System Load Viewer widget that does work for me, displaying the graph as intended. SUMMARY My CPU Load Monitor and Memory Status widgets have stopped displaying the graph that displays the system runtime info. STEPS TO REPRODUCE 1. Unlock widgets. 2. Add a CPU Load Monitor widget or Memory Status widget to the desktop, or to a panel. OBSERVED RESULT The labels in the widgets are displayed correctly, as are the text information, but there is only empty space where the graphs should be. EXPECTED RESULT The graphs should be shown in the widgets. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Graphics Driver: Nvidia 440.44 ADDITIONAL INFORMATION In the past, I have been able to trigger this issue by switching to a virtual console, and back. However, the issue would never persist through reboots. The recent event that I believe may have led to this being persistently nonfunctional is that, after a driver crash of sorts, my tray icons became low resolution with broken alpha, and a warning was displayed in my tray about having switched to software rendering. A reboot fixed my tray icons and made the warning go away, but my RAM and CPU widgets still don't display their graphs anymore. -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 415499] Some instructions for building KTimeTracker... would be good!
https://bugs.kde.org/show_bug.cgi?id=415499 --- Comment #1 from Ganton --- Created attachment 124674 --> https://bugs.kde.org/attachment.cgi?id=124674=edit Russian texts when trying to write in https://aspotashev.blogspot.com/2019/12/ktimetracker-501-released.html -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410254] Clipboard from platform to OS doesn't work 100% of the time
https://bugs.kde.org/show_bug.cgi?id=410254 André Vitor de Lima Matos changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 415499] New: Some instructions for building KTimeTracker... would be good!
https://bugs.kde.org/show_bug.cgi?id=415499 Bug ID: 415499 Summary: Some instructions for building KTimeTracker... would be good! Product: ktimetracker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: ku...@gmx.com Target Milestone: --- Some instructions for building KTimeTracker... would be good! By the way: - People have to understand Russian texts at the end of https://aspotashev.blogspot.com/2019/12/ktimetracker-501-released.html when trying to write to you. - It looks like you cannot compile KTimeTracker with the latest version of Ubuntu or Kubuntu (but maybe that's unavoidable): CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find KF5 (missing: IdleTime) (found suitable version "5.62.0", minimum required is "5.54.0") Thank you because KTimeTracker is useful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415498] New: Kwin crash twice in seccession after launching stam game.
https://bugs.kde.org/show_bug.cgi?id=415498 Bug ID: 415498 Summary: Kwin crash twice in seccession after launching stam game. Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: kwin_x11 (5.17.80) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.3.11-ck1-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: >From steam, ran Killing Floor 2 as the game opened i got 2 Dr Konqui notifications about kwin's crash. To be more precise as the game went fullscreen and the compositor turned off kwin crashes. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff703da3480 (LWP 10331))] Thread 17 (Thread 0x7ff6c57fa700 (LWP 10370)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7ff6c5ffb700 (LWP 10369)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7ff6c67fc700 (LWP 10368)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7ff6c6ffd700 (LWP 10367)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7ff6c77fe700 (LWP 10366)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7ff6c7fff700 (LWP 10365)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7ff6dcda2700 (LWP 10364)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7ff6dd5a3700 (LWP 10363)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff6ddda4700 (LWP 10362)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at /lib64/libpthread.so.0 #4 0x7ff7059274af in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff6de5a5700 (LWP 10361)): #0 0x7ff70367f6a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6f4eaeb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7ff6f4eaea37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7ff703678f2a in start_thread () at
[plasmashell] [Bug 415317] click on an entry of the context menu of systray icons has no effect on Wayland
https://bugs.kde.org/show_bug.cgi?id=415317 --- Comment #4 from David Edmundson --- Git bisect shows it has being introduced during the big CSD patchset. Can't quite work out which one as they're all tied together and some commits don't work. # good: [c22546868d75e94cd1a31b89daddd002555f1919] [effects] fix mouse wheel detection git bisect good c22546868d75e94cd1a31b89daddd002555f1919 # good: [f62086f9d3518c0c7e0a3cf34981e0aa57b543d1] [effects] Remove unneeded link to KService git bisect good f62086f9d3518c0c7e0a3cf34981e0aa57b543d1 # bad: [754b72d155820a6c8a9ba94b2c0960da1b2f86ce] [x11] Name client pixmap instead of frame pixmap git bisect bad 754b72d155820a6c8a9ba94b2c0960da1b2f86ce # bad: [84d75cb5674577098d584c7f3634ea2a81d8b9f2] [x11] Add support for _GTK_FRAME_EXTENTS git bisect bad 84d75cb5674577098d584c7f3634ea2a81d8b9f2 # good: [6bfa931f2b1d9787e75c4be4e44611d51ba835c3] Associate output transforms and orientations git bisect good 6bfa931f2b1d9787e75c4be4e44611d51ba835c3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415454] Timeline indicators
https://bugs.kde.org/show_bug.cgi?id=415454 emohr changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415448] Proxy error with Image Sequence
https://bugs.kde.org/show_bug.cgi?id=415448 emohr changed: What|Removed |Added Ever confirmed|0 |1 CC||fritzib...@gmx.net Flags||Brainstorm+ Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403944] Stabilizing 30fps clips in 60fps project problems
https://bugs.kde.org/show_bug.cgi?id=403944 emohr changed: What|Removed |Added Flags||timeline_corruption+ -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 401512] kig crashes with simple python script with a failing assertion
https://bugs.kde.org/show_bug.cgi?id=401512 --- Comment #7 from Kevin Kofler --- The patch from comment #2 prevents the tuple from being de-refcounted all the way down to 0 (because it adds a bogus unowned reference), so the tuple is leaked, and its continued existence also keeps the arguments referenced. (It is the destruction of the tuple that decreases the reference count of each argument.) On the other hand, the patch from comment #5 looks like the correct fix to me. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415442] crash on startup unless lanched with sudo command in terminal
https://bugs.kde.org/show_bug.cgi?id=415442 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- What you can try is delete kdenliverc see here: https://community.kde.org/Kdenlive/Configuration. Kdenlive 17.12.3 is not supported anymore. It could be that together Linux Mint 19.2 that some functionality is gone. Please try with the current Kdenlive AppImage version 19.12.0a https://files.kde.org/kdenlive/release/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 253091] digiKam will not launch
https://bugs.kde.org/show_bug.cgi?id=253091 --- Comment #11 from caulier.gil...@gmail.com --- For regression test, as this file has not been fully closed in the past. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415440] SVG support - scripts
https://bugs.kde.org/show_bug.cgi?id=415440 emohr changed: What|Removed |Added Ever confirmed|0 |1 CC||fritzib...@gmx.net Flags||Brainstorm+ Status|REPORTED|CONFIRMED --- Comment #1 from emohr --- Kdenlive SVG import relies on Qt QImage, which supports TinySVG only. See here as well: https://bugs.kde.org/show_bug.cgi?id=405249 -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 401512] kig crashes with simple python script with a failing assertion
https://bugs.kde.org/show_bug.cgi?id=401512 --- Comment #6 from David E. Narvaez --- (In reply to Kevin Kofler from comment #4) > So, after looking at the code and the documentation, I suspect the issue is > not really the reference count of the tuple itself, but of the individual > arguments, which would explain why you do not hit this assertion if the > function has no arguments. I agree that the issue seems to be the refcount of the arguments, but how would you explain that the patch in comment #2 works around the issue? On a separate note, the assertion was added 3 years ago here https://github.com/boostorg/python/commit/bc2f77a3db0b3b428ef7bc205804ce5625e46001 so it seems this has been broken since Boost 1.63 or so? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415446] Dissolve goes black
https://bugs.kde.org/show_bug.cgi?id=415446 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- Tested with version 19.12.0: it works as expected. Please try with the current Kdenlive AppImage version 19.12.0a 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.
[kdenlive] [Bug 415448] Proxy error with Image Sequence
https://bugs.kde.org/show_bug.cgi?id=415448 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit e083567cc30cf5af56ea441651b2322d63eb63f8 by Jean-Baptiste Mardelle. Committed on 23/12/2019 at 18:29. Pushed by mardelle into branch 'release/19.12'. Fix proxying of slideshow clips. M +2-0src/jobs/loadjob.cpp M +12 -0src/jobs/proxyclipjob.cpp https://invent.kde.org/kde/kdenlive/commit/e083567cc30cf5af56ea441651b2322d63eb63f8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 253091] digiKam will not launch
https://bugs.kde.org/show_bug.cgi?id=253091 --- Comment #10 from Giuseppe Vinci --- This bug is already no more reproducible since long time on my environment. I actually use the version 6.1.0; but why testing on beta versions? I think, most of kde users does not work with betas. Or there are now only beta testers among kde users? ;-) Have a nice time! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 400120] Feature Request: PDF View Support
https://bugs.kde.org/show_bug.cgi?id=400120 Francesco Turco changed: What|Removed |Added CC||ftu...@fastmail.fm -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415452] White squares
https://bugs.kde.org/show_bug.cgi?id=415452 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Flags||MOVIT+ Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please switch of GPU acceleration as it is not stable and unreliable. I assume the icons will appear normal afterwards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415497] New: Night Color breaks after compositing resumes
https://bugs.kde.org/show_bug.cgi?id=415497 Bug ID: 415497 Summary: Night Color breaks after compositing resumes Product: kwin Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dark...@nearce.com Target Milestone: --- SUMMARY When playing a game that disables compositing, night color still seems to work, however, when the game closes, night color is not reapplied, i.e. it must be manually toggled to restore the blue reduction. STEPS TO REPRODUCE 1. Open a game that disables compositing while night color is on 2. Close the game OBSERVED RESULT Blues return EXPECTED RESULT Blues stay suppressed ADDITIONAL INFORMATION Xorg night color with nvidia drivers 435.21. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415317] click on an entry of the context menu of systray icons has no effect on Wayland
https://bugs.kde.org/show_bug.cgi?id=415317 --- Comment #3 from David Edmundson --- Things I have learned so far for the system tray popup case: - Qt menu correctly sends a grab on the popup - kwin correctly receives the grab on the popup in PopupInputFilter - Qt does not get a pointer_enter event to the popup, only the panel underneath - Qt then sends input to the window it has been told has focus -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 abogi...@gmail.com changed: What|Removed |Added CC|abogi...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 soredake changed: What|Removed |Added CC||fds...@krutt.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382576] DNG Image Converter crashed trying to convert a RAW image
https://bugs.kde.org/show_bug.cgi?id=382576 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.0.0 --- Comment #2 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361678] dngconverter crashes when opening a raw file (*.NEF in my case)
https://bugs.kde.org/show_bug.cgi?id=361678 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||7.0.0 --- Comment #7 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 242479] crashes on appling refocus tool to raw image
https://bugs.kde.org/show_bug.cgi?id=242479 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|DUPLICATE |FIXED --- Comment #9 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 151523] RAW converter crashes on startup
https://bugs.kde.org/show_bug.cgi?id=151523 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||7.0.0 Resolution|WORKSFORME |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146259] Raw Converter won't convert to 16bit PNG
https://bugs.kde.org/show_bug.cgi?id=146259 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 CC||caulier.gil...@gmail.com --- Comment #13 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 155156] Raw file conversion crash single/batch mode
https://bugs.kde.org/show_bug.cgi?id=155156 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |FIXED CC||caulier.gil...@gmail.com Version Fixed In||7.0.0 --- Comment #2 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 99437] Incorrect Libraw option
https://bugs.kde.org/show_bug.cgi?id=99437 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Incorrect dcraw option -g |Incorrect Libraw option Version Fixed In||7.0.0 CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 139550] autocorrect levels for raw photos (which are shown too dark)
https://bugs.kde.org/show_bug.cgi?id=139550 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |FIXED Version Fixed In||7.0.0 CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 342233] Crash when decoding pentax k-r raw photo
https://bugs.kde.org/show_bug.cgi?id=342233 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Summary|crash wehn i elaborate a|Crash when decoding pentax |pentax k-r raw photo|k-r raw photo Version Fixed In||7.0.0 --- Comment #6 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 257737] Fuji S3 Pro Raw files (RAF) only S pixels are processed giving 6MP Should be S+R Pixels giving 12MP
https://bugs.kde.org/show_bug.cgi?id=257737 --- Comment #20 from caulier.gil...@gmail.com --- digiKam 7.0.0-beta1 use last Libraw 0.20.0 engine. https://download.kde.org/unstable/digikam/ Can you reproduce this problem ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 101281] EXIF info from RAW images not woking properly
https://bugs.kde.org/show_bug.cgi?id=101281 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|DUPLICATE |FIXED --- Comment #4 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359949] Bad canon raw file makes digikam to crash at startup
https://bugs.kde.org/show_bug.cgi?id=359949 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 Resolution|UPSTREAM|FIXED --- Comment #3 from caulier.gil...@gmail.com --- Not reproducible with digiKam 7.0.0-beta1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 154922] Start to use libopenraw instead of libraw
https://bugs.kde.org/show_bug.cgi?id=154922 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415454] Timeline indicators
https://bugs.kde.org/show_bug.cgi?id=415454 emohr changed: What|Removed |Added Flags||Brainstorm+ CC||fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 272725] Some PEF/jpeg files not recognized as raw/non raw
https://bugs.kde.org/show_bug.cgi?id=272725 caulier.gil...@gmail.com changed: What|Removed |Added Summary|certain PEF/jpeg files not |Some PEF/jpeg files not |recognized as raw/non raw |recognized as raw/non raw -- You are receiving this mail because: You are watching all bug changes.
