[okular] [Bug 487992] New: Add an option to make highlighters sticky, instead of single-action

[Steve Kelem]

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

Bug ID: 487992
   Summary: Add an option to make highlighters sticky, instead of
single-action
Classification: Applications
   Product: okular
   Version: 23.08.5
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: st...@kelem.net
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Make the highlighters "sticky"

STEPS TO REPRODUCE
1. I highlight a lot of text, particularly when balancing my checkbook via bank
statements.
2. You get to hightlight only once after clicking on a (yellow or green)
highlighter.
3. 

OBSERVED RESULT
After you highlight one item, the highlighter is de-selected, and Text
Selection becomes selected, meaning you have to move the mouse over to select
the highlighter again.

EXPECTED RESULT
It would be really productive if I could double-click the highlighter to have
it remain active until either another tool is selected or I single-click the
highlighter.

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

ADDITIONAL INFORMATION
Please? and Thank you!

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

[kdeplasma-addons] [Bug 481922] The Quick Launch icons on the taskbar cannot be freely rearranged

[Steve Therrien]

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

Steve Therrien  changed:

   What|Removed |Added

 CC||kdeb...@stevetherrien.ca

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

[plasma-browser-integration] [Bug 487303] plasma-brower-integration causes Cloudflare to lock out humans

[Steve Zhu]

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

Steve Zhu  changed:

   What|Removed |Added

 CC||steve.ziyao...@icloud.com

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

[krita] [Bug 482791] appmenu on title bar does not open in krita window

[Steve Cossette]

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

--- Comment #4 from Steve Cossette  ---
Forgot to add system details, sorry:

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
Memory: 61.9 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670E AORUS PRO X
System Version: -CF

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

[krita] [Bug 482791] appmenu on title bar does not open in krita window

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
Created attachment 169679
  --> https://bugs.kde.org/attachment.cgi?id=169679=edit
Krita, no menu

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

[krita] [Bug 482791] appmenu on title bar does not open in krita window

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #2 from Steve Cossette  ---
(In reply to stefanfunk1998 from comment #1)
> im experiencing a issue with krita and the appmenu myself, but in the
> opposite constellation: i have a global menu set up, but since updating to
> plasma 6, the global menu doesnt show for krita, but krita open normally.
> maybe has something to do with the QT version Krita is using?

Same thing here. I'll upload a screenshot to demonstrate.

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

[Plasma Bigscreen] [Bug 480929] Plasma Bigscreen fails to start

[Steve Cossette]

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

--- Comment #5 from Steve Cossette  ---
(In reply to Plata from comment #4)
> In this case it would probably better to delete the Fedora package until it
> works again.
> 
> Is there an issue to track Plasma 6 support?

Yeah we did retire it for a bit as they was no longer a maintainer. One came
back, but I'm not sure of the project's status.

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

[Plasma Bigscreen] [Bug 480929] Plasma Bigscreen fails to start

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
(In reply to Plata from comment #2)
> Just saw that the plasma-bigscreen package version is 5.27.80. Can that work
> with everything else Plasma 6?

It's still based on qt5, so yeah it very much wont work on plasma 6

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

[neon] [Bug 486424] New: USB drive corrupts itself if you edit pictures too quickly

[Steve Zakulec]

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

Bug ID: 486424
   Summary: USB drive corrupts itself if you edit pictures too
quickly
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: spzaku...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
If you edit photos quickly enough on an external drive, eventually the file
listing shows less files than you started with even if you did no delete
options.

STEPS TO REPRODUCE
1. Put a large number (68 or so in my case) of TIFF scans on an NTFS-formatted
USB stick. You can download https://archive.org/details/Ford-Times-May-1978 and
extract the CBZ file to a drive to recreate my setup.
2. Open the first file in Gwenview.
3. Make any crop to that file and save it.
4. Using the keyboard shortcuts for crop & save, edit photos until you either
wrap around to the first photo, or you notice that the number of files Gwenview
shows in the folder is not the number you started with. 

OBSERVED RESULT
You end up with a USB drive with corruption- files that were present are now no
longer accessible until you repair the drive in Windows with ChkDsk.

EXPECTED RESULT
You should be able to crop the entire set of files without the drive corrupting
itself.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 80SA
System Version: LENOVO_IDEAPAD

ADDITIONAL INFORMATION
I also filed this as https://bugs.kde.org/show_bug.cgi?id=481470, since I
wasn't sure at the time if this was a Gwenview or KDE Neon bug- that has
additional information.

USB Drive is a Kingston Technology DataTraveler Max, ID 0951:177f, formatted
NTFS.

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

[Steve Ramage]

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

--- Comment #58 from Steve Ramage  ---
> Lol, just have a "Nuke X11" button on a shortcut :)). But speaking of which, 
> it would be worth confirming for the others that would want a dirty fix in 
> the meantime, does killing kwin_x11 restart the applications smoothly from 
> where they were left off? 

Yes sorry, to be clear when I do that, it takes about 5 seconds but my session
continues without any negative side effects, the side effects are minimum. All
my applications seem unaffected, no crashes or anything.

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

[Steve Ramage]

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

Steve Ramage  changed:

   What|Removed |Added

 CC||k...@sjrx.net

--- Comment #56 from Steve Ramage  ---
Just wanted to say this is affecting me as  well, how I fix it , is by killing
kwin_x11  that seems to recover everything. Although maybe that is horrible.

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

[Merkuro] [Bug 482482] Merkuro Calandar starting wrong week in week-view

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
Sorry for the big screenshot... I forgot to crop it before I posted and it
seems Bugzilla's not allowing me to replace it. But ignore the Google search in
the background; if you look at the screenshot, Merkuro shows Jan 7th -> 13th as
being week 1 while the system calendar shows Dec 31st to Jan 6th as being Week
1.

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

[Merkuro] [Bug 482482] Merkuro Calandar starting wrong week in week-view

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #2 from Steve Cossette  ---
Created attachment 168776
  --> https://bugs.kde.org/attachment.cgi?id=168776=edit
Calendar

I can confirm that this is also in Fedora KDE.

Now, how to tell in what condition the first week of a year starts, that I
don't know how to check that. It might be a regional thing.

But there seems to be a discrepancy between the different KDE components, as in
the following screenshot, the Plasma Calendar and Merkuro disagree:

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

[frameworks-solid] [Bug 416065] Dolphin fails to mount LVM volumes locked behind a LUKS encryption

[Steve Leung]

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

Steve Leung  changed:

   What|Removed |Added

 CC||evet...@gmail.com

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

[digikam] [Bug 485332] Some images were not correlated even though GPS coordinates were available for the time they were taken

[Steve Franks]

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

--- Comment #9 from Steve Franks  ---
(In reply to Maik Qualmann from comment #6)
> I looked at the GPX data, you are in UTC time, +1 hour daylight saving time.
> I think you didn't set your camera to daylight saving time.
> 
> Maik

That's probably true. Sorry to have bothered you.
Steve

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

[plasmashell] [Bug 485271] plasmashell crashes in wl_abort() with interaction to the panel ("Tried to add event to destroyed queue")

[Catty Steve]

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

Catty Steve  changed:

   What|Removed |Added

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

--- Comment #5 from Catty Steve  ---
Trace log attached.
Maybe I need to change the bug status manually?

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

[digikam] [Bug 485332] Some images were not correlated even though GPS coordinates were available for the time they were taken

[Steve Franks]

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

--- Comment #1 from Steve Franks  ---
The photos are too big to upload here.
digikam metadata shows that one was taken at 11:45:29, the other at 11:45:37.

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

[digikam] [Bug 485332] New: Some images were not correlated even though GPS coordinates were available for the time they were taken

[Steve Franks]

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

Bug ID: 485332
   Summary: Some images were not correlated even though GPS
coordinates were available for the time they were
taken
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Geolocation-Correlator
  Assignee: digikam-bugs-n...@kde.org
  Reporter: steve...@gmail.com
  Target Milestone: ---

Created attachment 168348
  --> https://bugs.kde.org/attachment.cgi?id=168348=edit
GPX Track

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
I took some photos today and used digikam geolocation editor to geotag them.
This is something that I have done successfully many times.
Two of the 21 images were not located using my default Interpolate setting of
00:05:00. They were correctly located when the time was increased to 00:06:00.

STEPS TO REPRODUCE
1.  Save a GPX file containing a track recorded at the same time as a number of
photos were taken.
2.  Use digikam geolocation editor to match the photos to the track to
establish their coordinates.
3.  

OBSERVED RESULT
Two images were not matched against the GPX track.

EXPECTED RESULT
All images matched.

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

ADDITIONAL INFORMATION
I always allow a margin of 5 minutes for interpolating images in case the
Garmin eTrex 22x loses signal, as can happen in inclement weather.  digikam
shows the time that the two photos were taken was 10th Apr 2024 @ 11:45. The
track shows 5 points during that minute (11:45).

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

[kwin] [Bug 484992] Task Switcher does not get focus for XWayland windows and tab gets "forwarded" to original window

[Steve Therrien]

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

Steve Therrien  changed:

   What|Removed |Added

 CC||kdeb...@stevetherrien.ca

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

[plasmashell] [Bug 485271] plasmashell crashes in wl_abort() with interaction to the panel ("Tried to add event to destroyed queue")

[Catty Steve]

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

--- Comment #3 from Catty Steve  ---
Created attachment 168322
  --> https://bugs.kde.org/attachment.cgi?id=168322=edit
debug info from kwin

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

[plasmashell] [Bug 485271] plasmashell crashes in wl_abort() with interaction to the panel ("Tried to add event to destroyed queue")

[Catty Steve]

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

--- Comment #2 from Catty Steve  ---
Created attachment 168321
  --> https://bugs.kde.org/attachment.cgi?id=168321=edit
full trace log

This is the full backtrace log for /usr/bin/plasmashell.

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

[plasmashell] [Bug 485271] plasmashell crashes in wl_abort() with interaction to the panel ("Tried to add event to destroyed queue")

[Catty Steve]

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

Catty Steve  changed:

   What|Removed |Added

 Attachment #168321|0   |1
is obsolete||

--- Comment #4 from Catty Steve  ---
Created attachment 168323
  --> https://bugs.kde.org/attachment.cgi?id=168323=edit
Full trace log, updated.

full trace log for /usr/bin/plasmashell

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

[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop

[Steve Therrien]

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

Steve Therrien  changed:

   What|Removed |Added

 CC||kdeb...@stevetherrien.ca

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

[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators::paint()

[Steve Cossette]

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

--- Comment #6 from Steve Cossette  ---
(In reply to Steve Cossette from comment #5)
> So, this is very easily triggerable. Seems to happen if you are asking
> System Monitor to show details too quick, and it just dies from
> embarrassment (My interpretation of it, anyway XD)
> 
> Steps to reproduce (Pretty much fool-proof on my system):
> 
> 1- Open System Monitor.
> 2- Go to Applications section. (There needs to be a decent amount of entries
> there)
> 3- Open the Details sidebar.
> 4- Click on either the top of the line item, or the bottom of the line item,
> and use the Arrow keys on your keyboard to just quickly scroll through the
> list.
> 
> For me that just instantly crashes the app.

I don't think this is a critical bug because it's a result of the user using
the app in an unintended way. (If they don't click-spam entries OR scroll
through the list with the up/down arrows, this doesn't seem to occur)

But it is a bug nonetheless :)

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

[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators::paint()

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #5 from Steve Cossette  ---
So, this is very easily triggerable. Seems to happen if you are asking System
Monitor to show details too quick, and it just dies from embarrassment (My
interpretation of it, anyway XD)

Steps to reproduce (Pretty much fool-proof on my system):

1- Open System Monitor.
2- Go to Applications section. (There needs to be a decent amount of entries
there)
3- Open the Details sidebar.
4- Click on either the top of the line item, or the bottom of the line item,
and use the Arrow keys on your keyboard to just quickly scroll through the
list.

For me that just instantly crashes the app.

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

[plasmashell] [Bug 485271] New: plasmashell crashes with interaction to the panel

[Catty Steve]

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

Bug ID: 485271
   Summary: plasmashell crashes with interaction to the panel
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: cattysteve89...@163.com
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
plasmashell crashes after clicking on icon, clicking on built-in widgets (like
network or battery) and sometimes without interaction.

STEPS TO REPRODUCE
1. Click on icon or widgets several times.

OBSERVED RESULT
Crashes.

EXPECTED RESULT
Doesn't crash.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Kernel Version: 6.8.4-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800U with Radeon Graphics
Memory: 13.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82QF
System Version: Yoga 14c ARB7

ADDITIONAL INFORMATION
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7d64e8aab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2  0x7d64e8a5a6c8 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
#3  0x7d64eb7aa43f in KCrash::defaultCrashHandler (sig=6) at
/usr/src/debug/kcrash/kcrash-6.0.0/src/kcrash.cpp:586
#4  0x7d64e8a5a770 in  () at /usr/lib/libc.so.6
#5  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x7d64e8aab393 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#7  0x7d64e8a5a6c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7d64e8a424b8 in __GI_abort () at abort.c:79
#9  0x7d64eb8374f2 in wl_abort (fmt=fmt@entry=0x7d64eb83c6d8 "Tried to add
event to destroyed queue\n")
at ../wayland-1.22.0/src/wayland-util.c:462
#10 0x7d64eb8397e2 in queue_event (len=,
display=0x633ad13d1e60) at ../wayland-1.22.0/src/wayland-client.c:1575
#11 read_events (display=0x633ad13d1e60) at
../wayland-1.22.0/src/wayland-client.c:1670
#12 wl_display_read_events (display=0x633ad13d1e60) at
../wayland-1.22.0/src/wayland-client.c:1753
#13 0x7d64ead7eb40 in QtWaylandClient::EventThread::run
(this=0x633ad13d0780)
at
/usr/src/debug/qt6-wayland/qtwayland-everywhere-src-6.6.3/src/client/qwaylanddisplay.cpp:193
#14 0x7d64e92a15d3 in operator() (__closure=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.3/src/corelib/thread/qthread_unix.cpp:324
#15 (anonymous
namespace)::terminate_on_exception >
(t=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.3/src/corelib/thread/qthread_unix.cpp:260
#16 QThreadPrivate::start (arg=0x633ad13d0780)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.3/src/corelib/thread/qthread_unix.cpp:283
#17 0x7d64e8aa955a in start_thread (arg=) at
pthread_create.c:447
#18 0x7d64e8b26a3c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

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

[Active Window Control] [Bug 483998] Image from an IntelliJ window but focus and actions happen on another one (as if 100% transparent but on top)

[Steve Therrien]

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

Steve Therrien  changed:

   What|Removed |Added

 CC||kdeb...@stevetherrien.ca

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

[kwin] [Bug 484664] New: Pinning windows can sometimes result in the window going out of bounds.

[Steve Cossette]

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

Bug ID: 484664
   Summary: Pinning windows can sometimes result in the window
going out of bounds.
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

Created attachment 167888
  --> https://bugs.kde.org/attachment.cgi?id=167888=edit
Stacktrace, and some system logs

So, Plasma has a feature where you can "snap" windows to the left, right, top
of the screen. Heck, I think you can even snap it to a corner of a screen.

Seems on Plasma 6, it can sometimes happen where the window will snap out of
bounds.

I made a video of the bug: https://youtu.be/TP_Wisn1DLw

My setup is a dual monitor setup, and the video is taken from the right monitor
(If it matters, that screen is NOT the primary screen, as set in KDE's Settings
Manager. It does have HDR enabled too.)

You'll see in the video that it ends abruptly after I minimized the window. At
that point, kwin_wayland crashed, but it seems to have been in a response to
something happening in the kernel, strangely. I attached part of the system
logs to this bug.

Here's what I got installed:

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

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

[frameworks-bluez-qt] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6

[Steve Cossette]

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

--- Comment #9 from Steve Cossette  ---
So, this is unlikely to be KDE's fault. I tried to restart the bluetooth
service, and after about 20 seconds, it restarted and bluetooth came back.
Maybe a problem with bluetoothd?

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

[frameworks-bluez-qt] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

  Component|general |general
 Resolution|UPSTREAM|---
   Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org
 Status|RESOLVED|REPORTED
Product|kde |frameworks-bluez-qt
Version|unspecified |6.0.0

--- Comment #8 from Steve Cossette  ---
I'm going to reset this to bluez-qt, seems more related to this. I did some
more additional testing:

As the bug reporter said, this occured at first when the system goes in suspend
mode (Meta+L, let the screens turn off) for a while.

But I was also able to reproduce this without letting the system go to
sleep/lock, by simply turning off the bluetooth mouse using the power toggle
behind it.

So, as I do have a backup mouse, I decided to go in system settings, in the
bluetooth settings, and turned off bluetooth. Waited 10 seconds, and turned it
back on.

No more bluetooth. The mouse no longer connects. Going in the system logs, I
see the following:

Mar 20 13:38:15 steve-desktop systemsettings[6479]: kf.bluezqt: PendingCall
Error: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."

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

[kde] [Bug 483944] Mx master's scroll wheel slows down after a while since upgrading to Plasma 6

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #6 from Steve Cossette  ---
I can also confirm this on Fedora 40, on Wayland. 6.0.2 as well.

I litterally have to roll the mousewheel like mad if I want to scroll. My
scrolling finger is growing muscles! XD

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

[plasmashell] [Bug 483837] New: Intermittent kioslave5 / plasma crashes

[Steve Jaques]

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

Bug ID: 483837
   Summary: Intermittent kioslave5 / plasma crashes
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: stevenjaq...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.6.20+rpt-rpi-v8 aarch64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Pi4 4GB, arm64 PiOs/Debian Bookworm, KDE installed via repos as kde-full.
Using Freetube in popup mode, Dolphin connected to server share via SMB.
Desktop effects enabled, except CUBE (WHICH I REALLY MISS).
Wayland Compositor, probably other stuff I don't know about.
Plasmashell recovers on its own after around 30 secs or so.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

   PID: 243843 (plasmashell)
   UID: 1000 (pi)
   GID: 1000 (pi)
Signal: 6 (ABRT)
 Timestamp: Sun 2024-03-17 10:34:40 EDT (2min 40s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (pi)
   Boot ID: e49b2ecf1d6542738e80710c0d1d695f
Machine ID: 8ce31457e9454d6a901622db18ef4e45
  Hostname: raspberrypi
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.e49b2ecf1d6542738e80710c0d1d695f.243843.171068608000.zst
(present)
  Size on Disk: 39.5M
   Message: Process 243843 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.arm64
Module libudev.so.1 from deb systemd-252.22-1~deb12u1.arm64
Stack trace of thread 485202:
#0  0x007fb8d30a10 __pthread_kill_implementation (libc.so.6
+ 0x80a10)
#1  0x007fb8cea76c __GI_raise (libc.so.6 + 0x3a76c)
#2  0x007fbb57506c _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x506c)
#3  0x007fbbc8f7b0 n/a (linux-vdso.so.1 + 0x7b0)
#4  0x007fbbc8f7b0 n/a (linux-vdso.so.1 + 0x7b0)
#5  0x007fb8d309fc __pthread_kill_implementation (libc.so.6
+ 0x809fc)
#6  0x007f5569ef00 n/a (n/a + 0x0)
ELF object binary architecture: AARCH64

[New LWP 485202]
[New LWP 482817]
[New LWP 352065]
[New LWP 352071]
[New LWP 485200]
[New LWP 315684]
[New LWP 352057]
[New LWP 321903]
[New LWP 243916]
[New LWP 243845]
[New LWP 352067]
[New LWP 461329]
[New LWP 485199]
[New LWP 243843]
[New LWP 482822]
[New LWP 243906]
[New LWP 314555]
[New LWP 315864]
[New LWP 352056]
[New LWP 352068]
[New LWP 243844]
[New LWP 352066]
[New LWP 243853]
[New LWP 243855]
[New LWP 352070]
[New LWP 244111]
[New LWP 461331]
[New LWP 485198]
[New LWP 461328]
[New LWP 352064]
[New LWP 485201]
[New LWP 352069]
[New LWP 243886]
[New LWP 243846]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=546893852416, signo=signo@entry=6,
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
[Current thread is 1 (Thread 0x7f5569ef00 (LWP 485202))]
[Current thread is 26 (Thread 0x7f5de6ef00 (LWP 244111))]

Thread 34 (Thread 0x7faaacef00 (LWP 243846)):
#0  0x007fb8d2b6d4 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x558027dc18) at
./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0,
clockid=0, expected=0, futex_word=0x558027dc18) at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x558027dc18, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
./nptl/futex-internal.c:139
#3  0x007fb8d2e210 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x558027dbc0, cond=0x558027dbf0) at ./nptl/pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x558027dbf0, mutex=0x558027dbc0) at
./nptl/pthread_cond_wait.c:618
#5  0x007fb073122c in ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
#6  0x007fb06ef5c4 in ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
#7  

[kwin] [Bug 482411] New: Deleting the system tray to which notifications is bound to makes it default to the top left

[Steve Cossette]

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

Bug ID: 482411
   Summary: Deleting the system tray to which notifications is
bound to makes it default to the top left
Classification: Plasma
   Product: kwin
   Version: 6.0.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

It's a bit difficult to explain this one. The default KDE setup is to have a
bar at the bottom with the application launcher/Discover/System
Settings/Spacer/Tray/... right? But let's say you change the way you use your
panels, and delete the System Tray widget to recreate it in another panel,
notifications from now on will default to the top left for me (Note: I'm on a
dual screen setup, and it defaults to the top left corner of my left screen).

Relogging/restarting plasma-desktop does fix this problem, and notifications do
bind themselves to the new location of the system tray.

Expected behavior would be to default to the top left corner if there are
nothing to bind to, but to bind properly again when a widget is added back.

Thanks!

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

[systemsettings] [Bug 481840] Removing a VPN connection is impossible on 6.0

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
https://www.youtube.com/watch?v=oTvygg7JI3Y Here's a video of the issue

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

[systemsettings] [Bug 481840] Removing a VPN connection is impossible on 6.0

[Steve Cossette]

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

--- Comment #2 from Steve Cossette  ---
Nope, that's the first thing I tried.

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

[gwenview] [Bug 481470] Editing enough files in Gwenview eventually causes files to disappear from USB drive

[Steve Zakulec]

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

--- Comment #1 from Steve Zakulec  ---
Got it to happen on my Neon Unstable testing laptop:
Gwenview 24.04.70
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-18-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-2370M CPU @ 2.40GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 3000
Manufacturer: Dell Inc.
Product Name: Inspiron 3520

Edited 30 photos (same kind as my test images) with cropping quickly, saving
each one before moving on to the next

I also have the error reports from checking the disk on a Windows laptop, and
then repairing after errors were found.

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

[systemsettings] [Bug 481840] New: Removing a VPN connection is impossible on 6.0

[Steve Cossette]

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

Bug ID: 481840
   Summary: Removing a VPN connection is impossible on 6.0
Classification: Applications
   Product: systemsettings
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_networkmanagement
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
CC: jgrul...@redhat.com
  Target Milestone: ---

I updated from RC2 to 6.0 Final. I then added a l2tp VPN connection in System
Settings, and tried to delete it. It shows a (Honestly kind of strange looking)
message box, but regardless if you click OK or Cancel, the connection remains
and does not get deleted.

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.0-0.rc5.41.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 27.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82UH
System Version: Legion 7 16ARHA7

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

[gwenview] [Bug 481470] New: Editing enough files in Gwenview eventually causes files to disappear from USB drive

[Steve Zakulec]

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

Bug ID: 481470
   Summary: Editing enough files in Gwenview eventually causes
files to disappear from USB drive
Classification: Applications
   Product: gwenview
   Version: 23.08.4
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: spzaku...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Hi, seemingly editing enough photos from an external USB drive in Gwenview will
eventually cause the drive to have missing files, and no longer show all of the
drive's files unless you run a filesystem check.

STEPS TO REPRODUCE
1. Put a large number (68 or so in my case) of TIFF scans on an NTFS-formatted
USB stick. You can download https://archive.org/details/Ford-Times-May-1978 and
extract the CBZ file to a drive to recreate my setup.
2. Open up the first file in Gwenview, and crop as desired.
3. Keep cropping successive files until Gwenview shows you the first file

OBSERVED RESULT
Gwenview unexpectedly wraps around to the first file before you've gone through
all the files on the disk, and checking the disk shows files missing from the
drive.

EXPECTED RESULT
You can safely crop all of the files, and everything is still present on the
drive at the end.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12
Gwenview 23.08.4
Kernel Version: 6.5.0-15-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 80SA
System Version: LENOVO_IDEAPAD

ADDITIONAL INFORMATION
Drive is automounted as such:
dev/sdb2 /media/steve/scans ntfs3
rw,nosuid,nodev,relatime,uid=1000,gid=1000,windows_names,iocharset=utf8 0 0

No errors show up in Gwenview.
Drive is a Kingston Technology DataTraveler Max, ID 0951:177f

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

[kwin] [Bug 481415] Double-clicking an app button in taskbar no longer minimizes app after resuming from sleep

[Steve Cossette]

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

--- Comment #5 from Steve Cossette  ---
Just to be 100% clear:

This only happens on the non-primary screen. The primary screen works just
fine/normally.

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

[kwin] [Bug 481415] Double-clicking an app button in taskbar no longer minimizes app after resuming from sleep

[Steve Cossette]

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

--- Comment #4 from Steve Cossette  ---
Oh and its any open apps. It does it for them all. But only on one screen.

On Fri, Feb 16, 2024 at 11:43 AM  wrote:

> https://bugs.kde.org/show_bug.cgi?id=481415
>
> fanzhuyi...@gmail.com changed:
>
>What|Removed |Added
>
> 
>  CC||fanzhuyi...@gmail.com
>  Resolution|--- |WAITINGFORINFO
>  Status|REPORTED|NEEDSINFO
>
> --- Comment #2 from fanzhuyi...@gmail.com ---
> Thank you for your bug report!
>
> Unfortunately I cannot reproduce on wayland, master build on arch linux.
>
> Is this happening on x11 or wayland? Do you see this happening with all
> apps,
> or just a few apps? Do you still reproduce this bug in RC2?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 481415] Double-clicking an app button in taskbar no longer minimizes app after resuming from sleep

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
Yes to all. I am using fedora 40 on wayland on latest rc2.

On Fri, Feb 16, 2024 at 11:43 AM  wrote:

> https://bugs.kde.org/show_bug.cgi?id=481415
>
> fanzhuyi...@gmail.com changed:
>
>What|Removed |Added
>
> 
>  CC||fanzhuyi...@gmail.com
>  Resolution|--- |WAITINGFORINFO
>  Status|REPORTED|NEEDSINFO
>
> --- Comment #2 from fanzhuyi...@gmail.com ---
> Thank you for your bug report!
>
> Unfortunately I cannot reproduce on wayland, master build on arch linux.
>
> Is this happening on x11 or wayland? Do you see this happening with all
> apps,
> or just a few apps? Do you still reproduce this bug in RC2?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kwin] [Bug 481415] Double-clicking an app button in taskbar no longer minimizes app after resuming from sleep

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[kwin] [Bug 481415] Double-clicking an app button in taskbar no longer minimizes app after resuming from sleep

[Steve Cossette]

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

--- Comment #1 from Steve Cossette  ---
Oh one more clarification:

This bug seems to somehow resolve itself after a while. I only notice after a
couple hours that the minimize behavior strangely starts working again out of
the blue. I don't know how to reproduce that part though.

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

[kwin] [Bug 481415] New: Double-clicking an app button in taskbar no longer minimizes app after resuming from sleep

[Steve Cossette]

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

Bug ID: 481415
   Summary: Double-clicking an app button in taskbar no longer
minimizes app after resuming from sleep
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

Created attachment 165858
  --> https://bugs.kde.org/attachment.cgi?id=165858=edit
A video of the behavior occuring. This was in RC1, and at that point I didn't
know how to properly reproduce it.

Description:
In the icon-only task manager, usually, if you click an app button, it will
bring that app to the forefront. If you click again, it'll minimize it. This
bug, when triggered, stops the minimizing behavior from happening on the second
screen.

How to reproduce:
(NOTE: in my case, I have 2 monitors, and my left monitor is set as primary)
1- Open a new session, open a couple apps. 
2- Make sure both your monitors have a taskbar, with an icon-only task manager.
3- The apps should show on both taskbars.
4- Lock your session (Meta+L). 
(Note: I have my screen set to turn off after 5 seconds of suspending. Not sure
if it's relevant to this bug though)
5- Resume your session.
In my case, activating/minimizing windows by clicking on the app in the
icon-only taskbar on the PRIMARY screen works fine.
Doing the same thing on the SECONDARY screen though no longer works. 
Also, you'll see that the icon-only taskbar's theme/design is a bit odd, a
large line pops above the button. Maybe a cause of this bug...?

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

[kscreenlocker] [Bug 480460] Waking up computer after a prolonged amount of time results in the first password entered to be always refused

[Steve Cossette]

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

--- Comment #5 from Steve Cossette  ---
After playing with this, this only happens roughly 80-85% of the time for me.
Sometimes it works fine.

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

[Welcome Center] [Bug 481337] OEM Mode

[Steve Cossette]

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

--- Comment #5 from Steve Cossette  ---
(In reply to Oliver Beard from comment #4)
> It's a good idea, but how would Welcome Center be shown in an OEM mode? I'm
> unsure what would go in to doing that on Linux - by which I mean showing a
> window on boot (mandatory until completed) and then logging you in to that
> created user.

Something like that. Basically, the equivalent of Windows's OOBE. Or, if you
want to test it in Linux Land, try to install Fedora 39 Workstation (Gnome),
you'll see the setup wizard on first boot.

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

[Welcome Center] [Bug 481337] New: [Feature Request] OEM Mode

[Steve Cossette]

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

Bug ID: 481337
   Summary: [Feature Request] OEM Mode
Classification: Applications
   Product: Welcome Center
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
CC: n...@kde.org
  Target Milestone: ---

It would be really awesome for Plasma-welcome to act as a user onboarding for
the KDE experience.

For example, after installation of a system, on first boot, you'd be prompted
to create your user account, with sudo permissions, etc.

Thank you!

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

[Welcome Center] [Bug 481319] [Feature Request] Add a function to execute a process from a qml page

[Steve Cossette]

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

--- Comment #5 from Steve Cossette  ---
No that's adequate. To be completely honest, I was looking at documentation on
api.kde.org and not plasma-welcome's readme. That's 100% my bad.

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

[Welcome Center] [Bug 481319] [Feature Request] Add a function to execute a process from a qml page

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
Oh i did not see that… sorry!

On Wed, Feb 14, 2024 at 10:36 AM Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=481319
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>  Resolution|NOT A BUG   |WORKSFORME
>
> --- Comment #2 from Nate Graham  ---
> In fact this is already implemented and documented here:
> https://invent.kde.org/plasma/plasma-welcome#run-a-terminal-command
>
> Did you miss that, or did you try it and find that it doesn't meet your
> needs?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[Welcome Center] [Bug 481319] New: [Feature Request] Add a function to execute a process from a qml page

[Steve Cossette]

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

Bug ID: 481319
   Summary: [Feature Request] Add a function to execute a process
from a qml page
Classification: Applications
   Product: Welcome Center
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
CC: n...@kde.org
  Target Milestone: ---

Good morning!

I'm working on customizing plasma-welcome for Fedora using it's function to add
more pages by simply adding qml pages to
/usr/share/plasma/plasma-welcome/extra-pages.

The page we're trying to add would allow the user to enable third party
repositories in dnf by pressing a button. Said button, once pressed, should
spawn a process in the background (pkexec fedora-third-party enable).

I've been searching on ways to do this, but that'd require a qml binding around
QProcess (If I understand qml properly -- I am very much 100% a newbie at qml
and c++, but I'm able to get around by looking at the logic of things).

IF something like that could be implemented in plasma-welcome, it would be
awesome!

Thank you!

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

[plasmashell] [Bug 467074] On X11, when returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment

[Steve]

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

--- Comment #37 from Steve  ---
Happy to try out the 6 RC packages Nate. I'll put a request into the current
release group on LQ to have the packages built and put into /testing.

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

[kwin] [Bug 481066] New: Documentation missing for Window Settings

[Steve Cossette]

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

Bug ID: 481066
   Summary: Documentation missing for Window Settings
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

If you go into window settings (kcmshell6 kcm_kwinrules), and click on the Help
button, you get a "Documentation not found" error.

The expected resolution would be for the documentation to be found :)

Operating System: Fedora Linux 40
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

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

[kscreenlocker] [Bug 481054] New: Locking a session on a Live Image (Password-less account) on a dual screen setup causes the 2nd screen to show a password field

[Steve Cossette]

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

Bug ID: 481054
   Summary: Locking a session on a Live Image (Password-less
account) on a dual screen setup causes the 2nd screen
to show a password field
Classification: Plasma
   Product: kscreenlocker
   Version: 5.93.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

NOTE: Requires a dual screen setup

STEPS TO REPRODUCE
1. Download the current Fedora KDE Nightly
(https://openqa.fedoraproject.org/nightlies.html, use the "Fedora Latest
Nightly, not latest "Known good")
2. Run it, and get to the live desktop.
3.  Lock the session with Meta+L. For me, one screen shows the "Log in" button,
one has a password field.


Operating System: Fedora Linux 40
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

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

[Plasma Bigscreen] [Bug 480929] New: Plasma Bigscreen fails to start

[Steve Cossette]

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

Bug ID: 480929
   Summary: Plasma Bigscreen fails to start
Classification: Plasma
   Product: Plasma Bigscreen
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Homescreen
  Assignee: notm...@gmail.com
  Reporter: farch...@gmail.com
  Target Milestone: ---

On Fedora 40 rawhide (Plasma 6 RC2), plasma-bigscreen fails to start. Checking
the logs I see the following repeated dozens of times:

Feb 05 21:34:54 fedora systemd-coredump[53727]: [] Process 53614 (plasmashell)
of user 1000 dumped core.

Module
org.kde.mycroft.bigscreen.homescreen.so from rpm
plasma-bigscreen-5.27.80~20240204.214319.046d404-1.fc40.x86_64
Module plasma_layouttemplate.so
from rpm plasma-workspace-5.93.0-1.fc40.x86_64
Module plasma_applet.so from
rpm libplasma-5.93.0-1.fc40.x86_64
Module
KF6WindowSystemKWaylandPlugin.so from rpm
kf6-kwindowsystem-5.249.0-1.fc40.x86_64
Module plasma_shell.so from rpm
libplasma-5.93.0-1.fc40.x86_64
Module plasma_lookandfeel.so
from rpm plasma-workspace-5.93.0-1.fc40.x86_64
Module libKF6Style.so.6 from
rpm kf6-frameworkintegration-5.249.0-1.fc40.x86_64
Module libKirigamiPlatform.so.6
from rpm kf6-kirigami-5.249.0-1.fc40.x86_64
Module breeze6.so from rpm
plasma-breeze-5.93.0-1.fc40.x86_64
Module libpciaccess.so.0 from
rpm libpciaccess-0.16-12.fc40.x86_64
Module libtinfo.so.6 from rpm
ncurses-6.4-12.20240127.fc40.x86_64
Module libedit.so.0 from rpm
libedit-3.1-50.20230828cvs.fc40.x86_64
Module libdrm_intel.so.1 from
rpm libdrm-2.4.120-3.fc40.x86_64
Module libdrm_nouveau.so.2 from
rpm libdrm-2.4.120-3.fc40.x86_64
Module libdrm_amdgpu.so.1 from
rpm libdrm-2.4.120-3.fc40.x86_64
Module libelf.so.1 from rpm
elfutils-0.190-6.fc40.x86_64
Module libdrm_radeon.so.1 from
rpm libdrm-2.4.120-3.fc40.x86_64
Module libsensors.so.4 from rpm
lm_sensors-3.6.0-16.fc40.x86_64
Module radeonsi_dri.so from rpm
mesa-24.0.0-1.fc40.x86_64
Module libxshmfence.so.1 from
rpm libxshmfence-1.3.2-3.fc40.x86_64
Module libxcb-sync.so.1 from
rpm libxcb-1.16-4.fc40.x86_64
Module libxcb-present.so.0 from
rpm libxcb-1.16-4.fc40.x86_64
Module libxcb-dri3.so.0 from
rpm libxcb-1.16-4.fc40.x86_64
Module libwayland-server.so.0
from rpm wayland-1.22.0-3.fc40.x86_64
Module libdrm.so.2 from rpm
libdrm-2.4.120-3.fc40.x86_64
Module libxcb-xfixes.so.0 from
rpm libxcb-1.16-4.fc40.x86_64
Module libxcb-dri2.so.0 from
rpm libxcb-1.16-4.fc40.x86_64
Module libX11-xcb.so.1 from rpm
libX11-1.8.7-3.fc40.x86_64
Module libexpat.so.1 from rpm
expat-2.5.0-5.fc40.x86_64
Module libglapi.so.0 from rpm
mesa-24.0.0-1.fc40.x86_64
Module libgbm.so.1 from rpm
mesa-24.0.0-1.fc40.x86_64
Module libEGL_mesa.so.0 from
rpm mesa-24.0.0-1.fc40.x86_64
Module libwayland-egl.so.1 from
rpm wayland-1.22.0-3.fc40.x86_64
Module
libQt6WaylandEglClientHwIntegration.so.6 from rpm
qt6-qtwayland-6.6.1-3.fc40.x86_64
Module
libqt-plugin-wayland-egl.so from rpm qt6-qtwayland-6.6.1-3.fc40.x86_64
Module libXrender.so.1 from rpm
libXrender-0.9.11-6.fc40.x86_64
Module libKF6Bookmarks.so.6
from rpm 

[okular] [Bug 480825] New: When Show Forms is active, saving the document unsets Show Forms

[Steve Kelem]

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

Bug ID: 480825
   Summary: When Show Forms is active, saving the document unsets
Show Forms
Classification: Applications
   Product: okular
   Version: 23.08.1
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: st...@kelem.net
  Target Milestone: ---

SUMMARY
***
When filling out PDF forms in Okular you have to set Show Forms to see and
enter data into the forms. Saving your work unsets Show Forms. It shouldn't.
***


STEPS TO REPRODUCE
1. Open a PDF document with forms
2. Click on Show Forms
3. Type control-s to save the file

OBSERVED RESULT
Show Forms becomes reset.

EXPECTED RESULT
Show Forms should not be affected by saving the document. It's a safe thing to
safe your work periodically. It's annoying to have to set Show Forms just
because you save your work.

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

ADDITIONAL INFORMATION

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

[okular] [Bug 480823] New: shift-mouse scroll should scroll left/right

[Steve Kelem]

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

Bug ID: 480823
   Summary: shift-mouse scroll should scroll left/right
Classification: Applications
   Product: okular
   Version: 23.08.1
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: st...@kelem.net
  Target Milestone: ---

SUMMARY
***
In many programs Control-Mouse-Scroll scrolls up and down. Shift-Mouse-Scroll
scrolls left/right. Okular uses both Control-Mouse-Scroll and
Shift-Mouse-Scroll to scroll up and down.
***


STEPS TO REPRODUCE
1. Press Shift-Mouse-Scroll and watch the screen scroll up and down.
2. Press Control-Mouse-Scroll and watch the screen scroll up and down.

OBSERVED RESULT
Both keyboard/mouse actions do the same thing.

EXPECTED RESULT
Scrolling left/right is important too. Please remap Shift-Mouse-Scroll to
scroll left/right.

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

ADDITIONAL INFORMATION

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

[okular] [Bug 480821] New: Make annotations easier to delete

[Steve Kelem]

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

Bug ID: 480821
   Summary: Make annotations easier to delete
Classification: Applications
   Product: okular
   Version: 23.08.1
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: st...@kelem.net
  Target Milestone: ---

SUMMARY
***
Creating an annotation is easy. The steps needed to delete an annotation is
convoluted and not intuitive.
***


STEPS TO REPRODUCE
1. Create an annotation.
2. Realize you really didn't want to create an annotation.
3. Try to figure out how to undo what you just did, or figure out how to delete
it.

OBSERVED RESULT
1. Right-clicking on the annotation doesn't bring up a menu with Delete as one
of the options.
2. Creating a popup, then clicking the [x] button doesn't delete the popup, it
just closes the popup.
3. There doesn't seem to be a menu item to delete the popup.

EXPECTED RESULT
The user mechanism to delete the popup should be as close to the popup as
possible. The farther the mechanism is from the popup, the less likely it is
that a user will find it.
1. Somewhere on the popup
1a. Right-click on the popup to get a menu is the closest to the popup, and
should work whether the popup is open or closed.
1b. The [x] in the popup should delete the popup. A "minimize" button [_]
should close it. This is the mechanism on Windows and Linux.
1c. Farther away is the Top Bar's menus.  It's less obvious to look in the
menus... would it be under Edit? View? Tools? Not obvious where to look.
1d.  The least obvious place to look is in the left sidebar. There are tabs for
Thumbnails, Annotations. Bookmarks, and Outline. It turns out the delete
command is squirreled away under Annotations, then right-click on the
annotation, and then select Delete. This also changes whatever view was already
in the left sidebar. It takes another mental distraction from your real task to
try to remember what the previous left sidebar was.

Make it easier on your users. A right-click, Delete on the popup is right where
the user's attention is focused. It doesn't distract from what s/he was doing,
as 1c and 1d would. 1b should also be implemented because users already expect
that on their windows. Don't distract them from their main task, which is
reviewing and annotating their PDF.

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

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 480563] New: accountwizard crash upon adding my first email account to it

[Steve Cossette]

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

Bug ID: 480563
   Summary: accountwizard crash upon adding my first email account
to it
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Account Wizard
  Assignee: kdepim-b...@kde.org
  Reporter: farch...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: accountwizard (0.3)

Qt Version: 6.6.1
Frameworks Version: 5.248.0
Operating System: Linux 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64
x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Rawhide)"
DrKonqi: 5.92.0 [CoredumpBackend]

-- Information about the crash:
When starting kmail for the first time, it asks me if I want to import from
Thunderbird (I said no).

Then, I go through the wizard to add my gmail email address. I enter my name,
email and password (I found that odd, figured it'd go through oauth... oh well)
and select the imap server. I then click on Create Account.

Nothing Happens.

So then I try to simply click Continue and/or Create account again, and the
wizard just dies.

The crash can be reproduced every time.

-- Backtrace:
Application: Account Assistant (accountwizard), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 50098]
[New LWP 50111]
[New LWP 50115]
[New LWP 50110]
[New LWP 50117]
[New LWP 50118]
[New LWP 50114]
[New LWP 50125]
[New LWP 50127]
[New LWP 50126]
[New LWP 50129]
[New LWP 50138]
[New LWP 50148]
[New LWP 50410]
[New LWP 50113]
[New LWP 50116]
[New LWP 50108]
[New LWP 50145]
[New LWP 50147]
[New LWP 50412]
[New LWP 50151]
[New LWP 50130]
[New LWP 50146]
[New LWP 50413]
[New LWP 50150]
[New LWP 50409]
[New LWP 50128]
[New LWP 50417]
[New LWP 50421]
[New LWP 50420]
[New LWP 50418]
[New LWP 50149]
[New LWP 50408]
[New LWP 50414]
[New LWP 50419]
[New LWP 50415]
[New LWP 50411]
[New LWP 50416]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/accountwizard'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc159cab184 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fc15566f4c0 (LWP 50098))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fc15566f4c0 (LWP 50098))]

Thread 38 (Thread 0x7fc1098006c0 (LWP 50416)):
#0  0x7fc159ca5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fc159ca8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fc15a559661 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fc15a5561e7 in QThreadPoolThread::run() () at /lib64/libQt6Core.so.6
#4  0x7fc15a550ace in QThreadPrivate::start(void*) () at
/lib64/libQt6Core.so.6
#5  0x7fc159ca91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fc159d2b2dc in clone3 () at /lib64/libc.so.6

Thread 37 (Thread 0x7fc1114006c0 (LWP 50411)):
#0  0x7fc159d1d73d in poll () at /lib64/libc.so.6
#1  0x7fc1596d7244 in g_main_context_iterate_unlocked.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fc15967c227 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7fc155ba47d2 in gdbus_shared_thread_func.lto_priv () at
/lib64/libgio-2.0.so.0
#4  0x7fc1596a6453 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7fc159ca91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fc159d2b2dc in clone3 () at /lib64/libc.so.6

Thread 36 (Thread 0x7fc10a2006c0 (LWP 50415)):
#0  0x7fc159ca5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fc159ca8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fc15a559661 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fc15a5561e7 in QThreadPoolThread::run() () at /lib64/libQt6Core.so.6
#4  0x7fc15a550ace in QThreadPrivate::start(void*) () at
/lib64/libQt6Core.so.6
#5  0x7fc159ca91f7 in start_thread () at /lib64/libc.so.6
#6  0x7fc159d2b2dc in clone3 () at /lib64/libc.so.6

Thread 35 (Thread 0x7fc1034006c0 (LWP 50419)):
#0  0x7fc159ca5959 in __futex_abstimed_wait_common () at /lib64/libc.so.6
#1  0x7fc159ca8692 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#2  0x7fc15a559661 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib64/libQt6Core.so.6
#3  0x7fc15a5561e7 in QThreadPoolThread::run() () at /lib64/libQt6Core.so.6
#4  0x7fc15a550ace in 

[dolphin] [Bug 480498] Set filters disappear when dolphin is closed

[Steve Cossette]

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

--- Comment #4 from Steve Cossette  ---
I found something interesting.

If I go in a folder and click on the "Modified" column to sort, and restart
dolphin, it will not remember the settings.

BUT, if I do the same sorting, but using the Right Click -> Sort By -> Modified
and relaunch Dolphin, THEN it remembers.

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

[dolphin] [Bug 480498] Set filters disappear when dolphin is closed

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
It's set to "Use common display style for all folders", I swear it was set to
remember display style for each folder though...

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

[kscreenlocker] [Bug 480460] Waking up computer after a prolonged amount of time results in the first password entered to be always refused

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
(In reply to Nate Graham from comment #2)
> Is this with a multi-screen setup? If so can you try again with only a
> single screen and see if it still happens? Thanks!

Nope, single screen.

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

[dolphin] [Bug 480498] Set filters disappear when dolphin is closed

[Steve Cossette]

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

--- Comment #1 from Steve Cossette  ---
I keep forgetting to post this:

Operating System: Fedora Linux 40
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

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

[dolphin] [Bug 480498] New: Set filters disappear when dolphin is closed

[Steve Cossette]

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

Bug ID: 480498
   Summary: Set filters disappear when dolphin is closed
Classification: Applications
   Product: dolphin
   Version: 24.01.90
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: bars: filter
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Problem: In dolphin, if you set a filter on a specific column in a specific
folder, Dolphin will not retain your preference next time it is started.

Steps to reproduce:
1- Open Dolphin, go in any folder.
2- Click on a column to sort by said column.
3- Close, and reopen Dolphin
4- Go back to that folder.

The filter you set should have reverted back.

(NOTE: This bug does not occur on the "File Picker" dialogs in apps, that one
retains the settings you set as far as filters go.)

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

[kscreenlocker] [Bug 480460] Waking up computer after a prolonged amount of time results in the first password entered to be always refused

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

Version|git-stable-Plasma/5.27  |5.92.0

--- Comment #1 from Steve Cossette  ---
Fixed version.

Also:

Operating System: Fedora Linux 40
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.8.0-0.rc1.20240123git7ed2632ec7d7.12.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 27,1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82UH
System Version: Legion 7 16ARHA7

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

[kscreenlocker] [Bug 480460] Waking up computer after a prolonged amount of time results in the first password entered to be always refused

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

Summary|Waking up computer after a  |Waking up computer after a
   |prolonged amount of time|prolonged amount of time
   |results in the password |results in the first
   |entered to be always|password entered to be
   |refused |always refused

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

[kscreenlocker] [Bug 480460] New: Waking up computer after a prolonged amount of time results in the password entered to be always refused

[Steve Cossette]

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

Bug ID: 480460
   Summary: Waking up computer after a prolonged amount of time
results in the password entered to be always refused
Classification: Plasma
   Product: kscreenlocker
   Version: git-stable-Plasma/5.27
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

I have two computers with Plasma 6 (On Fedora 40 Rawhide), and only the laptop
exhibit this issue.

If I open my laptop after a decent amount of time inactive, whatever password I
enter in kscreenlocker will always be refused with "Password incorrect". (I did
double-check the password a couple times now by clicking the eye icon).

Trying a second time logs me right in.

I can also see this in my system logs, I think it may be relevant:

Jan 28 16:14:58 fedora kscreenlocker_greet[16688]: The cached device pixel
ratio value was stale on window expose.  Please file a QTBUG which explains how
to reproduce.
Jan 28 16:14:58 fedora kscreenlocker_greet[16688]: qt.qpa.wayland: Could not
create EGL surface (EGL error 0x3000)
Jan 28 16:14:59 fedora kscreenlocker_greet[16688]: Failed to write to the pipe:
Bad file descriptor.

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

[KAccounts] [Bug 477696] kaccounts-providers does not compile for qt6

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Steve Cossette  ---
Nate fixed this. So I'll close this bug.

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

[plasmashell] [Bug 480264] New: Plasma shell (Temporarily) freezes, and shutdown (Through kicker) is no longer possible

[Steve Cossette]

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

Bug ID: 480264
   Summary: Plasma shell (Temporarily) freezes, and shutdown
(Through kicker) is no longer possible
Classification: Plasma
   Product: plasmashell
   Version: 5.92.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-performance
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: 1.0

This bug, once triggers, results in the following:

1- Once you try to shutdown (I haven't tried logout/reboot), plasma shell (i.e.
Kicker, the application bar -- the whole shell) freezes for roughly 2 minutes.
Applications running can still be interacted with though, so the computer is
not fully frozen. Once the UI unfreezes, the system simply does not shut down.
2- Shutdown is no longer possible (See #1).

Here's how to reproduce:

1- Start something in Konsole, anything (I just did sudo journalctl -f)
2- Try to shut down. Konsole will warn you that something is running, cancel
out of it to not reboot.
3- You'll see a Plasma Workspace notification about Konsole not closing. Ignore
it.
4- Simply try to shutdown again. (The desktop will just freeze at that point).

>From then on, if you need to reboot, you need to sudo shutdown -r now.

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

[kde-inotify-survey] [Bug 466366] "Communication not allowed" on /usr/share/dbus-1/system.d/org.kde.kded.inotify.conf

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Steve Cossette  ---
I'm going to close this bug, it ended up being a problem in another kde
component (The dbus config kde-inotify-survey uses is a template) which I
submitted a PR for, I just forgot to close this.

Thanks!

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

[Tokodon] [Bug 480137] New: crashed when viewing a conversation for a poll

[Steve Downs]

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

Bug ID: 480137
   Summary: crashed when viewing a conversation for a poll
Classification: Applications
   Product: Tokodon
   Version: 23.08.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: st...@sdowns.xyz
CC: c...@carlschwan.eu, j...@redstrate.com
  Target Milestone: ---

Application: tokodon (23.08.4)

Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.6.11-200.fc39.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 39 (KDE Plasma)
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Voted for a poll then went to the comments section and it instantly crashed. I
reloaded the application and it crashed again. THis poll had 75 replies, 402
boosts and 2 favorites. Found another poll with 3 replies and it instantly
crashed as well.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Tokodon (tokodon), signal: Segmentation fault

[KCrash Handler]
#4  0x7fdbc75c4b20 in loadProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const&) () from /lib64/libQt5Qml.so.5
#5  0x7fdbc75c5f25 in
QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5
#6  0x7fdbc75e64da in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5
#7  0x7fdbc75eaf6f in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5
#8  0x7fdbc757ad82 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5
#9  0x7fdbc7711000 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /lib64/libQt5Qml.so.5
#10 0x7fdbc7717787 in QQmlBinding::evaluate(bool*) () from
/lib64/libQt5Qml.so.5
#11 0x7fdbc771bd3b in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5
#12 0x7fdbc77195d5 in
QQmlBinding::update(QFlags) () from
/lib64/libQt5Qml.so.5
#13 0x7fdbc7727264 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#14 0x7fdbc76b9551 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#15 0x7fdbc76b9b60 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () from /lib64/libQt5Qml.so.5
#16 0x7fdbc76b3074 in QQmlComponent::create(QQmlIncubator&, QQmlContext*,
QQmlContext*) () from /lib64/libQt5Qml.so.5
#17 0x7fdbc7d21bb5 in QQuickLoaderPrivate::_q_sourceLoaded() () from
/lib64/libQt5Quick.so.5
#18 0x7fdbc77275fb in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#19 0x7fdbc76b9551 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#20 0x7fdbc76b9b60 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () from /lib64/libQt5Qml.so.5
#21 0x7fdbc76b3074 in QQmlComponent::create(QQmlIncubator&, QQmlContext*,
QQmlContext*) () from /lib64/libQt5Qml.so.5
#22 0x7fdbc6365631 in QQuickStackElement::load(QQuickStackView*) () from
/lib64/libQt5QuickTemplates2.so.5
#23 0x7fdbc636793d in QQuickStackView::push(QQmlV4Function*) () from
/lib64/libQt5QuickTemplates2.so.5
#24 0x7fdbc63958f2 in QQuickStackView::qt_metacall(QMetaObject::Call, int,
void**) () from /lib64/libQt5QuickTemplates2.so.5
#25 0x7fdbc76f532a in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const () from /lib64/libQt5Qml.so.5
#26 0x7fdbc75c9ec6 in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const () from /lib64/libQt5Qml.so.5
#27 0x7fdbc75e774c in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5
#28 0x7fdbc75eaf6f in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5
#29 0x7fdbc757ad82 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5
#30 0x7fdbc7711000 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /lib64/libQt5Qml.so.5
#31 0x7fdbc76bf5a1 in QQmlBoundSignalExpression::evaluate(void**) () from
/lib64/libQt5Qml.so.5
#32 0x7fdbc76c0820 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*,
void**) () from /lib64/libQt5Qml.so.5
#33 0x7fdbc76f4dd7 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /lib64/libQt5Qml.so.5
#34 0x7fdbc58e8540 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#35 0x7fdbc76992a9 in 

[kwin] [Bug 480099] Clicking out of the task switcher while using it causes the task manager to become confused

[Steve Cossette]

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

--- Comment #1 from Steve Cossette  ---
System info:

Operating System: Fedora Linux 40
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

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

[kwin] [Bug 480099] New: Clicking out of the task switcher while using it causes the task manager to become confused

[Steve Cossette]

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

Bug ID: 480099
   Summary: Clicking out of the task switcher while using it
causes the task manager to become confused
Classification: Plasma
   Product: kwin
   Version: 5.92.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: multi-screen
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

Created attachment 165077
  --> https://bugs.kde.org/attachment.cgi?id=165077=edit
Video of the issue (WARNING: Video spans 2 2K screens)

1- Put most apps on the second screen, except for 1 that you leave on screen 1.
2- Make sure you use the Thumbnail Grid task switcher (Not sure if it's
related, but...)
3- Click on the window on Screen one, and ALT+TAB. Hold ALT, to leave the task
switcher up.
4- Plasma 6 should highlight the app you selected in the task switcher on the
2nd screen. While still holding alt, make sure that you avoid the task switcher
currently open with your mouse (So not to highlight other apps) and go in your
taskbar, on the 2nd screen.
5- Click on an app, any EXCEPT for the one on screen 1, OR the one currently
highlighted. Try not to move your mouse and keep clicking.

On my screen, let's say I continuously click on button #2 in my task switcher,
another task (let's say button #5) gets minimized/restored.

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

[plasmashell] [Bug 478951] XWayland apps cannot be minimized clicking on their Task Manager entries until launching another app or switching to another task

[Steve Cossette]

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

--- Comment #12 from Steve Cossette  ---
And this morning, it seems to no longer do it Mind you I patched &
installed the patched plasma-workspace package two days ago, and I shut down my
computer every night. I need to find out why this bug triggers...

I guess for now this may need to be closed, if it reoccurs ill reopen it

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

[plasmashell] [Bug 478951] XWayland apps cannot be minimized clicking on their Task Manager entries until launching another app or switching to another task

[Steve Cossette]

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

--- Comment #11 from Steve Cossette  ---
(In reply to Steve Cossette from comment #10)
> Alright, I got two screens, right? Left screen being my primary screen (In
> case it matters). On that screen, you'll see in the video, if I click on an
> icon in the taskbar, it maximizes and un-minimizes just fine.
> 
> On the right screen, for me, if a window is minimized, clicking on it will
> un-minimize it. But if I click on it again to try to minimize it, it won't.
> And also there's a strange line that shows right on top of the button for
> some reason, but that's secondary.
> 
> Mind you though in my case, this happens regardless of the application type:
> Xorg or Wayland.
> 
> Hopefully that gives some context to the videos.

By the way, I did recompile plasma-workspace with this commit yesterday:
https://invent.kde.org/plasma/plasma-workspace/-/commit/df5a6097401124b8ecad874ae1a7e01df5e61028.
Then, I installed it, and rebooted.

The videos/explanations I submitted were after I got done doing this.

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

[plasmashell] [Bug 478951] XWayland apps cannot be minimized clicking on their Task Manager entries until launching another app or switching to another task

[Steve Cossette]

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

--- Comment #10 from Steve Cossette  ---
Alright, I got two screens, right? Left screen being my primary screen (In case
it matters). On that screen, you'll see in the video, if I click on an icon in
the taskbar, it maximizes and un-minimizes just fine.

On the right screen, for me, if a window is minimized, clicking on it will
un-minimize it. But if I click on it again to try to minimize it, it won't. And
also there's a strange line that shows right on top of the button for some
reason, but that's secondary.

Mind you though in my case, this happens regardless of the application type:
Xorg or Wayland.

Hopefully that gives some context to the videos.

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

[plasmashell] [Bug 478951] XWayland apps cannot be minimized clicking on their Task Manager entries until launching another app or switching to another task

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 CC||farch...@gmail.com
 Status|RESOLVED|REOPENED

--- Comment #8 from Steve Cossette  ---
FYI, this is still a problem here, but oddly enough, only on one screen.

I think the best way is to demonstrate this through a video (Well, two) so here
they are:

Screen 1, Primary (Works fine): https://www.youtube.com/watch?v=5AqL2hQBwqo
Screen 2 (Glitched): https://www.youtube.com/watch?v=T6ogBHOiL1w

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

[systemsettings] [Bug 479981] New: Theme switching crashes settings app

[steve]

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

Bug ID: 479981
   Summary: Theme switching crashes settings app
Classification: Applications
   Product: systemsettings
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: scal...@gmail.com
  Target Milestone: ---

Application: systemsettings (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-9-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Just trying to change themes, crashes the settings app.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault

   PID: 52370 (systemsettings)
   UID: 1000 (steve)
   GID: 1000 (steve)
Signal: 11 (SEGV)
 Timestamp: Wed 2024-01-17 19:12:04 HST (27s ago)
  Command Line: /usr/bin/systemsettings
Executable: /usr/bin/systemsettings
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fsystemsettings-77b89a5c95dc4d7dbde297f5dd8cb097.scope
  Unit: user@1000.service
 User Unit:
app-\x2fusr\x2fbin\x2fsystemsettings-77b89a5c95dc4d7dbde297f5dd8cb097.scope
 Slice: user-1000.slice
 Owner UID: 1000 (steve)
   Boot ID: 8653860ec7ec4de7892fc1da5b31bcb8
Machine ID: 7e77600ceb6142ee85eee493c53bcbd9
  Hostname: hikari
   Storage:
/var/lib/systemd/coredump/core.systemsettings.1000.8653860ec7ec4de7892fc1da5b31bcb8.52370.170555472400.zst
(present)
  Size on Disk: 9.7M
   Message: Process 52370 (systemsettings) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.19-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.19-1~deb12u1.amd64
Stack trace of thread 52370:
#0  0x7f10812a9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7f108125af32 raise (libc.so.6 + 0x3bf32)
#2  0x7f1082cb883d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x583d)
#3  0x7f108125afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7f107f86b96c
_ZN19QQuickWindowPrivate28sendFilteredPointerEventImplEP18QQuickPointerEventP10QQuickItemS3_
(libQt5Quick.so.5 + 0x26b96c)
#5  0x7f107f86b869
_ZN19QQuickWindowPrivate28sendFilteredPointerEventImplEP18QQuickPointerEventP10QQuickItemS3_
(libQt5Quick.so.5 + 0x26b869)
#6  0x7f107f86b869
_ZN19QQuickWindowPrivate28sendFilteredPointerEventImplEP18QQuickPointerEventP10QQuickItemS3_
(libQt5Quick.so.5 + 0x26b869)
#7  0x7f107f86b869
_ZN19QQuickWindowPrivate28sendFilteredPointerEventImplEP18QQuickPointerEventP10QQuickItemS3_
(libQt5Quick.so.5 + 0x26b869)
#8  0x7f107f86c674
_ZN19QQuickWindowPrivate24deliverToPassiveGrabbersERK7QVectorI8QPointerI20QQuickPointerHandlerEEP18QQuickPointerEvent
(libQt5Quick.so.5 + 0x26c674)
#9  0x7f107f872a4f
_ZN19QQuickWindowPrivate17deliverMouseEventEP23QQuickPointerMouseEvent
(libQt5Quick.so.5 + 0x272a4f)
#10 0x7f107f8740dd
_ZN19QQuickWindowPrivate19deliverPointerEventEP18QQuickPointerEvent
(libQt5Quick.so.5 + 0x2740dd)
#11 0x7f1081b493f5 _ZN7QWindow5eventEP6QEvent
(libQt5Gui.so.5 + 0x1493f5)
#12 0x7f1082362fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#13 0x7f10816b16f8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b16f8)
#14 0x7f1080397057
_ZN12QQuickWidget17mouseReleaseEventEP11QMouseEvent (libQt5QuickWidgets.so.5 +
0xf057)
#15 0x7f10823a4db8 _ZN7QWidget5eventEP6QEvent
(libQt5Widgets.so.5 + 0x1a4db8)
#16 0x7f1082362fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#17 0x7f108236b552
_ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16b552)
#18 0x7f10816b16f8
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2b16f8)
#19 0x7f108236965e
_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb
(libQt5Widgets.so.5 + 0x16965e)
#20 0x7f10823bdbd8 n/a (libQt5Widgets.so.5 + 0x1bdbd8)
#21 0x7f10823c0f60 n/a (libQt5Widgets.so.5 + 0x1c0f60)
#22 0x7f1082362fae
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162fae)
#23 0x7f10816b16f8

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

--- Comment #10 from Steve Cossette  ---
(In reply to Steve Cossette from comment #9)
> (In reply to fanzhuyifan from comment #8)
> > (In reply to Steve Cossette from comment #6)
> > > Created attachment 164986 [details]
> > > Both Screens
> > > 
> > > The left Konsole window is currently snapped.
> > 
> > Humm interesting. There seems to be nothing that could be causing the window
> > to snap, and I can't reproduce on my end. Do you observe any changes in the
> > snapping you reported if you set center snap zone to a non-zero value?
> > 
> > I am a little out of ideas for now. Would need to think about this a bit.
> 
> I went ahead and tried that. I've set the Center Snap Zone to 1px. On the
> left screen (The one affected), the behavior still occurs, but... as I move
> the window, it asks like if there's now 2 snap zones right on top of each
> other (As it snaps, if I move it a tiny bit, you can see the window snap to
> the following pixel a tiny bit).
> On the right screen, nothing snaps still.

Sorry, asks should've been "acts"... 

And if it helps:
Operating System: Fedora Linux 40
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT

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

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

--- Comment #9 from Steve Cossette  ---
(In reply to fanzhuyifan from comment #8)
> (In reply to Steve Cossette from comment #6)
> > Created attachment 164986 [details]
> > Both Screens
> > 
> > The left Konsole window is currently snapped.
> 
> Humm interesting. There seems to be nothing that could be causing the window
> to snap, and I can't reproduce on my end. Do you observe any changes in the
> snapping you reported if you set center snap zone to a non-zero value?
> 
> I am a little out of ideas for now. Would need to think about this a bit.

I went ahead and tried that. I've set the Center Snap Zone to 1px. On the left
screen (The one affected), the behavior still occurs, but... as I move the
window, it asks like if there's now 2 snap zones right on top of each other (As
it snaps, if I move it a tiny bit, you can see the window snap to the following
pixel a tiny bit).
On the right screen, nothing snaps still.

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

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

--- Comment #7 from Steve Cossette  ---
Oh by the way, this morning when I took a screenshot of the "Window Behavior
Settings, I freshly logged into Plasma 6 and simply opened systemsettings and
spectacle, and it did it.

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

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

--- Comment #6 from Steve Cossette  ---
Created attachment 164986
  --> https://bugs.kde.org/attachment.cgi?id=164986=edit
Both Screens

The left Konsole window is currently snapped.

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

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

--- Comment #5 from Steve Cossette  ---
(In reply to fanzhuyifan from comment #4)
> (In reply to Steve Cossette from comment #2)
> > Correct, it is indeed set to "None".
> > 
> > Also, I noticed something else that might help you pinpoint this issue. I
> > got two monitors. This seems to only happen on the primary monitor. (But
> > that might be intended if the feature was enabled that is)
> > 
> > Sending a screenshot of the window behavior settings (Just in case)
> 
> Could you share a screenshot of both your monitors when this happens? It
> might be the case that something on the other monitor is causing this
> behavior, like panels.
> Are you on X11 or wayland?
> 
> Also I haven't been able to reproduce on my end, so we would need to figure
> out what is causing this.

Sure thing, uploading now!

We're on Wayland, Fedora 40 will be wayland only as well.

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

[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab

[Steve Cossette]

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

--- Comment #10 from Steve Cossette  ---
I'm getting the same thing on RC1. Can't say if it was fixed in a future commit
though as ours is built from the release binaries.

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

[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #9 from Steve Cossette  ---
Created attachment 164979
  --> https://bugs.kde.org/attachment.cgi?id=164979=edit
System logs

System Logs (kwin_wayland filtered)

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

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

--- Comment #3 from Steve Cossette  ---
Created attachment 164976
  --> https://bugs.kde.org/attachment.cgi?id=164976=edit
Window Behavior Settings

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

[kwin] [Bug 479916] Windows seem to snap against nothing

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

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

--- Comment #2 from Steve Cossette  ---
Correct, it is indeed set to "None".

Also, I noticed something else that might help you pinpoint this issue. I got
two monitors. This seems to only happen on the primary monitor. (But that might
be intended if the feature was enabled that is)

Sending a screenshot of the window behavior settings (Just in case)

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

[kwin] [Bug 479916] New: Windows seem to snap against nothing

[Steve Cossette]

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

Bug ID: 479916
   Summary: Windows seem to snap against nothing
Classification: Plasma
   Product: kwin
   Version: 5.92.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

(Note: I'm not 100% sure this should go in kwin, nor if it is in the right
subcomponent of kwin. If I made a mistake, I apologize!)

Seems that, in Plasma 6 (RC1), windows have a tendancy to 'snap' around 1/6th
the way down the screen (See video).

It seems to also snap a little below the task bar, but to be honest, that's
very likely to be intended.

Video: https://youtu.be/poZ5vH8vUZo

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

[systemsettings] [Bug 477457] When fractional scale factor, clock SVG is sized inappropriately when KCM is opened externally

[Steve Cossette]

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

Steve Cossette  changed:

   What|Removed |Added

 CC||farch...@gmail.com

--- Comment #6 from Steve Cossette  ---
Still is the case on RC1 here.

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

[systemsettings] [Bug 479860] New: Once an account is created, it is impossible to rename it

[Steve Cossette]

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

Bug ID: 479860
   Summary: Once an account is created, it is impossible to rename
it
Classification: Applications
   Product: systemsettings
   Version: 5.92.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kaccounts
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
CC: ad...@leinir.dk
  Target Milestone: ---

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

I explained the whole problem, as well as demo'd it, in the attached video.

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

[Discover] [Bug 479782] New: When doing OS Updates, the UI Footer gets all jumbled up

[Steve Cossette]

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

Bug ID: 479782
   Summary: When doing OS Updates, the UI Footer gets all jumbled
up
Classification: Applications
   Product: Discover
   Version: 5.92.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Updates (interactive)
  Assignee: plasma-b...@kde.org
  Reporter: farch...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 164891
  --> https://bugs.kde.org/attachment.cgi?id=164891=edit
Reproducing the bug

It's a bit difficult to describe how to repro, but this is how I did it:

1- Go to distro updates, and refresh.
Before it's done updating:
2- Go to one of the other discover categories and go back to the updates.

You got about a 50/50 chance that the footer section will be all jumbled up.

(See the attached video for better clarification about the problem)

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

[plasma-systemmonitor] [Bug 477517] "Log Files" not listed in sensor browser

[Steve Vialle]

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

Steve Vialle  changed:

   What|Removed |Added

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

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

[dolphin] [Bug 475805] Files with ending .bak are treated as if they were hidden.

[Steve Vialle]

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

--- Comment #15 from Steve Vialle  ---
(In reply to Felix Ernst from comment #13)
> I am currently trying to think
> of a plan that makes everyone happy.
The obvious answer is right there in the feature request:
"it could be built-in (as suggested x-trash), like having a checkbox "[x] also
hide application/x-trash files when hiding files"."

Why continue to drag this out with diversions into what "application author
might expect" and "user isn't supposed to interact with"? That's up to the
application developer to deal with (usually using hidden "dot" files or
directories), and cleaning up after programs that make a mess is none of
dolphins business.

If you want to please both those who want to keep the old hidden file
definition and those who want x-trash (or some other list) hidden as well,
what's the problem with simply adding a configuration checkbox as proposed?
Worded as above, it even documents which mime type to edit if you want finer
control over exactly what is hidden.

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

[dolphin] [Bug 475805] Files with ending .bak are treated as if they were hidden.

[Steve Vialle]

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

--- Comment #12 from Steve Vialle  ---
(In reply to Felix Ernst from comment #8)
> Which application is creating those .bak files? Are those files created in a
> context in which the application author might expect users to directly
> interact with the file? Is the file created in a visible path in the user's
> home directory or in a path that contains hidden folders?

I really don't see where any of this relevant. It's not the job of a file
manager to predict the intent of other applications, but rather to provide an
accurate view of the filesystem to the user. 

But, if you insist:
* vi, diff and cp
* Yes. Filenames provided from user input.
* A first-level subdirectory of ~/, containing no traditional hidden files
or directory elements.

In the case that led me here, no application decided the names for the files I
was working with, and "extensions" were arbitrary and supplied by the user...
As is the norm on unix-like systems where file type is primarily determined by
magic number rather than vestiges of MS-DOS "8.3" naming conventions. 

IOW, *I* created files with those extensions, as I have done quite happily for
the last 2+ decades before this feature turned up, and having them suddenly
vanish for no documented reason, contrary to the behaviour of every other file
manager in existence, wasted considerable of my time.

Filenames beginning with "." being treated as hidden is a well understood, well
documented feature on unix-like systems, as established as the "hidden" file
attribute in DOS or Windows. 
Files suddenly disappearing from view based on an arbitrary list of filename
patterns buried in a rarely used mimetype is anything but, and leads to
*surprises* for the user. Surprises are the _last_ thing I want from a tool
like a file manager.

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

[lattedock] [Bug 479043] New: Latte Crashes trying to access PIM calendars for Digital Clock

[Steve Dude]

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

Bug ID: 479043
   Summary: Latte Crashes trying to access PIM calendars for
Digital Clock
Classification: Plasma
   Product: lattedock
   Version: 0.10.8
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: steve_d...@gmx.com
  Target Milestone: ---

Application: latte-dock (0.10.8)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.0-14-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.10
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
Right-clicking on the Digital Clock plasmoid > Configuring Digital Clock > PIM
Events Plugin > Select Calendar, crashed Latte Dock every time. This occurs
with KOrganizer installed or not installed.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x7fcaf6f25df5 in QV4::ExecutionEngine::fromVariant(QVariant const&) ()
at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#5  0x7fcaf6fa68a6 in ??? () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fcaf6f8375e in
QV4::QQmlContextWrapper::lookupScopeObjectProperty(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fcaf6fc6a94 in ??? () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fcaf6fcc107 in ??? () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fcaf6f5d566 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7fcaf70eb521 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7fcaf70f1988 in QQmlBinding::evaluate(bool*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7fcaf70f5c97 in ??? () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7fcaf70f3734 in
QQmlBinding::update(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7fcaf70980ad in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#16 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#17 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#18 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#19 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#20 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#21 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#22 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#23 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#24 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#25 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#26 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#27 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#28 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#29 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#30 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#31 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#32 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#33 0x7fcaf7098099 in
QQmlContextData::refreshExpressionsRecursive(QQmlJavaScriptExpression*) () at

[plasma-systemmonitor] [Bug 477517] "Log Files" not listed in sensor browser

[Steve Vialle]

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

--- Comment #2 from Steve Vialle  ---
(In reply to Arjen Hiemstra from comment #1)
> What does this do?
Exactly what it sounds like, allows adding a panel with a live tail of a log
file to a sensor sheet.
> What's the use case?
For one, adding a "why" to the "what" displayed by a CPU utilisation chart or
the like.
e.g. Here's a periodic spike in system load, there's the cron job that's
causing it, all on the same sheet.

I'm sure I could think of some more, but frankly I'm a bit confused at the
apparent need to justify removing existing functionality, or what is to be
gained in deprecating perfectly functional software in favour of something with
an obviously inferior feature set.

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

[KXStitch] [Bug 477693] Will not save or print files where selected

[Steve Allewell]

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

Steve Allewell  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WORKSFORME

--- Comment #1 from Steve Allewell  ---
I have tried both saving and printing to PDF and the file saves to and prints
to the folder I have specified.  I am unable to reproduce your problem.

If you can supply further information, KXStitch version, Linux distribution,
etc.  I will attempt to reproduce again.

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

[KOSMIndoorMaps] [Bug 478699] New: Building for Qt6 fails with a missing find_package line

[Steve Cossette]

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

Bug ID: 478699
   Summary: Building for Qt6 fails with a missing find_package
line
Classification: Applications
   Product: KOSMIndoorMaps
   Version: 24.01.80
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: vkra...@kde.org
  Reporter: farch...@gmail.com
  Target Milestone: ---

+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Werror=implicit-function-declaration -Werror=implicit-int
-Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64   -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64   -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3
-Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64  
-mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection
-fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1
-specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ /usr/bin/cmake -S . -B redhat-linux-build
-DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG
-DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG
-DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DBUILD_SHARED_LIBS:BOOL=ON
-DBUILD_TESTING:BOOL=FALSE -DCMAKE_BUILD_TYPE=release
-DCMAKE_INSTALL_INCLUDEDIR_kf6:PATH=/usr/include/KF6
-DCMAKE_INSTALL_LIBEXECDIR_kf6:PATH=/usr/libexec/kf6
-DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_USE_RELATIVE_PATHS:BOOL=ON
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON
-DECM_MKSPECS_INSTALL_DIR:PATH=/usr/lib64/qt6/mkspecs/modules
-DKDE_INSTALL_BINDIR:PATH=/usr/bin -DKDE_INSTALL_INCLUDEDIR:PATH=/usr/include
-DKDE_INSTALL_KCFGDIR:PATH=/usr/share/config.kcfg
-DKDE_INSTALL_LIBDIR:PATH=/usr/lib64 -DKDE_INSTALL_LIBEXECDIR:PATH=/usr/libexec
-DKDE_INSTALL_METAINFODIR:PATH=/usr/share/metainfo
-DKDE_INSTALL_PLUGINDIR:PATH=/usr/lib64/qt6/plugins
-DKDE_INSTALL_QMLDIR:PATH=/usr/lib64/qt6/qml
-DKDE_INSTALL_QTPLUGINDIR:PATH=/usr/lib64/qt6/plugins
-DKDE_INSTALL_QTQUICKIMPORTSDIR:PATH=/usr/lib64/qt6/imports
-DKDE_INSTALL_SYSCONFDIR:PATH=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS:BOOL=ON
-DQT_MAJOR_VERSION=6
-- The C compiler identification is GNU 13.2.1
-- The CXX compiler identification is GNU 13.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Performing Test HAVE_STDATOMIC
-- Performing Test HAVE_STDATOMIC - Success
-- Found WrapAtomic: TRUE  
-- Found OpenGL: /usr/lib64/libOpenGL.so   
-- Found WrapOpenGL: TRUE  
-- Found XKB: /usr/lib64/libxkbcommon.so (found suitable version "1.6.0",
minimum required is "0.5.0") 
-- Found WrapVulkanHeaders: /usr/include  
-- Found Gettext: /usr/bin/msgmerge (found version "0.22") 
-- Found KF6I18n: /usr/lib64/cmake/KF6I18n/KF6I18nConfig.cmake (found version
"5.246.0") 
-- Found KF6: success (found version "5.246.0") found components: I18n 
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.13")  
-- Found KF6CoreAddons:
/usr/lib64/cmake/KF6CoreAddons/KF6CoreAddonsConfig.cmake (found version
"5.246.0") 
-- Found KF6Service: /usr/lib64/cmake/KF6Service/KF6ServiceConfig.cmake (found
version "5.246.0") 
-- Found KF6: success (found version "5.246.0") found components: CoreAddons
Service 
-- Found OsmTools: /usr/bin/osmconvert  
-- Found FLEX: 

[plasmashell] [Bug 478561] Crash on Startup

[Steve Warren]

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

--- Comment #3 from Steve Warren  ---
The crash has not repeated, so no need for extensive effort on this.

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

[plasmashell] [Bug 478561] Crash on Startup

[Steve Warren]

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

--- Comment #2 from Steve Warren  ---
#61 0x7f1844055baa
_ZN17QQuickItemPrivate9refWindowEP12QQuickWindow (libQt5Quick.so.5 + 0x255baa)
#62 0x7f1844055fc4 _ZN10QQuickItem13setParentItemEPS_
(libQt5Quick.so.5 + 0x255fc4)
#63 0x7f1844aedd71 n/a (libKF5PlasmaQuick.so.5 + 0x30d71)

Stack trace of thread 1512:
#0  0x7f18420a4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7f18420a774c pthread_cond_timedwait (libc.so.6 +
0x8874c)
#2  0x7f18422d19bc
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd19bc)
#3  0x7f18422cf0a5 n/a (libQt5Core.so.5 + 0xcf0a5)
#4  0x7f18422cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#5  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#6  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1511:
#0  0x7f184211b05f __poll (libc.so.6 + 0xfc05f)
#1  0x7f1840e529ae n/a (libglib-2.0.so.0 + 0x549ae)
#2  0x7f1840e52acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#3  0x7f1842509836
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309836)
#4  0x7f18424b017b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2b017b)
#5  0x7f18422cab87 _ZN7QThread4execEv (libQt5Core.so.5 +
0xcab87)
#6  0x7f1843f566d6 n/a (libQt5Quick.so.5 + 0x1566d6)
#7  0x7f18422cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#8  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#9  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1513:
#0  0x7f18420a4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7f18420a774c pthread_cond_timedwait (libc.so.6 +
0x8874c)
#2  0x7f18422d19bc
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd19bc)
#3  0x7f18422cf0a5 n/a (libQt5Core.so.5 + 0xcf0a5)
#4  0x7f18422cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#5  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#6  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1134:
#0  0x7f184211b05f __poll (libc.so.6 + 0xfc05f)
#1  0x7f1843d2fcd6 n/a (libQt5WaylandClient.so.5 + 0x7acd6)
#2  0x7f18422cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#3  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#4  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1133:
#0  0x7f18420a4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7f18420a7468 pthread_cond_wait (libc.so.6 + 0x88468)
#2  0x7f18422d1a2b
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b)
#3  0x7f1843d2fc7f n/a (libQt5WaylandClient.so.5 + 0x7ac7f)
#4  0x7f18422cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#5  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#6  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1138:
#0  0x7f18420a4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7f18420a7468 pthread_cond_wait (libc.so.6 + 0x88468)
#2  0x7f183610c059 n/a (crocus_dri.so + 0x10c059)
#3  0x7f18360be17b n/a (crocus_dri.so + 0xbe17b)
#4  0x7f183610bf97 n/a (crocus_dri.so + 0x10bf97)
#5  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#6  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1139:
#0  0x7f18420a4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7f18420a7468 pthread_cond_wait (libc.so.6 + 0x88468)
#2  0x7f183610c059 n/a (crocus_dri.so + 0x10c059)
#3  0x7f18360be17b n/a (crocus_dri.so + 0xbe17b)
#4  0x7f183610bf97 n/a (crocus_dri.so + 0x10bf97)
#5  0x7f18420a8044 n/a (libc.so.6 + 0x89044)
#6  0x7f184212861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1140:
#0  0x7f184211b05f __poll (libc.so.6 + 0xfc05f)
#1  0x7f1840e529ae n/a (libglib-2.0.so.0 + 0x549ae)
#2  0x7f1840e52acc g_main_context_iteration
(libglib-2.0.so.0 + 0x54acc)
#3  0x7f1842509836
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x309836)
#4  0x7f18424b017b

[plasmashell] [Bug 478561] New: Crash on Startup

[Steve Warren]

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

Bug ID: 478561
   Summary: Crash on Startup
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: sdwa...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-15-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
Last night, I ran a Timeshift backup and then shut down. This morning's startup
reported a KDE crash.

The reporter is unsure if this crash is reproducible.

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

   PID: 1125 (plasmashell)
   UID: 1000 (steve)
   GID: 1000 (steve)
Signal: 11 (SEGV)
 Timestamp: Fri 2023-12-15 08:37:22 CST (3min 17s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (steve)
   Boot ID: 5d15495c5fc242de88ed53a6fa550df5
Machine ID: 8997a58b45ba40b58441251a2b19a31e
  Hostname: steve-Aspire-M5-581T
   Storage:
/var/lib/systemd/coredump/core.plasmashell.1000.5d15495c5fc242de88ed53a6fa550df5.1125.170265104200.zst
(present)
  Size on Disk: 10.1M
   Message: Process 1125 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.19-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.19-1~deb12u1.amd64
Stack trace of thread 1125:
#0  0x7f18420a9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7f184205af32 raise (libc.so.6 + 0x3bf32)
#2  0x7f184465ab46 _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x5b46)
#3  0x7f184205afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7f18420a9d3c n/a (libc.so.6 + 0x8ad3c)
#5  0x7f184205af32 raise (libc.so.6 + 0x3bf32)
#6  0x7f184205afd0 n/a (libc.so.6 + 0x3bfd0)
#7  0x7f18420ee385 clock_nanosleep (libc.so.6 + 0xcf385)
#8  0x7f18420f2c93 __nanosleep (libc.so.6 + 0xd3c93)
#9  0x7f184211e085 usleep (libc.so.6 + 0xff085)
#10 0x7f17cc306125 n/a (libsqlite3.so.0 + 0xaa125)
#11 0x7f17cc35cfb6 n/a (libsqlite3.so.0 + 0x100fb6)
#12 0x7f17cc35d6f2 sqlite3WalBeginReadTransaction
(libsqlite3.so.0 + 0x1016f2)
#13 0x7f17cc30edba sqlite3PagerSharedLock (libsqlite3.so.0
+ 0xb2dba)
#14 0x7f17cc297ed9 sqlite3BtreeBeginTrans (libsqlite3.so.0
+ 0x3bed9)
#15 0x7f17cc34b467 sqlite3VdbeExec (libsqlite3.so.0 +
0xef467)
#16 0x7f17cc34f29f sqlite3_step (libsqlite3.so.0 + 0xf329f)
#17 0x7f17cc3db263 n/a (libqsqlite.so + 0xa263)
#18 0x7f17cc3dd52a n/a (libqsqlite.so + 0xc52a)
#19 0x7f1842efb0f6 n/a (libQt5Sql.so.5 + 0x140f6)
#20 0x7f1842efb1a7 _ZN9QSqlQueryC1ERK7QString12QSqlDatabase
(libQt5Sql.so.5 + 0x141a7)
#21 0x7f17cda07402 n/a (libKF5ActivitiesStats.so.1 +
0x2a402)
#22 0x7f17cd9f2add n/a (libKF5ActivitiesStats.so.1 +
0x15add)
#23 0x7f17cda80ddb n/a (libkickerplugin.so + 0x4fddb)
#24 0x7f17cda7b057 n/a (libkickerplugin.so + 0x4a057)
#25 0x7f17cda5cd13 n/a (libkickerplugin.so + 0x2bd13)
#26 0x7f1843ac6c93 n/a (libQt5Qml.so.5 + 0x2c6c93)
#27 0x7f18439a3521 n/a (libQt5Qml.so.5 + 0x1a3521)
#28 0x7f18439a53e0
_ZNK3QV413QObjectMethod12callInternalEPKNS_5ValueES3_i (libQt5Qml.so.5 +
0x1a53e0)
#29 0x7f18439c1cb6 n/a (libQt5Qml.so.5 + 0x1c1cb6)
#30 0x7f18439c53df n/a (libQt5Qml.so.5 + 0x1c53df)
#31 0x7f1843957c2e
_ZN3QV48Function4callEPKNS_5ValueES3_iPKNS_16ExecutionContextE (libQt5Qml.so.5
+ 0x157c2e)
#32 0x7f1843ae144d
_ZN24QQmlJavaScriptExpression8evaluateEPN3QV48CallDataEPb (libQt5Qml.so.5 +
0x2e144d)
#33 0x7f1843a92baf
_ZN25QQmlBoundSignalExpression8evaluateEPPv (libQt5Qml.so.5 + 0x292baf)
#34 0x7f1843a942f8 n/a (libQt5Qml.so.5 + 0x2942f8)
#35 0x7f1843ac677f