[plasmashell] [Bug 482952] New: Showing error after logging in

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482952

Bug ID: 482952
   Summary: Showing error after logging in
Classification: Plasma
   Product: plasmashell
   Version: 6.0.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: asddsa...@gmail.com
  Target Milestone: 1.0

Application: plasmashell (6.0.1)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.8-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.0.1 [CoredumpBackend]

-- Information about the crash:
After logging in it shows this error message, I haven't done anything else just
logged in.

The crash can be reproduced every time.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 5260]
[New LWP 5296]
[New LWP 5297]
[New LWP 5275]
[New LWP 5571]
[New LWP 5575]
[New LWP 5573]
[New LWP 5576]
[New LWP 5513]
[New LWP 5580]
[New LWP 5495]
[New LWP 5499]
[New LWP 5512]
[New LWP 5581]
[New LWP 5498]
[New LWP 5509]
[New LWP 5274]
[New LWP 5582]
[New LWP 5510]
[New LWP 5579]
[New LWP 5788]
[New LWP 5395]
[New LWP 5807]
[New LWP 5511]
[New LWP 5574]
[New LWP 5270]
[New LWP 5302]
[New LWP 5303]
[New LWP 5578]
[New LWP 5304]
[New LWP 5305]
[New LWP 5497]
[New LWP 5486]
[New LWP 5496]
[New LWP 5572]
[New LWP 5577]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7806ee8ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7806e8c349c0 (LWP 5260))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7806e8c349c0 (LWP 5260))]

Thread 36 (Thread 0x780687e006c0 (LWP 5577)):
#0  0x7806ee8a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7806ee8a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7806edca3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7806edca64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7806edca0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7806ee8a955a in ??? () at /usr/lib/libc.so.6
#6  0x7806ee926a3c in ??? () at /usr/lib/libc.so.6

Thread 35 (Thread 0x7806aa8006c0 (LWP 5572)):
#0  0x7806ee8a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7806ee8a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7806edca3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7806edca64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7806edca0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7806ee8a955a in ??? () at /usr/lib/libc.so.6
#6  0x7806ee926a3c in ??? () at /usr/lib/libc.so.6

Thread 34 (Thread 0x7806b7e006c0 (LWP 5496)):
#0  0x7806ee8a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7806ee8a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7806d1c8685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x7806d1c9e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x7806ee8a955a in ??? () at /usr/lib/libc.so.6
#5  0x7806ee926a3c in ??? () at /usr/lib/libc.so.6

Thread 33 (Thread 0x7806c16006c0 (LWP 5486)):
#0  0x7806ee9190bf in poll () at /usr/lib/libc.so.6
#1  0x7806ec8882f6 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x7806ec828162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7806edd739c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x7806edb43d6e in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt6Core.so.6
#5  0x7806edc2106f in QThread::exec() () at /usr/lib/libQt6Core.so.6
#6  0x7806ef30d0d3 in ??? () at /usr/lib/libQt6Quick.so.6
#7  0x7806edca0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#8  0x7806ee8a955a in ??? () at /usr/lib/libc.so.6
#9  0x7806ee926a3c in ??? () at /usr/lib/libc.so.6

Thread 32 (Thread 0x7806a9a006c0 (LWP 5497)):
#0  0x7806ee8a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7806ee8a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7806d1c8685c in ??? () at /usr/lib/dri/iris_dri.so
#3  0x7806d1c9e82c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x7806ee8a955a in ??? () at /usr/lib/libc.so.6
#5  0x7806ee926a3c in ??? () at /usr/lib/libc.so.6

Thread 31 (Thread 0x7806c2a006c0 (LWP 5305)):
#0  0x7806ee8a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7806ee8a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7806d1c8685c in ??? () 

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #21 from caulier.gil...@gmail.com ---
can you try with the 8.3.0 pre-rellease available here :

https://files.kde.org/digikam/

Note : the database contents must be sync with the file metadata. Use
Tools/Maintenance/Sync Metadata and Database to do it

https://docs.digikam.org/en/maintenance_tools/maintenance_metadata.html

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=482944

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #20 from Maik Qualmann  ---
If the camera information is also shown as "unavailable", then the metadata has
not been read from the image. This problem has been reported by users from time
to time. We suspect a blockage if the images were opened in other programs
during the first scan or antivirus programs. Add digiKam and Exiftool in the
digiKam folder as an exception to the AntiVirus program. Perform a simple
re-read of the metadata from the image to the database, either via the album or
item menu. This will solve the problem for the images.

Maik

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

[krdc] [Bug 482950] KRDC RDP BLUE SCREEN SHOWS NOTHING

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482950

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[dolphin] [Bug 482951] Dolphin ServiceMenu's not working in kf6

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482951

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kde] [Bug 482830] Floating window doesn't float

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482830

--- Comment #1 from svsh...@gmail.com ---
Just checked what will happen on new user, still the same behavior.

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

[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font

[Guilherme Silva]

https://bugs.kde.org/show_bug.cgi?id=478549

Guilherme Silva  changed:

   What|Removed |Added

 CC||oguilhe...@protonmail.com

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

[kwin] [Bug 482818] Windows are moved after screen unlock

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482818

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

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

[dolphin] [Bug 482951] New: Dolphin ServiceMenu's not working in kf6

[PK]

https://bugs.kde.org/show_bug.cgi?id=482951

Bug ID: 482951
   Summary: Dolphin ServiceMenu's not working in kf6
Classification: Applications
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pieterkristen...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
***
The service-menu-files that I collected over the years in the folder
~/.local/share/kservices5/ServiceMenus don´t do anything in kf6.
Is it something I can fix? E.g. by putting them in a folder
~/.local/share/kservices6/ServiceMenus? Or do I have to have patience?
***

Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-25-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Celeron® J4105 CPU @ 1.50GHz
Memory: 7.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 600

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

[kwin] [Bug 482818] Windows are moved after screen unlock

[Marcin Juszkiewicz]

https://bugs.kde.org/show_bug.cgi?id=482818

--- Comment #2 from Marcin Juszkiewicz  ---
One 3440x1440 monitor.

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

[dolphin] [Bug 482525] drag and drop files to thunderbird and firefox

[tommaso]

https://bugs.kde.org/show_bug.cgi?id=482525

--- Comment #4 from tommaso  ---
(In reply to Nate Graham from comment #3)
> You're using the Wayland session, right?

Yes as the new plasma 6

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

[krdc] [Bug 482950] New: KRDC RDP BLUE SCREEN SHOWS NOTHING

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482950

Bug ID: 482950
   Summary: KRDC RDP BLUE SCREEN SHOWS NOTHING
Classification: Applications
   Product: krdc
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: RDP
  Assignee: uwol...@kde.org
  Reporter: hunterofgy...@gmail.com
CC: aa...@kde.org
  Target Milestone: ---

Created attachment 166779
  --> https://bugs.kde.org/attachment.cgi?id=166779=edit
BLUE SCREEN OF KRDC

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install Artix linux and use KRDC for a year without problems
2. a year later do sudo pacman -Syu
3. Plasma 6 installs
4. Attempt to use KRDC to RDP into Windows machine. The connection succeeds,
but it only shows a blue screen.

OBSERVED RESULT

BLUE SCREEN THAT DOES NOT SHOW ANYTHING

EXPECTED RESULT

BEING ABLE TO SEE THE MACHINE I RDP'd TO


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
ARTIX LINUX
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
X11 & WAYLAND


ADDITIONAL INFORMATION

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

[Powerdevil] [Bug 481308] screen locker black with cursor on X11

[Luke]

https://bugs.kde.org/show_bug.cgi?id=481308

--- Comment #33 from Luke  ---
(In reply to Bug Janitor Service from comment #31)
> A possibly relevant merge request was started @
> https://invent.kde.org/plasma/powerdevil/-/merge_requests/332

Following the logic of this merge request, I was able to fix the problem on my
PC by:
- enabling automatic screen turn-off;
- setting a long-enough LockGrace period.
In my case, LockGrace has to be at least 15 seconds; as soon as it’s set lower,
the unintentional screen turn-off happens again.

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

[plasmashell] [Bug 482908] Missing fallback icon for desktop-less MPRIS2 clients

[Fushan Wen]

https://bugs.kde.org/show_bug.cgi?id=482908

Fushan Wen  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi
   |t/9d92011d6022b57058ef8b02b |t/afa9e3406ba23a87cf4773f84
   |5384f42e3e3f687 |f917d6466a33fa3

--- Comment #3 from Fushan Wen  ---
Git commit afa9e3406ba23a87cf4773f84f917d6466a33fa3 by Fushan Wen, on behalf of
Guilherme Silva.
Committed on 09/03/2024 at 06:03.
Pushed by fusionfuture into branch 'Plasma/6.0'.

libkmpris: prevent an empty icon from being used

The previous logic would only use the fallback icon
("emblem-music-symbolic"), if the client had the "DesktopEntry"
property[1] set.

But since clients are allowed to omit that property completely
(mpd-mpris[2] does that), m_iconName would stay an empty string, and
clients would be left icon-less.

This change ensures that m_iconName is never an empty string.

[1]
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:DesktopEntry
[2] https://github.com/natsukagami/mpd-mpris/


(cherry picked from commit 9d92011d6022b57058ef8b02b5384f42e3e3f687)

M  +3-3libkmpris/playercontainer.cpp
M  +1-1libkmpris/playercontainer.h

https://invent.kde.org/plasma/plasma-workspace/-/commit/afa9e3406ba23a87cf4773f84f917d6466a33fa3

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

[frameworks-kded] [Bug 466467] Frameworks 5.103: wireless extensions that are deprecated for modern drivers; use nl80211

[panorain]

https://bugs.kde.org/show_bug.cgi?id=466467

--- Comment #5 from panorain  ---
Hi, I became aware of the error shown by dmesg on the machine here yesterday
and while discussing it on IRC was referred here by a more advanced user.

warning: `kded5' uses wireless extensions which will stop working for Wi-Fi 7
hardware; use nl80211

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

[plasmashell] [Bug 482543] Reset the circle of wallpaper slideshow

[Ali]

https://bugs.kde.org/show_bug.cgi?id=482543

--- Comment #2 from Ali  ---
(In reply to Nate Graham from comment #1)
> I gather you set the order to something other than "Random"?

No, Order is A to Z

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

[plasmashell] [Bug 482908] Missing fallback icon for desktop-less MPRIS2 clients

[Guilherme Silva]

https://bugs.kde.org/show_bug.cgi?id=482908

Guilherme Silva  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/-/commi
   ||t/9d92011d6022b57058ef8b02b
   ||5384f42e3e3f687
 Resolution|--- |FIXED

--- Comment #2 from Guilherme Silva  ---
Git commit 9d92011d6022b57058ef8b02b5384f42e3e3f687 by Guilherme Silva.
Committed on 09/03/2024 at 05:30.
Pushed by fusionfuture into branch 'master'.

libkmpris: prevent an empty icon from being used

The previous logic would only use the fallback icon
("emblem-music-symbolic"), if the client had the "DesktopEntry"
property[1] set.

But since clients are allowed to omit that property completely
(mpd-mpris[2] does that), m_iconName would stay an empty string, and
clients would be left icon-less.

This change ensures that m_iconName is never an empty string.

[1]
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:DesktopEntry
[2] https://github.com/natsukagami/mpd-mpris/

M  +3-3libkmpris/playercontainer.cpp
M  +1-1libkmpris/playercontainer.h

https://invent.kde.org/plasma/plasma-workspace/-/commit/9d92011d6022b57058ef8b02b5384f42e3e3f687

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

[kwin] [Bug 482805] Cursor is enlarged in some applications.

[Kalcifer]

https://bugs.kde.org/show_bug.cgi?id=482805

--- Comment #2 from Kalcifer  ---
> What scale factor (if any) are you using?

I am not scaling at all — it is at 100% on all monitors.

> Do you have the xsettingsd package installed?

I do.

Side note, this may be an issue with Flatpak in KDE Plasma 6. An update for
KWrite came out, and, after updating, the problem went away for KWrite. I have
also noticed that system themes are not being applied to other flatpak
applications now e.g. Signal Desktop (as in the menu bar is in a light theme
when it should be a dark theme — prior to updating to Plasma 6, it was a dark
theme). [I have also heard the same anectode from
others]https://sh.itjust.works/comment/9628686).

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

[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications

[vodka]

https://bugs.kde.org/show_bug.cgi?id=481069

vodka  changed:

   What|Removed |Added

 CC||vodka...@gmail.com

--- Comment #15 from vodka  ---
I'd like to add that this feature was one of my main reasons for switching to
KDE.
A really easy way to run a command for a notification is great, and not having
to faff about with custom services monitoring dbus activities.

This is a huge loss for me, being able to just quickly add a command to the
lock/unlock notification from the screensaver and not have to  struggle with a
service is probably the best feature of KDE.

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

[kwin] [Bug 481577] ship a window rule to keep picture-in-picture windows above

[Mariusz Libera]

https://bugs.kde.org/show_bug.cgi?id=481577

Mariusz Libera  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 Status|REPORTED|RESOLVED

--- Comment #6 from Mariusz Libera  ---
(In reply to Nate Graham from comment #5)
> An exact title match for "Picture-in-Picture" might work in English, but
> does this still work if the system is in another language?

Good point, just checked, Firefox does indeed translate that. Wouldn't expect
it. Well, this is pretty hopeless then.

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

[kde] [Bug 482943] System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1

[Neal Gompa]

https://bugs.kde.org/show_bug.cgi?id=482943

Neal Gompa  changed:

   What|Removed |Added

 CC||ngomp...@gmail.com

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

[plasmashell] [Bug 482948] Digital Clock panel does not reflect changes in Calendar Events plugins

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482948

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kate] [Bug 482946] Kate crashed while editing

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482946

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kdenlive] [Bug 482949] Nested sequence fails to update, after audio change

[red_Arti]

https://bugs.kde.org/show_bug.cgi?id=482949

--- Comment #1 from red_Arti  ---
Created attachment 166778
  --> https://bugs.kde.org/attachment.cgi?id=166778=edit
bug_3seq_audio_not_updated

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #16 from b...@plushkava.net ---
As to Nate's request, I just tested with a Microsoft Compact Optical Mouse 500
v2.0 and had dsda-doom malfunction after the third try.

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

[kdenlive] [Bug 482949] New: Nested sequence fails to update, after audio change

[red_Arti]

https://bugs.kde.org/show_bug.cgi?id=482949

Bug ID: 482949
   Summary: Nested sequence fails to update, after audio change
Classification: Applications
   Product: kdenlive
   Version: git-master
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: jijili...@yandex.com
  Target Milestone: ---

SUMMARY
3 sequences nested.
After changing audio in 1st sequence, Kdenlive fails to update audio in 3rd
sequence.

STEPS TO REPRODUCE
1. Create project (Project folder option: Parant folder of project file)
2. Add a video clip (with audio) to Seq1 
3. Create Seq2. Add Seq1 into Seq 2
4. Create Seq3. Add Seq2 into Seq 3
5. Save (click 'yes' for moving temporary files). Close. Reopen the project
6. Swtich to Seq1 tab. Ungroup the clip, and then delete audio
7. Switch to Seq3 tab. Play

OBSERVED RESULT
In Seq3, it plays audio, which has been deleted in Seq1 and shouldn't be
played.

EXPECTED RESULT
No audio in Seq3

SOFTWARE/OS VERSIONS
Latest git master ci build kdenlive-master-7593-linux-gcc-x86_64.AppImage

ADDITIONAL INFORMATION
You have to switch to Seq2 and do some change, then it updates in Seq3, then
everything seems fine

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

[kate] [Bug 482946] Kate crashed while editing

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482946

--- Comment #1 from Kishore Gopalakrishnan  ---
It happened again; this time, I was using the split view. The backtrace looks
very different from https://bugs.kde.org/show_bug.cgi?id=481654, though, and
similar to the one I posted here.

I also see some stuff saying 'UTF8' in the backtrace. I am not sure if it is
relevant that I am using a non-Latin language (Tamil) as my system language
(nevertheless, during these crashes, I was editing files with only English
text).


Thread 1 (Thread 0x70d74332fe80 (LWP 89395)):
[KCrash Handler]
#4  0x70d748cab32c in ??? () at /usr/lib/libc.so.6
#5  0x70d748c5a6c8 in raise () at /usr/lib/libc.so.6
#6  0x70d748c424b8 in abort () at /usr/lib/libc.so.6
#7  0x70d748c423dc in ??? () at /usr/lib/libc.so.6
#8  0x70d748c52d46 in __assert_fail () at /usr/lib/libc.so.6
#9  0x70d738373bdc in rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator
>::operator[] >
(this=, name=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1226
#10 rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator
>::operator[] >
(name=, this=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1226
#11 rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >::operator[] (name=, this=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1211
#12 rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >::operator[] (name=, this=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/rapidjson/include/rapidjson/document.h:1214
#13 parseLocationLink (loc=...) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:623
#14 parseDocumentLocation (result=) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:777
#15 0x70d738386d64 in std::__invoke_impl,
QList (*&)(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&),
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&>
(__f=) at /usr/include/c++/13.2.1/bits/invoke.h:60
#16 std::__invoke_r, QList
(*&)(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&),
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&>
(__fn=) at /usr/include/c++/13.2.1/bits/invoke.h:116
#17 std::_Function_handler
(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&),
QList (*)(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >
const&)>::_M_invoke(std::_Any_data const&,
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&)
(__functor=, __args#0=) at
/usr/include/c++/13.2.1/bits/std_function.h:291
#18 0x70d738388c41 in std::function
(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >
const&)>::operator()(rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > const&) const
(__args#0=, this=0x5aff0feccb70) at
/usr/include/c++/13.2.1/bits/std_function.h:591
#19 operator() (m=, __closure=0x5aff0feccb40) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:2096
#20 std::__invoke_impl
>(ReplyHandler >&, const QObject*,
utils::identity(const
rapidjson::GenericValue >&)> >::type)::&, const rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >&> (__f=...) at
/usr/include/c++/13.2.1/bits/invoke.h:61
#21 std::__invoke_r
>(ReplyHandler >&, const QObject*,
utils::identity(const
rapidjson::GenericValue >&)> >::type)::&, const rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator >&> (__fn=...) at
/usr/include/c++/13.2.1/bits/invoke.h:111
#22 std::_Function_handler,
rapidjson::MemoryPoolAllocator >&),
make_handler >(ReplyHandler >&,
const QObject*, utils::identity(const
rapidjson::GenericValue >&)> >::type):: >::_M_invoke(const std::_Any_data &, const
rapidjson::GenericValue,
rapidjson::MemoryPoolAllocator > &)
(__functor=, __args#0=) at
/usr/include/c++/13.2.1/bits/std_function.h:290
#23 0x70d73837e9e8 in std::function::operator()(LSPApplyWorkspaceEditResponse const&) const
(__args#0=, this=0x7ffc164853c0) at
/usr/include/c++/13.2.1/bits/std_function.h:591
#24 LSPClientServer::LSPClientServerPrivate::readStandardOutput
(this=0x5aff0f23a9b0) at
/usr/src/debug/kate/kate-24.02.0/addons/lspclient/lspclientserver.cpp:1523
#25 0x70d749390ca9 in ??? () at /usr/lib/libQt6Core.so.6
#26 0x70d7494f642f in ??? () at /usr/lib/libQt6Core.so.6
#27 0x70d7494fdb35 in ??? () at /usr/lib/libQt6Core.so.6
#28 0x70d749390fab in ??? () at /usr/lib/libQt6Core.so.6
#29 0x70d749398530 in QSocketNotifier::event(QEvent*) () at
/usr/lib/libQt6Core.so.6
#30 0x70d74a2f438b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt6Widgets.so.6
#31 0x70d749339818 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt6Core.so.6
#32 0x70d7495754d1 in ??? () at /usr/lib/libQt6Core.so.6
#33 0x70d74765af69 in ??? () at /usr/lib/libglib-2.0.so.0
#34 0x70d7476b93a7 in ??? () at /usr/lib/libglib-2.0.so.0
#35 

[frameworks-kded] [Bug 466467] Frameworks 5.103: wireless extensions that are deprecated for modern drivers; use nl80211

[panorain]

https://bugs.kde.org/show_bug.cgi?id=466467

panorain  changed:

   What|Removed |Added

 CC||pj.wo...@gmx.com

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

[Spectacle] [Bug 482605] Magnifier no longer works

[Noah Davis]

https://bugs.kde.org/show_bug.cgi?id=482605

--- Comment #9 from Noah Davis  ---
(In reply to Jet from comment #6)
> if i hold shift, but not move the cursor, it wont
> appear until i do move it. I would expect the magnifier view to update
> independent of cursor movement

It should appear next to the mouse cursor without needing to move the cursor.
At least that's how it works for me.

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #15 from b...@plushkava.net ---
(In reply to Sandro from comment #9)
> When I'm having this issue and open the kwin debug console (using krunner),
> the issue is gone and things work reliably afterwards (even after closing
> the debug console).

This is not the case for me, at least with the games that I am testing (none of
which have involved wine).

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

[plasmashell] [Bug 482948] New: Digital Clock panel does not reflect changes in Calendar Events plugins

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482948

Bug ID: 482948
   Summary: Digital Clock panel does not reflect changes in
Calendar Events plugins
Classification: Plasma
   Product: plasmashell
   Version: 6.0.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: el...@seznam.cz
  Target Milestone: 1.0

SUMMARY
***
I have enabled calendar plugin "Calendar Events". When I try to configure this
plugin, changes are not reflected and data from all calendars are always shown.
***


STEPS TO REPRODUCE
1. Configure Akonadi resource with multiple calendars and each calendar should
have some events
2. Go to Digital Clock settings
3. Enable Calendar Events plugin in Calendar tab, click Apply
4. Go to Calendar Events tab and select some calendars
5. Click apply and check Digital Clock

OBSERVED RESULT
It doesn't matter what calendars I select, widget always shows data from all
calendars. When I close settings and reopen them, my selection is not
remembered and no calendars are checked.

EXPECTED RESULT
I should only see data from selected calendars.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[systemsettings] [Bug 482947] Screen turns off automatically with Plasma 6

[William AC]

https://bugs.kde.org/show_bug.cgi?id=482947

William AC  changed:

   What|Removed |Added

 CC||warca...@live.com

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

[systemsettings] [Bug 482947] New: Screen turns off automatically with Plasma 6

[William AC]

https://bugs.kde.org/show_bug.cgi?id=482947

Bug ID: 482947
   Summary: Screen turns off automatically with Plasma 6
Classification: Applications
   Product: systemsettings
   Version: 6.0.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_powerdevil
  Assignee: plasma-b...@kde.org
  Reporter: warca...@live.com
CC: k...@privat.broulik.de, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 166777
  --> https://bugs.kde.org/attachment.cgi?id=166777=edit
my current Energy Saving settings

SUMMARY
I just installed Endeavouros with KDE Plasma 6, and I’m getting this problem
with my screen even when Energy Saving is unchecked all its properties (see
attachment). My screen persists in turning off after 5 or 7 minutes, sometimes
it fails to recover after making movements with the mouse and stays off. This
did not happen with Plasma 5.

STEPS TO REPRODUCE
1. Uncheck all properties on Energy Saving settings
2. Apply changes
3. Don't touch/move anything on your PC for 7 minutes at least 

OBSERVED RESULT
Screen turns off

EXPECTED RESULT
Screen stays on

SOFTWARE/OS VERSIONS
- OS: EndeavourOS Linux x86_64
- Kernel: 6.7.9-zen1-1-zen
- Shell: zsh 5.9
- Resolution: 3440x1440
- DE: Plasma 6.0.1
- WM: KWin
- Icons: breeze [GTK2/3]
- Terminal: WarpTerminal
- CPU: AMD Ryzen 7 1700 (16) @ 3.800GHz
- GPU: NVIDIA GeForce GTX 1070
- Memory: 15905MiB
- KDE Frameworks version: 6.0.0
- Qt version: 6.6.2
- Monitor: Huawei ZQE-CBA

ADDITIONAL INFORMATION

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #14 from b...@plushkava.net ---
I forgot to say, regarding Comment 13, this is something that I have never seen
happen before, whether it be while using Wayland with 5.27.10 or X11 with any
version of Plasma.

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #13 from b...@plushkava.net ---
I have another observation to make. Occasionally, I found that switching back
to dsda-doom with Alt-Tab - away from the terminal in which I launched libinput
- would yield a sudden burst of in-game movement, almost as if a sizeable batch
of events had suddenly been drained and handled normally. Following that, the
behaviour would again be as already described for this bug, with no solution
but to quit the game and try running it again.

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

[kwin] [Bug 482780] Incorrect color gamut with HDR enabled

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482780

--- Comment #7 from northon_patri...@yahoo.ca ---
Created attachment 166776
  --> https://bugs.kde.org/attachment.cgi?id=166776=edit
Window border effect: HDR version.

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

[kwin] [Bug 482780] Incorrect color gamut with HDR enabled

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482780

northon_patri...@yahoo.ca changed:

   What|Removed |Added

 CC||northon_patri...@yahoo.ca

--- Comment #6 from northon_patri...@yahoo.ca ---
Created attachment 166775
  --> https://bugs.kde.org/attachment.cgi?id=166775=edit
Window border effect: SDR version.

Same issue on 3 different screens, on AMD. Colors look washed out and wrong
even playing with the sliders.

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #12 from b...@plushkava.net ---
Created attachment 166774
  --> https://bugs.kde.org/attachment.cgi?id=166774=edit
bug482629-pointer-motion-bad.txt

A sequence of POINTER_MOTION events, captured from a DeathAdder V2 with
libinput(1) in the case that dsda-doom was responding abnormally.

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #11 from b...@plushkava.net ---
Created attachment 166773
  --> https://bugs.kde.org/attachment.cgi?id=166773=edit
bug482629-pointer-motion-good.txt

A sequence of POINTER_MOTION events, captured from a DeathAdder V2 with
libinput(1) in the case that dsda-doom was responding normally.

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

[kwin] [Bug 482629] FPS games sometimes respond incorrectly to mouse input after upgrading from 5.27.10 to 6.0.0

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482629

--- Comment #10 from b...@plushkava.net ---
I ran dsda-doom while tracing POINTER_MOTION events with libinput debug-events,
thrice moving the mouse clockwise in a broad circle, pausing for a short time
in between. I did all of this twice, once with the bug in effect and once
without. Unfortunately, there is no meaningful disparity between the two sets
of readings, nor do they reveal anything that appears interesting. I shall
attach the results anyway.

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

[kate] [Bug 482946] New: Kate crashed while editing

[Kishore Gopalakrishnan]

https://bugs.kde.org/show_bug.cgi?id=482946

Bug ID: 482946
   Summary: Kate crashed while editing
Classification: Applications
   Product: kate
   Version: 24.02.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kishor...@gmail.com
  Target Milestone: ---

Application: kate (24.02.0)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.8-arch1-1 x86_64
Windowing System: X11
Distribution: Arch Linux
DrKonqi: 6.0.1 [CoredumpBackend]

-- Information about the crash:
I was editing a remote file over SFTP. I had just saved the file by pressing
Ctrl+S, and I started scrolling down. Kate then crashed.

I have been facing crashes also while editing local files (only after upgrading
to 24.02).

Since the crash seems to be related to the LSP, I will note that I was editing
a Python file when this crash happened (the LSP plugin was using pylsp). I have
also had crashes happen while editing Fortran files (in which case the fortls
LSP server is used), but I haven't obtained a backtrace with such a crash yet.

I have built Kate from source on my machine (along with debug symbols) using
the Arch PKGBUILD.

The crash can be reproduced sometimes.

-- Backtrace:
Application: கேட் (kate), signal: Aborted

[New LWP 7433]
[New LWP 7459]
[New LWP 7462]
[New LWP 7658]
[New LWP 87539]
[New LWP 7652]
[New LWP 87644]
[New LWP 87645]
[New LWP 7651]
[New LWP 7653]
[New LWP 87646]
[New LWP 87647]
[New LWP 7648]
[New LWP 7656]

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/kate -session
1021b2181d61a17057267300037970296_1709818453_841'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7196fa2ab32c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7196f492fe80 (LWP 7433))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7196f492fe80 (LWP 7433))]

Thread 14 (Thread 0x7196e8e006c0 (LWP 7656)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at /usr/lib/dri/radeonsi_dri.so
#4  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#5  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7196f1e006c0 (LWP 7648)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at /usr/lib/dri/radeonsi_dri.so
#4  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#5  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7196d18006c0 (LWP 87647)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7196faaa3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7196faaa64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7196faaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#6  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7196d38006c0 (LWP 87646)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8a65 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x7196faaa3ba4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7196faaa64aa in ??? () at /usr/lib/libQt6Core.so.6
#4  0x7196faaa0bd3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#6  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7196e9a006c0 (LWP 7653)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at /usr/lib/dri/radeonsi_dri.so
#4  0x7196fa2a955a in ??? () at /usr/lib/libc.so.6
#5  0x7196fa326a3c in ??? () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7196f14006c0 (LWP 7651)):
#0  0x7196fa2a5ebe in ??? () at /usr/lib/libc.so.6
#1  0x7196fa2a8750 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7196e9c8681c in ??? () at /usr/lib/dri/radeonsi_dri.so
#3  0x7196e9c9e7ec in ??? () at 

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

mlh.k...@gmail.com changed:

   What|Removed |Added

Version|8.3.0   |8.2.0

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #19 from mlh.k...@gmail.com ---
(In reply to caulier.gilles from comment #17)
> Can you take a screen capture of the dysfunction under Windows ?

I have shared the link to that it

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #18 from mlh.k...@gmail.com ---
https://drive.google.com/file/d/16HYGvAO0HgZ_sS2RKoqQvVR8CGTVUpMs/view?usp=sharing

On Sat, 9 Mar 2024 at 17:30,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=482944
>
> --- Comment #17 from caulier.gil...@gmail.com ---
> Can you take a screen capture of the dysfunction under Windows ?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #17 from caulier.gil...@gmail.com ---
Can you take a screen capture of the dysfunction under Windows ?

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #16 from mlh.k...@gmail.com ---
(In reply to mlh.kiwi from comment #15)
> (In reply to caulier.gilles from comment #14)
> > No problem here with a mac M1. no special settings.
> > 
> > https://imgur.com/a/rB1Cr9x
> 
> where was it sorted to? What does the date say?

I can see in the screenshot it was sorted correctly

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #15 from mlh.k...@gmail.com ---
(In reply to caulier.gilles from comment #14)
> No problem here with a mac M1. no special settings.
> 
> https://imgur.com/a/rB1Cr9x

where was it sorted to? What does the date say?

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #14 from caulier.gil...@gmail.com ---
No problem here with a mac M1. no special settings.

https://imgur.com/a/rB1Cr9x

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

[Powerdevil] [Bug 481308] screen locker black with cursor on X11

[Steven Noonan]

https://bugs.kde.org/show_bug.cgi?id=481308

--- Comment #32 from Steven Noonan  ---
Tried applying the patch in the powerdevil merge request and rebuilt/installed
poweredevil. From what I can tell it had no impact on either the escape key
behavior or the blank lock screen render.

I notice that when I get the black screen with mouse cursor, I can move the
mouse over where the password field should be and it turns into the I-beam
cursor, and I am able to type in the field and unlock the screen. Doing so
causes it to present a few frames of what the locker *should* have been
rendering before the locker exits. And I can run `kscreenlocker_greet --test`
(or without `--test`) and it renders fine, so I'm not sure exactly what is
causing it to render the black screen.

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

[plasmashell] [Bug 482618] Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland, not x.

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482618

--- Comment #7 from Anon  ---
(In reply to Marco Martin from comment #2)
> can you attach the file ~/.config/plasma-org.kde.plasma.desktop-appletsrc  ?

Added. I just replaced file and directory names with fake data, Everything else
is as is.

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

[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

mlh.k...@gmail.com changed:

   What|Removed |Added

Summary|The date is wrong! Simply   |The date is wrong! Digikam
   |put the date inside digikam |appears to be using
   |is not the "date taken"!|modified date not the
   ||create date despite there
   ||being a "date taken" tag in
   ||windows properties.

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

[plasmashell] [Bug 482618] Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland, not x.

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482618

--- Comment #6 from Anon  ---
Created attachment 166771
  --> https://bugs.kde.org/attachment.cgi?id=166771=edit
Config

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #13 from mlh.k...@gmail.com ---
(In reply to caulier.gilles from comment #11)
> Read also this entry:
> 
> https://bugs.kde.org/show_bug.cgi?id=384086
> 
> And please provide a JPEg file samples to test here. Use a Cloud
> web-service.  
> 
> Gilles Caulier

https://drive.google.com/file/d/1YMMDJEYidw72mDfNv7zIxj9ULrEiWqxS/view?usp=sharing

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #12 from mlh.k...@gmail.com ---
sample JPG: I know where the fake date is from. It is the modified date.
But this should not be used as there is a date and time orginal

On Sat, 9 Mar 2024 at 17:06,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=482944
>
> --- Comment #11 from caulier.gil...@gmail.com ---
> Read also this entry:
>
> https://bugs.kde.org/show_bug.cgi?id=384086
>
> And please provide a JPEg file samples to test here. Use a Cloud
> web-service.
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[plasmashell] [Bug 482618] Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland, not x.

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482618

--- Comment #5 from Anon  ---
(In reply to Marco Martin from comment #1)
> was an update from 5.27 or an older one? (screen mapping changed in 5.27 and
> in 6.0 is still the logic introduced there)

It was the most recent one prior to 6.0.0. I update every 1-2 days to stay
current and get all the great new features in Plasma.

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

[plasmashell] [Bug 482618] Panels on two monitors were switched after update to Plasma 6.0.0 in Wayland, not x.

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482618

--- Comment #4 from Anon  ---
(In reply to Nate Graham from comment #3)
> > (or maybe the external monitor has been made primary; I didn't think to 
> > check that possibility) 
> Can you do it and report back on which one of the two options is the correct
> one?

That's what happened. In X, the laptop screen is primary. In Wayland (fresh
session after 6.0.0 update. I had never used Wayland before) the external
screen is primary.

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #10 from Anon  ---
Created attachment 166769
  --> https://bugs.kde.org/attachment.cgi?id=166769=edit
Closing laptop screen moves dolphin too far up and moves other window

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #9 from Anon  ---
Created attachment 166768
  --> https://bugs.kde.org/attachment.cgi?id=166768=edit
Two screens, Dolphin on laptop screen

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #8 from Anon  ---
(In reply to Nate Graham from comment #3)
> Interesting, cannot reproduce when I use the same setup.
> 
> Can you attach a screenshot of the Display & Monitor page in System Settings
> that shows your screen layout? Maybe that's a factor, and it only affects
> certain layouts.

I've uploaded screenshots of the two screens with Dolphin open on the external
monitor, first with the laptop screen open, next with it closed. In the closed
scenario, Dolphin has moved significantly.

Of note:

* Before 6.0.0 I only used X
* In X the laptop screen is set as primary
* In the Wayland session, for some reason the external monitor set itself as
primary (this explains another bug I filed where the panels are on the wrong
screen https://bugs.kde.org/show_bug.cgi?id=482618 but I did not set the
external screen as primary, a fresh unused Wayland session after the 6.0.0
update did that)
* The mouse pointer moves across screens as expected (so the physical layout of
the screens and the logical layout in the settings are in agreement and
correct)
* When I put the Dolphin window on the laptop screen, and close the laptop
screen, Dolphin moves up to the external monitor (good) but pushed way up and
cut off (not good). Another window that was open on the external monitor also
moves (not good).

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #11 from caulier.gil...@gmail.com ---
Read also this entry:

https://bugs.kde.org/show_bug.cgi?id=384086

And please provide a JPEg file samples to test here. Use a Cloud web-service.  

Gilles Caulier

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #10 from caulier.gil...@gmail.com ---
And about the XMP sidecar usage ?

I suspect that the metadata parser (Exiv2 library used in background) do not
like well your files from your camera.

You can try to use ExifTool backend instead but it's not guaranty.

https://docs.digikam.org/en/setup_application/metadata_settings.html#behavior-settings

Gilles caulier

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

[kwin] [Bug 463239] no shadow effect for electron applications and adding window decoration manually breaks some parts of the application

[quangngo]

https://bugs.kde.org/show_bug.cgi?id=463239

quangngo  changed:

   What|Removed |Added

 CC||ngoquang2...@gmail.com

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #7 from Anon  ---
Created attachment 166767
  --> https://bugs.kde.org/attachment.cgi?id=166767=edit
Display properties in Wayland, primary screen is wrong

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #6 from Anon  ---
Created attachment 166766
  --> https://bugs.kde.org/attachment.cgi?id=166766=edit
Display properties in X11, correct

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #5 from Anon  ---
Created attachment 166765
  --> https://bugs.kde.org/attachment.cgi?id=166765=edit
Laptop screen closed, window moves

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

[kwin] [Bug 482608] Windows on external monitor are shifted up by a large amount when closing laptop

[Anon]

https://bugs.kde.org/show_bug.cgi?id=482608

--- Comment #4 from Anon  ---
Created attachment 166764
  --> https://bugs.kde.org/attachment.cgi?id=166764=edit
Laptop screen open, looking good

Laptop is the bottom screen.

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

[kwin] [Bug 480992] Kwin (wayland) crashes after idle for about one hour

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=480992

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[systemsettings] [Bug 481703] plasma-localerc leads to a defunct locale configuration

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=481703

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kwin] [Bug 481693] Touchscreen mapping does nothing when you have multiple monitors

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=481693

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

[plasmashell] [Bug 433953] plasma systemmonitor desktop widget: network device specific sensors are not remembered

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=433953

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #9 from mlh.k...@gmail.com ---
(In reply to caulier.gilles from comment #5)
> "Did you import files using camera import tool from digiKam ?
> " No, was I meant to?
> 
> Well, you import files directly as collections. So respond to others Q...
> 
> Gilles Caulier

I have responded to all your Q please help, otherwise this digiKam is unusable

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

[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits

[Maria Keating]

https://bugs.kde.org/show_bug.cgi?id=481113

Maria Keating  changed:

   What|Removed |Added

 CC||ma...@mariakeating.com

--- Comment #12 from Maria Keating  ---
(In reply to Sam James from comment #9)
> Has anybody hit this on non-Gentoo yet? I haven't started looking at this
> yet, but it's an important factor if everyone hitting it is on Gentoo.

I experienced the bug on Alpine.

(In reply to Nate Graham from comment #10)
> Folks able to reproduce this issue, are you by any chance *not* using the
> systemd boot feature?

Not using systemd boot here when experiencing the issue due to the installs
being openrc systems (both Alpine and Gentoo).

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

[plasmashell] [Bug 453687] Floating panel on one screen also makes the panel on another screen "floating"

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=453687

--- Comment #3 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 449831] [X11] Meta+[number] shortcut working in opened-order instead of task manager order, and pinned apps get ignored

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=449831

--- Comment #3 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kwin] [Bug 479781] Switching between windows is slow in some cases

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=479781

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

[plasmashell] [Bug 449115] 24h clock with 9:59 is larger font than 10:00 in vertical panel

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=449115

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=423676

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

[plasmashell] [Bug 446024] KDE crashes and brings me back to login screen when hitting Super + ESC + F1

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=446024

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #8 from mlh.k...@gmail.com ---
I notice the make and model of the camera is also reported as unavailable?

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #7 from mlh.k...@gmail.com ---
How could this happen some of the photos are sorted properly others have
completely false dates despite there being an original date.

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #6 from mlh.k...@gmail.com ---
I did import yes as a folder I think.

On Sat, 9 Mar 2024 at 16:40,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=482944
>
> --- Comment #5 from caulier.gil...@gmail.com ---
> "Did you import files using camera import tool from digiKam ?
> " No, was I meant to?
>
> Well, you import files directly as collections. So respond to others Q...
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #5 from caulier.gil...@gmail.com ---
"Did you import files using camera import tool from digiKam ?
" No, was I meant to?

Well, you import files directly as collections. So respond to others Q...

Gilles Caulier

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #4 from mlh.k...@gmail.com ---
(In reply to caulier.gilles from comment #1)
> Hi,
> 
> Which file format didi you use ?
> 
> Which camera model did you use ?
> 
> Did you import files using camera import tool from digiKam ? If yes, take a
> look to these settings :
> 
> https://docs.digikam.org/en/setup_application/camera_settings.html#customize-
> the-behavior
> 
> Also check well how metadata are taken from XMP side car (if you use it)
> with these settings:
> 
> https://docs.digikam.org/en/setup_application/metadata_settings.
> html#sidecars-settings
> 
> Gilles Caulier

file format was JPG

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #3 from mlh.k...@gmail.com ---
(In reply to mlh.kiwi from comment #2)
The camera model was the samsung WB 700. And it did have a date created tag
know as date taken which can be seen in the default windows properties

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

[kwin] [Bug 482587] When snapping a firefox window the top border shows wrong resize cursor

[daf]

https://bugs.kde.org/show_bug.cgi?id=482587

--- Comment #6 from daf  ---
 (In reply to Nate Graham from comment #5)
> Thanks. Can you reproduce the issue if you turn on the system-provided
> titlebars, rather than using built-in CSD headerbars?

No, only seems to happen with CSD enabled.

While testing it i did notice some odd behaviour, the mouse clicks started to
get registered several pixels higher then the cursor so clicks on tabs would
get registered on the desktop.

Could sometimes reproduce by making a new incognito window and then snapping
it. When it triggers the window flashes in a smaller size before expanding to
the snapped area, i've made a video of it bellow.

https://www.youtube.com/watch?v=j3qv4bqQgSo

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

--- Comment #2 from mlh.k...@gmail.com ---
"Did you import files using camera import tool from digiKam ? " No, was I
meant to?

On Sat, 9 Mar 2024 at 16:35,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=482944
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
>
> 
>  CC||caulier.gil...@gmail.com
>Severity|grave   |normal
>
> --- Comment #1 from caulier.gil...@gmail.com ---
> Hi,
>
> Which file format didi you use ?
>
> Which camera model did you use ?
>
> Did you import files using camera import tool from digiKam ? If yes, take a
> look to these settings :
>
>
> https://docs.digikam.org/en/setup_application/camera_settings.html#customize-the-behavior
>
> Also check well how metadata are taken from XMP side car (if you use it)
> with
> these settings:
>
>
> https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 482944] The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Severity|grave   |normal

--- Comment #1 from caulier.gil...@gmail.com ---
Hi,

Which file format didi you use ?

Which camera model did you use ?

Did you import files using camera import tool from digiKam ? If yes, take a
look to these settings :

https://docs.digikam.org/en/setup_application/camera_settings.html#customize-the-behavior

Also check well how metadata are taken from XMP side car (if you use it) with
these settings:

https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings

Gilles Caulier

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

[filelight] [Bug 482945] Filelight not using Breeze icon for the folder

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482945

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kde] [Bug 482943] System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482943

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kde] [Bug 482942] Possible Text Scaling Issue on X11/NVIDIA After Update to KDE6.

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=482942

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kwin] [Bug 482780] Incorrect color gamut with HDR enabled

[Zamundaaa]

https://bugs.kde.org/show_bug.cgi?id=482780

Zamundaaa  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||xaver.h...@gmail.com
 Status|REPORTED|NEEDSINFO

--- Comment #5 from Zamundaaa  ---
(In reply to mith3113 from comment #0)
> SUMMARY
> With HDR enabled in display settings, colors appear very washed out, as if
> my monitor is handling all colors like they're bt.709 instead of bt.2020.
> Increasing the SDR Color Intensity slider to 100% makes SDR colors look
> correct, and viewing HDR content with MPV I can set --target-prim=bt.709 as
> a workaround. The only similar issue report I've seen is this resolved one:
> https://bugs.kde.org/show_bug.cgi?id=479168 However I'm having this issue on
> an Nvidia gpu over both DP and HDMI.
While it may not be that specific bug, if NVidia implements the Colorspace
property the same way Intel does, this could happen independently of the
connector type. I'll confirm with someone from NVidia next week.

(In reply to Dāvis from comment #1)
> Also for me that SDR Color Intensity slider doesn't work at all, it does
> nothing - no visual change between 0% and 100%.
That's bug 482809

(In reply to Dāvis from comment #3)
> Ohh it looks like SDR Brightness calculation is wrong. Atleast for me if I
> set it to max 542 nits then I get correct saturation but screen is WAY too
> bright (it daylight can be fine but at night I don't want to be blinded :D)
> With HDR disabled I can set monitor's builtin brightness to 0% and colors
> are still saturated while screen being dim/non-bright.
> 
> So I think KWin does brightness wrong, it probably needs to increase
> saturation when decreasing brightness to keep same ratio so that colors
> don't look washed out or something like that.
You're not entirely wrong, the perceived intensity of a color is tied to its
brightness, and that's much more noticeable when the color is less saturated.
I'm not sure yet if we should do anything about that in KWin though.

(In reply to Dāvis from comment #4)
> No, it's not related to brightness, colors are just wrong, it's very
> noticeable when opening `htop` in Konsole and switching between HDR on and
> HDR off. The difference is so insane that HDR off looks WAY better and more
> "HDR" than with HDR on... Even with 542 nits those colors look washed out
> and not as "bright/colorful".
To some degree, that is expected. Without color management, wide color gamut
displays show very oversaturated colors, and if you get used to that, the
correct colors seem desaturated.
If that's actually what's happening for you though is hard do judge without
objective measurements. If you have access to a colorimeter, could you measure
what color gamut KWin actually outputs for sRGB apps? If you don't, a visual
comparison with a display close to sRGB (most laptops have that) would also be
useful.

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

[filelight] [Bug 482945] New: Filelight not using Breeze icon for the folder

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482945

Bug ID: 482945
   Summary: Filelight not using Breeze icon for the folder
Classification: Applications
   Product: filelight
   Version: 24.02.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: liangrui...@gmail.com
CC: martin.sandsm...@kde.org
  Target Milestone: ---

Created attachment 166761
  --> https://bugs.kde.org/attachment.cgi?id=166761=edit
screenshot of the situation

SUMMARY
***
Filelight is not using Breeze icon for the folder displayed on the left side.
***


STEPS TO REPRODUCE
1. Open the filelight
2. Select to scan whatever folder

OBSERVED RESULT
Not using the Breeze icon for the folder

EXPECTED RESULT
Using the Breeze icon for the folder 

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2


ADDITIONAL INFORMATION

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

[kde] [Bug 482943] System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1

[Mark S]

https://bugs.kde.org/show_bug.cgi?id=482943

--- Comment #1 from Mark S  ---
Alsa, pipewire and wireplumber info

API: ALSA v: k6.8.0-0.rc6.49.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin

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

[kdenlive] [Bug 482555] Pressing "Z" (not ctrl + z) UNDO/REMOVE work done on timeline (and it's not even a shortcut!).

[Moltke]

https://bugs.kde.org/show_bug.cgi?id=482555

Moltke  changed:

   What|Removed |Added

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

--- Comment #1 from Moltke  ---
Ok. As it turns out, pressing "Z" is bound to "remove zone from timeline". I
didn't see before while trying to disable, it's not listed here
https://docs.kdenlive.org/en/user_interface/shortcuts.html. I just disabled it.
This is "fixed"

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

[digikam] [Bug 482944] New: The date is wrong! Simply put the date inside digikam is not the "date taken"!

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482944

Bug ID: 482944
   Summary: The date is wrong! Simply put the date inside digikam
is not the "date taken"!
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Metadata-Date
  Assignee: digikam-bugs-n...@kde.org
  Reporter: mlh.k...@gmail.com
  Target Milestone: ---

Simply put the date inside digikam is not the "date taken"!

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

[kde] [Bug 482943] New: System sounds play even when muted in PulseAudio Volume Control on KDE6.0.1

[Mark S]

https://bugs.kde.org/show_bug.cgi?id=482943

Bug ID: 482943
   Summary: System sounds play even when muted in PulseAudio
Volume Control on KDE6.0.1
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: mspuban...@fastmail.us
  Target Milestone: ---

SUMMARY
***
I system-upgraded to Fedora 40 develop which upgraded my laptop to KDE 6.0.1

I have a problem where I can’t turn off the “bong” system sounds that occurs
when the desktop volume is changed by either rolling the mouse wheel when
hovering over the volume or sliding the volume.
I’ve set the System Sounds in pavucontrol (pulseaudio volume control) to 0%
volume and muted it but the sounds still occurs.  I also unchecked the “Enable
notification sounds” checkbox in “global themes”-> "System Sounds" but I think
that’s unrelated to System Sounds.

qpwgraph shows that when the sound is produced it's coming from libcanberra
***

STEPS TO REPRODUCE
1. Install Fedora 40 Develop OS, upgrade via 'dnf upgrade' afterwards to KDE
6.0.1
2. Turn off System Sounds in Pulseaudio Volume Control Playback tab by muting
"System Sounds"
3. Change desktop Volume via the taskbar volume (roll mouse wheel over the
widget or slide slider)


OBSERVED RESULT
Changing the desktop volume via the volume widget results in a system sound
even if system sounds was muted

EXPECTED RESULT
System Sounds should not occur if System Sounds is muted

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

ADDITIONAL INFORMATION
Kernel 6.8.0-0.rc6.49.fc40.x86_64
MSI Bravo 15 A4DDR laptop
Wayland

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

[kwin] [Bug 482903] Separate screen focus not working

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=482903

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

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

[kde] [Bug 482942] Possible Text Scaling Issue on X11/NVIDIA After Update to KDE6.

[HeathenHacks]

https://bugs.kde.org/show_bug.cgi?id=482942

--- Comment #4 from HeathenHacks  ---
Created attachment 166760
  --> https://bugs.kde.org/attachment.cgi?id=166760=edit
Text Too Small: 3

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

[kde] [Bug 482942] Possible Text Scaling Issue on X11/NVIDIA After Update to KDE6.

[HeathenHacks]

https://bugs.kde.org/show_bug.cgi?id=482942

--- Comment #3 from HeathenHacks  ---
Created attachment 166759
  --> https://bugs.kde.org/attachment.cgi?id=166759=edit
Text Too Small: 2

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

[kde] [Bug 482942] Possible Text Scaling Issue on X11/NVIDIA After Update to KDE6.

[HeathenHacks]

https://bugs.kde.org/show_bug.cgi?id=482942

--- Comment #2 from HeathenHacks  ---
Created attachment 166758
  --> https://bugs.kde.org/attachment.cgi?id=166758=edit
Text Too Small: 1

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