[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

2023-05-17 Thread zyf0330
https://bugs.kde.org/show_bug.cgi?id=469090

--- Comment #8 from zyf0330  ---
Created attachment 159062
  --> https://bugs.kde.org/attachment.cgi?id=159062=edit
Tilix Quake monitor setting

Another thing, I have set Tilix Quake to display on Primary Monitor. And after
this problem appears, Tilix Quake window appears on laptop monitor which is set
as non-primary monitor.
And if I set it to display on Monitor 0, it still displays on laptop monitor.
If I set as Monitor 1, it displays on external primary monitor.

So I can guess that when this problem occurs, monitor 0 and 1 is swapped.

This is config in the .config/plasmashellrc.
```
[ScreenConnectors]
0=HDMI-A-0
1=eDP
```

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

[okular] [Bug 469882] The pdf file does not open and closes with an error.

2023-05-17 Thread ilirius
https://bugs.kde.org/show_bug.cgi?id=469882

--- Comment #6 from ilirius  ---
(In reply to ilirius from comment #5)
> (In reply to Sune Vuorela from comment #4)
> > Thanks. Crash happens in poppler. Merge-request submitted. 
> > 
> > Neither the current NSS backend nor the upcoming GPG backend supports GOST
> > as a hash algorithm though, so neither can validate the signature. I also
> > don't see it mentioned in 
> > 
> > GOST also isn't mentioned in neither ISO 32000-2:2020, nor in the extenisons
> > adding more hash algorithms.
> 
I tried to open libreoffice, it opened normally but displayed the message "The
document signature is invalid." Maybe it's worth adding this to Okular?

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

[okular] [Bug 469882] The pdf file does not open and closes with an error.

2023-05-17 Thread ilirius
https://bugs.kde.org/show_bug.cgi?id=469882

--- Comment #5 from ilirius  ---
(In reply to Sune Vuorela from comment #4)
> Thanks. Crash happens in poppler. Merge-request submitted. 
> 
> Neither the current NSS backend nor the upcoming GPG backend supports GOST
> as a hash algorithm though, so neither can validate the signature. I also
> don't see it mentioned in 
> 
> GOST also isn't mentioned in neither ISO 32000-2:2020, nor in the extenisons
> adding more hash algorithms.

Я пробовал открыть libreoffice, он открыл нормально но вывел сообщение "Подпись
документа недействительна." Может быть стоит такое добавить и в Okular?

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

[plasmashell] [Bug 469090] After screen is dim or switch off, primary becomes laptop internal monitor.

2023-05-17 Thread zyf0330
https://bugs.kde.org/show_bug.cgi?id=469090

--- Comment #7 from zyf0330  ---
This is xrandr output
```
Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 16384 x 16384
eDP connected primary 1920x1200+0+120 (normal left inverted right x axis y
axis) 301mm x 188mm
   2880x1800 90.01 +
   1920x1200 90.01* 
   1920x1080 90.01  
   1600x1200 90.01  
   1680x1050 90.01  
   1280x1024 90.01  
   1440x900  90.01  
   1280x800  90.01  
   1280x720  90.01  
   1024x768  90.01  
   800x600   90.01  
   640x480   90.01  
HDMI-A-0 connected 2560x1440+1920+0 (normal left inverted right x axis y axis)
597mm x 336mm
   2560x1440 59.95*+
   1920x1200 59.95  
   1920x1080 60.0050.0059.94  
   1600x1200 59.95  
   1280x1440 59.91  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1440x900  59.90  
   1280x960  60.00  
   1280x800  59.95  
   1280x720  60.0050.0059.94  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0072.8166.6760.0059.94  
   720x400   70.08  
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
DisplayPort-5 disconnected (normal left inverted right x axis y axis)
DisplayPort-6 disconnected (normal left inverted right x axis y axis)
```

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

[plasmashell] [Bug 423689] Add back split graphs and values

2023-05-17 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=423689

--- Comment #3 from Mihai Sorin Dobrescu  ---
Created attachment 159061
  --> https://bugs.kde.org/attachment.cgi?id=159061=edit
Individual Core Usage widget set as line chart

To illustrate my problem is the current Individual Core Usage widget set as
line chart.
There is no individual line chart here separated as it was before. Now are all
cores charts superimposed.
May be spectacular for a person that want's to show up a desktop, but does not
help much.
I know, I may be like a car driver that refuses automatic gear box for a manual
one, but I need that feedback.
I suspect it's just a display style definition to be added, but I am not sure
yet.
Why not having that original layout again?

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

[okular] [Bug 469927] New: Please provide a way to rotate individual pages clockwise or counterclockwise

2023-05-17 Thread Steve Kelem
https://bugs.kde.org/show_bug.cgi?id=469927

Bug ID: 469927
   Summary: Please provide a way to rotate individual pages
clockwise or counterclockwise
Classification: Applications
   Product: okular
   Version: 22.12.3
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: st...@kelem.net
  Target Milestone: ---

SUMMARY
Some PDF documents have a few pages oriented differently, e.g., a landscape
page rotated so that it will print on a piece of paper in portrait mode.
Sometimes pages are upside down.

Please provide a way to display a page rotated. I would like to be able to
rotate a single page CCW or CW multiple times, until the page is right-side up.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
The pages are displayed the way that they were set up when they were formatted.
When printed, the page can be turned physically. However, the displayed image
of a page can't be rotated, making it difficult to read.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 6.2.0-20-generic
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 436056] Separate System Monitor widgets in sensor-related and process/application-related

2023-05-17 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=436056

--- Comment #5 from Mihai Sorin Dobrescu  ---
If a user defines some custom sensor setup for a sensors widget, it is OK to
have all the display styles available, as the user can use anything that's
needed.

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

[plasmashell] [Bug 436056] Separate System Monitor widgets in sensor-related and process/application-related

2023-05-17 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=436056

--- Comment #4 from Mihai Sorin Dobrescu  ---
Created attachment 159060
  --> https://bugs.kde.org/attachment.cgi?id=159060=edit
Individual Core Usage widget set as Grid

An Individual Core Usage widget set as Grid makes sense, there are cores and
their load.

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

[plasmashell] [Bug 436056] Separate System Monitor widgets in sensor-related and process/application-related

2023-05-17 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=436056

--- Comment #3 from Mihai Sorin Dobrescu  ---
Created attachment 159059
  --> https://bugs.kde.org/attachment.cgi?id=159059=edit
Individual Core Usage widget as Application Table

Hi, I can't easily reproduce all the cases because sensors list it's always
broken and does not list all the sensors. To illustrate what I mean, at a basic
level, I have added an Individual Core Usage widget and have set its display
style as Application Table.
Application table is useful, but not for this use case. I mean, what does CPU's
cores usage have to do with this Application Table style? It does not list
which app uses which core and how much of that core (or cores). It's nice, but
make no sense to me.

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

[okular] [Bug 468647] Character not printed correctly

2023-05-17 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=468647

Martin  changed:

   What|Removed |Added

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

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

[okular] [Bug 468647] Character not printed correctly

2023-05-17 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=468647

--- Comment #3 from Martin  ---
No exactly. If you go on the homepage and dowmload the paper and open it with
firefox, the symbols are shown correctly. Just when you open in okular it is
not correct

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

[plasmashell] [Bug 469894] [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet

2023-05-17 Thread Samuel
https://bugs.kde.org/show_bug.cgi?id=469894

--- Comment #3 from Samuel  ---
Created attachment 159058
  --> https://bugs.kde.org/attachment.cgi?id=159058=edit
Journal log of plasmashell when the crash occured

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

[plasmashell] [Bug 469894] [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet

2023-05-17 Thread Samuel
https://bugs.kde.org/show_bug.cgi?id=469894

Samuel  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |samping...@gmail.com
 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #2 from Samuel  ---
Created attachment 159057
  --> https://bugs.kde.org/attachment.cgi?id=159057=edit
GDB Log of reproduced bug in plasmashell

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

[rkward] [Bug 469926] RKWard doesn't start anymore

2023-05-17 Thread Nuno Gomes
https://bugs.kde.org/show_bug.cgi?id=469926

Nuno Gomes  changed:

   What|Removed |Added

Summary|The program doesn't start   |RKWard doesn't start
   |anymore |anymore

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

[rkward] [Bug 469926] New: The program doesn't start anymore

2023-05-17 Thread Nuno Gomes
https://bugs.kde.org/show_bug.cgi?id=469926

Bug ID: 469926
   Summary: The program doesn't start anymore
Classification: Applications
   Product: rkward
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: rkward-de...@kde.org
  Reporter: nunogomes.pt+...@gmail.com
  Target Milestone: ---

SUMMARY
I was able to start the program after installing it. I took the opportunity to
configure it according to my needs. However, when I tried to restart it, it
didn't work anymore.
When I try to run it from the terminal, I get the following error messages:

```shell
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
zsh: segmentation fault (core dumped)  rkward
```
The program doesn't start even if I delete the .rkward configuration folder and

STEPS TO REPRODUCE
1. Install RKWard
2. Configure RKWard on first start
3. Relaunch the program

OBSERVED RESULT
RKWard won't start even if I delete the `.rkward/` configuration folder and
reinstall the program.

EXPECTED RESULT
RKWard starts with the new configuration.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: RebornOS Linux x86_64 / KDE Plasma 5.27.5
(available in About System)
KDE Plasma Version: KDE Plasma 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
RKWard version: 0.7.5
R version: 4.3.0
RKward and R were installed via pacman; KDE was installed along with the
RebornOS distribution.

I ran into the problem after configuring RKWard using the settings menu and
restarting the program.
I reinstalled RKWard and deleted the .rkward configuration folder, but the
problem persists.

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

[kalendar] [Bug 469065] Kalendar does not start

2023-05-17 Thread Carlos
https://bugs.kde.org/show_bug.cgi?id=469065

Carlos  changed:

   What|Removed |Added

Version|unspecified |23.04.1

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

[digikam] [Bug 469595] digikam 8.0.0 from fedora repository and also local build crash on startup

2023-05-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469595

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

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG
   Version Fixed In||8.1.0

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

[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen

2023-05-17 Thread Prajna Sariputra
https://bugs.kde.org/show_bug.cgi?id=469777

--- Comment #1 from Prajna Sariputra  ---
> I guess that MR might just be exacerbating an existing issue though, I have 
> been getting `kwin_screencast: Dropping a screencast frame because the 
> compositor is slow` messages appear repeatedly in journalctl anytime a 
> screencast session is active, but with 5.27.5 as well as with 5.27.4.1 with 
> that MR applied I get way more of those (from like 20 per second to well over 
> 1000 per second).

Correction: The warning messages I was getting prior to 5.27.5 is actually
`Dropping a screencast cursor update because the compositor is slow`, so that
part isn't as much "more warning messages than before" as it is "new warning
messages". Looking through old logs I did still see the screencast frame drop
message, but it was only occasionally occurring back then.

Also, out of the 3 commits introduced in the problematic MR I found that the
issue is specifically caused by commit 226d8c0a3b464f8870c45bfe5079f042a3cd5d67
(screencast: Ensure we respect the negotiated framerate), reverting it on top
of 5.27.5 drops KWin's CPU usage back to what it was before.

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

[frameworks-kio] [Bug 468516] When installed from Fedora distro packages, Peek and Gedit don't launch via GUI methods ("The name is not activatable" error)

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=468516

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kate] [Bug 467168] KWrite forgets file history

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=467168

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[krita] [Bug 465714] Assertion failure when attempting to open a PSD

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=465714

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.

[krita] [Bug 464999] When I am using the software it will randomly crash and not allow me to do anything. I will have to report the whole system. Its does it three to four time every day.

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=464999

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.

[krita] [Bug 461554] Copying selection sometimes causes Krita lock-up and enter infinite loop writing to krita.log until the disk is full

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=461554

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.

[okular] [Bug 468647] Character not printed correctly

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=468647

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

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

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

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

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

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

[Spectacle] [Bug 425715] Rectangular Region: Spectacle sometimes hides window, but i can't select a region, when Compositor is suspended.

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=425715

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

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

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

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

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

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

[kig] [Bug 467718] cursor in construction is excruciatingly slow

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=467718

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

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

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

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

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

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

[kwin] [Bug 430440] The "Show in Activities" menu does not work as expected

2023-05-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=430440

i...@xianwang.io changed:

   What|Removed |Added

 CC||i...@xianwang.io

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

[krita] [Bug 469925] New: The cursor has an offset on one specific file, but it works fine on all of the others

2023-05-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469925

Bug ID: 469925
   Summary: The cursor has an offset on one specific file, but it
works fine on all of the others
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: ajmason...@outlook.com
  Target Milestone: ---

Created attachment 159056
  --> https://bugs.kde.org/attachment.cgi?id=159056=edit
Cursor lags in one specific file

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

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION
?

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

[plasmashell] [Bug 336990] Chromium and Firefox does not remember their virtual desktops on session restore

2023-05-17 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=336990

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[kwin] [Bug 469924] New: Kwin crash during kscreenlocker issue

2023-05-17 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=469924

Bug ID: 469924
   Summary: Kwin crash during kscreenlocker issue
Classification: Plasma
   Product: kwin
   Version: 5.27.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: justin.zo...@gmail.com
  Target Milestone: ---

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

This is related I believe to the kscreenlocker issue where the device is locked
and the user sees the screen as shown in the screenshot where the user must go
to a TTY and unlock using loginctl.

Plasma 5.27.4 and KF5.105.0

   PID: 844 (kwin_wayland)
   UID: 1000 (user)
   GID: 1000 (user)
Signal: 11 (SEGV)
 Timestamp: Wed 2023-05-17 12:00:20 ACST (53 years 4 months left)
  Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0
--xwayland-fd 8 --xwayland-fd 9 --xwayland-display :0 --xwayland-xauthority
/run/user/1000/xauth_SssThN --xwayland
Executable: /usr/bin/kwin_wayland
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service
  Unit: user@1000.service
 User Unit: plasma-kwin_wayland.service
 Slice: user-1000.slice
 Owner UID: 1000 (user)
   Boot ID: 5491b35ce8804723aaa9de89f1579622
Machine ID: 348a8db330c44c9286295da83c34c2e2
  Hostname: op6-fedora
   Storage:
/var/lib/systemd/coredump/core.kwin_wayland.1000.5491b35ce8804723aaa9de89f1579622.844.168429062000.zst
(present)
  Size on Disk: 5.7M
   Package: kwin/5.27.4.1-1.fc38
  build-id: 0ffa87fdf9cd295f4c62c372996c4a19d39c0ea5
   Message: Process 844 (kwin_wayland) of user 1000 dumped core.

Module libpipewire-module-session-manager.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libpipewire-module-metadata.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libpipewire-module-adapter.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libpipewire-module-client-device.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libpipewire-module-client-node.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libpipewire-module-protocol-native.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libspa-dbus.so from rpm pipewire-0.3.70-1.fc38.aarch64
Module libspa-journal.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libspa-support.so from rpm
pipewire-0.3.70-1.fc38.aarch64
Module libKWinNightColorPlugin.so from rpm
kwin-5.27.4.1-1.fc38.aarch64
Module krunnerintegration.so from rpm
kwin-5.27.4.1-1.fc38.aarch64
Module colordintegration.so from rpm
kwin-5.27.4.1-1.fc38.aarch64
Module MouseButtonToKeyPlugin.so from rpm
kwin-5.27.4.1-1.fc38.aarch64
Module libxshmfence.so.1 from rpm
libxshmfence-1.3-12.fc38.aarch64
Module libxcb-dri2.so.0 from rpm libxcb-1.13.1-11.fc38.aarch64
Module libEGL_mesa.so.0 from rpm mesa-23.0.3-3.fc38.aarch64
Module libtinfo.so.6 from rpm
ncurses-6.4-3.20230114.fc38.aarch64
Module libedit.so.0 from rpm
libedit-3.1-45.20221030cvs.fc38.aarch64
Module libxcb-dri3.so.0 from rpm libxcb-1.13.1-11.fc38.aarch64
Module libdrm_nouveau.so.2 from rpm
libdrm-2.4.114-2.fc38.aarch64
Module libdrm_amdgpu.so.1 from rpm
libdrm-2.4.114-2.fc38.aarch64
Module libelf.so.1 from rpm elfutils-0.189-1.fc38.aarch64
Module libdrm_radeon.so.1 from rpm
libdrm-2.4.114-2.fc38.aarch64
Module msm_dri.so from rpm mesa-23.0.3-3.fc38.aarch64
Module libglapi.so.0 from rpm mesa-23.0.3-3.fc38.aarch64
Module libKF5Style.so.5 from rpm
kf5-frameworkintegration-5.105.0-3.fc38.aarch64
Module libbreezecommon5.so.5 from rpm
plasma-breeze-5.27.4-1.fc38.aarch64
Module libKF5Kirigami2.so.5 from rpm
kf5-kirigami2-5.105.0-1.fc38.aarch64
Module breeze.so from rpm plasma-breeze-5.27.4-1.fc38.aarch64
Module libusbmuxd-2.0.so.6 from rpm
libusbmuxd-2.0.2-8.fc38.aarch64
Module libplist-2.0.so.3 from rpm libplist-2.2.0-9.fc38.aarch64
Module libimobiledevice-1.0.so.6 from rpm
libimobiledevice-1.3.0-8.fc38.aarch64
Module libQt5QuickTemplates2.so.5 from rpm
qt5-qtquickcontrols2-5.15.9-1.fc38.aarch64
Module libXfixes.so.3 from rpm libXfixes-6.0.0-5.fc38.aarch64
Module libXrender.so.1 from rpm
libXrender-0.9.11-2.fc38.aarch64
Module libKF5Solid.so.5 from rpm
kf5-solid-5.105.0-1.fc38.aarch64
Module 

[kdenlive] [Bug 469922] Slide (composition) clips with duration less than 1 second copied from a video track only appear two tracks above

2023-05-17 Thread Gabriel Pinzón
https://bugs.kde.org/show_bug.cgi?id=469922

--- Comment #1 from Gabriel Pinzón  ---
Created attachment 159054
  --> https://bugs.kde.org/attachment.cgi?id=159054=edit
A .kdenlive filewith the problem

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

[kdiff3] [Bug 469923] Kdiff3 crashes when the compared directories contain symlinks with nonexistent targets

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469923

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kdiff3] [Bug 469923] New: Kdiff3 crashes when the compared directories contain symlinks with nonexistent targets

2023-05-17 Thread Jiri Palecek
https://bugs.kde.org/show_bug.cgi?id=469923

Bug ID: 469923
   Summary: Kdiff3 crashes when the compared directories contain
symlinks with nonexistent targets
Classification: Applications
   Product: kdiff3
   Version: 1.10.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: jpale...@web.de
  Target Milestone: ---

Application: kdiff3 (1.9.70 (64 bit))

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-6-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
Hello

when I tried to compare two directories, kdiff 3 crashed. From the bactrace and
inspection under gdb, I can see this is because it tripped on a file which is a
symlink with nonexistant target. QFileInfo can't provide a modification time in
that case, therefore the modification time is invalid, which causes an assert
failure.

The crash can be reproduced every time.

-- Backtrace:
Application: KDiff3 (kdiff3), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#5  0x7ff257ea9d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#6  0x7ff257e5aef2 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#7  0x7ff257e45472 in __GI_abort () at ./stdlib/abort.c:79
#8  0x7ff257e45395 in __assert_fail_base (fmt=0x7ff2515db91f "%s%s%s:%u:
%s%sP\305\231edpoklad \342\200\236%s\342\200\234 nespln\304\233n.\n%n",
assertion=assertion@entry=0x55f87554a7a8 "!m_modificationTime.isNull()",
file=file@entry=0x55f87554a728 "./src/fileaccess.cpp", line=line@entry=762,
function=function@entry=0x55f87554aa38 "QDateTime FileAccess::lastModified()
const") at ./assert/assert.c:92
#9  0x7ff257e53df2 in __GI___assert_fail (assertion=0x55f87554a7a8
"!m_modificationTime.isNull()", file=0x55f87554a728 "./src/fileaccess.cpp",
line=762, function=0x55f87554aa38 "QDateTime FileAccess::lastModified() const")
at ./assert/assert.c:101
#10 0x55f8754d41c0 in FileAccess::lastModified (this=) at
./src/fileaccess.cpp:762
#11 0x55f875510182 in MergeFileInfos::compareFilesAndCalcAges
(this=this@entry=0x55f87cff1aa0, errors=..., pOptions=..., pDMW=0x55f87757aaa0)
at ./src/MergeFileInfos.cpp:192
#12 0x55f87546e4d0 in
DirectoryMergeWindow::DirectoryMergeWindowPrivate::prepareListView
(this=this@entry=0x55f8775bcc80, pp=...) at ./src/directorymergewindow.cpp:1331
#13 0x55f875471fbb in
DirectoryMergeWindow::DirectoryMergeWindowPrivate::init (this=0x55f8775bcc80,
bDirectoryMerge=, bReload=) at
./src/directorymergewindow.cpp:951
#14 0x55f875472ee0 in DirectoryMergeWindow::init (this=,
bDirectoryMerge=, bReload=) at
./src/directorymergewindow.cpp:736
#15 0x55f875488d59 in KDiff3App::doDirectoryCompare
(this=this@entry=0x55f8772d05e0,
bCreateNewInstance=bCreateNewInstance@entry=false) at ./src/pdiff.cpp:1627
#16 0x55f87545da3f in KDiff3App::completeInit (this=0x55f8772d05e0,
fn1=..., fn2=..., fn3=...) at ./src/kdiff3.cpp:432
#17 0x55f87544fda8 in KDiff3Shell::KDiff3Shell (this=0x55f876f6a410,
bCompleteInit=, __in_chrg=, __vtt_parm=) at ./src/kdiff3_shell.cpp:60
#18 0x55f8754447bb in main (argc=, argv=) at
./src/main.cpp:197
[Inferior 1 (process 78517) detached]

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

[Haruna] [Bug 441256] Feature request: switch to force single instance

2023-05-17 Thread freeze_ball
https://bugs.kde.org/show_bug.cgi?id=441256

freeze_ball  changed:

   What|Removed |Added

 CC||freezeb...@gmail.com

--- Comment #6 from freeze_ball  ---
Bumping the request as it is the only thing stopping me to switching to Haruna.

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

[plasmashell] [Bug 449682] hp-systray does not restart on logging back in

2023-05-17 Thread Andrew Udvare
https://bugs.kde.org/show_bug.cgi?id=449682

--- Comment #1 from Andrew Udvare  ---
Since writing this bug I installed Plasma on another machine from scratch and
hp-systray restarts properly on that machine. Still does not restart on the
machine I originally reported this bug on.

I do not want to migrate to a new profile.

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

[kdenlive] [Bug 469912] Excess line breaks in title clips

2023-05-17 Thread Gabriel Pinzón
https://bugs.kde.org/show_bug.cgi?id=469912

Gabriel Pinzón  changed:

   What|Removed |Added

   Platform|Other   |Microsoft Windows

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

[kdenlive] [Bug 469922] Slide (composition) clips with duration less than 1 second copied from a video track only appear two tracks above

2023-05-17 Thread Gabriel Pinzón
https://bugs.kde.org/show_bug.cgi?id=469922

Gabriel Pinzón  changed:

   What|Removed |Added

   Platform|Other   |Microsoft Windows
 OS|Other   |Microsoft Windows

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

[kdenlive] [Bug 469922] New: Slide (composition) clips with duration less than 1 second copied from a video track only appear two tracks above

2023-05-17 Thread Gabriel Pinzón
https://bugs.kde.org/show_bug.cgi?id=469922

Bug ID: 469922
   Summary: Slide (composition) clips with duration less than 1
second copied from a video track only appear two
tracks above
Classification: Applications
   Product: kdenlive
   Version: 23.04.1
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: j...@kdenlive.org
  Reporter: g...@yahoo.com
  Target Milestone: ---

Created attachment 159053
  --> https://bugs.kde.org/attachment.cgi?id=159053=edit
Screenshot with the error message after trying to paste a preexisting
les-than-1-second slide clip

Pasting a preexisting less-than-1-sec duration Slide clip from a video track
appears only on the second video track above it regardless of the track you
selected to want the clip to be copied, and if such a clip is copied from one
of the two upper tracks, cannot be pasted, a "not enough tracks to paste
clipboard" error message is shown.


STEPS TO REPRODUCE
1. Open a .kdenlive file that alreaady had a slide clip with duration inferior
to 1 second.
2. Select and copy any such slide clip.
3. select "Paste" onto any video track.

OBSERVED RESULT
The copied clip appears pasted on the second video track above the one where
the clip is copied, or a "not enough tracks to paste clipboard" error message
appears if there are one or no video tracks above the one where the clip was
copied.

EXPECTED RESULT
The clip appearing pasted on the selected video track.

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
MLT version: 7.15.0

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

[Haruna] [Bug 469921] New: [Feature Request] Mobile device support

2023-05-17 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=469921

Bug ID: 469921
   Summary: [Feature Request] Mobile device support
Classification: Applications
   Product: Haruna
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: justin.zo...@gmail.com
  Target Milestone: ---

I have tested it on my Fedora Linux Plasma Mobile phone and while it works and
plays the interface gets cut off for obvious reasons.

As this is already written in QML hopefully this isn't an enormous task.

If you want help to test this let me know I have a device I can test on with
nightly builds of the flatpak, etc.

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

[Haruna] [Bug 469457] Media from a network folder won't open.

2023-05-17 Thread Grzesiek11
https://bugs.kde.org/show_bug.cgi?id=469457

Grzesiek11  changed:

   What|Removed |Added

 CC||grzesie...@stary.pc.pl

--- Comment #3 from Grzesiek11  ---
I am having the same issue on Debian Sid, Haruna 0.10.3.

You can work around it by copying the desktop file for Haruna
(/usr/share/applications/org.kde.haruna.desktop in Debian, probably the same
for Ubuntu) to ~/.local/share/applications, then replacing `%u` in the `Exec`
key with `%f`:
> Exec=haruna %f
This tells Dolphin Haruna can only open local files, thus forcing the use of
KIO FUSE when opening files with it.

In general, KIO FUSE should not be required at all to use Haruna or other KDE
tools, since they implement support for KIO itself, so this is a deeper issue.
However, forcing it to use KIO FUSE is a way to get this working for now.

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

[kwin] [Bug 445338] Visual glitch in form of narrow horizontal stripes across animated parts of the screen

2023-05-17 Thread Andrei Rybak
https://bugs.kde.org/show_bug.cgi?id=445338

Andrei Rybak  changed:

   What|Removed |Added

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

--- Comment #1 from Andrei Rybak  ---
Since 2021, I have

1. upgraded up to KDE 5.27.5.
2. changed my V-sync settings
3. upgraded my monitor

I haven't been able to reproduce the bug, so there's no sense in keeping this
bug open.

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

[neon] [Bug 469920] New: KFrameworks is not updated since long time

2023-05-17 Thread Piotr Mierzwinski
https://bugs.kde.org/show_bug.cgi?id=469920

Bug ID: 469920
   Summary: KFrameworks is not updated since long time
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY
Since some time, I suppose since decision to transition to Qt6 (master in git
went to Qt6), I observe that distribution I use, "Neon Unstable Edition"
doesn't receive any update related with KDE software. I think this is because
Qt6 port of KDE software is not usable yet to daily use. Anyway my version
KFrameworks stuck with 5.104, whereas one was released version 5.106 and I
think it is available for Plasma 5, so for example we can find it in Arch
Linux. I wonder if it is possible to update it to recent?
Maybe I need to switch repositories to stable edition?

OBSERVED RESULT
Missing updates

EXPECTED RESULT
Update, at least KFrameworks.

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

ADDITIONAL INFORMATION
KDE Neon Unstable Edition

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

[kwin] [Bug 469558] Wayland suffers from high CPU usage while doing trivial tasks

2023-05-17 Thread medin
https://bugs.kde.org/show_bug.cgi?id=469558

--- Comment #11 from medin  ---
(In reply to Zamundaaa from comment #10)
> Okay, so udev events triggering stuff in KWin can be ruled out. Can you try
> putting
> > KWIN_DRM_PREFER_COLOR_DEPTH=24
> and
> >  KWIN_DRM_USE_MODIFIERS=0
> and
> > KWIN_DRM_NO_AMS=1
> into /etc/environment and see if that makes a difference? Use only one at a
> time, and reboot after changing it


The 3 parameters cause close CPU usage (from 12% to 25%) with simply basic
tasks like passing the mouse over panel items, displaying tooltips and
thumbnails and opening/closing kickoff. But "KWIN_DRM_NO_AMS=1" has not great
but a little better result compared to the two others. And the most noticeable
is that setting "KWIN_DRM_NO_AMS=1" helped greatly in fixing the mouse laggy
movements and improved a lot its pointer precision while moving and clicking.

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

[Spectacle] [Bug 469919] Spectacle: crash on second launch after pressing Enter in text annotation tool

2023-05-17 Thread Andrei Rybak
https://bugs.kde.org/show_bug.cgi?id=469919

--- Comment #1 from Andrei Rybak  ---
Created attachment 159052
  --> https://bugs.kde.org/attachment.cgi?id=159052=edit
Screen recording of the OBSERVED RESULT

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

[Spectacle] [Bug 469919] New: Spectacle: crash on second launch after pressing Enter in text annotation tool

2023-05-17 Thread Andrei Rybak
https://bugs.kde.org/show_bug.cgi?id=469919

Bug ID: 469919
   Summary: Spectacle: crash on second launch after pressing Enter
in text annotation tool
Classification: Applications
   Product: Spectacle
   Version: 23.04.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: rybak@gmail.com
CC: k...@david-redondo.de
  Target Milestone: ---

Application: spectacle (23.04.1)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 5.19.0-41-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
SUMMARY
If a user closes Spectacle by pressing Enter, Shift+Enter, or Ctrl+Enter, the
application closes and notification "A screenshot was saved to your clipboard"
appears. However, if Enter, Shift+Enter, or Ctrl+Enter was pressed during text
input, then the next launch of Spectacle crashes.


STEPS TO REPRODUCE
1. Launch "Capture Rectangular Region" (default shortcut is Meta+Shift+Print)
2. Click on the button for the "Text" annotation tool
3. Click somewhere to start the "Text" annotation tool
4. Press button "Enter" on the keyboard (or Shift+Enter, or Ctrl+Enter)
5. Launch "Capture Rectangular Region" a second time

OBSERVED RESULT
After step 3, notification "A screenshot was saved to your clipboard" appears.
After step 5, notification about Spectacle crashing appears.

I will also attach a screen recording demostrating the crash.

EXPECTED RESULT
The crash after step 5 shouldn't happen. Maybe the behavior after step 4 should
be changed as well (e.g. to just close the text input instead of closing
Spectacle).

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

The crash can be reproduced every time.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x560d82653a1f in SelectedActionWrapper::setEditAction
(this=0x560d83da1c50, action=0x0) at
./src/Gui/Annotations/AnnotationDocument.cpp:561
#5  0x560d8265a7b4 in AnnotationDocument::deselectAction
(this=0x560d83dd0c60) at ./src/Gui/Annotations/AnnotationDocument.cpp:1436
#6  AnnotationDocument::clearAnnotations (this=0x560d83dd0c60) at
./src/Gui/Annotations/AnnotationDocument.cpp:928
#7  0x560d8264a201 in AnnotationDocument::clear (this=0x560d83dd0c60) at
./src/Gui/Annotations/AnnotationDocument.cpp:842
#8  operator() (screenImages=..., __closure=0x560d83dd9330) at
./src/SpectacleCore.cpp:129
#9  QtPrivate::FunctorCall, QtPrivate::List&>, void,
SpectacleCore::SpectacleCore(QObject*)::&)>
>::call (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#10 QtPrivate::Functor&)>, 1>::call const&>,
void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#11
QtPrivate::QFunctorSlotObject&)>, 1, QtPrivate::List&>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x560d83dd9320, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#12 0x7fb22e8f41e4 in QtPrivate::QSlotObjectBase::call (a=0x7fffea53c7c0,
r=0x7fffea53cd20, this=0x560d83dd9320) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x560d83da1bf0, signal_index=6,
argv=0x7fffea53c7c0) at kernel/qobject.cpp:3923
#14 0x7fb22e8ed287 in QMetaObject::activate
(sender=sender@entry=0x560d83da1bf0, m=m@entry=0x560d826b2640
, local_signal_index=local_signal_index@entry=3,
argv=argv@entry=0x7fffea53c7c0) at kernel/qobject.cpp:3983
#15 0x560d82670917 in Platform::newScreensScreenshotTaken (_t1=...,
this=0x560d83da1bf0) at
./obj-x86_64-linux-gnu/src/spectacle_autogen/UWYFJWVAJO/moc_Platform.cpp:298
#16 PlatformXcb::doGrabNow (this=0x560d83da1bf0, theGrabMode=,
theIncludePointer=, theIncludeDecorations=) at
./src/Platforms/PlatformXcb.cpp:713
#17 0x7fb22e8f8306 in QtPrivate::QSlotObjectBase::call (a=0x7fffea53c830,
r=, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 QSingleShotTimer::timerEvent (this=0x560d85b8f2b0) at kernel/qtimer.cpp:320
#19 0x7fb22e8e9b0f in QObject::event (this=0x560d85b8f2b0,
e=0x7fffea53c9a0) at kernel/qobject.cpp:1369
#20 0x7fb23016c793 in QApplicationPrivate::notify_helper (this=, receiver=0x560d85b8f2b0, e=0x7fffea53c9a0) at
kernel/qapplication.cpp:3640
#21 0x7fb22e8bc18a in QCoreApplication::notifyInternal2
(receiver=0x560d85b8f2b0, 

[krita] [Bug 469885] The lasso is not normal

2023-05-17 Thread vanyossi
https://bugs.kde.org/show_bug.cgi?id=469885

vanyossi  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |NOT A BUG

--- Comment #4 from vanyossi  ---
This is normal when you have "Canvas Graphics Acceleration" turned off. Please
review your Display settings
https://docs.krita.org/en/reference_manual/preferences/display_settings.html
and make sure everything is set as recommended. The GPU reported by the system
capable of using canvas acceleration.

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

[dolphin] [Bug 469918] New: Properties window: Move tags from 'Details' to 'General'

2023-05-17 Thread logicalwillow
https://bugs.kde.org/show_bug.cgi?id=469918

Bug ID: 469918
   Summary: Properties window: Move tags from 'Details' to
'General'
Classification: Applications
   Product: dolphin
   Version: 23.04.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: robloka...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 159051
  --> https://bugs.kde.org/attachment.cgi?id=159051=edit
Screenshot of the tags section in the details tab

The details tab has a *lot* of information, and it's easy for the tags to get
buried there. I think tags are a pretty important feature, so they should be in
the first tab people see when they open the properties window.

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

[frameworks-baloo] [Bug 466916] baloo_file_extractor crashes and the coredump take too much space

2023-05-17 Thread bachirgiga
https://bugs.kde.org/show_bug.cgi?id=466916

--- Comment #5 from bachirg...@gmail.com  ---
It is (In reply to tagwerk19 from comment #2)
> Possible that this is fixed with Frameworks 5.104 (Bug 465801)

It is indeed fixed (I mean it's an old report, but it seems like the bug is not
there since this version)

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

[XWaylandVideoBridge] [Bug 469917] New: XWaylandVideoBridge launches four instances at start

2023-05-17 Thread bachirgiga
https://bugs.kde.org/show_bug.cgi?id=469917

Bug ID: 469917
   Summary: XWaylandVideoBridge launches four instances at start
Classification: Applications
   Product: XWaylandVideoBridge
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bachirg...@gmail.com
CC: aleix...@kde.org, k...@davidedmundson.co.uk
  Target Milestone: ---

SUMMARY
4 instances are launched instead of only one (which leads to problem when
sharing)

STEPS TO REPRODUCE
1. Boot computer
2. 4 instances are visible in the system tray and in htop
3. Try to share a screen
4. 4 windows pop up

OBSERVED RESULT


EXPECTED RESULT
Only one instances is started automatically

SOFTWARE/OS VERSIONS 
Linux: 6.3.2-arch1-1
(available in About System)
KDE Plasma Version: 5.106.0
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
Note that the software was installed through the AUR
(if you are unfamiliar with it, just know that the following bash script
(https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=xwaylandvideobridge-bin)
was run to build and install the program (it repacks the flatpak into a regular
arch package basically))

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

[plasmashell] [Bug 469916] New: Env variables field is overwriting program and arguments fields

2023-05-17 Thread Łukasz Zając
https://bugs.kde.org/show_bug.cgi?id=469916

Bug ID: 469916
   Summary: Env variables field is overwriting program and
arguments fields
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: plasma-b...@kde.org
  Reporter: s...@rbtv.pl
  Target Milestone: 1.0

Created attachment 159050
  --> https://bugs.kde.org/attachment.cgi?id=159050=edit
video showcasing issue

STEPS TO REPRODUCE
1.  right click on app to enter properties
2.  In application tab, put some env variables, save, close

OBSERVED RESULT
App will no longer run because If You open properties again, You will notice
first env variable will move to program field and the rest to arguments field.

EXPECTED RESULT
env variables stay in the field and not overwrite the rest of fields.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

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

[krunner] [Bug 469769] Non-ideal results with two-character search for "te"

2023-05-17 Thread popov895
https://bugs.kde.org/show_bug.cgi?id=469769

--- Comment #7 from popov895  ---
Can we add some configuration UI so that the user can select the desktop entry
keys that should be used when searching for apps?

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

[tellico] [Bug 467378] Images can no longer be opened

2023-05-17 Thread Robby Stephenson
https://bugs.kde.org/show_bug.cgi?id=467378

Robby Stephenson  changed:

   What|Removed |Added

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

--- Comment #3 from Robby Stephenson  ---
Since this is specific to Flatpak, I added it as an issue there:
https://github.com/flathub/org.kde.tellico/issues/13

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

[Spectacle] [Bug 469915] New: Rectangular Region toolbars cover screen and need to be dragged out of the way to select region

2023-05-17 Thread nyanpasu64
https://bugs.kde.org/show_bug.cgi?id=469915

Bug ID: 469915
   Summary: Rectangular Region toolbars cover screen and need to
be dragged out of the way to select region
Classification: Applications
   Product: Spectacle
   Version: 23.04.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: nyanpas...@tuta.io
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
When I take a Rectangular Region screenshot, a toolbar appears covering part of
the screen I want to select.

STEPS TO REPRODUCE
1. Press Meta+Shift+PrintScr to take a region screenshot.
2. Try to select a region in the middle of the screen.

OBSERVED RESULT
A toolbar appears and covers the middle of the screen. It must be dragged out
of the way before you select a region near the middle.

EXPECTED RESULT
The toolbar appears at the top of the screen (where it's less likely to cover
screen content), or disappears altogether until you select a region (at which
point it appears below the region).

- Follow-up bug: if you select a region near the bottom of the screen, the
toolbar appears off-screen.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.1-zen1-1-zen (64-bit)
Graphics Platform: Wayland (X11 as well)
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550M DS3H

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 469914] System Settings: non-default settings for Software Update are not highlighted

2023-05-17 Thread Andrei Rybak
https://bugs.kde.org/show_bug.cgi?id=469914

--- Comment #2 from Andrei Rybak  ---
After more testing I realized that «4. If enabled, click on "Apply"» in "STEPS
TO REPRODUCE" is not needed.

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

[krita] [Bug 469885] The lasso is not normal

2023-05-17 Thread Marylands
https://bugs.kde.org/show_bug.cgi?id=469885

--- Comment #3 from Marylands  ---
That's why - YouTube 
I will admit to you that I myself do not know why I have this, certainly a
bad manipulation

Le mer. 17 mai 2023 à 19:41, vanyossi  a écrit :

> https://bugs.kde.org/show_bug.cgi?id=469885
>
> vanyossi  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  CC||ghe...@gmail.com
>  Status|REPORTED|NEEDSINFO
>
> --- Comment #1 from vanyossi  ---
> What do you mean by "not normal"?
>
> Please describe what you are experiencing, otherwise its going to be
> impossible
> to know what is going on. The report attached suggests a crash, is this
> what
> you are reporting?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[systemsettings] [Bug 469914] System Settings: non-default settings for Software Update are not highlighted

2023-05-17 Thread Andrei Rybak
https://bugs.kde.org/show_bug.cgi?id=469914

--- Comment #1 from Andrei Rybak  ---
Created attachment 159048
  --> https://bugs.kde.org/attachment.cgi?id=159048=edit
Screenshot for section EXPECTED RESULT

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

[systemsettings] [Bug 469914] New: System Settings: non-default settings for Software Update are not highlighted

2023-05-17 Thread Andrei Rybak
https://bugs.kde.org/show_bug.cgi?id=469914

Bug ID: 469914
   Summary: System Settings: non-default settings for Software
Update are not highlighted
Classification: Applications
   Product: systemsettings
   Version: 5.27.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_updates
  Assignee: plasma-b...@kde.org
  Reporter: rybak@gmail.com
  Target Milestone: ---

Created attachment 159047
  --> https://bugs.kde.org/attachment.cgi?id=159047=edit
Screenshot for section OBSERVED RESULT

SUMMARY
When a user changes a setting in System Settings to a value that isn't a
default, the UI element controlling the value usually gets highlighted.  This
doesn't happen to UI elements in "System Administration > Software Update"


STEPS TO REPRODUCE
1. Open System Settings
2. Navigate to "System Administration > Software Update"
3. If available, click on "Defaults"
4. If enabled, click on "Apply"
5. Change any one setting:
   - radio buttons "Manually"/"Automatically" for "Update software" 
   - dropdown (aka combobox) "Update frequency"
   - checkbox "Use offline updates"

OBSERVED RESULT
After step 5 all UI elements remain "unhighlighted". See the first screenshot.


EXPECTED RESULT
The UI element being changed to a non-default value has a highlight. See the
second screenshot – the panel "System Settings > Workspace > Window Management
> Tasks Switcher > Main" is shown with examples of both default and non-default
values.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

ADDITIONAL INFORMATION
In my color scheme, the UI elements with default values happen to have the blue
highlight, and UI elements with non-default values – orange highlight.

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

[lattedock] [Bug 469913] New: latte-dock crash on start fedora 38

2023-05-17 Thread Graeme Murray
https://bugs.kde.org/show_bug.cgi?id=469913

Bug ID: 469913
   Summary: latte-dock crash on start fedora 38
Classification: Plasma
   Product: lattedock
   Version: 0.10.8
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: graeme.w.mur...@gmail.com
  Target Milestone: ---

Application: latte-dock (0.10.8)

Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.2.15-300.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (Workstation Edition)
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
latte-dock crashes on startup. After installing rpmfusion mesa drivers .

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault

[KCrash Handler]
#4  0x7efdf777d7e8 in QString::toInt(bool*, int) const () at
/lib64/libQt5Core.so.5
#5  0x7efdb8c89f89 in Menu::updateViewData() () at
/usr/lib64/qt5/plugins/plasma/containmentactions/plasma_containmentactions_lattecontextmenu.so
#6  0x7efdb8c8dde1 in Menu::contextualActions() () at
/usr/lib64/qt5/plugins/plasma/containmentactions/plasma_containmentactions_lattecontextmenu.so
#7  0x55dabf4963bd in Latte::View::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
#8  0x7efdf91c3f0b in loadProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const&) () at /lib64/libQt5Qml.so.5
#9  0x7efdf91c5115 in
QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () at /lib64/libQt5Qml.so.5
#10 0x7efdf91e56fa in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) () at /lib64/libQt5Qml.so.5
#11 0x7efdf91ea18f in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) () at /lib64/libQt5Qml.so.5
#12 0x7efdf917a162 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () at /lib64/libQt5Qml.so.5
#13 0x7efdf9310120 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () at /lib64/libQt5Qml.so.5
#14 0x7efdf93168a7 in QQmlBinding::evaluate(bool*) () at
/lib64/libQt5Qml.so.5
#15 0x7efdf931ae5b in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) () at /lib64/libQt5Qml.so.5
#16 0x7efdf93186f5 in
QQmlBinding::update(QFlags) () at
/lib64/libQt5Qml.so.5
#17 0x7efdf92f3ee7 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /lib64/libQt5Qml.so.5
#18 0x7efdf78e8320 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#19 0x7efdf9298388 in QQmlVMEMetaObject::metaCall(QObject*,
QMetaObject::Call, int, void**) () at /lib64/libQt5Qml.so.5
#20 0x7efdf931a37b in GenericBinding<1>::write(QV4::Value const&, bool,
QFlags) () at /lib64/libQt5Qml.so.5
#21 0x7efdf931af7d in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) () at /lib64/libQt5Qml.so.5
#22 0x7efdf93186f5 in
QQmlBinding::update(QFlags) () at
/lib64/libQt5Qml.so.5
#23 0x7efdf92f3ee7 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /lib64/libQt5Qml.so.5
#24 0x7efdf78e8320 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#25 0x55dabf4c2ce7 in
Latte::Layout::GenericLayout::addView(Plasma::Containment*, bool, int,
QHash > >*) ()
#26 0x55dabf4be582 in
Latte::Layout::GenericLayout::addContainment(Plasma::Containment*) ()
#27 0x7efdf78e8651 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#28 0x7efdf9c6aca1 in
Plasma::Corona::containmentAdded(Plasma::Containment*) () at
/lib64/libKF5Plasma.so.5
#29 0x7efdf9caf0e2 in Plasma::CoronaPrivate::addContainment(QString const&,
QList const&, unsigned int, int, bool) [clone .isra.0] () at
/lib64/libKF5Plasma.so.5
#30 0x7efdf9c72356 in Plasma::CoronaPrivate::importLayout(KConfigGroup
const&, bool) () at /lib64/libKF5Plasma.so.5
#31 0x7efdf9c72929 in Plasma::Corona::loadLayout(QString const&) () at
/lib64/libKF5Plasma.so.5
#32 0x55dabf4dc382 in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) [clone .lto_priv.0] ()
#33 0x7efdf78ebc6a in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#34 0x7efdf78df6bb in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#35 0x7efdf85aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#36 0x7efdf78b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#37 0x7efdf7905c6b in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#38 0x7efdf7906569 in 

[krita] [Bug 469885] The lasso is not normal

2023-05-17 Thread Marylands
https://bugs.kde.org/show_bug.cgi?id=469885

--- Comment #2 from Marylands  ---
(In reply to vanyossi from comment #1)
> What do you mean by "not normal"?
> 
> Please describe what you are experiencing, otherwise its going to be
> impossible to know what is going on. The report attached suggests a crash,
> is this what you are reporting?

So : https://www.youtube.com/watch?v=qjgOjAAP0dM

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

[kdenlive] [Bug 469912] New: Excess line breaks in title clips

2023-05-17 Thread Gabriel Pinzón
https://bugs.kde.org/show_bug.cgi?id=469912

Bug ID: 469912
   Summary: Excess line breaks in title clips
Classification: Applications
   Product: kdenlive
   Version: 23.04.1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: g...@yahoo.com
  Target Milestone: ---

Created attachment 159046
  --> https://bugs.kde.org/attachment.cgi?id=159046=edit
Snapshot of how excess line breaks look when editing a title clip

Kdenlive adds line breaks to title clips by writing additional  strings
for each line break in each title clip (and also at the end of the lines of
"/item", "startviewport rect", "endviewport rect", "background color" and
"/kdenlivetitle" as seen when opening the .kdenlive file with a plain text
editor) every time a .kdenlive file is saved.


STEPS TO REPRODUCE
1. open an existing .kdenlive file with any amount of title clips
2. modify the .kdenlive file
3. Save the file.
4. Close kdenlive
5. Reopen kdenlive
6. Reopen the same .kdenlive file
7. Right click on a title clip and select "Edit clip".

OBSERVED RESULT
Excess line breaks in title clips caused by  strings, not visible in the
preview or in a processed file, but visible when opening a title clip,
additional  strings visible in a plain text editor.

EXPECTED RESULT
Having only the original line breaks of the file (visible in a plain text
editor as mere line breaks on Windows).

SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
MLT version: 7.15.0

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

[KScreen] [Bug 463527] Multi monitor layout no longer save - it always reverts to the previously saved layout (Wayland)

2023-05-17 Thread Khanich
https://bugs.kde.org/show_bug.cgi?id=463527

Khanich  changed:

   What|Removed |Added

 CC||khanich.opensou...@gmx.de

--- Comment #15 from Khanich  ---
(In reply to Nate Graham from comment #14)
> Oh good. :) 
> 
> Yes, being able to disable KScreen is a mixed blessing for sure. Perhaps we
> should prohibit that.

Maybe, but look at the reason on why they turned it off. And I just found
somebody else on r/kde who did it for the same reason.

So maybe that if this happens it should only happen after that bug is fixed.

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

[kwin] [Bug 469720] Gap between windows is different than the one being set

2023-05-17 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=469720

Ismael Asensio  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/2449b5897442 |ma/kwin/commit/1f2c1ec9b3b2
   |3b3be8e1382960299c586d42e64 |f3bee5a78eb2ee3ee6097e9b3b8
   |5   |7

--- Comment #3 from Ismael Asensio  ---
Git commit 1f2c1ec9b3b2f3bee5a78eb2ee3ee6097e9b3b87 by Ismael Asensio.
Committed on 17/05/2023 at 21:32.
Pushed by iasensio into branch 'Plasma/5.27'.

tiles: Adjust padding between windows

Make the total padding between windows equal to the padding against the
screen borders by applying just half of it on the common borders.

Adjust tests accordingly.
FIXED-IN: 5.27.6


(cherry picked from commit 2449b58974423b3be8e1382960299c586d42e645)

M  +26   -26   autotests/integration/tiles_test.cpp
M  +8-1src/tiles/tile.cpp

https://invent.kde.org/plasma/kwin/commit/1f2c1ec9b3b2f3bee5a78eb2ee3ee6097e9b3b87

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

[dolphin] [Bug 469911] [wishlist] Workspaces

2023-05-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469911

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[kwin] [Bug 469720] Gap between windows is different than the one being set

2023-05-17 Thread Ismael Asensio
https://bugs.kde.org/show_bug.cgi?id=469720

Ismael Asensio  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.27.6
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/2449b5897442
   ||3b3be8e1382960299c586d42e64
   ||5

--- Comment #2 from Ismael Asensio  ---
Git commit 2449b58974423b3be8e1382960299c586d42e645 by Ismael Asensio.
Committed on 17/05/2023 at 21:18.
Pushed by iasensio into branch 'master'.

tiles: Adjust padding between windows

Make the total padding between windows equal to the padding against the
screen borders by applying just half of it on the common borders.

Adjust tests accordingly.
FIXED-IN: 5.27.6

M  +26   -26   autotests/integration/tiles_test.cpp
M  +8-1src/tiles/tile.cpp

https://invent.kde.org/plasma/kwin/commit/2449b58974423b3be8e1382960299c586d42e645

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

[dolphin] [Bug 469911] New: [wishlist] Workspaces

2023-05-17 Thread Wesley Pimentel
https://bugs.kde.org/show_bug.cgi?id=469911

Bug ID: 469911
   Summary: [wishlist] Workspaces
Classification: Applications
   Product: dolphin
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: awakening...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Hello guys, 
You know, opera has a kind of workspaces, would be nice to have workspaces for
tabs. The "names" of workspaces are created by the user.
For example: 1 - work, 2- programming, 3- hobby.

For example, when I'm studying languages usually I open 3-4 tabs/folders in
different locations, same as programming.

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

[plasmashell] [Bug 444716] Do not activate the virtual keyboard when opening Widget Explorer

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=444716

Nate Graham  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 CC||n...@kde.org
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/-/commit/
   ||3829d2206d136d01b6449b944d6
   ||a9ce49f47ed67
 Resolution|--- |FIXED

--- Comment #3 from Nate Graham  ---
Fixed already with
https://invent.kde.org/plasma/plasma-desktop/-/commit/3829d2206d136d01b6449b944d6a9ce49f47ed67.

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

[dolphin] [Bug 450057] Unable to delete bookmark folders

2023-05-17 Thread Marian Ciobanu
https://bugs.kde.org/show_bug.cgi?id=450057

Marian Ciobanu  changed:

   What|Removed |Added

 CC||mciob...@gmail.com

--- Comment #4 from Marian Ciobanu  ---
I couldn't find "Bookmarks > Edit Bookmarks" either, but there is a workaround
of sorts: Edit the text file where these are stored, namely
/home/$USER/.local/share/dolphin/bookmarks.xml

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

[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs

2023-05-17 Thread Wesley Pimentel
https://bugs.kde.org/show_bug.cgi?id=469656

Wesley Pimentel  changed:

   What|Removed |Added

 CC||awakening...@gmail.com

--- Comment #22 from Wesley Pimentel  ---
(In reply to DarkThoughts from comment #21)
> I have the same issue on Arch / EOS for a few days now.
> This was already a slight issue previously whenever you used the open folder
> function in other programs such as the Firefox download manager or Steam,
> where it would either open a completely new instance with the existing
> session, or a completely new instance with a new session, even if Dolphin
> was already opened (and if it wasn't, the empty session would override the
> old one). Now it seems that whenever you restart Dolphin it starts a new
> session. This is really frustrating when you keep some tabs open that you're
> frequently working with or want to remember for later use, especially if
> they're embedded deeply into the file system.
> 
> It'd be great if it had a proper session manager that we could use to
> restore previous sessions.

Yeah I have the same problem, they could this this issue with a workaround a
button that we could press to restore some tabs (in the correct order) would be
nice, it's what the browser Opera calls "workspaces", For example: 1 -
workspace for work, 2- learn programming, 3- for a hobby. I will try to find a
place to request it.

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

[plasmashell] [Bug 469872] Problem with the taskbar.

2023-05-17 Thread Konstantin
https://bugs.kde.org/show_bug.cgi?id=469872

--- Comment #2 from Konstantin  ---
(In reply to Nate Graham from comment #1)

> Let's refocus on that. Do you by any chance have an NVIDIA GPU, and does
> this happen after you wake the computer or a monitor from sleep?

Yes, that's right, I have Nvidia :)

I don't notice a pattern in the taskbar hanging up. It hangs even when I'm just
modeling in Blender, for example. I had an RTX 3070Ti, now I have a 4080 and
the problem is still there.

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

[okular] [Bug 465055] All PDFs are shown stretched in y-axis

2023-05-17 Thread Oliver Sander
https://bugs.kde.org/show_bug.cgi?id=465055

--- Comment #21 from Oliver Sander  ---
Did you get Okular to build and link on your computer in the meantime?  My
apologies,  but I am not the one who can help with linker problems.

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

[plasmashell] [Bug 469894] [NVIDIA+WAYLAND] Plasmashell crashes when dragging a file/image from notifications applet

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469894

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 CC||n...@kde.org
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Nate Graham  ---
If something crashed, we need a backtrace of it so we can figure out what's
going on. Can you please attach a backtrace of the crash using the coredumpctl
command-line program, as detailed in
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

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

[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=461822

Nate Graham  changed:

   What|Removed |Added

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

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

[KScreen] [Bug 469115] 3-screen arrangement with one screen having multiple inputs connected to different computers gets messed up when switching the input between computers

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469115

Nate Graham  changed:

   What|Removed |Added

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

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

[KScreen] [Bug 469115] 3-screen arrangement with one screen having multiple inputs connected to different computers gets messed up when switching the input between computers

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469115

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #11 from Nate Graham  ---
Amazing. No wonder I was tearing out my hair and getting nowhere. I'll remember
to ask for this in the future. Thanks for following up!

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

[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=461822

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #19 from Nate Graham  ---
Amazing. No wonder I was tearing out my hair and getting nowhere. I'll remember
to ask for this in the future. Thanks for following up!

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

[kwin] [Bug 469891] Screenshot on multi-screen show false content

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469891

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
Product|kde |kwin
Version|unspecified |5.27.5
  Component|general |general
   Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org

--- Comment #1 from Nate Graham  ---
> spectacle as well as flameshot
Since it affects both apps, I'd lean towards this being caused by a GPU driver
issue.

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

[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login

2023-05-17 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=461822

--- Comment #18 from Raman Gupta  ---
Ok, so someone on Redditt found the root cause here by pointing me to
https://bugs.kde.org/show_bug.cgi?id=463527 -- my kscreen2 background service
was not running. I recalled I had disabled it some time ago because it was
causing issues with my monitors suspending or unsuspending or something, and
disabling it helped. Re-enabling the kscreen2 service fixes this problem, as
well as https://bugs.kde.org/show_bug.cgi?id=469115.

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

[KScreen] [Bug 469115] 3-screen arrangement with one screen having multiple inputs connected to different computers gets messed up when switching the input between computers

2023-05-17 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=469115

--- Comment #10 from Raman Gupta  ---
Ok, so someone on Redditt found the root cause here by pointing me to
https://bugs.kde.org/show_bug.cgi?id=463527 -- my kscreen2 background service
was not running. I recalled I had disabled it some time ago because it was
causing issues with my monitors suspending or unsuspending or something, and
disabling it helped. Re-enabling the kscreen2 service fixes this problem, as
well as https://bugs.kde.org/show_bug.cgi?id=461822.

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

[kwin] [Bug 469890] Allow one-to-one trackpad gestures when slide effect is disabled

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469890

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 CC||n...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---
The slide effect is the thing that provides the 1:1 animation for touchpads, so
I'm afraid there is no way to disable the effect but still have such a feature.

What would be possible is to do one of the following:
- add a setting to disable the effect's animations when switching using
something other than a touchpad gesture
- automatically don't use the effect for switching when using something other
than a touchpad gesture

But I think these are very niche and would not have broad appeal, requiring a
lot of code for little benefit. So I don't think we'll be doing it, sorry.

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

[kwin] [Bug 469864] Always on top is not respected

2023-05-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469864

viktor.horsmanhe...@gmail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|NOT A BUG   |---
 Status|RESOLVED|REOPENED

--- Comment #5 from viktor.horsmanhe...@gmail.com ---
(In reply to Nate Graham from comment #3)
> That's odd. What part of the window clicked through? An area that was
> clearly opaque, or an area around the edges, like in the shadow?

I'll record a video.(In reply to Nate Graham from comment #3)
> That's odd. What part of the window clicked through? An area that was
> clearly opaque, or an area around the edges, like in the shadow?

I made a video to show the POC of it https://youtu.be/HlY1U5E1UnY.

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

[plasmashell] [Bug 469889] plasmashell leaks inotify file descriptor

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469889

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org,
   ||sit...@kde.org

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

[kwin] [Bug 469864] Always on top is not respected

2023-05-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469864

--- Comment #4 from viktor.horsmanhe...@gmail.com ---
(In reply to Nate Graham from comment #1)
> There may be some confusion here; "always on top" doesn't mean that windows
> lower in the stacking order aren't resizable. It just means that the window
> marked as "always on top" is never overlapped by another window going over
> it.

Never mind, I just figured out how to reproduce the issue, it has to do with
multiple monitors. You need to move the window to the second screen and back.

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

[plasma-nm] [Bug 469887] Hotspot configuration is not reflected unless plasmashell is restarted

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469887

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[kwin] [Bug 469864] Always on top is not respected

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469864

--- Comment #3 from Nate Graham  ---
That's odd. What part of the window clicked through? An area that was clearly
opaque, or an area around the edges, like in the shadow?

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

[NeoChat] [Bug 469879] [enhancement]: Automatically activate the text entry field when searching in a room

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469879

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 CC||n...@kde.org
 Ever confirmed|0   |1
   Keywords||usability
 Status|REPORTED|CONFIRMED

--- Comment #1 from Nate Graham  ---
Agreed, this is a mild papercut that has annoyed me as well.

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

[kwin] [Bug 469864] Always on top is not respected

2023-05-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469864

--- Comment #2 from viktor.horsmanhe...@gmail.com ---
(In reply to Nate Graham from comment #1)
> There may be some confusion here; "always on top" doesn't mean that windows
> lower in the stacking order aren't resizable. It just means that the window
> marked as "always on top" is never overlapped by another window going over
> it.

It seems to have disappeared after restart, but it's not that the lower
stacking order shouldn't be resizable, but that you literally clicked through
the window. The top window was not registering the clicks, sadly I do not have
a video of this.

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

[NeoChat] [Bug 469875] [Feature]: Allow starting a new line with the enter key instead of sending the message

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469875

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[plasmashell] [Bug 469872] Problem with the taskbar.

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469872

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||n...@kde.org
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Nate Graham  ---
Lets try to focus on the bug itself that prompted this workaround, and not any
bugs stemming from the use of the workaround. :)  The bug is:

> Sometimes my taskbar freezes.

Let's refocus on that. Do you by any chance have an NVIDIA GPU, and does this
happen after you wake the computer or a monitor from sleep?

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

[systemsettings] [Bug 469869] [regression] KCM_SDDM Crashes Utilizing over 100% CPU

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469869

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |BACKTRACE
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---
Did you miss the big banner in the template that said that if you're reporting
a crash, you need to attach a backtrace of the crash? I notice you deleted that
text, but did not attach a backtrace. C'mon, John, I know you can do better
than this. :) Because if something crashed, we need a backtrace of it so we can
figure out what's going on. Otherwise it's a waste of both of our time. So can
you please attach a backtrace of the crash using the coredumpctl command-line
program, as detailed in
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

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

[konsole] [Bug 469910] [Feature request] Advanced paste dialog

2023-05-17 Thread Samantaz Fox
https://bugs.kde.org/show_bug.cgi?id=469910

Samantaz Fox  changed:

   What|Removed |Added

   Platform|Fedora RPMs |unspecified

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

[plasmashell] [Bug 463356] Audio indicators are displayed for some flatpaks that aren't running audio

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=463356

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #7 from Nate Graham  ---
*** Bug 469866 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 469866] icons-only task manager's sound icon is shared between spotify and ungoogled chromium

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469866

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||n...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---


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

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

[konsole] [Bug 469910] New: [Feature request] Advanced paste dialog

2023-05-17 Thread Samantaz Fox
https://bugs.kde.org/show_bug.cgi?id=469910

Bug ID: 469910
   Summary: [Feature request] Advanced paste dialog
Classification: Applications
   Product: konsole
   Version: 22.12.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: copy-paste
  Assignee: konsole-de...@kde.org
  Reporter: coding+kde_bugzi...@samantaz.fr
  Target Milestone: ---

SUMMARY

I've recently switched from tilix to Konsole, and one thing that I'm really
missing is a feature called "advanced paste". In essence, it's just a text box
in a dedicated dialog which allows to edit the content of the clipboard before
pasting it, with a dedicated shortcut (Ctrl+Alt+V in my case).

As a bonus, adding such a dialog could solve #89299

For reference, here is the Tilix implementation:
https://github.com/gnunn1/tilix/blob/master/source/gx/tilix/terminal/terminal.d#L1442


SOFTWARE/OS VERSIONS

Fedora KDE Spin, up to date.

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

[Skanpage] [Bug 457097] Scanning letter sized pages adds a blank area to scanned image

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=457097

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[Skanpage] [Bug 469865] Crash when exporting scans to PDF

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469865

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Nate Graham  ---
Crashing in tesseract, but it's hard to tell more without debug symbols. Can
you install debug symbols for tesseract and skanpage and get a new backtrace? 

See:
-
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Arch_Linux
-
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

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

[kwin] [Bug 469864] Always on top is not respected

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469864

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||n...@kde.org
 Resolution|--- |NOT A BUG

--- Comment #1 from Nate Graham  ---
There may be some confusion here; "always on top" doesn't mean that windows
lower in the stacking order aren't resizable. It just means that the window
marked as "always on top" is never overlapped by another window going over it.

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

[plasmashell] [Bug 456180] leftmost column in Status and Notifications has its focus highlight rendered on top

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=456180

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/
   |4d828b1b28e0bb0ecf720976453 |0ae0fbecf223c55bc6c713dbc50
   |9b1099ae3a328   |4acb0e5927194

--- Comment #3 from Nate Graham  ---
Git commit 0ae0fbecf223c55bc6c713dbc504acb0e5927194 by Nate Graham.
Committed on 17/05/2023 at 19:40.
Pushed by ngraham into branch 'Plasma/5.27'.

applets/systemtray: fix highlight being on top of first column items

By binding the content item's z to its x value, the first column where
x is 0 was being drawn underneath the highlight effect.
FIXED-IN: 5.27.6

co-authored-by: nttkde 
(cherry picked from commit 4d828b1b28e0bb0ecf7209764539b1099ae3a328)

M  +1-1applets/systemtray/package/contents/ui/items/ItemLoader.qml

https://invent.kde.org/plasma/plasma-workspace/commit/0ae0fbecf223c55bc6c713dbc504acb0e5927194

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

[kwin] [Bug 469909] Broken scaling in Qt6 apps when display scale is set to <100%

2023-05-17 Thread Kit
https://bugs.kde.org/show_bug.cgi?id=469909

--- Comment #2 from Kit  ---
Created attachment 159045
  --> https://bugs.kde.org/attachment.cgi?id=159045=edit
Audacious

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

[plasmashell] [Bug 456180] leftmost column in Status and Notifications has its focus highlight rendered on top

2023-05-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=456180

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.27.6
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/commit/
   ||4d828b1b28e0bb0ecf720976453
   ||9b1099ae3a328

--- Comment #2 from Nate Graham  ---
Git commit 4d828b1b28e0bb0ecf7209764539b1099ae3a328 by Nate Graham.
Committed on 17/05/2023 at 19:38.
Pushed by ngraham into branch 'master'.

applets/systemtray: fix highlight being on top of first column items

By binding the content item's z to its x value, the first column where
x is 0 was being drawn underneath the highlight effect.
FIXED-IN: 5.27.6

co-authored-by: nttkde 

M  +1-1applets/systemtray/package/contents/ui/items/ItemLoader.qml

https://invent.kde.org/plasma/plasma-workspace/commit/4d828b1b28e0bb0ecf7209764539b1099ae3a328

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

[kwin] [Bug 469909] Broken scaling in Qt6 apps when display scale is set to <100%

2023-05-17 Thread Kit
https://bugs.kde.org/show_bug.cgi?id=469909

--- Comment #1 from Kit  ---
Created attachment 159044
  --> https://bugs.kde.org/attachment.cgi?id=159044=edit
qBittorrent

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

  1   2   3   4   5   6   >