date:20230222

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[frameworks-baloo] [Bug 466161] baloo_file_extr crashing randomly, sometimes with garbled Kcrash files

2023-02-22 Thread Oxygel

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

--- Comment #4 from Oxygel  ---
I noticed, many comments regarding this issue concern Wayland. 
It shouldn't be related but I have another computer running Arch on X11 and
there's only report for SIGABRT (in coredumctl) on 2023-02-16 while I've been
using this computer everyday since this day. This date could have been a moment
where I tried Wayland for some reason.
Of course baloo is active on this PC.

I could be totally wrong, don't hesitate to tell if it's happening for you on
X11.

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

[frameworks-baloo] [Bug 466161] baloo_file_extr crashing randomly, sometimes with garbled Kcrash files

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

--- Comment #3 from tagwer...@innerjoin.org ---
(In reply to 860lacov from comment #2)
> Same here.
> Started after plasma 5.27 update.
Also on Arch?

Would be interesting to see if there's a link to the filesystem type. Ext4 or
something with more wrinkles (like BTRFS)?

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

[digikam] [Bug 465680] Fails to start due to missing library in openSUSE

2023-02-22 Thread Thomas Rother

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

Thomas Rother  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #17 from Thomas Rother  ---
confirmed, this version update fixes the dependency issue with libopenblas
(version info from /etc/os-release)

NAME="openSUSE Tumbleweed"
# VERSION="20230221"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20230221"

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

[plasma-nm] [Bug 465655] loopback interface shown with virtual interfaces disabled

2023-02-22 Thread Frank Kruger

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

Frank Kruger  changed:

   What|Removed |Added

 CC||fkrue...@mailbox.org

--- Comment #11 from Frank Kruger  ---
Thanks for the speedy fix, the loopback interface does not show up in the
applet anymore. However, it is still listed in the system settings. I this on
purpose?

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

[systemsettings] [Bug 466208] Display configuration for external display is lost after reboot (wayland)

2023-02-22 Thread Sebastian Turzański

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

--- Comment #2 from Sebastian Turzański  ---
I know what the issue was.
I was not using the settings center. Instead I always used this new widget in
the tray that allows to selected display layout (switch to external display)

When I do everything in the configuration center all works as expected.

Is that the idea that the widget is not persistent?

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

[plasmashell] [Bug 466131] Flatpak icons missing in system tray

2023-02-22 Thread Alexandre

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

Alexandre  changed:

   What|Removed |Added

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

--- Comment #1 from Alexandre  ---
Apparently it was a conflict between SOME Flatpak apps and the latest Plasma
update. Anyway, I was able to solve the most annoying missing tray icon
(SynologyDrive) by downloading it elsewhere. As of today, other Flatpaks seem
to work correctly.

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

[i18n] [Bug 466268] [PATCH] Translation for perceptualcolor provided

2023-02-22 Thread Frederik Schwarzer

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

Frederik Schwarzer  changed:

   What|Removed |Added

 CC||schwar...@kde.org

--- Comment #1 from Frederik Schwarzer  ---
Thanks a lot. :)

Once it appears in our translation files, I will sync your translation to it.

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

[frameworks-baloo] [Bug 466161] baloo_file_extr crashing randomly, sometimes with garbled Kcrash files

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

tagwer...@innerjoin.org changed:

   What|Removed |Added

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

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

[frameworks-baloo] [Bug 466266] baloo_file_extractor crashes frequently

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

tagwer...@innerjoin.org changed:

   What|Removed |Added

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

--- Comment #1 from tagwer...@innerjoin.org ---
There seems to be a rush of reports baloo_file-extractor / corrupt Kcrash dumps
just recently, see bug 466161. The ones that mention the OS say archlinux
(there are people who also say "happens to me" without giving an OS or
filesystem)

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

[frameworks-baloo] [Bug 466266] baloo_file_extractor crashes frequently

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

tagwer...@innerjoin.org changed:

   What|Removed |Added

 CC||tagwer...@innerjoin.org

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

[digikam] [Bug 462916] Different renaming behaviors for video files depending of the device

2023-02-22 Thread Maik Qualmann

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

--- Comment #18 from Maik Qualmann  ---
The two samples from here have the correct date (time zone is respected since
Android was detected as a device.
If you have a sample that you think digiKam is reporting an incorrect date,
please provide it.

Maik

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

[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze

2023-02-22 Thread Rune

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

Rune  changed:

   What|Removed |Added

Version|5.27.0  |5.27.1
Summary|Exiting full screen video   |Exiting full screen video
   |playback with on a  |playback with on a
   |multi-monitor setup with|multi-monitor setup causes
   |different scaling factors   |a freeze
   |causes a freeze |

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

[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze

2023-02-22 Thread Rune

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

--- Comment #6 from Rune  ---
(In reply to Rune from comment #5)
> (In reply to Rune from comment #0)
> > SUMMARY
> > 
> > Having multiple screens with different scaling factors in the plasma wayland
> > session makes it impossible to exit fullscreen video playback. The screen
> > that played back the video becomes unusable, the second screen works fine.
> > Graphical glitches can be observed on the primary screen when trying to exit
> > the full screen playback.
> > 
> > 
> > STEPS TO REPRODUCE
> > 1. Set different scaling factors on two monitors.
> > 2. Start playing back video in full screen mode (tried firefox (Youtube,
> > Netflix) as well as VLC (local file).
> > 3. Try exiting the playback.
> > 
> > OBSERVED RESULT
> > 
> > The screen becomes unresponsive and shows graphical artifacts.
> > 
> > EXPECTED RESULT
> > 
> > The video playback can be exited normally.
> > 
> > SOFTWARE/OS VERSIONS
> > Linux/KDE Plasma: Arch Linux 6.1.12-arch
> > (available in About System)
> > KDE Plasma Version: 5.27.1
> > KDE Frameworks Version: 5.103.0
> > Qt Version: 5.15.8
> > 
> > ADDITIONAL INFORMATION
> > 
> > AMD GPU with open source drivers, though proprietary OpenGL driver is
> > installed. Hardware acceleration is enabled.
> 
> More info: Even without mixed scaling factors, being unable to exit
> fullscreen is a problem. Wether it occurs or not seems to be linked to the
> time spent in fullscreen mode,
> It also does only happen with video playback, not when playing e.g. video
> games in full screen.

Uninstalling the amdgpu-pro-oglp package (Proprietary AMD OpenGL driver) did
not help.

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

[digikam] [Bug 465922] Digikam is crashing

2023-02-22 Thread Raffie

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

--- Comment #4 from Raffie  ---
That did it,
I've tested it the last couple of days,
not one single crash 珞

Thank you so much

Op vr 17 feb. 2023 om 17:49 schreef :

> https://bugs.kde.org/show_bug.cgi?id=465922
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
>
> 
>  CC||caulier.gil...@gmail.com
>
> --- Comment #3 from caulier.gil...@gmail.com ---
> We have a blocking bug about packaging MacOS with mysql database plugin.
> If you
> don't use mysql/mariadb as database, you can already use the 7.10.0
> pre-release
> bundle, it safe (only bugfixes)
>
> https://files.kde.org/digikam/
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze

2023-02-22 Thread Rune

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

--- Comment #5 from Rune  ---
(In reply to Rune from comment #0)
> SUMMARY
> 
> Having multiple screens with different scaling factors in the plasma wayland
> session makes it impossible to exit fullscreen video playback. The screen
> that played back the video becomes unusable, the second screen works fine.
> Graphical glitches can be observed on the primary screen when trying to exit
> the full screen playback.
> 
> 
> STEPS TO REPRODUCE
> 1. Set different scaling factors on two monitors.
> 2. Start playing back video in full screen mode (tried firefox (Youtube,
> Netflix) as well as VLC (local file).
> 3. Try exiting the playback.
> 
> OBSERVED RESULT
> 
> The screen becomes unresponsive and shows graphical artifacts.
> 
> EXPECTED RESULT
> 
> The video playback can be exited normally.
> 
> SOFTWARE/OS VERSIONS
> Linux/KDE Plasma: Arch Linux 6.1.12-arch
> (available in About System)
> KDE Plasma Version: 5.27.1
> KDE Frameworks Version: 5.103.0
> Qt Version: 5.15.8
> 
> ADDITIONAL INFORMATION
> 
> AMD GPU with open source drivers, though proprietary OpenGL driver is
> installed. Hardware acceleration is enabled.

More info: Even without mixed scaling factors, being unable to exit fullscreen
is a problem. Wether it occurs or not seems to be linked to the time spent in
fullscreen mode,
It also does only happen with video playback, not when playing e.g. video games
in full screen.

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

[Discover] [Bug 466290] New: When the dock icon indicates there are updates available, it shouldn't take 5 minutes to find out what they are.

2023-02-22 Thread P Fudd

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

Bug ID: 466290
   Summary: When the dock icon indicates there are updates
available, it shouldn't take 5 minutes to find out
what they are.
Classification: Applications
   Product: Discover
   Version: 5.27.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: bugs.kde@ch.pkts.ca
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
I updated my system to Fedora 37 last night.  This morning I see the "Updates
Available" icon on my dash.  I click on it, and Discover starts up, puts up a
"Fetching updates..." message and a progress bar, and then proceeds to take
several minutes to load the list of updates.

It would be nice if it could download the list of updates *before* trying to
gain my attention.

This irritation is further compounded by the fact that the progress bar travels
fast until it reaches about 95%, and then appears to hang (although I'm sure
it'll finish... eventually).

And under the hood, the icing on the cake is that the list of updates being
downloaded is likely 99% similar to the list it had from the day before, and
yet it's downloading the whole thing again.  If it could be changed to download
and apply a patch to the list of updates, that would speed things up.  If you
could do a DNS lookup of a TXT record (e.g. update-status.kde.org) that
returned a signed serial number and date, then the client wouldn't even have to
connect to the repository to discover that nothing's changed since the last
time they checked.  If the signature is bad or the date is old, fall back to
checking the repository.


STEPS TO REPRODUCE
1. Install Fedora (or maybe just KDE)
2. Wait for the "Updates available" icon to appear (hours? days?)
3. Click on the icon

OBSERVED RESULT
"Hurry up and wait" 

EXPECTED RESULT
"Skinner Box"

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora Linux 37 - Kernel 6.1.12-200.fc37.x86_64 (64-bit)
(available in About System)
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 466289] Teradici menu doesn't work with the global menu & can't access its menu when fullscreen

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

--- Comment #3 from techxga...@outlook.com ---
Created attachment 156633
  --> https://bugs.kde.org/attachment.cgi?id=156633=edit
Screenshot of fullscreen Teradici session in Neon Unstable

No global menu

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

[plasmashell] [Bug 466289] Teradici menu doesn't work with the global menu & can't access its menu when fullscreen

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

--- Comment #2 from techxga...@outlook.com ---
Created attachment 156632
  --> https://bugs.kde.org/attachment.cgi?id=156632=edit
Screenshot of maximized Teradici session in Neon Unstable

This VM doesn't have a global menu enabled, and it shows that the local menu of
Teradici being accessible.

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-3-liquorix-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD EPYC-Milan Processor
Memory: 7.8 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: QEMU
Product Name: Standard PC (Q35 + ICH9, 2009)
System Version: pc-q35-6.0

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

[KScreen] [Bug 466149] On Xorg, Plasma's idea of the monitor configuration differs from xrandr's

2023-02-22 Thread Trent M

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

--- Comment #3 from Trent M  ---
(In reply to David Edmundson from comment #2)
> The xrandr output shows  DP-1-1 disconnected, the kscreen output shows
> DP-1-1 connected
> 
> Are these different program outputs of the same setup?

That's correct.

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

[plasmashell] [Bug 466289] Teradici menu doesn't work with the global menu & can't access its menu when fullscreen

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

--- Comment #1 from techxga...@outlook.com ---
Created attachment 156631
  --> https://bugs.kde.org/attachment.cgi?id=156631=edit
Screenshot of Teradici session with Plasma 5.27

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

[plasmashell] [Bug 466028] Upgrading to KDE 5.27 resulted in older version of desktop

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

--- Comment #5 from Nate Graham  ---
If your setup is simple, then yes, the old data would be helpful so we can
improve the migration code.

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

[plasmashell] [Bug 466289] Teradici menu doesn't work with the global menu & can't access its menu when fullscreen

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

techxga...@outlook.com changed:

   What|Removed |Added

Summary|Teradici menu doesn't work  |Teradici menu doesn't work
   |with the global menu &  |with the global menu &
   |can;t access its menu when  |can't access its menu when
   |fullscreen  |fullscreen

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

[xdg-desktop-portal-kde] [Bug 428373] "Examining (Failed)" notifications some times when trying to save in folders with many files.

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|REMIND  |FIXED
 Status|VERIFIED|RESOLVED

--- Comment #16 from Nate Graham  ---
Please submit a new bug report with your issue, and avoid changing the
resolution status of closed bug reports. Thanks!

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

[plasmashell] [Bug 466289] New: Teradici menu doesn't work with the global menu & can;t access its menu when fullscreen

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

Bug ID: 466289
   Summary: Teradici menu doesn't work with the global menu &
can;t access its menu when fullscreen
Classification: Plasma
   Product: plasmashell
   Version: 5.27.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Global Menu
  Assignee: plasma-b...@kde.org
  Reporter: techxga...@outlook.com
CC: k...@privat.broulik.de, mvourla...@gmail.com
  Target Milestone: 1.0

SUMMARY
I can't seem to make Teradici show the global menu for a long time.  The menu
does work if there's no global menu present or the button on the title bar is
present.
The button mode in the global menu doesn't work either
In addition, the menu is inaccessible when global menu is present.

STEPS TO REPRODUCE
1. Add the global menu in a panel

OBSERVED RESULT
Global menu doesn't stay too long, and can be used if fast enough.
Local menu doesn't work as well, unless global menu was removed.

EXPECTED RESULT
Menu should remain present,

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.10
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.6
Kernel Version: 6.1.12-1-liquorix-amd64 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570S AORUS MASTER
System Version: -CF

ADDITIONAL INFORMATION
This is the link to download Teradici:
https://docs.teradici.com/find/product/software-and-mobile-clients
Also created a reddit post that shows that I can't access its menu when full
screen
https://www.reddit.com/r/kde/comments/119pgfu/is_there_a_way_for_kwin_to_show_the_titlebar_of/

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

[plasmashell] [Bug 466288] New: Bluetooth media sessions don't appear in Media Player when using mpris-proxy

2023-02-22 Thread Jackson

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

Bug ID: 466288
   Summary: Bluetooth media sessions don't appear in Media Player
when using mpris-proxy
Classification: Plasma
   Product: plasmashell
   Version: 5.27.1
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Media Player
  Assignee: plasma-b...@kde.org
  Reporter: jacksonbur...@icloud.com
CC: k...@privat.broulik.de
  Target Milestone: 1.0

SUMMARY
By connecting my phone to my computer through Bluetooth, and by using PipeWire,
I'm able to play my phone's audio through my computer. By default, my phone's
Bluetooth media session doesn't show up in Media Player, but I can use BlueZ's
mpris-proxy utility to expose the session as an MPRIS player. However, the
MPRIS player generated by mpris-proxy isn't detected by Media Player. Media
keys don't work either.

STEPS TO REPRODUCE
1. Use Bluetooth to connect a phone to a machine running Plasma with PipeWire
as the audio system.
2. Play music on the phone. Make sure the sound output is set to the computer.
3. Open a terminal, and run `mpris-proxy`.

OBSERVED RESULT
The Media Player icon doesn't appear in the system tray, and manually selecting
it results in the 'No media playing' message. Media keys don't affect playback,
either.

EXPECTED RESULT
Once mpris-proxy is started, playback controls for the Bluetooth media session
should appear in Media Player, and media keys should function.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (Wayland)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
I'm able to successfully control playback by using playerctl v2.4.1 or GNOME
Shell 43.3.
I'm using a Pixel 6 running Android 13 with YouTube Music, but the same
behavior should occur with other phone brands and music apps.

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

[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.

2023-02-22 Thread Raman Gupta

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

--- Comment #29 from Raman Gupta  ---
One other detail: when opening on the left monitor, yakuake opens according to
my settings: horizontally centered. But when opening on the middle monitor,
yakuake opens horizontally left-aligned to screen edge, and when opening on the
right monitor, yakuake opens on the middle monitor but horizontally
right-aligned to screen edge.

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

[plasmashell] [Bug 466028] Upgrading to KDE 5.27 resulted in older version of desktop

2023-02-22 Thread Wyatt Childers

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

--- Comment #4 from Wyatt Childers  ---
(In reply to Nate Graham from comment #3)
> Thanks for the offer. Unfortunately it doesn't really help as the old state
> is inherently non-determinstic. That's why stuff was so bad before,
> especially with 3+ screens or a frequently-changing screen arrangement.

The odd thing is, I was/am on a desktop, and never had any issues with the old
way doing anything surprising; i.e., for me anyways it was very deterministic.
Maybe this isn't the case, but because of that, it seems like the migration
script should be able to handle this equally as well, no?

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

[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.

2023-02-22 Thread Raman Gupta

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

Raman Gupta  changed:

   What|Removed |Added

 CC||rocketra...@gmail.com

--- Comment #28 from Raman Gupta  ---
I have the same problem with 3 hidpi screens on Plasma 5.27.0. Yakuake is
configured to open at the mouse location, but I can only open it on the left or
middle screens. Attempting to open it on the right screen opens it on the
middle screen instead.

Deleting `~/.config/yakuakerc ` and restarting yakuake did not fix the problem
for me.

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

[plasma-nm] [Bug 465655] loopback interface shown with virtual interfaces disabled

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

Nate Graham  changed:

   What|Removed |Added

 Status|VERIFIED|RESOLVED
 Resolution|REMIND  |FIXED

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

[krita] [Bug 466287] New: Timers cannot have negative intervals crash on startup

2023-02-22 Thread Ralek Kolemios

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

Bug ID: 466287
   Summary: Timers cannot have negative intervals crash on startup
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@ralek.art
  Target Milestone: ---

In the latest several nightly master releases, Krita crashes on startup. The
output it gives when run in terminal is this:

> krita.lib.pigment: Replacing color space factory "LABA" "L*a*b* (16-bit 
> integer/channel, unmanaged)" with "LABA" "L*a*b*/Alpha (16-bit 
> integer/channel)"
> krita.lib.pigment: Replacing color space factory "RGBA" "RGB (8-bit 
> integer/channel, unmanaged)" with "RGBA" "RGB/Alpha (8-bit integer/channel)"
> krita.lib.pigment: Replacing color space factory "RGBA16" "RGB (16-bit 
> integer/channel, unmanaged)" with "RGBA16" "RGB/Alpha (16-bit 
> integer/channel)"
> QObject::startTimer: Timers cannot have negative intervals
> /tmp/.mount_krita-MpqDCc/usr/lib/krita-python-libs/krita added to PYTHONPATH


I have tested from 0e85ce2a to the latest d92f026c

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

[kstars] [Bug 466286] Ekos does not return my saved Indi Preferences at next startup

2023-02-22 Thread Len North

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

--- Comment #1 from Len North  ---
MY Location is always correct, except when it places all targets below the
horizon. This was fixed by Jasem at my request years ago
The QSI does not remember my camera temperature, cooling ramps,  This occurred
when cooling ramps were introduced. WCS degrees Rotation and observer name
always show empty.
Solver is never enabled, I often re-enable it 5 or 6 times during startup -
then it's good til I do a meridian flip and we start again.

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

[kstars] [Bug 466286] New: Ekos does not return my saved Indi Preferences at next startup

2023-02-22 Thread Len North

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

Bug ID: 466286
Summary: Ekos does not return my saved Indi Preferences at next
startup
Classification: Applications
Product: kstars
Version: unspecified
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: astroga...@westnet.com.au
Target Milestone: ---

Created attachment 156630
--> https://bugs.kde.org/attachment.cgi?id=156630=edit
Starting with Astrometry, Default configuration loaded last. It's not what I
Saved.

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
***
I appear to be getting default configurations overwriting my saved preferences
in the Indi Control Panel as shown by the attached text.
This problem has been better defined for me by the help of Forum members,
especially Frederick Ruegsegger on #90756 "For my part, this has been fiddly
from time to time - particularly during configuration of a new or revised
profile."
Fred has defined this well, and since I commenced doing Bug reporting on
Nightly Builds I have have reloaded the Linux PC with 3 new OS and now run an
exclusive Kubuntu SSD drive only - each time I blame my system as my KStars Ver
3.5.7 has none of the Fatal issues I am now finding with a new build.
STEPS TO REPRODUCE
1. An Mature KStars is annoying sometimes, but not with fatal crashes.
2. A new build is difficult to configure each night for imaging, hours are lost
in the setup.
3. The logs show the configuration information, but the text entered below the
Indi Control Panels indicate that My Saved Configurations may be being
overwritten by system default configurations.

OBSERVED RESULT
New Builds of any KStars on a new OS are not stable. They stabilize over time.

EXPECTED RESULT
Without a 'Portable and Editable Configuration File Backup' confirming my
preferances, then I'm just getting a factory default setting in my preferances

SOFTWARE/OS VERSIONS:
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-60-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 31.3 GiB of RAM
Graphics Processor: llvmpipe

ADDITIONAL INFORMATION
Would you please consider a USB drive backup / restore file system where we
could just reload all our details, equipment, optial trains and preferances?
Thanks

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

[dolphin] [Bug 466121] Folders panel menu translucency is broken

2023-02-22 Thread Vladimir Yerilov

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

--- Comment #3 from Vladimir Yerilov  ---
Couldn't reproduce it in Wayland session, it happens under X only.

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

[plasma-nm] [Bug 465655] loopback interface shown with virtual interfaces disabled

2023-02-22 Thread KazuhiroShigeru

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

--- Comment #10 from KazuhiroShigeru  ---
(In reply to KazuhiroShigeru from comment #9)
> (In reply to ratijas from comment #6)
> > Git commit 57bbd8a07ec7a37071eede01ef399ab2f8fc24f1 by ivan tkachenko, on
> > behalf of David Redondo.
> > Committed on 16/02/2023 at 15:46.
> > Pushed by davidre into branch 'master'.
> > 
> > Filter out the loopback device
> > 
> > Quick fix so we can backport it.
> > FIXED-IN:5.27.1
> > 
> > M  +2-1libs/declarative/networkstatus.cpp
> > M  +5-0libs/models/networkmodel.cpp
> > 
> > https://invent.kde.org/plasma/plasma-nm/commit/
> > 57bbd8a07ec7a37071eede01ef399ab2f8fc24f1
> 
> how we can apply this fix?

nvm, noticed that I have to update plasma.

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

[kdeplasma-addons] [Bug 466230] The eyedropper in the colorpicker widget does not work

2023-02-22 Thread Fushan Wen

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

Fushan Wen  changed:

   What|Removed |Added

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

--- Comment #5 from Fushan Wen  ---
Should probably disable the picker button when compositing is disabled and show
some text in the tooltip.

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

[kdeplasma-addons] [Bug 466230] The eyedropper in the colorpicker widget does not work

2023-02-22 Thread grayich

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

--- Comment #4 from grayich  ---
systemsettings > Display and Monitor > Compositor > [off] Enable on startup

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

[xdg-desktop-portal-kde] [Bug 428373] "Examining (Failed)" notifications some times when trying to save in folders with many files.

2023-02-22 Thread LandisTwo

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

LandisTwo  changed:

   What|Removed |Added

 CC||lan...@landistwo.com
 Status|RESOLVED|VERIFIED
 Resolution|FIXED   |REMIND

--- Comment #15 from LandisTwo  ---
I am having the exact same 'Portal Examining (Failed)
/path/to/directory/with/xk-files
What is 'Portal' and Why is it 'Examining' a path (directory) specifically 'Not
Indexed' in System Settings?
Landis.

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

[plasma-nm] [Bug 465655] loopback interface shown with virtual interfaces disabled

2023-02-22 Thread KazuhiroShigeru

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

--- Comment #9 from KazuhiroShigeru  ---
(In reply to ratijas from comment #6)
> Git commit 57bbd8a07ec7a37071eede01ef399ab2f8fc24f1 by ivan tkachenko, on
> behalf of David Redondo.
> Committed on 16/02/2023 at 15:46.
> Pushed by davidre into branch 'master'.
> 
> Filter out the loopback device
> 
> Quick fix so we can backport it.
> FIXED-IN:5.27.1
> 
> M  +2-1libs/declarative/networkstatus.cpp
> M  +5-0libs/models/networkmodel.cpp
> 
> https://invent.kde.org/plasma/plasma-nm/commit/
> 57bbd8a07ec7a37071eede01ef399ab2f8fc24f1

how we can apply this fix?

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

[plasma-nm] [Bug 465655] loopback interface shown with virtual interfaces disabled

2023-02-22 Thread KazuhiroShigeru

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

KazuhiroShigeru  changed:

   What|Removed |Added

 Resolution|FIXED   |REMIND
 CC||shigerukazuh...@gmail.com
 Status|RESOLVED|VERIFIED

--- Comment #8 from KazuhiroShigeru  ---
(In reply to Nicolas Fella from comment #5)
> FTR this behavior was introduced by the NetworkManager 1.42 release

I also noticed this after my last update. I don't mind having virtual devices
or loops, but allow us to hide it at least. thanks that archwiki mentions what
it is. I don't want it to show it on my system tray network settings.

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

[kwin] [Bug 107302] Per-screen virtual desktops

2023-02-22 Thread Ricardo

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

Ricardo  changed:

   What|Removed |Added

 CC||rica...@dymstro.nl

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

[kdenlive] [Bug 463959] Warning while rendering

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[systemsettings] [Bug 464657] Support for changing the axes values in variable fonts

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- 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 463020] copy merge on a group layer can crash krita

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 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 464711] When I try to use any brush, it erase the drawing, even though I checked that the erase function is off, it keeps erasing the drawing, so it's impossible to use krita.

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

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.

[plasmashell] [Bug 439917] Sometimes unable to rearrange pinned apps via touch

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |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.

[Smb4k] [Bug 465392] Just flat doesn't work on Zorin 16.2

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

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

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

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

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

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

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

[kwin] [Bug 460752] Frozen image when window is snapped into corner under X11

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kmymoney] [Bug 465471] Import split transactions from csv

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

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

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

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

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

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

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

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[skrooge] [Bug 465467] skrooge segfault

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

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

[skrooge] [Bug 462666] Joint accounts

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

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

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

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

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

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

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

[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup

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

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

[skrooge] [Bug 437933] Confirm before dismissing changed operation

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

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

[kdeplasma-addons] [Bug 466230] The eyedropper in the colorpicker widget does not work

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

--- Comment #3 from Nate Graham  ---
Thanks. Which effect were turned off?

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

[plasmashell] [Bug 466228] Black screen when changing from X11 to Wayland or vice-versa

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

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
   Version Fixed In||5.27.1
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Nate Graham  ---
Ok, great news! Let's say it did.

Feel free to re-open this bug report if you see the issue again, though.

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

[kasts] [Bug 466274] Album artwork does not refresh when podcast subscription originated from a sync that pulled from the server.

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

--- Comment #1 from benmorde...@protonmail.com ---
As a test I have subscribed to a podcast that I was not previously synced with
on Gpoddersync and it also did not contain album artwork, so it may be that
something for me it just broken with album art in general.

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

[kdeplasma-addons] [Bug 466230] The eyedropper in the colorpicker widget does not work

2023-02-22 Thread grayich

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

--- Comment #2 from grayich  ---
Found the reason why it didn't work. The eefects were completely turned off .
It works with the effects enabled.
imho - it's not obvious, it wasn't written anywhere in the supplement that
effects are needed

thanks

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

[kwin] [Bug 466279] kwin_wayland crashes in KWin::TabBox::SwitcherItem::visibleChanged() when alt-tabbing with 5 or more items and using Large Icons task switcher

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

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
   Keywords||regression
 Ever confirmed|0   |1
   Priority|NOR |VHI
 CC||vlad.zahorod...@kde.org

--- Comment #1 from Nate Graham  ---
Git bisect says it was 4b1ef33c1e3887b58b5d787d2df71c017c2318a3.

I've noticed that 5 items is exactly the number of items that will require the
Large Icons task switcher to change the size of its background dialog; up to 4
items fit in its default size but 5 makes it need to expand. Something about
the above commit causes kwin_wayland to crash when it tried to expand its
dialog.

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

[plasmashell] [Bug 466228] Black screen when changing from X11 to Wayland or vice-versa

2023-02-22 Thread Doug

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

--- Comment #2 from Doug  ---
(In reply to David Edmundson from comment #1)
> Can you include output of journalctl --user -b after reproducing this issue

I can no longer reproduce the issue.  I did get an update today- plasma-desktop
5.27.1-2.  Maybe that fixed it?

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

[frameworks-knotifications] [Bug 466285] Click the notification popup button doesn't work

2023-02-22 Thread zyf0330

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

--- Comment #1 from zyf0330  ---
related to https://bugs.kde.org/show_bug.cgi?id=444243

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

[digikam] [Bug 466259] digiKam crash after launch

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

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

   What|Removed |Added

   Version Fixed In||8.0.0
 CC||caulier.gil...@gmail.com

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

[frameworks-knotifications] [Bug 466285] New: Click the notification popup button doesn't work

2023-02-22 Thread zyf0330

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

Bug ID: 466285
   Summary: Click the notification popup button doesn't work
Classification: Frameworks and Libraries
   Product: frameworks-knotifications
   Version: 5.98.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: zyf034...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

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

SUMMARY 
The KdeConnect app displays a popup box for Android app notifications, but it
does not respond when the button in the popup is clicked.


STEPS TO REPRODUCE
1. there is a notification from KDEConnect
2. click button

OBSERVED RESULT
Nothing happened.

EXPECTED RESULT
The action related to button is executed, and notification popup diesappears.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version:  5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION

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

[kwin] [Bug 466179] Graphical glitches after minimizing windows using multi-screen setup

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
Thanks for the info!

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

[kwin] [Bug 466179] Graphical glitches after minimizing windows using multi-screen setup

2023-02-22 Thread Andrew

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

--- Comment #2 from Andrew  ---
(In reply to Nate Graham from comment #1)
> What kind of GPU are you using?
> 
> Also, can you paste the output of:
> - `kscreen-doctor -o`
> - `qdbus org.kde.KWin /KWin supportInformation`

Here is the output of when my laptop is connected to my monitors via a CalDigit
TB3+ dock:

```
➜  ~ inxi -Gzzz   
Graphics:
  Device-1: Intel Iris Plus Graphics 640 driver: i915 v: kernel
  Device-2: Suyin HP TrueVision FHD RGB-IR type: USB driver: uvcvideo
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: kwin_wayland driver: X: loaded: intel gpu: i915 resolution:
1: 900x1600 2: 2560x1440 3: 900x1600
  OpenGL:
renderer: Mesa Intel Iris Plus Graphics 640 (Kaby Lake GT3e) (KBL GT3)
v: 4.6 Mesa 22.2.5
```

```
➜  ~ kscreen-doctor -o
Output: 1 eDP-1 disabled connected priority 0 Panel Modes: 0:1920x1080@60*!
1:1920x1080@40 2:1280x1024@60 3:1024x768@60 4:1280x800@60 5:1920x1080@60
6:1600x900@60 7:1368x768@60 8:1280x720@60 Geometry: 0,0 1920x1080 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic
Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:1600x900@60*!
1:1280x1024@75 2:1280x1024@60 3:1152x864@75 4:1024x768@75 5:1024x768@60
6:800x600@75 7:800x600@60 8:640x480@75 9:640x480@60 10:720x400@70
11:1024x768@60 12:1280x800@60 13:1368x768@60 14:1280x720@60 Geometry: 0,0
900x1600 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: Automatic
Output: 3 DP-3 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60*!
1:2048x1080@60 2:2048x1080@24 3:1920x1080@60 4:1920x1080@60 5:1920x1080@60
6:1920x1080@50 7:1600x1200@60 8:1280x1024@75 9:1280x1024@60 10:1152x864@75
11:1280x720@60 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75
16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x576@50
21:720x480@60 22:720x480@60 23:720x480@60 24:720x480@60 25:640x480@75
26:640x480@60 27:640x480@60 28:640x480@60 29:720x400@70 30:1600x1200@60
31:1280x1024@60 32:1024x768@60 33:1920x1200@60 34:1280x800@60 35:1920x1080@60
36:1600x900@60 37:1368x768@60 38:1280x720@60 Geometry: 900,0 2560x1440 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic
Output: 4 DP-4 enabled connected priority 3 DisplayPort Modes: 0:1600x900@60*!
1:1280x1024@75 2:1280x1024@60 3:1152x864@75 4:1024x768@75 5:1024x768@60
6:800x600@75 7:800x600@60 8:640x480@75 9:640x480@60 10:720x400@70
11:1024x768@60 12:1280x800@60 13:1368x768@60 14:1280x720@60 Geometry: 3460,0
900x1600 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: Automatic
```

```
KWin Support Information:
The following information should be used when requesting support on e.g.
https://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a
paste bin service
like https://paste.kde.org instead of pasting into support threads.

==

Version
===
KWin version: 5.27.0
Qt Version: 5.15.8
Qt compile version: 5.15.8
XCB compile version: 1.14

Operation Mode: Xwayland

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12201001
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 1
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true

Cursor
==
themeName: breeze_cursors
themeSize: 24

Options
===
focusPolicy: 1
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 750
delayFocusInterval: 300
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28

[kwin] [Bug 466281] Nested kwin_wayland crashed in KWin::GLFramebuffer::size in VMs using the llvmpipe driver

2023-02-22 Thread Matt Fagnani

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

--- Comment #1 from Matt Fagnani  ---
I booted the Fedora 38 KDE Plasma live image
Fedora-KDE-Live-x86_64-38-20230221.n.1.iso in a QEMU/KVM VM using GNOME Boxes
with 3D acceleration disabled using the llvmpipe driver. I ran nested
kwin_wayland under valgrind in konsole with valgrind
--log-file=valgrind-nested-kwin_wayland-5.27.0-1.txt --enable-debuginfod=no
kwin_wayland --xwayland

The valgrind log showed the syscall param waitid(infop) pointed to
unaddressable byte(s) 0x0 and an invalid read of the address 0x4 at
UnknownInlinedFun (kwinglutils.h:421) causing the segmentation fault.

==4964== Memcheck, a memory error detector
==4964== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==4964== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==4964== Command: kwin_wayland --xwayland
==4964== Parent PID: 4142
==4964== 
==4964== Syscall param waitid(infop) points to unaddressable byte(s)
==4964==at 0x78A3D2D: syscall (syscall.S:38)
==4964==by 0x666F85E: sys_waitid (forkfd_linux.c:65)
==4964==by 0x666F85E: detect_clone_pidfd_support (forkfd_linux.c:126)
==4964==by 0x666F85E: system_forkfd (forkfd_linux.c:142)
==4964==by 0x666F85E: forkfd (forkfd.c:651)
==4964==by 0x6655118: QProcessPrivate::startProcess()
(qprocess_unix.cpp:466)
==4964==by 0x2137EE: KWin::Xwl::XwaylandLauncher::startInternal() [clone
.isra.0] (xwaylandlauncher.cpp:186)
==4964==by 0x66FBF50: call (qobjectdefs_impl.h:398)
==4964==by 0x66FBF50: void doActivate(QObject*, int, void**)
(qobject.cpp:3923)
==4964==by 0x4CB93BE: KWin::Compositor::setupStart() [clone .part.0]
(composite.cpp:335)
==4964==by 0x4CBAE27: KWin::WaylandCompositor::start() (composite.cpp:799)
==4964==by 0x66F303A: QObject::event(QEvent*) (qobject.cpp:1347)
==4964==by 0x6E34CE4: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(in /usr/lib64/libQt5Widgets.so.5.15.8)
==4964==by 0x66C7647: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1064)
==4964==by 0x66CAAF4: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1821)
==4964==by 0x6717370:
QEventDispatcherUNIX::processEvents(QFlags)
(qeventdispatcher_unix.cpp:468)
==4964==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==4964== 
==4964== Invalid read of size 8
==4964==at 0x4CC2EAD: UnknownInlinedFun (kwinglutils.h:421)
==4964==by 0x4CC2EAD: KWin::RenderTarget::size() const
(rendertarget.cpp:30)
==4964==by 0x4D69FEB: KWin::CursorScene::paint(KWin::RenderTarget*, QRegion
const&) (cursorscene.cpp:57)
==4964==by 0x4D6ED90: KWin::SceneDelegate::paint(KWin::RenderTarget*,
QRegion const&) (scene.cpp:55)
==4964==by 0x4EA4431:
KWin::Wayland::WaylandOutput::renderCursorOpengl(KWin::Wayland::WaylandEglBackend*,
KWin::CursorSource*) (wayland_output.cpp:229)
==4964==by 0x4EA4804: UnknownInlinedFun (wayland_output.cpp:191)
==4964==by 0x4EA4804:
KWin::Wayland::WaylandOutput::setCursor(KWin::CursorSource*)
(wayland_output.cpp:184)
==4964==by 0x4CB6A41:
KWin::Compositor::addOutput(KWin::Output*)::{lambda()#2}::operator()() const
(composite.cpp:455)
==4964==by 0x4CBA685: KWin::Compositor::addOutput(KWin::Output*)
(composite.cpp:471)
==4964==by 0x4CBA987: KWin::Compositor::startupWithWorkspace()
(composite.cpp:383)
==4964==by 0x66F303A: QObject::event(QEvent*) (qobject.cpp:1347)
==4964==by 0x6E34CE4: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(in /usr/lib64/libQt5Widgets.so.5.15.8)
==4964==by 0x66C7647: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(qcoreapplication.cpp:1064)
==4964==by 0x66CAAF4: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1821)
==4964==  Address 0x4 is not stack'd, malloc'd or (recently) free'd
==4964== 
==4964== 
==4964== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==4964==  Access not within mapped region at address 0x4
==4964==at 0x4CC2EAD: UnknownInlinedFun (kwinglutils.h:421)
==4964==by 0x4CC2EAD: KWin::RenderTarget::size() const
(rendertarget.cpp:30)
==4964==by 0x4D69FEB: KWin::CursorScene::paint(KWin::RenderTarget*, QRegion
const&) (cursorscene.cpp:57)
==4964==by 0x4D6ED90: KWin::SceneDelegate::paint(KWin::RenderTarget*,
QRegion const&) (scene.cpp:55)
==4964==by 0x4EA4431:
KWin::Wayland::WaylandOutput::renderCursorOpengl(KWin::Wayland::WaylandEglBackend*,
KWin::CursorSource*) (wayland_output.cpp:229)
==4964==by 0x4EA4804: UnknownInlinedFun (wayland_output.cpp:191)
==4964==by 0x4EA4804:
KWin::Wayland::WaylandOutput::setCursor(KWin::CursorSource*)
(wayland_output.cpp:184)
==4964==by 0x4CB6A41:
KWin::Compositor::addOutput(KWin::Output*)::{lambda()#2}::operator()() const
(composite.cpp:455)
==4964==by 0x4CBA685: KWin::Compositor::addOutput(KWin::Output*)
(composite.cpp:471)
==4964==by 0x4CBA987:

[kwin] [Bug 465001] Multi monitor: Third monitor can not be used until after a seep / wake cycle

2023-02-22 Thread John

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

--- Comment #2 from John  ---
Modified to be reported under kwin / multimonitor as per blog post by Marco
Martin.

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

[kwin] [Bug 465001] Multi monitor: Third monitor can not be used until after a seep / wake cycle

2023-02-22 Thread John

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

John  changed:

   What|Removed |Added

  Component|general |multi-screen
Version|unspecified |5.26.90
   Assignee|neon-b...@kde.org   |kwin-bugs-n...@kde.org
Product|neon|kwin

-- 
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-02-22 Thread Raman Gupta

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

--- Comment #14 from Raman Gupta  ---
Here is the new `kscreen-doctor -o` output with my new hardware:

Output: 84 DisplayPort-0 enabled connected priority 2 DisplayPort Modes:
89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30
93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60
98:2048x1280@60 99:1920x1200@60 100:1920x1080@60 101:1920x1080@60
102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24
106:1920x1080@24 107:1600x1200@60 108:1680x1050@60 109:1600x900@60
110:1280x1024@75 111:1280x1024@60 112:1440x900@60 113:1280x800@60
114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60
119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60
124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 Geometry: 0,0
3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 85 DisplayPort-1 enabled connected priority 1 DisplayPort Modes:
89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30
93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60
98:2048x1280@60 99:1920x1200@60 100:1920x1080@60 101:1920x1080@60
102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24
106:1920x1080@24 107:1600x1200@60 108:1680x1050@60 109:1600x900@60
110:1280x1024@75 111:1280x1024@60 112:1440x900@60 113:1280x800@60
114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60
119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60
124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 Geometry: 3840,0
3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 86 DisplayPort-2 disabled disconnected priority 0 DisplayPort Modes:
Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange:
unknown
Output: 87 HDMI-A-0 enabled connected priority 3 HDMI Modes: 90:3840x2160@60*!
91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30
96:3840x2160@24 97:2560x1440@60 100:1920x1080@60 101:1920x1080@60
102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24
106:1920x1080@24 107:1600x1200@60 109:1600x900@60 110:1280x1024@75
111:1280x1024@60 114:1152x864@75 115:1280x720@60 116:1280x720@60
117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50
122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60
127:720x400@70 128:1920x1200@60 129:1680x1050@60 130:1440x900@60
131:1280x800@60 Geometry: 7680,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0
Vrr: incapable RgbRange: unknown

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

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

2023-02-22 Thread Andrew Udvare

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

--- Comment #23 from Andrew Udvare  ---
This bug is actually caused by using --march=native to GCC. Maybe it's specific
to my CPU or how my GCC is built. Regardless, it would seem the code path in
question is sensitive to CPU optimisations. I can compile a local Git clone
with -march=native and get the same behaviour. When -march=native is gone, the
problem is gone.

Can the section of code dealing with this be marked to avoid optimisation?

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

[kdenlive] [Bug 466284] New: Archiving a project does not save image files used as masks

2023-02-22 Thread Bernd

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

Bug ID: 466284
   Summary: Archiving a project does not save image files used as
masks
Classification: Applications
   Product: kdenlive
   Version: 22.12.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: bern...@yahoo.com
  Target Milestone: ---

SUMMARY
When archiving a project all assets are saved in their respective sub-folders
(for example ..\images, ..\audio). However, this is not the case for images
that are used as masks (for example in Shape Alpha effect)


STEPS TO REPRODUCE
1. Use a Shape Alpha effect with a .PNG image as the mask
2. Archive the project as a .ZIP file
3. Open the .ZIP file

OBSERVED RESULT
Only the .kdenlive project file is in the .ZIP file

EXPECTED RESULT
Besides the .kdenlive project file at least one folder with the .PNG file

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Pop!_OS 22.04
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep

2023-02-22 Thread Bob English

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

--- Comment #140 from Bob English  ---
(In reply to brian from comment #139)
> Well it was nice while it lasted.  As I reported two days ago, my system was
> working after the 5.27.0 upgrade for the first time since Christmas.  It
> worked for a couple days including power offs, reboots.  But I never let the
> system sleep -- until today.  Once the screens slept, the second screen
> would not return on wake up.  And now even reboots and cold-boots will not
> let me re-activate that second screen again.  Its back to square one. 
> 
> And there were no system changes applied during this time.
> 
> My system details:
> Operating System: Fedora Linux 37
> KDE Plasma Version: 5.27.0
> KDE Frameworks Version: 5.103.0
> Qt Version: 5.15.8
> Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit)
> Graphics Platform: X11
> Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
> Memory: 31.3 GiB of RAM
> Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
> Manufacturer: Gigabyte Technology Co., Ltd.

If you read this entire thread you would have found out there is a way to get
the monitor back.  At least manually until this is fixed:

If you delete any files with monitor layouts that are named like this:
c2cda156c1e54840478e5af385672567 from:

$ /home/USER/.local/share/kscreen/ 
and
$ /home/USER/.local/share/kscreen/outputs

and logging off/ back in (not sure) or as I did: reboot, so new versions of the
files will be regenerated as detected:  Viola', 2 Monitors again.  I did have
to change their orientation in the settings though.

Theres another workaround in this thread too.

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

[KScreen] [Bug 466136] Multi-screen arrangement scrambled on login with screens from the same model but serial numbers that differ by only one character at the end

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

Nate Graham  changed:

   What|Removed |Added

Summary|Multiscreen does not work   |Multi-screen arrangement
   |if the serialnumber is  |scrambled on login with
   |nearly the same |screens from the same model
   ||but serial numbers that
   ||differ by only one
   ||character at the end

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

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

Nate Graham  changed:

   What|Removed |Added

Summary|Each of two monitors are|Triple-monitor setup with
   |mis-identified as the other |all monitors being the same
   |one on login|model (with different
   ||serial numbers) gets
   ||scrambled on login

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

[kwin] [Bug 465424] Attaching external monitor turns both screens black and kwin_x11 hogs CPU until manually restarted

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

Nate Graham  changed:

   What|Removed |Added

Summary|Blank Screen on Attaching   |Attaching external monitor
   |External Monitor|turns both screens black
   ||and kwin_x11 hogs CPU until
   ||manually restarted
  Component|general |multi-screen

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

[Welcome Center] [Bug 466282] RFE: Add a live environment mode so Plasma Welcome is useful on live media

2023-02-22 Thread Neal Gompa

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

Neal Gompa  changed:

   What|Removed |Added

 CC||ad...@happyassassin.net,
   ||kpa...@redhat.com

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

[lattedock] [Bug 466283] New: Latte crashes when clicking on recent documents on Onze Menu 11

2023-02-22 Thread aliquo93

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

Bug ID: 466283
   Summary: Latte crashes when clicking on recent documents on
Onze Menu 11
Classification: Plasma
   Product: lattedock
   Version: unspecified
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: aliqu...@gmail.com
  Target Milestone: ---

Application: latte-dock (0.10.77)

Qt Version: 5.15.3
Frameworks Version: 5.98.0
Operating System: Linux 5.15.0-60-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.2 LTS
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
Latte crashes when clicking on recent documents on Onze Menu 11

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x7f02ff5500a5 in QV4::QObjectWrapper::create(QV4::ExecutionEngine*,
QObject*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#5  0x7f02ff551eeb in
QV4::QObjectWrapper::wrap_slowPath(QV4::ExecutionEngine*, QObject*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f02ff552192 in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f02ff55370a in
QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f02ff572b35 in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f02ff5775af in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f02ff50972e in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f02ff694905 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f02ff645beb in QQmlBoundSignalExpression::evaluate(void**) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f02ff646de8 in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f02ff679725 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7f02fdb232fc in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f02ffb071c6 in QQuickMouseArea::released(QQuickMouseEvent*) () at
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#17 0x7f02ffb08b95 in QQuickMouseArea::setPressed(Qt::MouseButton, bool,
Qt::MouseEventSource) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#18 0x7f02ffb09df5 in QQuickMouseArea::mouseReleaseEvent(QMouseEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#19 0x7f02ffa9bbd8 in QQuickItem::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#20 0x7f02fe894713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f02fdaebe3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f02ffab9f75 in
QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () at
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#23 0x7f02ffabb65f in
QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () at
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#24 0x7f02fe0315a5 in QWindow::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Gui.so.5
#25 0x7f02fe894713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7f02fdaebe3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f02fe025307 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#28 0x7f02fdffaa2c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#29 0x7f02f8bc1d6e in  () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#30 0x7f02fbda5d3b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x7f02fbdfa6c8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7f02fbda33e3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x7f02fdb450b8 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x7f02fdaea75b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x7f02fdaf2cf4 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x563b2f71f025 in main ()
[Inferior 1 (process 2586) detached]

Reported using DrKonqi

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

[Welcome Center] [Bug 466282] New: RFE: Add a live environment mode so Plasma Welcome is useful on live media

2023-02-22 Thread Neal Gompa

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

Bug ID: 466282
   Summary: RFE: Add a live environment mode so Plasma Welcome is
useful on live media
Classification: Applications
   Product: Welcome Center
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ngomp...@gmail.com
CC: n...@kde.org
  Target Milestone: ---

SUMMARY
Plasma Welcome does a great job of introducing people to Plasma, but it also
offers prompts and settings that are inappropriate when booted into a live
environment. However, Plasma Welcome can be useful for live environments, and
it'd be great for it to be configured with the ability to present a welcome to
tour Plasma or to launch the OS installer.


STEPS TO REPRODUCE
1. Boot an F38 nightly compose ISO, like this one:
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-38-20230222.n.0/compose/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-38-20230222.n.0.iso

OBSERVED RESULT
Plasma Welcome starts up and guides you through configuring Plasma in the live
environment as if it's a permanent installed one.

EXPECTED RESULT
When Plasma Welcome detects it's operating in a live environment (if
"rd.live.image" is in the kernel command-line, it's a live environment), it
starts in a different mode suitable for live environments, where it offers
either to give you a tour of Plasma or launch the distribution installer.

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

ADDITIONAL INFORMATION
This was discovered by Kamil Paral of Fedora QA:
https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/message/YY7AKUD2737IOCE47QEQDIBLEQUXUJ5V/

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

[KScreen] [Bug 465226] Input gets redirected to the 2nd monitor

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #8 from Nate Graham  ---
Can you attach a screenshot showing the layout in the KScreen KCM?

Does it happen on Wayland?

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

[kwin] [Bug 466281] Nested kwin_wayland crashed in KWin::GLFramebuffer::size in VMs using the llvmpipe driver

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep

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

--- Comment #139 from br...@fodvo.org ---
Well it was nice while it lasted.  As I reported two days ago, my system was
working after the 5.27.0 upgrade for the first time since Christmas.  It worked
for a couple days including power offs, reboots.  But I never let the system
sleep -- until today.  Once the screens slept, the second screen would not
return on wake up.  And now even reboots and cold-boots will not let me
re-activate that second screen again.  Its back to square one. 

And there were no system changes applied during this time.

My system details:
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.

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

[kwin] [Bug 466281] New: Nested kwin_wayland crashed in KWin::GLFramebuffer::size in VMs using the llvmpipe driver

2023-02-22 Thread Matt Fagnani

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

Bug ID: 466281
   Summary: Nested kwin_wayland crashed in
KWin::GLFramebuffer::size in VMs using the llvmpipe
driver
Classification: Plasma
   Product: kwin
   Version: 5.27.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 156628
  --> https://bugs.kde.org/attachment.cgi?id=156628=edit
The full trace of all threads of the nested kwin_wayland crash.

SUMMARY

I booted the Fedora 38 KDE Plasma live image
Fedora-KDE-Live-x86_64-38-20230221.n.1.iso in a QEMU/KVM VM using GNOME Boxes
with 3D acceleration disabled using the llvmpipe driver from
mesa-dri-drivers-23.0.0~rc4-3.fc38.x86_64.
Plasma 5.27.0 on Wayland started. I started Konsole. I tried to run a nested
kwin_wayland session using the instructions at
https://community.kde.org/KWin/Wayland
export $(dbus-launch)
kwin_wayland --xwayland 

The nested kwin_wayland window didn't appear except for a Wayland icon in the
task manager. The following output was in Konsole which showed some Permission
denied errors and a segmentation fault of kwin_wayland.

$ kwin_wayland --xwayland
No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is
set
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor
is running
libEGL warning: egl: failed to create dri2 screen
OpenGL vendor string:   Mesa
OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits)
OpenGL version string:  4.5 (Core Profile) Mesa 23.0.0-rc4
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class:  Unknown
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   23.0
Linux kernel version:   6.2
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kwin_core: Parse error in tiles configuration for monitor
"7fb8c463-c102-5440-8fb7-5253b26b5d9c" : "illegal value" Creating default setup
kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker"
kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate"
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
kwin_wayland_backend: Failed to allocate a buffer for an output layer
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
kwin_wayland_backend: Failed to allocate a buffer for an output layer
(WW) Option "-listen" for file descriptors is deprecated
Please use "-listenfd" instead.
(WW) Option "-listen" for file descriptors is deprecated
Please use "-listenfd" instead.
libEGL warning: egl: failed to create dri2 screen
libEGL warning: NEEDS EXTENSION: falling back to kms_swrast
(EE) could not connect to wayland server
Segmentation fault (core dumped)

The nested kwin_wayland crashed in KWin::GLFramebuffer::size. The crash
might've been due to a null pointer dereference since this=0x0.

Core was generated by `kwin_wayland --xwayland'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f56fe3fcead in KWin::GLFramebuffer::size (this=0x0) at
/usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/libkwineffects/kwinglutils.h:421
421 return mSize;
[Current thread is 1 (Thread 0x7f56fdaa9e40 (LWP 4389))]

(gdb) bt
#0  0x7f56fe3fcead in KWin::GLFramebuffer::size (this=0x0)
at
/usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/libkwineffects/kwinglutils.h:421
#1  KWin::RenderTarget::size (this=0x7ffe85125500)
at /usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/core/rendertarget.cpp:30
#2  0x7f56fe4a3fec in KWin::CursorScene::paint
(this=this@entry=0x5564ab4fd200, 
renderTarget=renderTarget@entry=0x7ffe85125500, region=...)
at /usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/scene/cursorscene.cpp:57
#3  0x7f56fe4a8d91 in KWin::SceneDelegate::paint
(this=this@entry=0x5564ab747590, 
renderTarget=renderTarget@entry=0x7ffe85125500, region=...)
at /usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/scene/scene.cpp:55
#4  0x7f56fe5de432 in KWin::Wayland::WaylandOutput::renderCursorOpengl
(this=this@entry=0x5564aaef17f0, 
backend=, source=source@entry=0x5564ab6448e0)
at
/usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/backends/wayland/wayland_output.cpp:229
#5  0x7f56fe5de805 in KWin::Wayland::WaylandOutput::setCursor
(source=0x5564ab6448e0, this=0x5564aaef17f0)
at
/usr/src/debug/kwin-5.27.0-2.fc38.x86_64/src/backends/wayland/wayland_output.cpp:191
#6  KWin::Wayland::WaylandOutput::setCursor (this=0x5564aaef17f0,
source=0x5564ab6448e0)
at

[NeoChat] [Bug 466280] New: Add ability to copy room ID from room settings window

2023-02-22 Thread Justin Zobel

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

Bug ID: 466280
   Summary: Add ability to copy room ID from room settings window
Classification: Applications
   Product: NeoChat
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: justin.zo...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Currently, you cannot select the text of the room ID.

I'd like to be able to select it with the cursor or a button next to it to copy
it to the clipboard.

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

[kwin] [Bug 466279] New: kwin_wayland crashes in KWin::TabBox::SwitcherItem::visibleChanged() when alt-tabbing with 5 or more items and using Large Icons task switcher

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

Bug ID: 466279
   Summary: kwin_wayland crashes in
KWin::TabBox::SwitcherItem::visibleChanged() when
alt-tabbing with 5 or more items and using Large Icons
task switcher
Classification: Plasma
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: tabbox
  Assignee: kwin-bugs-n...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

I use the Large Icons task Switcher. As of today's git master everything,
kwin_wayland reproducibly crashes when I press Alt+Tab while there are 5 or
more windows or apps open.

If I switch to the default Breeze task switcher, this condition does not
trigger a crash. This is 100% reproducible for me. It started happening today,
and I alt tab hundreds of times a day, so I strongly suspect the regression was
introduced today. Will bisect KWin shortly.

Here's the full backtrace:

#0  QOpenGLContext::surface() const (this=this@entry=0x0) at
kernel/qopenglcontext.cpp:1078
#1  0x7f985fe2b18f in qsg_device_pixel_ratio (ctx=0x0) at
scenegraph/qsgdefaultglyphnode_p.cpp:99
#2  QSGTextMaskMaterial::updateCache(QFontEngine::GlyphFormat)
(this=this@entry=0x24f7e90, glyphFormat=QFontEngine::Format_A32, 
glyphFormat@entry=QFontEngine::Format_None) at
scenegraph/qsgdefaultglyphnode_p.cpp:781
#3  0x7f985fe2b422 in QSGTextMaskMaterial::init(QFontEngine::GlyphFormat)
(this=this@entry=0x24f7e90,
glyphFormat=glyphFormat@entry=QFontEngine::Format_None)
at scenegraph/qsgdefaultglyphnode_p.cpp:749
#4  0x7f985fe2b4b0 in
QSGTextMaskMaterial::QSGTextMaskMaterial(QSGRenderContext*, QVector4D const&,
QRawFont const&, QFontEngine::GlyphFormat)
(this=this@entry=0x24f7e90, rc=, color=..., font=...,
glyphFormat=glyphFormat@entry=QFontEngine::Format_None) at
scenegraph/qsgdefaultglyphnode_p.cpp:718
#5  0x7f985fe276d6 in QSGDefaultGlyphNode::update() (this=0x25ac280)
at scenegraph/qsgdefaultglyphnode.cpp:107
#6  0x7f985fec64d4 in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun
const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*)
(this=this@entry=0x11a0ee0, position=..., glyphs=..., color=...,
style=style@entry=QQuickText::Normal, styleColor=..., parentNode=0x0) at
items/qquicktextnode.cpp:117
#7  0x7f985fecb8a8 in
QQuickTextNodeEngine::addToSceneGraph(QQuickTextNode*, QQuickText::TextStyle,
QColor const&)
(this=this@entry=0x7ffe6df8c6c0, parentNode=parentNode@entry=0x11a0ee0,
style=style@entry=QQuickText::Normal, styleColor=...) at
items/qquicktextnodeengine.cpp:793
#8  0x7f985fec7538 in QQuickTextNode::addTextLayout(QPointF const&,
QTextLayout*, QColor const&, QQuickText::TextStyle, QColor const&, QColor
const&, QColor const&, QColor const&, int, int, int, int)
(this=this@entry=0x11a0ee0, position=...,
textLayout=textLayout@entry=0x2a60138, color=..., style=QQuickText::Normal,
styleColor=..., anchorColor=..., selectionColor=..., selectedTextColor=...,
selectionStart=-1, selectionEnd=-1, lineStart=0, lineCount=) at
items/qquicktextnode.cpp:287
#9  0x7f985fec5f61 in QQuickText::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*)
(this=0x24d2c80, oldNode=, data=) at
items/qquicktext.cpp:2500
#10 0x7f985fea62d8 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*)
(this=0x31396c0, item=0x24d2c80) at items/qquickwindow.cpp:3888
#11 0x7f985fea6802 in QQuickWindowPrivate::updateDirtyNodes()
(this=this@entry=0x31396c0)
at items/qquickwindow.cpp:3633
#12 0x7f985fea83a1 in QQuickWindowPrivate::syncSceneGraph()
(this=this@entry=0x31396c0)
at items/qquickwindow.cpp:524
#13 0x7f985fe23207 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
 (this=0x3194af0, window=) at
scenegraph/qsgrenderloop.cpp:752
#14 0x7f985fe250e2 in
QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*)
(this=0x3194af0, window=) at
scenegraph/qsgrenderloop.cpp:853
#15 0x7f985ef76365 in QWindow::event(QEvent*) (this=0x1f5fde0,
ev=)
at kernel/qwindow.cpp:2455
#16 0x7f985d7aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x1f5fde0, e=0x7ffe6df8f070) at
kernel/qapplication.cpp:3640
#17 0x7f985ea9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x1f5fde0, event=0x7ffe6df8f070) at
kernel/qcoreapplication.cpp:1064
#18 0x7f985ef6c085 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
(e=0x2c179b0) at kernel/qguiapplication.cpp:3254
#19 0x7f985ef49f1c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#20 0x7f985ef4a2a0 in
QWindowSystemInterface::flushWindowSystemEvents(QFlags)
(flags=flags@entry=...) at

[neon] [Bug 466278] New: Missing dependency for 'kweather'

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

Bug ID: 466278
   Summary: Missing dependency for 'kweather'
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: robloka...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

The 'kweather' package is missing the dependency
'qml-module-org-kde-kirigami-addons-labs-mobileform'

This package is needed for the settings menu to open in kweather

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

[kwin] [Bug 465456] kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen

2023-02-22 Thread Vlad Zahorodnii

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

Vlad Zahorodnii  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/da26deaa5c84
   ||3ef303ef9f1b9f0cd3d341c5c5f
   ||5
 Status|ASSIGNED|RESOLVED

--- Comment #4 from Vlad Zahorodnii  ---
Git commit da26deaa5c843ef303ef9f1b9f0cd3d341c5c5f5 by Vlad Zahorodnii.
Committed on 22/02/2023 at 19:39.
Pushed by vladz into branch 'master'.

backends/libinput: Fix crash upon receiving motion absolute events

The input events can be processed when the workspace is not available,
e.g. during startup or shutdown, so add a corresponding guard.

As a long term plan, we need to decouple Workspace from low-level input
backend parts, but it will be a too invasive change for now.
Related: bug 449317

M  +3-1src/backends/libinput/connection.cpp

https://invent.kde.org/plasma/kwin/commit/da26deaa5c843ef303ef9f1b9f0cd3d341c5c5f5

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

[kwin] [Bug 449317] (SEGV) KWin Wayland crashed in KWin::Workspace::geometry when existing fullscreen in VirtualBox

2023-02-22 Thread Vlad Zahorodnii

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

Vlad Zahorodnii  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/da26deaa5c84
   ||3ef303ef9f1b9f0cd3d341c5c5f
   ||5
 Status|ASSIGNED|RESOLVED

--- Comment #5 from Vlad Zahorodnii  ---
Git commit da26deaa5c843ef303ef9f1b9f0cd3d341c5c5f5 by Vlad Zahorodnii.
Committed on 22/02/2023 at 19:39.
Pushed by vladz into branch 'master'.

backends/libinput: Fix crash upon receiving motion absolute events

The input events can be processed when the workspace is not available,
e.g. during startup or shutdown, so add a corresponding guard.

As a long term plan, we need to decouple Workspace from low-level input
backend parts, but it will be a too invasive change for now.
Related: bug 465456

M  +3-1src/backends/libinput/connection.cpp

https://invent.kde.org/plasma/kwin/commit/da26deaa5c843ef303ef9f1b9f0cd3d341c5c5f5

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

[KScreen] [Bug 466187] Screen priorities get scrambled after switching to a TTY and back

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

Nate Graham  changed:

   What|Removed |Added

Summary|Screen priorities get   |Screen priorities get
   |scrambled after switching   |scrambled after switching
   |to a TTY and back.  |to a TTY and back

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

[KScreen] [Bug 466187] Screen priorities get scrambled after switching to a TTY and back.

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
The output of `kscreen-doctor-o` is the same in the before and after; both say
that HDMI-A-1 is the primary.

Is this the way it actually is, or was that a copy-paste error?

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

[plasma-systemmonitor] [Bug 466277] USB sensor devices name changes causes sensors not to be found on nearly every boot

2023-02-22 Thread Ville Aakko

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

--- Comment #1 from Ville Aakko  ---
Created attachment 156627
  --> https://bugs.kde.org/attachment.cgi?id=156627=edit
A screenshot demonstrating the issue and cause

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

[kweather] [Bug 466273] Settings menu does not open

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

robloka...@gmail.com changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #4 from robloka...@gmail.com ---
Alright, thanks.

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

[plasma-systemmonitor] [Bug 466277] New: USB sensor devices name changes causes sensors not to be found on nearly every boot

2023-02-22 Thread Ville Aakko

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

Bug ID: 466277
   Summary: USB sensor devices name changes causes sensors not to
be found on nearly every boot
Classification: Plasma
   Product: plasma-systemmonitor
   Version: 5.27.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: ville.aa...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Plasma System Monitor does not find the sensors on a USB monitoring device
after a reboot.

This is because the name of the device in lmsensors changes every boot. It has
a suffix in case of USB devices of the form -hid-X-Y (or similar), where X and
Y change. In my case, the device is a Corsair Commander Pro.

Plasma System Monitor could be more intelligent in finding the right device.
The devices have a name node in /sys/class/hwmon/hwmon?/name, but I'm not sure
if this is exposed to System Monitor (does it use libsensors?).

This bug is very similar to the one I've reported against ksysguard:
https://bugs.kde.org/show_bug.cgi?id=438031

STEPS TO REPRODUCE
1. Add sensors from a USB sensoring device into Plasma System Monitor
2. Reboot
3. Re-open Plasma System Monitor.

OBSERVED RESULT

More likely than not, the sensors have not been found (retry from step 2 if the
bug didn't trigger by chance).

EXPECTED RESULT

The sensors should be found.

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

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

[kweather] [Bug 466273] Settings menu does not open

2023-02-22 Thread Devin Lin

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

--- Comment #3 from Devin Lin  ---
Looks like your distribution doesn't have kirigami-addons as a dependency of
kweather, you can try manually installing that package. This is a bug that
needs to be reported to your distribution.

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

[kweather] [Bug 466273] Settings menu does not open

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

--- Comment #2 from robloka...@gmail.com ---
qrc:/qml/settings/SettingsWindow.qml:37:13: Type SettingsComponent unavailable
qrc:/qml/settings/SettingsComponent.qml:13:1: module
"org.kde.kirigamiaddons.labs.mobileform" is not installed
qrc:/qml/main.qml:117: TypeError: Cannot call method 'close' of null

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

[kwin] [Bug 466179] Graphical glitches after minimizing windows using multi-screen setup

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

Nate Graham  changed:

   What|Removed |Added

Summary|Artifacts from minimized|Graphical glitches after
   |windows are visible and |minimizing windows using
   |flickering  |multi-screen setup

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

[kwin] [Bug 466179] Artifacts from minimized windows are visible and flickering