[kstars] [Bug 420490] KStars crashes on start of INDI server
https://bugs.kde.org/show_bug.cgi?id=420490 --- Comment #4 from Jasem Mutlaq --- I'm going to rebuild KStars later today so please retest. Otherwise, I might need teamviewer access to debug remotely. This can be arranged via private email. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419385] Windows snapped to side edges do not show the border of the side snapped
https://bugs.kde.org/show_bug.cgi?id=419385 --- Comment #7 from Michael D --- Sorry! It does not (in regard to my previous comment). That only happens with previously snapped windows of course. On a multi-monitor setup, snapping takes into account the window border, as it should. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419385] Windows snapped to side edges do not show the border of the side snapped
https://bugs.kde.org/show_bug.cgi?id=419385 --- Comment #6 from Michael D --- I just noticed that in a multi-monitor set-up with screen1 on the left and screen2 on the right, snapping on the right of screen1 causes the window border to appear on the left of screen2, which is obviously not desirable. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Ivan Čukić changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REOPENED|RESOLVED --- Comment #3 from Ivan Čukić --- Thanks for the reply. I understand what you are saying and I agree that the end user does not care where the bug is. But Vault can not detect errors that cryfs does not tell it about. Vault reports all errors it gets from cryfs. Cryfs reports errors via return error codes. If cryfs does not report something as an error, Vault is not going to be able to show it to the user. In this case, cryfs crashes and reports an error through debugging output instead through the error codes as it should. And that *IS* an upstream issue. Grepping the output text is not something that could be used as an error detection mechanism reliably because the debugging output is not stable between backend versions and might depend on the active system language. While Vault can catch (and report to the user) many errors, it can not detect everything. It can only rely on the backend command to tell it what is wrong. Problems like this one would require to be handled on a case by case basis. If this was an issue that still existed in the current cryfs version, I would add some sort of a temporary hack to detect and report this problem to the user until the issue in cryfs was fixed. If you find a similar error with the latest version of cryfs, reopen this issue. P.S. While I really appreciate the discussion, it is not generally useful to reopen bug reports just because you disagree with a decision. The bug report status serves the developers to organize their work. If developers set the status to Fixed/Upstream, that means they consider the report to be a bug in an upstream product. If you change the status, that does not change the decision of the developer. It should go the other way round - you explain why you think an issue should be fixed, and the developer will then change the bug report status. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #10 from Wolfgang Bauer --- The crash is also fixed by this commit in kbookmarks: https://cgit.kde.org/kbookmarks.git/commit/?id=4b3fc2aedd86505a47b9b185e086ef253e73ede8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420408] Part of the letters disappear
https://bugs.kde.org/show_bug.cgi?id=420408 --- Comment #3 from Ahab Greybeard --- Can you try this with the appimage from here: https://download.kde.org/stable/krita/4.2.9/krita-4.2.9-x86_64.appimage Can you provide a link to download that font file (and maybe some of the others that do it) so I can try it? -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 420479] Impossible to save data
https://bugs.kde.org/show_bug.cgi?id=420479 --- Comment #4 from Stephane MANKOWSKI --- >From a console, could you try this ? export SKGTRACE=5 skrooge > traces.txt 2>&1 Replay your scenario to get the error. Send me the trace file by email (you can find it in the About of Skrooge) -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 399569] Descriptions for DEC2BIN/OCT2BIN/HEX2DEC/HEX2BIN do not mention input number system
https://bugs.kde.org/show_bug.cgi?id=399569 Dag Andersen changed: What|Removed |Added Version Fixed In||3.2.0 CC||dand...@get2net.dk -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 378527] "Distraction free mode" should be called "Full screen mode"
https://bugs.kde.org/show_bug.cgi?id=378527 Dag Andersen changed: What|Removed |Added Version Fixed In||3.2.0 CC||dand...@get2net.dk -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 277284] Add the NTFS file name compatibility in the CD ripping function
https://bugs.kde.org/show_bug.cgi?id=277284 enno changed: What|Removed |Added CC||enno.na...@t-online.de --- Comment #1 from enno --- To solve this, how about adding, perhaps as a default, the lines regexp_replace=_ regexp_search=[<>":|?*] to ~/.config/kcmaudiocdrc ? Few have titles with these letters, but those that do and use Windows will be grateful. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420495] New: Akonadi Crashes upon removal of duplicates in folder
https://bugs.kde.org/show_bug.cgi?id=420495 Bug ID: 420495 Summary: Akonadi Crashes upon removal of duplicates in folder Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: s.pa...@spiekerbros.com Target Milestone: --- Application: akonadiserver (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.4-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: As, once again, many duplicates are showing up in some folders I wanted to use the "remove duplicates in folder" functionality. This makes akonadi crash every time. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1292ce6800 (LWP 18221))] Thread 6 (Thread 0x7f12897fa700 (LWP 18231)): #0 0x7f1293a5e629 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1293a13324 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1293a1345f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1295488c0b in QEventDispatcherGlib::processEvents (this=0x7f126c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1295430b9b in QEventLoop::exec (this=this@entry=0x7f12897f9da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f129525b5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f129525c698 in QThreadPrivate::start (arg=0x55c9d81878c0) at thread/qthread_unix.cpp:342 #7 0x7f1294722efa in start_thread () from /lib64/libpthread.so.0 #8 0x7f1295c243bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1289ffb700 (LWP 18230)): #0 0x7f1294729795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f12952621db in QWaitConditionPrivate::wait (deadline=..., this=0x55c9d8159a30) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55c9d8187170, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f1295262299 in QWaitCondition::wait (this=this@entry=0x55c9d8187168, mutex=mutex@entry=0x55c9d8187170, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x55c9d804560c in Akonadi::Server::SearchTaskManager::searchLoop (this=0x55c9d8187140) at /usr/src/debug/akonadi-server-19.12.3-1.1.x86_64/src/server/search/searchtaskmanager.cpp:221 #5 0x7f129545ea19 in QObject::event (this=0x55c9d8187140, e=0x55c9d8187680) at kernel/qobject.cpp:1339 #6 0x7f1295431fdf in doNotify (event=0x55c9d8187680, receiver=0x55c9d8187140) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #7 QCoreApplication::notify (event=0x55c9d8187680, receiver=0x55c9d8187140, this=) at kernel/qcoreapplication.cpp:1168 #8 QCoreApplication::notifyInternal2 (receiver=0x55c9d8187140, event=0x55c9d8187680) at kernel/qcoreapplication.cpp:1092 #9 0x7f1295434794 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55c9d81872f0) at kernel/qcoreapplication.cpp:1832 #10 0x7f1295489573 in postEventSourceDispatch (s=0x7f1268004fe0) at kernel/qeventdispatcher_glib.cpp:277 #11 0x7f1293a13048 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7f1293a133d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7f1293a1345f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7f1295488bee in QEventDispatcherGlib::processEvents (this=0x7f1268000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #15 0x7f1295430b9b in QEventLoop::exec (this=this@entry=0x7f1289ffada0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #16 0x7f129525b5ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #17 0x7f129525c698 in QThreadPrivate::start (arg=0x55c9d8187240) at thread/qthread_unix.cpp:342 #18 0x7f1294722efa in start_thread () from /lib64/libpthread.so.0 #19 0x7f1295c243bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f128a7fc700 (LWP 18229)): [KCrash Handler] #6 0x7f12952dca4e in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/9/bits/atomic_base.h:413 #7 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #9 QtPrivate::RefCount::deref (this=0x0)
[karbon] [Bug 334608] Rectangle with rounded corners turns into square
https://bugs.kde.org/show_bug.cgi?id=334608 Dag Andersen changed: What|Removed |Added Version Fixed In||3.2.0 Resolution|--- |FIXED CC||dand...@get2net.dk Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #17 from Ivan Čukić --- Great to hear that! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420484] Entering a string in the search field of the message list crashes the application
https://bugs.kde.org/show_bug.cgi?id=420484 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Could you add a backtrace ? Do you have a debug in console ? -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 381341] Crash opening large doc file
https://bugs.kde.org/show_bug.cgi?id=381341 Dag Andersen changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||3.2.0 Status|REPORTED|RESOLVED CC||dand...@get2net.dk -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 379255] Opening a docx file
https://bugs.kde.org/show_bug.cgi?id=379255 Dag Andersen changed: What|Removed |Added CC||dand...@get2net.dk Status|REPORTED|RESOLVED Version Fixed In||3.2.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419921] Cursor doesn't draw
https://bugs.kde.org/show_bug.cgi?id=419921 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419888] Not able to paint
https://bugs.kde.org/show_bug.cgi?id=419888 --- 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.
[amarok] [Bug 419185] Amarok 2.9.70 crashes at startup with QSocketNotifier: Invalid socket on FreeBSD 12.1-RELEASE
https://bugs.kde.org/show_bug.cgi?id=419185 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |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.
[krita] [Bug 418532] Krita will crash Whilst trying to transform a selection
https://bugs.kde.org/show_bug.cgi?id=418532 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 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.
[dolphin] [Bug 419873] DOLPHIN STILL DOES NOT REMEMBER THE MP3 FILE ASSOCIATION
https://bugs.kde.org/show_bug.cgi?id=419873 --- 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.
[umbrello] [Bug 419845] Can't create association between use case and actor
https://bugs.kde.org/show_bug.cgi?id=419845 --- 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.
[plasma-nm] [Bug 418921] systemsettings5 crashes in wayland if wi-fi connections are clicked.
https://bugs.kde.org/show_bug.cgi?id=418921 --- 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-plasma] [Bug 418722] Add stacks like on MacOS
https://bugs.kde.org/show_bug.cgi?id=418722 --- Comment #5 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 420494] New: Opening the archived project crashes
https://bugs.kde.org/show_bug.cgi?id=420494 Bug ID: 420494 Summary: Opening the archived project crashes Product: kdenlive Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jinchoise...@gmail.com Target Milestone: --- Created attachment 127814 --> https://bugs.kde.org/attachment.cgi?id=127814&action=edit as described in the description form above SUMMARY I simply archived my project using the feature in the application. Whether I compress it or not opening this archived project crashes. STEPS TO REPRODUCE 1. archive a project 2. open the project 3. the program crashes while loading the project. OBSERVED RESULT below is the error hint from my terminal (--mlt-log debug mode) | 2020-04-24 13:02:50.322 | [consumer sdl2_audio] stopping put waiting | 2020-04-24 13:02:50.322 | [consumer sdl2_audio] stopping consumer | 2020-04-24 13:02:50.322 | mlt_consumer.c:864: T(mlt_consumer_get_frame)=508 us | 2020-04-24 13:02:50.322 | [filter audiolevel] channel 0 level 0.00 | 2020-04-24 13:02:50.322 | [filter audiolevel] channel 1 level 0.00 | 2020-04-24 13:02:50.329 | [filter avcolor_space] rgb24a @ 1920x1080 -> yuv422 @ 1920x1080 space 709->709 | 2020-04-24 13:02:50.341 | [filter deinterlace] error 0 deint 1 prog 1 fmt yuv422 method onefield | 2020-04-24 13:02:50.341 | TFF in 0 out -1 | 2020-04-24 13:02:50.341 | mlt_consumer.c:908: T(mlt_frame_get_image)=18295 us | 2020-04-24 13:02:50.341 | mlt_consumer.c:864: T(mlt_consumer_get_frame)=206 us | 2020-04-24 13:02:50.341 | [filter audiolevel] channel 0 level 0.00 | 2020-04-24 13:02:50.341 | [filter audiolevel] channel 1 level 0.00 | 2020-04-24 13:02:50.343 | [filter avcolor_space] rgb24a @ 1920x1080 -> yuv422 @ 1920x1080 space 709->709 | 2020-04-24 13:02:50.356 | [filter deinterlace] error 0 deint 1 prog 1 fmt yuv422 method onefield | 2020-04-24 13:02:50.356 | TFF in 0 out -1 | 2020-04-24 13:02:50.356 | mlt_consumer.c:908: T(mlt_frame_get_image)=14851 us | 2020-04-24 13:02:50.356 | mlt_consumer.c:864: T(mlt_consumer_get_frame)=413 us | 2020-04-24 13:02:50.356 | [filter audiolevel] channel 0 level 0.00 | 2020-04-24 13:02:50.356 | [filter audiolevel] channel 1 level 0.00 | 2020-04-24 13:02:50.361 | [filter avcolor_space] rgb24a @ 1920x1080 -> yuv422 @ 1920x1080 space 709->709 | 2020-04-24 13:02:50.375 | [filter deinterlace] error 0 deint 1 prog 1 fmt yuv422 method onefield | 2020-04-24 13:02:50.375 | TFF in 0 out -1 | 2020-04-24 13:02:50.375 | mlt_consumer.c:908: T(mlt_frame_get_image)=19209 us | 2020-04-24 13:02:50.399 | [consumer sdl2_audio] stopping read_ahead | 2020-04-24 13:02:50.400 | mlt_consumer.c:864: T(mlt_consumer_get_frame)=309 us | 2020-04-24 13:02:50.400 | [filter audiolevel] channel 0 level 0.00 | 2020-04-24 13:02:50.400 | [filter audiolevel] channel 1 level 0.00 | 2020-04-24 13:02:50.402 | [filter avcolor_space] rgb24a @ 1920x1080 -> yuv422 @ 1920x1080 space 709->709 | 2020-04-24 13:02:50.420 | [filter deinterlace] error 0 deint 1 prog 1 fmt yuv422 method onefield | 2020-04-24 13:02:50.420 | TFF in 0 out -1 | 2020-04-24 13:02:50.420 | mlt_consumer.c:908: T(mlt_frame_get_image)=20273 us | 2020-04-24 13:02:50.420 | [consumer sdl2_audio] stopped QUnifiedTimer::stopAnimationDriver: driver is not running Case insensitive sorting unsupported in the posix collation implementation Numeric mode unsupported in the posix collation implementation Calling appendChild() on a null node does nothing. /tmp/.mount_kdenliwJpFwI/AppRun: line 26: 11030 세그멘테이션 오류 (core dumped) kdenlive --config kdenlive-appimagerc $@ and 세그먼테이션 오류 is 'segmentation fault'. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Some of my clips' filenames are of Korean. and my clips from the original project are all over (as you might find yourself reading the original project file I attached here) Also, I tried the same step on my other Windows 8.1 system with the latest Kdenlive program of the same version and it gives this "no tarcks found" in the end (not crushing but staying as clean slate) Let me share the original kdenlive project file and then archived one in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419301] Krita crashes when opening a file containing a fill layer
https://bugs.kde.org/show_bug.cgi?id=419301 --- Comment #5 from Franck Rabeson --- Hello. Sorry for the late response. For the sake of clarification, the layer’s entry in maindoc.xml was: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420487] Feature request: lock window geometry
https://bugs.kde.org/show_bug.cgi?id=420487 Andrew Udvare changed: What|Removed |Added Summary|Feature request: lock |Feature request: lock |window placement|window geometry -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420487] Feature request: lock window geometry
https://bugs.kde.org/show_bug.cgi?id=420487 --- Comment #1 from Andrew Udvare --- To answer my last question, yes. I made a Kwin script to implement this feature. https://github.com/Tatsh/kwin-lock-window-placement/blob/master/contents/code/main.js -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 420493] Events fire only on key-press instead of on key-release, impossible to blank screen on keypress.
https://bugs.kde.org/show_bug.cgi?id=420493 Vincenzo Di Massa changed: What|Removed |Added CC||hawk...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 420493] Events fire only on key-press instead of on key-release, impossible to blank screen on keypress.
https://bugs.kde.org/show_bug.cgi?id=420493 Vincenzo Di Massa changed: What|Removed |Added Summary|Events fire only key-press |Events fire only on |instead of key-release, |key-press instead of on |impossible to blank screen |key-release, impossible to |on keypress.|blank screen on keypress. -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 420493] New: Events fire only key-press instead of key-release, impossible to blank screen on keypress.
https://bugs.kde.org/show_bug.cgi?id=420493 Bug ID: 420493 Summary: Events fire only key-press instead of key-release, impossible to blank screen on keypress. Product: khotkeys Version: 5.18.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@michael-jansen.biz Reporter: hawk...@tiscali.it Target Milestone: --- SUMMARY Can't blank screen with hotkey meta+k. STEPS TO REPRODUCE 1. configure a hotkey (meta+k) to blank screen (xrandr script, powerdevil, dbus, ...) 2. press the hotkey untill and release it after some time (the problem i evident when you release the key when the screen is already powering off) OBSERVED RESULT As soon as you press the key the monitor powers off. When you release the keys on the keyboard the release event wakes up the screen again. EXPECTED RESULT There are two valit behaviors: 1) When you release the keys on the keyboard the keyboard-release-event wakes off the screen (not the key-press-event). 2) (in this case the bug should be assigned to powerdevil) a keyboard realease event should never wake up the screen. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-48-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,1 GiB of RAM ADDITIONAL INFORMATION Would be nice to have the option to configure an action to be fired on on keyboard-release-events. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420490] KStars crashes on start of INDI server
https://bugs.kde.org/show_bug.cgi?id=420490 --- Comment #3 from RD Beck --- Found issue with arduino devices causing problems after updating to 1.8.5, I can confirm that it appears to be the arduino which was causing my problems. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] New: 20.04.0 significantly slows down mouse scrolling
https://bugs.kde.org/show_bug.cgi?id=420492 Bug ID: 420492 Summary: 20.04.0 significantly slows down mouse scrolling Product: okular Version: 20.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: dragonrmar...@gmail.com Target Milestone: --- SUMMARY 20.04.0 update breaks fast scrolling in Okular. Most noticeable with a "hyperscroll" mouse wheel. STEPS TO REPRODUCE 1. open any PDF or EPub file in 20.04.0 2a. with a hyperscroll mouse, free scroll the mouse wheel inside the document panel 2b. with a normal mouse, scroll as fast as possible inside the document window 3. downgrade to 1.9.3 and repeat step 2 OBSERVED RESULT Scrolling the same amount of clicks scrolls down less lines in 20.04.0 compared to 1.9.3. Scrolling with a hyperscroll wheel significantly limits the speed of scrolling to make free scrolling unusable. This bug is only observed when scrolling in the document panel. Scrolling in the navigation panel or in the scrollbar on the right produces the expected scroll speed. EXPECTED RESULT The scroll speed in the document panel is as fast as in the other panels and keeps the same speed as 1.9.3 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.4.1-1 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION Mouse: Logitech G502 with free scroll also tested with a generic mouse with normal scroll wheel videos of the scrolling attached: https://youtu.be/wIts9r-meME https://youtu.be/nfDjuFkjQLE -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420051] Reference Images disappear when using compositions
https://bugs.kde.org/show_bug.cgi?id=420051 vanyossi changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||ghe...@gmail.com Ever confirmed|0 |1 --- Comment #1 from vanyossi --- I can reproduce this issue. 1. Create a new composition if there is none. 2. Add a reference image if there is none. 3. activate the composition (double click) 4. pan canvas. RESULT: Reference images dissapear. Krita 4.2.9 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420490] KStars crashes on start of INDI server
https://bugs.kde.org/show_bug.cgi?id=420490 --- Comment #2 from RD Beck --- Running with either EQMOD or Moonlite with simulators results in crashes. Running with Moonlight and simulators: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdcb6f4bac0 (LWP 6680))] Thread 15 (Thread 0x7fdc9d928700 (LWP 6723)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fdcbc42f081 in QSemaphore::acquire(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fdcbc61f875 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x564ab36bdb76 in ClientManager::newINDIDevice (this=this@entry=0x564ab90705f0, _t1=, _t1@entry=0x7fdc8c003fc0) at ./obj-x86_64-linux-gnu/kstars/KStarsLib_autogen/FRI4DANIHA/moc_clientmanager.cpp:333 #4 0x564ab373a19f in ClientManager::newDevice (this=0x564ab90705f0, dp=0x7fdc8c0e0f50) at ./kstars/indi/clientmanager.cpp:86 #5 0x564ab3cda0b7 in INDI::BaseClient::addDevice(xml_ele_*, char*) () #6 0x564ab3cda242 in INDI::BaseClient::findDev(xml_ele_*, int, char*) () #7 0x564ab3cdb36d in INDI::BaseClient::dispatchCommand(xml_ele_*, char*) () #8 0x564ab3cdc007 in INDI::BaseClient::listenINDI() () #9 0x564ab3cdc19c in INDI::BaseClient::listenHelper(void*) () #10 0x564ab3cdc1db in std::thread::_State_impl > >::_M_run() () #11 0x7fdcbba68f74 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7fdcbbdd9669 in start_thread (arg=) at pthread_create.c:479 #13 0x7fdcbb758323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fdc69ffe700 (LWP 6696)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fdc69ffda10, clockid=, expected=0, futex_word=0x7fdc6c003454) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fdc69ffda10, clockid=, mutex=0x7fdc6c003400, cond=0x7fdc6c003428) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fdc6c003428, mutex=0x7fdc6c003400, abstime=0x7fdc69ffda10) at pthread_cond_wait.c:656 #3 0x7fdcbc432d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdcbc432e7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdcbc430421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdcbc42cc92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdcbbdd9669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fdcbb758323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fdc6bfff700 (LWP 6695)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fdc6bffea10, clockid=, expected=0, futex_word=0x7fdc94009754) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fdc6bffea10, clockid=, mutex=0x7fdc94009700, cond=0x7fdc94009728) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fdc94009728, mutex=0x7fdc94009700, abstime=0x7fdc6bffea10) at pthread_cond_wait.c:656 #3 0x7fdcbc432d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdcbc432e7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdcbc430421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdcbc42cc92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdcbbdd9669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fdcbb758323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fdc73fff700 (LWP 6694)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fdc73ffea10, clockid=, expected=0, futex_word=0x7fdc94009344) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fdc73ffea10, clockid=, mutex=0x7fdc940092f0, cond=0x7fdc94009318) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fdc94009318, mutex=0x7fdc940092f0, abstime=0x7fdc73ffea10) at pthread_cond_wait.c:656 #3 0x7fdcbc432d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdcbc432e7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdcbc430421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdcbc42cc92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdcbbdd9669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fdcbb758323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fdc7bfff700 (LWP 6693)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fdc7bffea10, clockid=, expected=0, futex_word=0x7fdc94012254) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common
[frameworks-kwallet] [Bug 420491] New: kwallet - data loss of all passwords
https://bugs.kde.org/show_bug.cgi?id=420491 Bug ID: 420491 Summary: kwallet - data loss of all passwords Product: frameworks-kwallet Version: 5.69.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: va...@kde.org Reporter: k...@aschoettler.com CC: kdelibs-b...@kde.org Target Milestone: --- After the KDE frameworks were updated, all existing passwords in kwallet were lost. The existing file kdewallet.kwl was overwritten empty. A backup had to be restored. Otherwise, all passwords will be lost forever. STEPS TO REPRODUCE 1. Update kwallet to 5.69.0 2. Reboot system 3. kwalletd asks for creating a new wallet and immediately deletes the existing wallet OBSERVED RESULT All stored passwords in kwallet are lost/deleted EXPECTED RESULT No critical data loss! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375220] mouse wheel scrolling broken after update to 16.12
https://bugs.kde.org/show_bug.cgi?id=375220 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420490] KStars crashes on start of INDI server
https://bugs.kde.org/show_bug.cgi?id=420490 --- Comment #1 from RD Beck --- Failure appears to be related to my normal imaging setup -- EQMOD, Moonlite, ZWO cameras(2), ZWO EFW EKOS / INDI appears to work with simulators. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420490] New: KStars crashes on start of INDI server
https://bugs.kde.org/show_bug.cgi?id=420490 Bug ID: 420490 Summary: KStars crashes on start of INDI server Product: kstars Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: b...@ripabe.net Target Milestone: --- Application: kstars (3.4.2) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-46-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I started KStars, clicked on the EKOS icon, confirmed the correct configuration was selected and clicked on start. No devices are scheduled to be connected at start up. - Unusual behavior I noticed: Immediately after the INDI control panel is visible on the screen, I get the message that KStars has crashed and all the windows disappear. - Custom settings of the application: This is the same setup I used in 1.8.4 The crash can be reproduced every time. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe5eebeaac0 (LWP 3823))] Thread 15 (Thread 0x7fe59700 (LWP 3839)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fe59fffea10, clockid=, expected=0, futex_word=0x555d2f8dbe14) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fe59fffea10, clockid=, mutex=0x555d2f8dbdc0, cond=0x555d2f8dbde8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x555d2f8dbde8, mutex=0x555d2f8dbdc0, abstime=0x7fe59fffea10) at pthread_cond_wait.c:656 #3 0x7fe5f40d1d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe5f40d1e7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5f40cf421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe5f40cbc92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe5f3a78669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fe5f33f7323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fe5afffd700 (LWP 3838)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fe5afffca10, clockid=, expected=0, futex_word=0x555d2fac57c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fe5afffca10, clockid=, mutex=0x555d2fac5770, cond=0x555d2fac5798) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x555d2fac5798, mutex=0x555d2fac5770, abstime=0x7fe5afffca10) at pthread_cond_wait.c:656 #3 0x7fe5f40d1d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe5f40d1e7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5f40cf421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe5f40cbc92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe5f3a78669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fe5f33f7323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fe5b1ffe700 (LWP 3837)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fe5b1ffda10, clockid=, expected=0, futex_word=0x555d2fe8f430) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fe5b1ffda10, clockid=, mutex=0x555d2fe8f3e0, cond=0x555d2fe8f408) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x555d2fe8f408, mutex=0x555d2fe8f3e0, abstime=0x7fe5b1ffda10) at pthread_cond_wait.c:656 #3 0x7fe5f40d1d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe5f40d1e7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5f40cf421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe5f40cbc92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe5f3a78669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fe5f33f7323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fe5b3fff700 (LWP 3836)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fe5b3ffea10, clockid=, expected=0, futex_word=0x555d2ff4b850) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fe5b3ffea10, clockid=, mutex=0x555d2ff4b800, cond=0x555d2ff4b828) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x555d2ff4b828, mutex=0x555d2ff4b800, abstime=0x7fe5b3ffea10) at pthread_cond_wait.c:656 #3 0x7fe5f40d1d2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x
[krita] [Bug 419529] Text Tool broken
https://bugs.kde.org/show_bug.cgi?id=419529 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #4 from vanyossi --- This just happened to me under multiple monitors. The text editor is opened in the second monitor at max width and height. On macos, my test machine, the text editor does not dissapear, however after the first usage any call after that shows the editor in the last position before closing. The first odd position and size can be recreated by renaming kritarc and opening text tool on a multiple monitor setup. I cannot test multiple monitor on Linux or Windows. The monitor/cable combination does not work to get a second display. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420489] New: a new brush bundle is not showing on the brush presets
https://bugs.kde.org/show_bug.cgi?id=420489 Bug ID: 420489 Summary: a new brush bundle is not showing on the brush presets Product: krita Version: 4.2.9 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: gusdue...@gmail.com Target Milestone: --- SUMMARY The brushes and bundles doesn't show of in Krita 4.2.9, It loads the bundle but the brushes does not show in the brushes pannel under any category STEPS TO REPRODUCE 1. download the brushes of david revoe 2. went to setting/manage resources 3. load the bundle and nothing happens after OBSERVED RESULT The brushes are no show in the Krita Brush Preset EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420450] Wayland: Switching compositor backend causes Task Switcher (alt+tab) to have black background
https://bugs.kde.org/show_bug.cgi?id=420450 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Possible duplicate of bug 415798 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420488] New: Wrong accelerator and shortcut keys specified in Kirigami-based apps
https://bugs.kde.org/show_bug.cgi?id=420488 Bug ID: 420488 Summary: Wrong accelerator and shortcut keys specified in Kirigami-based apps Product: frameworks-kirigami Version: 5.68.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: k...@peremen.name Target Milestone: Not decided Created attachment 127813 --> https://bugs.kde.org/attachment.cgi?id=127813&action=edit Discover's Korean screenshot, where accelerator keys are misallocated SUMMARY While this bug do not exist in QWidgets based applications, but Kirigami based applications seems to have the accelerator bug. Attached here is configuration dialog of Dolphin and update dialog of Discover, using QWidgets and Kirigami respectively. In Dolphin's dialog, only the translated message of "Switch between split views panes with tab key" has its accelerator key assigned, as only that item of the configuration dialog has alphabet. All other texts are using 100% Hangul, so no accelerator keys were added. That actually hurts usability (no accelerator keys available for Korean users) but I think this should be discussed in another bug. On the other hand, in Discover's update dialog, accelerator keys are allocated to composed Hangul which could not be used as an accelerator key. Only the translated message of "Plasma Addons" has alphabets in this case. All others are using 100% Hangul, but accelerator keys are nevertheless allocated. This is clearly a bug. Note that I checked the behavior of KHangMan's settings dialog which is using Qt Quick but not Kirigami, and the said accelerator key problem is not present there. STEPS TO REPRODUCE 1. Launch any app using Kirigami and translated into Korean with LANG=ko_KR.UTF-8 2. Press Alt key to see the accelerator key OBSERVED RESULT When pressing Alt key, there is also underlines in Hangul characters. This is unacceptable as there is basically no way to press such accelerator key. Also in case of Plasma Discovery, there are shortcut keys with Hangul such as "Alt+설" displayed, but there is basically no way to press short cut key either. EXPECTED RESULT No Hangul characters should be underlined and used as an accelerator key. Usually translations will specifiy the accelerators separate from the main text. Kirigami should pick up accelerators only from [A-Za-z]. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409814] Reply-to SMS box is incorrectly opened when a single-sign-on SMS with a "Copy" button is clicked
https://bugs.kde.org/show_bug.cgi?id=409814 Simon Redman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||b59ef618b2809b709e3f833fb0e ||c1b3005decaa9 Resolution|--- |FIXED --- Comment #6 from Simon Redman --- This should be fixed with commit b59ef618b2809b709e3f833fb0ec1b3005decaa9 (https://invent.kde.org/kde/kdeconnect-kde/commit/b59ef618b2809b709e3f833fb0ec1b3005decaa9) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420487] New: Feature request: lock window placement
https://bugs.kde.org/show_bug.cgi?id=420487 Bug ID: 420487 Summary: Feature request: lock window placement Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: audv...@gmail.com Target Milestone: --- SUMMARY I often want to lock a window so I cannot accidentally move/resize it especially if it has a grabber somewhere besides the title bar such as the bottom right corner. Setting up a rule for this in settings makes the rule basically permanent. It is not easy to add and remove rules as needed, nor is it quick. I want to be able to enable/disable this quickly, such as in the context menu in the title bar, under More Actions, if there was an option: Lock size/placement This would set the window to be not moveable and not resizeable. PS I've not done much KDE development especially not with Kwin but I wouldn't mind attempting to put something together for this. Also, can this be achieved with a Kwin script? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419118] System settings crash while opening translucency config
https://bugs.kde.org/show_bug.cgi?id=419118 pierovisc...@gmail.com changed: What|Removed |Added CC||pierovisc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #16 from luancarvalho --- Nate Graham's comment actually encouraged me to setup a KDE dev-env to write a patch regarding this bug, and perhaps start contributing a bit to KDE development in general. Yes, sure. I will make sure to test the import vault implementation. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 420486] New: Bump Qt5 requirement to match other packages requirements
https://bugs.kde.org/show_bug.cgi?id=420486 Bug ID: 420486 Summary: Bump Qt5 requirement to match other packages requirements Product: kdesrc-build Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: luancarvalhomart...@gmail.com Target Milestone: --- Created attachment 127811 --> https://bugs.kde.org/attachment.cgi?id=127811&action=edit Trivial patch bumping Qt5 to 5.14.2 SUMMARY kdesrc-build master branch builds Qt5 5.13, but some packages require 5.14 (eg: ksysguard; commit: 5559e2ed7d78bd47d0c1499d93e54b7c07b6a80c). Fix is trivial. A patch is attached. STEPS TO REPRODUCE 1. git clone https://anongit.kde.org/kdesrc-build.git 2. cd kdesrc-build 3. ./kdesrc-build --initial-setup 4. source ~/.bashrc 5. kdesrc-build plasma-desktop plasma-workspace plasma-framework plasma-nm plasma-pa plasma-thunderbolt plasma-vault plasma-workspace-wallpapers kdeplasma-addons kwin systemsettings kscreen breeze discover kinfocenter --include-dependencies OBSERVED RESULT Build of ksysguard and other packages fails with version of Qt5 <= 5.14 EXPECTED RESULT Building of all packages working. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: System installed Qt5 is 5.12.8, but I am not using it. kdesrc-build is building 5.13, but it should build version >= 5.14 ADDITIONAL INFORMATION Please, find a (trivial) patch attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390713] Change in "Touch Screen" KCM only takes effect after relogin
https://bugs.kde.org/show_bug.cgi?id=390713 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Patrick Silva --- cannot reproduce. Possibly fixed by https://phabricator.kde.org/D27862 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419051] Discover won't open
https://bugs.kde.org/show_bug.cgi?id=419051 Damian Sánchez changed: What|Removed |Added CC||dami2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 420364] Kontact window has wrong title
https://bugs.kde.org/show_bug.cgi?id=420364 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kon ||tact/a62c89751bff05c87ed6aa ||a868d51bb38ba8c7e8 --- Comment #3 from David Faure --- Git commit a62c89751bff05c87ed6aaa868d51bb38ba8c7e8 by David Faure. Committed on 23/04/2020 at 23:11. Pushed by dfaure into branch 'master'. Adjust caption handling after the switch from ReadOnlyPart to Part. KParts::ReadOnlyPart::guiActivateEvent is no longer called, so nothing clears the window title anymore. Just detect that the plugin didn't touch it. OpenQA rocks (as well as Fabian for submitting bug reports when OpenQA detects a regression). M +4-3src/mainwindow.cpp https://commits.kde.org/kontact/a62c89751bff05c87ed6aaa868d51bb38ba8c7e8 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 420364] Kontact window has wrong title
https://bugs.kde.org/show_bug.cgi?id=420364 David Faure changed: What|Removed |Added Assignee|kdepim-b...@kde.org |fa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 420364] Kontact window has wrong title
https://bugs.kde.org/show_bug.cgi?id=420364 --- Comment #2 from David Faure --- Oh, wait, I get it. The switch from KParts::ReadOnlyPart to KParts::Part made us lose the automatic caption handling that was happening in KParts::ReadOnlyPart::guiActivateEvent. How unexpected ;) Oh well, it's cleaner this way. I'll fix it. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 420364] Kontact window has wrong title
https://bugs.kde.org/show_bug.cgi?id=420364 --- Comment #1 from David Faure --- I confirm, but I'm surprised that it's a regression (IOW I wonder how it ever worked). Does openQA have the information of what was the last version where it worked? (Qt5, KF5, kdepim -- I suspect the change was either in KF5 or in Qt5) Excellent GUI regression system you guys have, in any case. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Franco Pellegrini changed: What|Removed |Added Resolution|UPSTREAM|--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Franco Pellegrini --- I disagree... the issue I am reporting is not that cryfs crashes, but instead that the UI does not provide any error to the user whatsoever. I agree that if cryfs crashes it is an issue that cryfs should fix, but in any case, the enduser does not care, he should know at the very least that his encrypted folder failed to be mounted, and get a minimum idea on why... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420485] New: Support JMAP
https://bugs.kde.org/show_bug.cgi?id=420485 Bug ID: 420485 Summary: Support JMAP Product: Akonadi Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: timo...@eastlincoln.net Target Milestone: --- SUMMARY JMAP is a new standard for email developed by the IETF. See https://jmap.io for more information about JMAP. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420454] Option to add a touchpad hotkey missing
https://bugs.kde.org/show_bug.cgi?id=420454 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Nate Graham --- (In reply to Postix from comment #2) > "KDE Daemon" is definitely a bad name. What will it be called in the future? "Touchpad" :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418662] Some system tray icons seem to choose the wrong color/become invisible
https://bugs.kde.org/show_bug.cgi?id=418662 --- Comment #8 from Nate Graham --- Argh, now I can't reproduce it anymore! :( -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #30 from Nate Graham --- *observation that when users are restive like this, it's something that ought to be listened to, even if sometimes they express themselves harshly. You need to look past that and see the underlying problem that they're complaining about. I personally happen to agree with the complaints. In my experience, some of the KMail developers have not been interested in listening to VDG recommendations or respecting the community-set goals. Like I said, KMail can evolve, or it can become obsolete. If you don't pick the former, the latter happens by default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420322] Krita crashing instantly on certain files
https://bugs.kde.org/show_bug.cgi?id=420322 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Dmitry Kazakov --- *** This bug has been marked as a duplicate of bug 419301 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419301] Krita crashes when opening a file containing a fill layer
https://bugs.kde.org/show_bug.cgi?id=419301 Dmitry Kazakov changed: What|Removed |Added CC||triggerpigking@protonmail.c ||om --- Comment #4 from Dmitry Kazakov --- *** Bug 420322 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419301] Krita crashes when opening a file containing a fill layer
https://bugs.kde.org/show_bug.cgi?id=419301 --- Comment #3 from Dmitry Kazakov --- Okay, the file is not needed, I can reproduce the crash in a unittest -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #29 from Nate Graham --- You know, it's been my -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 417248] html file received a perl file icon if it has "use strict" or "use warnings" in it
https://bugs.kde.org/show_bug.cgi?id=417248 --- Comment #14 from David Faure --- Bastien: OK. I thought this one was pretty non-controversial, but I'll use merge requests in the future. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kbookmarks] [Bug 419981] With KBookmarks >= 5.69, Ctrl+B standard KDE shortcut overrides Konsole shortcut settings
https://bugs.kde.org/show_bug.cgi?id=419981 bjoe...@arcor.de changed: What|Removed |Added CC||bjoe...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420484] New: Entering a string in the search field of the message list crashes the application
https://bugs.kde.org/show_bug.cgi?id=420484 Bug ID: 420484 Summary: Entering a string in the search field of the message list crashes the application Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: acra...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open kmail. 2. Enter a string in the message list search field. 3. Hit enter. OBSERVED RESULT Application crash. EXPECTED RESULT Filter the message list according to search term. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.18 User Edition / 5.18.4 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420408] Part of the letters disappear
https://bugs.kde.org/show_bug.cgi?id=420408 --- Comment #2 from sebastian labi --- No, it is a rare bug, because it only does it with a few fonts, all of them are similar. I leave you a recording of the bug. maybe it's not a matter of urgency. https://youtu.be/f9qaJ_lUSgU I am not using appimage, I installed from the ppa service -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419301] Krita crashes when opening a file containing a fill layer
https://bugs.kde.org/show_bug.cgi?id=419301 --- Comment #2 from Dmitry Kazakov --- Btw, the layer you removed doesn't seem to be a "Fill Layer". Perhaps it was a Paint Layer with Colorize Mask attached? At least the contents of Layer26 you attached looks as if it was filled with colorize mask and then rasterized... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419301] Krita crashes when opening a file containing a fill layer
https://bugs.kde.org/show_bug.cgi?id=419301 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com --- Comment #1 from Dmitry Kazakov --- Hi, Franck! Is it possible to share the entire original file with me? If it is private, you can sent it me to an email: dimula73 at gmail dot com. This bug seem to be ralated to: https://bugs.kde.org/show_bug.cgi?id=420322 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #15 from Ivan Čukić --- You can test how well the current implementation of importing works, and then we could think of a way to expose it to the user without it being overly accessible for the reasons mentioned before. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Ivan Čukić --- In general, if cryfs crashed, than it is an upstream issue. I'd advise you to update to cryfs 0.10 as this issue has been resolved. If it happens again after the update, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420483] New: crashes on attempt to open
https://bugs.kde.org/show_bug.cgi?id=420483 Bug ID: 420483 Summary: crashes on attempt to open Product: kdenlive Version: 20.04.0 Platform: Other OS: other Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: e...@acm.org Target Milestone: --- SUMMARY I have updated from the following repositories allowing vendor change - 1 | http-download.opensuse.org-125fad39 | KDE:Applications | Yes | (r ) Yes | Yes 2 | http-download.opensuse.org-12c7f429 | KDE:Frameworks5| Yes | (r ) Yes | Yes 3 | http-download.opensuse.org-76fddd53 | KDE:Qt5| Yes | (r ) Yes | Yes 4 | openSUSE-Leap-15.1-1| openSUSE-Leap-15.1-1 | Yes | (r ) Yes | Yes 5 | opensuse-guide.org-repo | Libdvdcss Repository | Yes | (r ) Yes | Yes 6 | packman.inode.at-suse | Packman Repository | Yes | (r ) Yes | Yes 7 | repo-debug | Debug Repository | Yes | (r ) Yes | Yes 8 | repo-debug-non-oss | Debug Repository (Non-OSS) | Yes | (r ) Yes | Yes 9 | repo-debug-update | Update Repository (Debug) | Yes | (r ) Yes | Yes 10 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | Yes | (r ) Yes | Yes 11 | repo-non-oss| Non-OSS Repository | Yes | (r ) Yes | Yes 12 | repo-oss| Main Repository| Yes | (r ) Yes | Yes 13 | repo-source | Source Repository | Yes | (r ) Yes | Yes 14 | repo-source-non-oss | Source Repository (Non-OSS)| Yes | (r ) Yes | Yes 15 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes 16 | repo-update-non-oss | Update Repository (Non-Oss)| Yes | (r ) Yes | Yes STEPS TO REPRODUCE 1. attempt to open kdenlive 2. 3. OBSERVED RESULT blink and error message EXPECTED RESULT SOFTWARE/OS VERSIONS see repository list above Suse Leap 15.1 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.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 --- Comment #28 from Parker --- Do that. Kick me out for telling the truth. It's good to know how things work around here. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419461] Audio out of sync in rendered output
https://bugs.kde.org/show_bug.cgi?id=419461 --- Comment #10 from alridd...@googlemail.com --- I've sent the file to your address via WeTransfer. Many thanks for taking a look. Do let me know if there is anything else I can do to help. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #27 from Allen Winter --- Enough. Parker will be banned. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420482] New: Kdenlive installed via snap can't access vaapi
https://bugs.kde.org/show_bug.cgi?id=420482 Bug ID: 420482 Summary: Kdenlive installed via snap can't access vaapi Product: kdenlive Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: nicocarb...@gmail.com Target Milestone: --- SUMMARY I have kdenlive (recently updated to 20.04) installed via snap. When I try to enable vaapi acceleration, it says it is not available. Installing Kdenlive via flatpak or .deb allows me to enable vaapi in the same PC. Not having vaapi acceleration in kdenlive is a really big handicap of the snap version. As an example, obs-studio snap can access vaapi both for encoding and decoding. STEPS TO REPRODUCE 1. Install kdenlive via snap 2. Try to enable vaapi OBSERVED RESULT Kdenlive says vaapi is not available. EXPECTED RESULT Vaapi is enabled and works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 ADDITIONAL INFORMATION Installed via snap. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420482] Kdenlive installed via snap can't access vaapi
https://bugs.kde.org/show_bug.cgi?id=420482 Nicolás Abel Carbone changed: What|Removed |Added CC||nicocarb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420480] Okular crashed after opening a file in Wayland
https://bugs.kde.org/show_bug.cgi?id=420480 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- There's a fatal message being printed according to the backtrace. If you open it from a terminal what message do you get when it crashes? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418662] Some system tray icons seem to choose the wrong color/become invisible
https://bugs.kde.org/show_bug.cgi?id=418662 --- Comment #7 from Konrad Materka --- I was not able to reproduce again... Does it happen for only this icon or all SNI icons? In my case all SNI icons were not rendering. Is the icon visible in System Tray settings? What happens is you force-hide it in settings? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412579] kmail notifications should take you to the actual email when clicked
https://bugs.kde.org/show_bug.cgi?id=412579 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #26 from Parker --- @Laurent Montel, you seem to keep developing kmail as a karma you've acquired. Why don't you give it up and get on with your life? Let someone else who really has an interest and passion for what you do take care of it. You treat people as inferior and disagree with all your opinions. I don't think the KDE community can be contaminated with toxic people like you. Btw, I've never seen any KDE application have so many bugs and not work like KMail. KDE really needs an e-mail client. I don't understand how this is not prioritized. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417667] Bad allocation crash
https://bugs.kde.org/show_bug.cgi?id=417667 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/ef3c9fe7199886 |krita/commit/06fc241c21454e |ba4f089694a042bcb154b46003 |97cfc22d4042bda6ba2b8799ba --- Comment #13 from Dmitry Kazakov --- Git commit 06fc241c21454e97cfc22d4042bda6ba2b8799ba by Dmitry Kazakov. Committed on 23/04/2020 at 20:53. Pushed by dkazakov into branch 'krita/4.3'. Fix crash when applying liquify transformation via Transform Mask We must not access Qt containers in non-const manner in multithreaded environment. Qt has lazy sharing routines, which are not thread safe. M +19 -0libs/global/kis_algebra_2d.h M +5-11 libs/image/kis_liquify_transform_worker.cpp https://invent.kde.org/kde/krita/commit/06fc241c21454e97cfc22d4042bda6ba2b8799ba -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417667] Bad allocation crash
https://bugs.kde.org/show_bug.cgi?id=417667 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/ef3c9fe7199886 ||ba4f089694a042bcb154b46003 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Dmitry Kazakov --- Git commit ef3c9fe7199886ba4f089694a042bcb154b46003 by Dmitry Kazakov. Committed on 23/04/2020 at 20:52. Pushed by dkazakov into branch 'master'. Fix crash when applying liquify transformation via Transform Mask We must not access Qt containers in non-const manner in multithreaded environment. Qt has lazy sharing routines, which are not thread safe. M +19 -0libs/global/kis_algebra_2d.h M +5-11 libs/image/kis_liquify_transform_worker.cpp https://invent.kde.org/kde/krita/commit/ef3c9fe7199886ba4f089694a042bcb154b46003 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420462] Make selected tool in Review pane more visible on Breeze dark
https://bugs.kde.org/show_bug.cgi?id=420462 --- Comment #2 from Postix --- (In reply to Nate Graham from comment #1) > Will be fixed by https://invent.kde.org/kde/okular/-/merge_requests/105 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415199] Okular doesn't show digital signatures without visible component
https://bugs.kde.org/show_bug.cgi?id=415199 Albert Astals Cid changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REPORTED --- Comment #4 from Albert Astals Cid --- Sadly the fix in poppler required new API so that means we also need to change Okular :( -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420481] New: Dolphin hangs on leaving (!) big directories on a network share
https://bugs.kde.org/show_bug.cgi?id=420481 Bug ID: 420481 Summary: Dolphin hangs on leaving (!) big directories on a network share Product: dolphin Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: virusma...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have a cifs mounted directory (/mnt/share) with 700+ sub directories (/mnt/share/sub1, /mnt/share/sub2 etc) with only few files under. Going inside of that directory (/mnt/share) happens immediately, but clicking on the sub directory takes 3-4 seconds. Also going from /mnt/share to /mnt also takes the same amount of the time. So exiting directory hangs, but entering it happens quick. STEPS TO REPRODUCE 1. Mount cifs share with 700+ subfolders sudo mount -t cifs //192.168.1.20/share/ /mnt/share -o username=user,password="pass",workgroup=workgroup,iocharset=utf8,uid=1000,gid=1000 2. Go inside of /mnt/share - it happens immediately 3. Enter any subfolder or click mnt /mnt - dolphin hangs for 3-4 seconds OBSERVED RESULT Dolphin hangs for 3-4 seconds EXPECTED RESULT Dolphin opens sub directory immediately SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Also tried with most current development version of KDE Neon Live CD - the same result ADDITIONAL INFORMATION Previews are disabled, columns with size and recent edit are hidden. In konsole everything works quick - cd works immediately. Thunar also works fast. I would understand a slowdown on enter a directory, but on leave? I tried to include logs, but there is no dbg version of Dolphin, so the instruction on wiki didn't work. Tried to run it with dbg, but Dolphin forked out and --no-fork parameter doesn't exist anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420454] Option to add a touchpad hotkey missing
https://bugs.kde.org/show_bug.cgi?id=420454
--- Comment #2 from Postix ---
(In reply to Nate Graham from comment #1)
> I see one such option ("Toggle Touchpad" in System Settings > Shortcuts >
> KDE Daemon. Do you see that?
>
> "KDE Daemon" is a bad name, but that was just fixed today. :)
Yes, thanks found it.
I thought I had filtered the hotkeys for "touchpad" but I might have had a typo
I didn't notice.
"KDE Daemon" is definitely a bad name. What will it be called in the future?
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 419461] Audio out of sync in rendered output
https://bugs.kde.org/show_bug.cgi?id=419461 --- Comment #9 from Jean-Baptiste Mardelle --- Hello and thanks a lot for your detailed report. Could you share the project clip for this project so that I can investigate ? You can send me a mail at my @kdenlive.org address for the file link. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 272730] Sidebar does not adjust scroll area size automatically
https://bugs.kde.org/show_bug.cgi?id=272730 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||7.0.0 Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #7 from Maik Qualmann --- No feedback and the problem cannot be reproduced with digiKam-7.0.0-Beta3. I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420480] New: Okular crashed after opening a file in Wayland
https://bugs.kde.org/show_bug.cgi?id=420480 Bug ID: 420480 Summary: Okular crashed after opening a file in Wayland Product: okular Version: 1.9.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: okular (1.9.3) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.6.5 x86_64 Windowing system: Wayland Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: I am using Wayland and Sway WM 1.4. Okular crashed right after opening a file. -- Backtrace: Application: Okular (okular), signal: Aborted Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4c72c4cc0 (LWP 1106384))] Thread 17 (Thread 0x7fb4a97fa700 (LWP 1106400)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cbc78, cond=0x55c5e77cbca0) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e72f1850) at ../mesa-20.0.5/src/util/u_queue.c:275 #3 0x7fb4be7fe387 in impl_thrd_routine (p=) at ../mesa-20.0.5/include/c11/threads_posix.h:87 #4 0x7fb4ca12e02a in start_thread () from /usr/lib64/libpthread.so.0 #5 0x7fb4ca91926f in clone () from /usr/lib64/libc.so.6 Thread 16 (Thread 0x7fb4a9ffb700 (LWP 1106399)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cbc78, cond=0x55c5e77cbca0) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e72aef30) at ../mesa-20.0.5/src/util/u_queue.c:275 #3 0x7fb4be7fe387 in impl_thrd_routine (p=) at ../mesa-20.0.5/include/c11/threads_posix.h:87 #4 0x7fb4ca12e02a in start_thread () from /usr/lib64/libpthread.so.0 #5 0x7fb4ca91926f in clone () from /usr/lib64/libc.so.6 Thread 15 (Thread 0x7fb4aa7fc700 (LWP 1106398)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cbc78, cond=0x55c5e77cbca0) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e74244d0) at ../mesa-20.0.5/src/util/u_queue.c:275 #3 0x7fb4be7fe387 in impl_thrd_routine (p=) at ../mesa-20.0.5/include/c11/threads_posix.h:87 #4 0x7fb4ca12e02a in start_thread () from /usr/lib64/libpthread.so.0 #5 0x7fb4ca91926f in clone () from /usr/lib64/libc.so.6 Thread 14 (Thread 0x7fb4aaffd700 (LWP 1106397)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cbc78, cond=0x55c5e77cbca0) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e7424490) at ../mesa-20.0.5/src/util/u_queue.c:275 #3 0x7fb4be7fe387 in impl_thrd_routine (p=) at ../mesa-20.0.5/include/c11/threads_posix.h:87 #4 0x7fb4ca12e02a in start_thread () from /usr/lib64/libpthread.so.0 #5 0x7fb4ca91926f in clone () from /usr/lib64/libc.so.6 Thread 13 (Thread 0x7fb4ab7fe700 (LWP 1106396)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cb570, cond=0x55c5e77cb598) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e73e63b0) at ../mesa-20.0.5/src/util/u_queue.c:275 #3 0x7fb4be7fe387 in impl_thrd_routine (p=) at ../mesa-20.0.5/include/c11/threads_posix.h:87 #4 0x7fb4ca12e02a in start_thread () from /usr/lib64/libpthread.so.0 #5 0x7fb4ca91926f in clone () from /usr/lib64/libc.so.6 Thread 12 (Thread 0x7fb4b0ff9700 (LWP 1106395)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cb570, cond=0x55c5e77cb598) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e73e6190) at ../mesa-20.0.5/src/util/u_queue.c:275 #3 0x7fb4be7fe387 in impl_thrd_routine (p=) at ../mesa-20.0.5/include/c11/threads_posix.h:87 #4 0x7fb4ca12e02a in start_thread () from /usr/lib64/libpthread.so.0 #5 0x7fb4ca91926f in clone () from /usr/lib64/libc.so.6 Thread 11 (Thread 0x7fb4b17fa700 (LWP 1106394)): #0 0x7fb4ca134957 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib64/libpthread.so.0 #1 0x7fb4be7fe77b in cnd_wait (mtx=0x55c5e77cb570, cond=0x55c5e77cb598) at ../mesa-20.0.5/include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55c5e723d9e0) at ../mesa
[krita] [Bug 419918] Krita crashes on my Mac
https://bugs.kde.org/show_bug.cgi?id=419918 vanyossi changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from vanyossi --- Chevy: Could you test this dmg can be debugged? https://drive.google.com/open?id=1xn6eDKG-jPoYqDCdV2mBP2pAVkQcM9dk If you can, then try to get a log. Instructions: https://docs.krita.org/en/reference_manual/sharing_krita_logs.html#getting-backtrace-mac (you may need to install or enable development features first). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 420287] KFontChooser sometimes selects a non-regular style by default
https://bugs.kde.org/show_bug.cgi?id=420287 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Priority|NOR |VHI Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||n...@kde.org --- Comment #2 from Nate Graham --- I'm not seeing that the above commit fixed the issue. Opening the Fonts dialog in the Fonts KCM still results in "SemiCondensed" being set by default, and if you don't change it, you'll get very narrow fonts when you click OK. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417075] pwritev(vector[...]) suppression ignored
https://bugs.kde.org/show_bug.cgi?id=417075 --- Comment #11 from Philippe Waroquiers --- Updated the warning message to be: ==3170== WARNING: preadv(vector[...]) is an obsolete suppression line not supported anymore since valgrind 3.15. ==3170== You should replace [...] by a specific index such as [0] or [1] or [2] or similar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418662] Some system tray icons seem to choose the wrong color/become invisible
https://bugs.kde.org/show_bug.cgi?id=418662 --- Comment #6 from Nate Graham --- I just had this happen when I changed the Media Player plasmoid's tray icon to be "Always shown" or "Shown when relevant" and the relevancy condition triggers (i.e. I start playing a song). I usually have it always hidden. Making it appear in the visible part of the tray triggers this bug for me. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417075] pwritev(vector[...]) suppression ignored
https://bugs.kde.org/show_bug.cgi?id=417075 --- Comment #10 from Philippe Waroquiers --- Some further notes: I should re-update the warning to replace the final 'or ...' by 'or [2]. And I sincerely hope that nobody is using preadv and pwritev wrongly with huge vectors, as otherwise they might need to type a lot of supp entries. (that is in fact a main reason to avoid variable extra error lines ...) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417075] pwritev(vector[...]) suppression ignored
https://bugs.kde.org/show_bug.cgi?id=417075 --- Comment #9 from Philippe Waroquiers --- Created attachment 127809 --> https://bugs.kde.org/attachment.cgi?id=127809&action=edit not a fix, but detects the incompatible supp entry and produce a warning The commit log explains in details what we envisaged, and why the decision is to keep what 3.15 accepts instead of rolling back the change in 3.15 or make the error matching logic even more complex -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420476] Krita canvas wont let me draw or use any tools but after clicking outside of canvas the drawings will appear
https://bugs.kde.org/show_bug.cgi?id=420476 Rebecca Breu changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||rebe...@rbreu.de Resolution|--- |WAITINGFORINFO --- Comment #1 from Rebecca Breu --- Does it help if you go to Settings -> Configure Krita -> Display -> Canvas Acceleration and there set the Renderer from OpenGL to Angle (or vice versa) and then restart Krita? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420430] Inconsistent behavior of View tab of Metadata dialog in digiKam Configure menu
https://bugs.kde.org/show_bug.cgi?id=420430 Maik Qualmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/73e05f198293 ||82f9f7e7252590a1ae3b006802d ||7 Resolution|--- |FIXED Version Fixed In||7.0.0 --- Comment #3 from Maik Qualmann --- Git commit 73e05f19829382f9f7e7252590a1ae3b006802d7 by Maik Qualmann. Committed on 23/04/2020 at 20:05. Pushed by mqualmann into branch 'master'. fix filter in the metadata view FIXED-IN: 7.0.0 M +2-1NEWS M +4-2core/libs/widgets/metadata/metadatalistview.cpp https://invent.kde.org/kde/digikam/commit/73e05f19829382f9f7e7252590a1ae3b006802d7 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 droidSumit changed: What|Removed |Added CC||droidsu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 420479] Impossible to save data
https://bugs.kde.org/show_bug.cgi?id=420479 --- Comment #3 from Pierre --- I would like to be able to save the data I entered, not loose them ... I am available right now and if you have time and want to take hold on my machine, please let me know -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 420479] Impossible to save data
https://bugs.kde.org/show_bug.cgi?id=420479 --- Comment #2 from Pierre --- Hi I have many 10-ths of Gbytes and the file is less than 10 Mb 544 -rwxrwxrwx 1 pedro users 9768978 avril 13 08:21 comptes.skg 9564 -rwxrwxrwx 1 pedro pedro 9792530 avril 13 08:21 comptes.skg.old -- You are receiving this mail because: You are watching all bug changes.
