[plasma-browser-integration] [Bug 476367] Default-Browser
https://bugs.kde.org/show_bug.cgi?id=476367 --- Comment #4 from Thomas Vatter --- Not my opinion. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476367] Default-Browser
https://bugs.kde.org/show_bug.cgi?id=476367 --- Comment #3 from Nate Graham --- That's for you to do. :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476367] Default-Browser
https://bugs.kde.org/show_bug.cgi?id=476367 --- Comment #2 from Thomas Vatter --- Shouldn't the developers of Konqueror or Falkon forward this to OpenSuSE? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474752] Bounce keys does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=474752 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476451] Compilation error with OpenJPEG
https://bugs.kde.org/show_bug.cgi?id=476451 --- Comment #2 from Halla Rempt --- Ah, I saw https://invent.kde.org/graphics/krita/-/merge_requests/1985 only after the bug report. Was there a problem with that patch? Please if you submit a merge request and a bug report at the same time, make sure they link to each other... -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil-5.27.9 fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #7 from Nate Graham --- That commit is master-only; it's not present on the 5.27 branch: https://invent.kde.org/plasma/powerdevil/-/commits/Plasma%2F5.27 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil-5.27.9 fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #6 from Natalie Clarius --- (In reply to Natalie Clarius from comment #5) > (In reply to Nate Graham from comment #3) > > The only substantive change in 5.27.9 compared to 5.27.8 is > > https://invent.kde.org/plasma/powerdevil/-/commit/ > > d176188ff9b573a784905cada8824897af86b34b, which doesn't look related to me > > (but I could be wrong; CCing the author). > > > https://invent.kde.org/plasma/powerdevil/-/commit/ > a8cbb0bb82d3efe42e1190c75ba0c0023433d924 seems related, but that would > already have been present in Plasma 5.27.9-1, right? Ignore me, shouldn't be in 5.27 at all of course -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476451] Compilation error with OpenJPEG
https://bugs.kde.org/show_bug.cgi?id=476451
Halla Rempt changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|--- |WAITINGFORINFO
CC||ha...@valdyas.org
--- Comment #1 from Halla Rempt ---
I'm afraid that this really is something that users of the Nix platform or the
Nix krita package maintainer need to investigate in way more detail, preferably
proposing a patch that doesn't break other platforms. None of the Krita
developers use Nix nor do we use platform builds of Krita.
It might be related or the same as the issue that prevents the openjpeg plugin
to be built on FreeBSD, but since the same holds for FreeBSD as for Nix (i.e.,
users of the platform need to fix the issue, because it's not a platform any of
use use), and nobody stepped up to help out, I was forced to disable the plugin
on freebsd:
commit 0018d78eeb099aaff7c606b75588cf1b07fe51dd
Author: Halla Rempt
Date: Fri Nov 22 15:08:29 2019 +0100
Don't build the jp2 plugin on freebsd
It's broken, and I don't know why.
diff --git a/plugins/impex/CMakeLists.txt b/plugins/impex/CMakeLists.txt
index 80961161b5..499b1c97d0 100644
--- a/plugins/impex/CMakeLists.txt
+++ b/plugins/impex/CMakeLists.txt
@@ -27,7 +27,7 @@ if(Poppler_Qt5_FOUND)
add_subdirectory(pdf)
endif()
-if(OpenJPEG_FOUND)
+if(OpenJPEG_FOUND AND NOT ${CMAKE_SYSTEM_NAME} STREQUAL "FreeBSD")
add_subdirectory(jp2)
endif()
I'm not dismissing the issue, but without access to and knowledge of the
platform, we cannot begin to guess why cmake/modules/FindOpenJPEG.cmake
apparently doesn't provide the right include paths. Best would be to contact
the authors of the Krita nix package first, and then come back to us with more
information.
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil-5.27.9 fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #5 from Natalie Clarius --- (In reply to Nate Graham from comment #3) > The only substantive change in 5.27.9 compared to 5.27.8 is > https://invent.kde.org/plasma/powerdevil/-/commit/ > d176188ff9b573a784905cada8824897af86b34b, which doesn't look related to me > (but I could be wrong; CCing the author). https://invent.kde.org/plasma/powerdevil/-/commit/a8cbb0bb82d3efe42e1190c75ba0c0023433d924 seems related, but that would already have been present in Plasma 5.27.9-1, right? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476454] New: Attempting to undo after changing animation layers sometimes results in crash
https://bugs.kde.org/show_bug.cgi?id=476454 Bug ID: 476454 Summary: Attempting to undo after changing animation layers sometimes results in crash Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: alexsmudg...@gmail.com Target Milestone: --- SUMMARY When using the "Animation" workspace, if you make a change in your document (e.g. drawing a line), change layer, and then undo once or several times, occasionally the program crashes. STEPS TO REPRODUCE 1. Use the "Animation" workspace 2. Draw lines or perform some action on the canvas 3. Change the current layer 4. Perform the Undo action. I AM NOT ENTIRELY CERTAIN THE CONDITIONS WHICH THIS ERROR OCCURS IN. I cannot get it to reproduce consistently. You may have more luck if you switch the positions of step 2 and 3. You may need to perform further testing to reproduce this crash and find its conditions. OBSERVED RESULT The program immediately closes and all of your unsaved documents are lost. EXPECTED RESULT The program should not crash. Krita Version: 5.1.5 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19045 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Crash Log: Error occurred on Thursday, November 2, 2023 at 14:41:57. krita.exe caused an Access Violation at location 7FFEFEF5FA1C in module libkritaimage.dll Writing to location 00A0. AddrPC Params 7FFEFEF5FA1C 02B92C0D3DC0 7FFF0082D47D 02B92BDF8EB0 libkritaimage.dll!KisPaintDeviceFramesInterface::setFrameOffset+0x8c 7FFEFEF95EF8 02B92BFBAA30 7FFEFAEEE001 7FFEFF12F368 libkritaimage.dll!KisTransactionData::undo+0x128 7FFF3C9F9D17 02B9 02B9274B9100 2710AA00 libkritacommand.dll!KisCommandUtils::CompositeCommand::undo+0xd7 7FFF3C9F2E70 0001 libkritacommand.dll!KUndo2Command::undo+0x30 7FFEFED1FE4E 7FFEFAEEE0A0 00BFAB2FFD88 libkritaimage.dll!KisUpdateCommand::undo+0xe 7FFEFEE668C4 02B92C5270C0 7FFF 00010007 libkritaimage.dll!KisStrokeStrategyUndoCommandBased::doStrokeCallback+0xb4 7FFEFEC7E102 02B92BDCE8B0 02B9 libkritaimage.dll!KisUpdateJobItem::run+0x132 7FFEFAEEFFAD Qt5Core.dll!QThreadPoolThread::run+0xad -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 470485] Settings lack persistence
https://bugs.kde.org/show_bug.cgi?id=470485 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474563] Crash after changing audio effect channel layout from stereo to mono with LADPSA plugins
https://bugs.kde.org/show_bug.cgi?id=474563 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 467137] [Mobile] Audio coming out of bottom speaker on phone *extremely* quiet.
https://bugs.kde.org/show_bug.cgi?id=467137 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475179] Horizontal line when opening SpeedCrunch
https://bugs.kde.org/show_bug.cgi?id=475179 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 469461] After the update on the kernel 6.1 and 6.3 (I think it will be the same for others), the wallet began to fail wildly. It either decrypts the data or it doesn’t. I think i
https://bugs.kde.org/show_bug.cgi?id=469461 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil-5.27.9 fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #4 from Natalie Clarius --- I can't reproduce this with the given versions of ddcutil and powerdevil. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475725] 搜索中文错误
https://bugs.kde.org/show_bug.cgi?id=475725 --- 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.
[krita] [Bug 475453] Krita closes by it self
https://bugs.kde.org/show_bug.cgi?id=475453 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475588] after selecting a layer, cannot change brush size
https://bugs.kde.org/show_bug.cgi?id=475588 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475173] Kdenlive crash on startup
https://bugs.kde.org/show_bug.cgi?id=475173 --- 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.
[krita] [Bug 470870] My brush is always set on eraser even though it is set on pencil. I use a double sided pen that flips from pencil to eraser but both sides are eraser. I've tried to reset my compu
https://bugs.kde.org/show_bug.cgi?id=470870 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471641] Some krita gmic-qt filters like burn give an extremely cryptic and hard to figure out error
https://bugs.kde.org/show_bug.cgi?id=471641 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475112] Brush outline not rendering if brush tip 100% white
https://bugs.kde.org/show_bug.cgi?id=475112 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473943] filter mask error if we filter max again the image in animation play
https://bugs.kde.org/show_bug.cgi?id=473943 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469217] 23.04.0 is leading to "INVALID" renders and corrupted files
https://bugs.kde.org/show_bug.cgi?id=469217 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472518] I was trying to export my art and and error came up saying it was having trouble opening up the file, plus saying it could not read the pixel data. WHY?!
https://bugs.kde.org/show_bug.cgi?id=472518 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468263] bundle brushes not all loaded after installing
https://bugs.kde.org/show_bug.cgi?id=468263 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467692] If I create a new window, my workspace changes from before, especially in the left workspace, also a hand icon cursor appears when drawing even though it is not using the pan tool
https://bugs.kde.org/show_bug.cgi?id=467692 --- 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.
[kwin] [Bug 474430] Tiny cursor on Firefox when using scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=474430 --- Comment #6 from Joe --- So, my previous bug was closed and marked duplicate of this - which seems correctly. Just wanted to bring up the other half of my report which is the video can 'jump' a bit when moving the mouse (and it becomes the right size again). I have noticed the same frame jumping/slight ghosting also in two Proton steam games (Rome 2 Total War & Attila Total War) where the cursor is fine, but I get the jumping/frame ghosting. Switching them from full screen to windowed and the ghosting stops. At this point not sure if they are related - or if I should create a separate bug for this side of my original report. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 476453] New: plasmashell crash crashes DrKonqi
https://bugs.kde.org/show_bug.cgi?id=476453
Bug ID: 476453
Summary: plasmashell crash crashes DrKonqi
Classification: Applications
Product: drkonqi
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: natalie_clar...@yahoo.de
Target Milestone: ---
STEPS TO REPRODUCE
1. https://bugs.kde.org/show_bug.cgi?id=476452
OBSERVED RESULT
DrKonqi crashes
SOFTWARE/OS VERSIONS
KDE git master
Qt 6.6.0
Arch
Wayland
ADDITIONAL INFORMATION
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0)
at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {92}}
ret =
#1 0x7ffa4a8ac8a3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2 0x7ffa4a85c668 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
ret =
#3 0x7ffa4dde7c57 in KCrash::defaultCrashHandler(int) (sig=6)
at /home/natalie/kde/src/kcrash/src/kcrash.cpp:597
data = { = {_vptr.MetadataWriter =
0x7ffa4ddf3bd8 }, argv = {_M_elems = {0x0,
0x7ffa4ddee326 "--platform", 0x55f850874710 "wayland", 0x7ffa4ddee351
"--appname", 0x55f850678f20 "drkonqi", 0x7ffa4ddee365 "--apppath",
0x55f8505f4000 "/home/natalie/kde/usr/lib/libexec", 0x7ffa4ddee372 "--signal",
0x7fff70a0c736 "6", 0x7ffa4ddee380 "--pid", 0x7fff70a0c740 "62129",
0x7ffa4ddee386 "--appversion", 0x55f850659050 "5.27.80", 0x7ffa4ddee393
"--programname", 0x55f8506375c0 "Crash Handler", 0x7ffa4ddee3a1 "--bugaddress",
0x55f850685410 "sub...@bugs.kde.org", 0x0 }}, argc = 17,
m_writer = 0x7fff70a0c320}
platformName = {d = {d = 0x55f850874700, ptr = 0x55f850874710
"wayland", size = 7}, static _empty = 0 '\000'}
about = 0x55f850678080
argv = 0x7fff70a0c218
ini = { = {_vptr.MetadataWriter =
0x7ffa4ddf3c08 }, writable = false, fd
= 34, iniLine = {_M_elems =
"bugaddress=sub...@bugs.kde.org\n\000b/libexec\n\000qi\n", '\000' }}
sigtxt = "6\000\000\000\000\000\000\000\000"
pidtxt = "62129", '\000'
argc = 17
crashRecursionCounter = 2
#4 0x7ffa4a85c710 in () at /usr/lib/libc.so.6
#5 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0)
at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {140712330805752}}
ret =
#6 0x7ffa4a8ac8a3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#7 0x7ffa4a85c668 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#8 0x7ffa4a8444b8 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {94524991294576, 3, 0, 94524991295776, 140712980964328,
140735082974976, 140735082975056, 140711989534544, 140711989894828,
140735082985712, 140713027928812, 3, 140713027939708, 140735082975352,
140712975801809, 0}}, sa_flags = 3, sa_restorer = 0x7fff70a0cf50}
#9 0x7ffa4aeb3924 in qAbort() ()
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/global/qglobal.cpp:161
buf = {d = {d = 0x55f850874c60, ptr = 0x55f850874c70 u"ASSERT:
\"m_theme\" in file
/home/natalie/kde/src/qqc2-desktop-style/plugin/kquickstyleitem.cpp, line 160",
size = 103}, static _empty = 0 u'\000'}
#10 qt_message_fatal (message=..., context=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/global/qlogging.cpp:2030
buf = {d = {d = 0x55f850874c60, ptr = 0x55f850874c70 u"ASSERT:
\"m_theme\" in file
/home/natalie/kde/src/qqc2-desktop-style/plugin/kquickstyleitem.cpp, line 160",
size = 103}, static _empty = 0 u'\000'}
#11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *)
--Type for more, q to quit, c to continue without paging--
(msgType=msgType@entry=QtFatalMsg, context=..., msg=,
ap=ap@entry=0x7fff70a0cf90)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/global/qlogging.cpp:378
buf = {d = {d = 0x55f850874c60, ptr = 0x55f850874c70 u"ASSERT:
\"m_theme\" in file
/home/natalie/kde/src/qqc2-desktop-style/plugin/kquickstyleitem.cpp, line 160",
size = 103}, static _empty = 0 u'\000'}
#12 0x7ffa4aeb4135 in QMessageLogger::fatal(char const*, ...) const
(this=, msg=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/global/qlogging.cpp:901
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fff70a0d070, reg_save_area = 0x7fff70a0cfb0}}
#13 0x7ffa4aeb2770 in qt_assert(char const*, char const*, int)
(assertion=, file=, line=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.0/src/corelib/global/qassert.cpp:68
#14 0x7ffa247c1b6b in KQuickStyleItem::initStyleOption()
[plasmashell] [Bug 476452] New: Right-clicking in containment crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=476452 Bug ID: 476452 Summary: Right-clicking in containment crashes plasmashell Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: natalie_clar...@yahoo.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 162813 --> https://bugs.kde.org/attachment.cgi?id=162813=edit Full Backtrace STEPS TO REPRODUCE 1. Right-click on wallpaper or panel OBSERVED RESULT Plasmashell crashes, reproducible everytime SOFTWARE/OS VERSIONS git master Only happens on Wayland ADDITIONAL INFORMATION See backtrace. (Would have pasted it in the comment but it exceeds the character limit) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476451] New: Compilation error with OpenJPEG
https://bugs.kde.org/show_bug.cgi?id=476451 Bug ID: 476451 Summary: Compilation error with OpenJPEG Classification: Applications Product: krita Version: 5.2.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: n...@nek0.eu Target Milestone: --- Created attachment 162812 --> https://bugs.kde.org/attachment.cgi?id=162812=edit Compilation error SUMMARY When compiling krita 5.2.0 through nix (see https://github.com/nek0/nixpkgs/tree/krita_5_2_0/pkgs/applications/graphics/krita for the nix buiild files used) I run into the attached error STEPS TO REPRODUCE 1. check out branch from github 2. run 'nix-build default.nix -A krita' 3. see the compilation break at roughly 75% OBSERVED RESULT Compilation breaks EXPECTED RESULT Compilation succeeds SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: NixOS 23.11pre (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476170] Widgets on the bottom panel do not increase in size
https://bugs.kde.org/show_bug.cgi?id=476170 --- Comment #7 from moni...@tutanota.com --- (In reply to Nate Graham from comment #6) > That's the entire thing? Yes, I only found this file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476450] New: Global animation speed setting no longer affects smooth scrolling
https://bugs.kde.org/show_bug.cgi?id=476450 Bug ID: 476450 Summary: Global animation speed setting no longer affects smooth scrolling Classification: Frameworks and Libraries Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Other Status: REPORTED Keywords: accessibility, qt6, regression Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: qydwhotm...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided SUMMARY After Kirigami platform plugin was renamed, WheelHandler no longers receives longDuration updates from the platform Units. STEPS TO REPRODUCE 1. Adjust animation speed in systemsettings 2. Test scrolling up and down 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: kirigami at 5892e5b39c265acf06e6cea166a173aaa994cb96 Qt Version: 6.6.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[isoimagewriter] [Bug 476449] New: Add an option to restore the drive to a storage drive
https://bugs.kde.org/show_bug.cgi?id=476449 Bug ID: 476449 Summary: Add an option to restore the drive to a storage drive Classification: Applications Product: isoimagewriter Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: j...@jriddell.org Reporter: jus...@kde.org Target Milestone: --- It would be great if isoimagewriter could be used to "restore" the drive to a regular storage drive (with a small selection of file systems) for users that don't know about partitions. The file system list could easily be ext4 and NTFS with a small explanation that NTFS will work on Linux and Windows, ext4 only on Linux. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476448] New: Kmail Crashes while checking email
https://bugs.kde.org/show_bug.cgi?id=476448 Bug ID: 476448 Summary: Kmail Crashes while checking email Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: billyh...@billyhoya.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadi_imap_resource (5.24.1 (23.08.1)) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.8-200.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Kmail crashes when clicking the check email button. Restarting app does not resolve issue. Restarting does. The crash can be reproduced every time. -- Backtrace: Application: billyhoya.com (billyhoya) (akonadi_imap_resource), signal: Segmentation fault [KCrash Handler] #4 0x7f44e3cd7239 in Akonadi::Collection::hasAttribute(QByteArray const&) const () from /lib64/libKPim5AkonadiCore.so.5 #5 0x7f44e3f74c45 in (anonymous namespace)::sortCollectionsForSync(Akonadi::Collection const&, Akonadi::Collection const&) [clone .lto_priv.0] () from /lib64/libKPim5AkonadiAgentBase.so.5 #6 0x7f44e3f8483a in void std::__introsort_loop::iterator, int, __gnu_cxx::__ops::_Iter_comp_iter >(QTypedArrayData::iterator, QTypedArrayData::iterator, int, __gnu_cxx::__ops::_Iter_comp_iter) [clone .constprop.0] () from /lib64/libKPim5AkonadiAgentBase.so.5 #7 0x7f44e3f76a79 in Akonadi::ResourceBasePrivate::slotLocalListDone(KJob*) () from /lib64/libKPim5AkonadiAgentBase.so.5 #8 0x7f44e22e8481 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f44e3b95666 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #10 0x7f44e3b9b52b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #11 0x7f44e22ded2b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f44e2faeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f44e22b41a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f44e22b7655 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #15 0x7f44e2306c5f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #16 0x7f44e14e04fc in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7f44e153e6b8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #18 0x7f44e14ddb83 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7f44e2306749 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f44e22b2b6b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7f44e22badfb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #22 0x555cd988bd09 in main () [Inferior 1 (process 8284) detached] The reporter indicates this bug may be a duplicate of or related to bug 476421. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 476447] New: About Elisa only present in desktop interface, not mobile.
https://bugs.kde.org/show_bug.cgi?id=476447 Bug ID: 476447 Summary: About Elisa only present in desktop interface, not mobile. Classification: Applications Product: Elisa Version: 23.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: jus...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Switch to mobile interface 2. Try to open about OBSERVED RESULT No About dialog option EXPECTED RESULT About dialog option -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442312] No "About KDE" dialogue in hamburger menu
https://bugs.kde.org/show_bug.cgi?id=442312 Justin Zobel changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Justin Zobel --- It is now present but only in desktop mode. I will open a new bug report for the mobile interface. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 476417] country(territory) code list is out of sync with qlocale_data_p.h
https://bugs.kde.org/show_bug.cgi?id=476417 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kholidays/-/commit/7 ||20f63bc02b5d1f416a4f0fe2df5 ||a3b5a81dea62 Status|ASSIGNED|RESOLVED Version Fixed In||6.0 Resolution|--- |FIXED --- Comment #2 from Fushan Wen --- Git commit 720f63bc02b5d1f416a4f0fe2df5a3b5a81dea62 by Fushan Wen. Committed on 01/11/2023 at 15:46. Pushed by fusionfuture into branch 'master'. HolidayRegion: sync territory_code_list with qlocale_data_p.h FIXED-IN: 6.0 M +96 -92 src/holidayregion.cpp https://invent.kde.org/frameworks/kholidays/-/commit/720f63bc02b5d1f416a4f0fe2df5a3b5a81dea62 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 Erec changed: What|Removed |Added CC||ere...@polywog.org -- You are receiving this mail because: You are watching all bug changes.
[krecorder] [Bug 476446] New: dont change folder for save file
https://bugs.kde.org/show_bug.cgi?id=476446 Bug ID: 476446 Summary: dont change folder for save file Classification: Applications Product: krecorder Version: 23.08.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: espi...@gmail.com Reporter: supo...@indexdata.com.br Target Milestone: --- Created attachment 162811 --> https://bugs.kde.org/attachment.cgi?id=162811=edit dont change folder for paste file, dont have folder default Music in my language, but have folder Musica! After generating the audio file, the program does not allow changing the folder where the file will be saved, consequently it does not play. STEPS TO REPRODUCE 1. speak some text 2. save the file 3. choose the folder..YOU CANNOT CHOOSE A FOLDER OTHER THAN THE STANDARD "MUSIC FOLDER", WHICH DOESN'T EXIST! OBSERVED RESULT WORKS GOOD, BUT DOESN'T CHANGE THE DEFAULT FOLDER EXPECTED RESULT YOU CAN SAVE IN ANOTHER FOLDER SOFTWARE/OS VERSIONS GNU/Linux KDu8.0-Final Revisao 4d - Kernel: 6.5.7-060507-generic (64-bit) Linux/KDE Plasma: KDE Neon 5.27 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Runing in GNU/Linux KDu8.0 - www.linux-kdu.com.br - https://sourceforge.net/projects/kduxp/ -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 476392] Scanning music popup text is not aligned nicely
https://bugs.kde.org/show_bug.cgi?id=476392 --- Comment #4 from Justin Zobel --- I was running a released version but I couldn't tell you what version because there's no about option on mobile for Elisa (separate bug filed about that already). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476442] Maximizing Discover window leaves a visible stripe of 1-2 pixels of the wallpaper showing through on the right side
https://bugs.kde.org/show_bug.cgi?id=476442 --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! Please note that Plasma 5.26.1 will not be supported for much longer by KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to the latest version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476445] New: Power profile settings should be hidden if there are only placeholder profiles
https://bugs.kde.org/show_bug.cgi?id=476445 Bug ID: 476445 Summary: Power profile settings should be hidden if there are only placeholder profiles Classification: Applications Product: systemsettings Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: fabian.ar...@root-core.net CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 162810 --> https://bugs.kde.org/attachment.cgi?id=162810=edit Combobox with single item SUMMARY The UI elements for power profiles should be hidden if there are only placeholder profiles. The same behaviour is used in the Battery & Brightness applet. Currently you end up with a combobox containing a single item. STEPS TO REPRODUCE Open the KCM, while having only the placeholder profiles. OBSERVED RESULT There are UI elements for power profile settings. EXPECTED RESULT There should not be UI elements for power profile settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Developer Edition KDE Plasma Version: 6.0 - master ADDITIONAL INFORMATION https://invent.kde.org/plasma/powerdevil/-/merge_requests/259#note_795081 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476444] SDDM theme chooser glitches when installing two themes at once
https://bugs.kde.org/show_bug.cgi?id=476444 --- Comment #1 from Reuben --- Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476444] New: SDDM theme chooser glitches when installing two themes at once
https://bugs.kde.org/show_bug.cgi?id=476444 Bug ID: 476444 Summary: SDDM theme chooser glitches when installing two themes at once Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Created attachment 162809 --> https://bugs.kde.org/attachment.cgi?id=162809=edit showing issue SUMMARY STEPS TO REPRODUCE 1. Startup & Shutdown > Login Screen 2. Get new SDDM themes 3. Click install on theme A and wait for evidence that something is happening 4. Click install on theme B OBSERVED RESULT Theme B eventually sort of half installs. There's a green checkmark on it, but it isn't (and doesn't become) available in the options in the main window. 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.
[kde] [Bug 476443] SDDM theme chooser is very laggy, frequently loses images it had already displayed
https://bugs.kde.org/show_bug.cgi?id=476443 Reuben changed: What|Removed |Added Summary|SDDM theme chooser is very |SDDM theme chooser is very |laggy, frequently loses |laggy, frequently loses |images it had already |images it had already |disaplyed |displayed -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476443] New: SDDM theme chooser is very laggy, frequently loses images it had already disaplyed
https://bugs.kde.org/show_bug.cgi?id=476443 Bug ID: 476443 Summary: SDDM theme chooser is very laggy, frequently loses images it had already disaplyed Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@flavor8.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Be on a 15Mb connection 2. Go to settings, startup & shutdown, Login Screen 3. Click Get new SDDM themes Browse OBSERVED RESULT This UI could really use some love. The previews are a) very slow to download (which might be my current slow connection), but just scrolling around, it frequently decides to throw away all the preview images it has already rendered and re-render them. EXPECTED RESULT More slickness. It would also be lovely if there were a handful of pro themes in there, but that's an aside. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476364] Incorrectly styled font selector
https://bugs.kde.org/show_bug.cgi?id=476364 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-integration/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476442] New: Maximizing Discover window leaves a visible stripe of 1-2 pixels of the wallpaper showing through on the right side
https://bugs.kde.org/show_bug.cgi?id=476442 Bug ID: 476442 Summary: Maximizing Discover window leaves a visible stripe of 1-2 pixels of the wallpaper showing through on the right side Classification: Applications Product: Discover Version: 5.26.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: sunsp...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When Discover window is maximized it does not cover the screen entirely. STEPS TO REPRODUCE 1. System set to 150% scaling/144 logical dpi 2. Maximize Discover window OBSERVED RESULT A stripe of wallpaper pixels is visible along the entire right side of the screen. EXPECTED RESULT For the wallpaper not to be visible, as is the case with other apps. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.11 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve37-1-neptune (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456718] Window activation policy description label not initialized on opening the KCM
https://bugs.kde.org/show_bug.cgi?id=456718 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/40a4f4c90b ||f4c0a5c54640db652afda1286bc ||e6b Version Fixed In||6.0 Resolution|--- |FIXED --- Comment #3 from Nate Graham --- Git commit 40a4f4c90bf4c0a5c54640db652afda1286bce6b by Nate Graham. Committed on 01/11/2023 at 23:41. Pushed by ngraham into branch 'master'. kcms/options: set focus policy strings on load, not just on change Right now the string is only set when the option is changed to anything else. That's fine, but we need to set it on load too, or else the user will see a placeholder string instead of the real text if they don't change anything. FIXED-IN: 6.0 M +28 -6src/kcms/options/windows.cpp M +2-0src/kcms/options/windows.h https://invent.kde.org/plasma/kwin/-/commit/40a4f4c90bf4c0a5c54640db652afda1286bce6b -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot on many laptops that support charge limits; need to write it on every boot
https://bugs.kde.org/show_bug.cgi?id=450551 Fabian Arndt changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||fabian.ar...@root-core.net Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/merge_reque ||sts/253 Assignee|plasma-b...@kde.org |fabian.ar...@root-core.net --- Comment #41 from Fabian Arndt --- There is some progress: https://invent.kde.org/plasma/powerdevil/-/merge_requests/253 Please note that this is only a draft and there are still some points open for discussion. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 474973] baloosearch (as well as Dolphin and other apps using baloo) do not find anything when serching files inside the Downloads directory
https://bugs.kde.org/show_bug.cgi?id=474973 --- Comment #27 from tagwer...@innerjoin.org --- Maybe I'm a step further. I have a system where I see the same behaviour, something I consider a remarkable step forward 8-/ Bad news is it's a "bashed about" Neon Unstable, not something I can reproduceably rebuild. Further bad news is that if I leave the configuration and test files untouched, do a "balooctl6 purge" and reindex, the behaviour goes away. That would help explain why the issue is so slippery. It also means that when you have the issue, copy your .local/share/baloo/index somewhere safe so you can go back to it. It's also quite possible that this is one cause of the problem rather then "the" cause, but what I see is: $ baloosearch -i test 144044ed0da2dd /home/test/testfiles/test.txt 14ba61fc01 /home/test/testfiles 14ba61ed0da2dd /home/test/testfiles Elapsed: 0.297092 msecs $ baloosearch -i -d /home/test/testfiles test 14ba61fc01 /home/test/testfiles Elapsed: 0.62894 msecs $ baloosearch -i -d /home/test test 14ba61fc01 /home/test/testfiles Elapsed: 0.284228 msecs $ baloosearch -i -d /home/ test 14ba61fc01 /home/test/testfiles Elapsed: 0.278637 msecs $ balooctl6 purge $ baloosearch -i test 144044ed0da2dd /home/test/testfiles/test.txt 14ba61ed0da2dd /home/test/testfiles Elapsed: 0.410179 msecs $ baloosearch -i -d /home/test/testfiles test 144044ed0da2dd /home/test/testfiles/test.txt 14ba61ed0da2dd /home/test/testfiles Elapsed: 0.307979 msecs The index has two records for the /home/test/testfiles folder with different DocIDs and the "test.txt" file was created with the new format DocID and it was not found in the search. After the reindex, it was found. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 476441] New: Kolourpaint 100% zoom appears as 200%
https://bugs.kde.org/show_bug.cgi?id=476441 Bug ID: 476441 Summary: Kolourpaint 100% zoom appears as 200% Classification: Applications Product: kolourpaint Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: sunsp...@gmail.com Target Milestone: --- SUMMARY Copying the screen with Spectacle and pasting it into Kolourpaint does not display as 100%, but rather zoomed in closer to 200%. Bug appears to be related to https://bugs.kde.org/show_bug.cgi?id=436135 STEPS TO REPRODUCE 1. Have your desktop be set to 150% zoom/144 logical dpi 2. Take a screenshot using Spectacle and copy to clipboard 3. Paste into Kolourpaint OBSERVED RESULT Kolourpaint says 100% but the zoom is closer to 200%, all the pixels are too large. EXPECTED RESULT For the image to be displayed at the same size as the screen when it was taken. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.11 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve37-1-neptune (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476376] Changing source on Kdenlive triggers sources to duplicate
https://bugs.kde.org/show_bug.cgi?id=476376 --- Comment #4 from Nate Graham --- Bugzilla makes this a bit annoying. The easiest way is to navigate to "My Bugs" on the homepage, then at the bottom of the page, click "Edit Search". In the advanced search view that appears, include all the resolution statuses. You'll end up with this: https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED_status=CONFIRMED_status=ASSIGNED_status=REOPENED_status=RESOLVED_status=NEEDSINFO_status=VERIFIED_status=CLOSED=domojestic%40gmail.com_to1=1=1=substring=OP=OP=bug_status=reporter=CP=CP=OR_id=2510261=notequals=equals_format=advanced=---=FIXED=INVALID=WONTFIX=LATER=REMIND=DUPLICATE=WORKSFORME=MOVED=UPSTREAM=DOWNSTREAM=WAITINGFORINFO=BACKTRACE=UNMAINTAINED=UNCONFIRMED=domojestic%40gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476439] Changing fonts in KDE System Settings will force hinting to true in .fonts.conf when desired result is false.
https://bugs.kde.org/show_bug.cgi?id=476439 --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! Please note that Plasma 5.26.1 will not be supported for much longer by KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to the latest version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476440] Moving panels in Storyboard Docker erases image layer data for all frames on save
https://bugs.kde.org/show_bug.cgi?id=476440 --- Comment #3 from znekityz...@gmail.com --- Created attachment 162808 --> https://bugs.kde.org/attachment.cgi?id=162808=edit An image showing the error after save -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476424] Files can't be imported to album on SMB share
https://bugs.kde.org/show_bug.cgi?id=476424 --- Comment #4 from Maik Qualmann --- A test here with an SMB share via SMB4k shows no problems importing images. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476440] Moving panels in Storyboard Docker erases image layer data for all frames on save
https://bugs.kde.org/show_bug.cgi?id=476440 --- Comment #2 from znekityz...@gmail.com --- Created attachment 162807 --> https://bugs.kde.org/attachment.cgi?id=162807=edit An image showing the the blank scenes error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476440] Moving panels in Storyboard Docker erases image layer data for all frames on save
https://bugs.kde.org/show_bug.cgi?id=476440 --- Comment #1 from znekityz...@gmail.com --- Created attachment 162806 --> https://bugs.kde.org/attachment.cgi?id=162806=edit An image showing the first step in reproducing the error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476440] New: Moving panels in Storyboard Docker erases image layer data for all frames on save
https://bugs.kde.org/show_bug.cgi?id=476440 Bug ID: 476440 Summary: Moving panels in Storyboard Docker erases image layer data for all frames on save Classification: Applications Product: krita Version: 5.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Storyboard Assignee: krita-bugs-n...@kde.org Reporter: znekityz...@gmail.com Target Milestone: --- Created attachment 162805 --> https://bugs.kde.org/attachment.cgi?id=162805=edit A .kra test file encountering the bug SUMMARY When changing the position of any two scenes using the storyboard docker, the scenes in the storyboard docker turn blank as though there is no drawings in those scenes. This appears to be an irreversable change, even putting the scenes back to where they were initially does not fix this. If the file is saved in this state, all drawing layer information is lost on all scenes and frames in the Animation Timeline. This occurs in both autosaves and normal saves, and cannot be undone. STEPS TO REPRODUCE 1. Open a document in Krita with the storyboard docker enabled 2. Create two or more scenes with art in them in the storyboard docker 3. switch the position of two scenes in the storyboard docker (at this point the scenes turn apparently blank) 4. Save the canvas and close Krita 5. Open the document in Krita either through the Recent Images window or directly from file explorer OBSERVED RESULT When two scenes in the storyboard docker switch places, all scenes in the storyboard docker (not just the two that were switched) show completely blank panels. As long as the file remains open, the drawings are still visible in the Layers panel. Upon saving, closing Krita, reopening Krita, and selecting the affected .kra file, Krita shows an error stating "There were problems opening *file directory for the affected .kra file* " and under more details "Could not load pixel data: *file name*/Layers/*names of all layers that had drawings on them* ", and all layer data across all frames is lost. EXPECTED RESULT The two panels in the storyboard docker would switch places without showing blank scenes or losing layer data after save and reopening of the file. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 5.2.0 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19045 Pretty Productname: Windows 10 Version 2009 Product Type: windows Product Version: 10 Locale Languages: en_US, en, en_Latn_US C locale: C QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 1252 (ANSI - Latin I) OpenGL Info Vendor: "Google Inc. (AMD)" Renderer: "ANGLE (AMD, AMD Radeon RX 6700 XT Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.12027.9001)" Driver version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Requested format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) GL version: 3.0 Supports deprecated functions false Is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: true Extensions: GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture GL_WEBGL_video_texture GL_EXT_EGL_image_external_wrap_modes GL_EXT_sRGB GL_EXT_texture_compression_rgtc GL_EXT_texture_format_BGRA GL_ANGLE_provoking_vertex GL_OES_texture_float GL_OES_compressed_ETC2_RGB8_texture GL_EXT_blend_minmax GL_EXT_draw_buffers_indexed GL_OES_texture_npot GL_ANGLE_client_arrays GL_NV_pack_subimage GL_OES_compressed_ETC2_RGBA8_texture GL_ANGLE_base_vertex_base_instance GL_CHROMIUM_copy_compressed_texture GL_ANGLE_texture_compression_dxt5 GL_OVR_multiview GL_EXT_texture_norm16 GL_OES_rgb8_rgba8 GL_ANGLE_framebuffer_blit GL_EXT_texture_type_2_10_10_10_REV GL_EXT_discard_framebuffer GL_NV_fence GL_EXT_multi_draw_indirect GL_ANGLE_get_tex_level_parameter
[kdenlive] [Bug 476430] No Alpha shapes in 23.08.2
https://bugs.kde.org/show_bug.cgi?id=476430 --- Comment #2 from Bernd --- (In reply to Roxane from comment #0) > Hi! It seems the Alpha shapes effect isn't in 23.08.2, for me on Windows but > I also had a comment saying they didn't have it on Linux. Is this normal and > it's never gonna come back or some sort of mistake or other? Or this: https://www.reddit.com/r/kdenlive/comments/179cowi/comment/k5oue06/?utm_source=share_medium=web2x=3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476430] No Alpha shapes in 23.08.2
https://bugs.kde.org/show_bug.cgi?id=476430 Bernd changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||bern...@yahoo.com --- Comment #1 from Bernd --- (In reply to Roxane from comment #0) > Hi! It seems the Alpha shapes effect isn't in 23.08.2, for me on Windows but > I also had a comment saying they didn't have it on Linux. Is this normal and > it's never gonna come back or some sort of mistake or other? Check this post: https://discuss.kde.org/t/alpha-shapes-mask-removed-from-kdenlive-23-08-2/6144/4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476439] New: Changing fonts in KDE System Settings will force hinting to true in .fonts.conf when desired result is false.
https://bugs.kde.org/show_bug.cgi?id=476439 Bug ID: 476439 Summary: Changing fonts in KDE System Settings will force hinting to true in .fonts.conf when desired result is false. Classification: Applications Product: systemsettings Version: 5.26.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: plasma-b...@kde.org Reporter: sunsp...@gmail.com Target Milestone: --- SUMMARY Changing fonts in KDE System Settings will force hinting to true in .fonts.conf when desired result is false. Likely regression of https://bugs.kde.org/show_bug.cgi?id=105797 STEPS TO REPRODUCE 1. Have hinting manually set to "false" in .fonts.conf 2. Change fonts in KDE System Settings OBSERVED RESULT .fonts.conf now displays "true" for hinting. EXPECTED RESULT .fonts.conf to stay as "false" for hinting if I manually defined it in the file. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.11 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve37-1-neptune (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION With the fonts I generally use and with a certain amount of understanding of how Freetype (and also the associated QT bug of always forcing AA except in some apps/areas) works, I get the best text rendering results with: hinting false, hintstyle hintfull, rgba rgb, antialias false. These 4 settings will render well like on Windows. Using hinting true will make the fonts look worse with the remaining 3 declarations. This is why I prefer hinting false. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] New: crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Bug ID: 476438 Summary: crash after login with nvidia 545.29.02 Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: spaced.wom...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.9-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: after login plasmashell crashes using latest nvidia beta driver 545.29.02 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1780 (plasmashell) UID: 1000 (adi) GID: 1000 (adi) Signal: 11 (SEGV) Timestamp: Wed 2023-11-01 22:54:03 CET (44s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (adi) Boot ID: c59c5c6ee9cd439d853aae416a6adafc Machine ID: 22b9d9d52a5e4f7cbb40ed1b383dd97c Hostname: adipc Storage: /var/lib/systemd/coredump/core.plasmashell.1000.c59c5c6ee9cd439d853aae416a6adafc.1780.169887564300.zst (present) Size on Disk: 92.5M Message: Process 1780 (plasmashell) of user 1000 dumped core. Stack trace of thread 1780: #0 0x7fb4aa691dec __pthread_kill_implementation (libc.so.6 + 0x91dec) #1 0x7fb4aa63f0c6 raise (libc.so.6 + 0x3f0c6) #2 0x7fb4ad267d9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d9a) #3 0x7fb4aa63f190 __restore_rt (libc.so.6 + 0x3f190) #4 0x7fb4aa691dec __pthread_kill_implementation (libc.so.6 + 0x91dec) #5 0x7fb4aa63f0c6 raise (libc.so.6 + 0x3f0c6) #6 0x7fb4aa63f190 __restore_rt (libc.so.6 + 0x3f190) #7 0x7fb4aa68c4ec __futex_abstimed_wait_common (libc.so.6 + 0x8c4ec) #8 0x7fb4aa68f230 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8f230) #9 0x7fb4aaf09a1b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0x109a1b) #10 0x7fb4acc3b0f8 n/a (libQt5Quick.so.5 + 0x23b0f8) #11 0x7fb4acc3be33 n/a (libQt5Quick.so.5 + 0x23be33) #12 0x7fb4ab5890a5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1890a5) #13 0x7fb4ad699bf1 _ZN11PlasmaQuick6Dialog5eventEP6QEvent (libKF5PlasmaQuick.so.5 + 0x2abf1) #14 0x7fb4abda519e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1a519e) #15 0x7fb4ab0ed198 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed198) #16 0x7fb4ab57e44d _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x17e44d) #17 0x7fb4ab55038c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x15038c) #18 0x7fb4ac9617b0 n/a (libQt5WaylandClient.so.5 + 0xbc7b0) #19 0x7fb4a9b50f30 n/a (libglib-2.0.so.0 + 0x5bf30) #20 0x7fb4a9b52b58 n/a (libglib-2.0.so.0 + 0x5db58) #21 0x7fb4a9b5320c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #22 0x7fb4ab1460d6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3460d6) #23 0x7fb4ab0ebc2b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebc2b) #24 0x7fb4ab0f40c0 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f40c0) #25 0x55780925baa1 n/a (plasmashell + 0x29aa1) #26 0x7fb4aa6281b0 __libc_start_call_main (libc.so.6 + 0x281b0) #27 0x7fb4aa628279 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x28279) #28 0x55780925be35 n/a (plasmashell + 0x29e35) Stack trace of thread 1783: #0 0x7fb4aa709d7f __poll (libc.so.6 + 0x109d7f) #1 0x7fb4a9b52aff n/a (libglib-2.0.so.0 + 0x5daff) #2 0x7fb4a9b5320c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #3
[kwin] [Bug 476102] [Wayland] Downscaled X11 Windows Look Blocky/Blurry
https://bugs.kde.org/show_bug.cgi?id=476102 --- Comment #4 from Eamonn Rea --- In case I am still not being clear enough, as I am having some trouble knowing if I'm articulating the problem correctly, here's a visual representation of the issue. I hope it serves to show that while the window *sizing* is correct, the window contents look significantly worse when an X11 application is downscaled when the "Apply scaling themselves" option is used. https://i.postimg.cc/MZLqg6Fk/Screenshot-20231101-215050.png The example here is with a Qt6 application called ProtonUp-Qt. On the left is the program running using Wayland, running from source. On the right is the Flatpak version of the tool, running with the Wayland socket disabled so it's forced to use X11. The text looks significantly worse when downscaled, more blocky and sometimes even blurry in some programs. The issue is not specific to ProtonUp-Qt, it happens with any application I can apply scaling to. Heck, even without a scale factor applied, the applications do not simply look like they're running too small on unscaled displays, they are smaller when they can't apply scaling themselves, but they also still look a little bit blocky/blurry. When both the Wayland and X11 versions of the application are running on the scaled display, aside from some font differences as a result of one running from source and one running on Flatpak, they look virtually indistinguishable even when zooming in: https://i.postimg.cc/4xgdF4Yf/Screenshot-20231101-215645.png What I'm really hoping to illustrate here is that the window sizing isn't an issue, because applications can scale themselves just fine or have a flag I can set, but that when this flag is set, application *contents* is what looks off. Hope that makes sense! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476102] [Wayland] Downscaled X11 Windows Look Blocky/Blurry
https://bugs.kde.org/show_bug.cgi?id=476102 --- Comment #3 from Eamonn Rea --- Sorry if I wasn't clear, I understand that X11 doesn't support mixed DPI. I wasn't referring to applications not scaling, I was referring to how they look visually when downscaled, is there no way to make these applications which are scaled up and then scaled down on non-scaled displays look any better visually? I am fine with applications which don't support scaling looking too small on unscaled displays, but applications which can be scaled up and moved to non-scaled displays should be filtered better in some way, no? The impact varies from application to application, for example with Steam it's generally ok, but with some other cases like Qt applications, text can be borderline-illegible when not on the display with the given scale factor. Many applications are now using Wayland, but two massive use-cases are not filled yet: The Steam Client, and games. Games running through Proton are fine because once Wine and then Proton gets Wayland support, this will be fine, but legacy games which may never get this kind of support, will consistently look blocky when downscaled. My post was not about adding mixed-scale support for X11, which is not feasible and not relevant to KDE specifically. What I was asking for is a way to make the apps which can be scaled up, look better when moved to displays which are not scaled. They match the scale factor just fine but their contents do not look visually appealing. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 103788] input of arbitrary unicode characters as defined in ISO 14755
https://bugs.kde.org/show_bug.cgi?id=103788 --- Comment #29 from Jan Rathmann --- (In reply to Nate Graham from comment #28) > Can someone explain in plain English what exactly is being requested here? > I'm not understanding what needs to be done to support it, because it isn't > clear to me what the feature is. Thanks! The feature is to be able to insert arbitrary unicode characters in text fields (or a text editor) by pressing Ctrl+Shift+u and then the hexadecimal number of the unicode character. Example: Ctrl+Shift+u + 1F600 will give you the emoji . You can test it in Firefox or other GTK-based applications. More details on https://en.wikipedia.org/wiki/Unicode_input (Note: The article claims that it is supported by Qt applications on Linux, what doesn't seem to be correct) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.
https://bugs.kde.org/show_bug.cgi?id=398582 --- Comment #65 from Maik Qualmann --- Git commit a793381d5d36e032e458941b514702df2e41b90d by Maik Qualmann. Committed on 01/11/2023 at 22:40. Pushed by mqualmann into branch 'master'. revert QIODevice Exiv2 reader/writer It is too slow over network drives. M +8-14 core/libs/metadataengine/engine/metaengine_comments.cpp M +8-14 core/libs/metadataengine/engine/metaengine_exif.cpp M +18 -28 core/libs/metadataengine/engine/metaengine_fileio.cpp M +8-14 core/libs/metadataengine/engine/metaengine_iptc.cpp M +126 -115 core/libs/metadataengine/engine/metaengine_p.cpp M +8-15 core/libs/metadataengine/engine/metaengine_previews.cpp M +8-15 core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/graphics/digikam/-/commit/a793381d5d36e032e458941b514702df2e41b90d -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476060] Setting resolution to anything less than native resolution causes screen area to be reduced, rather than content to become blurry
https://bugs.kde.org/show_bug.cgi?id=476060 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/ff2bc0798f ||e659f6388cf54b6bf3ed0a26785 ||b40 --- Comment #5 from Zamundaaa --- Git commit ff2bc0798fe659f6388cf54b6bf3ed0a26785b40 by Xaver Hugl. Committed on 01/11/2023 at 22:29. Pushed by zamundaaa into branch 'master'. backends/drm: fix properties not being applied when a modeset is not needed When testing whether or not a modeset is needed, all that gets tested is whether or not the kernel would allow the commit to happen without the ALLOW_MODESET flag. If there's properties that are only changed in DrmPipeline::prepareAtomicModeset, we need to apply those in the next commit, regardless of whether or not the ALLOW_MODESET flag is necessary. M +33 -19 src/backends/drm/drm_pipeline.cpp M +2-0src/backends/drm/drm_pipeline.h https://invent.kde.org/plasma/kwin/-/commit/ff2bc0798fe659f6388cf54b6bf3ed0a26785b40 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475667] cannot make new events in kalendar
https://bugs.kde.org/show_bug.cgi?id=475667 --- Comment #1 from goo --- i've since updated to the latest backports and backports-extra repositories and still the same behavior Operating System: Kubuntu 22.04 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 Kernel Version: 6.2.0-36-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476376] Changing source on Kdenlive triggers sources to duplicate
https://bugs.kde.org/show_bug.cgi?id=476376 --- Comment #3 from domojes...@gmail.com --- (In reply to Nate Graham from comment #2) > Yikes! > > However I'm afraid Plasma 5.24 is unfortunately no longer eligible for > support or maintenance from KDE. Plasma is a fast-moving project, and bugs > in one version are often fixed in the next one. Please update to Plasma 5.27 > as soon as your distro offers it to you. If you need support for Plasma > 5.24, please contact your distro, who bears the responsibility of providing > support for older non-LTS releases. > > If this issue is still reproducible in Plasma 5.27, feel free to re-open > this bug report. > > Thanks for understanding! Makes sense! I'm using Kubuntu LTS so I'm a bit slow to get new Plasma versions, which kinda stinks. With classes it doesn't make sense to switch distros right now, but come winter break I might take the opportunity to find something that has better access to newer Plasma versions. Might even give Neon a second shot! Though I also like the idea of an immutable distro, so perhaps BlendOS might be something I try. Thank you for the response! Unrelatedly, how can I view all the bug reports I've made in the past, even closed ones? I could only get back to this thread via an email I'd received. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.
https://bugs.kde.org/show_bug.cgi?id=430157 --- Comment #13 from Yaroslav Sidlovsky --- This code has been already included in latest kf5-kservice release (5.111.0), http://download.kde.org/stable/frameworks/5.111/kservice-5.111.0.tar.xz. ``` $ grep -Fr 'but has no Exec field' kservice-5.111.0/src/services/kservice.cpp:qCWarning(SERVICES) << "The desktop entry file" << entryPath() << "has Type=" << d->m_strType << "but has no Exec field."; ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476340] After disabling the laptop screen while an external screen is connected, disconnecting the external screen doesn't re-activate the laptop screen
https://bugs.kde.org/show_bug.cgi?id=476340 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=476412 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476412] Display freezes when reconnecting to Lenovo Thunderbolt 4 dock
https://bugs.kde.org/show_bug.cgi?id=476412 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||xaver.h...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=476342, ||https://bugs.kde.org/show_b ||ug.cgi?id=476340 Keywords||multiscreen, wayland Version|git-stable-Plasma/5.27 |5.27.9 --- Comment #2 from Nate Graham --- There are similarities to Bug 476342 and Bug 476340, which I experience on Plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476342] After disabling laptop screen while external screen is connected, re-enabling laptop screen causes a visual freeze until switching to another VT and back
https://bugs.kde.org/show_bug.cgi?id=476342 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=476412 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476345] Unmovable button bars in full screen annotation mode
https://bugs.kde.org/show_bug.cgi?id=476345 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org Version Fixed In||24.02 Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This is fixed in Spectacle 24.02. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476377] One cannot switch mplayer to full screen in Wayland session
https://bugs.kde.org/show_bug.cgi?id=476377 Nate Graham changed: What|Removed |Added CC||n...@kde.org Component|general |wayland-generic Target Milestone|1.0 |--- Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED Product|plasmashell |kwin --- Comment #1 from Nate Graham --- Works for me with mplayer-1.5.1 on Fedora KDE run on Plasma 6. If you're using an older version of mplayer, it might be that it doesn't have Wayland support yet. Regardless, this is an app issue, not a problem with Plasma or KWin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476383] Panel spacers center applets in free space, instead of in the middle of the panel
https://bugs.kde.org/show_bug.cgi?id=476383 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Keywords|regression | Status|REPORTED|CONFIRMED CC||n...@kde.org, ||nicc...@venerandi.com, ||notm...@gmail.com --- Comment #3 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476364] Incorrectly styled font selector
https://bugs.kde.org/show_bug.cgi?id=476364 --- Comment #3 from Nate Graham --- Ah right, and in Qt 6, the QML one no longer falls back to the Widgets one, right? Do we need to style it ourselves in plasma-integration or something? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476389] Missing KDE Connect icon in System Tray
https://bugs.kde.org/show_bug.cgi?id=476389 Nate Graham changed: What|Removed |Added CC||alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476389] Missing KDE Connect icon in System Tray
https://bugs.kde.org/show_bug.cgi?id=476389 Nate Graham changed: What|Removed |Added Product|plasmashell |kdeconnect Version|master |unspecified Target Milestone|1.0 |--- Component|System Tray |plasmoid Ever confirmed|0 |1 Assignee|plasma-b...@kde.org |albertv...@gmail.com CC||n...@kde.org, ||nicolas.fe...@gmx.de Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Can reproduce. Doesn't seem to be an issue with X-Plasma-NotificationAreaCategory being missing in the JSON metadata. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 --- Comment #3 from steffen-wink...@posteo.de --- While creating the screenshots I did observe something curious: If I write the text in Okular, click the show form button, close Okular and confirm that I want to save the changes to the file, then open the file in evince the text is rendered incorrectly again, if I go into the text field to edit it the text is shown correctly but regardless of what I do, change the text, remove the text and enter the same text again or leave it as it is, the characters will not be rendered anymore. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 --- Comment #2 from steffen-wink...@posteo.de --- Created attachment 162804 --> https://bugs.kde.org/attachment.cgi?id=162804=edit Actual Text that was entered into the field -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476364] Incorrectly styled font selector
https://bugs.kde.org/show_bug.cgi?id=476364 --- Comment #2 from Nicolas Fella --- (In reply to Nate Graham from comment #1) > Can reproduce. It's quite horrible now. We must be doing something wrong in > the Digital Clock code, as it works correctly in the Fonts KCM. Nothing wrong per se. The difference is that the clock code uses the QML font dialog, which has this horrible default implementation. The KCM uses KFontChooserDialog, which is widgets-based -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 --- Comment #1 from steffen-wink...@posteo.de --- Created attachment 162803 --> https://bugs.kde.org/attachment.cgi?id=162803=edit Text shown after clicking show forms again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476364] Incorrectly styled font selector
https://bugs.kde.org/show_bug.cgi?id=476364 Nate Graham changed: What|Removed |Added CC||k...@privat.broulik.de, ||n...@kde.org, ||nicolas.fe...@gmx.de Component|general |Digital Clock Ever confirmed|0 |1 Target Milestone|--- |1.0 Status|REPORTED|CONFIRMED Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Version|unspecified |master Product|kde |plasmashell --- Comment #1 from Nate Graham --- Can reproduce. It's quite horrible now. We must be doing something wrong in the Digital Clock code, as it works correctly in the Fonts KCM. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476437] New: Wrong header color on appearance section of kcm_screenlocker until window regains focus
https://bugs.kde.org/show_bug.cgi?id=476437 Bug ID: 476437 Summary: Wrong header color on appearance section of kcm_screenlocker until window regains focus Classification: Applications Product: systemsettings Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_screenlocker Assignee: plasma-b...@kde.org Reporter: guimarcalsi...@gmail.com Target Milestone: --- Created attachment 162802 --> https://bugs.kde.org/attachment.cgi?id=162802=edit Wrong header color until window regains focus SUMMARY The page header in the "Appearance" section of kcm_screenlocker has the wrong color. The problem can be corrected by clicking outside of the window and clicking on it again to make it regain focus. Check the attached screenshot. STEPS TO REPRODUCE 1. Open kcm_screenlocker 2. Click on "Appearance" OBSERVED RESULT Wrong page header color EXPECTED RESULT Same header color as all other KCMs SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Graphics Platform: Wayland ADDITIONAL INFORMATION Running on a VM. Terminal output after opening, clicking on Appearance, clicking outside and clicking inside the window: file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/private/globaltoolbar/PageRowGlobalToolBarUI.qml:5 5:5: QML Rectangle: Cannot specify top, bottom, and verticalCenter anchors at the same time. qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_objectN ame" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_Preview ImageDefault" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_Preview Image" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_objectN ameChanged" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_valueCh anged" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_keys" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_isImmut able" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg_writeCo nfig" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___0" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___1" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___2" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___3" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___4" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___5" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___6" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___7" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___8" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___9" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___10" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___11" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___12" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___13" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___14" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___15" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___16" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___17" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___18" qrc:/kcm/kcm_screenlocker/WallpaperConfig.qml:35: Error: Cannot assign to non-existent property "cfg___19" qrc:/kcm/kcm_screenlocker/LnfConfig.qml:31: Error: Cannot assign to non-existent property "cfg_objectName" qrc:/kcm/kcm_screenlocker/LnfConfig.qml:31: Error: Cannot assign to non-existent property "cfg_objectNameCha nged" qrc:/kcm/kcm_screenlocker/LnfConfig.qml:31: Error: Cannot assign to non-existent property "cfg_valueChanged"
[systemsettings] [Bug 476437] Wrong header color on appearance section of kcm_screenlocker until window regains focus
https://bugs.kde.org/show_bug.cgi?id=476437 guimarcalsi...@gmail.com changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476436] New: German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 Bug ID: 476436 Summary: German umlaute are not shown in textfields in this PDF document Classification: Applications Product: okular Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: steffen-wink...@posteo.de Target Milestone: --- Created attachment 162801 --> https://bugs.kde.org/attachment.cgi?id=162801=edit PDF that contains form fields SUMMARY I've attached a PDF that contains text fields that can be filled out. When doing this using Okular I can enter German umlaute like äöü and the special character ß, but once I switch back to the default view those characters are no longer visible and something like "Straße" becomes "Strae". If I open the same PDF in Gnome's Evince the characters are shown as expected. STEPS TO REPRODUCE 1. Open PDF 2. Click "Show Forms" 3. Enter "Straße äöü" in any of the fields 4. Press "Show Forms" again OBSERVED RESULT The text "Straße äöü" becomes "Strae " EXPECTED RESULT The text should be "Straße äöü" SOFTWARE/OS VERSIONS Linux: 6.5.9-arch2-1 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 476435] New: In the advanced settings, entering a tracker list URL has no effect
https://bugs.kde.org/show_bug.cgi?id=476435 Bug ID: 476435 Summary: In the advanced settings, entering a tracker list URL has no effect Classification: Applications Product: ktorrent Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: coocoola...@protonmail.ch Target Milestone: --- SUMMARY In the advanced settings, I have tried using URLs that pull a list of trackers' URLS when used with wget or pasted in a browser's address bar. Example: https://newtrackon.com/api/stable However, nothing happens, no trackers are added, whether I just wait or go in the tracker down panel and click on "add trackers" or "update trackers". The only I could find to add those trackers was using the URL with wget or a browser, copy the output, click on "add trackers" in the tracker down panel, see how the copied list of URL is already pasted in the text field, and click OK. Then I see all the new trackers in the list of the tracker down panel. STEPS TO REPRODUCE Sorry, my GUI is in French; I am just translating and the actual labels may slightly differ. 1. Open Menu Configuration > Configure kTorrent choose section "Advanced". 2. In the field Tracker list URL, paste an URL that pulls a tracker list, such as https://newtrackon.com/api/stable 3. Check kTorrent's trackers down panel; possibly click on "Update trackers" and "Add trackers" OBSERVED RESULT No tracker from the list returned by https://newtrackon.com/api/stable is added to the tracker list. EXPECTED RESULT All the trackers returned by https://newtrackon.com/api/stable are added to the tracker list SOFTWARE/OS VERSIONS kTorrent: 22.12.x (and probably several previous versions, as I have experienced this issue for a while) Linux/KDE Plasma: Kali GNU/Linux 2023.3 (based on Debian Testing) KDE Plasma Version: 5.27.x (and several previous versions) KDE Frameworks Version: 5.107.x (and several previous versions) Qt Version: 5.15.x (and several previous versions) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476431] Crash report showfoto
https://bugs.kde.org/show_bug.cgi?id=476431 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476419] digiKam deleted images himself.
https://bugs.kde.org/show_bug.cgi?id=476419 Maik Qualmann changed: What|Removed |Added Summary|digiKam deleted images |digiKam deleted images |himself. (digiKam hat |himself. |selbstständig Bilder| |gelöscht.) | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476434] New: Timeline/Render includes hidden tracks as black/empty space after moving shown clips around
https://bugs.kde.org/show_bug.cgi?id=476434 Bug ID: 476434 Summary: Timeline/Render includes hidden tracks as black/empty space after moving shown clips around Classification: Applications Product: kdenlive Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: themb...@pm.me Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. create a project with 2 or more tracks 2. hide/unshow one of the tracks (Make sure something is in that track) 3. move around a clip in the shown track 4. Playback/Render continues after the shown track ends OBSERVED RESULT Playback/Rendering continues after the shown track ends and is filled with black space. EXPECTED RESULT Playback/Rendering ends when shown/visible clips end. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.8-zen1-1-zen / Plasma 5.27.9 (available in About System) KDE Plasma Version: Plasma 5.27.9 KDE Frameworks Version: Version 5.111.0 Qt Version: Version 5.15.11 (built against 5.15.11) ADDITIONAL INFORMATION Kdenlive Version 23.08.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476419] digiKam deleted images himself. (digiKam hat selbstständig Bilder gelöscht.)
https://bugs.kde.org/show_bug.cgi?id=476419 Maik Qualmann changed: What|Removed |Added Summary|digikam deleted images |digiKam deleted images |himself. (digiKam hat |himself. (digiKam hat |selbstständig Bilder|selbstständig Bilder |gelöscht.) |gelöscht.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476419] digikam deleted images himself. (digiKam hat selbstständig Bilder gelöscht.)
https://bugs.kde.org/show_bug.cgi?id=476419 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.2.0 Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Maik Qualmann --- Erstmal schön, dass Deine Bilder wohl noch vorhanden sind. Wichtig ist immer ein Backup zu haben, nur ein Laufwerk ist kein Backup. Festplatten können jeder Zeit ausfallen, auch eine SSD. Bei der FritzBox NAS benötigst Du aktive Festplatten, siehe AVM Empfehlung. Der USB Port gibt nicht so viel Strom für Laufwerke unbedingt her. Ich habe selber eine FritzBox, manchmal aktiviere ich auch die NAS zu Testzwecken, hier allerdings unter Linux. Wenn jetzt 2 Speicherorte vorhanden sind, müsste die FritzBox auch 2 Laufwerke oder Partitionen erkannt haben. Das werde ich aber von hier nicht debuggen können. Wie Du deine Foto Sammlung verwalten willst, musst Du entscheiden. Wenn Du die Fotos im Netzwerk benötigst, kommst Du um eine NAS nicht herum. Aber auch die "großen" NAS Laufwerke müssen verwaltet und konfiguriert werden, was nicht immer ganz einfach ist. Externe SSD Festplatten mit USB3 sind leichter zu verwalten. Ich schliesse den Bug nun, da digiKam wohl nichts gelöscht hat, anbei noch der Link zur digiKam Dokumentation, leider noch nicht ins deutsche übersetzt. https://docs.digikam.org/en/setup_application/collections_settings.html#the-network-shares-specificity https://docs.digikam.org/en/asset_management/data_protection.html Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475491] When changing the "Transfer from" of a transaction a Deposit is changed into a Payment.
https://bugs.kde.org/show_bug.cgi?id=475491 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #15 from Ralf Habacker --- (In reply to Thomas Baumgart from comment #13) > This issue is fixed on the master branch and I don't know if we have the > resources to tackle this on the 5.1 branch. It might be helpful to know the corresponding commit from the master branch where this problem was fixed. Maybe someone can be found to backport this commit. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil-5.27.9 fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Nate Graham changed: What|Removed |Added Severity|normal |grave Summary|Powerdevil fails to start, |Powerdevil-5.27.9 fails to |spikes cpu usage to max |start with ddcutil-2.0.0, |every few seconds |spikes cpu usage to max ||every few seconds Priority|NOR |VHI Keywords||regression Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||nicolas.fe...@gmx.de --- Comment #3 from Nate Graham --- The only substantive change in 5.27.9 compared to 5.27.8 is https://invent.kde.org/plasma/powerdevil/-/commit/d176188ff9b573a784905cada8824897af86b34b, which doesn't look related to me (but I could be wrong; CCing the author). Folks who are affected, are you able to make it work again by downgrading only ddcutil and keeping powerdevil the same? Don't forget to reboot afterwards. :) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Nate Graham changed: What|Removed |Added CC||theatt...@gmail.com --- Comment #2 from Nate Graham --- *** Bug 476369 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
