[NeoChat] [Bug 479053] Save As button opens "Open File" dialog instead of Save

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=479053

--- Comment #4 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/network/neochat/-/merge_requests/1562

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

[NeoChat] [Bug 479053] Save As button opens "Open File" dialog instead of Save

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=479053

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #3 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/network/neochat/-/merge_requests/1561

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

[digikam] [Bug 481180] digikam incorrectly reads metadata field "Subject" when "HierarchicalSubject" is also present

2024-02-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=481180

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||8.3.0
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This is not a bug. Check out the advanced metadata settings:

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

Here you can specify the order in which digiKam finds the metadata in images;
the list is processed from top to bottom. At the first entry where valid values
are found, the process is aborted and this one is used. You can set the order
yourself, you can also see that xmp.lr.hierarchicalSubject is before
xmp.dc.subject in the list, therefore tags in xmp.dc.subject are ignored. So if
you have metadata in images that are out of sync, you can enable the "Read all
metadata for tags" option. Now digiKam will read and mix all metadata fields
for tags. Then you have your desired result.

Maik

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

[plasmashell] [Bug 481197] When the panel is hidden, a thin blue line is always visible

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481197

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kde] [Bug 481195] SDDM password field does not submit when the Enter key is pressed

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481195

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[krita] [Bug 470109] Moving the timeline with the bar makes the zoom function on the timeline engage for some reason

2024-02-10 Thread nunya
https://bugs.kde.org/show_bug.cgi?id=470109

--- Comment #3 from nunya  ---
 This is a video showing the bug exactly. First with the mouse then with the
tablet. This is still happening in the most recent 5.2.2 release.
On Thursday, January 25, 2024 at 05:43:02 PM PST, Emmet O'Neill
 wrote:  

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

Emmet O'Neill  changed:

          What    |Removed                    |Added

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

--- Comment #1 from Emmet O'Neill  ---
The zoomable scrollbar on the animation timeline is designed to slide the
tileline left and right when you drag it left and right, while zooming in and
out when you drag it up and down. It's a bit unconventional, but this is a to
make it very quick and easy to pan and zoom the timeline with a single
press-and-slide motion of a mouse or pen.

In other words, it should only zoom in when you drag it in an upwards
direction, and it should only zoom out when you drag it downwards. 
As such, when dragging left and right, it shouldn't affect the zoom much (if at
all).

Right now it seems to be working as intended for me with both a tablet and
mouse, and because of that I can't confirm it.
If you feel like it's still not working the way you want or expect it to,
please feel free to reopen this bug and I can take another look at it.

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

[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover

2024-02-10 Thread Yao Mitachi
https://bugs.kde.org/show_bug.cgi?id=481000

--- Comment #8 from Yao Mitachi  ---
Created attachment 165738
  --> https://bugs.kde.org/attachment.cgi?id=165738=edit
Same issue with a new user.

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

[plasmashell] [Bug 481197] New: When the panel is hidden, a thin blue line is always visible

2024-02-10 Thread Tobias G.
https://bugs.kde.org/show_bug.cgi?id=481197

Bug ID: 481197
   Summary: When the panel is hidden, a thin blue line is always
visible
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: tobi.goerg...@gmail.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 165737
  --> https://bugs.kde.org/attachment.cgi?id=165737=edit
Screenshot showing blue line

SUMMARY
I have a floating panel and set it to dodge windows, which works fine. However,
when the panel is hidden, a thin blue line is visible at the bottom of the
screen where the panel is located (see screenshot)
If this behavior is wanted, is there an option to turn this off?


STEPS TO REPRODUCE
1. Set panel to floating
2. Set panel to dodge windows
3. Open fullscreen content

OBSERVED RESULT
There's a blue line at the screen edge where the panel is

EXPECTED RESULT
There is no indicator at to where the panel is

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240206
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.2-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7

ADDITIONAL INFORMATION
See Image

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

[krita] [Bug 481196] New: Imported audio is not audible.

2024-02-10 Thread Izzy
https://bugs.kde.org/show_bug.cgi?id=481196

Bug ID: 481196
   Summary: Imported audio is not audible.
Classification: Applications
   Product: krita
   Version: 5.2.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: thechillchillisr...@gmail.com
  Target Milestone: ---

Basically whenever I upload an audio file of any sort, nothing seems to
actually get uploaded. There is no sound whenever I put it in and despite my
attempts to figure out why it's been doing this nothing has changed.


STEPS TO REPRODUCE
1. Open canvas
2. Use animation workspace
3.  Upload mp3

OBSERVED RESULT
Imported audio does not play upon testing animation with sound.

EXPECTED RESULT
Imported audio is audible upon pressing the play animation button.

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

ADDITIONAL INFORMATION
Where am I meant to paste the data that it says to paste?

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

[kde] [Bug 481195] New: SDDM password field does not submit when the Enter key is pressed

2024-02-10 Thread Nicholas Estrada
https://bugs.kde.org/show_bug.cgi?id=481195

Bug ID: 481195
   Summary: SDDM password field does not submit when the Enter key
is pressed
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: k...@nicholasjestrada.aleeas.com
  Target Milestone: ---

SUMMARY
SDDM password field does not submit when the Enter key is pressed.
Might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=478875 
Not sure, because that one mentions X11 and the virtual keyboard specifically,
neither of which apply to my setup.

STEPS TO REPRODUCE
1. Restart computer
2. Type in password
3. Press [Enter]

OBSERVED RESULT
Does not log in or try to submit the password

EXPECTED RESULT
Submits the password

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.5.0-17-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 3 Graphics
Manufacturer: MOTILE
Product Name: M141

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

[NeoChat] [Bug 479053] Save As button opens "Open File" dialog instead of Save

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=479053

ulte...@gmail.com changed:

   What|Removed |Added

 CC||ulte...@gmail.com

--- Comment #2 from ulte...@gmail.com ---
Not a recent regression.
Same bug exists in 23.08.4

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

[neon] [Bug 481043] After boot, there was no splash screen for loading, just the wallpaper. It took several minutes for the lock screen to load

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481043

--- Comment #6 from feat...@engineer.com ---
One additional piece of info: The login without password is enabled, so no
lockscreen of login screen should have been shown. But the problem with lack of
splash screen, and the desktop taking about a minute to become usable (while
displaying just a mouse cursor over the wallpaper) still stands.

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

[plasmashell] [Bug 479183] With Qt 6.7, no "Add to favorites" and "Remove from favorites" menu items

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=479183

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/plasma/plasma-desktop/-/merge_requests/2032

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

[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover

2024-02-10 Thread Yao Mitachi
https://bugs.kde.org/show_bug.cgi?id=481000

--- Comment #7 from Yao Mitachi  ---
I am using Breeze Dark. Haven't customized it. Also noticed the issue with
light Breeze.

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

[dolphin] [Bug 480982] Dolphin icon color stopped respect accent color (in Taskbar)

2024-02-10 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=480982

Fushan Wen  changed:

   What|Removed |Added

   Target Milestone|1.0 |---
   Keywords|wayland |
Version|master  |24.01.95
Product|plasmashell |dolphin
   Assignee|plasma-b...@kde.org |dolphin-bugs-n...@kde.org
 CC||kfm-de...@kde.org
  Component|Task Manager and Icons-Only |general
   |Task Manager|

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

[kid3] [Bug 481194] Failed to display full date in the file browser date column if the filename contains non-English text.

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481194

--- Comment #1 from rxpre...@gmail.com ---
I don't know how to edit my report. I typed the wrong date but basically set
date tag into 2013-11-21 or 2014-02-27 are just examples, so shouldn't be
confused.

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

[kid3] [Bug 481194] New: Failed to display full date in the file browser date column if the filename contains non-English text.

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481194

Bug ID: 481194
   Summary: Failed to display full date in the file browser date
column if the filename contains non-English text.
Classification: Applications
   Product: kid3
   Version: 3.9.x
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: uflei...@users.sourceforge.net
  Reporter: rxpre...@gmail.com
  Target Milestone: ---

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

SUMMARY
Failed to display full date in the file browser date column if the filename
contains non-English text.

STEPS TO REPRODUCE
1.  Set date tag into 2013-11-21
2. Add non-English text into title tag & album tag: 그리워해요
3.  Apply filename format from tag: %{artist} - %{album} - %{track} - %{title} 
4. Right click on file browser column to show Date column

OBSERVED RESULT
Date column will only show the year (2014) instead of full date (2014-02-27)

EXPECTED RESULT
Date column should show full date: 2014-02-27

SOFTWARE/OS VERSIONS
Windows: 11 23H2
Kid3: 3.9.4

ADDITIONAL INFORMATION
Tested using a flac file using Vorbis as Tag 2.

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

[frameworks-kstatusnotifieritem] [Bug 478734] Main window is not closable after first close to tray

2024-02-10 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=478734

--- Comment #8 from Nicolas Fella  ---
https://invent.kde.org/frameworks/kstatusnotifieritem/-/merge_requests/11 works
around this

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

[kmail2] [Bug 481135] Closing KMail window with system tray icon enabled doesn't always close the window

2024-02-10 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=481135

Nicolas Fella  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||nicolas.fe...@gmx.de

--- Comment #1 from Nicolas Fella  ---


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

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

[frameworks-kstatusnotifieritem] [Bug 478734] Main window is not closable after first close to tray

2024-02-10 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=478734

Nicolas Fella  changed:

   What|Removed |Added

 CC||stefano.cro...@alice.it

--- Comment #7 from Nicolas Fella  ---
*** Bug 481135 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 481193] The position of window of application is not saved after it is closed and restored when opened again

2024-02-10 Thread Piotr Mierzwinski
https://bugs.kde.org/show_bug.cgi?id=481193

Piotr Mierzwinski  changed:

   What|Removed |Added

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

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

[kwin] [Bug 481193] New: The position of window of application is not saved after it is closed and restored when opened again

2024-02-10 Thread Piotr Mierzwinski
https://bugs.kde.org/show_bug.cgi?id=481193

Bug ID: 481193
   Summary: The position of window of application is not saved
after it is closed and restored when opened again
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

SUMMARY
I think in Plasma 5 window position were saved, but In Plasma 6.1 I noticed
that this is doesn't happen.
I don't know if there is any global option for this or should I set this for
every window by "Window Rules"?

STEPS TO REPRODUCE
1. Start Dolphin or Konsole
2. Move window to right/left of desktop
3. log off and log in and start Dolphin or Konsole
or just close window and open Dolphin or Konsole
4. 

OBSERVED RESULT
Window of again opened application is always placed at the center of desktop.

EXPECTED RESULT
Window of again opened application should be placed at the position where
finished its work.

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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 480982] Dolphin icon color stopped respect accent color (in Taskbar)

2024-02-10 Thread Piotr Mierzwinski
https://bugs.kde.org/show_bug.cgi?id=480982

--- Comment #8 from Piotr Mierzwinski  ---
(In reply to fin-w from comment #7)
> With "Plasma Style" set to "Breeze: Follows colour scheme", and any default
> "Colours" colour scheme (Breeze Classic / Light / Dark), the Dolphin icon
> ignores custom accent colours. Folders shown within Dolphin itself will
> respect the custom colour though: the issue seems only with the icon.

And forgot to mention. My Plasma Style is "ROUNDED COLOR". As far as I remember
this style follows by color scheme (at least in Plasma 5). And that's why I
installed it some time ago and used long time starting Plasma 5.
Before Plasma 6.1 the color of Dolphin icon placed in TaskBar was as I
expected. So for me it looks like regression and that's why reported this.. I
didn't change icon of Dolphin. So maybe any update changed this.

> Folders shown within Dolphin itself . ...
This works fine. The color of icons of folders showing in files list by Dolphin
are in accent color I set.

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

[dolphin] [Bug 447115] Dolphin reports "Access denied" when moving files from ext4 to ntfs

2024-02-10 Thread Eduardo
https://bugs.kde.org/show_bug.cgi?id=447115

Eduardo  changed:

   What|Removed |Added

 CC||eduardo.c...@kdemail.net

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

[plasmashell] [Bug 479490] plasmashell crashes upon opening menu

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=479490

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kscreenlocker] [Bug 479698] Kscreenlocker_g Segfaults in 3-monitor setup

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=479698

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WORKSFORME

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

[plasmashell] [Bug 479456] Screen corruption after wake from sleep on Wayland session

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=479456

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[plasmashell] [Bug 476737] Plasma crashed (and reset) itself a few moments after sleep

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=476737

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[systemsettings] [Bug 434988] "Shift" key cannot be used with some shortcuts combinations

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=434988

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[Powerdevil] [Bug 480093] Screens don't stay turned off after 60 seconds on lock screen

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=480093

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

[plasma-systemmonitor] [Bug 480841] Hardware sensors under sensors in system monitor seem to be broken in plasma 6

2024-02-10 Thread Pieter van der Vegte
https://bugs.kde.org/show_bug.cgi?id=480841

--- Comment #5 from Pieter van der Vegte  ---
Working properly for me now.
Thank you :-)

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

[plasma-systemmonitor] [Bug 480840] Neon unstable Plasma 6 Wayland System Monitor does not find & display NVMe temps, as on X11 Plasma 5.27.10 - same PC.

2024-02-10 Thread Pieter van der Vegte
https://bugs.kde.org/show_bug.cgi?id=480840

--- Comment #3 from Pieter van der Vegte  ---
Working properly now.
Thank you :-)

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

[Spectacle] [Bug 479058] Spectacle becomes unresponsive and has to be terminated when screen recording entire screen

2024-02-10 Thread Prajna Sariputra
https://bugs.kde.org/show_bug.cgi?id=479058

--- Comment #5 from Prajna Sariputra  ---
Another bug report has been filed about Spectacle freezing only when a second
recording is started: https://bugs.kde.org/show_bug.cgi?id=481188

Not sure if that bug should be marked as duplicate of this one or if this bug
should be closed since the original description no longer describes the current
situation.

Also, when running Spectacle in a terminal I see these error messages appearing
after the end of the first recording, might have something to do with why the
second recording fails?

*** pw_stream_destroy called from wrong context, check thread and locking: Not
in loop
*** impl_ext_end_proxy called from wrong context, check thread and locking: Not
in loop
'pthread_equal(impl->thread, thread_id)' failed at
../pipewire/spa/plugins/support/loop.c:363 loop_leave()

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

[Breeze] [Bug 479269] Breeze-Dark Icon Theme not using Dark Icons

2024-02-10 Thread Dominic
https://bugs.kde.org/show_bug.cgi?id=479269

--- Comment #12 from Dominic  ---
(In reply to Nate Graham from comment #10)
> Thanks. Can you reproduce the issue in any non-GTK apps?

Sorry for the late reply, I need to turn on email notifications
No it seems to be exclusive to gtk

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

[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules

2024-02-10 Thread Dominic
https://bugs.kde.org/show_bug.cgi?id=481192

Dominic  changed:

   What|Removed |Added

 CC||dominicglus...@gmail.com

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

[systemsettings] [Bug 481192] New: Systemsettings crashes when going into various kcm modules

2024-02-10 Thread Dominic
https://bugs.kde.org/show_bug.cgi?id=481192

Bug ID: 481192
   Summary: Systemsettings crashes when going into various kcm
modules
Classification: Applications
   Product: systemsettings
   Version: master
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: dominicglus...@gmail.com
  Target Milestone: ---

SUMMARY
***
Various kcm modules cause systemsettings to crash, from navigating to it in the
gui or running systemsettings kcm_foobar, here's a list of the one's I can
confirm are broken. It always gives an error about Cyclic dependency, and the
kcrash always says crashRecursionCounter=2
kcm_aboutdistro
qt.qml.typeresolution.cycle: Cyclic dependency detected between
"qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and
"qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2
[1]5731 segmentation fault (core dumped)  systemsettings kcm_about-distro

kcm_colors
qt.qml.typeresolution.cycle: Cyclic dependency detected between
"qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and
"qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
KCrash: Application 'systemsettings' crashing... crashRecursionCounter = 2
[1]6862 segmentation fault (core dumped)  systemsettings kcm_colors

(It's the same for the rest)
kcm_cursortheme
kcm_pulseaudio
kcm_style
kcm_fonts

There might be more that I accidently clicked over, if anyone can confirm more
please list them.
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. Add the kde unstable repos to openSUSE Tumbleweed
2. Update via sudo zypper dup --force-resolution ; sudo zypper install
plasma6-session ; sudo zypper inr ; reboot
3. Open systemsettings either from the application launcher or running
systemsettings kcm_foobar (replace with the broken kcm module)

OBSERVED RESULT
Crashes on various modules

EXPECTED RESULT
Not to crash

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20240208
(available in About System)
KDE Plasma: 6.0.80
KDE Frameworks: 5.116.0
Qt: 5.15.12
Kernel: 6.7.4-1-default
ADDITIONAL INFORMATION
I'm new to bug reporting, please let me know how I can provide more info.

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

[frameworks-knewstuff] [Bug 481191] New: Cant download ram widget from github source

2024-02-10 Thread Kangarooo
https://bugs.kde.org/show_bug.cgi?id=481191

Bug ID: 481191
   Summary: Cant download ram widget from github source
Classification: Frameworks and Libraries
   Product: frameworks-knewstuff
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: kangar...@gmail.com
CC: alexander.loh...@gmx.de, kdelibs-b...@kde.org
  Target Milestone: ---

Widgets, install new, find ram, filter by most downloaded
find Resources Monitor by Martin
Install, choose github, not installing
Asks to open link
Also suggests to report this bug

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

[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep

2024-02-10 Thread Ilya Bizyaev
https://bugs.kde.org/show_bug.cgi?id=475605

Ilya Bizyaev  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 CC||bizy...@zoho.com

--- Comment #43 from Ilya Bizyaev  ---
I see that similarly named bugs for Wayland are being merged into this one as
duplicates, but I'm still getting this issue with the referenced commit after
suspending the Wayland session.

Turning the monitor off and on again with the physical button helped just now.

Operating System: openSUSE Tumbleweed 20240208
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.7.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × Intel® Core™ i9-14900K
Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2 (driver version:
545.29.06)

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

[kwin] [Bug 416570] Option for "sticky edges" in multi-screen configuration

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=416570

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored

2024-02-10 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=481166

--- Comment #3 from David Jarvie  ---
As stated in its handbook, KAlarm is designed as a personal message, email and
command scheduler. It is not designed for group use. It aims to present a
simple interface (unless the user chooses to expand the options displayed) to
allow ordinary (i.e. non-technical) users to schedule alarms. Most users only
use it with its default calendars, and not with any calendars created by other
applications. The fact that KOrganizer reminders have been messed up in recent
times is unfortunate, but I don't want KAlarm to be amended or expanded in any
way in order to be used as an adjunct to KOrganizer to provide its reminder
functionality. It's up to KOrganizer to sort out its own deficiencies.

For these reasons, I don't see it as important to provide KAlarm with the
ability to read VTODOs, but I wouldn't object. It would be important to first
of all decide on how reading calendars containing VTODOs should fit into
KAlarm's user interface. As I said previously, I would see it as being via some
sort of import function, but I don't know whether that would satisfy your goal
of users not being surprised when VTODOs are ignored if KAlarm is told to use a
calendar which it didn't create itself. Bear in mind that if VTODOs were edited
in KAlarm, or if they contained recurrences, they would need to be rewritten as
VEVENTs (and of course, functions specific to todos would be not show in
KAlarm).

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

[kdevelop] [Bug 481189] No option to attach to the process

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481189

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[frameworks-frameworkintegration] [Bug 423669] Change OK/Cancel buttons order/layout to improve consistency with other software

2024-02-10 Thread Hyuri
https://bugs.kde.org/show_bug.cgi?id=423669

Hyuri  changed:

   What|Removed |Added

 CC||hyuri.pimen...@gmail.com

--- Comment #10 from Hyuri  ---
This small quality-of-life change would be perfect to feature in the Plasma 6
release ;)

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

[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text

2024-02-10 Thread Rodrigo Pedra Brum
https://bugs.kde.org/show_bug.cgi?id=475378

--- Comment #6 from Rodrigo Pedra Brum  ---
For completeness, setting the line-height back to 1 gets rid of the odd
behavior, and text selection behaves as expected.

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

[kwin] [Bug 481190] New: KWin crashes on alt tab. Several windows were open.

2024-02-10 Thread Johannes Derrer
https://bugs.kde.org/show_bug.cgi?id=481190

Bug ID: 481190
   Summary: KWin crashes on alt tab. Several windows were open.
Classification: Plasma
   Product: kwin
   Version: 5.27.10
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: johannes.der...@gmx.de
  Target Milestone: ---

Application: kwin_x11 (5.27.10)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.6.13-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
I alt+tab through several firefox windows and pycharm windows. The tabbing was
buggy and the windows didn't show a preview. KWin crashed then 2 times in a row
when alt+tabbing.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

   PID: 1942 (kwin_x11)
   UID: 1000 (johannes)
   GID: 1000 (johannes)
Signal: 11 (SEGV)
 Timestamp: Sat 2024-02-10 22:55:52 CET (46s ago)
  Command Line: /usr/bin/kwin_x11 --replace
Executable: /usr/bin/kwin_x11
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service
  Unit: user@1000.service
 User Unit: plasma-kwin_x11.service
 Slice: user-1000.slice
 Owner UID: 1000 (johannes)
   Boot ID: 5ed1274be3a84b2eb136b4b1fc514515
Machine ID: 7022a249a2a04e5688393321af5fbac6
  Hostname: johannes-debian
   Storage:
/var/lib/systemd/coredump/core.kwin_x11.1000.5ed1274be3a84b2eb136b4b1fc514515.1942.170760215200.zst
(present)
  Size on Disk: 7.2M
   Message: Process 1942 (kwin_x11) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-255.3-1.amd64
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64
Module libudev.so.1 from deb systemd-255.3-1.amd64
Stack trace of thread 1942:
#0  0x7f16529c916c n/a (libc.so.6 + 0x8a16c)
#1  0x7f165297b472 raise (libc.so.6 + 0x3c472)
#2  0x7f1655d49b46 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b46)
#3  0x7f165297b510 n/a (libc.so.6 + 0x3c510)
#4  0x7f16529c916c n/a (libc.so.6 + 0x8a16c)
#5  0x7f165297b472 raise (libc.so.6 + 0x3c472)
#6  0x7f165297b510 n/a (libc.so.6 + 0x3c510)
#7  0x7f16529c41c4 n/a (libc.so.6 + 0x851c4)
#8  0x7f16529c6888 pthread_cond_wait (libc.so.6 + 0x87888)
#9  0x7f16538e0cab
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xe0cab)
#10 0x7f165520c508 n/a (libQt5Quick.so.5 + 0x20c508)
#11 0x7f165520d7c3 n/a (libQt5Quick.so.5 + 0x20d7c3)
#12 0x7f1653f4b9c5 _ZN7QWindow5eventEP6QEvent
(libQt5Gui.so.5 + 0x14b9c5)
#13 0x7f1653162f32
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162f32)
#14 0x7f1653acc748
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2cc748)
#15 0x7f1653f40931
_ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE
(libQt5Gui.so.5 + 0x140931)
#16 0x7f1653f131ac
_ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Gui.so.5 + 0x1131ac)
#17 0x7f164e0fa15e n/a (libQt5XcbQpa.so.5 + 0x6f15e)
#18 0x7f16515111f4 n/a (libglib-2.0.so.0 + 0x571f4)
#19 0x7f1651514317 n/a (libglib-2.0.so.0 + 0x5a317)
#20 0x7f1651514930 g_main_context_iteration
(libglib-2.0.so.0 + 0x5a930)
#21 0x7f1653b27d4a
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x327d4a)
#22 0x7f1653acb0fb
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2cb0fb)
#23 0x7f1653ad38a4 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2d38a4)
#24 0x55af4c902275 n/a (kwin_x11 + 0x43275)
#25 0x7f16529666ca n/a (libc.so.6 + 0x276ca)
#26 0x7f1652966785 __libc_start_main (libc.so.6 + 0x27785)
#27 0x55af4c903831 n/a (kwin_x11 + 0x44831)

Stack trace of thread 1970:
#0  0x7f1652a3aabf __poll (libc.so.6 + 0xfbabf)
#1  0x7f1651514277 n/a (libglib-2.0.so.0 + 0x5a277)
#2  0x7f1651514930 g_main_context_iteration
(libglib-2.0.so.0 + 0x5a930)
  

[kdevelop] [Bug 481189] No option to attach to the process

2024-02-10 Thread popov895
https://bugs.kde.org/show_bug.cgi?id=481189

popov895  changed:

   What|Removed |Added

 CC||popov...@ukr.net

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

[kdevelop] [Bug 481189] New: No option to attach to the process

2024-02-10 Thread popov895
https://bugs.kde.org/show_bug.cgi?id=481189

Bug ID: 481189
   Summary: No option to attach to the process
Classification: Applications
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: popov...@ukr.net
  Target Milestone: ---

SUMMARY

After the System Activity has been removed from the Plasma 6, there's no option
to attach to the process.

SOFTWARE/OS VERSIONS

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249.0
KDE Gear Version: 24.04.70
Qt Version: 6.6.1
Graphics Platform: Wayland

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

[ktorrent] [Bug 481151] cannot restore ktorrent window after closing

2024-02-10 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=481151

Andrius Štikonas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/netw
   ||ork/ktorrent/-/commit/e35b4
   ||881605f045ebe8bca2da357c2a3
   ||ae2f1e02

--- Comment #3 from Andrius Štikonas  ---
Git commit e35b4881605f045ebe8bca2da357c2a3ae2f1e02 by Andrius Štikonas, on
behalf of Yifan Zhu.
Committed on 10/02/2024 at 21:50.
Pushed by stikonas into branch 'master'.

Replace QWidget->show() with QWindow()->show()

efe4aa0dcc23e57e68ecd809068f1a49d7705a07 replaces many calls to
QWidget->show() with QWindow()->show(). Since mixing these is not
supported (https://bugreports.qt.io/browse/QTBUG-120316), replace the
remaining QWidget->show() with QWindow()->show() as well.

Test-plan:
- Enable KTorrent's system tray icon
- Close the main KTorrent window
- Execute ktorrent from the command line
- Close the main KTorrent window
- Execute ktorrent from the command line

Previously:
- After a few repeats ktorrent window doesn't show

Now:
- ktorrent window always shows after executing ktorrent

M  +2-1ktorrent/main.cpp

https://invent.kde.org/network/ktorrent/-/commit/e35b4881605f045ebe8bca2da357c2a3ae2f1e02

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

[systemsettings] [Bug 481187] When typing in the Pointer Speed numerical field (the -1 to 1 float field), it changes the number as you're typing making manual entry difficult

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481187

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[Spectacle] [Bug 481188] Spectacle hangs when trying to start a second recording

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481188

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[systemsettings] [Bug 481187] When typing in the Pointer Speed numerical field (the -1 to 1 float field), it changes the number as you're typing making manual entry difficult

2024-02-10 Thread alem99393
https://bugs.kde.org/show_bug.cgi?id=481187

alem99...@gmail.com  changed:

   What|Removed |Added

 CC||alem99...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[Spectacle] [Bug 481188] New: Spectacle hangs when trying to start a second recording

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481188

Bug ID: 481188
   Summary: Spectacle hangs when trying to start a second
recording
Classification: Applications
   Product: Spectacle
   Version: 24.01.95
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: briguy...@live.com
CC: k...@david-redondo.de
  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. Launch Spectacle
2. Select Recording
3. Choose Full Screen or Window (I did not attempt Rectangular Region)
4. Select a window or screen to start your recording
5. Go back to Spectacle and select Finish Recording
6. Choose Full Screen or Window to start a second recording
7. Select a window or screen to start your recording

OBSERVED RESULT
Spectacle hangs when you try to start a second recording, and a recording is
not made.

EXPECTED RESULT
A recording is made successfully

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.7.4-arch1-1 EndeavourOS
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 481187] New: When typing in the Pointer Speed numerical field (the -1 to 1 float field), it changes the number as you're typing making manual entry difficult

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481187

Bug ID: 481187
   Summary: When typing in the Pointer Speed numerical field (the
-1 to 1 float field), it changes the number as you're
typing making manual entry difficult
Classification: Applications
   Product: systemsettings
   Version: 5.93.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_mouse
  Assignee: plasma-b...@kde.org
  Reporter: briguy...@live.com
CC: natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 165735
  --> https://bugs.kde.org/attachment.cgi?id=165735=edit
Demonstration of field behavior editing numerical numbers

SUMMARY
(I would assume this is a QT 6 bug, however I don't have the technical
understanding to confirm so filing this where I encountered the issue)

When editing the Pointer Speed field, and typing in numbers, it changes the
number as you're typing, making it difficult to type in a specific number you
want. The two scenarios are as soon as you end up with a -0 in the field, it
will reset the field immediately back to 0, even if your intent was to change
to a different negative floating point 0 number. The second scenario is when
adding back a floating point number, the first number you add it will
immediately append a zero to, making it difficult to put in the two levels of
sensitivity expected in this field.


STEPS TO REPRODUCE
1. Open System Settings
2. Select Mouse & Touchpad
3. Select Mouse and choose your mouse device
4. In the Pointer speed text bad, click into the box
5. Delete the last 2 digits (for example, if the number is -0.40, select it and
delete the 0 and then the 4)
6. Observe the negative sign is immediately removed from the number, meaning
you can't simply type a new number to choose a different negative number if
that was your intent.
7. Now, select it and try to change the sensitivity to -0.23
8. Notice when you type in the 2, it immediately appends a zero to become
-0.20, so you need to delete the zero to then add the 3 to be become -0.23

OBSERVED RESULT
The number in the field is consistently evaluated and overridden by a different
value even when the user is actively typing in the field

EXPECTED RESULT
When I am actively typing in a field, the number should not be changed by the
system which interrupts my ability to type the number I want.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.7.4-arch1-1 EndeavourOS
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

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

[kwin] [Bug 481186] New: No option to have CAPS Lock to toggle Numbers AZERTY keyboards

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481186

Bug ID: 481186
   Summary: No option to have CAPS Lock to toggle Numbers AZERTY
keyboards
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sourcew...@mailbox.org
  Target Milestone: ---

Created attachment 165734
  --> https://bugs.kde.org/attachment.cgi?id=165734=edit
caps lock options

SUMMARY
***
Sorry already, could not find the right category, maybe there should be a
general category when we don't know which category to use


STEPS TO REPRODUCE
1. press on caps lock then press a number key on an Azerty keyboard
2. 
3. 

OBSERVED RESULT
Will  activate the horizontal number keys from the Azerty keyboard but will
keep the "maintain shift key behavior"

EXPECTED RESULT
Should activate the horizontal number keys from the Azerty keyboard(not
numlock) without having a "maintain Shift behaviour."
but in the current situation, if you forget to toggle off shift lock, then you
click on your task bar and it duplicates an item, if you click on a mail in
thunderbird, it add its to a selection, etc.

CONFIGURATION 
>From the menu the caps lock key is configured either : 
1°as caps lock behavior>caps lock toggles normal capitalization of alphabetic
letters
2° caps lock toggles shift lock
If you use option 1, the numbers are not activated
If you use option 2, the numbers are activated but Caps then has a "maintain
shift" behavior activated too

--> I think there should be a 3rd option to activate Caps lock without having
the "maintain shift behaviors" in applications




SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  kubuntu 23.10
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 481185] Upon upgrade from KDE 5 to KDE 6 RC2, my mouse sensitivity was massively increased

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481185

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[systemsettings] [Bug 481185] New: Upon upgrade from KDE 5 to KDE 6 RC2, my mouse sensitivity was massively increased

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481185

Bug ID: 481185
   Summary: Upon upgrade from KDE 5 to KDE 6 RC2, my mouse
sensitivity was massively increased
Classification: Applications
   Product: systemsettings
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: plasma-b...@kde.org
  Reporter: briguy...@live.com
CC: natalie_clar...@yahoo.de
  Target Milestone: ---

SUMMARY
I upgrade from KDE 5 to KDE 6 RC2, and upon upgrade the first thing I noticed
was my mouse sensitivity seemed massively faster to the point of being unusable
(2-3x faster at least). It was very jarring and my first task on upgrade needed
to be changing the sensitivity to how it felt before.

NOTE: I do not know the values before and after to know if the sensitivity
values needed to be different, or if it just felt different due to some KDE 6
change in behavior. 

STEPS TO REPRODUCE
1. Be on KDE 5 with a mouse sensitivity that you set and feels comfortable
2. Upgrade to KDE 6 RC2
3. Notice the mouse sensitivity has increased massively

OBSERVED RESULT
Mouse sensitivity increases massively upon upgrade to KDE 6 RC2

EXPECTED RESULT
The mouse sensitivity should feel functionally identical when doing an upgrade,
as this feels like a regression when doing an upgrade and gives an immediate
jarring feeling to using KDE 6.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Kernel 6.7.4-arch1-1

Unfortunately I do not know what my mouse sensitivity values were, so I'm
unsure if the sensitivity was reset, or if there's some other fundamental
change in KDE 6 that makes the mouse feel significantly faster.

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

[digikam] [Bug 481180] digikam incorrectly reads metadata field "Subject" when "HierarchicalSubject" is also present

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481180

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

   What|Removed |Added

  Component|Metadata-Engine |Metadata-Xmp

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

[kscreenlocker] [Bug 480709] +when external monitor is connected the screen locker crashes when the computer goes to sleep.

2024-02-10 Thread grestil
https://bugs.kde.org/show_bug.cgi?id=480709

--- Comment #3 from grestil <1wheelspi...@gmail.com> ---
(In reply to Nate Graham from comment #2)
> What instructions did it give you? Can you take a phone photo of the message?

https://photos.app.goo.gl/hTXCaGe82RpHTYdz6

None of these commands displayed seem to have any effect.

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

[digikam] [Bug 481180] digikam incorrectly reads metadata field "Subject" when "HierarchicalSubject" is also present

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481180

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

   What|Removed |Added

  Component|Tags-Engine |Metadata-Engine
 CC||caulier.gil...@gmail.com

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

[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.

2024-02-10 Thread Tobias Leupold
https://bugs.kde.org/show_bug.cgi?id=481103

Tobias Leupold  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #6 from Tobias Leupold  ---
Thanks for the update. I'm closing this then :-)

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

[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.

2024-02-10 Thread Kim
https://bugs.kde.org/show_bug.cgi?id=481103

--- Comment #5 from Kim  ---
SOLVED
I used flatseal to add host file permissions and now it works as expected, so
no problem with kgeotag, just another system to learn.
Can also use "sudo flatpak override [app id] --filesystem=host"
Thanks for the tips

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

[krita] [Bug 481184] New: Krita crashes on animation cache on a file without animation

2024-02-10 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=481184

Bug ID: 481184
   Summary: Krita crashes on animation cache on a file without
animation
Classification: Applications
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Mint (Debian based)
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: tamtamy.tym...@gmail.com
  Target Milestone: ---

Created attachment 165733
  --> https://bugs.kde.org/attachment.cgi?id=165733=edit
Crash log

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. Be on f3bb64bec1 (I was over it with some changes)
2. I was testing MR !636, so my file had at least a paint layer and some
references, possibly also a vector layer. Never had any animation, I doubt the
Animation Timeline docker was enabled.

OBSERVED RESULT
Crash

EXPECTED RESULT
No crash

SOFTWARE/OS VERSIONS
(Krita in a docker)
Krita

 Version: 5.3.0-prealpha (git 7406513)
 Hidpi: true

Qt

  Version (compiled): 5.15.7
  Version (loaded): 5.15.7

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.15.0-76-generic
  Pretty Productname: Ubuntu 20.04.6 LTS
  Product Type: ubuntu
  Product Version: 20.04
  Desktop: 
  Appimage build: No

Locale

  Languages: en_US, en, en_Latn_US
  C locale: en_US.UTF-8
  QLocale current: en
  QLocale system: en
  QTextCodec for locale: UTF-8

OpenGL Info

  Vendor:  "Intel" 
  Renderer:  "Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2)" 
  Driver version:  "4.6 (Core Profile) Mesa 21.2.6" 
  Shading language:  "4.60" 
  Requested format:  QSurfaceFormat(version 3.3, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:  QSurfaceFormat(version 4.6, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CoreProfile) 
  GL version: 4.6 
  Supports deprecated functions false 
  Is OpenGL ES: false 
  supportsBufferMapping: true 
  supportsBufferInvalidation: true 
  forceDisableTextureBuffers: false 
  Extensions: 
 GL_ARB_compute_shader 
 GL_ARB_sync 
 GL_ARB_indirect_parameters 
 GL_EXT_texture_compression_rgtc 
 GL_ARB_clip_control 
 GL_AMD_draw_buffers_blend 
 GL_KHR_blend_equation_advanced 
 GL_AMD_depth_clamp_separate 
 GL_INTEL_blackhole_render 
 GL_ARB_framebuffer_sRGB 
 GL_ARB_draw_instanced 
 GL_ARB_texture_query_lod 
 GL_ARB_pipeline_statistics_query 
 GL_EXT_shader_samples_identical 
 GL_MESA_texture_signed_rgba 
 GL_ARB_shader_image_load_store 
 GL_ARB_uniform_buffer_object 
 GL_ARB_clear_buffer_object 
 GL_EXT_shader_integer_mix 
 GL_ARB_timer_query 
 GL_KHR_robustness 
 GL_ARB_depth_clamp 
 GL_ARB_vertex_attrib_64bit 
 GL_EXT_demote_to_helper_invocation 
 GL_ARB_texture_buffer_object 
 GL_ARB_shader_texture_lod 
 GL_EXT_texture_shared_exponent 
 GL_ARB_robust_buffer_access_behavior 
 GL_ARB_shader_image_size 
 GL_3DFX_texture_compression_FXT1 
 GL_EXT_draw_buffers2 
 GL_ARB_vertex_type_10f_11f_11f_rev 
 GL_EXT_blend_equation_separate 
 GL_ARB_texture_multisample 
 GL_ARB_gpu_shader_int64 
 GL_EXT_semaphore_fd 
 GL_AMD_vertex_shader_viewport_index 
 GL_ARB_texture_non_power_of_two 
 GL_ARB_texture_cube_map_array 
 GL_ARB_invalidate_subdata 
 GL_ARB_texture_compression_bptc 
 GL_EXT_transform_feedback 
 GL_ARB_vertex_array_bgra 
 GL_ARB_sampler_objects 
 GL_ARB_texture_stencil8 
 GL_ARB_transform_feedback3 
 GL_ARB_map_buffer_alignment 
 GL_ARB_vertex_buffer_object 
 GL_KHR_robust_buffer_access_behavior 
 GL_ARB_gpu_shader5 
 GL_ARB_buffer_storage 
 GL_ARB_texture_query_levels 
 GL_ARB_internalformat_query2 
 GL_ARB_shader_precision 
 GL_ARB_texture_view 
 GL_ARB_copy_image 
 GL_ARB_framebuffer_object 
 GL_EXT_polygon_offset_clamp 
 GL_ARB_clear_texture 
 GL_ARB_shader_bit_encoding 
 GL_ARB_vertex_shader 
 GL_EXT_timer_query 
 GL_ARB_derivative_control 
 GL_AMD_conservative_depth 
 GL_ARB_post_depth_coverage 
 GL_EXT_memory_object_fd 
 GL_ARB_vertex_attrib_binding 
 

[Discover] [Bug 481183] New: Support adding the Flathub --user repo

2024-02-10 Thread Henning
https://bugs.kde.org/show_bug.cgi?id=481183

Bug ID: 481183
   Summary: Support adding the Flathub --user repo
Classification: Applications
   Product: Discover
   Version: git-stable-Plasma/5.27
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Flatpak Backend
  Assignee: plasma-b...@kde.org
  Reporter: amanita+kdeb...@mailbox.org
CC: aleix...@kde.org, jgrul...@redhat.com,
trav...@redhat.com
  Target Milestone: ---

Adding the --user repository allows users without any special elevated
privileges to install Flatpaks. The use case is simply if you want to only use
your system single-user anyways, or you even want to isolate apps only in your
profile.

on the "add Flathub" button it would be cool to have the possibility to choose,
between "system" and "user".

The rest already works well. Discover displays that repo (just not with the
icon) and it is also displayed as source correctly.

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

[kwin] [Bug 481182] Using Wayland only, when resuming from sleep the taskbar and desktop are always corrupted

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481182

--- Comment #1 from briguy...@live.com ---
Created attachment 165732
  --> https://bugs.kde.org/attachment.cgi?id=165732=edit
Video taken moments after resuming from sleep. Note I use the standard Breeze
Dark theme.

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

[kwin] [Bug 481182] Using Wayland only, when resuming from sleep the taskbar and desktop are always corrupted

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481182

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[kwin] [Bug 481182] New: Using Wayland only, when resuming from sleep the taskbar and desktop are always corrupted

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481182

Bug ID: 481182
   Summary: Using Wayland only, when resuming from sleep the
taskbar and desktop are always corrupted
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: briguy...@live.com
  Target Milestone: ---

SUMMARY
Using KDE 6 RC2, when using Wayland only, when I resume from sleep the desktop
is completely corrupted and unusable 100% of the time, and the taskbar, and
other KDE items are missing text, missing UI elements, flashing colors, etc.

I use the Breeze Dark theme, but as seen in the video taken moments after I
resumed from sleep, it is not my theme.

This repro's using both the nvidia stable and nvidia beta proprietary drivers.

When I switch back to X11, this does not repro.

STEPS TO REPRODUCE
1. Using KDE 6 RC2 with Wayland, at the desktop use Sleep to put the PC to
sleep
2. Wake the PC once it has gone to sleep
3. Observe task bar and desktop

OBSERVED RESULT
Taskbar and Desktop are corrupted, preventing you from using your system

EXPECTED RESULT
When resumed, there should not be corruption and it should match the state when
you put it to sleep.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Linux Kernel: 6.7.4-arch1-1
Nvidia driver version: 550.40.07

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

[kphotoalbum] [Bug 481181] Can not select images using tag with leading/trailing whitespace in the tag name

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481181

--- Comment #1 from rsquare...@proton.me ---
A better expected result: an image should always be selectable using an
assigned tag.

This is arguably a bug in the image selection logic, but is there a reason to
allow leading/trailing whitespace in a tag name?

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

[kalarm] [Bug 481166] When entering VTODOs into KALARM's ICAL calender they are ignored

2024-02-10 Thread Flossy Cat
https://bugs.kde.org/show_bug.cgi?id=481166

--- Comment #2 from Flossy Cat  ---
(In reply to David Jarvie from comment #1)
> By design, KAlarm stores all its alarms in VEVENT, and in order to provide
> all its functionality it uses quite a few custom properties in VEVENT and
> VALARM. 

Perhaps I have a wrong understanding of the function of KAlarm within the KDE
ecosystem.

I perceive it as a reminder application which would serve well – and with
better functionality
than »korganizer« (or the patch by David) ever provided – as substitute for the
notifications
(see https://bugs.kde.org/show_bug.cgi?id=481024).
(Better, namely: the preview of impending alarms, the overview over recent
alarms, command alarms, … more)

IMHO it is neither a substitute for a calendaring application nor a todo list.

What is your intended usage of KAlarm?

> Giving full support to VTODO would be outside the current scope of
> KAlarm, whose purpose is to provide reminders.

VTODOs contain VALARMs with the exact same syntax and semantics
as VEVENTs. (There are only minimal differences between VTODOs and
VEVENTs anyhow – they are practically fraternal twins. The only differences
coming readily to my mind are "transparency" and "dtend" for VEVENTs and 
"percentage completed" and "due" for VTODOs – all seemingly not used by KAlarm
anyhow.)
(see https://www.rfc-editor.org/rfc/rfc5545#section-3.6.1 and
https://www.rfc-editor.org/rfc/rfc5545#section-3.6.2)

I only suggest to honor the reminders in the VALARMs of both ICAL-entry-types
to make KAlarm an universal reminder for all ICAL-entry-types having reminders
i.e. VALARMS …

> Adding todo functionality
> would almost certainly need significant user interface changes in addition
> to logic changes.

That is not my intention at all – only reminders.

> It might be possible to add import (read-only) support for VTODO. This would
> need to convert them to VEVENT. I don't know how practical this would be,
> and I don't think the work would be justified unless there was evidence that
> people would actually use that facility. 

Trivial. The only difference between VTODO and VEVENT for the purpose of
KAlarm is, if the time period is not given via DTSTART and DURATION (identical
for both) 
but by start and end time, then for the end time
* VTODO uses DUE
* VEVENT uses DTEND 

(Actually users knowledgeable about the ICAL format have an unexpected nasty
surprise 
if KAlarm handles only alarms of VEVENTs because they are for many purposes
completely
interchangeable with VTODOs …)

> Of course, if you wanted to
> implement something yourself along these lines, I'd be happy to consider
> incorporating that into KAlarm, and could point the way to how to go about
> it.

Point me ;-)

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

[palapeli] [Bug 481175] Cannot create new puzzles

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481175

Bug Janitor Service  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

--- Comment #1 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/games/palapeli/-/merge_requests/25

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

[kphotoalbum] [Bug 481181] New: Can not select images using tag with leading/trailing whitespace in the tag name

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481181

Bug ID: 481181
   Summary: Can not select images using tag with leading/trailing
whitespace in the tag name
Classification: Applications
   Product: kphotoalbum
   Version: GIT master
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Annotation Dialog
  Assignee: kpab...@willden.org
  Reporter: rsquare...@proton.me
  Target Milestone: ---

SUMMARY
My database had a tag with an unintended trailing space character.  Clicking on
the tag showed zero thumbnails even though KPhotoalbum reported in the listview
that the tag was assigned to hundreds of images.

This is reproducible with git master.

STEPS TO REPRODUCE
1. Open the demo database, click Events and then click on the "desktop" tag. 
Four thumbnails are displayed.  
2. Select an image, open the annotation dialog, and rename the "desktop" tag to
"desktop " (with a trailing space).
3. Click home, then Events.  Note that the trailing whitespace is not obvious
in the list view.
4. Click on the "desktop " tag.  No thumbnails are displayed.

OBSERVED RESULT
The tag cannot be used to select images.

EXPECTED RESULT
The user should not be able to create a tag name with leading/trailing
whitespace.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.04.3 LTS
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Trailing whitespace is not obvious unless the tag name is selected in an edit
control.

The same issue occurs with leading whitespace in the tag name, but it is more
obvious if the tags are displayed in a list view because the tag name appears
indented.

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

[digikam] [Bug 481180] New: digikam incorrectly reads metadata field "Subject" when "HierarchicalSubject" is also present

2024-02-10 Thread fales
https://bugs.kde.org/show_bug.cgi?id=481180

Bug ID: 481180
   Summary: digikam incorrectly reads metadata field "Subject"
when "HierarchicalSubject" is also present
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Tags-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: fale...@outlook.com
  Target Milestone: ---

SUMMARY
Keywords present in "Subject" are ignored if they are part of any
"HierarchicalSubject" keyword and they are not the last part of 
"HierarchicalSubject" keyword.

STEPS TO REPRODUCE
1. Prepare a picture with the following metadata fields (all other tag related
metadata empty):
 - Subject: France, Nord, Lille
 - HierarchicalSubject: places|France|Nord|Lille 
This can be done e.g. by command:
 - exiftool -Subject="France, Nord, Lille"
-HierarchicalSubject="places|France|Nord|Lille" image.jpg
in my case the tags are generated by darktable.
2. Add the picture into digikam database and read the metadata.

OBSERVED RESULT
Only the last level of the tag "places/France/Nord/Lille" is attached to the
picture. Hence, the picture cannot be found by searching for "France" or
"Nord", it can only be found by searching for "Lille".

EXPECTED RESULT
Either both middle levels ("France", "Nord") of the tag
"places/France/Nord/Lille" attached to the picture (preferably) or
non-hierarchical tags "France" and "Nord" attached to the picture.

ADDITIONAL INFORMATION
If the field "Subject" were to contain also an additional tag, let's say
"panorama" (while "HierarchicalSubject" being the same), the tag would also be
attached to the picture. There is no reason to ignore the tags ("France",
"Nord") from the example. Moreover, when digikam itself writes the read
metadata (only the last level of tag "places/France/Nord/Lille" attached), the
result differs:
 - Subject: Lille
 - HierarchicalSubject: places|France|Nord|Lille
Notice that only "Lille" is in the "Subject".

I don't see this topic in the release notes for digikam 8.2 (no idea about
8.3).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian GNU/Linux 12
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

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

[kwin] [Bug 481177] Tabbox leave residue on screen with fall apart effect when switching virtual desktps

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481177

fanzhuyi...@gmail.com changed:

   What|Removed |Added

   Keywords|regression  |

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

[kwin] [Bug 481177] Tabbox leave residue on screen with fall apart effect when switching virtual desktps

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481177

--- Comment #1 from fanzhuyi...@gmail.com ---
Edit: I am not so sure if it is a recent regression anymore, since I built a
pretty old version of kwin and the issue still exists. Maybe I just started
noticing this recently.

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

[dolphin] [Bug 481179] dolphin doesn't update disk space

2024-02-10 Thread ksso
https://bugs.kde.org/show_bug.cgi?id=481179

ksso  changed:

   What|Removed |Added

URL||https://drive.google.com/fi
   ||le/d/1fD-4vZTi0YaLnVTKpt9-p
   ||F2lpv-g2uyD/view?usp=sharin
   ||g

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

[dolphin] [Bug 481179] New: dolphin doesn't update disk space

2024-02-10 Thread ksso
https://bugs.kde.org/show_bug.cgi?id=481179

Bug ID: 481179
   Summary: dolphin doesn't update disk space
Classification: Applications
   Product: dolphin
   Version: 23.08.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kep...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
***
When you erase files in Dolphin, the free space indicator doesn't update, as
appear on the partition manager. Need to restart to update dolphin.
***
https://drive.google.com/file/d/1fD-4vZTi0YaLnVTKpt9-pF2lpv-g2uyD/view?usp=sharing

STEPS TO REPRODUCE
1. Erase big files
2. F5 on Dolphin
3. The free space indicator is different from the partition manager.

OBSERVED RESULT
Free space not updated

EXPECTED RESULT
Real free space available

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 23.10
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-17-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 3.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HP
Product Name: HP Laptop 15-ef2xxx

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

[kwin] [Bug 481177] Tabbox leave residue on screen with fall apart effect when switching virtual desktps

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481177

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[dolphin] [Bug 481178] Dolphin displays two languages.

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481178

--- Comment #1 from gigastarcra...@proton.me ---
Created attachment 165731
  --> https://bugs.kde.org/attachment.cgi?id=165731=edit
dolphin

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

[dolphin] [Bug 481178] New: Dolphin displays two languages.

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481178

Bug ID: 481178
   Summary: Dolphin displays two languages.
Classification: Applications
   Product: dolphin
   Version: 23.08.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: gigastarcra...@proton.me
CC: kfm-de...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1.  I am not sure how to reproduce this bug. I only have more than two
languages in a keyboard layout settings but in the Region & Language I only
have English. 

OBSERVED RESULT
Two languages.
https://imgur.com/1GFaz3i

EXPECTED RESULT
Only one language displayed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Artix Linux 6.7.4 
KDE Plasma Version: 5.27.1 Wayland
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION

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

[kalarm] [Bug 481053] kalarm CLI options wrongly transfered to »--edit-new-display« and actual alarm

2024-02-10 Thread Flossy Cat
https://bugs.kde.org/show_bug.cgi?id=481053

--- Comment #7 from Flossy Cat  ---
(In reply to David Jarvie from comment #6)
> The KDE 22.12 branch was effectively closed when 23.04 was created, so I
> wouldn't be willing to apply the fix to it. 

When it is closed it is closed …

> I'm afraid the options are to
> apply a patch to the OpenSUSE repository or to wait for 23.08.5.

For this specific bug fix I can wait.
(I'm just wondering from which source OpenSUSE is pulling all the bug fixes I
regularly receive alongside the security patches …)

Thank you, again.

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

[kalarm] [Bug 481132] According documentation »kalarm« allows calendar directories where each event is a single ICS file – in practice it doesn't

2024-02-10 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=481132

David Jarvie  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/pim/
   ||kalarm/-/commit/268ecdf9300
   ||a900a6b9cd0908ae670ec342b59
   ||e9
   Version Fixed In||23.08.5

--- Comment #1 from David Jarvie  ---
The local directory calendar functionality was removed some time ago in KAlarm
version 3.0 (KDE Applications 20.08), when KAlarm ceased to use Akonadi for
calendar storage. The description of the local directory calendar has now been
removed from the documentation for KDE Gear 23.08.5 (commit
268ecdf9300a900a6b9cd0908ae670ec342b59e9) and 24.02 (commit
936f9adf949e8b273ebaadf4bb1e12ab0f945994).

Note that the link to the KAlarm documentation in your bug report actually
shows an out of date version of the documentation. The last released revision
of the documentation was for KAlarm version 3.6. I've raised a bug report
https://bugs.kde.org/show_bug.cgi?id=481176 to get the website updated.

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

[kwin] [Bug 481177] Tabbox leave residue on screen with fall apart effect when switching virtual desktps

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481177

fanzhuyi...@gmail.com changed:

   What|Removed |Added

   Keywords||regression

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

[kwin] [Bug 481177] New: Tabbox leave residue on screen with fall apart effect when switching virtual desktps

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481177

Bug ID: 481177
   Summary: Tabbox leave residue on screen with fall apart effect
when switching virtual desktps
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: effects-tabbox
  Assignee: kwin-bugs-n...@kde.org
  Reporter: fanzhuyi...@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. Create multiple virtual desktops
2. Enable fall apart window effect
3. Enable Slide effect for virtual desktop switching
4. Toggle tabbox
5. Quickly use shortcut to switch to another virtual desktop

OBSERVED RESULT
Rectangular residue in the shape of tabbox on screen

EXPECTED RESULT
No such residue.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.5.0-17-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0

ADDITIONAL INFORMATION
Seems a recent regression

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

[docs.kde.org] [Bug 481176] New: KAlarm stable documentation shows old version

2024-02-10 Thread David Jarvie
https://bugs.kde.org/show_bug.cgi?id=481176

Bug ID: 481176
   Summary: KAlarm stable documentation shows old version
Classification: Websites
   Product: docs.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: djar...@kde.org
  Target Milestone: ---

SUMMARY

The stable KAlarm documentation at
https://docs.kde.org/stable5/en/kalarm/kalarm/index.html is out of date.  It
currently shows a version from May 2022 which applied up to KDE Gear 23.04.3,
but the document was subsequently updated in the KDE Gear 23.08 release. It has
also now had another update for the 23.08.5 release.

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

[ktorrent] [Bug 481151] cannot restore ktorrent window after closing

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481151

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/network/ktorrent/-/merge_requests/111

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

[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01

2024-02-10 Thread Valter Mura
https://bugs.kde.org/show_bug.cgi?id=480704

--- Comment #21 from Valter Mura  ---
HI,
ok, the system now restarted, but returns the following error:
"Aggiornamento di 1 pacchetto non riuscito
Error while installing package: trying to overwrite
'/usr/share/locale/ar/LC_MESSAGES/libtextautocorrection.mo', which is also in
package libkf5textaddons-data 1.5.2+p22.04+vstable+git20240109.0209-0"

Now, many things don't work, for example:
- Firefox doesn't have Icon
- Widgets don't work, returning the error: "This widget was written for an
unknown older version of Plasma and is not compatible with Plasma 6. Please
contact the widget's author for an updated version.Error loading applet:
Package does not exist." (unknown widget); and "This widget was written for an
unknown older version of Plasma and is not compatible with Plasma 6. Contact
the author of the widget for an updated version." (Weather Widget and Key
State); for System Monitor widget, no sensor is available.
- Lokalize crashes; KDEsvn crashes

I attach a screenshot of my desktop

My present system:
Operating System: KDE neon Testing Edition
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.5.0-14-generic (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVE7

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

[palapeli] [Bug 481175] Cannot create new puzzles

2024-02-10 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=481175

Bug Janitor Service  changed:

   What|Removed |Added

   Keywords||qt6

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

[palapeli] [Bug 481175] New: Cannot create new puzzles

2024-02-10 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=481175

Bug ID: 481175
   Summary: Cannot create new puzzles
Classification: Applications
   Product: palapeli
   Version: 2.1.240195
  Platform: Exherbo
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: majew...@gmx.net
  Reporter: li...@bernd-steinhauser.de
CC: kde-games-b...@kde.org
  Target Milestone: ---

SUMMARY
Since I upgraded to the release candidate based on kf6, I can't create a new
puzzle. I get stuck at the screen saying "Choose a slicing method" and no
matter what I choose, the "Next" and "Finish" buttons remained deactivated.

STEPS TO REPRODUCE
1. Update to current release candidate
2. Create a new puzzle
3. Select image, provide metadata and click on next
4. Select a slicing method

OBSERVED RESULT
Can't progress/finish the creation

SOFTWARE/OS VERSIONS 
Operating System: Exherbo 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Kernel Version: 6.7.3-amdgpu (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I've verified this on my laptop, which is running RC2 on Arch Linux. This
laptop has never run Plasma 5 and especially never run palapeli before, so it
started with a clean config.

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

[parley] [Bug 469716] Parley lags when editing a list

2024-02-10 Thread Andreas Cord-Landwehr
https://bugs.kde.org/show_bug.cgi?id=469716

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #1 from Andreas Cord-Landwehr  ---
I was able to reproduce the named behavior when running in a Wayland session
(actually, only when running on Wayland an never on X11).
Can you confirm that you had a Wayland session running when you noticed this
behavior?

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

[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=457233

davidkace...@gmail.com changed:

   What|Removed |Added

 CC||davidkace...@gmail.com

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

[okular] [Bug 479141] Graphical glitches in presentation mode

2024-02-10 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=479141

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #9 from Albert Astals Cid  ---
Does the problem go away when not using wayland?

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

[systemsettings] [Bug 417615] Option to disable kdeconnect

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=417615

kimim...@posteo.net changed:

   What|Removed |Added

 CC||kimim...@posteo.net

--- Comment #22 from kimim...@posteo.net ---
I'm also in favor of an option to disable KDEConnect. It could be a simple
toggle or button on the KDEConnect setting page like with Bluetooth and the
like.

This has many benefits, including working with multi-user and immutable
systems, and preventing other annoyances (Ex. friend takes your phone from the
kitchen and starts doing things on your desktop). While some of these can be
worked around by unpairing and/or uninstalling KDEConnect, these have setup and
maintenance burdens that in my opinion shouldn't be necessary for connectivity
software like this.

As an example, Syncthing is a piece of software that someone might want running
all the time, but it can still be shutdown when needed.

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

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

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=480862

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

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

[systemsettings] [Bug 481164] After upgrading to 5.93.0, shortcuts like Ctrl+1, Ctrl+2 stopped working with numpad keys

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481164

fanzhuyi...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from fanzhuyi...@gmail.com ---
Possible duplicate of 480862. Need to test with Qt patch
https://codereview.qt-project.org/c/qt/qtwayland/+/533675.

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

[kwin] [Bug 481157] Going to window overview and listing the application name should always list installed application first, not some KDE discover store page

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481157

fanzhuyi...@gmail.com changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
  Component|Activity Switcher   |effects-overview
   Target Milestone|1.0 |---
Product|plasmashell |kwin
 CC||fanzhuyi...@gmail.com

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

[xdg-desktop-portal-kde] [Bug 480435] Remote Desktop session restore does not work after xdg-desktop-portal-kde is restarted

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=480435

unblended_icing...@simplelogin.com changed:

   What|Removed |Added

 CC|unblended_icing552@simplelo |
   |gin.com |

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

[systemsettings] [Bug 481164] After upgrading to 5.93.0, shortcuts like Ctrl+1, Ctrl+2 stopped working with numpad keys

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481164

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from fanzhuyi...@gmail.com ---
Can reproduce.

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

[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=480235

unblended_icing...@simplelogin.com changed:

   What|Removed |Added

 CC||unblended_icing552@simplelo
   ||gin.com

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

[xdg-desktop-portal-kde] [Bug 480435] Remote Desktop session restore does not work after xdg-desktop-portal-kde is restarted

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=480435

unblended_icing...@simplelogin.com changed:

   What|Removed |Added

 CC||unblended_icing552@simplelo
   ||gin.com

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

[okular] [Bug 481160] [wish] filling the fields in a pdf document without any form.

2024-02-10 Thread Philippe ROUBACH
https://bugs.kde.org/show_bug.cgi?id=481160

--- Comment #6 from Philippe ROUBACH  ---
>> FWIW the easier solution for this is go back to whoever gave you those PDF 
>> and ask them to create a better ones.

I did that many times. I helped them by supplying some kind of how-to, saying
to use LibreOffice to create pdf with form ... without any success.

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

[kwin] [Bug 481173] keyboard shortcuts don't accept all key combinations

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481173

--- Comment #2 from fanzhuyi...@gmail.com ---
In plasma 6 wayland I can correctly assign Meta as a shortcut in system
settings. But currently in system settings assigning multi-key shortcuts is not
supported, perhaps that is what you want to change?

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

[kwin] [Bug 481173] keyboard shortcuts don't accept all key combinations

2024-02-10 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=481173

fanzhuyi...@gmail.com changed:

   What|Removed |Added

 CC||fanzhuyi...@gmail.com

--- Comment #1 from fanzhuyi...@gmail.com ---
We can't do much about the Fn+Key part -- pressing the fn key does not send a
keypress to the OS (with the exception of apple macs); it just reinterprets the
key presses.

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

  1   2   3   >