[kwin] [Bug 454668] Alt+Shift+Tab doesn't reverse task switcher

[Marco]

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

Marco  changed:

   What|Removed |Added

 CC||m...@triarc-labs.com

--- Comment #11 from Marco  ---
I'm having the same issue. It works on X11, but not on wayland. 

Kubuntu 22.10
Kde: 5.27.3 (ppa backports)
Frameworks: 5.104.0
Qt: 5.15.6

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[bugzilla_noreply]

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

--- Comment #18 from caulier.gil...@gmail.com ---
> -new issue noticed - linux appimage doesn't include g'mic. 

==> already fixed with last bundle pushed at usual place...

Gilles

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

[digikam] [Bug 463785] Slideshow starts with black screen and digikam crashes

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||caulier.gil...@gmail.com
   Version Fixed In||8.0.0
 Resolution|--- |FIXED

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

[Smb4k] [Bug 467843] New: Command line use

[bugzilla_noreply]

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

Bug ID: 467843
   Summary: Command line use
Classification: Applications
   Product: Smb4k
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: alexander.reinho...@kdemail.net
  Reporter: y...@masson-informatique.fr
  Target Milestone: ---

SUMMARY
It would be great if smb4k could be used from command line, at least for
mounting shares from bookmarks.


STEPS TO REPRODUCE
Let's say we have an enterprise computer that is not joined to a Active
Directory domain. As an administrator, I would like to configure the user's
session to automatically mount SMB shares on login. Simply configuring
bookmarks in Dolphin is unfortunately not an option yet because of current
weakness of KIO (regarding applications not using KIO). smb4k would be a good
candidate, because it avoids running things as root and passwords are safely
stored in KDE wallet.

OBSERVED RESULT
I am really new to smb4k, but unfortunately it seems it can not be used from
command line (did not find it in the online documentation nor by running smb4k
from command line).

EXPECTED RESULT
Being able to use something like:
- `smb4k mount --all` (to mount all bookmarks)
- `smb4k mount someshare` (to mount a specific bookmark)


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian testing
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.2
Qt Version: 5.15.8

ADDITIONAL INFORMATION
smb4k installed from Debian repository: 3.1.7-1


Regards,
Yvan

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

[Spectacle] [Bug 467842] Screencast output looks very poor, likely from bad/non-configurable default settings

[bugzilla_noreply]

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

--- Comment #1 from mira...@mirandastreeter.com ---
Created attachment 157621
  --> https://bugs.kde.org/attachment.cgi?id=157621=edit
example screencast

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

[Spectacle] [Bug 467842] New: Screencast output looks very poor, likely from bad/non-configurable default settings

[bugzilla_noreply]

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

Bug ID: 467842
   Summary: Screencast output looks very poor, likely from
bad/non-configurable default settings
Classification: Applications
   Product: Spectacle
   Version: 23.03.80
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: mira...@mirandastreeter.com
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
When attempting to use the spectacle screencast feature, the output looks
awful. I believe this is due to poor capture defaults.


STEPS TO REPRODUCE
1. Open wayland session
2. Open spectacle
3. Record screen (window, workspace, etc)

OBSERVED RESULT
You can see the attached video as an example. The same issue still occurs if I
pick a smaller region. From what I can see the bitrate is arguably higher than
necessary, and defaults to a variable framerate with what seems to be some kind
of ABR-like rate control. Something also seems wrong with the color range,
maybe?

EXPECTED RESULT
A default of, or at least an option for, a constant framerate with some form of
CRF that can be tuned.


SOFTWARE/OS VERSIONS
Arch Linux w/ KDE Plasma
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Kernel: 6.2.8-arch1-1
AMD Radeon RX 6600 XT
Mesa: 23.0.0

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

[kdenlive] [Bug 467573] [EXPERIMENTAL] Crash on 1660S when trying to use GPU for Whisper subtitles

[erjiang]

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

erjiang  changed:

   What|Removed |Added

 CC||erji...@alumni.iu.edu

--- Comment #1 from erjiang  ---
Searching the Web, there's a similar bug reported here against Whisper:
https://github.com/openai/whisper/discussions/88

Seems like what you said about not using fp16 (half-precision) can work around
the issue: maybe you can try modifying the whisper code to not use fp16 and see
if that fixes it?

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

[frameworks-qqc2-desktop-style] [Bug 467841] PlasmaDesktopTheme::syncWindow() uses a lot of memory

[bugzilla_noreply]

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

liu...@gmail.com changed:

   What|Removed |Added

 CC||liu...@gmail.com

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

[frameworks-qqc2-desktop-style] [Bug 467841] New: PlasmaDesktopTheme::syncWindow() uses a lot of memory

[bugzilla_noreply]

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

Bug ID: 467841
   Summary: PlasmaDesktopTheme::syncWindow() uses a lot of memory
Classification: Frameworks and Libraries
   Product: frameworks-qqc2-desktop-style
   Version: 5.104.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: liu...@gmail.com
CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk,
noaha...@gmail.com, notm...@gmail.com
  Target Milestone: ---

SUMMARY
I've observed that plasmashell sometimes keeps allocating more and more memory
- over 20GB in a few minutes, but normally it should use less than 500MB.

Most of the memory is allocated by this line in
`PlasmaDesktopTheme::syncWindow()`.

connect(qw, ::sceneGraphInitialized, this,
::syncWindow).

I tried adding `Qt::UniqueConnection` to this connection, and so far the
problem has not reappeared, and no other problems have been observed.


STEPS TO REPRODUCE
1. start plasmashell
2. switch to another tty
3. wait for some time (about 30 minutes)


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

ADDITIONAL INFORMATION

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

[kscreenlocker] [Bug 458130] Fingerprint authentication sometimes fails to activate immediately; sometimes activates after a few seconds, and sometimes only activates once you try to enter an incorrec

[bugzilla_noreply]

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

mira...@mirandastreeter.com changed:

   What|Removed |Added

 CC||mira...@mirandastreeter.com

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

[Spectacle] [Bug 467591] Spectacle records video with low framerate (25fps)

[bugzilla_noreply]

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

mira...@mirandastreeter.com changed:

   What|Removed |Added

 CC||mira...@mirandastreeter.com

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

[krita] [Bug 465844] Crashes every time I Scale all layers to new size

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kmymoney] [Bug 465707] Menu bar items not working

[Bug Janitor Service]

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

--- Comment #7 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 463785] Slideshow starts with black screen and digikam crashes

[Peter]

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

--- Comment #7 from Peter  ---
Tested in Windows 10 22H2; digiKam-8.0.0-20230326T140515-Win64.exe

I can't reproduce anymore. Works well.
Thank you Maik.

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

[kdialog] [Bug 467840] New: KDialog always has "-- KDialog" in titlebar, is meaningless to user

[Michael]

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

Bug ID: 467840
   Summary: KDialog always has "-- KDialog" in titlebar, is
meaningless to user
Classification: Applications
   Product: kdialog
   Version: 22.12.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: k...@callthecomputerdoctor.com
  Target Milestone: ---

SUMMARY

Right now, KDialog always displays "KDialog" in the title bar, or the suffix "-
KDialog" even if a title is set using the --title argument.

Recently, it was decided that "it's an implementation detail meaningless to the
user" to have "-- Portal" or "- PolicyKit1 KDE Agent" in the title bar of their
respective windows:

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

I feel, and have seen other feedback, that having "KDialog" is meaningless to
the user. "KDialog" is only meaningful to programmers and is visual noise
otherwise; for 98% of users, it's something that they have to read and ignore,
which makes KDE appear technical to users. Yes, we can see it's a dialog window
by its very nature, we don't need it spelled out to us.

Can the same fix be applied to KDialog windows? The method was:

Unset QApplication::applicationDisplayName()


STEPS TO REPRODUCE

1. kdialog --sorry "So sorry that you will see the words in the title bar"
--title "Hello"
2. kdialog --sorry "So sorry that you will see the words in the title bar"
3. kdialog --getopenfilename ~/ "audio/mpeg" --title "Hello"

"KDialog" is present, even in standard open file windows.

EXPECTED RESULT

Have an empty title bar by default. If a coder wants to have their title bar
contain "KDialog", they could manually add it back in with the --title
argument.

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-35-generic (64-bit)
Graphics Platform: X11

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

[valgrind] [Bug 467839] New: Gdbserver: Improve compatibility of library directory name

[JojoR]

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

Bug ID: 467839
   Summary: Gdbserver: Improve compatibility of library directory
name
Classification: Developer tools
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: rjie...@gmail.com
  Target Milestone: ---

Created attachment 157620
  --> https://bugs.kde.org/attachment.cgi?id=157620=edit
0001-Gdbserver-Improve-compatibility-of-library-directory.patch

Some linux os make softlink from customized directory like lib64xxx into
standard system lib64 directory,
we could improve compatibility for these cases, see Attachment :)

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

[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually

[Andrew Udvare]

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

--- Comment #29 from Andrew Udvare  ---
I tried every single -mno-avx512* option until I had all of them set. When all
were set the issue was gone. So really, *any* AVX512 feature in use will cause
this bug. I also tried with Clang and got the same results with all sorts of
flag combinations.

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

[Breeze] [Bug 443024] Icons for cartridge-based video game ROM images

[Nagy Tibor]

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

--- Comment #3 from Nagy Tibor  ---
Created attachment 157619
  --> https://bugs.kde.org/attachment.cgi?id=157619=edit
Icon ideas

Some icon ideas based on a stylized NES cartridge

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

[dolphin] [Bug 467838] Weird colouring bug causes selected location in sidebar to become darkened, therefore not following the colour scheme.

[Logan Turner]

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

Logan Turner  changed:

   What|Removed |Added

URL||https://imgur.com/a/ZOvn8sH

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

[dolphin] [Bug 467838] New: Weird colouring bug causes selected location in sidebar to become darkened, therefore not following the colour scheme.

[Logan Turner]

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

Bug ID: 467838
   Summary: Weird colouring bug causes selected location in
sidebar to become darkened, therefore not following
the colour scheme.
Classification: Applications
   Product: dolphin
   Version: 22.12.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: loganturner...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 157618
  --> https://bugs.kde.org/attachment.cgi?id=157618=edit
A video showing the issue.

STEPS TO REPRODUCE
1. Open dolphin
2. Select a location from the sidebar
3. Click on the selected location again. 

OBSERVED RESULT
The selected location does not follow the colour scheme. For a split second, it
shows your accent colour before dimming it. When clicking on the selected
location again however, it goes back to full brightness.

EXPECTED RESULT
The selected location should follow the rest of the system colour scheme, not
showing a darkened version.

SOFTWARE/OS VERSIONS
Arch Linux, KDE Plasma
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

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

[LabPlot2] [Bug 456328] Labplot 2.9 does not run

[Peter]

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

Peter  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
 CC||peter_heidr...@arcor.de
Version|2.9.0   |2.10.0
 Ever confirmed|0   |1

--- Comment #5 from Peter  ---
I have the same issues.  I have an up-to-date Windows 10 64-Bit system, all
drivers are up-to-date.  The PC has an integrated Intel Graphics and an
additional NVIDIA Quadro system.  The last revision running on this PC was the
one released with https://labplot.kde.org/2021/10/27/multi-axes-made-easy/. 
Already revision 2.9 did not work.  Now I tested 2.10.  The same issue.  What I
see: the initial logo pops-up for a few seconds, then disappears.  That's all. 
I would appreciate if you could investigate this now rather permanent issue. 
There must have been some significant change from the test-version introducing
the multi-axes feature and the 2.9 release.

PS: What I already tried with the latest 2.10 revision: installation for only
me, installation for all user's, installation in a directory which is not MS
Windows dominated.  (I am aware of issues related to installation into the MS
default directories.)  In my case: I installed into C:\Progs\LabPlot. 
Installation via the MS Store.  Installation of the nightly build. 
Installation as Administrator.  All behave the same: a few seconds the logo,
then nothing.

Best regards, Peter.

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

[plasmashell] [Bug 467812] login to X11 session hangs (Arm64 on Raspberry Pi 4B)

[HankB]

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

HankB  changed:

   What|Removed |Added

 CC||hba...@gmail.com

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

[kdeconnect] [Bug 467822] SMS messages are sent but not acknowledged and replies are not received on CalyxOS

[Tony Schmidt]

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

--- Comment #1 from Tony Schmidt  ---
Sorry, I guess I can't grok how to edit a ticket description in Bugzilla, so
adding as a comment:

Desktop KDEConnect Version:  GSConnect 50 (Also tried with latest KDE-Connect
version)

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

[plasmashell] [Bug 466586] System tray disappeared after screen size change, reboot did not recover

[James Harkins]

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

--- Comment #4 from James Harkins  ---
Brief update -- while understanding that any work on this issue has already
gone into 5.27, I also need to report that the advice to "update to 5.27 as
soon as your distro offers it" has proven to be untenable.

I did try an upgrade to Ubuntu Studio 22.10 (with Plasma 5.27), as the bad
behaviors were worsening. 22.10 completely broke the system. Screen updates,
and mouse pointer updates, would occur only every 2-3 seconds. Launching Chrome
produced a black screen and no way out, at which point I forced a shutdown and
rebooted from the Ubuntu Studio 22.04 installer medium, and subsequently spent
a "quality" afternoon reinstalling software.

Now, this might be a result of bad interaction between the Ubuntu 22.10 kernel
and the specific hardware -- maybe not directly Plasma's fault. But I did need
to point out that "just upgrade" is not always feasible.

Corruption of settings files reminds me of the early days of GTK Unity, btw.

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[Geoff King]

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

--- Comment #17 from Geoff King  ---
Created attachment 157617
  --> https://bugs.kde.org/attachment.cgi?id=157617=edit
_test5 image

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[Geoff King]

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

--- Comment #16 from Geoff King  ---
Created attachment 157616
  --> https://bugs.kde.org/attachment.cgi?id=157616=edit
_test3 image

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[Geoff King]

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

--- Comment #15 from Geoff King  ---
Created attachment 157615
  --> https://bugs.kde.org/attachment.cgi?id=157615=edit
_test2 image

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[Geoff King]

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

--- Comment #14 from Geoff King  ---
Created attachment 157614
  --> https://bugs.kde.org/attachment.cgi?id=157614=edit
_test0 image

I am sharing the files from my tests and some new observations below. 
This is on digiKam-8.0.0-20230326T082403-MacOS-x86-64-debug.pkg with MacBook
Pro Intel.
-new issue noticed - metadata not being carried over to exported files,
including comments and gps on Mac, I also tried on Ubuntu and the metadata does
carry over.  
-new issue noticed - linux appimage doesn't include g'mic.  
-sorry forgot to capture the debug log

_test0.jpg - original source use for all tests, opened in Image editor, and
exported to the formats below.
_test1.webp - no edits to original, just export as webp lossless, seems okay
except no metadata or coordinates
_test2.webp - no edits to original, just export as webp quality 65, no edits to
original file, seems okay except no metadata or coordinates
_test3.wbmp - no edits to original, just export as wbmp -  corrupt, but 1.3 MB
_test4.jp2 - edited in gmic with black and white filter before exporting,
jpeg2000, no metadata carried over, but otherwise looks okay, 
_test5.webp - edited in gmic with black and white filter before exporting,
small file created, image is missing, and shows transparent checkerboard
pattern thumbnail
_test6.jpg, edited in gmic with black and white filter before exporting,
missing gps metadata, other metadata is present

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

[krita] [Bug 467837] New: Value input (HSV) in color dialog should be able to go higher than 100%

[erjiang]

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

Bug ID: 467837
   Summary: Value input (HSV) in color dialog should be able to go
higher than 100%
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: erji...@alumni.iu.edu
  Target Milestone: ---

Created attachment 157613
  --> https://bugs.kde.org/attachment.cgi?id=157613=edit
Screen capture of buggy color dialog

SUMMARY

Color picker dialog does not allow Value > 100%.


STEPS TO REPRODUCE
1. Create new document using ACEScg color profile (linear), 16-bit float
2. In the Brushes and Stuff toolbar, double-click on the foreground color
swatch to select a color
3. Enter the values R: 3.5, G: 3.0, B: 1.5
4. Switch to HSV, see that value=100%. Click down arrow for value to lower to
99%, then click up to go back to 100%.

OBSERVED RESULT

Value selector is limited to 100% maximum. Switch back to RGB, see that
original RGB values are lost.

EXPECTED RESULT

Value selector should have shown 350% and not be limited to 100% (if image
format allows it).

SOFTWARE/OS VERSIONS

Using krita-5.2.0-prealpha-8550960a23-x86_64.appimage

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

[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors

[Mark Richardson]

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

--- Comment #4 from Mark Richardson  ---
(In reply to Mark Richardson from comment #3)

> None of this happens on the lavapipe vulkan driver, min/max extant always
> matches the window size exactly on Xorg and XWayland, and always returns min
> of (1,1) and max of (16384,16384) on wayland

actually, I had the scale set wrong when I tested lvp, the problem happens with
xWayland windows on lvp with 150% and 250% scaling just like with RADV.

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

[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors

[Mark Richardson]

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

--- Comment #3 from Mark Richardson  ---
After even more testing this appears to only happen with XWayland windows and a
scale set to 150%, or 250%, no other fractional scale factors trigger the
disconnect between the window size, and the vulkan surface extent.

Just to be clear what's happening, with XWayland windows on kwin_wayland and
scale values of 150% or 250%, vkGetPhysicalDeviceSurfaceCapabilitiesKHR returns
a min and max extent of (1280,721) on a window of size (1280,720). This breaks
most Vulkan apps, including almost every Steam/Proton game.

The solution can not be to create the swapchain based on either the min/max
extent instead of the window size, because with SDL2's native Wayland backend,
the min/max reported extants are always (1,1),(16384,16384).

This still happens on the latest KDE(opensuse tumbleweed), with the stock
amdgpu kernel driver with RADV, and started on Plasma 5.26, before the new
fractional scaling protocol.

None of this happens on the lavapipe vulkan driver, min/max extant always
matches the window size exactly on Xorg and XWayland, and always returns min of
(1,1) and max of (16384,16384) on wayland

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

[kwin] [Bug 467703] I got locked out from my account after closing and opening my laptop lid.

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

Product|plasma-wayland-protocols|kwin
  Component|general |general
   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
Version|1.10.0  |5.27.3

--- Comment #4 from Aleix Pol  ---
Please enter which version you are referring to.

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

[kwin] [Bug 466346] kwin_wayland crashes in KWaylandServer::OutputInterface::handle() when disabling and re-enabling a screen and letting it get turned off via power management

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[kwin] [Bug 467836] Kwin crash with pen input on maximize gesture (wayland)

[B. Elyesa]

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

--- Comment #3 from B. Elyesa  ---
Created attachment 157612
  --> https://bugs.kde.org/attachment.cgi?id=157612=edit
Quick demonstration of expected behaviour (done with mouse instead, since pen
crashes, you can see by the regular cursor shape)

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

[kwin] [Bug 467836] Kwin crash with pen input on maximize gesture (wayland)

[B. Elyesa]

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

--- Comment #2 from B. Elyesa  ---
Created attachment 157611
  --> https://bugs.kde.org/attachment.cgi?id=157611=edit
quick video demonstration

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

[kwin] [Bug 467836] Kwin crash with pen input on maximize gesture (wayland)

[B. Elyesa]

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

--- Comment #1 from B. Elyesa  ---
Created attachment 157610
  --> https://bugs.kde.org/attachment.cgi?id=157610=edit
backtrace 2

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

[kwin] [Bug 467836] New: Kwin crash with pen input on maximize gesture (wayland)

[B. Elyesa]

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

Bug ID: 467836
   Summary: Kwin crash with pen input on maximize gesture
(wayland)
Classification: Plasma
   Product: kwin
   Version: 5.27.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bery...@proton.me
  Target Milestone: ---

Created attachment 157609
  --> https://bugs.kde.org/attachment.cgi?id=157609=edit
backtrace

SUMMARY
Moving a window to top edge with pen, to maximize, crashes kwin occasionally

STEPS TO REPRODUCE
1. click a titlebar with pen
2. move it to top edge
3. shake up and down, touching and not touching, see the maximize animation
4. within 2 to 22 moves, kwin crashes (random number)
- a little video attachment just in case

OBSERVED RESULT
kwin maximizes the window every time

EXPECTED RESULT
kwin sometimes crash while maximizing

SOFTWARE/OS VERSIONS
Linux: Fedora 37 kernel 6.2
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Just before it crashes, I see that it sticks to the pen while I'm hovering (not
holding) without releasing the click and it goes black
The additional video crashed too early without even the maximizing effect, so I
have 2 traces with one being a quick crash and one taking a bit of up and down
effort. I doubt they're much different but just trying to help :P

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

[xdg-desktop-portal-kde] [Bug 467831] Portals do not open on Nvidia Wayland (Fedora 38)

[Aleix Pol]

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

--- Comment #1 from Aleix Pol  ---
What makes you think it's because of Nvidia?

Can you check your logs (using `journalctl -xe`) to see if there's any
outstanding error messages in there?

Can you see that it works with flatpak apps?

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

[plasmashell] [Bug 467835] Random loss of desktop (black un-interactive background) after login

[bugzilla_noreply]

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

mira...@mirandastreeter.com changed:

   What|Removed |Added

 CC||mira...@mirandastreeter.com

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

[plasmashell] [Bug 467835] Random loss of desktop (black un-interactive background) after login

[bugzilla_noreply]

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

--- Comment #1 from mira...@mirandastreeter.com ---
Created attachment 157608
  --> https://bugs.kde.org/attachment.cgi?id=157608=edit
journal log during login

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

[plasmashell] [Bug 467835] New: Random loss of desktop (black un-interactive background) after login

[bugzilla_noreply]

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

Bug ID: 467835
   Summary: Random loss of desktop (black un-interactive
background) after login
Classification: Plasma
   Product: plasmashell
   Version: 5.27.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: plasma-b...@kde.org
  Reporter: mira...@mirandastreeter.com
CC: aleix...@kde.org, notm...@gmail.com
  Target Milestone: 1.0

Created attachment 157607
  --> https://bugs.kde.org/attachment.cgi?id=157607=edit
video of blank background

SUMMARY
Randomly, on login, I'll get a black background on one of my monitors that
cannot be clicked or interacted with. The attached video should show what I'm
talking about.


STEPS TO REPRODUCE
1. Log in
2. ???

OBSERVED RESULT
- Instead of each desktop appearing on each display, both are shoved over to
the same (in this case rightmost) display. My monitors are slightly ajar (one
raised by 100px), and in the attached video you can see one (normally leftmost)
background overlayed on the other (note the 100px difference).
- I cannot left click or right click the leftmost background.
- The panel/task manager on the otherwise blank screen can be interacted with.
- Adjusting the display positions does not resolve the issue (attempting this
cut off the recording, but trust me it does not work).

EXPECTED RESULT
Both desktops are contained within the proper displays and are interactable

SOFTWARE/OS VERSIONS
Arch Linux w/ KDE Plasma
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Kernel: 6.2.8-arch1-1
AMD Radeon RX 6600 XT
Mesa: 23.0.0 (this has previously occurred on Mesa v22.x w/ plasma 5.27 as
well)
No /etc/X11/xorg.conf file

Attached you will find:
- A video showcasing the problem
- journalctl output from when logging into the session (hostname and username
scrubbed)
  - I'd continued with it like that for a few hours, in case you're wondering
about the time difference

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

[kwin] [Bug 467834] Screen doesn't turn on after long time sleeping (DPMS error)

[Marcelo Bossoni]

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

--- Comment #2 from Marcelo Bossoni  ---
Forgot to add the system info
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7A37
System Version: 1.0

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

[kwin] [Bug 467834] Screen doesn't turn on after long time sleeping (DPMS error)

[Marcelo Bossoni]

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

--- Comment #1 from Marcelo Bossoni  ---
Created attachment 157606
  --> https://bugs.kde.org/attachment.cgi?id=157606=edit
systemd journal

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

[kwin] [Bug 467834] New: Screen doesn't turn on after long time sleeping (DPMS error)

[Marcelo Bossoni]

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

Bug ID: 467834
   Summary: Screen doesn't turn on after long time sleeping (DPMS
error)
Classification: Plasma
   Product: kwin
   Version: 5.27.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mmboss...@gmail.com
  Target Milestone: ---

SUMMARY
I left computer idle for a long time (around 2 hours) and screen cannot turn on
again.
SSH from other machine worked fine.
Switch to TTY didn't work
Disconnecting/reconnecting the DP cable didn't work

STEPS TO REPRODUCE
1. Use the computer
2. Leave the computer idle for a long time so that screen goes to sleep (and
more after that)
3. Try to use the PC again

OBSERVED RESULT
Screen didn't come back

EXPECTED RESULT
Screen is turned on normally

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

ADDITIONAL INFORMATION
I stopped playing around 17:42
mar 26 17:42:15 URSO kwin_wayland[725]: kwin_core: could not find the toplevel
to activate KWaylandServer::SurfaceInterface(0x55fcffd37d20)
mar 26 17:42:15 URSO kwin_wayland[725]: kwin_core: could not find the toplevel
to activate KWaylandServer::SurfaceInterface(0x55fcffd37d20)
mar 26 17:40:18 URSO kwin_wayland[725]: kwin_core: XCB error: 3 (BadWindow),
sequence: 22843, resource id: 90177651, major code: 129 (SHAPE), minor code: 6
(Input)

Then near 20:00 kwin had some strange messages (that repeated for about 4
minutes)
mar 26 20:00:19 URSO kwin_wayland[725]: kwin_wayland_drm: Failed to create
gamma blob! Argumento inválido
mar 26 20:00:12 URSO kwin_wayland[725]: kwin_wayland_drm: Failed to create
gamma blob! Argumento inválido
mar 26 20:00:06 URSO kwin_wayland[725]: kwin_wayland_drm: Failed to create
gamma blob! Argumento inválido

When I tried to use the PC again (20:13)
mar 26 20:13:14 URSO kwin_wayland[725]: kwin_wayland_drm: Setting dpms mode
failed!
mar 26 20:13:14 URSO kwin_wayland[725]: kwin_wayland_drm: Setting dpms mode
failed!
mar 26 20:13:14 URSO kwin_wayland[725]: kwin_wayland_drm: Setting dpms mode
failed!

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

[Akonadi] [Bug 463225] Akonadi server crashed when switching user

[rarsa]

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

--- Comment #8 from rarsa  ---
After the crash, the screen went back to using the full monitor and the
touchpad started working. When I was writing the crash report, everything was
working OK, however, if I log out and log back in, the same happens again.

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

[Akonadi] [Bug 463225] Akonadi server crashed when switching user

[rarsa]

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

--- Comment #7 from rarsa  ---
Created attachment 157605
  --> https://bugs.kde.org/attachment.cgi?id=157605=edit
New crash information added by DrKonqi

akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.8

After booting, my desktop was showing in just about 1/4 of the screen,  the
Display parameters said that I only had a 1024x768 resolution available. inxi
showed the same. when I tried to log out, I got the crash report.

I rebooted and the same happened. It only happened in Wayland. If I log in to
KDE with X I don't have a problem.

Also, when the screen showed scaled to 1/4 of the laptop's monitor, the
touchpad didn't detect taps or clicks and when I went to the settings it said
that it hadn't detected any touch pad

-- Backtrace (Reduced):
#4  0x55d613a8b29b in
Akonadi::Server::AkonadiServer::connectionDisconnected() ()
#5  0x7fd6376c8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#6  0x7fd63769d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#7  0x7fd6376a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#8  0x7fd6376eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5

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

[Akonadi] [Bug 463225] Akonadi server crashed when switching user

[rarsa]

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

rarsa  changed:

   What|Removed |Added

 CC||ra...@yahoo.com

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

[ksysguard] [Bug 467821] ksysguardd crashed repeatedly after starting ksysguard with a buffer overflow detected

[Matt Fagnani]

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

--- Comment #3 from Matt Fagnani  ---
This problem might be fixed by the commit lmsensors: Fix buffer size passed to
snprintf at
https://invent.kde.org/plasma/ksysguard/-/commit/cb52be2f743a6717355445889dd3e2e265ad75fa

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

[dolphin] [Bug 467682] Initiate filter bar when typing

[Felix Ernst]

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

Felix Ernst  changed:

   What|Removed |Added

 CC||felixer...@kde.org

--- Comment #1 from Felix Ernst  ---
I don't think those two should be combined. Typing a key to find a specific
file seems intuitive to me. I don't think a user would want all the files that
don't match this to be hidden then.

It certainly is a bit weird that we have a "type ahead" feature, a "filter"
feature, and a "search" feature, but if I were to combine two of them it would
be "filter" and "search" and not "type ahead" and "filter". In a way filtering
is the same as searching but only for the current location.

I agree however that the "type ahead" feature could be improved in the sense
that it currently isn't very clear what was typed. I believe we should show
text in the bottom left of the view that explains "Jumping to "test"…". The
text should fade away when no new key was typed for a second or two.

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

[gwenview] [Bug 467833] New: gwenview crashed after trying to delete multiple images

[Andrew]

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

Bug ID: 467833
   Summary: gwenview crashed after trying to delete multiple
images
Classification: Applications
   Product: gwenview
   Version: 22.12.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: travn...@gmail.com
  Target Milestone: ---

Application: gwenview (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.7-200.fc37.x86_64+debug x86_64
Windowing System: X11
Distribution: "Fedora release 37 (Thirty Seven)"
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
I did ctrl+a to select several images. Then pressed del (maybe shift/ctrl+del,
not sure) and it crashed immediately.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault

[KCrash Handler]
#4  0x7f8c866ed6e8 in
Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib64/libgwenviewlib.so.5
#5  0x7f8c866f85b5 in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded()
() from /lib64/libgwenviewlib.so.5
#6  0x7f8c848d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f8c846f21b5 in QFutureWatcherBase::event(QEvent*) () from
/lib64/libQt5Core.so.5
#8  0x7f8c855aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#9  0x7f8c8489d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#10 0x7f8c848a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#11 0x7f8c848eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#12 0x7f8c82718c7f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#13 0x7f8c8276f118 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#14 0x7f8c82715f00 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#15 0x7f8c848ee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#16 0x7f8c8489bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#17 0x7f8c848a4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#18 0x55ebed1b4afb in main ()
[Inferior 1 (process 11095) detached]

The reporter indicates this bug may be a duplicate of or related to bug 458876.

Reported using DrKonqi

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

[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave

[Geoff King]

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

--- Comment #49 from Geoff King  ---
Hi Gilles,
I read through the G'MIC-Qt chapter in the digiKam online documentation and
it looks good to me.   I didn’t see any obvious errors. I could suggest
a few minor grammatical or style changes if we want to be picky, but that
may be just regional language use preference.  If you would like me to
suggest edits what is the best way to do that?

Thanks, Geoff

On Sun, Mar 26, 2023 at 4:28 AM  wrote:

> https://bugs.kde.org/show_bug.cgi?id=422996
>
> --- Comment #48 from caulier.gil...@gmail.com ---
> Hi Geoff,
>
> I write a G'MIC-Qt chapter in the digiKam online documentation. If you can
> take
> a look and give me a feedback, it will be very appreciate:
>
>
> https://docs.digikam.org/en/image_editor/enhancement_tools.html#g-mic-qt-tool
>
> Thanks in advance
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kmail2] [Bug 467832] New: Add ability to change position of subject column in classic list view

[bugzilla_noreply]

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

Bug ID: 467832
   Summary: Add ability to change position of subject column in
classic list view
Classification: Applications
   Product: kmail2
   Version: 5.22.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: heino...@tf.uni-freiburg.de
  Target Milestone: ---

Created attachment 157603
  --> https://bugs.kde.org/attachment.cgi?id=157603=edit
Example from Gnome Revolution

I'd like to be able to change the position of the subject column in the
classical message list view just like I can already do it for all the other
types of colums. Right now it seems to be fixed to the very left, probably
because the subject column also contains the icons for read/unread and
attachment. Imo the read/unread status and attachment indicator should be a
separate column anyway, just like Gnome Revolution is doing it (see attached
screenshot). I'm aware of the Smart message list layout, but that's not an
option for me personally, because I prefer having one line per message to
reduce mental overhead when scanning through messages.

Looking forward to hear your thoughts about this.

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

[xdg-desktop-portal-kde] [Bug 467831] New: Portals do not open on Nvidia Wayland (Fedora 38)

[bugzilla_noreply]

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

Bug ID: 467831
   Summary: Portals do not open on Nvidia Wayland (Fedora 38)
Classification: Plasma
   Product: xdg-desktop-portal-kde
   Version: 5.27.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: chriser...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
  Target Milestone: ---

SUMMARY

Dialogs like Firefox's "Save Link / Image as..."  or even downloading files do
not prompt any Window to open asking for the directory or which app to use to
open the file. Same behaviour with any flatpak with an "Open ..." dialog
option. I've checked that xdg portal and xdg portal kde are running, and they
are.


STEPS TO REPRODUCE
1.  Launch any flatpak application
2. Click on a dialog such as "Open file in... / Save image as..." if available

OBSERVED RESULT
Nothing happens; no portal is opened and the application does nothing.

EXPECTED RESULT
A Portal should appear as usual.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38
KDE Plasma Version:  5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

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

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

   Version Fixed In||0.10.1
 Status|CONFIRMED   |ASSIGNED
  Latest Commit||774be9be04d204bd70a74f2650c
   ||035c8b470c44a

--- Comment #2 from Thomas Fischer  ---
I think I fixed this bug. Please check branch 'bugs/kde467803' in my personal
Git repository and confirm that it got indeed fixed:
https://invent.kde.org/thomasfischer/kbibtex/-/tree/bugs/kde467803

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

[kmail2] [Bug 467830] New: After setting an already read message to unread it's not set to read when selecting it again

[bugzilla_noreply]

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

Bug ID: 467830
   Summary: After setting an already read message to unread it's
not set to read when selecting it again
Classification: Applications
   Product: kmail2
   Version: 5.22.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: heino...@tf.uni-freiburg.de
  Target Milestone: ---

SUMMARY
See title


STEPS TO REPRODUCE
0. Use Classic Theme (View -> Message List -> Theme -> Classic)
1. Start up KMail and click on unread message in list (which should set it to
read)
2. Right-click this message -> Mark message -> Mark message as unread
3. Click on other message in list and click back on the message which has just
been set to unread

OBSERVED RESULT
Message is viewed in preview window but remains marked as unread

EXPECTED RESULT
Message is set to read

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.102-1-MANJARO x86_64 GNU/Linux
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

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

[krita] [Bug 467829] New: The line tool doesn't work propperly with pressure sensitive brushes

[bugzilla_noreply]

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

Bug ID: 467829
   Summary: The line tool doesn't work propperly with pressure
sensitive brushes
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: javiervigo@gmail.com
  Target Milestone: ---

SUMMARY
Tested on Krita v.5.2.0-prealpha (git 8550960)

When using the line tool with a brush that has pressure sensitivity the line
doesn't start where it should. When drawing the line vertically downwards the
line is drawn over the entire path, but drawing upwards the line skips the
beginning of the path.

STEPS TO REPRODUCE
1. Create a new file
2. Select a brush with pressure sensitivity (I used Pencil 1 Sketch)
3. Select the line tool
4. Draw a vertical lines vertically upwards at different pressures

OBSERVED RESULT
The line skips the start of the line path

EXPECTED RESULT
The line covers the entire line path from start to end

SOFTWARE/OS VERSIONS
Windows: 10 Pro v.10.0.19044
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Here's a link to a couple images that hopefuly explains the bug
https://imgur.com/a/J1GPVxd

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

[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography

[Philip Murray]

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

--- Comment #5 from Philip Murray  ---
Created attachment 157602
  --> https://bugs.kde.org/attachment.cgi?id=157602=edit
The 3 sizes, separated.

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

[krita] [Bug 467828] New: File dialogs: awkward keyboard interaction

[Frann]

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

Bug ID: 467828
   Summary: File dialogs: awkward keyboard interaction
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: fra...@pm.me
  Target Milestone: ---

SUMMARY

Keyboard interaction with File dialogs is difficult. When using Tab to browse
interactive items, the focus order is deceptive, and some items do not
highlight, or the highlighted style is barely noticeable (with light or dark
themes).

STEPS TO REPRODUCE
1. Open a file and choose "File > Save As...". The "Save As" File dialog opens
with the File Name field focused.
2. Press Tab in order to get focus on the File Type drop-down.

OBSERVED RESULT
TL/DR: The File Type dropdown cannot be focused via Tab presses. Awkwardly it
can only be focused with Shift + Tab presses.

Also, some items get focus invisibly, (navigation arrows to the right of the
navigation drop-down, or the Locations column on the left). It's hard to keep
track of what gets focus.

EXPECTED RESULT
With the File Name highlighted, a single Tab press should give focus to the
File Type drop-down.

More generally, Tab and Shift + Tab press should allow for a logical
forward/backward item selection, with every focused element visibly highlited.

SOFTWARE/OS VERSIONS
Linux Mint 20.3 Cinnamon 

ADDITIONAL INFORMATION
5.1.5 Appimage version

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

[krita] [Bug 467826] [master] HSV/HSL Adjustment is very broken

[Deif Lou]

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

Deif Lou  changed:

   What|Removed |Added

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

--- Comment #2 from Deif Lou  ---
Yes it seems it was solved by that mr, which is now merged

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

[krita] [Bug 467517] Hue saturation filter dialog shows black sliders at start (git 14447ec)

[Invent Merge Service]

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

Invent Merge Service  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/2f3e75cca
   ||d34986aaa4b6caec4a339c26570
   ||47e3

--- Comment #1 from Invent Merge Service  ---
Git commit 2f3e75ccad34986aaa4b6caec4a339c2657047e3 by Merge Service, on behalf
of Freya Lupen.
Committed on 26/03/2023 at 20:56.
Pushed by merge-service into branch 'master'.

Fix HSV filter sliders not being initialized

Fixes a safe assert mistakenly being triggered,
causing the sliders to appear black initially.

Part-of: 

M  +1-1plugins/filters/colorsfilters/kis_hsv_adjustment_filter.cpp

https://invent.kde.org/graphics/krita/commit/2f3e75ccad34986aaa4b6caec4a339c2657047e3

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

[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography

[Philip Murray]

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

--- Comment #4 from Philip Murray  ---
The zoom pixels one is even better when smaller, it almost looks spherical,
like a visual trick.

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

[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography

[Philip Murray]

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

--- Comment #3 from Philip Murray  ---
Notes: there are 3 sizes of magnifying glass, there was a method to it:

1. Big ones (diameter=16px); For where there's something complex inside them.
These ones have somewhat stubby handle due to space constraints, but I think it
looks OK. E.g. zoom-pixels, zoom-2-to-1, zoom-original.

2. Medium (diameter=13px); Realistic handle length & enough space inside it to
put a clear plus/minus symbol. E.g. zoom-in, zoom-out.

3. Small ones (diameter=9px); where there's something going on around it. E.g.
zoom-previous, zoom-width, zoom-out-x.

The arrow heads are a bit difficult so, these are still WIP. 
The plain 'zoom' one is a bit unclear in the original, so I just made it an
empty eyeglass.

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

[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
Oh, these are great! So much clearer! I especially like your take on
`zoom-pixels`. That one looks really nice.

The magnifying glasses all having different sizes might not be ideal though. It
would be best if we could make them all have the same size somehow.

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

[KBibTeX] [Bug 467803] User preferences are no longer saved

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Thomas Fischer  ---
First I had problems reproducing the report, as I tested various settings which
indeed get stored and later restored correctly.
The reported issue concerns "free-text" configuration options, for example the
language to be used for Babel.

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

[kmail2] [Bug 467796] Two Kmail icons appearing in dock

[Georg Schwarz]

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

--- Comment #1 from Georg Schwarz  ---
Additional information: when I switch off "show unread email in taskbar" in
Configure Kmail -> Appearance->System Tray, the second icon, the one with the 0
in the red solid circle, no longer shows up in the dock. Only the normal KMail
icon remains. Makes me wonder why showing the number of unread emails in the
taskbar results in a second icon.

The 0 in the red circle is probably supposed to be the number of unread emails.
However in my test setup it is a four-digit number, definitely not 0.

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

[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography

[Philip Murray]

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

Philip Murray  changed:

   What|Removed |Added

 CC||philipihmur...@hotmail.com

--- Comment #1 from Philip Murray  ---
Created attachment 157601
  --> https://bugs.kde.org/attachment.cgi?id=157601=edit
Existing zoom icons + new ones I've created for comparison.

Some zoom icons, as per Nate's comments I think the zoom icons might be clearer
if the usual magnifying glass is used. At least for the basic zoom in/out ones,
the others maybe not so necessary or maybe are clearer for complex use cases.
But I made some drafts as per attached.

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

[krita] [Bug 467826] [master] HSV/HSL Adjustment is very broken

[Deif Lou]

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

Deif Lou  changed:

   What|Removed |Added

 CC||gin...@gmail.com

--- Comment #1 from Deif Lou  ---
Maybe this mr solve the issue? It seems to solve at least the wrong
initialization. https://invent.kde.org/graphics/krita/-/merge_requests/1776

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

[marble] [Bug 400409] Segmentation fault when trying to add some WMS maps.

[Torsten Rahn]

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

--- Comment #8 from Torsten Rahn  ---
I have added initial support to WMTS. With this support added Marble doesn't
crash anymore and allows for the selection of the WMTS layers provided. However
there are a few things that I still need to add to Marble in order to have this
particular WMTS server supported. If you're interested in the details have a
look at:

https://mail.kde.org/pipermail/marble-devel/2023-March/009671.html

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

[Discover] [Bug 467827] New: Discover crash upon startup, failing to find flathub

[B. Elyesa]

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

Bug ID: 467827
   Summary: Discover crash upon startup, failing to find flathub
Classification: Applications
   Product: Discover
   Version: 5.27.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Flatpak Backend
  Assignee: plasma-b...@kde.org
  Reporter: bery...@proton.me
CC: aleix...@kde.org, jgrul...@redhat.com,
trav...@redhat.com
  Target Milestone: ---

Created attachment 157600
  --> https://bugs.kde.org/attachment.cgi?id=157600=edit
backtrace

SUMMARY
Sometimes discover "can't find flathub" and doesn't launch.
`Could not find source: 0x7fffa001c240 "flathub"` (0x number probably doesn't
matter)

Very out of ordinary actually, randomly happens after an update is available
from flathub.
Even though I couldn't trigger intentionally(can't give virtual updates by
myself), I highly guess it's related to nvidia flatpak updates as it regularly
happens right after I get an nvidia update on system side.

OBSERVED RESULT
Discover crashes upon startup, before any gui is shown.

EXPECTED RESULT
Discover launched properly (obviously )
Maybe temporarily ignore the broken backend instead of crashing and warn the
user about "unexpected issue with the flatpak backend: couldn't find flathub"
without forcing the user to use command line.

SOFTWARE/OS VERSIONS
Linux: Fedora 37 kernel 6.2
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Can be worked around by using gnome-software or flatpak cli, then discover no
longer breaks. Can't trigger again until an update though, making it harder to
reproduce. I got the backtrace in 5.27.2 but it's not introduced in that
release nor fixed in .3, it's just that I couldn't get my way to report.

Attached backtrace, my first bug report, hope it's useful (⁠✿⁠^⁠‿⁠^⁠)

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

[digikam] [Bug 463785] Slideshow starts with black screen and digikam crashes

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #6 from Maik Qualmann  ---
A new test version of digiKam-8.0.0 is available. Please test whether the
problem can still be reproduced.

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

If you still want to go back to an older digiKam version, back up your database
beforehand.

Maik

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

[krita] [Bug 467826] New: [master] HSV/HSL Adjustment is very broken

[bugzilla_noreply]

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

Bug ID: 467826
   Summary: [master] HSV/HSL Adjustment is very broken
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Filters
  Assignee: krita-bugs-n...@kde.org
  Reporter: tomtomtomreportin...@gmail.com
  Target Milestone: ---

SUMMARY
In latest Krita nightly builds, the HSV/HSL Adjustment filter is very hard to
use and is often dysfunctional.

STEPS TO REPRODUCE
1. Paint an orange line.
2. Add a Filter Mask for HSV/HSL Adjustment filter.
3. Notice that all the sliders are initially black.
4. Enable Colorize.
5. Setting Hue to the far left of the slider will break the filter completely,
producing no effect.
6. If Hue is set to the right of the slider, setting Saturation to the far left
of the slider will break the Value slider.

Occurs in git 855096 (3/26/23), git daf98f (2/28/23), but NOT in 743b90
(2/2/2023).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.7 (appimage)

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

[plasmashell] [Bug 467825] Plasmashell crashes when using Mullvad GUI App system tray context menu

[Eric R]

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

--- Comment #1 from Eric R  ---
Created attachment 157599
  --> https://bugs.kde.org/attachment.cgi?id=157599=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 467825] New: Plasmashell crashes when using Mullvad GUI App system tray context menu

[Eric R]

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

Bug ID: 467825
   Summary: Plasmashell crashes when using Mullvad GUI App system
tray context menu
Classification: Plasma
   Product: plasmashell
   Version: 5.27.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: aer0...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 5.19.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.3 [CoredumpBackend]

-- Information about the crash:
I used the Mullvad VPN GUI tray icon right-click menu to enable VPN.
I don't know if this is a Plasma GUI issue or an issue with the Mullvad GUI app
(version 2023.1).
Plasmashell crashed "gracefully" and restarted a few seconds later.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#3  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140686968268352)
at ./nptl/pthread_kill.c:44
#4  __pthread_kill_internal (signo=6, threadid=140686968268352) at
./nptl/pthread_kill.c:78
#5  __GI___pthread_kill (threadid=140686968268352, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#6  0x7ff464842476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#7  0x7ff4648287f3 in __GI_abort () at ./stdlib/abort.c:79


Reported using DrKonqi

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

[kdiff3] [Bug 467652] Escape key doesn't quit the application when Output pane is focused

[michael]

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

michael  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/
   |kdiff3/commit/dc811b1091b6c |kdiff3/commit/28c44e9440d9c
   |c0fb021d099f0d90f0855e60ea2 |dd256881abf2839aa6883ba2b77

--- Comment #3 from michael  ---
Git commit 28c44e9440d9cdd256881abf2839aa6883ba2b77 by Michael Reeves.
Committed on 26/03/2023 at 19:17.
Pushed by mreeves into branch 'master'.

Use  QShortcut for escape key quit

This will prevent the escape key from being sent as a keyPress event and
possibly intercepted.́́
FIXED-IN:10.0.1

M  +4-0src/kdiff3.cpp
M  +2-0src/kdiff3.h
M  +1-6src/pdiff.cpp

https://invent.kde.org/sdk/kdiff3/commit/28c44e9440d9cdd256881abf2839aa6883ba2b77

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

[kdiff3] [Bug 467652] Escape key doesn't quit the application when Output pane is focused

[michael]

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

michael  changed:

   What|Removed |Added

   Version Fixed In||10.0.1
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/sdk/
   ||kdiff3/commit/dc811b1091b6c
   ||c0fb021d099f0d90f0855e60ea2
 Status|REPORTED|RESOLVED

--- Comment #2 from michael  ---
Git commit dc811b1091b6cc0fb021d099f0d90f0855e60ea2 by Michael Reeves.
Committed on 26/03/2023 at 19:18.
Pushed by mreeves into branch '1.10'.

Use  QShortcut for escape key quit

This will prevent the escape key from being sent as a keyPress event and
possibly intercepted.́́
FIXED-IN:10.0.1
(cherry picked from commit 28c44e9440d9cdd256881abf2839aa6883ba2b77)

M  +4-0src/kdiff3.cpp
M  +2-0src/kdiff3.h
M  +1-6src/pdiff.cpp

https://invent.kde.org/sdk/kdiff3/commit/dc811b1091b6cc0fb021d099f0d90f0855e60ea2

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

[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5

[bugzilla_noreply]

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

nekone...@protonmail.ch changed:

   What|Removed |Added

  Component|general |general
   Assignee|now...@gmail.com|fa...@kde.org
Version|5.27.3  |5.93.0
Product|Bluedevil   |frameworks-kded

--- Comment #7 from nekone...@protonmail.ch ---
You guys REALLY need to stop interfering with this page and file your issues
elsewhere.
Stop hijacking this report to change the topic to your own issues; that's not
how a bug tracker works.

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

[Breeze] [Bug 467824] New: CheckBox, RadioButton keyboard focus rect does not cover icon

[ratijas]

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

Bug ID: 467824
   Summary: CheckBox, RadioButton keyboard focus rect does not
cover icon
Classification: Plasma
   Product: Breeze
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: QStyle
  Assignee: plasma-b...@kde.org
  Reporter: m...@ratijas.tk
CC: noaha...@gmail.com, uhh...@gmail.com
  Target Milestone: ---

Created attachment 157598
  --> https://bugs.kde.org/attachment.cgi?id=157598=edit
Breeze icon-only controls and their keyboard focus indicator

SUMMARY

With Breeze style, keyboard focus indicator (solid underline) on CheckBox and
RadioButton controls (both QtWidgets and QQC2 via qqc2-desktop-style bridge)
only covers text label but not the icon. If a button is icon-only (no text),
then focus indicator is practically invisible because it has a width of zero.

STEPS TO REPRODUCE
1. Create a CheckBox and RadioButton with an icon but without text string.
2. Tab-navigate to it.

OBSERVED RESULT
Keyboard focus right is present, but underline indicator is invisible
(zero-sized).

EXPECTED RESULT
In Fusion style, focus rect covers icon and label with a subtle gradient. In MS
Windows 9x style, a dotted rectangle outline is drawn around both icon and
label. In Oxygen, there are no icon/text indicators at all, unfortunately.

So, an average expected behavior is to highlight an icon alongside the text
label.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: git Plasma/5.27
KDE Frameworks Version: git kf5
Qt Version: 5.15.8
Kernel Version: 6.2.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 970M/PCIe/SSE2
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: G752VT
System Version: 1.0

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

[kio-extras] [Bug 325574] Unable to modifying file on Android device using kio-mtp

[bugzilla_noreply]

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

y...@masson-informatique.fr changed:

   What|Removed |Added

 CC||y...@masson-informatique.fr

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

[kwin] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it

[Carlo]

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

--- Comment #5 from Carlo  ---
The issue appears to not occur with a different display server (from from
SDDM).
Might be worth waiting for SDDM 0.20 release and see if the port to Wayland
fixes the issue

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

[krita] [Bug 467820] When doing a levels adjustment on a noise layer the final product is not accurate to the preview at all

[Deif Lou]

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

Deif Lou  changed:

   What|Removed |Added

 CC||gin...@gmail.com

--- Comment #1 from Deif Lou  ---
Please try previewing at 100% zoom. It may be that the filter is applied to the
small size zoomed image and gives different results than when it is confirmed
and applied to the full size image, all that exagerated by the nature of the
noisy image. Not sure.

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

[Alligator] [Bug 465220] [Feature] Selection mode for posts, and then mark posts as read/unread

[Tobias Fella]

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

Tobias Fella  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[Alligator] [Bug 465220] [Feature] Selection mode for posts, and then mark posts as read/unread

[Tobias Fella]

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

Tobias Fella  changed:

   What|Removed |Added

Summary|Selection mode for posts,   |[Feature] Selection mode
   |and then mark posts as  |for posts, and then mark
   |read/unread |posts as read/unread

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

[trojita] [Bug 467270] SMTP login not recognizing 334\r\n (example: GMX)

[Espen Sandøy Hustad]

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

Espen Sandøy Hustad  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||es...@ehustad.com
Version|0.7 |git

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

[trojita] [Bug 428078] SMTP AUTH Login truncates Base64 representation of username

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #5 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/pim/trojita/-/merge_requests/34

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

[kde] [Bug 467823] New: There is no response on Korganizer when 'Edit' is checked

[Edward]

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

Bug ID: 467823
   Summary: There is no response on Korganizer when 'Edit' is
checked
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: edh...@gmail.com
  Target Milestone: ---

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


STEPS TO REPRODUCE
1. Right click on Entry
2. Left click on 'Edit'
3. 

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Edit window

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 20.3 Cinnamon
(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.

[trojita] [Bug 428078] SMTP AUTH Login truncates Base64 representation of username

[Espen Sandøy Hustad]

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

Espen Sandøy Hustad  changed:

   What|Removed |Added

 CC||es...@ehustad.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #4 from Espen Sandøy Hustad  ---
I can confirm that this also happens with gcc (Gentoo 12.2.1_p20230304 p13)
12.2.1 20230304

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

[ksysguard] [Bug 467821] ksysguardd crashed repeatedly after starting ksysguard with a buffer overflow detected

[Bug Janitor Service]

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

--- Comment #2 from Bug Janitor Service  ---

Thank you for the bug report!

However Plasma 5.22.0 is no longer eligible for support or maintenance from
KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a
supported version as soon as your distribution makes it available to you.
Plasma is a fast-moving project, and bugs in one version are often fixed in the
next one.

If you need support for Plasma 5.22.0, please contact your distribution, who
bears the responsibility of providing support for older releases that are no
longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel
free to re-open this bug report.

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

[ksysguard] [Bug 467821] ksysguardd crashed repeatedly after starting ksysguard with a buffer overflow detected

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Bug Janitor Service  ---

Thank you for the bug report!

However Plasma 5.22.0 is no longer eligible for support or maintenance from
KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a
supported version as soon as your distribution makes it available to you.
Plasma is a fast-moving project, and bugs in one version are often fixed in the
next one.

If you need support for Plasma 5.22.0, please contact your distribution, who
bears the responsibility of providing support for older releases that are no
longer supported by KDE.

If you can reproduce the issue after upgrading to a supported version, feel
free to re-open this bug report.

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

[ksysguard] [Bug 467821] ksysguardd crashed repeatedly after starting ksysguard with a buffer overflow detected

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[plasmashell] [Bug 419421] QML timers go too fast with multi-threaded render loop when using any high refresh rate screens on X11 when using FOSS amdgpu drivers

[Philip P.]

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

Philip P.  changed:

   What|Removed |Added

Summary|QML timers go too fast with |QML timers go too fast with
   |multi-threaded render loop  |multi-threaded render loop
   |when using any high refresh |when using any high refresh
   |rate screens on X11 when|rate screens on X11 when
   |using proprietary NVIDIA|using FOSS amdgpu drivers
   |drivers |

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

[kdeconnect] [Bug 467822] New: SMS messages are sent but not acknowledged and replies are not received on CalyxOS

[Tony Schmidt]

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

Bug ID: 467822
   Summary: SMS messages are sent but not acknowledged and replies
are not received on CalyxOS
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Unspecified
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: t...@opensourceit.org
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY
SMS messages are sent but not acknowledged and replies are not received on
Pixel 4a5g running CalyxOS 4.7.5.


STEPS TO REPRODUCE
1. Pair phone with computer.
2. Send an SMS to a contact from the computer.

OBSERVED RESULT
Messages are sent to contact but the message appears gray (unacknowledged?) in
desktop UI and replies from the contact are only received on the phone and not
the computer.

EXPECTED RESULT
Sent messages should turn black and replies from contact should be received
(tested and works on Pixel 6 running stock Android).

SOFTWARE/OS VERSIONS
Desktop OS: PopOS 22.04
Mobile OS: CalyxOS 4.7.5
Android KDE Connect 1.23.2

ADDITIONAL INFORMATION
Several warnings are posted in the attached Android logs, but I'm unsure which
warning is the primary issue or what configuration the CalyxOS system may be
missing to support the SMS message acknowledgement and receiving functions.

Some of the suspect warnings and logs include:
* W ContextImpl: Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1222
com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3085
com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1616
com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:492
android.os.Binder.execTransactInternal:1285
* W BroadcastQueue: Permission Denial: receiving Intent {
act=android.intent.action.SERVICE_STATE flg=0x110 (has extras) } to
ProcessRecord{df2db07 2591:com.android.systemui/u0a171} (pid=2591, uid=10171)
requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid
1001)
* I QImsService: ImsSmsImpl : onSendSmsResult:: token:6 smsResponse:{
mMessageRef = 6, mSendSmsResult = 1, mSendSmsReason = 0, mNetworkErrorCode =
-1}

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

[digikam] [Bug 467215] macOS 11.74 Big Sur: digikam crashes unexpectedly after launching G'MIC (theme settings relevant)

[No_Planet_2]

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

--- Comment #26 from No_Planet_2  ---
Hats off, Gilles. Describing G'MIC is a real painstaking job. I can only say:
Thumbs up! One thing perhaps: The menu item About/Download external data could
possibly be of importance for travelers, as well as the possibility to load new
filter definitions via internet. I couldn't find out anything about that,
because G'MIC is much less documented than digikam ;-).

But the jpfleury.github.io link is very helpful. Thanks!
Greetings, Martin

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

[ksysguard] [Bug 467821] New: ksysguardd crashed repeatedly after starting ksysguard with a buffer overflow detected

[Matt Fagnani]

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

Bug ID: 467821
   Summary: ksysguardd crashed repeatedly after starting ksysguard
with a buffer overflow detected
Classification: Applications
   Product: ksysguard
   Version: 5.22.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ksysguardd
  Assignee: ksysguard-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 157597
  --> https://bugs.kde.org/attachment.cgi?id=157597=edit
Full trace of ksysguardd crash

SUMMARY

I'm using Plasma 5.27.3 on Wayland in a Fedora 38 KDE Plasma installation. I
started ksysguard from ksysguard-5.22.0-8.fc38.x86_64. A crash notification
appeared. gnome-abrt and coredumpctl showed that ksysguardd crashed repeatedly
after starting ksysguard when lmSensors was being initalized. The function
__GI___fortify_fail showed the error "buffer overflow detected" in frame 5 of
the trace.

Core was generated by `/usr/bin/ksysguardd'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, 
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, 
no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7fd376a2bc03 in __pthread_kill_internal (signo=6, threadid=)
at pthread_kill.c:78
#2  0x7fd3769daaee in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7fd3769c387f in __GI_abort () at abort.c:79
#4  0x7fd3769c460f in __libc_message (fmt=fmt@entry=0x7fd376b3f2e6 "*** %s
***: terminated\n")
at ../sysdeps/posix/libc_fatal.c:150
#5  0x7fd376abfb29 in __GI___fortify_fail (
msg=msg@entry=0x7fd376b3f28c "buffer overflow detected") at
fortify_fail.c:24
#6  0x7fd376abe364 in __GI___chk_fail () at chk_fail.c:28
#7  0x7fd376abdf45 in ___snprintf_chk (s=,
maxlen=maxlen@entry=300, 
flag=flag@entry=2, slen=slen@entry=36, format=format@entry=0x55ecb81b1f98
"lmsensors/%s/%s")
at snprintf_chk.c:29
#8  0x55ecb81a88d6 in snprintf (__fmt=0x55ecb81b1f98 "lmsensors/%s/%s",
__n=300, 
__s=) at /usr/include/bits/stdio2.h:54
#9  initLmSensors (sm=0x55ecb81b8190 )
at
/usr/src/debug/ksysguard-5.22.0-8.fc38.x86_64/ksysguardd/Linux/lmsensors.c:170
#10 0x55ecb8195319 in initModules ()
at
/usr/src/debug/ksysguard-5.22.0-8.fc38.x86_64/ksysguardd/ksysguardd.c:467
#11 main (argc=, argv=)
at
/usr/src/debug/ksysguard-5.22.0-8.fc38.x86_64/ksysguardd/ksysguardd.c:558

The crash happened 264 times according to coredumpctl. I'm attaching the full
trace.

STEPS TO REPRODUCE
1. Boot a Fedora 38 KDE Plasma installation updated to 2023-3-26 with the
updates-testing repo enabled
2. Log in to Plasma on Wayland
3. Start ksysguard

OBSERVED RESULT
ksysguardd crashed repeatedly after starting ksysguard with a buffer overflow
detected

EXPECTED RESULT
No crashes would happen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

Fedora 38 involved a change to use the build flag _FORTIFY_SOURCE=3 
https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags
That change might be involved in the buffer overflow being detected. This
problem appears to have been reported at
https://bugzilla.redhat.com/show_bug.cgi?id=2179990

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[Maik Qualmann]

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

--- Comment #13 from Maik Qualmann  ---
The webmp format is also broken here on Linux. There should be a bug report for
the KImageFormats plugins.

Maik

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

[muon] [Bug 425073] Can't configure software sources through Muon package manager

[Aaron Wolf]

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

--- Comment #16 from Aaron Wolf  ---
(In reply to Aaron Wolf from comment #15)
> Seems to me because it is trying to use `software-properties-kde` when the
> correct package (in Neon at least) is `software-properties-qt`
> 
> Maybe that would fix this?

Sorry, I see this was discussed already, just somehow didn't see the comments
at first

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

[muon] [Bug 425073] Can't configure software sources through Muon package manager

[Aaron Wolf]

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

Aaron Wolf  changed:

   What|Removed |Added

 CC||wolft...@gmail.com

--- Comment #15 from Aaron Wolf  ---
Seems to me because it is trying to use `software-properties-kde` when the
correct package (in Neon at least) is `software-properties-qt`

Maybe that would fix this?

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

[digikam] [Bug 467675] digiKam fail to export to WEBP and WBMP formats

[bugzilla_noreply]

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

--- Comment #12 from caulier.gil...@gmail.com ---
Can you share the test files to try to reproduce ?

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

[kwin] [Bug 430112] "certificate expired" dialog steals focus from other applications

[Christian Boltz]

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

Christian Boltz  changed:

   What|Removed |Added

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

--- Comment #6 from Christian Boltz  ---
I've seen it with X.

(I have to admit that I didn't try wayland yet, therefore I don't know if it
also happens there.)

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

[i18n] [Bug 467802] Wrong translations on https://kstars.kde.org/tr/features

[Phu H. Nguyen]

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

--- Comment #5 from Phu H. Nguyen  ---
Many thanks!

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

[cantor] [Bug 465278] Inconsistent printing of dollar-terminated commands

[Alexander Semke]

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

Alexander Semke  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Alexander Semke  ---


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

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