[khelpcenter] [Bug 484176] The KDE help center does not show the documentation for KDE applications.

2024-03-31 Thread Neal Gompa 
https://bugs.kde.org/show_bug.cgi?id=484176

Neal Gompa  changed:

   What|Removed |Added

 CC||ngomp...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 484833] Small lines appears below the panel and on the left side

2024-03-31 Thread Xwang 
https://bugs.kde.org/show_bug.cgi?id=484833

--- Comment #3 from Xwang  ---
(In reply to Xwang from comment #2)
> (In reply to fanzhuyifan from comment #1)
> > Are you using fractional scaling? Possible duplicate of BUG 480171.
> 
> Yes, I'm using 150% fractional scaling with a screen which has physical
> dimension equal to 2560x1600

I've changed to 160% (that is still fine) and the issue disappeared.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 484833] Small lines appears below the panel and on the left side

2024-03-31 Thread Xwang 
https://bugs.kde.org/show_bug.cgi?id=484833

--- Comment #2 from Xwang  ---
(In reply to fanzhuyifan from comment #1)
> Are you using fractional scaling? Possible duplicate of BUG 480171.

Yes, I'm using 150% fractional scaling with a screen which has physical
dimension equal to 2560x1600

-- 
You are receiving this mail because:
You are watching all bug changes.

[Skanpage] [Bug 483151] Skanpage scans only 75dpi

2024-03-31 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=483151

--- Comment #4 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.

[dolphin] [Bug 483124] Dolphin Opens Second Instance

2024-03-31 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=483124

--- 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.

[Bluedevil] [Bug 484814] Bluetooth showing not connected, even though it is

2024-03-31 Thread gromky 
https://bugs.kde.org/show_bug.cgi?id=484814

gromky  changed:

   What|Removed |Added

 CC||dr_th...@mail.ru

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-31 Thread Jakob Petsovits 
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #22 from Jakob Petsovits  ---
(In reply to Jakob Petsovits from comment #21)
> And after the PAM authentication workers have started, we've got two invalid
> reads with an actually useful backtrace for which I just created
> https://bugreports.qt.io/browse/QTBUG-123878. Either I'm stupid and can't
> read code / valgrind output, or this is actually a non-trivial bug in
> central Qt code.

Digging a little deeper, it looks like Qt is not broken and I was in the wrong.
Bwah. I wonder whether that means we have an issue in KSvg though?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 483058] Plasma 6 inconsistent `Switch Window {Left,Right,Up,Down}` behavior

2024-03-31 Thread Sridaran 
https://bugs.kde.org/show_bug.cgi?id=483058

Sridaran  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Sridaran  ---
Update: Seems to have been fixed in the next version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

2024-03-31 Thread Matt Fagnani 
https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #28 from Matt Fagnani  ---
I built qca 2.3.8 with your patch and the one in comment 11 and upgraded to it.
I logged out and in. Using the steps as before, I ran kwalletd6 with the old
config like OPENSSL_CONF=/etc/pki/tls/openssl.cnf.rpmold kwalletd6.
protonvpn-app started normally and kwalletd6 didn't crash. I did likewise with
the empty config, and protonvpn-app and kwalletd6 didn't crash. Thanks. The
patch for https://bugreports.qt.io/browse/QTBUG-118227 looks like it was
included in Qt 6.6.1 there and I'm using 6.6.2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 484729] Reply to HTML mail using same visual style hangs Kmail

2024-03-31 Thread Vladimir 
https://bugs.kde.org/show_bug.cgi?id=484729

Vladimir  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Vladimir  ---
(In reply to shivarryn from comment #1)
> Another victim of bug 482367 most probably.
> Should be fixed in Qt 6.6.3.

Can confirm it is fixed in Qt 6.6.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 477968] Snaps not showing in Discover (plasma-discover-backend-snap is missing necessary files)

2024-03-31 Thread Rafael Lima 
https://bugs.kde.org/show_bug.cgi?id=477968

Rafael Lima  changed:

   What|Removed |Added

 CC||rafael.palma.l...@gmail.com

--- Comment #4 from Rafael Lima  ---
I can confirm that snaps are not showing in Discover, even though
plasma-discover-backend-snap and snapd are installed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 478263] Victor Mono Nerd Font been rendered incorrectly when setting it to italic

2024-03-31 Thread Oliver Tzeng 
https://bugs.kde.org/show_bug.cgi?id=478263

--- Comment #4 from Oliver Tzeng  ---
(In reply to Matan Ziv-Av from comment #3)
> Can you include the font files you use? I cannot reproduce this issue.

Although I stopped using nf-victor-mono a while ago ill still provide the aur i
installed from
https://aur.archlinux.org/packages/ttf-victor-mono

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 442265] Opening an app from konsole has no activation environment set

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=442265

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=407288

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 407288] Kate doesn't bring existing session into foreground

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=407288

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=442265

--- Comment #27 from Nate Graham  ---
Ah in that case the issue is Bug 442265.

Looks like it's my bad that this mutated back in 2019 from a Windows bug into a
Wayland bug. Sorry about that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 484849] New: Wrong mouse pointer during login

2024-03-31 Thread Rafael Lima 
https://bugs.kde.org/show_bug.cgi?id=484849

Bug ID: 484849
   Summary: Wrong mouse pointer during login
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: rafael.palma.l...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY
When I boot my laptop and get to the login screen, the mouse pointer does not
use the Breeze theme. Instead it uses a small pointer that reminds Gnome's
mouse theme.

STEPS TO REPRODUCE
1. Boot your PC
2. Wait till it gets to the login screen
3. Notice the mouse pointer is not the Breeze style

OBSERVED RESULT
Wrong mouse pointer

EXPECTED RESULT
Breeze mouse pointer should be used

SYSTEM INFO

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 82CG
System Version: IdeaPad Gaming 3 15IMH05

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 484848] New: Dolphin crashes on right click

2024-03-31 Thread Brandon 
https://bugs.kde.org/show_bug.cgi?id=484848

Bug ID: 484848
   Summary: Dolphin crashes on right click
Classification: Applications
   Product: dolphin
   Version: 22.04.3
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: brandonwalker8...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (22.04.3)

Qt Version: 5.15.3
Frameworks Version: 5.104.0
Operating System: Linux 6.5.0-25-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.4 LTS
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Dolphin crashes when right clicking. I copied and pasted a .zip file then I
right clicked on the zip file to extract and Dolphin crashed twice.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7545810fb184 in QVariant::toString() const () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x754511003275 in
FileItemActionInsyncPlugin::getContextMenuActions(QString const&) () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/fileitemactioninsyncplugin.so
#6  0x754511002fb9 in
FileItemActionInsyncPlugin::actions(KFileItemListProperties const&, QWidget*)
() from /usr/lib/x86_64-linux-gnu/qt5/plugins/fileitemactioninsyncplugin.so
#7  0x754583112386 in ?? () from
/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#8  0x584eebd073d2 in ?? ()
#9  0x584eebcf7113 in ?? ()
#10 0x7545810f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x754583489e48 in DolphinView::requestContextMenu(QPoint const&,
KFileItem const&, QUrl const&, QList const&) () from
/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#12 0x7545834f7a16 in DolphinView::slotItemContextMenuRequested(int,
QPointF const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5
#13 0x7545810f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x754583487b8a in KItemListController::itemContextMenuRequested(int,
QPointF const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5
#15 0x7545834c17e1 in KItemListController::onPress(QPoint const&, QPointF
const&, QFlags, QFlags) () from
/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#16 0x7545834c1d66 in
KItemListController::mousePressEvent(QGraphicsSceneMouseEvent*, QTransform
const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5
#17 0x7545834c4609 in KItemListController::processEvent(QEvent*, QTransform
const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5
#18 0x7545834c7521 in KItemListView::event(QEvent*) () from
/lib/x86_64-linux-gnu/libdolphinprivate.so.5
#19 0x754581d6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7545810b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7545820abeb5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7545820ac271 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7545820b4b3a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7545820bea91 in QGraphicsScene::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x754581d6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7545810b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7545820dc585 in QGraphicsView::mousePressEvent(QMouseEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x754581daf4ee in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x754581e5d422 in QFrame::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x7545810b9b9a in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x754581d6c702 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#32 0x754581d74364 in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#33 0x7545810b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x754581d72e47 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x754581dc8d40 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#36 0x754581dcbfd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#37 0x754581d6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-31 Thread Jakob Petsovits 
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #21 from Jakob Petsovits  ---
If it's not a caching issue, and it's not necessarily a race condition, it
could also be an issue with invalid memory access somewhere. I decided to run
`kscreenlocker_greet --testing` in valgrind to see what it says.

Here's the excerpt that should roughly line up with window creation (I forgot
to specify more verbose QT_LOGGING_RULES):

kf.windowsystem: Loaded plugin
"/home/kpetso/build/prefix/lib/plugins/kf6/kwindowsystem/KF6WindowSystemX11Plugin.so"
for platform "xcb"
kf.coreaddons.kdirwatch: Available methods:  QList("Stat", "INotify",
"QFileSystemWatcher") preferred= INotify
kf.kirigami.platform: Loading style plugin from
"/home/kpetso/build/prefix/lib/plugins/kf6/kirigami/platform/KirigamiPlasmaStyle.so"
==10885== Conditional jump or move depends on uninitialised value(s)
==10885==at 0x1D0CD789: ???
==10885==by 0x218D1E4F: ???
==10885== 
Locked at 1711932039
==10885== Conditional jump or move depends on uninitialised value(s)
==10885==at 0x1D0CD789: ???
==10885==by 0x1D2D08DF: ???
==10885== 
==10885== Conditional jump or move depends on uninitialised value(s)
==10885==at 0x1D0CD789: ???
==10885==by 0x2140FF5F: ???
==10885== 
kscreenlocker_greet: PamAuthenticators: starting authenticators
kscreenlocker_greet: PamAuthenticators: state changing from
PamAuthenticators::Idle to PamAuthenticators::Authenticating

And after the PAM authentication workers have started, we've got two invalid
reads with an actually useful backtrace for which I just created
https://bugreports.qt.io/browse/QTBUG-123878. Either I'm stupid and can't read
code / valgrind output, or this is actually a non-trivial bug in central Qt
code.

It's somewhat plausible that our bug is coming from one of these invalid memory
accesses. I wish I had an actually useful backtrace for the "Conditional jump"
ones too. Not sure why valgrind denies me that one. Missing frame pointers on
Arch perhaps?

If you have a debug build of kscreenlocker at hand, maybe you can see if your
invocation of `valgrind ${KDE_PREFIX}/lib/libexec/kscreenlocker_greet
--testing` gives you something more useful than the pasted question marks
above.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 482696] Game Controller setting blocks UI before loading the page

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=482696

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484794] Some Fullscreen Apps get minimized when switching from one Virtual Desktop to another Virtual Desktop

2024-03-31 Thread Ali 
https://bugs.kde.org/show_bug.cgi?id=484794

Ali  changed:

   What|Removed |Added

 CC||radical...@proton.me

--- Comment #1 from Ali  ---
+1, I can reproduce on Arch Linux with Plasma 6.0.3 Wayland.
Games tested:
Stardew Valley - bug doesn't happen - Native 
Half Life 1 - bug doesn't happen - Native
Terraria - bug doesn't happen (though the preview seems a lil glitched when
switching back? gameplay is unaffected though) - Native
Pizza Tower - bug does happen - Proton/Steam
Brawlhalla - bug doesn't happen - Proton/Steam
Deltarune - bug does happen - Proton/Steam
Shovel Knight - bug does happen - Native
Minecraft (Tested under OpenGL/Xwayland, OpenGL/Native Wayland via
WayGL,Vulkan/Wayland) - bug does happen - Native (NOTE: Enabling windowed
fullscreen by way of clicking the titlebar and enabling the fullscreen option
from plasma does not have this bug happen)

I think this might apply to other apps that have a fullscreen function built
in, but every other app I've fullscreened using the option available by right
clicking the title bar > more actions > fullscreen doesn't result in this bug
happening.

 SYSTEM DETAILS:
Operating System: Arch Linux 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.6.23-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Graphics 550
Manufacturer: Apple Inc.
Product Name: MacBookPro13,2
System Version: 1.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484790] GNOME Disk Usage Analyzer/KWin

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484790

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com
 Resolution|--- |UNMAINTAINED
 Status|REPORTED|RESOLVED

--- Comment #2 from fanzhuyi...@gmail.com ---
Thank you for your bug report!

Debian advises users to not submit bugs upstream
(https://www.debian.org/Bugs/Reporting), as this version of the KDE software is
out of support from KDE, and so it's possible that the bug exists only in
Debian at this point.
Could you report the bug to Debian using the report bug utility
(https://packages.debian.org/stable/utils/reportbug)? If necessary, the
maintainer of the package will forward the bug upstream.

Thanks for understanding!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484827] Overview should close when activating an app

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484827

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480171] With 225% scale on a 4k screen, right-side-tiled windows and full-screen video/image content are not fully adjacent to right screen edge

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=480171

fanzhuyi...@gmail.com changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=484833

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 484833] Small lines appears below the panel and on the left side

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484833

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com
 Status|REPORTED|NEEDSINFO
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=480171
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from fanzhuyi...@gmail.com ---
Are you using fractional scaling? Possible duplicate of BUG 480171.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while

2024-03-31 Thread Fushan Wen 
https://bugs.kde.org/show_bug.cgi?id=481736

Fushan Wen  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 463518] can not maximize the kdenlive window

2024-03-31 Thread ksso 
https://bugs.kde.org/show_bug.cgi?id=463518

--- Comment #3 from ksso  ---
still happen with 23.08.5 with debian and kubuntu
with 24.02.1 the appimage crashes when try to apply effects

thank you

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 484832] the box fill with pattern is not working on vector layer

2024-03-31 Thread Darrell D 
https://bugs.kde.org/show_bug.cgi?id=484832

--- Comment #1 from Darrell D  ---
also tested on windows 10, krita 5.2.2 and has the same behavior

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwalletmanager] [Bug 428903] Kwallet causes system shutdown to hang for about 8 seconds

2024-03-31 Thread Julien Delquié 
https://bugs.kde.org/show_bug.cgi?id=428903

--- Comment #6 from Julien Delquié  ---
Hello, still have this issue here?
Because I do not, since a long time now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators

2024-03-31 Thread Magne Djupvik 
https://bugs.kde.org/show_bug.cgi?id=479235

Magne Djupvik  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from Magne Djupvik  ---
Same issue here; see duplicated issue for my backtrace plus another.

Operating System: openSUSE Tumbleweed 20240329
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2
Manufacturer: ASUS

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484093] Added applications doesn't persist after reboot

2024-03-31 Thread Gena 
https://bugs.kde.org/show_bug.cgi?id=484093

--- Comment #1 from Gena  ---
Can't reproduce anymore after 6.0.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484093] Added applications doesn't persist after reboot

2024-03-31 Thread Gena 
https://bugs.kde.org/show_bug.cgi?id=484093

Gena  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators

2024-03-31 Thread Magne Djupvik 
https://bugs.kde.org/show_bug.cgi?id=479235

Magne Djupvik  changed:

   What|Removed |Added

   Platform|Arch Linux  |openSUSE
Version|5.249.0 |6.0.0
 CC||magn...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators

2024-03-31 Thread Magne Djupvik 
https://bugs.kde.org/show_bug.cgi?id=479235

Magne Djupvik  changed:

   What|Removed |Added

 CC||bednarczyk.pa...@outlook.co
   ||m

--- Comment #2 from Magne Djupvik  ---
*** Bug 482537 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482537] crash in QHashPrivate::iterator >::node

2024-03-31 Thread Magne Djupvik 
https://bugs.kde.org/show_bug.cgi?id=482537

Magne Djupvik  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Magne Djupvik  ---


*** This bug has been marked as a duplicate of bug 479235 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484835] Proton games do not lock onto game window on a multi-monitor setup since 6.0.x

2024-03-31 Thread Gurenko Alex 
https://bugs.kde.org/show_bug.cgi?id=484835

Gurenko Alex  changed:

   What|Removed |Added

 CC||agure...@protonmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 483579] kwin_wayland crash when refocusing a fullscreen application that captures the mouse while the cursor is at the screen edge of an auto-hiding panel.

2024-03-31 Thread Arttu 
https://bugs.kde.org/show_bug.cgi?id=483579

Arttu  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
   Version Fixed In||6.0.3
 Resolution|--- |FIXED

--- Comment #3 from Arttu  ---
The crash no longer occurs after upgrading to Kwin 6.0.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482537] crash in QHashPrivate::iterator >::node

2024-03-31 Thread Magne Djupvik 
https://bugs.kde.org/show_bug.cgi?id=482537

--- Comment #2 from Magne Djupvik  ---
Created attachment 168008
  --> https://bugs.kde.org/attachment.cgi?id=168008=edit
Backtrace

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482537] crash in QHashPrivate::iterator >::node

2024-03-31 Thread Magne Djupvik 
https://bugs.kde.org/show_bug.cgi?id=482537

Magne Djupvik  changed:

   What|Removed |Added

Version|6.0.0   |6.0.3
 CC||magn...@gmail.com
   Platform|Arch Linux  |openSUSE

--- Comment #1 from Magne Djupvik  ---
I also have this crash in 6.0.3 using openSUSE Tumbleweed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-31 Thread Jakob Petsovits 
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #20 from Jakob Petsovits  ---
I enabled some extra logs and encountered this issue (or something that looks
exactly like it) on an X11 session today, current newest master of all Plasma
session components, as of 2024-03-31. I locked manually using the Meta+L
shortcut and got it to remain black once before a correctly painted lock
screen, in another session black on a following lock screen after the initial
one worked correctly.

I posted my logs into a GitLab snippet: https://invent.kde.org/-/snippets/3059

They look roughly alike, no particular differences stick out to me between
locks that worked fine and locks that turned black with cursor.

Info Center blurb:
Operating System: Arch Linux 
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.3
Kernel Version: 6.8.2-arch2-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20QD001VUS
System Version: ThinkPad X1 Carbon 7th

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480171] With 225% scale on a 4k screen, right-side-tiled windows and full-screen video/image content are not fully adjacent to right screen edge

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=480171

guilla...@m1ch0.ca changed:

   What|Removed |Added

 CC||guilla...@m1ch0.ca

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 484847] BRHE PS4 Controller Fails to Pair Properly

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484847

--- Comment #1 from nekone...@protonmail.ch ---
Forgot to list my kernel:
6.7.1-tkg-pds-gentoo-llvm-zen2 (https://github.com/frogging-family/linux-tkg)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 484847] New: BRHE PS4 Controller Fails to Pair Properly

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484847

Bug ID: 484847
   Summary: BRHE PS4 Controller Fails to Pair Properly
Classification: Plasma
   Product: Bluedevil
   Version: 6.0.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wizard
  Assignee: plasma-b...@kde.org
  Reporter: nekone...@protonmail.ch
  Target Milestone: ---

Created attachment 168007
  --> https://bugs.kde.org/attachment.cgi?id=168007=edit
Bluetoothctl Log

SUMMARY
This controller:
https://web.archive.org/web/20231030230144/https://www.amazon.com/Controller-Joysticks-Compatible-Vibration-PlayStation-4/dp/B0CCTXQ6P5?th=1

Fails to connect properly via bluetooth under Plasma 6.
For some reason, however, it does connect properly on the Steam Deck.
(Back on my Plasma 5 desktop, before I update to Plasma 6, it used to randomly
decide whether or not it wanted to; it was inconsistent back then).

STEPS TO REPRODUCE
1. Enable bluetooth
2. Run "bluedevil-wizard" via the terminal (unpair the device from the
systemsettings menu if it was previously paired - this is included in my log)
3. Attempt to pair the device
4. Get this error via the terminal from the wizard:
kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken."

OBSERVED RESULT
PS4 bluetooth controller fails to pair/connect properly but may still register
itself in the bluetooth paired devices menu in systemsettings.

EXPECTED RESULT
PS4 controller to pair and connect without issue.

SOFTWARE/OS VERSIONS
Linux: Gentoo (OpenRC & LLVM-based)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

ADDITIONAL INFORMATION
Log attached with this report.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484846] Switching from big screen to built in display doesn't work correctly for gtk windows

2024-03-31 Thread Piotr Mierzwinski 
https://bugs.kde.org/show_bug.cgi?id=484846

Piotr Mierzwinski  changed:

   What|Removed |Added

   Keywords||multiscreen, qt6
Summary|Switching from big screen   |Switching from big screen
   |to built in display doesn't |to built in display doesn't
   |work correctly  |work correctly for gtk
   ||windows
 CC||piotr.mierzwin...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484846] New: Switching from big screen to built in display doesn't work correctly

2024-03-31 Thread Piotr Mierzwinski 
https://bugs.kde.org/show_bug.cgi?id=484846

Bug ID: 484846
   Summary: Switching from big screen to built in display doesn't
work correctly
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

Created attachment 168006
  --> https://bugs.kde.org/attachment.cgi?id=168006=edit
desktop in buillt-in display

Usually I work on big screen (NEC with res.: 2560x1440) and closed lid. After I
disconnect my external display and start KDE/Plasma on built in display (res.
1920x1080) I get not scaled correctly gtk windows - to detailed I mean Firefox
(check attached screen shot) which seems to not scaled at all to lower
resolution and for example title bar isn't visible.

SUMMARY


STEPS TO REPRODUCE
1. Connect external monitor with resolution greater that that placed in build
in display
2. Configure the system to work with closed lid and external monitor as primary
3. Set save recent session
4. Start couple Firefox windows and resize them to size bigger than built in
display.
5. Start konsole and resize it to be 80 rows and 30 rows 
6. Turn off PC
7. Disconnect external monitor 
8. Start PC
9. Login do KDE/Plasma

OBSERVED RESULT
Firefox windows are too big to fit current display, so title bar isn't visible
Konsole is very small window
(check screen shots)

EXPECTED RESULT
Firefox should be scaled to fit lower screen resolution
Konsole should not be very small (couple cols and couple rows)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.1.0
Qt Version: 6.2.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-qqc2-desktop-style] [Bug 484845] New: Alt accelerators not shown on all buttons (like in Spectacle) just most buttons

2024-03-31 Thread Michael 
https://bugs.kde.org/show_bug.cgi?id=484845

Bug ID: 484845
   Summary: Alt accelerators not shown on all buttons (like in
Spectacle) just most buttons
Classification: Frameworks and Libraries
   Product: frameworks-qqc2-desktop-style
   Version: 6.0.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: k...@callthecomputerdoctor.com
CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk,
noaha...@gmail.com, notm...@gmail.com
  Target Milestone: ---

SUMMARY

In Spectacle 24.02.1, I can hold down the Alt key and I'll see an underline
appear in the GUI, which signifies which key to press to activate the button. 

But not for the first button. No underline appears there.


STEPS TO REPRODUCE

1. Invoke Spectacle
2. Depress Alt


OBSERVED RESULT

See that all items show an underline in the right place, EXCEPT for the Save
button. 


EXPECTED RESULT

All items should have an underline, including the Save button.


OPERATING SYSTEM

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 14.9 GiB of RAM
Graphics Processor: AMD Radeon Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 484844] Info in "About this system" about hardware is not completed

2024-03-31 Thread Piotr Mierzwinski 
https://bugs.kde.org/show_bug.cgi?id=484844

Piotr Mierzwinski  changed:

   What|Removed |Added

   Keywords||qt6, usability
 CC||piotr.mierzwin...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 484844] New: Info in "About this system" about hardware is not completed

2024-03-31 Thread Piotr Mierzwinski 
https://bugs.kde.org/show_bug.cgi?id=484844

Bug ID: 484844
   Summary: Info in "About this system" about hardware is not
completed
Classification: Applications
   Product: kinfocenter
   Version: master
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: sit...@kde.org
  Target Milestone: ---

In my humble opinion information in hardware is not completed. I cannot find
out here all general information. 
I think most systems has more parts than only processor, RAM and graphics card,
so would be nice to put here also info about
1. my display(s) - at least manufacturer and resolution
To find out I need to run additional application - System Settings -> Display
Information
2. local (not network) storage(s)
To find out I need to run additional application - System Monitor (here I can
find info about: Memory, Disc, CPU, Network but not about display)
To get full information about my hardware I need to jump between couple
applications, which for sure this is not comfortable.

Second thing is wasting space. I mean information about laptop.
Now there is split manufacturer, model (calling here "System Version" which IMO
is not intuitive, and better would be just "model") and "Product Name" 3 lines.
I wonder why? Isn't would be better just put all in one line (and alternatively
show tool tip for each part after mouse over it), for example: 
LENOVO, ThinkPad T480 (20L50003PB)

Third thing is the order.
Why more general information about my hardware like manufacturer, model is
placed as last and as first I can see info about CPU? Isn't more intuitive to
put these information in opposite way? 
for example: 
My PC: LENOVO, ThinkPad T480 (20L50003PB)
Processors: ...
Memory: ...
Graphics Processor: ...
Display: ...
Audio Processor: ...
Storage: ...

STEPS TO REPRODUCE
1.Start "Info Center" 
2. Open "About this System"
3. 

OBSERVED RESULT
Missing several information about hardware in one place

EXPECTED RESULT
All general information about hardware should be placed in one place.
Card is calling "About this System" and I get limited information about
hardware.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 484843] while i was drawing i made a screenshot of the process but later the screenshot appeared as an image on my drawing on the top left corner. Its not a layer, i cannot draw over it,

2024-03-31 Thread David REVOY 
https://bugs.kde.org/show_bug.cgi?id=484843

David REVOY  changed:

   What|Removed |Added

 CC||i...@davidrevoy.com
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from David REVOY  ---
Hi, you probably accidentally inserted the screenshot as a reference image. 

Use in your Krita toolbar the "Reference Image Tool" (an icon of a pin)
https://docs.krita.org/en/reference_manual/tools/reference_images_tool.html ,
you'll be able to select, move and delete this. 

Let us know if that was it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484842] Icons-Only Task Manager Goes From Partially Broken to Crashing Plasma

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484842

--- Comment #1 from morrismyles...@gmail.com ---
Created attachment 168005
  --> https://bugs.kde.org/attachment.cgi?id=168005=edit
Crash Demonstration

This is an OBS recording of the crash in action.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 484843] New: while i was drawing i made a screenshot of the process but later the screenshot appeared as an image on my drawing on the top left corner. Its not a layer, i cannot draw over

2024-03-31 Thread zid 
https://bugs.kde.org/show_bug.cgi?id=484843

Bug ID: 484843
   Summary: while i was drawing i made a screenshot of the process
but later the screenshot appeared as an image on my
drawing on the top left corner. Its not a layer, i
cannot draw over it, i cannot cut it, and i can't do
anything about it,.
Classification: Applications
   Product: krita
   Version: 5.0.6
  Platform: Compiled Sources
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: bubug...@gmail.com
  Target Milestone: ---

Created attachment 168004
  --> https://bugs.kde.org/attachment.cgi?id=168004=edit
the image on the top left corner does not budge, i cannot paint over it or
earse it

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
while i was drawing i made a screenshot of the process but later the screenshot
appeared as an image on my drawing on the top left corner. Its not a layer, i
cannot draw over it, i cannot cut it, and i can't do anything about it. i've
checked every layer and nothing.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484842] New: Icons-Only Task Manager Goes From Partially Broken to Crashing Plasma

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484842

Bug ID: 484842
   Summary: Icons-Only Task Manager Goes From Partially Broken to
Crashing Plasma
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: morrismyles...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

Created attachment 168003
  --> https://bugs.kde.org/attachment.cgi?id=168003=edit
GDB Backtrace

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
What originally started as an isolated continuation of a bug from back in
5.27.9 has escalated to a repeatable crash on 6.0.3 on my end. Essentially,
after updating or restarting the desktop, adding a floating Icons-Only Task
Manager (theoretically possible on the normal Task Manager as well) or
interacting with it causes the shell to crash and restart before eventually
crashing to the point that it can't recover.

STEPS TO REPRODUCE
1.  Restart Plasma using "killall plasmashell | kstart plasmashell" in Konsole
or another terminal emulator.
2.  When the desktop has loaded, right click on the desktop and choose "Add
Widgets."
3.  Find the Icons-Only Task Manager or Task Manager and add it to the desktop.
4.  The shell will crash, but recover soon after (if it hasn't jumped right to
unrecoverable status).
5.  Continue interacting with either Task Manager by opening applications each
one until they cause another crash.
6.  Eventually, "plasmashell" can no longer recover from the crash and present
a black screen with nothing but currently running applications.

OBSERVED RESULT

Several observable results:
*  The Task Manager fails to report running applications. This is similar to
Bug 475896 but goes much farther.
*  Right-clicking on applications no longer shows menu options.
*  The desktop crashes simply by adding the Task Manager to the desktop.
*  The desktop crashes simply by opening applications from the Task Manager and
subsequently closing them.

EXPECTED RESULT

*  The Task Manager should report running applications and show jump lists
after right-clicking them.
*  Adding another Task Manager or interacting with either one should not cause
Plasma to crash.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.5.0-26-generic (64-bit)
(available in About System)
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 
Qt Version: 6.6.2
Graphics Platform: Wayland

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484841] Thunderbolt settings unreadable in dark mode

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484841

dcko...@gmail.com changed:

   What|Removed |Added

 Attachment #168002|Thunderbolt settinhs in |Thunderbolt settings in
description|dark mode   |dark mode

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 484841] New: Thunderbolt settings unreadable in dark mode

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484841

Bug ID: 484841
   Summary: Thunderbolt settings unreadable in dark mode
Classification: Applications
   Product: systemsettings
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_thunderbolt
  Assignee: plasma-b...@kde.org
  Reporter: dcko...@gmail.com
CC: dvra...@kde.org
  Target Milestone: ---

Created attachment 168002
  --> https://bugs.kde.org/attachment.cgi?id=168002=edit
Thunderbolt settinhs in dark mode

SUMMARY
The thunderbolt settings screen is unreadable in dark mode. It has black text
on dark background.

STEPS TO REPRODUCE
1. Set the theme to dark
2. Visit Thunderbolt settings page in System Settings

OBSERVED RESULT
The text is black on dark background.

EXPECTED RESULT
The text colour is in sync with the rest of the theme; light on dark.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480862] Unable to assign numpad keys to shortcuts on Wayland

2024-03-31 Thread Antti Savolainen 
https://bugs.kde.org/show_bug.cgi?id=480862

--- Comment #8 from Antti Savolainen  ---
Nice. Can confirm it works now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 484840] New: Vim starts in replace mode

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484840

Bug ID: 484840
   Summary: Vim starts in replace mode
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: mpeter.68...@simplelogin.co
  Target Milestone: ---

Konsole version: 24.04.70
Source: gitlab CI release with name
'konsole-master-2985-windows-cl-msvc2022-x86_64'

SUMMARY
When opening Vim (even with the `--clean` option) in a WSL shell, it will start
up in replace mode, as it shows as usual in the bottom left corner.

The issue does not happen when using the Windows Terminal terminal emulator.

STEPS TO REPRODUCE
1. Start a WSL shell
2. Run the `vim`  command (with a file or without, does not matter)

OBSERVED RESULT
Vim opens in replace mode

EXPECTED RESULT
Vim should open in command mode

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
In a local WSL shell it is always happening.
If I use the local WSL shell to connect to a linux system through ssh, it
happens only sometimes.

It seems in the past Windows Terminal also had this issue. The information
below might be useful:
-
https://vi.stackexchange.com/questions/27391/why-it-enters-replace-mode-automatically-even-with-clean-flag-in-wsl
- https://github.com/microsoft/terminal/issues/1637
- https://github.com/vim/vim/issues/6951
- https://github.com/vim/vim/issues/6365
- https://superuser.com/questions/1284561/why-is-vim-starting-in-replace-mode

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 484839] New: Tap-and-drag does not work

2024-03-31 Thread Piotr Gliźniewicz 
https://bugs.kde.org/show_bug.cgi?id=484839

Bug ID: 484839
   Summary: Tap-and-drag does not work
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: gli...@gmail.com
  Target Milestone: ---

SUMMARY
I have Tap-and-drag enabled in Touchpad settings. But tapping and dragging
doesn't work. Tested in Dolphin and KPatience.

STEPS TO REPRODUCE
1. Enable Tap-and-drag in Touchpad settings.
2. Try to tap-and-drag on a folder in Dolphin or card in KPatience.

OBSERVED RESULT
The folder in Dolphin doesn't move. The card in KPatience doesn't move.

EXPECTED RESULT
The folder moves in Dolphin, the card moves in KPatience.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40 
(available in About System)
KDE Plasma Version: 6.0.2 
KDE Frameworks Version:  6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Tested on a ThinkPad X13 Gen 3 (AMD)

libinput list-devices output for the touchpad:
Device:   SYNA8018:00 06CB:CE67 Touchpad
Kernel:   /dev/input/event8
Group:6
Seat: seat0, default
Size: 112x57mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock:disabled
Left-handed:  disabled
Nat.scrolling:disabled
Middle emulation: disabled
Calibration:  n/a
Scroll methods:   *two-finger edge 
Click methods:*button-areas clickfinger 
Disable-w-typing: enabled
Disable-w-trackpointing: enabled
Accel profiles:   flat *adaptive custom
Rotation: n/a

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-qqc2-desktop-style] [Bug 469637] Alt accelerators not shown on buttons

2024-03-31 Thread Michael 
https://bugs.kde.org/show_bug.cgi?id=469637

Michael  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Michael  ---
This appears to be largely fixed in KF6. Closing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 484836] Background color of whitespace characters changed by scrolling

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484836

--- Comment #1 from mpeter.68...@simplelogin.co ---
One more thing I forgot to mention: the issue does not happen when using the
Windows Terminal terminal emulator.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482875] Desktop icons reset positions to alphabetical order after a long time from auto shut-off of screen (Wayland)

2024-03-31 Thread Velent 
https://bugs.kde.org/show_bug.cgi?id=482875

Velent  changed:

   What|Removed |Added

Version|6.0.2   |6.0.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482875] Desktop icons reset positions to alphabetical order after a long time from auto shut-off of screen (Wayland)

2024-03-31 Thread Velent 
https://bugs.kde.org/show_bug.cgi?id=482875

--- Comment #9 from Velent  ---
Created attachment 168001
  --> https://bugs.kde.org/attachment.cgi?id=168001=edit
Dolphin places panel size after few hours of standby

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482875] Desktop icons reset positions to alphabetical order after a long time from auto shut-off of screen (Wayland)

2024-03-31 Thread Velent 
https://bugs.kde.org/show_bug.cgi?id=482875

Velent  changed:

   What|Removed |Added

 CC||vele...@proton.me

--- Comment #8 from Velent  ---
Created attachment 168000
  --> https://bugs.kde.org/attachment.cgi?id=168000=edit
Windows size after few hours of standby

I've noticed that standby affects not only icons, but sometimes the size of
windows and UI panels in qt applications

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484838] New: Clicking on notifications occasionally crashes Plasmashell

2024-03-31 Thread Mark 
https://bugs.kde.org/show_bug.cgi?id=484838

Bug ID: 484838
   Summary: Clicking on notifications occasionally crashes
Plasmashell
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Notifications
  Assignee: plasma-b...@kde.org
  Reporter: m...@leyva.me
CC: k...@privat.broulik.de
  Target Milestone: 1.0

SUMMARY
After unlocking my desktop, I tried to click on the notification applet which
resulted in some stutter before Plasmashell crashed. I'm unsure if the
following steps can reproduce it. 

STEPS TO REPRODUCE
1. Lock desktop
2. Unlock desktop
3. Click on notification applet if present

OBSERVED RESULT
Notification applet opens without crashing Plasmashell

EXPECTED RESULT
Plasmashell crashes.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240329
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.1-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H

ADDITIONAL INFORMATION
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {94513001237136}}
ret = 
#1  0x7effc4894a73 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2  0x7effc4841176 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
ret = 
#3  0x7effc7ad3b93 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-6.0.0/src/kcrash.cpp:586
data = { = {_vptr.MetadataWriter =
0x7effc7ad87d8 }, argv = {_M_elems = {0x0,
0x7effc7ad63f9 "--glrenderer", 0x55f5861461c0 "NVIDIA GeForce GTX 1660
SUPER/PCIe/SSE2", 0x7effc7ad6406 "--platform", 0x55f5936e58b0 "wayland",
0x7effc7ad6437 "--appname", 0x55f585ddbb30 "plasmashell", 0x7effc7ad6441
"--apppath", 0x55f585dd0120 "/usr/bin", 0x7effc7ad644e "--signal",
0x7ffd874c7626 "11", 0x7effc7ad645c "--pid", 0x7ffd874c7630 "2861",
0x7effc7ad6462 "--appversion", 0x55f585dd2b70 "6.0.3", 0x7effc7ad646f
"--programname", 0x55f584f37a18  "", 0x7effc7ad647d
"--bugaddress", 0x55f585dd8a90 "sub...@bugs.kde.org", 0x0 }},
argc = 19, m_writer = 0x7ffd874c75d0}
platformName = {d = {d = 0x55f5936e58a0, ptr = 0x55f5936e58b0
"wayland", size = 7}, static _empty = 0 '\000'}
about = 0x55f586148350
argv = 0x7ffd874c7658
ini = { = {_vptr.MetadataWriter =
0x7effc7ad8808 }, writable = false, fd
= 68}
sigtxt = "11\000zL\207\375\177\000"
pidtxt = "2861\000\177\000\000\001vL\207\375\177\000\000\002\000\000"
argc = 
crashRecursionCounter = 2
#4  0x7effc4841240 in  () at /lib64/libc.so.6
#5  0x7effc64aa3ea in QQmlContextData::contextObject() const
(this=, this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlcontextdata_p.h:128
contextObject = 
#6  QQmlContextData::ContextGuard::objectDestroyedImpl(QQmlGuardImpl*)
(impl=0x55f595691878) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlcontextdata_p.h:455
contextObject = 
#7  0x7effc64b6e72 in QQmlData::destroyed(QObject*) (this=0x55f58db318c0,
object=0x55f58db318a0) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlengine.cpp:1489
guard = 
binding = 
signalHandler = 
#8  0x7effc51cf702 in QObject::~QObject() (this=0x55f58db318a0,
this=) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qobject.cpp:1065
d = 0x55f595663650
sharedRefcount = 0x55f594164190
cd = 
#9  0x7effc6c006e5 in
QQmlPrivate::QQmlElement::~QQmlElement() (this=0x55f58db318a0,
this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlprivate.h:99
#10 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55f58db318a0, this=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.3/src/qml/qml/qqmlprivate.h:99
#11 0x7effc51caba7 in QObject::event(QEvent*) (this=0x55f58db318a0,
e=0x55f594c881d0) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qobject.cpp:1424
#12 0x7effc71c1a7e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55f58db318a0, e=0x55f594c881d0) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/widgets/kernel/qapplication.cpp:3296
consumed = false
filtered = false
#13 0x7effc5187998 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55f58db318a0, event=0x55f594c881d0) at
/usr/src/debug/qtbase-everywhere-src-6.6.3/src/corelib/kernel/qcoreapplication.cpp:1121
selfRequired = true
result =

[kactivitymanagerd] [Bug 484837] New: kactivitymanagerd runs one CPU core at 100% under Plasma 6.0, laptop fan runs at idle

2024-03-31 Thread Michael 
https://bugs.kde.org/show_bug.cgi?id=484837

Bug ID: 484837
   Summary: kactivitymanagerd runs one CPU core at 100% under
Plasma 6.0, laptop fan runs at idle
Classification: Plasma
   Product: kactivitymanagerd
   Version: 6.0.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: k...@callthecomputerdoctor.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY

kactivitymanagerd runs one CPU core at 100% from the moment of login and until
logout. 

This is new behaviour which wasn't present under Plasma 5.27; it's only
recently with the upgrade to 6.0.x.


STEPS TO REPRODUCE

1. Log in.
2. Open up System Monitor, or better yet, htop from the terminal.
3. Notice that kactivitymanagerd is running constantly at 100%.
4. From the terminal, stop the daemon by executing this and notice that the CPU
is now normal: 
 systemctl --user stop plasma-kactivitymanagerd


OBSERVED RESULT

System Monitor/htop shows one core fully utilitzed by kactivitymanagerd. Also
laptop power usage is increased and the fan is coming on more often.


EXPECTED RESULT

kactivitymanagerd should be at a negligible CPU usage. Laptop fan does not come
on at idle.


SOFTWARE/OS VERSIONS

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 14.9 GiB of RAM
Graphics Processor: AMD Radeon Graphics

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 479728] DarkTable does not open when trying to edit a Raw formatted picture (DNG) in digiKam

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=479728

--- Comment #3 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 42, bug 451917, bug 257737, bug
477631, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 285610] Be able to apply RAW decoding settings from one item to another one

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=285610

--- Comment #4 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 42, bug 451917, bug 479728, bug
257737, bug 477631, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 374655] Working with raw processors

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=374655

--- Comment #2 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 42, bug 451917, bug 479728, bug
257737, bug 477631, bug 285610

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 418941] Convert RAF Fuji XT2 to DNG not working

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=418941

--- Comment #8 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 42, bug 451917, bug 479728, bug 257737, bug
477631, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 390700] Unable to convert Fujifilm S3Pro RAF RAW to DNG [patch]

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=390700

--- Comment #26 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 418941, bug 42, bug 451917, bug 479728, bug 257737, bug
477631, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 451917] Converting RAW (from CANON RP) to DNG produces files not useable in Rawtherapee

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=451917

--- Comment #6 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 42, bug 479728, bug 257737, bug
477631, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 477631] digiKam cannot decode Nikon Z8/Z9 NEF images in the HE/HE* formats

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=477631

--- Comment #7 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 42, bug 451917, bug 479728, bug
257737, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 257737] Fuji S3 Pro Raw files (RAF) only S pixels are processed giving 6MP Should be S+R Pixels giving 12MP

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=257737

--- Comment #22 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 42, bug 451917, bug 479728, bug
477631, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[digikam] [Bug 444442] Conversion from Sony ARW to DNG loses pixels on the right side of the image

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=42

--- Comment #7 from caulier.gil...@gmail.com ---
Git commit 1b911bc46a1631f9d00ef2866f9987f3a04fbdde by Gilles Caulier.
Committed on 31/03/2024 at 20:28.
Pushed by cgilles into branch 'master'.

Update Adobe DNG SDK from 1.5.1 to 1.7.1 to support JPEG-XL compression
formats.
Related: bug 390700, bug 418941, bug 451917, bug 479728, bug 257737, bug
477631, bug 285610, bug 374655

M  +1-0Mainpage.dox
M  +2-0NEWS
M  +3-1core/CMakeLists.txt
M  +1-0core/app/DigikamCoreTarget.cmake
A  +109  -0core/cmake/modules/FindLibjxl.cmake
M  +3-0core/cmake/rules/RulesDNGSdk.cmake
M  +17   -1core/libs/dngwriter/CMakeLists.txt
M  +1-1core/libs/dngwriter/dngwriter.cpp
M  +1-1core/libs/dngwriter/dngwriter_export.cpp
M  +242  -52   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.cpp
M  +99   -36   core/libs/dngwriter/extra/dng_sdk/dng_1d_function.h
M  +69   -67   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.cpp
M  +57   -26   core/libs/dngwriter/extra/dng_sdk/dng_1d_table.h
M  +54   -52   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.cpp
M  +57   -47   core/libs/dngwriter/extra/dng_sdk/dng_abort_sniffer.h
M  +444  -88   core/libs/dngwriter/extra/dng_sdk/dng_area_task.cpp
M  +230  -33   core/libs/dngwriter/extra/dng_sdk/dng_area_task.h
M  +27   -4core/libs/dngwriter/extra/dng_sdk/dng_assertions.h
M  +67   -53   core/libs/dngwriter/extra/dng_sdk/dng_auto_ptr.h
M  +486  -474  core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.cpp
M  +53   -48   core/libs/dngwriter/extra/dng_sdk/dng_bad_pixels.h
M  +4976 -1140 core/libs/dngwriter/extra/dng_sdk/dng_big_table.cpp
M  +1290 -389  core/libs/dngwriter/extra/dng_sdk/dng_big_table.h
A  +397  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.cpp  *
A  +113  -0core/libs/dngwriter/extra/dng_sdk/dng_bmff.h  *
M  +9-2core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.cpp
M  +491  -252  core/libs/dngwriter/extra/dng_sdk/dng_bottlenecks.h
M  +1371 -386  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.cpp
M  +513  -166  core/libs/dngwriter/extra/dng_sdk/dng_camera_profile.h
M  +48   -3core/libs/dngwriter/extra/dng_sdk/dng_classes.h
M  +1323 -585  core/libs/dngwriter/extra/dng_sdk/dng_color_space.cpp
M  +299  -66   core/libs/dngwriter/extra/dng_sdk/dng_color_space.h
M  +363  -191  core/libs/dngwriter/extra/dng_sdk/dng_color_spec.cpp
M  +52   -24   core/libs/dngwriter/extra/dng_sdk/dng_color_spec.h
M  +444  -430  core/libs/dngwriter/extra/dng_sdk/dng_date_time.cpp
M  +100  -105  core/libs/dngwriter/extra/dng_sdk/dng_date_time.h
A  +60   -0core/libs/dngwriter/extra/dng_sdk/dng_deprecated_flags.h  *
M  +11   -5core/libs/dngwriter/extra/dng_sdk/dng_errors.h
M  +62   -62   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.cpp
M  +56   -56   core/libs/dngwriter/extra/dng_sdk/dng_exceptions.h
M  +1984 -1960 core/libs/dngwriter/extra/dng_sdk/dng_exif.cpp
M  +144  -128  core/libs/dngwriter/extra/dng_sdk/dng_exif.h
M  +5-3core/libs/dngwriter/extra/dng_sdk/dng_fast_module.h
M  +148  -37   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.cpp
M  +41   -16   core/libs/dngwriter/extra/dng_sdk/dng_file_stream.h
M  +58   -58   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.cpp
M  +15   -15   core/libs/dngwriter/extra/dng_sdk/dng_filter_task.h
M  +173  -146  core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.cpp
M  +98   -72   core/libs/dngwriter/extra/dng_sdk/dng_fingerprint.h
M  +127  -57   core/libs/dngwriter/extra/dng_sdk/dng_flags.h
M  +1014 -256  core/libs/dngwriter/extra/dng_sdk/dng_gain_map.cpp
M  +343  -45   core/libs/dngwriter/extra/dng_sdk/dng_gain_map.h
M  +10   -4core/libs/dngwriter/extra/dng_sdk/dng_globals.cpp
M  +3-3core/libs/dngwriter/extra/dng_sdk/dng_globals.h
M  +365  -154  core/libs/dngwriter/extra/dng_sdk/dng_host.cpp
M  +216  -96   core/libs/dngwriter/extra/dng_sdk/dng_host.h
M  +227  -90   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.cpp
M  +26   -16   core/libs/dngwriter/extra/dng_sdk/dng_hue_sat_map.h
M  +2514 -1712 core/libs/dngwriter/extra/dng_sdk/dng_ifd.cpp
M  +140  -108  core/libs/dngwriter/extra/dng_sdk/dng_ifd.h
M  +631  -315  core/libs/dngwriter/extra/dng_sdk/dng_image.cpp
M  +117  -92   core/libs/dngwriter/extra/dng_sdk/dng_image.h
M  +5843 -3135 core/libs/dngwriter/extra/dng_sdk/dng_image_writer.cpp
M  +733  -471  core/libs/dngwriter/extra/dng_sdk/dng_image_writer.h
M  +1382 -1126 core/libs/dngwriter/extra/dng_sdk/dng_info.cpp
M  +99   -69   core/libs/dngwriter/extra/dng_sdk/dng_info.h
M  +325  -325  core/libs/dngwriter/extra/dng_sdk/dng_iptc.cpp
M  +32   -32   core/libs/dngwriter/extra/dng_sdk/dng_iptc.h
M  +544  -210  core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.cpp
M  +139  -18   core/libs/dngwriter/extra/dng_sdk/dng_jpeg_image.h
A  +90   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.cpp  *
A  +19   -0core/libs/dngwriter/extra/dng_sdk/dng_jpeg_memory_source.h  *
A  +18   -0

[konsole] [Bug 484836] New: Background color of whitespace characters changed by scrolling

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484836

Bug ID: 484836
   Summary: Background color of whitespace characters changed by
scrolling
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: mpeter.68...@simplelogin.co
  Target Milestone: ---

Created attachment 167999
  --> https://bugs.kde.org/attachment.cgi?id=167999=edit
steps to reproduce in images

Konsole version: 24.04.70
Source: gitlab CI release with name
'konsole-master-2985-windows-cl-msvc2022-x86_64'

SUMMARY
If I scroll a larger amount (like with Page Up/Down, or in vim with with '50
Ctrl+e'), the background color of multiple lines will be applied a specific
color.
The same happens if I scroll up after scrolling down, but sometimes it is also
happening if I just scroll down one line at a time.

So far I have only noticed this in vim, independently of whether it syntax
colors the file or not.

STEPS TO REPRODUCE
1. Find a file which is large enough that you can scroll it (example file
below)
2. Open this file in vim
a)
3. Scroll more than 1 line at once
b)
3. scroll down by pressing the down arrow on the keyboard
4. scroll back with the up arrow

I have also included an image with screenshots to help understand what is
happening.

The following is a file with which I can reproduce the problem, but any file
should do:
https://invent.kde.org/utilities/konsole/-/blob/ac11bc83b450196eb942e7b377b506fe332b7696/src/Application.cpp

OBSERVED RESULT
The background color of lines have changed

EXPECTED RESULT
The background colors stay unchanged

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
It appears that it does not matter whether vim uses colored text in the file or
not, the background color of blanks will change on scrolling regardless of
that.

The `less` command with the same file does not reproduce this problem.

While experiencing the problem in vim, I have found 2 ways that temporarly fix
the background colors of lines in the current view:
- resizing the terminal pane, or the whole window if the tab only has 1 pane
- using the "Visual Line" selection mode, if I go over with my cursor all the
affected lines twice (by moving the cursor so that the lines are selected and
then not anymore), it fixes up their background color. Some lines are fixed up
the first time they are reached, but some only partly.

It seems the incorrect background color of blanks is always the normal variant
of the "Color 3" color of the current color scheme. Changing the color scheme
changes the blanks' color to the appropriate color of the new color scheme.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=482645

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In|6.0.2   |Plasma 6.0.2 with
   ||Frameworks 6.1

--- Comment #23 from Nate Graham  ---
The icon changes are landing in Frameworks 6.1 in a few weeks; only the plasma
changes are already released.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=482198

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-systemmonitor/-/c |ma/plasma-systemmonitor/-/c
   |ommit/64c366458ce2064c07585 |ommit/21db049b4d43c81d212e2
   |62f634b75c7f72fc5ea |b1c973d0595c3d2602c
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #15 from Nate Graham  ---
Git commit 21db049b4d43c81d212e2b1c973d0595c3d2602c by Nate Graham, on behalf
of Arjen Hiemstra.
Committed on 31/03/2024 at 20:11.
Pushed by ngraham into branch 'Plasma/6.0'.

page: Store FaceController cache in QPointer

To make sure that we track deletion of FaceControllers if they get
destroyed.


(cherry picked from commit 64c366458ce2064c0758562f634b75c7f72fc5ea)

M  +8-2src/page/FaceLoader.cpp
M  +3-3src/page/FaceLoader.h

https://invent.kde.org/plasma/plasma-systemmonitor/-/commit/21db049b4d43c81d212e2b1c973d0595c3d2602c

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=482198

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In|6.0.3   |6.0.4

--- Comment #14 from Nate Graham  ---
Yup, looks like the cherry-pick got forgotten. :/ I'll do that real fast.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page

2024-03-31 Thread Bug Janitor Service 
https://bugs.kde.org/show_bug.cgi?id=482198

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED

--- Comment #13 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-systemmonitor/-/merge_requests/275

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

2024-03-31 Thread Fabian Vogt 
https://bugs.kde.org/show_bug.cgi?id=482819

Fabian Vogt  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #27 from Fabian Vogt  ---
(In reply to Matt Fagnani from comment #26)
> I switched /etc/pki/tls/openssl.cnf back to the old config and rebooted. I
> closed the wallet and ran killall kwalletd6 twice. I ran ltrace -fCe
> 'DH_*+OSSL_*' kwalletd6 I opened the wallet. I ran protonvpn-app which
> crashed. kwalletd6 crashed after some of the DH functions as shown in the
> output.
> 
> ltrace -fCe 'DH_*+OSSL_*' kwalletd6
...
> [pid 3603] libQt6Core.so.6->OSSL_PROVIDER_load(0, 0x7fb30e297499,
> 0x55d4cee99010, 1) = 0x7fb2e8001ff0
> [pid 3682] +++ exited (status 0) +++
> [pid 3603] --- SIGCHLD (Child exited) ---
> [pid 3683] --- Called exec() ---
> [pid 3683] +++ exited (status 0) +++
> [pid 3603] libQt6Core.so.6->OSSL_PROVIDER_unload(0x7fb2e8001ff0,
> 0x55d4cf2530c0, 0xfffa, 0x7fb30d9f3b20) = 1

This caught my attention now, I don't get this here. Looking at the code, this
is only in Qt since
https://github.com/qt/qtbase/commit/ddb1c75afe474e399fe9f5f839a9ac3873dee247
and would actually explain what happens.

By default, OpenSSL loads the "DEFAULT" provider, but only if no other provider
was loaded. That disables this logic:

https://www.openssl.org/docs/manmaster/man7/OSSL_PROVIDER-default.html:
> Automatic loading of the default provider only occurs a maximum of once; if 
> the default provider is explicitly unloaded then the default provider will 
> not be automatically loaded again.

It appears like Fedora backported the linked Qt commit, so Qt itself loads and
unloads the DEFAULT provider.

> [pid 3603] libqca-ossl.so->OSSL_PROVIDER_try_load(0, 0x7fb2f19a10f1, 1,
> 0x7fb30d9f3ac0 
> [pid 3603] legacy.so->OSSL_LIB_CTX_new_child(0x55d4cf2504b0, 0x7fb30c89f300,
> 24, 0x55d4cf26ac60) = 0x55d4cf25cfb0
> [pid 3603] <... OSSL_PROVIDER_try_load resumed> ) =
> 0x55d4cf2504b0
> [pid 3603] libqca-ossl.so->DH_new(0x55d4cf205910, 0x55d4cf2059f0,
> 0x55d4cf25a630, 0) = 0x7fb2f400bd30
> [pid 3603] libqca-ossl.so->DH_set0_pqg(0x7fb2f400bd30, 0x55d4cf24a2b0, 0,
> 0x55d4cf24a2d0) = 1
> [pid 3603] libqca-ossl.so->DH_generate_key(0x7fb2f400bd30, 0x7fb30c8511c0,
> 16, 0xb10b8f96a080e01d) = 0

As expected, DH_generate_key fails, causing the returned key to be null.

The Qt behavior also explains why it works with the config in comments 20 and
22, those load the default provider explicitly.

I'll leave a comment on https://bugreports.qt.io/browse/QTBUG-118227. I'm not
sure whether this is the right fix, but this should work:

diff --git a/plugins/qca-ossl/qca-ossl.cpp b/plugins/qca-ossl/qca-ossl.cpp
index f41fcbb5..0176da3b 100644
--- a/plugins/qca-ossl/qca-ossl.cpp
+++ b/plugins/qca-ossl/qca-ossl.cpp
@@ -6637,6 +6637,8 @@ public:
 if (OSSL_PROVIDER_try_load(nullptr, "legacy", 1)) {
 s_legacyProviderAvailable = true;
 }
+// No idea how to report failure here...
+OSSL_PROVIDER_try_load(nullptr, "default", 1);
 #else
 s_legacyProviderAvailable = true;
 #endif

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 483575] Delay time between click and menu appearing

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=483575

--- Comment #4 from Nate Graham  ---
I think you're noticing that the menu appears on mouse release, not on press.
This is done on purpose so that you can "change your mind" and release
elsewhere to avoid opening the menu. In your screencast, I think you're
clicking with various levels of speed, and observing that the menu opens slowly
when you do a click-and-briefly-press-and-release. But when you do a
"click-and-immediately-release", the menu opens faster. This would be by
design.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 482198] System Monitor crashes when discarding changes on edit page

2024-03-31 Thread bugsie 
https://bugs.kde.org/show_bug.cgi?id=482198

--- Comment #12 from bugsie  ---
(In reply to Dashon from comment #11)
> I went and built plasma system monitor from git master and the issue has
> indeed been fixed. Either something is wrong with the arch package for
> plasma-system-monitor version 6.0.3 or something wasn't cherry picked to the
> 6.0.3 bug fix release.

Still crashing in:
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland

(gdb) bt

  #0  0x7c50a17d562b in QObjectPrivate::connectImpl(QObject const*, int,
QObject const*, void**, QtPrivate::QSlotObjectBase*, int, int const*,
QMetaObject const*) ()
   from /lib/x86_64-linux-gnu/libQt6Core.so.6
#1  0x7c50a17d962b in QObject::connectImpl(QObject const*, void**, QObject
const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*,
QMetaObject const*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#2  0x7c50702ec83c in ?? () from
/lib/x86_64-linux-gnu/libPlasmaSystemMonitorPage.so
#3  0x7c50a282ae98 in ?? () from /lib/x86_64-linux-gnu/libQt6Qml.so.6
#4  0x7c50a28c1ec8 in ?? () from /lib/x86_64-linux-gnu/libQt6Qml.so.6
#5  0x7c50a28c9972 in
QQmlBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) ()
   from /lib/x86_64-linux-gnu/libQt6Qml.so.6
#6  0x7c50a28c7101 in
QQmlBinding::update(QFlags) () from
/lib/x86_64-linux-gnu/libQt6Qml.so.6
#7  0x7c50a2847ce3 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib/x86_64-linux-gnu/libQt6Qml.so.6
#8  0x7c50a28f8c67 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from
/lib/x86_64-linux-gnu/libQt6Qml.so.6
#9  0x7c50a28f9e7f in QQmlIncubationController::incubateFor(int) () from
/lib/x86_64-linux-gnu/libQt6Qml.so.6
#10 0x7c50a183c6ab in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#11 0x7c5097b01f21 in ?? () from /lib/x86_64-linux-gnu/libQt6Quick.so.6
#12 0x7c5097d09e84 in QQuickWindow::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt6Quick.so.6
#13 0x7c50a31f181b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt6Widgets.so.6
#14 0x7c50a1875e08 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt6Core.so.6
#15 0x7c50a1f2bf2c in QPlatformWindow::deliverUpdateRequest() () from
/lib/x86_64-linux-gnu/libQt6Gui.so.6
#16 0x7c50a17cc9b2 in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt6Core.so.6
#17 0x7c50a31f181b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt6Widgets.so.6
#18 0x7c50a1875e08 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt6Core.so.6
#19 0x7c50a1876000 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#20 0x7c50a16584f7 in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6
#21 0x7c50a089ad3b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7c50a08f0258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7c50a08983e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7c50a1655c30 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt6Core.so.6
#25 0x7c50a187fceb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt6Core.so.6
#26 0x7c50a187a36c in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt6Core.so.6
#27 0x5a9818e96b4a in ?? ()
#28 0x7c50a0c29d90 in __libc_start_call_main
(main=main@entry=0x5a9818e959d0, argc=argc@entry=1,
argv=argv@entry=0x7ffc34c24e08)
at ../sysdeps/nptl/libc_start_call_main.h:58
#29 0x7c50a0c29e40 in __libc_start_main_impl (main=0x5a9818e959d0, argc=1,
argv=0x7ffc34c24e08, init=, fini=, 
rtld_fini=, stack_end=0x7ffc34c24df8) at
../csu/libc-start.c:392
#30 0x5a9818e976c5 in ?? ()

Maybe related, it also crashes if one goes to "Applications" instead of
"Overview" and clicks "Show Details Sidebar".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484835] Proton games do not lock onto game window on a multi-monitor setup since 6.0.x

2024-03-31 Thread Paragoumba 
https://bugs.kde.org/show_bug.cgi?id=484835

Paragoumba  changed:

   What|Removed |Added

 CC||paragou...@proton.me

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland

2024-03-31 Thread Ashcon Mohseninia 
https://bugs.kde.org/show_bug.cgi?id=477124

--- Comment #19 from Ashcon Mohseninia  ---
Done. Filed bug 484835 for this

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484835] New: Proton games do not lock onto game window on a multi-monitor setup since 6.0.x

2024-03-31 Thread Ashcon Mohseninia 
https://bugs.kde.org/show_bug.cgi?id=484835

Bug ID: 484835
   Summary: Proton games do not lock onto game window on a
multi-monitor setup since 6.0.x
Classification: Plasma
   Product: kwin
   Version: 6.0.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ashco...@gmail.com
  Target Milestone: ---

Created attachment 167998
  --> https://bugs.kde.org/attachment.cgi?id=167998=edit
Demo showing the bug

SUMMARY
When playing a game on a multi-monitor setup, the mouse can escape the main
monitor (Where the game is being played), but is teleported back to the window
fairly quickly.

The issue is that when it is outside the window, clicking (IE: Firing a
weapon), instead causes the focus of the game to be lost, and the other
monitors become the focus.

What is interesting, is since 6.0.3, the game still looks around as if the
mouse is still present in the game window. Pre 6.0.3, the mouse would move
outside the window and the game would stop looking around.

STEPS TO REPRODUCE
1. Play a proton Game on any version of plasma 6.0.x on a multi-monitor setup
2. Try to look around
3. Notice that the mouse is escaping the main game window.

I've attached a video here to show the bug in action

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 484729] Reply to HTML mail using same visual style hangs Kmail

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484729

shivar...@gmail.com changed:

   What|Removed |Added

 CC||shivar...@gmail.com

--- Comment #1 from shivar...@gmail.com ---
Another victim of bug 482367 most probably.
Should be fixed in Qt 6.6.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 482476] Weird mouse and cursor behavior in video games

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=482476

--- Comment #26 from kaosu...@protonmail.com ---
Seems it fixed the issue for me too! 6.0.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 482367] kmail / kontact eates all my memory during startup and crashes than.

2024-03-31 Thread luna 
https://bugs.kde.org/show_bug.cgi?id=482367

--- Comment #14 from luna  ---
(In reply to shivarryn from comment #13)
> Good news!
> Problem is gone on my side after Qt 6.6.3 reached Arch.
> So yes, it was probably a Qt issue.
> If the other reporters can confirm after Qt 6.6.3 reaches your distros, we
> can close the bug.

I can also confirm that this is fixed on my Arch machine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 482367] kmail / kontact eates all my memory during startup and crashes than.

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=482367

--- Comment #13 from shivar...@gmail.com ---
Good news!
Problem is gone on my side after Qt 6.6.3 reached Arch.
So yes, it was probably a Qt issue.
If the other reporters can confirm after Qt 6.6.3 reaches your distros, we can
close the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=477124

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
   Version Fixed In||6.0.3

--- Comment #18 from Nate Graham  ---
"Looks a little different" means it's now a different issue; can I trouble you
to submit a new bug report for it? Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 482476] Weird mouse and cursor behavior in video games

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=482476

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WAITINGFORINFO
   Version Fixed In||6.0.3

--- Comment #25 from Nate Graham  ---
Great! aosob...@yahoo.de, can you confirm that?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 482575] Grid unable to be set in Screen Edges settings

2024-03-31 Thread Nate Graham 
https://bugs.kde.org/show_bug.cgi?id=482575

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In|6.0.3   |6.1

--- Comment #20 from Nate Graham  ---
I did, sorry about that.

Would be nice to backport the fix if it's technically feasible though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 484815] After playing a video, pause command no longer has any effect on the others videos you preview until you preview a photo.

2024-03-31 Thread Maik Qualmann 
https://bugs.kde.org/show_bug.cgi?id=484815

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
The problem cannot be reproduced here on Qt6 with QtMultimedia.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484661] repeated appearance of screen switching pop up with nothing being plugged in

2024-03-31 Thread faisal 
https://bugs.kde.org/show_bug.cgi?id=484661

--- Comment #2 from faisal  ---
changed product from Kscreen to kwin as I've just read that Kscreen no longer
handles multiscreen and is now handled by kwin.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484661] repeated appearance of screen switching pop up with nothing being plugged in

2024-03-31 Thread faisal 
https://bugs.kde.org/show_bug.cgi?id=484661

faisal  changed:

   What|Removed |Added

  Component|OSD and Plasma applet   |multi-screen
   Assignee|kscreen-bugs-n...@kde.org   |kwin-bugs-n...@kde.org
Product|KScreen |kwin

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

2024-03-31 Thread Matt Fagnani 
https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #26 from Matt Fagnani  ---
I switched /etc/pki/tls/openssl.cnf back to the old config and rebooted. I
closed the wallet and ran killall kwalletd6 twice. I ran ltrace -fCe
'DH_*+OSSL_*' kwalletd6 I opened the wallet. I ran protonvpn-app which crashed.
kwalletd6 crashed after some of the DH functions as shown in the output.

ltrace -fCe 'DH_*+OSSL_*' kwalletd6
kf.wallet.kwalletd: Lacking a socket, pipe: 0 env: 0
[pid 3618] +++ exited (status 0) +++
[pid 3617] +++ exited (status 0) +++
[pid 3616] +++ exited (status 0) +++
[pid 3615] +++ exited (status 0) +++
[pid 3614] +++ exited (status 0) +++
[pid 3613] +++ exited (status 0) +++
[pid 3654] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3655] --- Called exec() ---
[pid 3655] +++ exited (status 0) +++
[pid 3656] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3657] --- Called exec() ---
[pid 3657] +++ exited (status 0) +++
[pid 3658] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3659] --- Called exec() ---
[pid 3659] +++ exited (status 0) +++
[pid 3660] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3661] --- Called exec() ---
[pid 3661] +++ exited (status 0) +++
[pid 3662] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3663] --- Called exec() ---
[pid 3663] +++ exited (status 0) +++
[pid 3664] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3665] --- Called exec() ---
[pid 3665] +++ exited (status 0) +++
[pid 3677] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3678] --- Called exec() ---
[pid 3678] +++ exited (status 0) +++
[pid 3603] libQt6Core.so.6->OSSL_PROVIDER_load(0, 0x7fb30e297499,
0x55d4cee99010, 1) = 0x7fb2e8001ff0
[pid 3682] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3683] --- Called exec() ---
[pid 3683] +++ exited (status 0) +++
[pid 3603] libQt6Core.so.6->OSSL_PROVIDER_unload(0x7fb2e8001ff0,
0x55d4cf2530c0, 0xfffa, 0x7fb30d9f3b20) = 1
[pid 3603] libqca-ossl.so->OSSL_PROVIDER_try_load(0, 0x7fb2f19a10f1, 1,
0x7fb30d9f3ac0 
[pid 3603] legacy.so->OSSL_LIB_CTX_new_child(0x55d4cf2504b0, 0x7fb30c89f300,
24, 0x55d4cf26ac60) = 0x55d4cf25cfb0
[pid 3603] <... OSSL_PROVIDER_try_load resumed> ) =
0x55d4cf2504b0
[pid 3603] libqca-ossl.so->DH_new(0x55d4cf205910, 0x55d4cf2059f0,
0x55d4cf25a630, 0) = 0x7fb2f400bd30
[pid 3603] libqca-ossl.so->DH_set0_pqg(0x7fb2f400bd30, 0x55d4cf24a2b0, 0,
0x55d4cf24a2d0) = 1
[pid 3603] libqca-ossl.so->DH_generate_key(0x7fb2f400bd30, 0x7fb30c8511c0, 16,
0xb10b8f96a080e01d) = 0
[pid 3603] libqca-ossl.so->DH_free(0x7fb2f400bd30, 0x55d4cf205c30,
0x55d19269ff25, 6) = 12
[pid 3603] libqca-ossl.so->DH_new(0x55d4cf205c08, 0, 1, 2)=
0x7fb2f400bd30
[pid 3603] libqca-ossl.so->DH_set0_key(0x7fb2f400bd30, 0x55d4cf206bf0, 0, 1) =
1
[pid 3603] libqca-ossl.so->DH_set0_pqg(0x7fb2f400bd30, 0x55d4cf206160, 0,
0x55d4cf206180) = 1
[pid 3603] --- SIGSEGV (Segmentation fault) ---
[pid 3608] +++ killed by SIGSEGV +++
[pid 3606] +++ killed by SIGSEGV +++
[pid 3611] +++ killed by SIGSEGV +++
[pid 3612] +++ killed by SIGSEGV +++
[pid 3610] +++ killed by SIGSEGV +++
[pid 3609] +++ killed by SIGSEGV +++
[pid 3607] +++ killed by SIGSEGV +++
[pid 3605] +++ killed by SIGSEGV +++
[pid 3604] +++ killed by SIGSEGV +++
[pid 3603] +++ killed by SIGSEGV +++

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 482642] On X11, cannot change multi-screen settings via OSD

2024-03-31 Thread Akram Abdeslem Chaima 
https://bugs.kde.org/show_bug.cgi?id=482642

--- Comment #18 from Akram Abdeslem Chaima  ---
(In reply to Tony from comment #16)
> From what I can see, this bug seems to be half-fixed. Changing screen layout
> through system tray option/button is fixed and works as it should. Changing
> such option via OSD when you hit Meta + P still does nothing.
> 
> Plasma: 6.0.3
> Frameworks: 6.0.0
> Qt: 6.6.2

Exactly it's works in other parts , just via OSD selector there is no effect .

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 389568] Feature to reset all settings to default values

2024-03-31 Thread medin 
https://bugs.kde.org/show_bug.cgi?id=389568

--- Comment #40 from medin  ---
I confirm the need of such premium feature, after upgrading to Plasma 6, if you
keep your old user then you will surely suffer from high number of mysterious
bugs, and it also increases the number of bug reports in KDE tracker, which
makes it hard for devs to process them or reproduce them because they are
originally occurring in specific contexts.

Without this feature, any user who finish a major Plasma upgrade must create a
fresh new account in order to avoid those problems.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 482642] On X11, cannot change multi-screen settings via OSD

2024-03-31 Thread Akram Abdeslem Chaima 
https://bugs.kde.org/show_bug.cgi?id=482642

--- Comment #17 from Akram Abdeslem Chaima  ---
(In reply to Fushan Wen from comment #14)
> I myself cannot reproduce, but you can try to debug yourself by adding some
> qDebug in OsdAction::applyAction to see what is wrong

I tried to debug this but the same result

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 484834] New: Unable to rename console tabs

2024-03-31 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=484834

Bug ID: 484834
   Summary: Unable to rename console tabs
Classification: Applications
   Product: konsole
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tabbar
  Assignee: konsole-de...@kde.org
  Reporter: mpeter.68...@simplelogin.co
  Target Milestone: ---

Konsole version: 24.04.70
Source: gitlab CI release with name
'konsole-master-2985-windows-cl-msvc2022-x86_64'

SUMMARY
Renaming the tab in the "Tab Properties" window does not result in the new name
being applied, regardless of the active profile.

STEPS TO REPRODUCE
1. Open Konsole
1.1 If you dont see the tab bar, open a second tab
2. Rename a first tab (for example, to 'test')

OBSERVED RESULT
The tab does not use its new name.

EXPECTED RESULT
The tab uses its new name.

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
The given new name is preserved somewhere, as reopening this window will show
the new name, but the tab bar will keep the old name, more precisely the name
set by the inner shell (a special $PS1 can update it just fine).
This is the case not only with WSL Linux shells but with the Windows CMD shell
too.

It does not matter if I rename if I change the name both in the local and the
remote tab title format fields.

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 469193] hovered message's buttons move while scrolling

2024-03-31 Thread James Graham 
https://bugs.kde.org/show_bug.cgi?id=469193

James Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
 CC||james.h.graham@protonmail.c
   ||om

--- Comment #1 from James Graham  ---
This no longer happens on master and should also be sorted on the latest
release

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 454997] [Feature] Have option for sidebar on separate room window view

2024-03-31 Thread James Graham 
https://bugs.kde.org/show_bug.cgi?id=454997

James Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #1 from James Graham  ---
With the separate window mode being removed this is no longer going to be
implemented https://invent.kde.org/network/neochat/-/merge_requests/1642

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

2024-03-31 Thread Matt Fagnani 
https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

  1   2   3   >