[gwenview] [Bug 486769] New: gwenview not opening maximised

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=486769

Bug ID: 486769
   Summary: gwenview not opening maximised
Classification: Applications
   Product: gwenview
   Version: 24.02.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
Gwenview does not open maximized even when closed maximized. The window button
will show it's maximized, but it will only fill about a third of the screen

STEPS TO REPRODUCE
1. Open gwenview (via clicking on an image)
2. Maximize the window
3. Close and reopen

OBSERVED RESULT
The window button (top right corner in my setting) will show the window as
maximized, but it actually isn't. You have to click the maximize button twice
to make it maximize.

EXPECTED RESULT
Gwenview should remember its status and open maximized.

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: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION

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

[Discover] [Bug 484650] Reboot notification does not disappear when running "pkcon update" manually

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

--- Comment #8 from Martin Tlustos  ---
Sorry for not expressing myself clearly, I'm neither a native English speaker
nor a programmer... ;-)
And I also thought it's a very minor thing, but still should get reported so
someone more knowledgeable than I can decide whether and what to do. ;-)

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

[Discover] [Bug 484650] Reboot notification does not disappear when running "pkcon update" manually

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

--- Comment #6 from Martin Tlustos  ---
Oh, and it wouldn't go away even after closing and reopening discover (which
then refreshes the update search)

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

[Discover] [Bug 484650] Reboot notification does not disappear when running "pkcon update" manually

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

--- Comment #5 from Martin Tlustos  ---
this was after I
1) opened discover updates
2) clicked on "update all"
3) let it finish and the "reboot" notification appears
4) run "sudo pkcon update" in konsole

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

[Discover] [Bug 484650] Reboot notification does not disappear when running "pkcon update" manually

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

Martin Tlustos  changed:

   What|Removed |Added

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

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

[Discover] [Bug 484650] Reboot notification does not disappear when running "pkcon update" manually

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

--- Comment #4 from Martin Tlustos  ---
Created attachment 169301
  --> https://bugs.kde.org/attachment.cgi?id=169301=edit
discover update reboot notification inconsistency

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

[Discover] [Bug 484650] Reboot notification does not disappear when running "pkcon update" manually

2024-05-08 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

Martin Tlustos  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Tlustos  ---
I have set the system to do offline updates (apply system updates at the next
restart). So, from my limited understanding, discover would download the
updates and install them at the next reboot, then reboot again with the updates
installed, right?
The above behavior shows in that environment. It's not a big deal, just an
inconsistency.

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

[plasmashell] [Bug 485801] With mixed light/dark themes (e.g. Breeze Twilight) KSvg and Kirigami.Icon use app color scheme rather than Plasma color scheme when given an absolute path

2024-05-07 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485801

--- Comment #10 from Marco Martin  ---
So https://invent.kde.org/frameworks/ksvg/-/merge_requests/48 attempts to
always recolor images also the ones "non themed" as in taken from somewhere
else in the filesystem

Now this should be checked for possible sideeffect worst case scenario can
be added api about it, to not change default behavior

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

[plasmashell] [Bug 485801] With mixed light/dark themes (e.g. Breeze Twilight) KSvg and Kirigami.Icon use app color scheme rather than Plasma color scheme when given an absolute path

2024-05-07 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485801

--- Comment #8 from Marco Martin  ---
(In reply to Nicolas Fella from comment #5)
> Reading the KSVG code this seems to be somewhat intentional.
> 
> The documentation for KSvg::Svg
> (https://invent.kde.org/frameworks/ksvg/-/blob/master/src/ksvg/svg.
> h?ref_type=heads#L39) says
> 
> > Unless an absolute path to a file is provided, it loads the SVG document 
> > using KSvg::ImageSet
> 
> and in
> https://invent.kde.org/frameworks/ksvg/-/blob/master/src/ksvg/svg.cpp#L466
> svgs with absolute paths are considered unthemed

This is a very, very old thing that's there since 4.0 times, but i think the
behavior in that it could be safely changed: as if the svg has the proper
stylesheet things would always be styled, otherwise it wouldn't be anyways, so
i don't see danger in changing this

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

[plasmashell] [Bug 485223] Traditional Task Manager overflows space right of itself in multi row mode

2024-05-06 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485223

Marco Martin  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/-/commit/
   ||d1b33d1a9dc872e9a2af042152d
   ||6ab5ed2617e4e
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #14 from Marco Martin  ---
Git commit d1b33d1a9dc872e9a2af042152d6ab5ed2617e4e by Marco Martin.
Committed on 06/05/2024 at 07:50.
Pushed by mart into branch 'master'.

Use a GridLayout for taskbar layout

The current javascript layout code is very buggy and error prone,
The normal layouting mechanism of GridLayout is much more reliable
and does for faster and more readable code
Related: bug 424055

M  +2-2applets/taskmanager/package/contents/ui/ContextMenu.qml
M  +4-4applets/taskmanager/package/contents/ui/GroupDialog.qml
M  +1-17   applets/taskmanager/package/contents/ui/MouseHandler.qml
M  +109  -28   applets/taskmanager/package/contents/ui/Task.qml
M  +28   -14   applets/taskmanager/package/contents/ui/TaskList.qml
D  +0-246  applets/taskmanager/package/contents/ui/code/layout.js
A  +126  -0applets/taskmanager/package/contents/ui/code/layoutmetrics.js
M  +51   -49   applets/taskmanager/package/contents/ui/main.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/d1b33d1a9dc872e9a2af042152d6ab5ed2617e4e

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

[plasmashell] [Bug 424055] Pinned launchers add extra unnecessary whitespace to Traditional Task manager, causing improper centering behavior

2024-05-06 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=424055

Marco Martin  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/-/commit/
   ||d1b33d1a9dc872e9a2af042152d
   ||6ab5ed2617e4e
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Marco Martin  ---
Git commit d1b33d1a9dc872e9a2af042152d6ab5ed2617e4e by Marco Martin.
Committed on 06/05/2024 at 07:50.
Pushed by mart into branch 'master'.

Use a GridLayout for taskbar layout

The current javascript layout code is very buggy and error prone,
The normal layouting mechanism of GridLayout is much more reliable
and does for faster and more readable code
Related: bug 485223

M  +2-2applets/taskmanager/package/contents/ui/ContextMenu.qml
M  +4-4applets/taskmanager/package/contents/ui/GroupDialog.qml
M  +1-17   applets/taskmanager/package/contents/ui/MouseHandler.qml
M  +109  -28   applets/taskmanager/package/contents/ui/Task.qml
M  +28   -14   applets/taskmanager/package/contents/ui/TaskList.qml
D  +0-246  applets/taskmanager/package/contents/ui/code/layout.js
A  +126  -0applets/taskmanager/package/contents/ui/code/layoutmetrics.js
M  +51   -49   applets/taskmanager/package/contents/ui/main.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/d1b33d1a9dc872e9a2af042152d6ab5ed2617e4e

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

[yakuake] [Bug 486651] Yakuake won't fully cover the screen when a Plasma panel is configured to 'Dodge windows'

2024-05-05 Thread Martin C.
https://bugs.kde.org/show_bug.cgi?id=486651

--- Comment #1 from Martin C.  ---
Created attachment 169232
  --> https://bugs.kde.org/attachment.cgi?id=169232=edit
Yakuake width and height set to %100

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

[yakuake] [Bug 486651] New: Yakuake won't fully cover the screen when a Plasma panel is configured to 'Dodge windows'

2024-05-05 Thread Martin C.
https://bugs.kde.org/show_bug.cgi?id=486651

Bug ID: 486651
   Summary: Yakuake won't fully cover the screen when a Plasma
panel is configured to 'Dodge windows'
Classification: Applications
   Product: yakuake
   Version: 24.02.2
  Platform: NixOS
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: martincigorr...@gmail.com
  Target Milestone: ---

SUMMARY
As the title says. Otherwise, if the panel is configured to 'Auto hide',
Yakuake can correctly fill the space.
I'm not sure if this is a Yakuake issue or a Plasma issue that is not correctly
advertising the behavior of the panels; let me know if you want me to bring
this issue somewhere else.

STEPS TO REPRODUCE
1. Configure a Plasma panel to 'Dodge windows'; it doesn't matter the placement
of the panel; the issue is reproducible always
2. Configure Yakuake to fully expand on both width and height
3. Open the Yakuake window

OBSERVED RESULT
Yakuake will stop expanding when it finds a plasma panel, leaving an empty
strip along the edge of the screen.

EXPECTED RESULT
The Plasma panel will retract (hide) to dodge Yakuake's unfolding window,
allowing it to cover the designated screen space.

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

ADDITIONAL INFORMATION
Happens on my two Plasma 6 installations: NixOS `unstable` branch and Fedora
Kinoite 40.

Thanks!!

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

[plasmashell] [Bug 485456] With Qt 6.7, System Tray popup is inappropriately resized to a tiny nub

2024-05-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485456

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/libplasma/-/commit/a0949 |ma/libplasma/-/commit/6ef5f
   |c6afcff4192ffcdf43c2ef305fb |23018f02eb7cdb2523adb224f34
   |4b61f857|b7a8f22d

--- Comment #20 from Marco Martin  ---
Git commit 6ef5f23018f02eb7cdb2523adb224f34b7a8f22d by Marco Martin.
Committed on 02/05/2024 at 12:45.
Pushed by mart into branch 'Plasma/6.0'.

Workaround setMinimumSize not resizing

on wayland, setting  the  minimum size of a window, doesn't
resize it if its new minimum size is bigger then the current size
Related: bug 480722


(cherry picked from commit a0949c6afcff4192ffcdf43c2ef305fb4b61f857)

0404657c Workaround setMinimumSize not resizing
a82e4ca1 enforce bounds everywhere
e625482e Apply 1 suggestion(s) to 1 file(s)

M  +15   -5src/plasmaquick/appletpopup.cpp

https://invent.kde.org/plasma/libplasma/-/commit/6ef5f23018f02eb7cdb2523adb224f34b7a8f22d

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

[plasmashell] [Bug 480722] Clicking a GPU memory-used System Monitor freezes Plasmashell

2024-05-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=480722

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/libplasma/-/commit/a0949 |ma/libplasma/-/commit/6ef5f
   |c6afcff4192ffcdf43c2ef305fb |23018f02eb7cdb2523adb224f34
   |4b61f857|b7a8f22d

--- Comment #7 from Marco Martin  ---
Git commit 6ef5f23018f02eb7cdb2523adb224f34b7a8f22d by Marco Martin.
Committed on 02/05/2024 at 12:45.
Pushed by mart into branch 'Plasma/6.0'.

Workaround setMinimumSize not resizing

on wayland, setting  the  minimum size of a window, doesn't
resize it if its new minimum size is bigger then the current size
Related: bug 485456


(cherry picked from commit a0949c6afcff4192ffcdf43c2ef305fb4b61f857)

0404657c Workaround setMinimumSize not resizing
a82e4ca1 enforce bounds everywhere
e625482e Apply 1 suggestion(s) to 1 file(s)

M  +15   -5src/plasmaquick/appletpopup.cpp

https://invent.kde.org/plasma/libplasma/-/commit/6ef5f23018f02eb7cdb2523adb224f34b7a8f22d

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

[plasmashell] [Bug 485456] With Qt 6.7, System Tray popup is inappropriately resized to a tiny nub

2024-05-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485456

Marco Martin  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/libplasma/-/commit/a0949
   ||c6afcff4192ffcdf43c2ef305fb
   ||4b61f857
 Resolution|--- |FIXED

--- Comment #18 from Marco Martin  ---
Git commit a0949c6afcff4192ffcdf43c2ef305fb4b61f857 by Marco Martin.
Committed on 02/05/2024 at 09:50.
Pushed by mart into branch 'master'.

Workaround setMinimumSize not resizing

on wayland, setting  the  minimum size of a window, doesn't
resize it if its new minimum size is bigger then the current size
Related: bug 480722

M  +15   -5src/plasmaquick/appletpopup.cpp

https://invent.kde.org/plasma/libplasma/-/commit/a0949c6afcff4192ffcdf43c2ef305fb4b61f857

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

[plasmashell] [Bug 480722] Clicking a GPU memory-used System Monitor freezes Plasmashell

2024-05-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=480722

Marco Martin  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/libplasma/-/commit/a0949
   ||c6afcff4192ffcdf43c2ef305fb
   ||4b61f857
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Marco Martin  ---
Git commit a0949c6afcff4192ffcdf43c2ef305fb4b61f857 by Marco Martin.
Committed on 02/05/2024 at 09:50.
Pushed by mart into branch 'master'.

Workaround setMinimumSize not resizing

on wayland, setting  the  minimum size of a window, doesn't
resize it if its new minimum size is bigger then the current size
Related: bug 485456

M  +15   -5src/plasmaquick/appletpopup.cpp

https://invent.kde.org/plasma/libplasma/-/commit/a0949c6afcff4192ffcdf43c2ef305fb4b61f857

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

[kdeconnect] [Bug 486356] New: can't lock phone from pc

2024-04-30 Thread Martin Ross
https://bugs.kde.org/show_bug.cgi?id=486356

Bug ID: 486356
   Summary: can't lock phone from pc
Classification: Applications
   Product: kdeconnect
   Version: 24.02.2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: windows-application
  Assignee: piyushaggarwal...@gmail.com
  Reporter: martinjohnr...@gmail.com
  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
Can't lock phone from PC

STEPS TO REPRODUCE
1. click on 'lock'
2. 
3. 

OBSERVED RESULT
nothing happens

EXPECTED RESULT
phone should lock

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

ADDITIONAL INFORMATION

Android 13

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

[kdeconnect] [Bug 486251] KDEConnect spams MDNS query errors in log

2024-04-28 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=486251

--- Comment #1 from Martin  ---
Created attachment 168971
  --> https://bugs.kde.org/attachment.cgi?id=168971=edit
Seemingly one of the "Error sending MDNS query response" wireshark captures

Not sure which part of this errors out of it is supposed to have more back and
forth, but it seems to be the thing behind one of the issues.

Capture is attached, short version:

14:17:08.631641324  192.168.1.156   224.0.0.251 MDNS113
Standard query 0x PTR _kdeconnect._udp.local, "QM" question PTR
15447d7f50b6f64d._kdeconnect._udp.local

14:17:08.631801298  fe80::61bc:2d94:7824:ea83   ff02::fbMDNS   
133 Standard query 0x PTR _kdeconnect._udp.local, "QM" question PTR
15447d7f50b6f64d._kdeconnect._udp.local

14:17:08.631810124  192.168.1.10224.0.0.251 MDNS292
Standard query response 0x PTR
_b23e5f59_4ad3_4f23_a64c_db862d04ce0f_._kdeconnect._udp.local SRV 0 0 1716
Luxuria.local A 192.168.1.10  fdb9:9e13:d719:0:5aa:7f9a:caa4:dd53 TXT

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

[kdeconnect] [Bug 486251] New: KDEConnect spams MDNS query errors in log

2024-04-28 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=486251

Bug ID: 486251
   Summary: KDEConnect spams MDNS query errors in log
Classification: Applications
   Product: kdeconnect
   Version: 24.02.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: spleefe...@gmail.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY

This just seems to occur 3 times in the same moment every minute or less,
sometimes multiple times in a minute when I started trying to reproduce it by
clicking around in kdeconnect and avahi-discover:
  Apr 28 16:08:37 Luxuria kdeconnectd[11570]: 2024-04-28T16:08:37
kdeconnect.core: Error sending MDNS query response

If I click Refresh on the devices, I get 21~ errors like this at once,
reproducable:
  Apr 28 16:11:07 Luxuria kdeconnectd[11570]: 2024-04-28T16:11:07
kdeconnect.core: Failed to send mDNS query: Cannot assign requested address

OBSERVED RESULT
Spam in logs with no idea why

EXPECTED RESULT
No spam at all, or at least with an explanation why they're occurring. Which
address cannot be assigned? Which what query response exactly is erroring?

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 AORUS ELITE AX

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

[systemsettings] [Bug 485900] "Night color" not applying day time temperature automatically

2024-04-26 Thread Martin Seidel
https://bugs.kde.org/show_bug.cgi?id=485900

Martin Seidel  changed:

   What|Removed |Added

 CC||web.msei...@mailbox.org

--- Comment #3 from Martin Seidel  ---
I also have this problem on Debian testing:

KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.6.15-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Memory: 27.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics

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

[kinfocenter] [Bug 486157] New: lspci | grep -i audio says: 00:1f.3 Audio device: Intel Corporation Jasper Lake HD Audio (rev 01). But I found no way to let it work.

2024-04-26 Thread John Martin Ungar
https://bugs.kde.org/show_bug.cgi?id=486157

Bug ID: 486157
   Summary: lspci | grep -i audio says: 00:1f.3 Audio device:
Intel Corporation Jasper Lake HD Audio (rev 01). But I
found no way to let it work.
Classification: Applications
   Product: kinfocenter
   Version: 5.27.11
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: schwarzb...@dokom.net
CC: sit...@kde.org
  Target Milestone: ---

lspci | grep -i audio 
00:1f.3 Audio device: Intel Corporation Jasper Lake HD Audio (rev 01)

 But is not installed/working...

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

[digikam] [Bug 486132] XMP file is not created if directory contains non-ascii UTF-8 chars

2024-04-25 Thread martin
https://bugs.kde.org/show_bug.cgi?id=486132

--- Comment #1 from martin  ---
I am actually not sure about reading/interpreting XMP files inside "ř"
directory.
It seems that rating is somehow loaded from database. If I copy XMP file into
"ř" directory, it doesn't change rating of the JPG file there.

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

[digikam] [Bug 486132] New: XMP file is not created if directory contains non-ascii UTF-8 chars

2024-04-25 Thread martin
https://bugs.kde.org/show_bug.cgi?id=486132

Bug ID: 486132
   Summary: XMP file is not created if directory contains
non-ascii UTF-8 chars
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Sidecar
  Assignee: digikam-bugs-n...@kde.org
  Reporter: gfoiwe...@seznam.cz
  Target Milestone: ---

If I place JPG files into subdirectory "ř", XMP files are never created.
If I place the same JPG files into subdirectory "r", XMP files are created
correctly.
I can even copy XMP files from directory "r" to "ř" and they are
read/interpreted correctly (for JPG files inside "ř"), but never updated.

Same result with HEIC files.

Writing metadata into JPG files works just fine.

My Settings -> Metadata: 

Write this Information to the Metadata: Image tags + Rating
Delegate to ExifTool backend all operations to write metadata to files: (can be
true or false, doesn't change anything)
Sidecars/Write to sidecar files: Write to XMP sidecar only

If I set it to "Write to item and XMP Sidecar", then the JPG files are modified
correctly (event inside "ř" directory), but XMP files are still never created.

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

[plasmashell] [Bug 485223] Traditional Task Manager overflows space right of itself in multi row mode

2024-04-24 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485223

--- Comment #13 from Marco Martin  ---
Git commit 9ad41c26e0bbe57b7c19883fc5db772613a5d6ca by Marco Martin.
Committed on 24/04/2024 at 07:37.
Pushed by mart into branch 'Plasma/6.0'.

On multiline launchers are often as wide as tasks

Since on multiline launchers are often as big as tasks,
don't remove launchers count from the task count when we're on multiline
It's only a partial solution and tasks won't always be optimally wide,
but is a simple one that can be cherrypicked to 6.0

In the long term the custom layouting code should be removed and be ported to
a standard GridLayout


(cherry picked from commit 0c576c940b1db0433a7e9b3dd0248948ed5f9368)

0c576c94 On multiline launchers are often as wide as tasks

M  +9-0applets/taskmanager/package/contents/ui/code/layout.js

https://invent.kde.org/plasma/plasma-desktop/-/commit/9ad41c26e0bbe57b7c19883fc5db772613a5d6ca

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

[kdenlive] [Bug 485804] Kan na installatie niet activeren.

2024-04-23 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485804

--- Comment #2 from Martin  ---
Thanks for your help!


It works, Ill will start with KDENLive


Regards,

Martin

> Op 23 apr. 2024, om 13:38 heeft emohr  het volgende 
> geschreven:
> 
> https://bugs.kde.org/show_bug.cgi?id=485804
> 
> emohr  changed:
> 
>   What|Removed |Added
> 
> CC||fritzib...@gmx.net
>  Flags||timeline_corruption+
> 
> --- Comment #1 from emohr  ---
> Please follow these steps:
> https://docs.kdenlive.org/en/getting_started/installation.html#kdenlive-on-macos
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[plasmashell] [Bug 485456] Qith Qt 6.7, System Tray popup is inappropriately resized to a tiny nub

2024-04-23 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485456

Martin  changed:

   What|Removed |Added

 CC||z...@inversi0n.org

--- Comment #10 from Martin  ---
This has been happening to me for a few days as well.

It usually works as expected in a new session, at some point it breaks to the
described tiny nub.

Changing the scaling (I usually do 125, 130 or 135%) seems to temporarily fix
it for me. My windows are usually garbled after the screen has been locked or
my computer has suspended, and I suspect that to be the trigger for the system
tray popups as well.

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

[plasmashell] [Bug 485223] Traditional Task Manager overflows space right of itself in multi row mode

2024-04-23 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485223

--- Comment #11 from Marco Martin  ---
Git commit 0c576c940b1db0433a7e9b3dd0248948ed5f9368 by Marco Martin.
Committed on 23/04/2024 at 07:32.
Pushed by mart into branch 'master'.

On multiline launchers are often as wide as tasks

Since on multiline launchers are often as big as tasks,
don't remove launchers count from the task count when we're on multiline
It's only a partial solution and tasks won't always be optimally wide,
but is a simple one that can be cherrypicked to 6.0

In the long term the custom layouting code should be removed and be ported to
a standard GridLayout

M  +9-0applets/taskmanager/package/contents/ui/code/layout.js

https://invent.kde.org/plasma/plasma-desktop/-/commit/0c576c940b1db0433a7e9b3dd0248948ed5f9368

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

[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard

2024-04-22 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=368063

Martin  changed:

   What|Removed |Added

 CC||spleefe...@gmail.com

--- Comment #60 from Martin  ---
(this thread is linked in other places)

New bug report can be found here - https://bugs.kde.org/show_bug.cgi?id=485940

Adjacent bug report is also here (on=on but last-state==on=off) -
https://bugs.kde.org/show_bug.cgi?id=454478

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

[kde] [Bug 485804] New: Kan na installatie niet activeren.

2024-04-19 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485804

Bug ID: 485804
   Summary: Kan na installatie niet activeren.
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mart.co...@gmail.com
  Target Milestone: ---

Created attachment 168685
  --> https://bugs.kde.org/attachment.cgi?id=168685=edit
Melding bij installatie

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


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kmail2] [Bug 485715] New: update count in unified mailboxes don't always get updated

2024-04-18 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=485715

Bug ID: 485715
   Summary: update count in unified mailboxes don't always get
updated
Classification: Applications
   Product: kmail2
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
I have unified mailbox set up to show inbox, sent mail, drafts, templates and
spam. I have two google accounts and one office 365 account.
When opening gmail web and marking a message in the spam folder there as "not
spam" (where it gets moved into the inbox folder), the changes are reflected in
my normal folders, but the unified mailbox still shows the unread number,
although it doesn't show the message anymore (because it has been moved to the
inbox).
Minor stuff, but still a bug.

STEPS TO REPRODUCE
1. have an unread message in google spam folder
2. open gmail and mark this message as "not spam"
3. in kmail, right click on according gmail account and select "update all"

OBSERVED RESULT
Message count gets updated accordingly in original folders, but not in unified
mailbox folders (the inbox folder gets updated, as there is one more message
now).

EXPECTED RESULT
the unread count numbers should update as well.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION

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

[dolphin] [Bug 485692] Shell integration cannot handle long filenames

2024-04-17 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485692

--- Comment #1 from Martin  ---
mkdir
/tmp/XABCDEFGHIJKLMNOPQRSTUVWXYZ

dolphin
/tmp/XABCDEFGHIJKLMNOPQRSTUVWXYZ

Better repro, it seems that max file path is 246+1 where the 247th char will be
the end of the path.

[0] %  cd
/tmp/XABCDEFGHIJKLZ
cd: no such file or directory:
/tmp/XABCDEFGHIJKLZ

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

[dolphin] [Bug 485692] New: Shell integration cannot handle long filenames

2024-04-17 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485692

Bug ID: 485692
   Summary: Shell integration cannot handle long filenames
Classification: Applications
   Product: dolphin
   Version: 24.02.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: panels: terminal
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: spleefe...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Shell integration cannot handle long filenames, at least not in zsh.

STEPS TO REPRODUCE
1. mkdir -p
/tmp/udio/alfabetagamma
2. dolphin
/tmp/udio/
3. Open terminal with F4
4. Double click alfabetagamma

OBSERVED RESULT
[0] %  cd
/tmp/udio/alfabetaa
cd: no such file or directory:
/tmp/udio/alfabetaa

The file or folder
/tmp/udio/alfabetaa
does not exist.


EXPECTED RESULT
Open folderarc

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 AORUS ELITE AX

ADDITIONAL INFORMATION

With the terminal closed this issue does not happen.
Using zsh.

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

[plasmashell] [Bug 485223] Traditional Task Manager overflows space right of itself in multi row mode

2024-04-16 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485223

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #7 from Marco Martin  ---
There are 2 issues here: 

* the launchers taking the space of a full task item: at the moment it's an
architectural thing that will need a bit of a refactor to be able to be
changed.
* the taskbar overflowing its allowed space: this takes the priority for now as
is a bug also within the current architecture

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

[plasmashell] [Bug 485588] Application Dashboard: Can't run searched commands using keyboard

2024-04-16 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485588

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/
   |9817d455fcfb1897f74dfdbcdf3 |86faa13193b51cc789d0f89d55f
   |de50e9fd66d77   |6a6ae20ccd984

--- Comment #3 from Marco Martin  ---
Git commit 86faa13193b51cc789d0f89d55f6a6ae20ccd984 by Marco Martin.
Committed on 16/04/2024 at 12:12.
Pushed by mart into branch 'Plasma/6.0'.

Fix keyboard navigation

As a fallout from porting to kf6, there were sevaral items that were
renamed and not all users now accessed the proper id

this fixes keyboard navigation in krunner results and "all applications" view
Related: bug 477348


(cherry picked from commit 9817d455fcfb1897f74dfdbcdf3de50e9fd66d77)

f290bb9e Fix keyboard navigation

M  +2-0applets/kicker/package/contents/ui/DashboardRepresentation.qml
M  +37   -37   applets/kicker/package/contents/ui/ItemMultiGridView.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/86faa13193b51cc789d0f89d55f6a6ae20ccd984

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

[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching

2024-04-16 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=477348

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/
   |9817d455fcfb1897f74dfdbcdf3 |86faa13193b51cc789d0f89d55f
   |de50e9fd66d77   |6a6ae20ccd984

--- Comment #8 from Marco Martin  ---
Git commit 86faa13193b51cc789d0f89d55f6a6ae20ccd984 by Marco Martin.
Committed on 16/04/2024 at 12:12.
Pushed by mart into branch 'Plasma/6.0'.

Fix keyboard navigation

As a fallout from porting to kf6, there were sevaral items that were
renamed and not all users now accessed the proper id

this fixes keyboard navigation in krunner results and "all applications" view
Related: bug 485588


(cherry picked from commit 9817d455fcfb1897f74dfdbcdf3de50e9fd66d77)

f290bb9e Fix keyboard navigation

M  +2-0applets/kicker/package/contents/ui/DashboardRepresentation.qml
M  +37   -37   applets/kicker/package/contents/ui/ItemMultiGridView.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/86faa13193b51cc789d0f89d55f6a6ae20ccd984

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

[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching

2024-04-16 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=477348

Marco Martin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/-/commit/
   ||9817d455fcfb1897f74dfdbcdf3
   ||de50e9fd66d77

--- Comment #7 from Marco Martin  ---
Git commit 9817d455fcfb1897f74dfdbcdf3de50e9fd66d77 by Marco Martin.
Committed on 16/04/2024 at 08:01.
Pushed by mart into branch 'master'.

Fix keyboard navigation

As a fallout from porting to kf6, there were sevaral items that were
renamed and not all users now accessed the proper id

this fixes keyboard navigation in krunner results and "all applications" view
Related: bug 485588

M  +2-0applets/kicker/package/contents/ui/DashboardRepresentation.qml
M  +37   -37   applets/kicker/package/contents/ui/ItemMultiGridView.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/9817d455fcfb1897f74dfdbcdf3de50e9fd66d77

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

[plasmashell] [Bug 485588] Application Dashboard: Can't run searched commands using keyboard

2024-04-16 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485588

Marco Martin  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/-/commit/
   ||9817d455fcfb1897f74dfdbcdf3
   ||de50e9fd66d77
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from Marco Martin  ---
Git commit 9817d455fcfb1897f74dfdbcdf3de50e9fd66d77 by Marco Martin.
Committed on 16/04/2024 at 08:01.
Pushed by mart into branch 'master'.

Fix keyboard navigation

As a fallout from porting to kf6, there were sevaral items that were
renamed and not all users now accessed the proper id

this fixes keyboard navigation in krunner results and "all applications" view
Related: bug 477348

M  +2-0applets/kicker/package/contents/ui/DashboardRepresentation.qml
M  +37   -37   applets/kicker/package/contents/ui/ItemMultiGridView.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/9817d455fcfb1897f74dfdbcdf3de50e9fd66d77

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

[plasmashell] [Bug 484687] plasma crash after waking monitor

2024-04-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484687

--- Comment #8 from Marco Martin  ---
Git commit da35849d5f4913221ba362d3961fd29526f364d5 by Marco Martin.
Committed on 15/04/2024 at 12:37.
Pushed by mart into branch 'Plasma/6.0'.

Fix redundantoutputs when the enabled screens change very quickly

on X11, when a single transaction from KScreen disables screenA and
enabled screenB, a new output order arrivers before the old output gets removed
 and in that moment the new screen will be considered redundant to che screen
that is about to be removed, causing an invalid internal state
Related: bug 456947


(cherry picked from commit dfd160bdf6f660c10b712a664c86a2a7339e8e72)

c6ff79fd Fix redundantoutputs when the enabled screens change very quickly

M  +4-3shell/screenpool.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/da35849d5f4913221ba362d3961fd29526f364d5

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

[plasmashell] [Bug 456947] On X11, Plasma crashes in ShellCorona::screenInvariants() when computer starts up without screen or monitor

2024-04-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=456947

--- Comment #16 from Marco Martin  ---
Git commit da35849d5f4913221ba362d3961fd29526f364d5 by Marco Martin.
Committed on 15/04/2024 at 12:37.
Pushed by mart into branch 'Plasma/6.0'.

Fix redundantoutputs when the enabled screens change very quickly

on X11, when a single transaction from KScreen disables screenA and
enabled screenB, a new output order arrivers before the old output gets removed
 and in that moment the new screen will be considered redundant to che screen
that is about to be removed, causing an invalid internal state
Related: bug 484687


(cherry picked from commit dfd160bdf6f660c10b712a664c86a2a7339e8e72)

c6ff79fd Fix redundantoutputs when the enabled screens change very quickly

M  +4-3shell/screenpool.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/da35849d5f4913221ba362d3961fd29526f364d5

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

[plasmashell] [Bug 484687] plasma crash after waking monitor

2024-04-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484687

--- Comment #6 from Marco Martin  ---
Git commit dfd160bdf6f660c10b712a664c86a2a7339e8e72 by Marco Martin.
Committed on 15/04/2024 at 12:36.
Pushed by mart into branch 'master'.

Fix redundantoutputs when the enabled screens change very quickly

on X11, when a single transaction from KScreen disables screenA and
enabled screenB, a new output order arrivers before the old output gets removed
 and in that moment the new screen will be considered redundant to che screen
that is about to be removed, causing an invalid internal state
Related: bug 456947

M  +4-3shell/screenpool.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/dfd160bdf6f660c10b712a664c86a2a7339e8e72

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

[plasmashell] [Bug 456947] On X11, Plasma crashes in ShellCorona::screenInvariants() when computer starts up without screen or monitor

2024-04-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=456947

--- Comment #14 from Marco Martin  ---
Git commit dfd160bdf6f660c10b712a664c86a2a7339e8e72 by Marco Martin.
Committed on 15/04/2024 at 12:36.
Pushed by mart into branch 'master'.

Fix redundantoutputs when the enabled screens change very quickly

on X11, when a single transaction from KScreen disables screenA and
enabled screenB, a new output order arrivers before the old output gets removed
 and in that moment the new screen will be considered redundant to che screen
that is about to be removed, causing an invalid internal state
Related: bug 484687

M  +4-3shell/screenpool.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/dfd160bdf6f660c10b712a664c86a2a7339e8e72

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

[plasmashell] [Bug 456947] On X11, Plasma crashes in ShellCorona::screenInvariants() when computer starts up without screen or monitor

2024-04-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=456947

--- Comment #13 from Marco Martin  ---
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4238  *might*
fix that, needs to see if it will make sentry reports go down

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

[plasmashell] [Bug 484687] plasma crash after waking monitor

2024-04-15 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484687

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #5 from Marco Martin  ---
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4238 *might*
fix that, at least fixes it for the way i could reproduce (disabling internal
monitor and enabling external in one go from the kcm) needs to see if it will
make sentry reports go down

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

[Skanpage] [Bug 482224] Add ability to import PDF document to add a new page into an existing PDF document

2024-04-14 Thread Martin Steigerwald
https://bugs.kde.org/show_bug.cgi?id=482224

--- Comment #4 from Martin Steigerwald  ---
Thank you very much, Alexander!

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

[plasmashell] [Bug 477317] Non-floating Panel with "Fit Content" does not take the correct width on plasmashell start if Digital Clock is present, but resizes to correct width if "Edit Mode" is activa

2024-04-12 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=477317

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi
   |t/6016a816d5788a7a621f9bdae |t/4e37c1d1c23773df6dff95ae1
   |f194979229081f4 |1b58df8b04ab3f4

--- Comment #38 from Marco Martin  ---
Git commit 4e37c1d1c23773df6dff95ae11b58df8b04ab3f4 by Marco Martin.
Committed on 12/04/2024 at 09:23.
Pushed by mart into branch 'master'.

Never set minimum/maximum size

a long time ago we used minimum/maximum window sizes
for the minimum and maximum length of the panel, but now this
is not necessary anymore as they are stored separatedly.

setting minimum then maximum then resizing can sometimes cause
several subsequent resize attempts, and a wrong order of setminimum/setMaximum
can even fail the resize completely

The size is saved as a private member as source of truth: when we reposition
the panel
we can have not yet received a configure event of the last size we called
resize()
upon, making that former resize fail

M  +18   -54   shell/panelview.cpp

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

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

[dolphin] [Bug 484018] KDE Plasma in Wayland does not support Drag and Drop operations from Dolphin to Chromium (and Firefox).

2024-04-12 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=484018

Martin  changed:

   What|Removed |Added

 CC||spleefe...@gmail.com

--- Comment #3 from Martin  ---
I can't reproduce the exact issue as OP, but I can 100% reproduce at least a
very similar issue in the same browser on a more up to date setup.

Drag and drop seems to depend on last-touched window.

For example, if I drag a file from Dolphin over VSC(Electron) and then to the
target Chromium window with https://www.virustotal.com/gui/home/upload it works
fine.

But if the last thing I dragged over is Plasma notifications, it will have the
red crossed out O and won't let me upload. In that state, I can change the
last-dragged-through-element by hovering over VSC again and back to Chromium,
and the icon will change and it will work.

Note that there is currently a bug in current Chromium versions where drag and
drop will break the browser, and the workaround is to do drag and drop again
without actually dropping the file to re-enable it. 

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-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 AORUS ELITE AX

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

[kwin] [Bug 484394] Dragging tabs from Firefox on to the Desktop is inaccurate and unreliable

2024-04-12 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=484394

Martin  changed:

   What|Removed |Added

 CC||spleefe...@gmail.com

--- Comment #3 from Martin  ---
Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=484336

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

[plasmashell] [Bug 485303] Mouse cannot select desktops on pager on floating panel

2024-04-10 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485303

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #2 from Marco Martin  ---
does this happens only when the pager is configured to have multiple lines?

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

[kwin] [Bug 485304] Missing Grey Scale option in desktop effects

2024-04-10 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=485304

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com
   Severity|normal  |wishlist

--- Comment #1 from Marco Martin  ---
might be important indeed for accessibility reasons, marking as wishlist but
should be quite easy to do

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

[plasmashell] [Bug 483702] Plasma crashed when opening the "leave" menu in Kickoff

2024-04-10 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=483702

--- Comment #7 from Marco Martin  ---
an interesting part is
/usr/src/debug/libplasma/libplasma-6.0.2/src/declarativeimports/plasmaextracomponents/qmenu.cpp:469

where in the end is crashing in qt internally attempting to create the platform
window with winId()

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

[plasmashell] [Bug 483702] Plasma crashed when opening the "leave" menu in Kickoff

2024-04-10 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=483702

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #6 from Marco Martin  ---
pasting the second bt inline 

Thread 1 (Thread 0x7442a281b9c0 (LWP 8979)):
[KCrash Handler]
#5  std::__atomic_base::fetch_add (__m=std::memory_order_acq_rel, __i=1,
this=0x107b83484d7e01, this=, __i=,
__m=) at /usr/include/c++/13.2.1/bits/atomic_base.h:633
#6  QAtomicOps::ref (_q_value=, _q_value=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qatomic_cxx11.h:258
#7  QBasicAtomicInteger::ref (this=0x107b83484d7e01, this=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qbasicatomic.h:49
#8  QtSharedPointer::ExternalRefCountData::getAndRef
(obj=obj@entry=0x595a9a0e2270) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer.cpp:1409
#9  0x7442a7d78170 in QWeakPointer::QWeakPointer
(ptr=0x595a9a0e2270, this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer_impl.h:685
#10 QWeakPointer::assign (this=0x595a9e5bcee0,
ptr=0x595a9a0e2270) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer_impl.h:680
#11 0x7442a7dc9957 in QPointer::operator= (p=0x595a9a0e2270,
this=0x595a9e5bcee0, this=, p=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qpointer.h:68
#12 QWindowPrivate::connectToScreen (screen=, this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qwindow.cpp:481
#13 QWindowPrivate::setTopLevelScreen (this=0x595a9e5bcd90,
newScreen=0x595a9a0e2270, recreate=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qwindow.cpp:506
#14 0x7442a95312d7 in QWidgetPrivate::create
(this=this@entry=0x595a9cfc3220) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.cpp:1283
#15 0x7442a95300f2 in QWidget::create (this=0x595a9cfef370,
window=, initializeWindow=,
destroyOldWindow=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.cpp:1174
#16 0x7442a9530a87 in QWidgetPrivate::createWinId (this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.cpp:2377
#17 0x7442a9530b03 in QWidget::winId (this=0x595a9cfef370) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.h:101
#18 QWidget::winId (this=0x595a9cfef370) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.cpp:2341
#19 0x74428af9fcad in QMenuProxy::openInternal
(this=this@entry=0x595a9cecabe0, pos=...) at
/usr/src/debug/libplasma/libplasma-6.0.2/src/declarativeimports/plasmaextracomponents/qmenu.cpp:469
#20 0x74428afa0210 in QMenuProxy::openRelative (this=0x595a9cecabe0) at
/usr/src/debug/libplasma/libplasma-6.0.2/src/declarativeimports/plasmaextracomponents/qmenu.cpp:460
#21 0x74428afa8334 in QMenuProxy::qt_metacall (this=0x595a9cecabe0,
_c=QMetaObject::InvokeMetaMethod, _id=13, _a=0x7fffe297d820) at
/usr/src/debug/libplasma/build/src/declarativeimports/plasmaextracomponents/plasmaextracomponentsplugin_autogen/include/moc_qmenu.cpp:670
#22 0x7442a88d7d64 in QQmlObjectOrGadget::metacall (this=0x7fffe297da90,
type=QMetaObject::InvokeMetaMethod, index=, argv=) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlobjectorgadget.cpp:14
#23 0x7442a87b6a86 in QV4::CallMethod
(callType=QMetaObject::InvokeMetaMethod, callArgs=,
engine=0x595a9a60c3a0, argTypes=0x0, argCount=0, returnType=...,
index=, object=...) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:1563
#24 QV4::CallPrecise (object=..., data=..., engine=,
engine@entry=0x595a9a60c3a0, callArgs=,
callArgs@entry=0x74426d3bf578,
callType=callType@entry=QMetaObject::InvokeMetaMethod) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:1856
#25 0x7442a87bb239 in operator() (__closure=) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2753
#26 operator() > (call=,
__closure=) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2730
#27 QV4::QObjectMethod::callInternal (this=0x7fffe297dba0,
thisObject=, argv=0x74426d3bf4f8, argc=0) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2753
#28 0x7442a8800efa in QV4::Moth::VME::interpret (frame=0x7fffe297df50,
engine=0x595a9a60c3a0, code=0x595a9cfe0aa0 "\240\205x\250Bt") at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4vme_moth.cpp:902
#29 0x7442a88045c5 in QV4::Moth::VME

[kup] [Bug 482015] Kup system tray icon and settings module missing on Plasma 6

2024-04-10 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=482015

Martin Tlustos  changed:

   What|Removed |Added

 CC||martin.tlus...@gmail.com

--- Comment #13 from Martin Tlustos  ---
When will this become available to the public? It doesn't work on my laptop
yet... (backups work, though, so that much is fine).

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

[kscreenlocker] [Bug 485216] Login screen lists users with /usr/bin/nologin shell

2024-04-08 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485216

Martin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin  ---
I got confused because I was used to a different theme for years, this is SDDM.

https://github.com/sddm/sddm/issues/1909

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

[kscreenlocker] [Bug 485216] New: Login screen lists users with /usr/bin/nologin shell

2024-04-08 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=485216

Bug ID: 485216
   Summary: Login screen lists users with /usr/bin/nologin shell
Classification: Plasma
   Product: kscreenlocker
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: spleefe...@gmail.com
  Target Milestone: ---

I think this was introduced in 6.0.3.

This user is not in login screen:
incus:x:942:942:Incus user:/var/lib/incus:/usr/bin/nologin

This user is:
oauth2-proxy:x:1056:1057::/:/usr/bin/nologin

It looks like the current code only checks UID >999 and ignores the fact user
explicitly has nologin as the shell.

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.2-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 62.0 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670 AORUS ELITE AX

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

[plasmashell] [Bug 449034] Reset "expose password text" setting when UI fades out

2024-04-05 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=449034

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/commit/ |ma/plasma-desktop/-/commit/
   |00576ef1499a319791b217fedd2 |bfb048a5412d4a58839de361889
   |34f2ed6e92ed8   |717a4d97d4180

--- Comment #6 from Marco Martin  ---
Git commit bfb048a5412d4a58839de361889717a4d97d4180 by Marco Martin, on behalf
of Nate Graham.
Committed on 05/04/2024 at 11:25.
Pushed by mart into branch 'master'.

Reset "show password" status on lock and login screens when fading in

Otherwise, if the user earlier turned on the "show password" feature and
then forgot about it and let the UI fade out, when it fades back in and
they start typing their password again, it will be entered in the clear.
FIXED-IN; 5.27.5

M  +1-0Main.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/bfb048a5412d4a58839de361889717a4d97d4180

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

[kwin] [Bug 466969] Tapping Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)

2024-04-05 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=466969

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/commit/ |ma/plasma-desktop/-/commit/
   |e7c7a0688418f8111760b9fdfe0 |4580d0437735f895993e3b7ccbe
   |9c3ddb1c1c88f   |c2b942b195e99

--- Comment #13 from Marco Martin  ---
Git commit 4580d0437735f895993e3b7ccbec2b942b195e99 by Marco Martin, on behalf
of Aleix Pol i Gonzalez.
Committed on 05/04/2024 at 11:25.
Pushed by mart into branch 'master'.

sddm-theme: Transfer the focus to the text field as we show the OSK

Borrowed from the lockscreen, we need to make sure the correct component
is focussed, otherwise the Virtual Keyboard cannot find its purpose.

M  +6-1Main.qml

https://invent.kde.org/plasma/plasma-desktop/-/commit/4580d0437735f895993e3b7ccbec2b942b195e99

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

[plasmashell] [Bug 484826] Plasmoid crashes on editing when Plasma5Support.DataSource sets its interval to 0

2024-04-03 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484826

--- Comment #5 from Marco Martin  ---
(In reply to NSLW from comment #3)
> Ok, but you do have Workrave running and see timers ticking, correct? It
> won't crash if all that you see is a placeholder image of a sheep (that
> means no Workrave installed and running or no qdbus or qdbus-qt6 command
> detected).

yeah, i tried with workrave up and running.

> 
> Would a coredump be any help to you?

a complete coredump would be very useful indeed, thanks :)

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

[plasmashell] [Bug 483985] plasmashell crashes in QQuickAccessibleAttached::setRole

2024-04-03 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=483985

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #11 from Marco Martin  ---
issue in sentry:
https://crash-reports.kde.org/organizations/kde/issues/5916/?project=9

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

[plasmashell] [Bug 484924] Plasmashell crash on qquickaccessibleattached.cpp

2024-04-03 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484924

--- Comment #2 from Marco Martin  ---
Quick google translate:

Plasmashell closes spontaneously, apparently when an application that has a
component in GTK, this has happened to me when maximizing Discord, the entire
plasmashell restarts several times

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

[plasmashell] [Bug 484826] Plasmoid crashes on editing when Plasma5Support.DataSource sets its interval to 0

2024-04-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484826

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #2 from Marco Martin  ---
can't reproduce

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

[plasmashell] [Bug 484842] Icons-Only Task Manager Goes From Partially Broken to Crashing Plasma

2024-04-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484842

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #2 from Marco Martin  ---
pasting inline. in the backtrace there is some suspect stuff about
screencasting/pipewire (taskbar thumbnails)

Thread 1 "plasmashell" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=140737230232256) at
./nptl/pthread_kill.c:44
Download failed: Invalid argument.  Continuing without source file
./nptl/./nptl/pthread_kill.c.
44  ./nptl/pthread_kill.c: No such file or directory.
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737230232256)
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140737230232256) at
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140737230232256, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#3  0x74a42476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#4  0x74a287f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x756db597 in qAbort() () at ./src/corelib/global/qglobal.cpp:161
#6  0x756d67f5 in qt_message_fatal (message=...,
context=)
at ./src/corelib/global/qlogging.cpp:2003
#7  qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *)
(msgType=msgType@entry=QtFatalMsg, context=, msg=, ap=ap@entry=0x7fff6f90)
at ./src/corelib/global/qlogging.cpp:378
#8  0x756dbfc3 in QMessageLogger::fatal(char const*, ...) const
(this=, msg=)
at ./src/corelib/global/qlogging.cpp:901
#9  0x756a0327 in qt_assert(char const*, char const*, int)
(assertion=assertion@entry=0x7fff93f14267 "isInitialized()",
file=file@entry=0x7fff93f14150
"./libtaskmanager/declarative/screencasting.cpp", line=line@entry=75) at
./src/corelib/global/qassert.cpp:68
#10 0x7fff93f0bc26 in
ScreencastingPrivate::ScreencastingPrivate(Screencasting*)
 (this=0x592f3060, q=0x58ac7380) at
./libtaskmanager/declarative/screencasting.cpp:66
#11 ScreencastingPrivate::ScreencastingPrivate(Screencasting*)
(q=0x58ac7380, this=0x592f3060)
at ./libtaskmanager/declarative/screencasting.cpp:66
#12 Screencasting::Screencasting(QObject*) (this=this@entry=0x58ac7380,
parent=parent@entry=0x59281770)
at ./libtaskmanager/declarative/screencasting.cpp:90
#13 0x7fff93f121da in ScreencastingRequest::setUuid(QString const&)
(this=0x59281770, uuid=...)
at ./libtaskmanager/declarative/screencastingrequest.cpp:48
#14 0x7642ae98 in QQmlPropertyData::writeProperty(QObject*, void*,
QFlags) const
(this=, target=, value=,
flags=...)
at ./src/qml/qml/qqmlpropertydata_p.h:338
#15 0x76455810 in tryConvertAndAssign
(isUrl=false, variantMetaType=..., propertyMetaType=..., flags=...,
value=..., property=..., object=0x59281770) at
./src/qml/qml/qqmlproperty.cpp:1442
#16 QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant
const&, QQmlRefPointer const&,
QFlags) (object=0x59281770, property=...,
value=..., context=, flags=...) at
./src/qml/qml/qqmlproperty.cpp:1555
#17 0x764c8700 in QQmlBinding::slowWrite(QQmlPropertyData const&,
QQmlPropertyData const&, QV4::Value const&, bool,
QFlags) (this=, core=...,
valueTypeData=..., result=..., isUndefined=, flags=...) at
./src/qml/qml/qqmlbinding.cpp:540
#18 0x7651e5c2 in GenericBinding<10>::write(QV4::Value const&, bool,
QFlags) (this=0x596eefb0, result=...,
isUndefined=, flags=...) at ./src/qml/qml/qqmlbinding.cpp:268
#19 0x764c9972 in
QQmlBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) (this=0x596eefb0,
watcher=..., flags=..., scope=) at
./src/qml/qml/qqmlbinding.cpp:700
#20 0x764c7101 in
QQmlBinding::update(QFlags) (this=0x596eefb0,
flags=...) at ./src/qml/qml/qqmlbinding.cpp:164
#21 0x76447ce3 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) (this=0x59cabd90,
interrupt=...) at ./src/qml/qml/qqmlobjectcreator.cpp:1462
#22 0x764f8c67 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&)
(this=this@entry=0x59282a00, i=...) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qscopedpointer.h:90
#23 0x764f9854 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlRefPointer const&) (this=0x55e47b10, i=, forContext=) at ./src/qml/qml/qqmlincubator.cpp:53
#24 0x764d1f4e in QQmlComponent::create(QQmlIncubator&, QQmlContext*,
QQmlContext*) (this=, incubator=..., context=,
forContext=) at ./src/qml/qml/qqmlcomponent.cpp:1437
#25 0x76d7dfd0 in QQuickLoaderPrivate::_q_sourceLoaded()
(this=0x570ecad0) at ./src/quick/items/qquickloader.cpp:741
#26 0x7fff

[plasmashell] [Bug 484878] Plasma crashes after wakeup from suspend when clicking on the Kickoff launcher

2024-04-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484878

Marco Martin  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |BACKTRACE
 CC||notm...@gmail.com

--- Comment #1 from Marco Martin  ---
Can you reproduce with debug symbols? see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[plasmashell] [Bug 484924] Plasmashell crash on qquickaccessibleattached.cpp

2024-04-02 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=484924

Marco Martin  changed:

   What|Removed |Added

Summary|Plasmashell |Plasmashell crash on
   ||qquickaccessibleattached.cp
   ||p
 CC||notm...@gmail.com

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

[dolphin] [Bug 484773] New: "open folders during drag operations" doesn't work as expected between windows/views on wayland

2024-03-30 Thread Martin Corley
https://bugs.kde.org/show_bug.cgi?id=484773

Bug ID: 484773
   Summary: "open folders during drag operations" doesn't work as
expected between windows/views on wayland
Classification: Applications
   Product: dolphin
   Version: 24.02.1
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: martin.cor...@ed.ac.uk
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

In Wayland: When dragging an item from one view (F3) or window to another, the
folder does not open, even if "View->Open folders during drag operations" has
been selected in dolphin config.  Works as expected in X, and within a view.

STEPS TO REPRODUCE
1.  Select "View->Open folders during drag operations"
2.  Either press F3 (for two views), or open two windows.
3. Drag a file from one view/window over a folder in the other.

OBSERVED RESULT

Folder is highlighted but nothing further happens.

EXPECTED RESULT

After a delay, the folder should open and show its contents.
SOFTWARE/OS VERSIONS

Arch Linux: kernel 6.8.2-zen2-1-zen
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

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

[Discover] [Bug 484650] New: Reboot notification does not disappear when running "pkcon update" manually

2024-03-28 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484650

Bug ID: 484650
   Summary: Reboot notification does not disappear when running
"pkcon update" manually
Classification: Applications
   Product: Discover
   Version: 6.0.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Notifier
  Assignee: plasma-b...@kde.org
  Reporter: martin.tlus...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Ok, this is a weird bug report, but anyway...

SUMMARY
When discover shows that there are updates, and I manually run "pkcon update",
the notification disappears.
But when I actually click "apply all" in discover, it will download the updates
and show me a restart notification. If I then do "pkcon update", the
notification will not disappear, but no updates will be installed on reboot.

STEPS TO REPRODUCE
1. Open discover - updates. Click on "apply all". Wait until the "reboot"
notification appears. Close discover.
2. open konsole and run "pkcon update"
3. Restart

OBSERVED RESULT
Nothing

EXPECTED RESULT
Either the notification should disappear, or updates should be installed

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION
Yes, I know it's a weird and (possibly) stupid thing to do... ;-)

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

[okular] [Bug 484547] Does not show drop down menu in formular

2024-03-27 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=484547

--- Comment #2 from Martin  ---
(In reply to Albert Astals Cid from comment #1)
> Are you clicking on the arrow of the combo box? (right hand side in the
> regular style)

Ah now I see, the button with the arrow for point 5 is just not rendered (See
Attachment).

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

[Akonadi] [Bug 478033] EWS accounts unusable - constantly lose authentication

2024-03-27 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=478033

--- Comment #18 from Martin Tlustos  ---
I can confirm that akonadi ews resource keeps growing in memory usage, although
it's not that big for me - only from 25mb to 87 mb in 6 hours or so...

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

[okular] [Bug 484547] New: Does not show drop down menu in formular

2024-03-26 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=484547

Bug ID: 484547
   Summary: Does not show drop down menu in formular
Classification: Applications
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: martin.marmso...@gmail.com
  Target Milestone: ---

Created attachment 167812
  --> https://bugs.kde.org/attachment.cgi?id=167812=edit
Okular no drop down

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

https://bundeswahlleiterin.de/europawahlen/2024/informationen-waehler/unionsbuerger.html

STEPS TO REPRODUCE
1. Open the following document in okular:
https://bundeswahlleiterin.de/dam/jcr/d975b44c-d57d-439a-b290-7ff6b956ccb4/euwo_anlage-2a_ausfuellbar.pdf
2. Check for point 5 in formulae mode

OBSERVED RESULT
No drop down menu

EXPECTED RESULT
Drop down menu like in firefox

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

ADDITIONAL INFORMATION

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

[kmail2] [Bug 484538] kmail classic theme doesn't show subjects with emoticons

2024-03-26 Thread Martin Bednar
https://bugs.kde.org/show_bug.cgi?id=484538

--- Comment #3 from Martin Bednar  ---
Created attachment 167805
  --> https://bugs.kde.org/attachment.cgi?id=167805=edit
Dolphin screenshot

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

[kmail2] [Bug 484538] kmail classic theme doesn't show subjects with emoticons

2024-03-26 Thread Martin Bednar
https://bugs.kde.org/show_bug.cgi?id=484538

--- Comment #2 from Martin Bednar  ---
Created attachment 167804
  --> https://bugs.kde.org/attachment.cgi?id=167804=edit
Save As dialog, showcasing the issue

So, this is apparently deeper than kmail...
I just realized that while saving the incriminating email, I saw the same issue
in the Save As dialog. And the filename in Dolphin is weirdly stretched out
too.
Sorry kmail, you were the first place I noticed it.

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

[kmail2] [Bug 484538] kmail classic theme doesn't show subjects with emoticons

2024-03-26 Thread Martin Bednar
https://bugs.kde.org/show_bug.cgi?id=484538

--- Comment #1 from Martin Bednar  ---
Created attachment 167803
  --> https://bugs.kde.org/attachment.cgi?id=167803=edit
Screenshot of part of the message list.

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

[kmail2] [Bug 484538] New: kmail classic theme doesn't show subjects with emoticons

2024-03-26 Thread Martin Bednar
https://bugs.kde.org/show_bug.cgi?id=484538

Bug ID: 484538
   Summary: kmail classic theme doesn't show subjects with
emoticons
Classification: Applications
   Product: kmail2
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: martin+...@serafean.cz
  Target Milestone: ---

Created attachment 167802
  --> https://bugs.kde.org/attachment.cgi?id=167802=edit
email to showcase issue. Half spam, recommend not loading remote images.

Kmail doesn't show text in subject lines of messages with emoticons in the
subject.

STEPS TO REPRODUCE
1. Use kmail classic message list theme
2. receive mail with emoticon in subject
3. Observe subject not being displayed


Linux/KDE Plasma: Gentoo
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

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

2024-03-26 Thread Martin Spudich
https://bugs.kde.org/show_bug.cgi?id=483998

--- Comment #3 from Martin Spudich  ---
(In reply to Pedro Boschi from comment #2)
> (In reply to Martin Spudich from comment #1)
> > I have the same issue on OpenSuse TW. It's really annoying.
> > 
> > I'm working with multiple IntelliJ windows, currently on one project:
> > 
> > 1x IntelliJ IDEA
> > 2x GoLand
> > 
> > I found, that if I open only 1x IDEA and 1x GoLand, it is working fine. I
> > have the issue only with 2x GoLand windows. Expecting it will be the same
> > with 2x IDEA windows.
> > 
> > @PedroBoschi did you found any workeround?
> 
> I could not find a way to make the windows behave as they should, so my
> "workaround" is to close the application (IntelliJ's "File" menu -> Exit),
> as they are in the same place for all the IntelliJ windows, and then open
> the application again, so my open projects are restored.
> Yes, annoying

Right now, I found, that I could send one of the IntellJ windows to a different
workspace. And then the "stack" window works again.

I will open IntelliJ windows in different workspaces until this issue is
resolved.

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

2024-03-26 Thread Martin Spudich
https://bugs.kde.org/show_bug.cgi?id=483998

Martin Spudich  changed:

   What|Removed |Added

 CC||martin.spud...@gmail.com

--- Comment #1 from Martin Spudich  ---
I have the same issue on OpenSuse TW. It's really annoying.

I'm working with multiple IntelliJ windows, currently on one project:

1x IntelliJ IDEA
2x GoLand

I found, that if I open only 1x IDEA and 1x GoLand, it is working fine. I have
the issue only with 2x GoLand windows. Expecting it will be the same with 2x
IDEA windows.

@PedroBoschi did you found any workeround?

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

[kmymoney] [Bug 351274] add graphical report for payees

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=351274

--- Comment #7 from Martin Tlustos  ---
And, additionally, if there was a possibility to select/deselect payees on the
right or left side of the report, right in the graphical view, that would make
it easier to check specific people.
Another way would be some way to scroll through the list of payees while
dynamically updating the "transaction by payees" view.

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

[kmymoney] [Bug 351274] add graphical report for payees

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=351274

--- Comment #6 from Martin Tlustos  ---
Well, the easiest way is to just enable a graphical view of the already
available "transactions by payee". That of course would seriously clutter the
chart with too many lines, but one could adjust the filter/sort to show just
the regular donors. Then they would be able to see sudden changes more quickly
than by scrolling through an endless list of transactions.

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

[muon] [Bug 341523] add shortcuts to uninstall (DEL) and purge (SHIFT-DEL) packages

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=341523

Martin Tlustos  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|REPORTED|RESOLVED

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

[muon] [Bug 341523] add shortcuts to uninstall (DEL) and purge (SHIFT-DEL) packages

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=341523

--- Comment #6 from Martin Tlustos  ---
Any replacement in sight?

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

[kmymoney] [Bug 351274] add graphical report for payees

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=351274

--- Comment #4 from Martin Tlustos  ---
It's probably very difficult to do, as a lot of payees will clutter the report.
Anyway, nothing has changed. I'd propose it'd be marked as "won't fix" and
close the report

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

[muon] [Bug 341523] add shortcuts to uninstall (DEL) and purge (SHIFT-DEL) packages

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=341523

--- Comment #4 from Martin Tlustos  ---
Still not working as in Plasma 6.0.1

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

[plasmashell] [Bug 477317] Non-floating Panel with "Fit Content" does not take the correct width on plasmashell start if Digital Clock is present, but resizes to correct width if "Edit Mode" is activa

2024-03-25 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=477317

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi
   |t/c9642b6c862ea9146f10c99b8 |t/6016a816d5788a7a621f9bdae
   |e52b379e954affb |f194979229081f4

--- Comment #37 from Marco Martin  ---
Git commit 6016a816d5788a7a621f9bdaef194979229081f4 by Marco Martin.
Committed on 25/03/2024 at 09:43.
Pushed by mart into branch 'Plasma/6.0'.

Always set a fixed size

when the resize mode is fitcontent, always set a fixed size for the panel
(both setMinimumSize and setMaximumSize as the same size) because this
should be the only place where the panel is resized, and every other attempt
from either anywhere else in Qt or kwin should be denied


(cherry picked from commit c9642b6c862ea9146f10c99b8e52b379e954affb)

c9642b6c Always set a fixed size

M  +1-1shell/panelview.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/6016a816d5788a7a621f9bdaef194979229081f4

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

[plasmashell] [Bug 477317] Non-floating Panel with "Fit Content" does not take the correct width on plasmashell start if Digital Clock is present, but resizes to correct width if "Edit Mode" is activa

2024-03-25 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=477317

Marco Martin  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-desktop/-/commit/ |ma/plasma-workspace/-/commi
   |281e61914f3ebc82df4076d0a40 |t/c9642b6c862ea9146f10c99b8
   |ce91a0ada9ecc   |e52b379e954affb

--- Comment #36 from Marco Martin  ---
Git commit c9642b6c862ea9146f10c99b8e52b379e954affb by Marco Martin.
Committed on 25/03/2024 at 09:38.
Pushed by mart into branch 'master'.

Always set a fixed size

when the resize mode is fitcontent, always set a fixed size for the panel
(both setMinimumSize and setMaximumSize as the same size) because this
should be the only place where the panel is resized, and every other attempt
from either anywhere else in Qt or kwin should be denied

M  +1-1shell/panelview.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/c9642b6c862ea9146f10c99b8e52b379e954affb

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

[systemsettings] [Bug 346505] display extended font info

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=346505

Martin Tlustos  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Tlustos  ---
Very old, and never implemented, so probably intentional.

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

[kmail2] [Bug 252844] Sort names/addresses alphabetically in emails with multiple recipients and in groups (in kaddressbook)

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=252844

Martin Tlustos  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #2 from Martin Tlustos  ---
Seems to work now, closing

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

[plasmashell] [Bug 470410] kmail windows list text in plasma window list with symbols only appears heads-down

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=470410

Martin Tlustos  changed:

   What|Removed |Added

Version|5.27.3  |6.0.1

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

[plasmashell] [Bug 470410] kmail windows list text in plasma window list with symbols only appears heads-down

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=470410

--- Comment #4 from Martin Tlustos  ---
Any updates? It's still the same in Plasma 6.0.1. Also, that bug is assigned to
me (not a developer at all)...

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

[Akonadi] [Bug 484440] New: Can't send email over EWS mailtransport resource

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484440

Bug ID: 484440
   Summary: Can't send email over EWS mailtransport resource
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 6.0.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
CC: c...@carlschwan.eu, kri...@op.pl
  Target Milestone: ---

SUMMARY
I set up an EWS resource that kind of works (with problems, see other bug
reports - i have to re-authenticate again and again). But I cannot send any
emails via EWS-MTA.

STEPS TO REPRODUCE
1. create EWS resource (office365, not live.com)
2. add EWS Mailtransport resource that is linked to the above EWS resource
3. send an email over this EWS mailstransport resource

OBSERVED RESULT
Not sent for several days

EXPECTED RESULT
should be sent immediately

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 483315] Contacts don't show up in kmail (component in kontact)

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=483315

--- Comment #2 from Martin Tlustos  ---
Another observation.
when clicking "Calendar properties", it opens the authentification page. After
re-authenticating, reloading, and re-updating, Things seem to become more
accurate, e.g. tasks and events are updated etc.

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

[digikam] [Bug 406889] ability to search for specific faces

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=406889

--- Comment #8 from Martin Tlustos  ---
I would like to clear up my bug reports a bit. So, is this bug confirmed,
assigned, fixed?

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

[Akonadi] [Bug 482442] After update to plasma 6, akonadi can't start because mysql configuration is missing/faulty

2024-03-25 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=482442

--- Comment #7 from Martin Tlustos  ---
Since an update some time ago, it started working again. If no one is against
it, I would suggest closing this as fixed.

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

[kleopatra] [Bug 484435] New: Icon in notification area does not match other icons

2024-03-24 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484435

Bug ID: 484435
   Summary: Icon in notification area does not match other icons
Classification: Applications
   Product: kleopatra
   Version: 3.1.28.240201
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: aheine...@gnupg.org
  Reporter: martin.tlus...@gmail.com
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

SUMMARY
When starting kleopatra, it's icon appears in the notification area, but it's
colored and not outlined like all the other icons in the notification are
(Breeze dark theme)



SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12
ADDITIONAL INFORMATION

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

[kmail2] [Bug 484434] New: HTML per-user settings are not applied consistently

2024-03-24 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484434

Bug ID: 484434
   Summary: HTML per-user settings are not applied consistently
Classification: Applications
   Product: kmail2
   Version: 6.0.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
I tried to turn of "prefer html" for message viewing and only turn it on for
trusted contacts. It doesn't work. It will hop back and forth from displaying
messages in html or not.



STEPS TO REPRODUCE
1. Set kmail to prefer plain text over html in settings
2. click on a received email, right-click on the contact in the header and
either create or edit the contact to prefer html (and/or load external links to
your liking), close.
3. Click on another email, than on the email you chose first (to reload it).
4. Click on another email from the same contact
5. Close kontact/kmail and akonadi completely, re-open and click on the same
message (or another from the same contact)

OBSERVED RESULT
It should follow my preferences from that specific contact

EXPECTED RESULT
Sometimes it does, sometimes it doesn't

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12
ADDITIONAL INFORMATION

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

[kmail2] [Bug 484433] New: Kmail asks for opengpg password every time I send a signed email

2024-03-24 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484433

Bug ID: 484433
   Summary: Kmail asks for opengpg password every time I send a
signed email
Classification: Applications
   Product: kmail2
   Version: 6.0.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
This probably is by design, but it's bothersome. Once per session would be
enough, or maybe even save it somewhere. Or add integration for a password
manager where the password is saved.


STEPS TO REPRODUCE
1. Enable crypto with a openpgp key that is password-protected
2. write an email and sign it.
3. click send

OBSERVED RESULT
kmail asks for the openpgp password

EXPECTED RESULT
It shouldn't.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION

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

[kontact] [Bug 484432] New: Opening Settings takes too long

2024-03-24 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484432

Bug ID: 484432
   Summary: Opening Settings takes too long
Classification: Applications
   Product: kontact
   Version: 6.0.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: martin.tlus...@gmail.com
  Target Milestone: ---

SUMMARY
It takes a long time to open kontact settings, about ten seconds or so. This
only happens the first time you open them, other times it goes much quicker.


STEPS TO REPRODUCE
1. Click "Settings - Configure Kontact"

OBSERVED RESULT
It takes a long time to open

EXPECTED RESULT
Should open (almost) immediately

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION
Updated from Plasma 5

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

[systemsettings] [Bug 484092] [KCM_Powerdevil] When using the mouse wheel to change the value of time, the value changes from minutes to seconds, or from seconds to minutes

2024-03-20 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=484092

Martin  changed:

   What|Removed |Added

Summary|When using the mouse wheel  |[KCM_Powerdevil] When using
   |to change the value of  |the mouse wheel to change
   |time, the value changes |the value of time, the
   |from minutes to seconds, or |value changes from minutes
   |from seconds to minutes |to seconds, or from seconds
   ||to minutes

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

[systemsettings] [Bug 484092] New: When using the mouse wheel to change the value of time, the value changes from minutes to seconds, or from seconds to minutes

2024-03-20 Thread Martin
https://bugs.kde.org/show_bug.cgi?id=484092

Bug ID: 484092
   Summary: When using the mouse wheel to change the value of
time, the value changes from minutes to seconds, or
from seconds to minutes
Classification: Applications
   Product: systemsettings
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_powerdevil
  Assignee: plasma-b...@kde.org
  Reporter: emtorr...@gmail.com
CC: k...@privat.broulik.de, natalie_clar...@yahoo.de
  Target Milestone: ---

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

SUMMARY
When using the mouse wheel to change the value of time, the value changes from
minutes to seconds, or from seconds to minutes and becomes confusing


STEPS TO REPRODUCE
1. Enter en power settings
2. Use mouse wheel to change value of time for suspend 
3. (Attached video for more details)

OBSERVED RESULT
- the value changes from minutes to seconds, or from seconds to minutes

EXPECTED RESULT
- If the value is greater than 59 seconds, convert to minutes and vice versa.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240318
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-1-default (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Vega 8 Graphics

ADDITIONAL INFORMATION

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

[kwin] [Bug 470759] Crash in KWin::CustomTile::setRelativeGeometry using custom script

2024-03-20 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=470759

--- Comment #3 from Marco Martin  ---
not sure if it's relevant, but does this happen with x11 or wayland?

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

[libkgapi] [Bug 484041] Changes don't get synced with google

2024-03-20 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484041

--- Comment #1 from Martin Tlustos  ---
Configuring and re-authorizing akonadi google services doesn't help either.

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

[libkgapi] [Bug 484041] Changes don't get synced with google

2024-03-20 Thread Martin Tlustos
https://bugs.kde.org/show_bug.cgi?id=484041

Martin Tlustos  changed:

   What|Removed |Added

  Component|general |calendar
Product|korganizer  |libkgapi
 CC||kdepim-b...@kde.org
   Assignee|kdepim-b...@kde.org |dvra...@kde.org

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

<    1   2   3   4   5   6   7   8   9   10   >