date:20230324

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

--- Comment #30 from Maik Qualmann  ---
Note: With the Geolocation Editor you can remove zero altitudes that have
arisen or fill in the altitude automatically via the web service.

Maik

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

[digikam] [Bug 467090] Maps Window with Google Maps only empty

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||8.0.0
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #12 from Maik Qualmann  ---
At the moment QWebKit works again with Google Maps without us changing
anything.

Maik

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

[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/digikam/commit/40e0023 |hics/digikam/commit/0a08ca0
   |d0c2695f9399d2e939dd41a8925 |cd21eadf238a12a453b936a5292
   |3933ff  |fd9f71
 Resolution|--- |FIXED

--- Comment #29 from Maik Qualmann  ---
Git commit 0a08ca0cd21eadf238a12a453b936a5292fd9f71 by Maik Qualmann.
Committed on 25/03/2023 at 05:16.
Pushed by mqualmann into branch 'master'.

check if altitude is present when writing metadata
DIXED-IN: 8.0.0

M  +3-1core/libs/fileactionmanager/metadatahub.cpp

https://invent.kde.org/graphics/digikam/commit/0a08ca0cd21eadf238a12a453b936a5292fd9f71

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

[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking

2023-03-24 Thread zellox

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

zellox  changed:

   What|Removed |Added

 CC||zel...@fastmail.com

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

[kate] [Bug 467768] Kate crashes Wayland completely upon launch

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kate] [Bug 467768] New: Kate crashes Wayland completely upon launch

2023-03-24 Thread spittingverse

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

Bug ID: 467768
   Summary: Kate crashes Wayland completely upon launch
Classification: Applications
   Product: kate
   Version: 22.12.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: spittingve...@gmail.com
  Target Milestone: ---

Created attachment 157559
  --> https://bugs.kde.org/attachment.cgi?id=157559&action=edit
gdp output

SUMMARY
Kate crashes Wayland. It does not happen every time. I tried this 10 times, and
Wayland froze 7 of those times. This happened only today and has never occurred
before. This issue is reproducible even after multiple reboots.

STEPS TO REPRODUCE
1. Login to KDE plasma Wayland.
2. Launch Kate from either command line or application menu 
3. Applications cannot be recovered and the only thing to do other than a
restart is to switch to a tty and kill kwin_wayland

OBSERVED RESULT
Kate freezes Kwin Wayland completely and permanently. As in, I cannot move my
mouse and there is no response to any keyboard input other than switching to
other ttys.

EXPECTED RESULT
Kate should launch and function normally. Even if it crashes, it should not
take down all my processes with it.

Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550M DS3H AC
System Version: -CF

ADDITIONAL INFORMATION
Attached is the output of sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set
logging file kwin_wayland.gdb" -ex "set logging on" -ex "set print
thread-events off" -ex  "thread apply all backtrace" -ex "quit"

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

[kate] [Bug 465852] Kwrite 22.12.2: Saving a new document with key combo has a chance of opening infinite file pickers

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

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

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

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

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[krita] [Bug 467146] Some of Krita Layer and Brush Effect are not working properly Like Lumminosity, Multiply, Linear Bun, and some other

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

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

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

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

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

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

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

[KScreen] [Bug 466885] Extend screen keeps secondary screen powered on and enabled even when lid closed

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

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

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

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

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

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

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

[KScreen] [Bug 466484] Lost 3rd monitor with Plasma 5.27.1

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

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

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

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

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

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

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

[Discover] [Bug 466047] With Octicons font, Text, Icons, Install/Remove buttons projecting out of their app's card boxes in Home tab and search results

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

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

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

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

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

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

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

[kmymoney] [Bug 465698] Better handling of transaction type naming in imports

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

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

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

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

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

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

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

[kdenlive] [Bug 363107] frame extract is not making a file.

2023-03-24 Thread David Knierim

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

David Knierim  changed:

   What|Removed |Added

 OS|Linux   |Microsoft Windows
Version|16.04.0 |22.12.3
 Status|RESOLVED|REOPENED
   Platform|Ubuntu  |Microsoft Windows
 Resolution|DOWNSTREAM  |---
 CC||dave...@yahoo.com
 Ever confirmed|0   |1

--- Comment #5 from David Knierim  ---
This bug behaves exactly as described initially.  I'm using 2022.12.3 on
Windows 10 professional 64-bit.  Frame extraction menu behaves exactly as
expected, but no file created.  (Checked selected directory.  Also, Windows
file search does not find any file by the selected name in any folder.)
Found this on 2022.08.3, updated hoping it had been fixed, but no change in
behavior.

BTW, thank you all for this tool.  I'm only an occasional user, but it is great
for my Tesla coil etc. videos.

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

[plasmashell] [Bug 467709] [Wayland] Hovering over task icons with disabled previews still spikes up wireplumber cpu usage

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

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

[Falkon] [Bug 466936] Make dates in History sidebar and dialog unselectable upon filtering

2023-03-24 Thread Juraj

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

Juraj  changed:

   What|Removed |Added

 CC||jurajora...@mailo.com

--- Comment #3 from Juraj  ---
Hello,

the "fix" is more like a workaround and just makes it so, that the items will
not be deleted.
I know there is a way to properly manage what items are selected but I am not
skilled at using that.

Best regards,
Juraj.

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

[Falkon] [Bug 466936] Make dates in History sidebar and dialog unselectable upon filtering

2023-03-24 Thread Juraj

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

Juraj  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
   |ork/falkon/commit/74cfccd69 |ork/falkon/commit/85f999010
   |d7249f6380120e9a8c46c1566e0 |4f5d59458bfdf4693cf6a3b2901
   |f7b6|6f22

--- Comment #2 from Juraj  ---
Git commit 85f9990104f5d59458bfdf4693cf6a3b29016f22 by Juraj Oravec.
Committed on 25/03/2023 at 02:11.
Pushed by jurajo into branch 'master'.

History: Don't delete all items under dates when filtering
FIXED-IN: 23.04.0

Signed-off-by: Juraj Oravec 

M  +5-0src/lib/history/historymodel.cpp
M  +1-0src/lib/history/historymodel.h
M  +1-1src/lib/history/historytreeview.cpp

https://invent.kde.org/network/falkon/commit/85f9990104f5d59458bfdf4693cf6a3b29016f22

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

[Falkon] [Bug 466936] Make dates in History sidebar and dialog unselectable upon filtering

2023-03-24 Thread Juraj

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

Juraj  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/netw
   ||ork/falkon/commit/74cfccd69
   ||d7249f6380120e9a8c46c1566e0
   ||f7b6
   Version Fixed In||23.04.0

--- Comment #1 from Juraj  ---
Git commit 74cfccd69d7249f6380120e9a8c46c1566e0f7b6 by Juraj Oravec.
Committed on 25/03/2023 at 02:15.
Pushed by jurajo into branch 'release/23.04'.

History: Don't delete all items under dates when filtering
FIXED-IN: 23.04.0

Signed-off-by: Juraj Oravec 

M  +5-0src/lib/history/historymodel.cpp
M  +1-0src/lib/history/historymodel.h
M  +1-1src/lib/history/historytreeview.cpp

https://invent.kde.org/network/falkon/commit/74cfccd69d7249f6380120e9a8c46c1566e0f7b6

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

[digikam] [Bug 467766] QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Images` F

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

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

   What|Removed |Added

  Component|Database-Engine |Database-Mysql
   Platform|Other   |Mint (Ubuntu based)
 CC||caulier.gil...@gmail.com

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

[kwin] [Bug 454668] Alt+Shift+Tab doesn't reverse task switcher

2023-03-24 Thread donquixote

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

--- Comment #10 from donquixote  ---
> I can reassign to Alt+^ which on my keyboard layout is right above Tab.

I should add:
If I add both Alt+^ and Alt+Shift-Tab, then even Alt+^ has the same problem as
Alt+Shift+Tab.
If I only assign Alt+^, it works fine.

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

[kwin] [Bug 454668] Alt+Shift+Tab doesn't reverse task switcher

2023-03-24 Thread donquixote

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

--- Comment #9 from donquixote  ---
> This happens to me since I switched from X11 to wayland.

I should add, I can switch back to X11 and have the problem disappear.
But I would like to use wayland :)

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

[kwin] [Bug 454668] Alt+Shift+Tab doesn't reverse task switcher

2023-03-24 Thread donquixote

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

donquixote  changed:

   What|Removed |Added

 CC||py7sm...@anonaddy.me

--- Comment #8 from donquixote  ---
This happens to me since I switched from X11 to wayland.

A single Alt+Shift+Tab works, it goes one tab backwards and reveals the tab
switcher as long as Alt is down.
However, when I repeatedly hit Tab while Alt+Shift is down, it has no effect.
Going forward works, with repeated Alt+Tab, while holding Alt down.

The same happens for Meta+Shift+Tab.

I can reassign to Alt+^ which on my keyboard layout is right above Tab.
But I would prefer not having to learn another shortcut..

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

[kscreenlocker] [Bug 456210] Under certain circumstances when using multiple monitors, "unlock" button is clickable but does nothing

2023-03-24 Thread sparkie

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

sparkie  changed:

   What|Removed |Added

 CC||lg_ninj...@yahoo.com

--- Comment #73 from sparkie  ---
I'm having this issue as well. I can enter my password, then it goes to a
screen with an "Unlock" button, but clicking the button does nothing. I'm on
Wayland, plasma 5.27.3, Fedora 37, Qt 5.15.8, and I have three identical
monitors connected to an AMD 6700XT GPU. Two via displayport-->hdmi adapters
and one normal HDMI.

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

[KScreen] [Bug 466674] Wayland: various apps crash in DpmsManager::addScreen() when display enters sleep

2023-03-24 Thread Mau

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

Mau  changed:

   What|Removed |Added

 CC||mav...@gmail.com

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

[Discover] [Bug 465071] Content rating: text is cut off when it's too big

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

guimarcalsi...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from guimarcalsi...@gmail.com ---


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

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

[Discover] [Bug 466815] Broken "Content Rating" layout

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

guimarcalsi...@gmail.com changed:

   What|Removed |Added

 CC||guimarcalsi...@gmail.com

--- Comment #4 from guimarcalsi...@gmail.com ---
*** Bug 465071 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 467767] [nvidia, wayland] Messing with night light freezes the screen

2023-03-24 Thread Arsen Arsenović

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

--- Comment #2 from Arsen Arsenović  ---
Oh, sorry - I missed one more observation: the key only freezes for the
duration of the transitional period (which might be quite long if you're
currently in magic hour), so if you toggle from Always On to Always Off or vice
versa, you get a brief freeze of a few seconds with the usual...

Mar 25 00:32:25 bstg kwin_wayland[275491]: kwin_wayland_drm: Failed to create
gamma blob! Invalid argument
Mar 25 00:32:25 bstg kwin_wayland[275491]: kwin_wayland_drm: Failed to create
gamma blob! Invalid argument

... spam in logs.

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

[plasmashell] [Bug 467767] [nvidia, wayland] Messing with night light freezes the screen

2023-03-24 Thread Arsen Arsenović

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

--- Comment #1 from Arsen Arsenović  ---
OK, I've tested without the patch - the problem seems to not be introduced by
it.

Though, it has come to my attention that my original reproduction steps are
incomplete!  Here are the new ones:

1. Lock the desktop,
2. Let it go into inactivity and turn off the screen,
3. Unlock the desktop,
4. Open Night Color settings,
5. Toggle it's active state (i.e. go from always on/on at set times -> always
off or vice versa),
6. Hit apply

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

[frameworks-kio] [Bug 466359] since upgrade to KDE Framework 5.103, kstart5 does not return after starting application

2023-03-24 Thread Nicolas Fella

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

Nicolas Fella  changed:

   What|Removed |Added

   Version Fixed In||5.105

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

[frameworks-kio] [Bug 466359] since upgrade to KDE Framework 5.103, kstart5 does not return after starting application

2023-03-24 Thread Nicolas Fella

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

Nicolas Fella  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram
   |eworks/kio/commit/fea052ba3 |eworks/kio/commit/01481fb95
   |69e474a092516a4717556b52ff9 |ec443988dfbf51116d807359c08
   |2e00|dfab

--- Comment #7 from Nicolas Fella  ---
Git commit 01481fb95ec443988dfbf51116d807359c08dfab by Nicolas Fella, on behalf
of Thenujan Sandramohan.
Committed on 24/03/2023 at 22:38.
Pushed by nicolasfella into branch 'master'.

CommandLauncher: call emitResult() as soon as process has started

This MR makes `emitResult` get called as soon as the process has started
instead of when the process has ended. It also changes `emitDelayedError` as a
protected member of `KProcessRunner` to make it invokable by
`ForkingProcessRunner`. It also removes `processFinished` signal as it's not
used anymore.

M  +0-2src/gui/commandlauncherjob.cpp
M  +1-2src/gui/kprocessrunner.cpp
M  +1-6src/gui/kprocessrunner_p.h

https://invent.kde.org/frameworks/kio/commit/01481fb95ec443988dfbf51116d807359c08dfab

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

[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)

2023-03-24 Thread Galen Adams

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

--- Comment #28 from Galen Adams  ---
Maybe my explanation was unclear - like before, the affected images do have
Altitude and not Altitude Reference.

When I do Write Metadata to Selected Files, it still changes Altitude to
Zero(0) and now it also fills in the Altitude Reference with Above Sea
Level (which would be fine if it didn't change the Altitude)

I will send more image files soon.

On Fri, Mar 24, 2023 at 5:45 PM Maik Qualmann 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=467623
>
> --- Comment #27 from Maik Qualmann  ---
> I can't reproduce the problem. Note that XMP-GPS metadata takes precedence
> over
> Exif because of sidecars. Your sample images also have GPS metadata in XMP.
> Otherwise send me a sample image that should not have any altitude
> information
> and with which the problem occurs.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)

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

--- Comment #27 from Maik Qualmann  ---
I can't reproduce the problem. Note that XMP-GPS metadata takes precedence over
Exif because of sidecars. Your sample images also have GPS metadata in XMP.
Otherwise send me a sample image that should not have any altitude information
and with which the problem occurs.

Maik

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

[digikam] [Bug 467766] QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Images` F

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

--- Comment #5 from Petr Schonmann  ---
No, ive mysql db from begins.

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

[digikam] [Bug 467766] QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Images` F

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

--- Comment #4 from Maik Qualmann  ---
mysqlcheck cannot detect such an error. An attempt is made to use an imageid
with 0 (QVariant(qlonglong, 0)), this can never happen in the worst case. Have
you performed a migration from SQLite to MySQL?

Maik

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

[frameworks-kio] [Bug 466359] since upgrade to KDE Framework 5.103, kstart5 does not return after starting application

2023-03-24 Thread Nicolas Fella

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

Nicolas Fella  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kio/commit/fea052ba3
   ||69e474a092516a4717556b52ff9
   ||2e00
 Resolution|--- |FIXED

--- Comment #6 from Nicolas Fella  ---
Git commit fea052ba369e474a092516a4717556b52ff92e00 by Nicolas Fella, on behalf
of Thenujan Sandramohan.
Committed on 24/03/2023 at 22:33.
Pushed by nicolasfella into branch 'kf5'.

CommandLauncher: call emitResult() as soon as process has started

This MR makes `emitResult` get called as soon as the process has started
instead of when the process has ended. It also changes `emitDelayedError` as a
protected member of `KProcessRunner` to make it invokable by
`ForkingProcessRunner`. It also removes `processFinished` signal as it's not
used anymore.

M  +0-2src/gui/commandlauncherjob.cpp
M  +1-2src/gui/kprocessrunner.cpp
M  +1-6src/gui/kprocessrunner_p.h

https://invent.kde.org/frameworks/kio/commit/fea052ba369e474a092516a4717556b52ff92e00

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

[konversation] [Bug 466040] Konversation dumps core on exit

2023-03-24 Thread Yannick

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

--- Comment #2 from Yannick  ---
It looks like it's no longer happening.
Maybe the Frameworks 5.104.0 or Plasma 5.27.3 update somehow fixed the issue.

@Enrico: Do you still encounter the issue on Debian?

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

[digikam] [Bug 467766] QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Images` F

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

--- Comment #3 from Petr Schonmann  ---
Created attachment 157557
  --> https://bugs.kde.org/attachment.cgi?id=157557&action=edit
error log

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

[digikam] [Bug 467766] QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Images` F

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

--- Comment #2 from Petr Schonmann  ---
Nope, DB seems to be fine.

--
root@nas:/usr/local/mariadb10/bin# ./mysqlcheck -A
digikam.AlbumRoots OK
digikam.Albums OK
digikam.CustomIdentifiers  OK
digikam.DownloadHistoryOK
digikam.FaceMatrices   OK
digikam.FaceSettings   OK
digikam.FilePaths  OK
digikam.Identities OK
digikam.IdentityAttributes OK
digikam.ImageComments  OK
digikam.ImageCopyright OK
digikam.ImageHaarMatrixOK
digikam.ImageHistory   OK
digikam.ImageInformation   OK
digikam.ImageMetadata  OK
digikam.ImagePositions OK
digikam.ImagePropertiesOK
digikam.ImageRelations OK
digikam.ImageSimilarityOK
digikam.ImageTagProperties OK
digikam.ImageTags  OK
digikam.Images OK
digikam.KDTree OK
digikam.Searches   OK
digikam.Settings   OK
digikam.SimilaritySettings OK
digikam.TagProperties  OK
digikam.Tags   OK
digikam.TagsTree   OK
digikam.ThumbSettings  OK
digikam.Thumbnails OK
digikam.UniqueHashes   OK
digikam.VideoMetadata  OK

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

[digikam] [Bug 467766] QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Images` F

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This is nothing we can fix, the error says the imageid does not exist in images
to be written/updated in ImageTagProperties. Broken database?

Maik

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

[plasmashell] [Bug 467767] New: [nvidia,wayland] Messing with night light freezes the screen

2023-03-24 Thread Arsen Arsenović

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

Bug ID: 467767
   Summary: [nvidia,wayland] Messing with night light freezes the
screen
Classification: Plasma
   Product: plasmashell
   Version: 5.27.3
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Night Color
  Assignee: plasma-b...@kde.org
  Reporter: ar...@aarsen.me
  Target Milestone: 1.0

SUMMARY
I've first noticed something is awry a few days ago, when Plasma stopped being
able to re-enable the screen after turning it off via DPMS (saying
'kwin_wayland_drm: Setting dpms mode failed!' - I am decently sure this is a
known issue).
This seemed to have gone away after a bit (and an update), but some of the
problem remains - namely, if I left the screen off when going outside around
noon, despite screens being able to wake up before that,  when I returned, I'd
found that the screens are unable to reenable with the same log being printed.
Shortly after, I had backported kwin!3868 as it seemed related (the jury is
still out on whether this helps in the "screen is off" case), and the thread
referenced in that PR piqued my interest with regards to the Night Color.
As a result, I toggled night color in the settings, to find that my screen
frozen (but enabled).

I will remove the patch and re-test momentarily (apologies for the delay).

Running 'qdbus org.kde.NightColor /ColorCorrect
org.kde.kwin.ColorCorrect.inhibit' recovers the screen.

STEPS TO REPRODUCE
1. Open Night Color settings,
2. Toggle it's active state (i.e. go from always on/on at set times -> always
off or vice versa),
3. Hit apply

OBSERVED RESULT
Screen freezes.

EXPECTED RESULT
Screen does nothing (since I don't think this feature works on Nvidia devices
at all, if it does, then the expected result is an oranger screen :-).

SOFTWARE/OS VERSIONS
Operating System: Gentoo GNU/Linux 2.13
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.13-gentoo-dist-hardened (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B550M DS3H

ADDITIONAL INFORMATION
The build I'm currently running has
https://invent.kde.org/plasma/kwin/-/merge_requests/3868 backported into it.
As I have a feeling Nvidia is probably integral here, I currently have
x11-drivers/nvidia-drivers-525.89.02 installed.

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

[digikam] [Bug 467623] I do "Item > Write Metadata to File" = Erases the Altitude field and leaves Altitude at Zero(0)

2023-03-24 Thread Galen Adams

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

Galen Adams  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #26 from Galen Adams  ---
I have tested the fix = this is what is happening now when Write Metadata to
Selected Files:

When I choose a file(s) that lacks the Altitude reference, it changes the
Altitude to Zero(0) and adds the reference Above Sea Level.

Thanks

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

[kdiff3] [Bug 442618] KDiff3 crashes on a git merge conflict with "Severe Internal Error line != i for srcSelector= 1"

2023-03-24 Thread michael

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

--- Comment #7 from michael  ---
The current stable branch is 1.10.x this appears fixed there and in master
however I have no recollection of the exact  commit. Awaiting confirmation.

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

[digikam] [Bug 467766] New: QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT `ImageTagProperties_Imag

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

Bug ID: 467766
   Summary: QMYSQL3: Unable to execute statement" "Cannot add or
update a child row: a foreign key constraint fails
(`digikam`.`ImageTagProperties`, CONSTRAINT
`ImageTagProperties_Images` FOREIGN KEY (`imageid`)
REFERENCES `Images` (`id`) ON DELETE CASCADE ON UPDATE
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Database-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: pschonm...@gmail.com
  Target Milestone: ---

SUMMARY
***
Ive got error in UPDATE/DELETE to DB when tagging people.
QMYSQL3: Unable to execute statement" "Cannot add or update a child row: a
foreign key constraint fails (`digikam`.`ImageTagProperties`, CONSTRAINT
`ImageTagProperties_Images` FOREIGN KEY (`imageid`) REFERENCES `Images` (`id`)
ON DELETE CASCADE ON UPDATE CASCADE)" "1452" 2
***


STEPS TO REPRODUCE
1. Go to people
2. Choose some person. Look at unconfirmed section. When you see somebody thats
not belong face to this selected person write name into small input field to
tag face to right person
3. In debuglog see some complaints about INSERT/DELETE
4. But person has right tags in picture

EXPECTED RESULT

Logs without complaints about failure :)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Mint 21.1
(available in About System)

KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
MySQL is on Synology, some MariaDB 10.x - probably latest mariadb package from
synology

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

[frameworks-kiconthemes] [Bug 448248] Cannot change Qbittorrent Tray icon anymore

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

--- Comment #11 from Martino Fontana  ---
Still an issue.

qBittorrent: 4.5.2
Operating System: NixOS 23.05
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.3-xanmod1 (64-bit)
Graphics Platform: Wayland

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

[plasmashell] [Bug 467765] Application Launcher search, highlighted item may not be the first

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

--- Comment #1 from Martino Fontana  ---
*** Bug 467764 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 467764] Application Launcher search, highlighted item may not be the first

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

Martino Fontana  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martino Fontana  ---
Sorry, accidentally reported twice.

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

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

[kdenlive] [Bug 467763] Kdenlive crashes when switching to projects in a certain order

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[systemsettings] [Bug 440353] Firefox maximized icon missing

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

--- Comment #5 from Martino Fontana  ---
Still an issue. (I'll repeat that it doesn't happen on Breeze Light, it happens
on Breeze Dark.)

Firefox: 111.0.1
Operating System: NixOS 23.05
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.3-xanmod1 (64-bit)
Graphics Platform: Wayland

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

[Powerdevil] [Bug 423035] Turn off screen shortcut turns the screen back on automatically

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

--- Comment #13 from Martino Fontana  ---
The issue is kinda solved on Wayland: because there the screen fades off slowly
(instead of instantly), the user has plenty of time to release the buttons used
for the shortcut (but if they hold them long enough, then the screen will turn
back on).

(On X11, about `xset dpms force off`, because the terminal takes a little time
to process the instruction, you can have the screen stay off if you release
Enter fast enough)

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

[plasmashell] [Bug 467765] New: Application Launcher search, highlighted item may not be the first

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

Bug ID: 467765
   Summary: Application Launcher search, highlighted item may not
be the first
Classification: Plasma
   Product: plasmashell
   Version: 5.27.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: tinozzo...@tutanota.com
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
When you open the Application Launcher and type with the keyboard to search for
something, you expect the first item in the list to be highlighted, so that you
can press Enter to get what you are looking for.
However, under certain conditions (see below), the highlighted item will not be
the first, even if you didn't move the mouse, which will make you open the
wrong app.

STEPS TO REPRODUCE
1. Open the Application Launcher
2. Type on the keyboard to search for something
3. Move the cursor to an item that isn't the first
4. Press the hotkey to close the Application Launcher
5. Open the Application Launcher again, and type with the keyboard again

OBSERVED RESULT
What happens depends on where the cursor is right now:
- If you moved the cursor is out of the way, then the Nth item will be
highlighted, where N depends on which item was highlighted when you closed the
Application Launcher before.
- If the cursor is in the launcher, then it will select the item over which it
hovers, even if you haven't moved it.

(This doesn't always happen, it's a bit inconsistent. It seems to happen more
often when there is no application open on the virtual desktop, and when the
Application Launcher is opened (the first time) by clicking on it, instead of
using a hotkey).

EXPECTED RESULT
If you don't move the cursor, the highlighted item is always the first on the
list.

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

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

[plasmashell] [Bug 467764] New: Application Launcher search, highlighted item may not be the first

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

Bug ID: 467764
   Summary: Application Launcher search, highlighted item may not
be the first
Classification: Plasma
   Product: plasmashell
   Version: 5.27.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: tinozzo...@tutanota.com
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
When you open the Application Launcher and type with the keyboard to search for
something, you expect the first item in the list to be highlighted, so that you
can press enter to get what you searched for.
However, in specific conditions (see below), the highlighted item will be
different even if you don't move the mouse: if the user has the habit of
opening the app by pressing Enter, that will make them open an app they didn't
intend to open.


STEPS TO REPRODUCE
1. Open the Application Launcher
2. Type with the keyboard to search for something
3. Hover the cursor to an item that isn't the first
4. Leaving the cursor on this position, press the hotkey to close the
Application Launcher
5. Open the Application Launcher again, and type with the keyboard again

OBSERVED RESULT
What happens depends on where the cursor is right now:
- If you moved the cursor is out of the way, then the Nth item will be
highlighted, with N depending on which item was highlighted when you closed the
application launcher before.
- If the cursor is in the launcher, then it will highlight the item it's
hovering, even if you didn't move it.

(It doesn't always happen, it's a bit inconsistent. It seems it happens more
likely without any open application on the virtual desktop, and if the
Application Launcher is opened (the first time) by clicking on it, instead of
using a hotkey)

EXPECTED RESULT
If you don't move the cursor, the highlighted item is always the first on the
list.

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

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

[plasma-pa] [Bug 450471] Audio output not changed to HDMI automatically when plugin to TV

2023-03-24 Thread Włodzimierz Ciesielski

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

Włodzimierz Ciesielski  changed:

   What|Removed |Added

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

--- Comment #2 from Włodzimierz Ciesielski  
---
(In reply to Kangarooo from comment #1)
> Is it fixed?
Currently on Ubuntu 22.10 it works correctly
> Can you try again?
Done
> Does connecting monitors and then running this in terminal fixes anything?
> xrandr -q
Its more pulseaudio issue than screen as I see

A lot of time elapsed. Lets close it and if it will reproduced I'll reopen this
issue with additional information

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

[kdenlive] [Bug 467763] New: Kdenlive crashes when switching to projects in a certain order

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

Bug ID: 467763
   Summary: Kdenlive crashes when switching to projects in a
certain order
Classification: Applications
   Product: kdenlive
   Version: 22.12.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: fritz.seiff...@protonmail.com
  Target Milestone: ---

Application: kdenlive (21.12.3)

Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.14.21-150400.24.49-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.4"
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I attempted to switch projects from one that I currently had open (dubbed
"Project A") to another one (dubbed "Project B"). There was only one opened
instance of Kdenlive. It appeared as if Project B loaded successfully (the
loading bar filled to 100% and the small loading sub-window disappeared, the
clips and the timeline assembled etc), but about 1-2 seconds after this
Kdenlive crashed.

I did the same thing twice again (first Project A, then Project B) and Kdenlive
crashed in both instances. I tried the inverse, first switching to Project B
(from an empty instance) and then switching to Project A, this worked fine and
Kdenlive did not crash. I then proceeded to switching to Project B again, at
which point Kdenlive crashed just as it had before. This last step (B->A->B) I
repeated, with the same result.

Whenever I write "switch" what I mean is going to "File" -> "Recent Projects"
and then selecting the project in question.

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault

[KCrash Handler]
#4  0x7f66f3b400d0 in pthread_mutex_lock () at /lib64/libpthread.so.0
#5  0x7f66fc85d86e in mlt_properties_dec_ref
(self=self@entry=0x559b49698380) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_properties.c:401
#6  0x7f66fc85ae33 in mlt_producer_close (self=0x559b49698380) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_producer.c:1089
#7  0x7f66fc863128 in clear_property (self=self@entry=0x559b490df9b0) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_property.c:115
#8  0x7f66fc864a69 in mlt_property_close (self=0x559b490df9b0) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_property.c:917
#9  0x7f66fc85d929 in mlt_properties_close (self=0x559b460e7d30) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_properties.c:1523
#10 0x7f66fc85ae74 in mlt_producer_close (self=0x559b460e7d30) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_producer.c:
#11 0x7f66fc852825 in mlt_frame_close (self=0x559b47b9c8d0) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_frame.c:766
#12 0x7f66fc863128 in clear_property (self=self@entry=0x559b48c00e80) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_property.c:115
#13 0x7f66fc864a69 in mlt_property_close (self=0x559b48c00e80) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_property.c:917
#14 0x7f66fc85d929 in mlt_properties_close (self=self@entry=0x559b458df390)
at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_properties.c:1523
#15 0x7f66fc852844 in mlt_frame_close (self=0x559b458df390) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_frame.c:768
#16 0x7f66fc863128 in clear_property (self=self@entry=0x559b458e7ed0) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_property.c:115
#17 0x7f66fc864a69 in mlt_property_close (self=0x559b458e7ed0) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_property.c:917
#18 0x7f66fc85d929 in mlt_properties_close (self=self@entry=0x559b4706aad0)
at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_properties.c:1523
#19 0x7f66fc852844 in mlt_frame_close (self=0x559b4706aad0) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/framework/mlt_frame.c:768
#20 0x7f66fc62af4b in Mlt::Frame::~Frame() (this=0x559b48eef5c8,
__in_chrg=) at
/usr/src/debug/libmlt-7.4.0-bp154.1.60.x86_64/src/mlt++/MltFrame.cpp:54
#21 0x559b3fb9003e in FrameData::~FrameData() (this=,
__in_chrg=) at
/usr/src/debug/kdenlive-21.12.3-bp154.1.38.x86_64/src/monitor/scopes/sharedframe.cpp:26
#22
QExplicitlySharedDataPointer::operator=(QExplicitlySharedDataPointer
const&) (o=..., this=0x559b43de5078, this@entry=0x559b48eef798) at
/usr/include/qt5/QtCore/qshareddata.h:208
#23 SharedFrame::operator=(SharedFrame const&) (this=this@entry=0x559b43de5078,
other=...) at
/usr/src/debug/kdenlive-21.12.3-bp154.1.38.x86_64/src/monitor/scopes/sharedframe.h:35
#24 0x5

[plasmashell] [Bug 435774] Ability to configure notifications for all events with apps that don't support per-event settings

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

guy...@pm.me changed:

   What|Removed |Added

 CC||guy...@pm.me

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

[kdenlive] [Bug 467762] New: Parts of the UI like the Clip Monitor on startup are glitched with Wayland

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

Bug ID: 467762
   Summary: Parts of the UI like the Clip Monitor on startup are
glitched with Wayland
Classification: Applications
   Product: kdenlive
   Version: 22.12.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: iodream...@gmail.com
  Target Milestone: ---

Created attachment 157556
  --> https://bugs.kde.org/attachment.cgi?id=157556&action=edit
video

SUMMARY
When you start Kdenlive with no project or materials open, parts of the Clip
Monitor and other uis are white and glitch out when the window is moved with
Wayland.

STEPS TO REPRODUCE
1. Open Kdenlive with Wayland
2. Move the window around

OBSERVED RESULT
Clip Monitor ui is glitching

EXPECTED RESULT
Clip Monitor ui is grey like on x11 and does not glitch

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: Mesa Intel® HD Graphics 3000

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

[kamoso] [Bug 467761] New: Support changing the codec (or default to the one supporting the highest resolution?)

2023-03-24 Thread Prajna Sariputra

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

Bug ID: 467761
   Summary: Support changing the codec (or default to the one
supporting the highest resolution?)
Classification: Applications
   Product: kamoso
   Version: 22.12.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: putr...@gmail.com
  Target Milestone: ---

SUMMARY
My webcam (Quanta Computer, Inc. HP Wide Vision HD Camera) only supports its
720p resolution if the MJPEG codec is used, otherwise the raw format is used it
is limited to 640x480. So, Kamoso ends up using 640x480 (or 640x360 if
gst-plugin-libcamera is installed).

For reference Cheese (the GNOME webcam app) does use 1280x720 resolution.


STEPS TO REPRODUCE
1. Have a webcam that only supports MJPEG for its native resolution
2. Open Kamoso
3. Take a photo

OBSERVED RESULT
The photo Kamoso captured is at a lower resolution than native, with no option
to change it.

EXPECTED RESULT
Kamoso should either default to the highest resolution possible or offer
options to select the native resolution.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 14.9 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: HP
Product Name: OMEN by HP Gaming Laptop 16-n0xxx

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

[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)

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

--- Comment #64 from Nate Graham  ---
15-minute bugs are Plasma only at this point and Dolphin isn't a part of
Plasma.

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

[kwin] [Bug 426644] Screens go black / unresponsive after sleep or lock

2023-03-24 Thread Thorolf E . R . Weißhuhn

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

Thorolf E.R. Weißhuhn  changed:

   What|Removed |Added

 CC||t...@gmx.de
 Resolution|DUPLICATE   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #25 from Thorolf E.R. Weißhuhn  ---
Same here with internal laptop display as secondary screen.

Deleting `~/.local/share` (suggested in the Manjaro forum[*]) worked for a day
or so.

Quick workaround: 
In system tray open Display Configuration, click a preset different from your
current settings; screen lights up, shows normal display. Click back to your
original setting, done.

Manjaro
KDE Plasma 5.26.5
KDE Frameworks 5.103.0
Qt 5.15.8
Kernel 6.1.19-1-MANJARO (64-bit)
Graphics X11
Graphics Processor: Mesa Intel® Xe Graphics

[*]
https://forum.manjaro.org/t/only-one-monitor-working-after-latest-update-11-02-22/125876

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

[kdeconnect] [Bug 422136] Album art gets sent from the computer to the phone, but not the other way round

2023-03-24 Thread darkN00B

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

darkN00B  changed:

   What|Removed |Added

 CC||rnbds...@gmail.com

--- Comment #1 from darkN00B  ---
Any updates on this issue? Seems like that this bug is getting unnoticed by the
devs out there.

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

[Powerdevil] [Bug 423035] Turn off screen shortcut turns the screen back on automatically

2023-03-24 Thread Alberto Mattea

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

Alberto Mattea  changed:

   What|Removed |Added

 CC||albe...@mattea.info

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

[plasmashell] [Bug 466362] 10+ MB leak every second after new display added

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

Nate Graham  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 467284] plasmashell - Unbound memory leaks and high cpu usage on deactivation of secondary screen using xrandr

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

Nate Graham  changed:

   What|Removed |Added

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

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

[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor

2023-03-24 Thread Hexagon

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

--- Comment #29 from Hexagon  ---
The problem exists now for over 6 months and it does not seem to have improved.
Unfortunately I do not have enough insight to provide a fix myself. Could
anyone involved in KWin please take a look at this problem? I think it
influences the whole Plasma experience on Wayland as nearly anyone uses some
kind of legacy application with xWayland and Hi-DPI monitors with scaling get
more and more common. Who knows, maybe it is just a "off by one error"
somewhere in the forwarding of the coordinates from the Xorg application to the
Wayland wrapper window in KWin. Or the coordinates returned when the
maximizeWindow() function is called returns wrong values, explaining why the
border sometimes disappears until one maximizes the window again. Whatever it
is, please try to find a solution. Thanks to all involved.

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

[konsole] [Bug 403285] When using Synaptics driver-provided scroll inertia feature, pressing CTRL while scrolling, but not using the touchpad causes zoom

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

Nate Graham  changed:

   What|Removed |Added

Summary|Pressing CTRL while |When using Synaptics
   |scrolling, but not using|driver-provided scroll
   |the touchpad causes zoom|inertia feature, pressing
   ||CTRL while scrolling, but
   ||not using the touchpad
   ||causes zoom

--- Comment #14 from Nate Graham  ---
The old unmaintained Synaptics touchpad drivers expose a driver-level scroll
inertia feature that's the cause of this issue.

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

[plasmashell] [Bug 464286] Re-add UI to expose IgnoreSelection=false setting

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

kdebugs.kap...@antichef.net changed:

   What|Removed |Added

 CC||kdebugs.kap...@antichef.net

--- Comment #9 from kdebugs.kap...@antichef.net ---
I am also affected by this bug. It is highly annoying as it is breaking my
workflow and decades long habits. Nerfing one of the superior advantage of *NIX
like OSes of having text selection copy/paste on middle click feels like
shooting one self in the foot.

this is feature is so central in my daily usage that I would consider migrating
away from KDE over losing this functionality despite using KDE a my DE of
choice since KDE 3.

Since I notice the features being broken I tried enabling it from the GUI
settings screen but the "always save in history" text selection grays itself
out when I click it. validating the settings in this state then sometimes works
for a very limited time and sometimes not at all.

That people are confused by their own use of their computer is not a valid
justification for removing a feature that other people actually rely on. The
confused users can educate themselves on how to disable the setting that
confuses them instead.

Sorry of being vocal about this issue but it is important to me and I really
dislike the GNOME mentality supposing that users are stupid and have to be
protected from their own stupidity by removing features.

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

[systemsettings] [Bug 467269] LC_PAGE should be LC_PAPER?

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In|5.27.3  |5.27.4

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

[NeoChat] [Bug 455048] Show non-message matrix events in the room list as message preview

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

James Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
   |ork/neochat/commit/76b5463d |ork/neochat/commit/741cb571
   |ac83507b38ef015c36c08d63c63 |056959c5ca56995b7238e9cf7dc
   |8bd1b   |2abb0

--- Comment #4 from James Graham  ---
Git commit 741cb571056959c5ca56995b7238e9cf7dc2abb0 by James Graham.
Committed on 13/03/2023 at 19:00.
Pushed by nvrwhere into branch 'master'.

Fix state event visiblity in timeline

Rework the filtering of state events in the timeline and for lastevent. This is
now consistent everywhere and includes the following:
- The timeline settings are obeyed everywhere
- A new setting is added to filter all state events
- Last event obeys the timeline setting in all cases
- The roomlist will show a state event as the latest event if it's visible in
the timeline
- Names are no longer hyperlinked in eventToString if plaintext is selected.
Closes network/neochat#148

M  +11   -20   src/models/messageeventmodel.cpp
M  +0-2src/models/messageeventmodel.h
M  +8-22   src/models/messagefiltermodel.cpp
M  +0-21   src/models/roomlistmodel.cpp
M  +0-1src/models/roomlistmodel.h
M  +8-4src/neochatconfig.kcfg
M  +31   -7src/neochatroom.cpp
M  +1-1src/neochatroom.h
M  +42   -15   src/qml/Settings/GeneralSettingsPage.qml

https://invent.kde.org/network/neochat/commit/741cb571056959c5ca56995b7238e9cf7dc2abb0

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

[krita] [Bug 467035] Transform tools are broken in the Krita Next nightly

2023-03-24 Thread amyspark

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

--- Comment #2 from amyspark  ---
Git commit b628f31ae02ddf899bb8271a40f42804699ab366 by L. E. Segovia.
Committed on 08/03/2023 at 12:10.
Pushed by lsegovia into branch 'master'.

Revert "TransformStrokeStrategy: pass references instead of ~512B of state"

This reverts commit 8d720211e292c2c3e8afb242593eff16b60aaee5.

M  +3-11   plugins/tools/tool_transform2/kis_tool_transform.cc
M  +1-3plugins/tools/tool_transform2/kis_tool_transform.h
M  +2-2   
plugins/tools/tool_transform2/strokes/inplace_transform_stroke_strategy.cpp
M  +1-1   
plugins/tools/tool_transform2/strokes/inplace_transform_stroke_strategy.h
M  +1-1   
plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp
M  +1-1   
plugins/tools/tool_transform2/strokes/transform_stroke_strategy.h

https://invent.kde.org/graphics/krita/commit/b628f31ae02ddf899bb8271a40f42804699ab366

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

[NeoChat] [Bug 466330] NeoChat Crashes at launch

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

James Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
   |ork/neochat/commit/da1c664f |ork/neochat/commit/f6ba4f2e
   |941b96d650e64240253ba09f46e |cd470487f1133a5704590860597
   |d291a   |50775

--- Comment #3 from James Graham  ---
Git commit f6ba4f2ecd470487f1133a570459086059750775 by James Graham.
Committed on 13/03/2023 at 17:28.
Pushed by nvrwhere into branch 'master'.

Improve Text Handling

Improve the handling of text both when sending and receiving.

The main feature is to fix the linked bug (and a host of others that are
unreported but similar) which is caused by the fact that we don't properly
clean html. This mr does that as per the matrix spec
https://spec.matrix.org/v1.5/client-server-api/#mroommessage-msgtypes. So any
disallowed tags or attributes are removed and it does the special handling for
certain attributes.

Additionally the functions are also designed to cover any other text formatting
required, particularly fro received strings.

The receive side is covered by 2 functions `handleRecieveRichText` and
`handleRecievePlainText`. The rich/plain in the function name refers to the
output type not the input type (both can take plain and rich input), so
`handleRecieveRichText` is called to get a string suitable to go in a rich text
control and `handleRecievePlainText` for a plain control.

The functions also handle the following some of which was previously handled by
`eventToString` in `NeoChatRoom`:
- Strip and reply from the string
- Format any user mentions
- Linkify links in plain strings
- Handle mxc urls in rich text (uses the new `room->makeMediaUrl` functionality
from libQuotient)
- `handleRecievePlainText` also deals with markup making
`NeoChatRoom->subtitle` redundant

There is also an extensive test suite which defines the behaviour and the best
way to review this is probably to look at the tests and decide whether you
agree with the expected output given the inputs and/or if there is any missing
behaviour.

The final aim especially with the test suite is to give us a framework to make
further updates in the future easier and hopefully prevent a new feature
breaking old behaviour with the tests.
Related: bug 463932, bug 466930

M  +6-0autotests/CMakeLists.txt
M  +1-1autotests/neochatroomtest.cpp
A  +482  -0autotests/texthandlertest.cpp [License: GPL(3+eV) GPL(v3.0)
GPL(v2.0)]
M  +1-1src/CMakeLists.txt
M  +5-17   src/actionshandler.cpp
M  +0-2src/actionshandler.h
M  +0-1src/models/messageeventmodel.cpp
M  +1-1src/models/roomlistmodel.cpp
M  +28   -76   src/neochatroom.cpp
M  +2-8src/neochatroom.h
M  +4-2src/notificationsmanager.cpp
M  +2-19   src/qml/Component/Timeline/RichLabel.qml
A  +378  -0src/texthandler.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
A  +131  -0src/texthandler.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
D  +0-4src/utils.cpp
D  +0-16   src/utils.h

https://invent.kde.org/network/neochat/commit/f6ba4f2ecd470487f1133a570459086059750775

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

[systemsettings] [Bug 466861] default print format overridden

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

--- Comment #8 from hanyo...@protonmail.com ---
Git commit 27de75798ee19fc1629c99cc13ee08754e0c47bd by Han Young, on behalf of
Nate Graham.
Committed on 13/03/2023 at 23:24.
Pushed by hanyoung into branch 'Plasma/5.27'.

kcms/region_language: set LC_PAPER, not LC_PAGE

The correct name of this environment variable/format is "LC_PAPER."
We look for it by the correct name in kcmregionandlang.cpp, but not in
regionandlangsettingsbase.kcfg, causing a mismatch.
Related: bug 467269
FIXED-IN: 5.27.3


(cherry picked from commit 7b7e70b2262285dbfc294cc6617f4c0787a61d5c)

M  +1-1kcms/region_language/regionandlangsettingsbase.kcfg

https://invent.kde.org/plasma/plasma-workspace/commit/27de75798ee19fc1629c99cc13ee08754e0c47bd

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

[NeoChat] [Bug 466930] URL that contains email-like pattern is split into two links

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

James Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
   |ork/neochat/commit/f6ba4f2e |ork/neochat/commit/da1c664f
   |cd470487f1133a5704590860597 |941b96d650e64240253ba09f46e
   |50775   |d291a

--- Comment #4 from James Graham  ---
Git commit da1c664f941b96d650e64240253ba09f46ed291a by James Graham.
Committed on 13/03/2023 at 18:18.
Pushed by nvrwhere into branch 'release/23.04'.

Cherrypick Improve Text Handling to 23.04

Improve the handling of text both when sending and receiving.

The main feature is to fix the linked bug (and a host of others that are
unreported but similar) which is caused by the fact that we don't properly
clean html. This mr does that as per the matrix spec
https://spec.matrix.org/v1.5/client-server-api/#mroommessage-msgtypes. So any
disallowed tags or attributes are removed and it does the special handling for
certain attributes.

Additionally the functions are also designed to cover any other text formatting
required, particularly fro received strings.

The receive side is covered by 2 functions `handleRecieveRichText` and
`handleRecievePlainText`. The rich/plain in the function name refers to the
output type not the input type (both can take plain and rich input), so
`handleRecieveRichText` is called to get a string suitable to go in a rich text
control and `handleRecievePlainText` for a plain control.

The functions also handle the following some of which was previously handled by
`eventToString` in `NeoChatRoom`:
- Strip and reply from the string
- Format any user mentions
- Linkify links in plain strings
- Handle mxc urls in rich text (uses the new `room->makeMediaUrl` functionality
from libQuotient)
- `handleRecievePlainText` also deals with markup making
`NeoChatRoom->subtitle` redundant

There is also an extensive test suite which defines the behaviour and the best
way to review this is probably to look at the tests and decide whether you
agree with the expected output given the inputs and/or if there is any missing
behaviour.

The final aim especially with the test suite is to give us a framework to make
further updates in the future easier and hopefully prevent a new feature
breaking old behaviour with the tests.
Related: bug 463932, bug 466330


(cherry picked from commit f6ba4f2ecd470487f1133a570459086059750775)

M  +6-0autotests/CMakeLists.txt
M  +1-1autotests/neochatroomtest.cpp
A  +482  -0autotests/texthandlertest.cpp [License: GPL(3+eV) GPL(v3.0)
GPL(v2.0)]
M  +1-1src/CMakeLists.txt
M  +5-17   src/actionshandler.cpp
M  +0-2src/actionshandler.h
M  +0-1src/models/messageeventmodel.cpp
M  +1-1src/models/roomlistmodel.cpp
M  +28   -76   src/neochatroom.cpp
M  +2-8src/neochatroom.h
M  +4-2src/notificationsmanager.cpp
M  +2-19   src/qml/Component/Timeline/RichLabel.qml
A  +378  -0src/texthandler.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
A  +131  -0src/texthandler.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
D  +0-4src/utils.cpp
D  +0-16   src/utils.h

https://invent.kde.org/network/neochat/commit/da1c664f941b96d650e64240253ba09f46ed291a

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

[systemsettings] [Bug 467269] LC_PAGE should be LC_PAPER?

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

hanyo...@protonmail.com changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/
   |7b7e70b2262285dbfc294cc6617 |27de75798ee19fc1629c99cc13e
   |f4c0787a61d5c   |e08754e0c47bd

--- Comment #5 from hanyo...@protonmail.com ---
Git commit 27de75798ee19fc1629c99cc13ee08754e0c47bd by Han Young, on behalf of
Nate Graham.
Committed on 13/03/2023 at 23:24.
Pushed by hanyoung into branch 'Plasma/5.27'.

kcms/region_language: set LC_PAPER, not LC_PAGE

The correct name of this environment variable/format is "LC_PAPER."
We look for it by the correct name in kcmregionandlang.cpp, but not in
regionandlangsettingsbase.kcfg, causing a mismatch.
Related: bug 466861
FIXED-IN: 5.27.3


(cherry picked from commit 7b7e70b2262285dbfc294cc6617f4c0787a61d5c)

M  +1-1kcms/region_language/regionandlangsettingsbase.kcfg

https://invent.kde.org/plasma/plasma-workspace/commit/27de75798ee19fc1629c99cc13ee08754e0c47bd

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

[krita] [Bug 466068] Wrong ICC profile handling when moving app from one display to another

2023-03-24 Thread amyspark

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

--- Comment #7 from amyspark  ---
Git commit 8355ae4ec082744be0614e238887540e8124d0aa by L. E. Segovia.
Committed on 01/03/2023 at 01:52.
Pushed by lsegovia into branch 'master'.

KisMainWindow: emit screenChanged to act on display preferences change

M  +3-0libs/ui/KisMainWindow.cpp

https://invent.kde.org/graphics/krita/commit/8355ae4ec082744be0614e238887540e8124d0aa

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

[NeoChat] [Bug 463932] Add upper limit to text size

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

James Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
   |ork/neochat/commit/f6ba4f2e |ork/neochat/commit/da1c664f
   |cd470487f1133a5704590860597 |941b96d650e64240253ba09f46e
   |50775   |d291a

--- Comment #6 from James Graham  ---
Git commit da1c664f941b96d650e64240253ba09f46ed291a by James Graham.
Committed on 13/03/2023 at 18:18.
Pushed by nvrwhere into branch 'release/23.04'.

Cherrypick Improve Text Handling to 23.04

Improve the handling of text both when sending and receiving.

The main feature is to fix the linked bug (and a host of others that are
unreported but similar) which is caused by the fact that we don't properly
clean html. This mr does that as per the matrix spec
https://spec.matrix.org/v1.5/client-server-api/#mroommessage-msgtypes. So any
disallowed tags or attributes are removed and it does the special handling for
certain attributes.

Additionally the functions are also designed to cover any other text formatting
required, particularly fro received strings.

The receive side is covered by 2 functions `handleRecieveRichText` and
`handleRecievePlainText`. The rich/plain in the function name refers to the
output type not the input type (both can take plain and rich input), so
`handleRecieveRichText` is called to get a string suitable to go in a rich text
control and `handleRecievePlainText` for a plain control.

The functions also handle the following some of which was previously handled by
`eventToString` in `NeoChatRoom`:
- Strip and reply from the string
- Format any user mentions
- Linkify links in plain strings
- Handle mxc urls in rich text (uses the new `room->makeMediaUrl` functionality
from libQuotient)
- `handleRecievePlainText` also deals with markup making
`NeoChatRoom->subtitle` redundant

There is also an extensive test suite which defines the behaviour and the best
way to review this is probably to look at the tests and decide whether you
agree with the expected output given the inputs and/or if there is any missing
behaviour.

The final aim especially with the test suite is to give us a framework to make
further updates in the future easier and hopefully prevent a new feature
breaking old behaviour with the tests.
Related: bug 466330, bug 466930


(cherry picked from commit f6ba4f2ecd470487f1133a570459086059750775)

M  +6-0autotests/CMakeLists.txt
M  +1-1autotests/neochatroomtest.cpp
A  +482  -0autotests/texthandlertest.cpp [License: GPL(3+eV) GPL(v3.0)
GPL(v2.0)]
M  +1-1src/CMakeLists.txt
M  +5-17   src/actionshandler.cpp
M  +0-2src/actionshandler.h
M  +0-1src/models/messageeventmodel.cpp
M  +1-1src/models/roomlistmodel.cpp
M  +28   -76   src/neochatroom.cpp
M  +2-8src/neochatroom.h
M  +4-2src/notificationsmanager.cpp
M  +2-19   src/qml/Component/Timeline/RichLabel.qml
A  +378  -0src/texthandler.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
A  +131  -0src/texthandler.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
D  +0-4src/utils.cpp
D  +0-16   src/utils.h

https://invent.kde.org/network/neochat/commit/da1c664f941b96d650e64240253ba09f46ed291a

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

[NeoChat] [Bug 466330] NeoChat Crashes at launch

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

James Graham  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/netw
   ||ork/neochat/commit/da1c664f
   ||941b96d650e64240253ba09f46e
   ||d291a
 Resolution|LATER   |FIXED

--- Comment #2 from James Graham  ---
Git commit da1c664f941b96d650e64240253ba09f46ed291a by James Graham.
Committed on 13/03/2023 at 18:18.
Pushed by nvrwhere into branch 'release/23.04'.

Cherrypick Improve Text Handling to 23.04

Improve the handling of text both when sending and receiving.

The main feature is to fix the linked bug (and a host of others that are
unreported but similar) which is caused by the fact that we don't properly
clean html. This mr does that as per the matrix spec
https://spec.matrix.org/v1.5/client-server-api/#mroommessage-msgtypes. So any
disallowed tags or attributes are removed and it does the special handling for
certain attributes.

Additionally the functions are also designed to cover any other text formatting
required, particularly fro received strings.

The receive side is covered by 2 functions `handleRecieveRichText` and
`handleRecievePlainText`. The rich/plain in the function name refers to the
output type not the input type (both can take plain and rich input), so
`handleRecieveRichText` is called to get a string suitable to go in a rich text
control and `handleRecievePlainText` for a plain control.

The functions also handle the following some of which was previously handled by
`eventToString` in `NeoChatRoom`:
- Strip and reply from the string
- Format any user mentions
- Linkify links in plain strings
- Handle mxc urls in rich text (uses the new `room->makeMediaUrl` functionality
from libQuotient)
- `handleRecievePlainText` also deals with markup making
`NeoChatRoom->subtitle` redundant

There is also an extensive test suite which defines the behaviour and the best
way to review this is probably to look at the tests and decide whether you
agree with the expected output given the inputs and/or if there is any missing
behaviour.

The final aim especially with the test suite is to give us a framework to make
further updates in the future easier and hopefully prevent a new feature
breaking old behaviour with the tests.
Related: bug 463932, bug 466930


(cherry picked from commit f6ba4f2ecd470487f1133a570459086059750775)

M  +6-0autotests/CMakeLists.txt
M  +1-1autotests/neochatroomtest.cpp
A  +482  -0autotests/texthandlertest.cpp [License: GPL(3+eV) GPL(v3.0)
GPL(v2.0)]
M  +1-1src/CMakeLists.txt
M  +5-17   src/actionshandler.cpp
M  +0-2src/actionshandler.h
M  +0-1src/models/messageeventmodel.cpp
M  +1-1src/models/roomlistmodel.cpp
M  +28   -76   src/neochatroom.cpp
M  +2-8src/neochatroom.h
M  +4-2src/notificationsmanager.cpp
M  +2-19   src/qml/Component/Timeline/RichLabel.qml
A  +378  -0src/texthandler.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
A  +131  -0src/texthandler.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
D  +0-4src/utils.cpp
D  +0-16   src/utils.h

https://invent.kde.org/network/neochat/commit/da1c664f941b96d650e64240253ba09f46ed291a

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

[NeoChat] [Bug 466930] URL that contains email-like pattern is split into two links

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

James Graham  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/netw
   ||ork/neochat/commit/f6ba4f2e
   ||cd470487f1133a5704590860597
   ||50775

--- Comment #3 from James Graham  ---
Git commit f6ba4f2ecd470487f1133a570459086059750775 by James Graham.
Committed on 13/03/2023 at 17:28.
Pushed by nvrwhere into branch 'master'.

Improve Text Handling

Improve the handling of text both when sending and receiving.

The main feature is to fix the linked bug (and a host of others that are
unreported but similar) which is caused by the fact that we don't properly
clean html. This mr does that as per the matrix spec
https://spec.matrix.org/v1.5/client-server-api/#mroommessage-msgtypes. So any
disallowed tags or attributes are removed and it does the special handling for
certain attributes.

Additionally the functions are also designed to cover any other text formatting
required, particularly fro received strings.

The receive side is covered by 2 functions `handleRecieveRichText` and
`handleRecievePlainText`. The rich/plain in the function name refers to the
output type not the input type (both can take plain and rich input), so
`handleRecieveRichText` is called to get a string suitable to go in a rich text
control and `handleRecievePlainText` for a plain control.

The functions also handle the following some of which was previously handled by
`eventToString` in `NeoChatRoom`:
- Strip and reply from the string
- Format any user mentions
- Linkify links in plain strings
- Handle mxc urls in rich text (uses the new `room->makeMediaUrl` functionality
from libQuotient)
- `handleRecievePlainText` also deals with markup making
`NeoChatRoom->subtitle` redundant

There is also an extensive test suite which defines the behaviour and the best
way to review this is probably to look at the tests and decide whether you
agree with the expected output given the inputs and/or if there is any missing
behaviour.

The final aim especially with the test suite is to give us a framework to make
further updates in the future easier and hopefully prevent a new feature
breaking old behaviour with the tests.
Related: bug 463932, bug 466330

M  +6-0autotests/CMakeLists.txt
M  +1-1autotests/neochatroomtest.cpp
A  +482  -0autotests/texthandlertest.cpp [License: GPL(3+eV) GPL(v3.0)
GPL(v2.0)]
M  +1-1src/CMakeLists.txt
M  +5-17   src/actionshandler.cpp
M  +0-2src/actionshandler.h
M  +0-1src/models/messageeventmodel.cpp
M  +1-1src/models/roomlistmodel.cpp
M  +28   -76   src/neochatroom.cpp
M  +2-8src/neochatroom.h
M  +4-2src/notificationsmanager.cpp
M  +2-19   src/qml/Component/Timeline/RichLabel.qml
A  +378  -0src/texthandler.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
A  +131  -0src/texthandler.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
D  +0-4src/utils.cpp
D  +0-16   src/utils.h

https://invent.kde.org/network/neochat/commit/f6ba4f2ecd470487f1133a570459086059750775

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

[partitionmanager] [Bug 466992] KDE Partition Manager shows the partition name as label and doesn't allow you to change one

2023-03-24 Thread Andrius Štikonas

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

--- Comment #4 from Andrius Štikonas  ---
Git commit 6f88ec0124fa7da45cd0c479829a66f7ddd41296 by Andrius Štikonas.
Committed on 12/03/2023 at 00:27.
Pushed by stikonas into branch 'master'.

Rename Partition Label to Partition Name

M  +1-1src/gui/partitionmanagerwidgetbase.ui
M  +1-1src/gui/partpropswidgetbase.ui

https://invent.kde.org/system/partitionmanager/commit/6f88ec0124fa7da45cd0c479829a66f7ddd41296

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

[NeoChat] [Bug 463932] Add upper limit to text size

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

James Graham  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/netw
   ||ork/neochat/commit/f6ba4f2e
   ||cd470487f1133a5704590860597
   ||50775

--- Comment #5 from James Graham  ---
Git commit f6ba4f2ecd470487f1133a570459086059750775 by James Graham.
Committed on 13/03/2023 at 17:28.
Pushed by nvrwhere into branch 'master'.

Improve Text Handling

Improve the handling of text both when sending and receiving.

The main feature is to fix the linked bug (and a host of others that are
unreported but similar) which is caused by the fact that we don't properly
clean html. This mr does that as per the matrix spec
https://spec.matrix.org/v1.5/client-server-api/#mroommessage-msgtypes. So any
disallowed tags or attributes are removed and it does the special handling for
certain attributes.

Additionally the functions are also designed to cover any other text formatting
required, particularly fro received strings.

The receive side is covered by 2 functions `handleRecieveRichText` and
`handleRecievePlainText`. The rich/plain in the function name refers to the
output type not the input type (both can take plain and rich input), so
`handleRecieveRichText` is called to get a string suitable to go in a rich text
control and `handleRecievePlainText` for a plain control.

The functions also handle the following some of which was previously handled by
`eventToString` in `NeoChatRoom`:
- Strip and reply from the string
- Format any user mentions
- Linkify links in plain strings
- Handle mxc urls in rich text (uses the new `room->makeMediaUrl` functionality
from libQuotient)
- `handleRecievePlainText` also deals with markup making
`NeoChatRoom->subtitle` redundant

There is also an extensive test suite which defines the behaviour and the best
way to review this is probably to look at the tests and decide whether you
agree with the expected output given the inputs and/or if there is any missing
behaviour.

The final aim especially with the test suite is to give us a framework to make
further updates in the future easier and hopefully prevent a new feature
breaking old behaviour with the tests.
Related: bug 466330, bug 466930

M  +6-0autotests/CMakeLists.txt
M  +1-1autotests/neochatroomtest.cpp
A  +482  -0autotests/texthandlertest.cpp [License: GPL(3+eV) GPL(v3.0)
GPL(v2.0)]
M  +1-1src/CMakeLists.txt
M  +5-17   src/actionshandler.cpp
M  +0-2src/actionshandler.h
M  +0-1src/models/messageeventmodel.cpp
M  +1-1src/models/roomlistmodel.cpp
M  +28   -76   src/neochatroom.cpp
M  +2-8src/neochatroom.h
M  +4-2src/notificationsmanager.cpp
M  +2-19   src/qml/Component/Timeline/RichLabel.qml
A  +378  -0src/texthandler.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
A  +131  -0src/texthandler.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)]
D  +0-4src/utils.cpp
D  +0-16   src/utils.h

https://invent.kde.org/network/neochat/commit/f6ba4f2ecd470487f1133a570459086059750775

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

[krita] [Bug 466497] Windows on ARM builds do not identify the OS architecture

2023-03-24 Thread amyspark

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

amyspark  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/-/commit/adf9290 |hics/krita/commit/adf92901b
   |1b643390a5d708ae8aa60551d14 |643390a5d708ae8aa60551d1498
   |98453d  |453d

--- Comment #6 from amyspark  ---
Git commit adf92901b643390a5d708ae8aa60551d1498453d by L. E. Segovia, on behalf
of Hernan Martinez.
Committed on 01/03/2023 at 17:16.
Pushed by merge-service into branch 'master'.

Update systeminformation_p.h to handle ARM64 on Windows

Part-of: 

M  +3-0libs/widgetutils/xmlgui/systeminformation_p.h

https://invent.kde.org/graphics/krita/commit/adf92901b643390a5d708ae8aa60551d1498453d

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

[krusader] [Bug 466864] New: Krusader crashes on launch with fresh install of krusader-git-2.9.0.dev.r6611.g07f7d051-1

2023-03-24 Thread camhelmuth

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

Bug ID: 466864
   Summary: Krusader crashes on launch with fresh install of
krusader-git-2.9.0.dev.r6611.g07f7d051-1
Classification: Applications
   Product: krusader
   Version: Git
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: camhelm...@protonmail.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY
***
❯ krusader
kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "No
jobs" msgid_plural: "" msgctxt: ""
22:50:05.614-debug default main@94 # System icon theme: "Win11"
22:50:05.739-warning kf.i18n unknown@0 # Trying to convert empty
KLocalizedString to QString.


***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Arch Linux
6.2.2-arch1-1 (64-bit)

(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[plasma-integration] [Bug 467553] New: workspace Behaviour - Screen Edges sudden stopped working

2023-03-24 Thread charles . davids . 1999

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

Bug ID: 467553
Summary: workspace Behaviour - Screen Edges sudden stopped
working
Classification: Plasma
Product: plasma-integration
Version: 5.18.8
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: charles.davids.1...@protonmail.com
Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I've set the top left corner of screen edges to display a grid of virtual
desktops. This has stopped working. I can still use the short cut keys in my
case (ctrl+1, ctrl+2). Unfortunately virtual desktop 2 is a VM, and blocks host
background commands. I have to minimise before I can use ctrl+1 to go to screen
1.

STEPS TO REPRODUCE
1. Swap position within screen edges. no effect
2. system update, reswap position in screen edges, no effect
3. guess I'll try a reboot, and retest as above

OBSERVED RESULT
Nothing happens when mouse is moved into top left corner

EXPECTED RESULT
I should see a grid of all virtual desktops (two 2) in total

SOFTWARE/OS VERSIONS
Windows: Not Likely
macOS: not yet
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
NO updates or system changes until I realised the problem. It just happened out
of the blue

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

[digikam] [Bug 466593] New: Add view spherical panoramas

2023-03-24 Thread sawser

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

Bug ID: 466593
   Summary: Add  view spherical panoramas
Classification: Applications
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: saw...@yandex.ru
  Target Milestone: ---

Modern smartphones (for example, google pixel) can shoot spherical panoramas.
You can add their viewer to digikam?

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

[krusader] [Bug 466864] Krusader crashes on launch with fresh install of krusader-git-2.9.0.dev.r6611.g07f7d051-1

2023-03-24 Thread camhelmuth

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

camhelm...@protonmail.com  changed:

   What|Removed |Added

 CC||camhelm...@protonmail.com

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

[plasma-integration] [Bug 467672] New: workspace Behaviour - Screen Edges sudden not working

2023-03-24 Thread charles . davids . 1999

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

Bug ID: 467672
Summary: workspace Behaviour - Screen Edges sudden not working
Classification: Plasma
Product: plasma-integration
Version: 5.24.7
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: charles.davids.1...@protonmail.com
Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I have the top left corner set to display a grid of all virtual
desktops/windows. It suddenly stopped working the other day. I have upgraded to
whatever the latest version of everything I could find. it took hours and my pc
is as fast as a dead snail now.

STEPS TO REPRODUCE
1. remove all, reset pc, reselect, test= nothing
2. remove, reset Pc, select different action, different location = nothing
3. upgraded, and repeated steps 1 and 2.

OBSERVED RESULT
nothing happens.
IS there a specific install for desktop effects & screen edges?

EXPECTED RESULT
hopefully my plasma is updated enough that I'll get a response, other than seek
help elsewhere

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

ADDITIONAL INFORMATION
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-67-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5 CPU 661 @ 3.33GHz
Memory: 7.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 710/PCIe/SSE2

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

[KScreen] [Bug 467760] Display details in arrangement and priority are ambiguous with multiple identical monitors

2023-03-24 Thread Reg

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

--- Comment #1 from Reg  ---
Created attachment 157555
  --> https://bugs.kde.org/attachment.cgi?id=157555&action=edit
Display priority ambiguity

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

[KScreen] [Bug 467760] New: Display details in arrangement and priority are ambiguous with multiple identical monitors

2023-03-24 Thread Reg

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

Bug ID: 467760
   Summary: Display details in arrangement and priority are
ambiguous with multiple identical monitors
Classification: Plasma
   Product: KScreen
   Version: 5.27.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Plasma Applet
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: nybbles2by...@gmail.com
  Target Milestone: ---

Created attachment 157554
  --> https://bugs.kde.org/attachment.cgi?id=157554&action=edit
Display arrange ambiguity

SUMMARY
I think the images attached show better than I can ever word it however the
issues, with reference to the obvious ambiguity shown in the images are:

- Changing monitor arrangement is trial and error because there is no way to
tell one monitor from the other.

- Changing monitor priority can look like you didn't even change the order
because the monitors are identical.

What needs to happen for this to be fixed:

1. The description of the monitors needs to contain a unique number or name.

2. The description of the monitors needs to contain the priority now that has
been added as a priority list and the priority list needs to show the unique
number or name for the monitors.

3. For large numbers of monitors like this it is desirable that when you click
on "Identity" that the numbers say up until you click to remove them. 2-3
seconds up is not nearly enough to be useful. Also, the 30+ character
description could be replaced with something like a single fixed number for the
display and perhaps another number showing it's priority - something more
useful to digest.

4. Ideally you could right-click on one of the monitor images that you use to
arrange them to set which one is primary. And, by extension set other
attributes that way.

Finally, there is an additional issue that sometimes moving a monitor or
changing some other parameter will cause all the monitors to pop to the same
resolution which ends up being lower than any of their native maximum
resolutions which is usually undesirable. If it's going to pop to some default
it would be highly desirable to make it the maximum/native resolution of the
monitors rather than some arbitrary lower resolution default. This would make
this particular bug essentially transparent to almost all users since the
default would be what is desirable.

STEPS TO REPRODUCE
1. You just need a bunch of identical monitors
2. 
3. 

OBSERVED RESULT
See images

EXPECTED RESULT
Being able to tell the which is which

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Tumbleweed
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[Tokodon] [Bug 467759] New: Support activitypub mimetypes

2023-03-24 Thread Soni L.

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

Bug ID: 467759
   Summary: Support activitypub mimetypes
Classification: Applications
   Product: Tokodon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: fakedme+...@gmail.com
CC: c...@carlschwan.eu, j...@redstrate.com
  Target Milestone: ---

Note: XDG is broken - see
https://mailarchive.ietf.org/arch/msg/art/EEAIbW8mtUGOQKPrfMkLFrjE83s/

The ActivityPub mimetypes are

application/ld+json; profile="https://www.w3.org/ns/activitystreams";
application/activity+json

While mimetypes are usually called with paths (except for x-scheme-handler
ones), they can also be called with URIs sometimes. It'd be nice to lean into
those.

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

[plasma-nm] [Bug 463412] I seem to connect to both Wi-Fi and Wired Ethernet

2023-03-24 Thread Marco Parillo

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

--- Comment #4 from Marco Parillo  ---
Informative Reddit Discussion:
https://www.reddit.com/r/kde/comments/120lb1a/why_does_kde_network_manager_connects_to_both_my/

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

[kate] [Bug 464088] Kate crashes when switching branches using git plugin

2023-03-24 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/util
   ||ities/kate/commit/1e71ffeca
   ||3d8e0daa69a85cf22730c84dc45
   ||7d02
 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Christoph Cullmann  ---
Git commit 1e71ffeca3d8e0daa69a85cf22730c84dc457d02 by Christoph Cullmann, on
behalf of Waqar Ahmed.
Committed on 24/03/2023 at 17:37.
Pushed by cullmann into branch 'master'.

Cleanup/improve MWModOnHDDialog

This commit is a clean up of Kate modified dialog to make it less crashy
and easier to understand.

- rename twDocuments to docsTreeWidget
- Store doc as a QPointer inside QTreeWidgetItem
- Check the doc for nullness everywhere
- Check the docInfo for nullness everywhere (it can be null)

M  +2-2apps/lib/katemainwindow.cpp
M  +54   -37   apps/lib/katemwmodonhddialog.cpp
M  +6-5apps/lib/katemwmodonhddialog.h

https://invent.kde.org/utilities/kate/commit/1e71ffeca3d8e0daa69a85cf22730c84dc457d02

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

[kde] [Bug 467757] xwaylandvideobridge looks weird when sharing sharing on discord

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

--- Comment #1 from dflewd...@mozmail.com ---
Got this when actually selecting and sharing the window.

select sources done
"/org/freedesktop/portal/desktop/request/1_301/pwbypass3756624794"
params QMap() 0
started! "/org/freedesktop/portal/desktop/request/1_301/pwbypass3756624794"
kpipewire_logging: Failed to query DMA-BUF formats.
close

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

[knotes] [Bug 467758] New: Typo in noteshared/src/settings/notesharedglobalconfig.kcfg:37 label text

2023-03-24 Thread Oliver Kellogg

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

Bug ID: 467758
   Summary: Typo in
noteshared/src/settings/notesharedglobalconfig.kcfg:37
label text
Classification: Applications
   Product: knotes
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: okell...@users.sourceforge.net
CC: myr...@kde.org
  Target Milestone: ---

Git master noteshared/src/settings/notesharedglobalconfig.kcfg approx. line 37
has


  The port will listen on and send notes to.
  24837


I believe the label text should be
"The port to listen on and send notes to."
I.e. replace "will" by "to".

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

[NeoChat] [Bug 464698] Sometimes the scrollbar doesn't move when clicking and dragging it

2023-03-24 Thread S. Christian Collins

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

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

--- Comment #8 from S. Christian Collins  ---
Whether or not the scrollbar works seems to do with how far to the right the
mouse cursor is positioned when you click to drag the scrollbar. If the cursor
is positioned more towards the left side of the scrollbar, it works. If it is
positioned more to the right side, it doesn't.

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

[plasmashell] [Bug 467756] Plasma crashes when turning on main monitor

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

Bug Janitor Service  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kde] [Bug 467757] New: xwaylandvideobridge looks weird when sharing sharing on discord