[yakuake] [Bug 418354] yakuake blur not working, while konsole has blur enabled

2021-12-23 Thread Robby Engelmann
https://bugs.kde.org/show_bug.cgi?id=418354

Robby Engelmann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|unspecified |Git (Frameworks 5)
   Platform|Kubuntu Packages|openSUSE RPMs
 Status|REPORTED|CONFIRMED
 CC||robby.engelmann@r-engelmann
   ||.de

--- Comment #6 from Robby Engelmann  ---
Same here using openSUSE's git master rpms

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

[yakuake] [Bug 447459] Feature request: Ability to visually group tabs or change their background color

2021-12-23 Thread Manuel Tancoigne
https://bugs.kde.org/show_bug.cgi?id=447459

Manuel Tancoigne  changed:

   What|Removed |Added

 CC||m...@experimentslabs.com

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

[konsole] [Bug 396960] Feature Request: ability to set Konsole tab background color using escape codes (like can already be done for the terminal background color)

2021-12-23 Thread Manuel Tancoigne
https://bugs.kde.org/show_bug.cgi?id=396960

Manuel Tancoigne  changed:

   What|Removed |Added

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

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

[yakuake] [Bug 447459] New: Feature request: Ability to visually group tabs or change their background color

2021-12-23 Thread Manuel Tancoigne
https://bugs.kde.org/show_bug.cgi?id=447459

Bug ID: 447459
   Summary: Feature request: Ability to visually group tabs or
change their background color
   Product: yakuake
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: m...@experimentslabs.com
  Target Milestone: ---

Created attachment 144820
  --> https://bugs.kde.org/attachment.cgi?id=144820=edit
UI examples

SUMMARY

As a user with a lot of tabs opened,
In order to quickly jump from one tab to another
I want to have a visual way to spot tabs in the same "context"

STEPS TO REPRODUCE

I thought about a few ways to achieve this:
- Tab background color:
  1. Open tabs
  2. Right-click on a tab (or use a keyboard shortcut) to assign one of the
pre-defined contexts to the tab
  3. Result: the tab background changed
  4. A keyboard shortcut allows me to "jump" to the previous/next tab of the
same group
- Tabs groups:
  1. Open tabs
  2. Right-click on a tab (or use a keyboard shortcut) to assign one of the
pre-defined contexts to the tab
  3. Result: the tab is somewhat grouped with others of the same context
  4. A keyboard shortcut allows me to "jump" from one group to another

OBSERVED RESULT

General workflow is improved

ADDITIONAL INFORMATION

If the solution of colored backgrounds is implemented, the proposed colors
should be the ones from the KDE style colors to match the current user theme ?

I have no Qt skills to do this myself quickly, but I'll be glad to give it a
try.

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

[krita] [Bug 447445] appimage extension should be AppImage for desktop integrations

2021-12-23 Thread Justin Garrison
https://bugs.kde.org/show_bug.cgi?id=447445

--- Comment #4 from Justin Garrison  ---
(In reply to Ahab Greybeard from comment #3)
> When you download the krita appimage, you have to set Execution permissions
> in Properties and while you're doing that it would be a simple task to also
> change the name capitalisation if you want to.
> Making desktop launchers or panel launchers or menu items is a simple task.
> 
> Also, there may be people who do have AppImage tooling who don't want krita
> integrated in this way, e.g. people who download and use many different
> versions for testing purposes, sometimes on a daily basis. They would be
> inconvenienced by that.
> 
> (I've tried using the probono appimages in the past and had to stop because
> I was concerned and annoyed by how they tried to integrate with my desktop.)

I agree it would be simple but it may also cause other bugs because it is
something that is unexpected from a user who uses app image files and wants to
have them integrated into my desktop. The integration is provided from an
optional daemon and not automatic.

Not having the extension properly capitalized has already caused two tickets
(one here and one on the daemon) and I'm sure more will happen in the future.

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

[konsole] [Bug 396960] Feature Request: ability to set Konsole tab background color using escape codes (like can already be done for the terminal background color)

2021-12-23 Thread Manuel Tancoigne
https://bugs.kde.org/show_bug.cgi?id=396960

Manuel Tancoigne  changed:

   What|Removed |Added

 CC||m...@experimentslabs.com

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

[krita] [Bug 447449] I get an error message that api-ms-win-downlevel-kernel32-l2-1-0.dll is not installed

2021-12-23 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=447449

Alvin Wong  changed:

   What|Removed |Added

 CC||al...@alvinhc.com

--- Comment #1 from Alvin Wong  ---
Are you using Windows 8.1? If so, try installing UCRT:
https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c

Technical information: This may be due to `dbghelp.dll` and `dbgcore.dll` used
by DrMingw. We failed to ship `dbgcore.dll` until after beta 5 which would
explain why this didn't happen for previous betas...

Though one of the references I can find
https://monorail-prod.appspot.com/p/chromium/issues/detail?id=1021650 seems to
indicate that this is only an issue with Windows 7 and with the debugging DLLs
from 10.0.18362, while the ones we ship are from 10.0.19041. Another source
https://stackoverflow.com/questions/65858706/the-program-cant-start-because-api-ms-win-downlevel-kernel32-l2-1-0-dll-is-miss
mentions installing update
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4507456, which is also
for Windows 7.

Mind that we technically don't support Windows 7 any more.

(DrMingw is technically not required so Krita can still function when loading
of it fails, however you won't get a backtrace when there is a crash, so its
not recommended to run Krita without it.)

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

[kid3] [Bug 447441] Version 3.9.0 will not run on Big Sur

2021-12-23 Thread J.F.Lanting
https://bugs.kde.org/show_bug.cgi?id=447441

--- Comment #2 from J.F.Lanting  ---
Kid3 is a great program and I'm satisfied with 3.8.7
You should be aware that MacOS is the safest OS and that the rules
will be tightened from day by day to keep it safe.
So, I expect that you will start to sign future releases.

Besides, I hope to continue the use of Kid3
when I'm forced to switch to Silicon hardware.
Another thing that's out of our hands.
;JFL.

On 23/12/2021 19:49, Urs Fleisch wrote:
> https://bugs.kde.org/show_bug.cgi?id=447441
>
> --- Comment #1 from Urs Fleisch  ---
> Kid3 was never signed, neither 3.9.0, nor 3.8.7 nor any older release, so it
> does not make sense why it should be refused to open on macOS 11.6.2. Maybe
> this is a false positive detection of macOS.
>
> You could try the alternative version which is built with Qt 6 and requires at
> least macOS Mojave:
> https://sourceforge.net/projects/kid3/files/kid3/development/kid3-3.9.0-Darwin-Qt6-Mojave.dmg
>
> If this version is also refused when using "Open" from the finder context menu
> (assuming it still exists in mac OS 11.6.2), you could try the build from the
> KDE build factory, which is signed by KDE:
> https://binary-factory.kde.org/job/Kid3_Nightly_macos/. Get the DMG from the
> artifacts at the top of then Jenkins page.
>

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

[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash

2021-12-23 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=447450

Dmitry Kazakov  changed:

   What|Removed |Added

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

--- Comment #5 from Dmitry Kazakov  ---


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

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

[krita] [Bug 447454] Resource-related crash (?) on startup

2021-12-23 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=447454

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||jarodragon@gmail.com

--- Comment #3 from Dmitry Kazakov  ---
*** Bug 447450 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash

2021-12-23 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=447450

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #4 from Dmitry Kazakov  ---
Hi, Jennifer!

Please join the discussion by the link below and try the steps I listed there.
I'm looking into this issue right now, but haven't managed to reproduce it yet.
I can tell for sure that the problem is **not** in Rakkuri and **not** in
RM_sketch brush bundles.

https://bugs.kde.org/show_bug.cgi?id=447454#c2

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

[krita] [Bug 447454] Resource-related crash (?) on startup

2021-12-23 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=447454

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #2 from Dmitry Kazakov  ---
Hi, Cheyenne!

The problem is in loading of some .abr brushes. Please try the following:

0) Make sure Krita is closed
1) Go to `%APPDATA%\krita` folder
2) Remove file `resourcecache.sqlite`
3) Move the following bundles into the safe space outside Krita's resources
directory:
   * Sketch-and-lineart-brush-set.bindle
   * The-Cloud-Brush-set.bundle
4) Try running Krita. If Krita starts fine without these bundles, please share
them with me. You can do that privately by sending to 'dimula73 at gmail dot
com'
5) If it doesn't help, search for .abr files in `%APPDATA%\krita\brushes`
folder and move all of them into a safe space
6) Remove file `resourcecache.sqlite` again (!)
7) Try running Krita. If Krita starts fine without these files, share the files
with me (privately, if needed).
8) If nothing helps, move the entire `%APPDATA%\krita` folder into a safe
place, run Krita and add the old resources one-by-one. And share the failing
resource with me.

I tried to forcefully trigger the 'unable to decode abr format version' error
here locally, but it doesn't cause a crash. The resource is just skipped.

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

[krita] [Bug 447458] New: Docker's title prevent the docker be smaller

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447458

Bug ID: 447458
   Summary: Docker's title prevent the docker be smaller
   Product: krita
   Version: 5.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: firecloud...@gmail.com
  Target Milestone: ---

SUMMARY

Docker cannot be narrower than the docker's title width, I can make it smaller
in Krita 4.4.8. This feature is very useful on some vertical type docks like
brush history or brush size selector, it can save space for the main canvas

STEPS TO REPRODUCE
1. Add a docker(like brush history)
2. Resize it

OBSERVED RESULT
Docker cannot be very narrow

EXPECTED RESULT
Docker be very narrow, like brush history only show the icon without the name

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

[krita] [Bug 442342] Cursor brush outline not visible on first pen proximity after opening document

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=442342

spikestherac...@gmail.com changed:

   What|Removed |Added

 CC||spikestherac...@gmail.com

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

[krita] [Bug 442342] Cursor brush outline not visible on first pen proximity after opening document

2021-12-23 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=442342

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com
   Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com

--- Comment #2 from Dmitry Kazakov  ---
People report that the same problem happens when one flips Pen/Eraser ends of
the stylus.

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

[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash

2021-12-23 Thread Jennifer Reuter
https://bugs.kde.org/show_bug.cgi?id=447450

--- Comment #3 from Jennifer Reuter  ---
Certainly! Here's the DrMingW backtrace:

krita.exe caused an Access Violation at location 7FF89BB999D6 in module
libkritaresources.dll Reading from location 0008.

AddrPC   Params
7FF89BB999D6 7FF89852A330 005FEF10 005FEF60 
libkritaresources.dll!0x499d6 KisStoragePlugin::timestamp+0x6
7FF89BB78A24 151F9778 6D9C5716 005FEEC0 
libkritaresources.dll!0x28a24 KisResourceStorage::timestamp+0x14
7FF89BB66444 005FF1B0 005FF170  
libkritaresources.dll!0x16444 KisResourceCacheDb::addStorage+0x5c4
7FF89BB67D12 005FF290 0001 153A1B30 
libkritaresources.dll!0x17d12 KisResourceCacheDb::synchronizeStorage+0xa12
7FF89BB76C91 005FF390 005FF390 0030 
libkritaresources.dll!0x26c91 KisResourceLocator::synchronizeDb+0x231
7FF89BB7765F 005FF548 005FF540 7FF8A744A870 
libkritaresources.dll!0x2765f KisResourceLocator::initialize+0x1bf
7FF8992D176E 005FFB80 005FF7A0 009E 
libkritaui.dll!0x38176e KisApplication::registerResources+0xede
7FF8992D47FB 7FF898399970 7FF88EC21D30 000C 
libkritaui.dll!0x3847fb KisApplication::start+0x36b
7FF899E3546F 0001 02821AD0 000140007970 
krita.dll!0x546f krita_main+0x25bf
0001400013C7    
krita.exe!0x13c7 __tmainCRTStartup+0x247
0001400014CB    
krita.exe!0x14cb WinMainCRTStartup+0x1b
7FF8D57A7034    
KERNEL32.DLL!0x17034 BaseThreadInitThunk+0x14
7FF8D6CE2651    
ntdll.dll!0x52651 RtlUserThreadStart+0x21

00014000-000140047000 krita.exe 5.0.0.52
7FF8D6C9-7FF8D6E85000 ntdll.dll 6.2.19041.1288
7FF8D579-7FF8D584E000 KERNEL32.DLL  6.2.19041.1348
7FF8D47D-7FF8D4A98000 KERNELBASE.dll6.2.19041.1348
7FF8D19F-7FF8D1A8 apphelp.dll   6.2.19041.1320
7FF8A851-7FF8A857 AcGenral.DLL  6.2.19041.546
7FF8D692-7FF8D69BE000 msvcrt.dll7.0.19041.546
7FF8D680-7FF8D689B000 sechost.dll   6.2.19041.906
7FF8D5B6-7FF8D5C8A000 RPCRT4.dll6.2.19041.1288
7FF8D4EB-7FF8D4F05000 SHLWAPI.dll   6.2.19041.1023
7FF8D58F-7FF8D5A91000 USER32.dll6.2.19041.1202
7FF8D47A-7FF8D47C2000 win32u.dll6.2.19041.1320
7FF8D4CE-7FF8D4D0B000 GDI32.dll 6.2.19041.1202
7FF8D456-7FF8D466B000 gdi32full.dll 6.2.19041.1110
7FF8D467-7FF8D470D000 msvcp_win.dll 6.2.19041.789
7FF8D440-7FF8D450 ucrtbase.dll  6.2.19041.789
7FF8D66D-7FF8D67FA000 ole32.dll 6.2.19041.1202
7FF8D618-7FF8D64D5000 combase.dll   6.2.19041.1348
7FF8D4F9-7FF8D56CF000 SHELL32.dll   6.2.19041.1320
7FF8D4D1-7FF8D4DBC000 ADVAPI32.dll  6.2.19041.1052
7FF8D42B-7FF8D42DE000 USERENV.dll   6.2.19041.572
7FF8CF64-7FF8CF65D000 MPR.dll   6.2.19041.546
7FF8D427-7FF8D42A1000 SspiCli.dll   6.2.19041.1266
7FF8D4E2-7FF8D4E5 IMM32.DLL 6.2.19041.546
7FF899E3-7FF89A4CF000 krita.dll
7FF89CC3-7FF89CCF2000 libkritaglobal.dll
7FF89BB5-7FF89BC41000 libkritaresources.dll
6144-6145A000 libgcc_s_seh-1.dll
7FF89982-7FF899E2D000 libkritaimage.dll
6FC4-6FDA5000 libstdc++-6.dll
7FF8A743-7FF8A7493000 libKF5ConfigCore.dll
7FF89E78-7FF89E7D7000 libKF5I18n.dll
7FF898F5-7FF89981F000 libkritaui.dll
7FF8BE1E-7FF8BE1EE000 libkritaversion.dll
7FF89892-7FF898F43000 Qt5Gui.dll5.12.12.0
7FF8982F-7FF89891E000 Qt5Core.dll   5.12.12.0
7FF8D5C9-7FF8D5CFB000 WS2_32.dll6.2.19041.546
7FF897D8-7FF8982EE000 Qt5Widgets.dll5.12.12.0
7FF8A84E-7FF8A8505000 libkritaplugin.dll
7FF89E8A-7FF89E8DB000 Qt5Xml.dll5.12.12.0
7FF8BE16-7FF8BE17D000 libkritastore.dll
7FF89E74-7FF89E773000 libquazip5.dll
7FF89DE0-7FF89DE48000 Qt5Sql.dll5.12.12.0
7FF89DAA-7FF89DB36000 libKF5CoreAddons.dll
6494-64955000 libwinpthread-1.dll   1.0.0.0
7FF8BD02-7FF8BD03F000 libkritacommand.dll
7FF89D47-7FF89D4A8000 libkritametadata.dll
7FF897D1-7FF897D73000 libkritapsd.dll
7FF89CBE-7FF89CC2E000 libHalf-2_5.dll
7FF897BB-7FF897D0D000 libkritawidgetutils.dll
7FF89787-7FF897BA2000 libkritapigment.dll
7FF8976D-7FF897867000 libfftw3.dll
7FF8976B-7FF8976CF000 intl.dll  0.19.0.0

[kmymoney] [Bug 447457] New: An OFX-imported transaction assigned to "Liability" will change from Deposit to Payment (or other way round) when re-assigned to "Expense"

2021-12-23 Thread Dawid Wróbel
https://bugs.kde.org/show_bug.cgi?id=447457

Bug ID: 447457
   Summary: An OFX-imported transaction assigned to  "Liability"
will change from Deposit to Payment (or other way
round) when re-assigned to "Expense"
   Product: kmymoney
   Version: 5.1.2
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: m...@dawidwrobel.com
  Target Milestone: ---

SUMMARY

A transaction assigned to "Liability" will change from Deposit to Payment (or
other way round) when re-assigned to "Expense" or "Asset". This only happens
once after the initial import of the transaction.

STEPS TO REPRODUCE
1. Import a transaction using OFX (using Direct Connect here, need to check if
importing from OFX file applies as well)
2. Re-assign the category from the originally assigned to one of the opposing
type (i.e. if it was Liability, assign to Asset or Expense and vice-versa).


OBSERVED RESULT
Notice the transaction changes from Payment to Deposit, or the other way round.
Re-assigning the category back to the previous one at this point does nothing.

EXPECTED RESULT
Nothing should change except the category itself when re-assigning the
transaction.

ADDITIONAL INFORMATION
This is most likely caused by some inconsistency in how the splits looks like
in the imported transaction.

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

[umbrello] [Bug 447453] umbrello-mingw64-2.32.0-126.1 when installed on Microsoft Surface Pro 7 running Windows 11 fails to run after installation

2021-12-23 Thread Mike Davis
https://bugs.kde.org/show_bug.cgi?id=447453

Mike Davis  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Mike Davis  ---
Failure of the program to start as described below has been overcome by
replacing the file libcrypto-10.dll which was installed by the package with a
more recent 64bit designated file: libcrypto-1_1-x64.dll.  While this corrects
the problem on this installation, the current download distribution still
contains the offending dll.

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

[krita] [Bug 447445] appimage extension should be AppImage for desktop integrations

2021-12-23 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=447445

Ahab Greybeard  changed:

   What|Removed |Added

 CC||ahab.greybe...@hotmail.co.u
   ||k

--- Comment #3 from Ahab Greybeard  ---
When you download the krita appimage, you have to set Execution permissions in
Properties and while you're doing that it would be a simple task to also change
the name capitalisation if you want to.
Making desktop launchers or panel launchers or menu items is a simple task.

Also, there may be people who do have AppImage tooling who don't want krita
integrated in this way, e.g. people who download and use many different
versions for testing purposes, sometimes on a daily basis. They would be
inconvenienced by that.

(I've tried using the probono appimages in the past and had to stop because I
was concerned and annoyed by how they tried to integrate with my desktop.)

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

[plasmashell] [Bug 444742] Plasma crash right after login

2021-12-23 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=444742

--- Comment #9 from Raman Gupta  ---
(In reply to burneddi from comment #7)
> at least on Fedora the easiest way to restart Plasmashell is with "systemctl 
> --user restart plasma-plasmashell"

On Fedora, is this a new approach to running Plasmashell? Interestingly, if I
run plasmashell this way, as opposed to just restarting it the way I always
used to (`kstart plasmashell &> /dev/null`) it no longer crashes on monitor
wakeup.

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

[Breeze] [Bug 447433] Some Icons are hard to see (Geany and Application menu)

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447433

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 CC||noaha...@gmail.com

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

[Breeze] [Bug 447433] Some Icons are hard to see (Geany and Application menu)

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447433

--- Comment #3 from Nate Graham  ---
You did! And I completely failed to read it! My apologies.

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

[frameworks-kirigami] [Bug 438260] KRecorder is located at the "lost & found" folder in the application launcher

2021-12-23 Thread Felipe Kinoshita
https://bugs.kde.org/show_bug.cgi?id=438260

Felipe Kinoshita  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
 CC||kinof...@gmail.com

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

[ksmserver] [Bug 432643] kdeconnect slowing down system shutdown

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=432643

Nate Graham  changed:

   What|Removed |Added

Product|kdeconnect  |ksmserver
  Component|common  |general
 CC||plasma-b...@kde.org
   Assignee|albertv...@gmail.com|k...@davidedmundson.co.uk

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

[dolphin] [Bug 416389] When in "All tags" section, information panel shows a dot below its icon instead of "All tags" text

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=416389

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||22.04

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

[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=432643

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.24

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

[systemsettings] [Bug 368305] Implement Samba printer browsing

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=368305

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||22.04

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

[kwin] [Bug 445860] Wayland for Nvidia works for Gnome not KDE

2021-12-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=445860

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[systemsettings] [Bug 445847] Crash opening "Appearance" in System Settings

2021-12-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=445847

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kwin] [Bug 445844] When an application is moved to 2nd display (not the main display), and user want to expand it to full screen, the bar with close/expand-to-full-screen/minimize vanishes. At some p

2021-12-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=445844

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[Planet KDE] [Bug 418703] Black screen after standby and sometimes after a boot.

2021-12-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418703

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[Discover] [Bug 446483] unexpected crash while cancelling downloading apps

2021-12-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=446483

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

[lattedock] [Bug 441885] Latte dock crashing when changing Plasma appearance

2021-12-23 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=441885

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

[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash

2021-12-23 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=447450

--- Comment #2 from Alvin Wong  ---
If you can manage to, can you please also try running "C:\Program Files\Krita
(x64)\bin\krita.com", and copy (or take a screenshot) of what the black console
window says when it crashes?

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

[krita] [Bug 447454] Resource-related crash (?) on startup

2021-12-23 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=447454

Alvin Wong  changed:

   What|Removed |Added

Summary|Hi so I am currently using  |Resource-related crash (?)
   |windows 11  and I was   |on startup
   |previously using krita 4, I |
   |previously tried krita 5|
   |beta and the same issue |
   |occurred. the loading   |
   |screen would say loading|
   |resources but then after a  |
   |minute it would just exit   |
   |out.  I really don't know   |
   |wha |
 CC||al...@alvinhc.com

--- Comment #1 from Alvin Wong  ---
Hi Cheyenne, if you may, please try to find the backtrace by following
https://docs.krita.org/en/reference_manual/dr_minw_debugger.html?highlight=backtrace#getting-a-backtrace

---

Note: the original subject was:

> Hi so I am currently using windows 11  and I was previously using krita 4,
> I previously tried krita 5 beta and the same issue occurred. the loading
> screen would say loading resources but then after a minute it would just
> exit out.  I really don't know wha

(Yes it was truncated as-is.)

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

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

2021-12-23 Thread Josesk Volpe
https://bugs.kde.org/show_bug.cgi?id=383555

Josesk Volpe  changed:

   What|Removed |Added

 CC||joseskvo...@gmail.com

--- Comment #17 from Josesk Volpe  ---
It happens to me on Wayland
I don't have this issue (not displaying on secondary monitor) on X11

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

[kwin] [Bug 446525] Meta key to open appmenu stops working after wakeup from hibernation

2021-12-23 Thread Sayantan Santra
https://bugs.kde.org/show_bug.cgi?id=446525

Sayantan Santra  changed:

   What|Removed |Added

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

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

[kwin] [Bug 446525] Meta key to open appmenu stops working after wakeup from hibernation

2021-12-23 Thread Sayantan Santra
https://bugs.kde.org/show_bug.cgi?id=446525

Sayantan Santra  changed:

   What|Removed |Added

Product|lattedock   |kwin
  Component|application |general
Version|0.10.4  |5.23.4
   Assignee|mvourla...@gmail.com|kwin-bugs-n...@kde.org

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

[yakuake] [Bug 447456] New: Wayland: Drop-down animation not working

2021-12-23 Thread Josesk Volpe
https://bugs.kde.org/show_bug.cgi?id=447456

Bug ID: 447456
   Summary: Wayland: Drop-down animation not working
   Product: yakuake
   Version: 21.12.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: joseskvo...@gmail.com
  Target Milestone: ---

SUMMARY
Drop-down animation for Yakuake is not working on Wayland, only on X11


STEPS TO REPRODUCE
1. Start your graphical interface on Wayland (I'm using KDE Plasma)
2. Open Yakuake

OBSERVED RESULT
Yakuake is displaying with growing animation

EXPECTED RESULT
Yakuake should display with a drop-down animation

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.10.85-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

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

[konsole] [Bug 447455] New: Blocks processes producing too much output when window not in active tty

2021-12-23 Thread Daniel Dawson
https://bugs.kde.org/show_bug.cgi?id=447455

Bug ID: 447455
   Summary: Blocks processes producing too much output when window
not in active tty
   Product: konsole
   Version: 21.12.0
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: danielcdaw...@gmail.com
  Target Milestone: ---

SUMMARY
If I switch to a different tty from the one a Konsole window is on, I find that
any child processes producing output get blocked after a certain amount is
produced.

STEPS TO REPRODUCE
1. Login on a virtual console (e.g. tty1).
2. Prepare a way to get output from a process. The way I did this was:
  $ mknod /tmp/test.pipe p
  $ cat /tmp/test.pipe
3. Start a graphical session, or switch back to one.
4. Start a terminal emulator, such as Konsole, and do something in it that both
produces output on stdout, and sends it to the VC:
  $ for ((i=0;;i++)); do echo $i; sleep 0.005; done | tee /tmp/test.pipe  #
sleep is optional, but recommended.
5. Switch back to the VC, and watch the output.

OBSERVED RESULT
When using Konsole, after a couple thousand lines, the output pauses. Only once
I switch back to the graphical session, does output continue. I tried this also
with xterm and LXTerminal (since they happen to be installed), and this
behavior does not occur with them (unless their buffers are just really huge).

EXPECTED RESULT
Not being in the active tty should, I believe, not affect child processes
simply because of their terminal output. This is a problem if running an
application under Konsole that's doing something important while writing to
stderr/stdout.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.0-gentoo (64-bit) [custom config]
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
A workaround seems to be to run things that need to avoid being blocked under
something like screen or tmux, since they take over as the controlling
terminal, and keep running even if their front-end disappears.

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

[krita] [Bug 447454] New: Hi so I am currently using windows 11 and I was previously using krita 4, I previously tried krita 5 beta and the same issue occurred. the loading screen would say loading re

2021-12-23 Thread Cheyenne
https://bugs.kde.org/show_bug.cgi?id=447454

Bug ID: 447454
   Summary: Hi so I am currently using windows 11  and I was
previously using krita 4, I previously tried krita 5
beta and the same issue occurred. the loading screen
would say loading resources but then after a minute it
would just exit out.  I really don't know wha
   Product: krita
   Version: 5.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: cheyenneyoung...@gmail.com
  Target Milestone: ---

Created attachment 144819
  --> https://bugs.kde.org/attachment.cgi?id=144819=edit
this is the ms dos application everytime I start up, I notice it's about my
brushes being broken but I can't remove them if I can't open krita

SUMMARY
***   I would try to send a backtrace crash report but I really don't
understand how? 
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. have windows 11
2. start up krita
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[Plasma SDK] [Bug 447452] [plasma-interactiveconsole] Ctrl+E to Execute is an ambiguous shortcut

2021-12-23 Thread Chris Holland
https://bugs.kde.org/show_bug.cgi?id=447452

--- Comment #1 from Chris Holland  ---
Looks like Ctrl+B is bookmark, not breakpoint.

https://github.com/KDE/ktexteditor/blob/92cab6563e46db4260c89b7b12c87237369f857c/src/view/kateview.cpp#L518

a = ac->addAction(QStringLiteral("Previous Editing Line"));
a->setText(i18n("Go to previous editing line"));
ac->setDefaultShortcut(a, QKeySequence(Qt::CTRL + Qt::Key_E));

a = ac->addAction(QStringLiteral("Next Editing Line"));
a->setText(i18n("Go to next editing line"));
ac->setDefaultShortcut(a, QKeySequence(Qt::CTRL + Qt::SHIFT +
Qt::Key_E));

https://github.com/KDE/ktexteditor/blob/da6275179c896613272bc4d70e9dc41943c30f5b/src/utils/katebookmarks.cpp#L48

m_bookmarkToggle = new KToggleAction(i18n("Set "), this);
ac->addAction(QStringLiteral("bookmarks_toggle"), m_bookmarkToggle);
   
m_bookmarkToggle->setIcon(QIcon::fromTheme(QStringLiteral("bookmark-new")));
ac->setDefaultShortcut(m_bookmarkToggle, Qt::CTRL + Qt::Key_B);
m_bookmarkToggle->setWhatsThis(i18n("If a line has no bookmark then add
one, otherwise remove it."));
connect(m_bookmarkToggle, ::triggered, this,
::toggleBookmark);

https://github.com/KDE/ktexteditor/blob/92cab6563e46db4260c89b7b12c87237369f857c/src/view/kateview.cpp#L690

a = m_toggleBlockSelection = new KToggleAction(i18n("Bl Selection
Mode"), this);
ac->addAction(QStringLiteral("set_verticalSelect"), a);
ac->setDefaultShortcut(a, QKeySequence(Qt::CTRL + Qt::SHIFT + Qt::Key_B));
a->setWhatsThis(i18n("This command allows switching between the normal
(line based) selection mode and the block selection mode."));
connect(a, ::triggered, this,
::ViewPrivate::toggleBlockSelection);

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

[krita] [Bug 438784] Panning and zooming bug in Krita

2021-12-23 Thread Protoniv
https://bugs.kde.org/show_bug.cgi?id=438784

--- Comment #10 from Protoniv  ---
(In reply to Protoniv from comment #9)
> I found this bug only happened when I enable Windows Ink, using mouse or 
> WinTab the bug will not occurr to me.
After some more test, the Windows Ink is actually from my tablet driver "Use
Digital Ink" (XP Pen), if "Use Digital Ink" in tablet driver is off then
Windows Ink/WinTab setting in Krita won't occur the bug, at least for me.

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

[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps

2021-12-23 Thread phrxmd
https://bugs.kde.org/show_bug.cgi?id=424485

phrxmd  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[umbrello] [Bug 447453] New: umbrello-mingw64-2.32.0-126.1 when installed on Microsoft Surface Pro 7 running Windows 11 fails to run after installation

2021-12-23 Thread Mike Davis
https://bugs.kde.org/show_bug.cgi?id=447453

Bug ID: 447453
   Summary: umbrello-mingw64-2.32.0-126.1 when installed on
Microsoft Surface Pro 7 running Windows 11 fails to
run after installation
   Product: umbrello
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: installer/packages
  Assignee: umbrello-de...@kde.org
  Reporter: mlda...@chaparralwest.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
***
After completed installation of umbrello-mingw64-2.32.0-126.1 on Microsoft
Surface Pro 7 running Windows 11 fails on startup.  The following system error
is found in the log:
Faulting application name: umbrello.exe, version: 0.0.0.0, time stamp:
0x
Faulting module name: libcrypto-10.dll, version: 1.0.2.8, time stamp:
0x
Exception code: 0xc005
Fault offset: 0x00010f23
Faulting process id: 0x4398
Faulting application start time: 0x01d7f8656745311d
Faulting application path: C:\Program Files\umbrello\bin\umbrello.exe
Faulting module path: C:\Program Files\umbrello\bin\libcrypto-10.dll
Report Id: f5283c6b-e72c-4f16-bfc2-954ec734b64f
Faulting package full name: 
Faulting package-relative application ID: 

STEPS TO REPRODUCE
1.  Install the program as noted.
2. 
3. 

OBSERVED RESULT
Fails to start and error log as shown above occurs.

EXPECTED RESULT


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

ADDITIONAL INFORMATION
Note that the portable version umbrello-mingw64-2.32.0-126.1-portable incurs
the same error.  Also, note that the 32bit version of the same build installs
and runs properly.  Also the 64bit version installs and works properly on a
Microsoft Surface Book 2 running the same version of Windows 11.

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

[Breeze] [Bug 447433] Some Icons are hard to see (Geany and Application menu)

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447433

--- Comment #2 from pqwoerituytruei...@gmail.com ---
Did I not include that under steps to reproduce?

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

[k3b] [Bug 446853] If title of DVD has too many spaces at end, the .iso extension is dropped when saving the copy

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=446853

--- Comment #11 from parkerjbar...@yahoo.com ---
(In reply to Albert Astals Cid from comment #10)
> Unfortunately still can not reproduce.
> 
> See https://i.imgur.com/RKnioct.mp4
> 
> I'll leave the issue open in case someone else can reproduce or we figure
> out what I am doing different than you that may be causing the issue

It looks like you cancelled the copying before it was done, and one can't see
the file that you're saving, whether it has an extension or not.  The DVD that
in this issue is not encrypted.  Perhaps if someone were to author a dvd,
unencrypted, but the title has 22 spaces at the end of the title, maybe that
would cause this issue that I'm describing.

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

[kwin] [Bug 443990] Kwin memory leak

2021-12-23 Thread dreaperxz
https://bugs.kde.org/show_bug.cgi?id=443990

dreape...@gmail.com  changed:

   What|Removed |Added

 CC||dreape...@gmail.com
   Platform|Archlinux Packages  |Neon Packages
  Component|compositing |aurorae
Version|5.23.0  |5.23.4

--- Comment #22 from dreape...@gmail.com  ---
When my custom themes are applied, kwin jumps up a few megabytes at a time
whenever a window is opened and closed again. So kwin keeps consuming more ram
until I have to kill it and start again. Is there a fix for this or something I
can fix with my themes?

These are my themes:

https://www.pling.com/p/1406638

https://www.pling.com/p/1574340

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

[krita] [Bug 447450] Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash

2021-12-23 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=447450

Alvin Wong  changed:

   What|Removed |Added

 CC||al...@alvinhc.com

--- Comment #1 from Alvin Wong  ---
Do you have a DrMingw backtrace? Please refer to
https://docs.krita.org/en/reference_manual/dr_minw_debugger.html?highlight=backtrace#getting-a-backtrace
on finding it.

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #192 from sombrag...@sombragris.org ---
Nate, I really appreciate showing up and answering this issue, but really, this
state of things is simply not acceptable. I am not a developer, I don't know
how to handle pointers and structs and such, but this stuff should REALLY be
fixed asap. I would urge you to get some KDE dev to fix this somewhat, be it as
an ugly hack or by a harmonious refactoring. I do not care, really. What I care
is that this is a bug reported over SEVEN YEARS ago, opened and biting over two
Plasma full major version releases and two Qt versions, and is still there,
still confusing for inexperienced users.

Or, at least in the next (minor) release, under a document identified as "Known
Issues", document the issue and any workaround if possible. That, at the very
least.

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

[gwenview] [Bug 420141] Gwenview acts slow and leaks memory when zooming/panning images without an alpha channel when display color space conversion is enabled

2021-12-23 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=420141

--- Comment #7 from Colin Griffith  ---
I'm still having this problem. It's likely not seen by many people because most
people don't profile/calibrate their displays with a colorimeter, so don't have
display profiles installed (other than standard sRGB and the like).

My guess is that however Gwenview interacts with LCMS2 is probably to blame.

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

[Plasma SDK] [Bug 447452] New: [plasma-interactiveconsole] Ctrl+E to Execute is an ambiguous shortcut

2021-12-23 Thread Chris Holland
https://bugs.kde.org/show_bug.cgi?id=447452

Bug ID: 447452
   Summary: [plasma-interactiveconsole] Ctrl+E to Execute is an
ambiguous shortcut
   Product: Plasma SDK
   Version: 5.23.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: zrenf...@gmail.com
CC: antonis.tsiapalio...@kde.org
  Target Milestone: ---

This is technically a bug for plasma-workspace, since that's where
plasma-interactiveconsole is.

*
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1293#note_363801
*
https://invent.kde.org/plasma/plasma-workspace/-/tree/master/interactiveconsole
*
https://invent.kde.org/plasma/plasma-workspace/-/blob/master/interactiveconsole/interactiveconsole.cpp#L188

Looks like it's bound to Ctrl+E, but pressing that shows that the shortcut is
Ambiguous. Looks like you need to not be focusing the code TextArea (select
text in the output TextArea) for Ctrl+E to work, which defeats the purpose of
the shortcut. Also, there is no settings menu (probably meant for Kate).

Ctrl+B seems to be bound to... Toggle Breakpoint or something? It turns the bg
blue on the line with the cursor.

We should probably keep `Alt+E` generated by the i18n text. So we should be
using something like:

auto shortcuts = QList() << m_executeAction->shortcut() <<
(Qt::CTRL | Qt::Key_E) << (Qt::CTRL | Qt::Key_B);
m_executeAction->setShortcuts(shortcuts);

We'll also need to figure out how to disable the default KTextEditor Ctrl+B /
Ctrl+E actions so they're not ambiguous.

* https://doc.qt.io/qt-5/qaction.html#shortcuts

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

[gwenview] [Bug 420141] Gwenview acts slow and leaks memory when zooming/panning images without an alpha channel when display color space conversion is enabled

2021-12-23 Thread Colin Griffith
https://bugs.kde.org/show_bug.cgi?id=420141

Colin Griffith  changed:

   What|Removed |Added

 CC||tyna...@gmail.com
Version|20.12.2 |21.12.0

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

[kwin] [Bug 447451] New: Kicker's sub-menus cannot be navigated by keyboard in Wayland

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447451

Bug ID: 447451
   Summary: Kicker's sub-menus cannot be navigated by keyboard in
Wayland
   Product: kwin
   Version: 5.23.4
  Platform: Slackware Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sombrag...@sombragris.org
  Target Milestone: ---

When usig the hierarchical kicker start menu with sub menus, the menu can be
navigated only in the first level using the keyboard (e.g., keyboard cursor
arrow keys). Entering into a sublevel and choosing a sublevel item is not
possible.

STEPS TO REPRODUCE
1. Boot Plasma with Wayland. Use the traditional Kicker Start Menu with
cascading/submenus.
2. Open menu with Alt+F1 or whatever shortcut you have.
3. Choose any item, for example "Power / Session"
4. Try to select one of the options, such as "Shut Down" by using the keyboard
navigation keys.

OBSERVED RESULT
The user is forced to use the mouse pointer device to select any item in any
sub-menus

EXPECTED RESULT
The user should be able to select any menu item in any category by using
regular keyboard navigation keys and activating any of these menu items by
using the Enter key.

This is the case in X11, where the start menu behaves as expected.

SYSTEM INFORMATION
Operating System: Slackware 15.0
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3
Kernel Version: 5.15.11 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
As I said, the submenus behave normally under X11.

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

[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408468

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||21.12.1

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

[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland appears under top panel at start

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=408468

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util
   |ities/yakuake/commit/d18320 |ities/yakuake/commit/c92e35
   |fd3f153315d5020b29f241bfd07 |8784cfc76126d16b0b26d33ddc1
   |11863f4 |06ffd92

--- Comment #43 from Nate Graham  ---
Git commit c92e358784cfc76126d16b0b26d33ddc106ffd92 by Nate Graham, on behalf
of Tranter Madi.
Committed on 24/12/2021 at 00:28.
Pushed by ngraham into branch 'cherry-pick-d18320fd'.

Make sure position is always set in wayland


(cherry picked from commit d18320fd3f153315d5020b29f241bfd0711863f4)

M  +1-0app/mainwindow.cpp

https://invent.kde.org/utilities/yakuake/commit/c92e358784cfc76126d16b0b26d33ddc106ffd92

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

[krita] [Bug 447450] New: Unable to open Krita 5.0 on Windows 10 - libkritaresrouces.dll crash

2021-12-23 Thread jarodragon
https://bugs.kde.org/show_bug.cgi?id=447450

Bug ID: 447450
   Summary: Unable to open Krita 5.0 on Windows 10 -
libkritaresrouces.dll crash
   Product: krita
   Version: 5.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: jarodragon@gmail.com
  Target Milestone: ---

SUMMARY
Krita 5.0.0 on Windows 10 won't start at all; it will show the image loader,
'adding resource types', then close.

STEPS TO REPRODUCE
1. Start Krita
2. Image loader shows on screen, sometimes 1st screen, sometimes 2nd; shows
'adding resource types'.
3. Closes, Krita doesn't start.

OBSERVED RESULT
Here's the Event Viewer log after crash:

Event ID: 1000

Faulting application name: krita.exe, version: 5.0.0.52, time stamp: 0x
Faulting module name: libkritaresources.dll, version: 0.0.0.0, time stamp:
0x
Exception code: 0xc005
Fault offset: 0x000499d6
Faulting process ID: 0x27e0
Faulting application start time: 0x01d7f858716f5f4d
Faulting application path: C:\Program Files\Krita (x64)\bin\krita.exe
Faulting module path: C:\Program Files\Krita (x64)\bin\libkritaresources.dll
Report ID: 2ad89dce-0ce5-4c84-9584-8f3b72e49851
Faulting package full name: 
Faulting package-relative application ID: 


EXPECTED RESULT
Krita opens upon clicking the executable.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Home 20H2
Processor: AND Ryzen 5 2600 Six-core Processor
RAM: 16GB
System type: 64-bit

ADDITIONAL INFORMATION
I installed 5.0.0 two different ways; once on top of the original 4.4.8
installation, and once a complete uninstall, restart, reinstall. Same result.
Did not have this issue with any installations of previous versions.
Reinstalling 4.4.8 runs completely fine.

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

[Breeze] [Bug 447433] Some Icons are hard to see (Geany and Application menu)

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447433

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
What color scheme are you using and what Plasma theme are you using?

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

[Breeze] [Bug 447431] Add icon for audio-card-bluetooth

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=447431

Nate Graham  changed:

   What|Removed |Added

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

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on Intel RAID/NTFS volume scan

2021-12-23 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=447248

--- Comment #9 from Andrius Štikonas  ---
This should at least fix lag of several minutes.

But I'm not sure what it does to RAID size. Could you test this commit?

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

[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on Intel RAID/NTFS volume scan

2021-12-23 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=447248

Andrius Štikonas  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/syst
   ||em/kpmcore/commit/a5bdd5a4e
   ||b44607fed3b0318ee64cc4f15ab
   ||b122
 Resolution|--- |FIXED

--- Comment #8 from Andrius Štikonas  ---
Git commit a5bdd5a4eb44607fed3b0318ee64cc4f15abb122 by Andrius Štikonas.
Committed on 24/12/2021 at 00:03.
Pushed by stikonas into branch 'master'.

Switch to ntfsinfo to read NTFS usage.

M  +19   -9src/fs/ntfs.cpp
M  +1-0src/util/externalcommand_whitelist.h

https://invent.kde.org/system/kpmcore/commit/a5bdd5a4eb44607fed3b0318ee64cc4f15abb122

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

[krita] [Bug 447046] Delay when selecting a brush preset and actually having it active

2021-12-23 Thread Larissa
https://bugs.kde.org/show_bug.cgi?id=447046

--- Comment #8 from Larissa  ---
(In reply to Dmitry Kazakov from comment #6)
> Hi, Larissa!
> 
> Can you clarify a bit, does the delay happen only when you select a brush
> for the first time in Krita session or every time when you select it? From
> your note about '/' shortcut, I have a feeling like it should happen only
> for the first click on the brush

Hello, Dmitry!

I decided to make some more tests with 5.0 release.
Using the same resource folder I used for the previous betas I get constant
delay no matter how many times I select the brush. I also have experience the
delay in loading the canvas and krita stopped responding for some seconds as I
reported in bug 447048. 
Even with a fresh resource folder, importing bundles have the exact same
behavior of constant lag, no matter how many times i select the brush.

Testing with a fresh resource folder:
- Without any additional bundles -> change between presets is instant, canvas
loading is also instant. (using 3000x3000 300ppi canvas for all these tests)

- Adding FizzyFlower Essentials and Concept & Illustration 1.2 bundles, without
restarting krita -> 
Things get a bit weird, at first seems like there is no lag when i try to
change brushes, however if i keep changing seems like the lag starts appearing,
after around 5 switches in sequence the lag becomes very noticiable.

- Adding FizzyFlower Essentials and Concept & Illustration 1.2 bundles, after
restarting krita -> 
Same behavior as before  but once it starts lagging the lag is not as much

- Adding the files(brush and presets) for both bundles, instead of importing
the bundle -> there is a bit of lag sometimes but is greatly reduced.

When adding more bundles even the krita 4 bundle starts lagging. Honestly the
more I test the more confused I get cause the behavior is inconsistent,
sometimes all brush changes lag other times just changing to brushes in the
bundles lag.

Seems like the bundle files create a bit more lag than having the separate
files in the folders. The only thing i could conclude so far is that importing
all bundles as preset and brush files seem to work as a workaround up to a
certain point, as too many will get to the same slowdown.

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

[krita] [Bug 445561] Krita 5 16bit integer colorspace canvas rendering is broken on M1

2021-12-23 Thread Gerhard Hellmann
https://bugs.kde.org/show_bug.cgi?id=445561

--- Comment #19 from Gerhard Hellmann  ---
The problem still seems to be around in the final 5.0 version published just
now. I still have the problem with the output which means I can't use 16bit
integer, which is unfortunately the depth I am using all the time.
Any way to work around this?!

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

[krita] [Bug 445561] Krita 5 16bit integer colorspace canvas rendering is broken on M1

2021-12-23 Thread Gerhard Hellmann
https://bugs.kde.org/show_bug.cgi?id=445561

Gerhard Hellmann  changed:

   What|Removed |Added

 CC||je...@jerri.de

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

[Falkon] [Bug 447448] PDF content can not be zoomed in or out

2021-12-23 Thread Graham Perrin
https://bugs.kde.org/show_bug.cgi?id=447448

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

> – disable the feature.

>From : 

> … I don't imagine any modern extension using the Pepper API, …

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

[krita] [Bug 447449] New: I get an error message that api-ms-win-downlevel-kernel32-l2-1-0.dll is not installed

2021-12-23 Thread cesar
https://bugs.kde.org/show_bug.cgi?id=447449

Bug ID: 447449
   Summary: I get an error message that
api-ms-win-downlevel-kernel32-l2-1-0.dll is not
installed
   Product: krita
   Version: 5.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: cesarnavaarteaga...@gmail.com
  Target Milestone: ---

I downloaded version 5.0 of krita but when I open it I see that I am missing
the file I api-ms-win-downlevel-kernel32-l2-1-0.dll but when I close the window
the program opens normally, there is really an error With the program? I cannot
update the file because other programs do not work, this did not happen to me
with previous versions or with betas 5.0

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

[Falkon] [Bug 447448] PDF content can not be zoomed in or out

2021-12-23 Thread Graham Perrin
https://bugs.kde.org/show_bug.cgi?id=447448

--- Comment #1 from Graham Perrin  ---
Workaround: 

1. Preferences
2. Browsing
3. ☐ Allow Pepper Plugins (Flash plugin)

– disable the feature.

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

[Falkon] [Bug 447448] New: PDF content can not be zoomed in or out

2021-12-23 Thread Graham Perrin
https://bugs.kde.org/show_bug.cgi?id=447448

Bug ID: 447448
   Summary: PDF content can not be zoomed in or out
   Product: Falkon
   Version: 3.1.0
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: grahamper...@gmail.com
  Target Milestone: ---

SUMMARY

Zooming has no effect. 

STEPS TO REPRODUCE

1. View menu
2. Zoom In
3. Zoom Out

OBSERVED RESULT

2. scroll up a fraction, but not to the previous page
3. scroll down a fraction, but not to the next page

EXPECTED RESULT

2. zoom
3. zoom

SOFTWARE/OS VERSIONS

% pkg info -x falkon
falkon-3.1.0_1
% uname -aKU
FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #116
main-n251146-d109559ddbf: Mon Nov 29 14:34:59 GMT 2021
root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
 amd64 1400043 1400043
% 

Operating System: FreeBSD 14.0
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 14.0-CURRENT (64-bit)
Graphics Platform: X11
Memory: 15.9 GiB of RAM
Graphics Processor: AMD TURKS

ADDITIONAL INFORMATION

Reported at .

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

[k3b] [Bug 446853] If title of DVD has too many spaces at end, the .iso extension is dropped when saving the copy

2021-12-23 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=446853

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #10 from Albert Astals Cid  ---
Unfortunately still can not reproduce.

See https://i.imgur.com/RKnioct.mp4

I'll leave the issue open in case someone else can reproduce or we figure out
what I am doing different than you that may be causing the issue

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

[krita] [Bug 447445] appimage extension should be AppImage for desktop integrations

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447445

--- Comment #2 from tomtomtomreportin...@gmail.com ---
Related issue: https://github.com/probonopd/go-appimage/issues/157

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

[digikam] [Bug 447408] Crash when loading metadata for specially-crafted JPEG images

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447408

--- Comment #3 from saaman1...@gmail.com ---
Maik,

Thank you for the prompt response and fix. Do you think it would make more
sense, though, to introduce checks like "if (component < (*it).count())"
instead of "if ((*it).count())" since component is a parameter that can be set
to values other than 0? (I'm not sure there are currently any usages that
specify other values, but this seems like a sensible precaution to avoid future
problems.)

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

[krita] [Bug 447445] appimage extension should be AppImage for desktop integrations

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447445

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 CC||tomtomtomreportingin@gmail.
   ||com

--- Comment #1 from tomtomtomreportin...@gmail.com ---
To be honest, I would consider this more of a problem of the program you linked
than a problem of Krita... but I'm not a dev and this is likely a trivial fix.

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #191 from Nate Graham  ---
Or better yet, submit everything upstream to QLocale. That would be even
better. IIRC that was what was supposed to happen during the Qt5 timeframe, but
it never happened, so we wound up with a crippled QLocale and lost the nice
user-friendly KLocale features.

In any similar situation in the future, I would like to extract a guarantee
that the code is submitted and accepted upstream FIRST before people port stuff
away from it! :)

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

2021-12-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #190 from Nate Graham  ---
Yeah, if anyone wants to bring back KLocale and port everything to it, that
would be a path forward.

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

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

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

   What|Removed |Added

   Version Fixed In||7.5.0

--- Comment #10 from caulier.gil...@gmail.com ---
Next 7.5.0 pre-release AppImage bundle will be published tomorrow morning at
usual place : 

https://files.kde.org/digikam/

Gilles Caulier

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

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

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

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/commit/32bfb8a
   ||28bdb968b2ac02ccc3899282f02
   ||957cc1
 Status|REOPENED|RESOLVED

--- Comment #9 from caulier.gil...@gmail.com ---
Git commit 32bfb8a28bdb968b2ac02ccc3899282f02957cc1 by Gilles Caulier.
Committed on 23/12/2021 at 22:07.
Pushed by cgilles into branch 'master'.

Fix new ImageMagick modules path to use at runtime with AppImage
FIXED: 7.5.0

M  +2-2project/bundles/appimage/data/AppRun

https://invent.kde.org/graphics/digikam/commit/32bfb8a28bdb968b2ac02ccc3899282f02957cc1

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

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

--- Comment #8 from caulier.gil...@gmail.com ---
This is the ImageMagick coders from 7.3.0 AppImage :

[gilles@localhost coders]$ pwd
/tmp/.mount_digiKafJtyFs/usr/lib/modules-Q16/coders

[gilles@localhost coders]$ ll
total 3149
-rwxr-xr-x 1 root root  15424 Jul 10 20:59 aai.so*
-rwxr-xr-x 1 root root  15456 Jul 10 20:59 art.so*
-rwxr-xr-x 1 root root  15440 Jul 10 20:59 avs.so*
-rwxr-xr-x 1 root root  23712 Jul 10 20:59 bgr.so*
-rwxr-xr-x 1 root root  40272 Jul 10 20:59 bmp.so*
-rwxr-xr-x 1 root root  11176 Jul 10 20:59 braille.so*
-rwxr-xr-x 1 root root  15448 Jul 10 20:59 cals.so*
-rwxr-xr-x 1 root root  15376 Jul 10 20:59 caption.so*
-rwxr-xr-x 1 root root  23888 Jul 10 20:59 cin.so*
-rwxr-xr-x 1 root root  11160 Jul 10 20:59 cip.so*
-rwxr-xr-x 1 root root  11232 Jul 10 20:59 clip.so*
-rwxr-xr-x 1 root root  27840 Jul 10 20:59 cmyk.so*
-rwxr-xr-x 1 root root  19584 Jul 10 20:59 cut.so*
-rwxr-xr-x 1 root root 265792 Jul 10 20:59 dcm.so*
-rwxr-xr-x 1 root root  40464 Jul 10 20:59 dds.so*
-rwxr-xr-x 1 root root  11208 Jul 10 20:59 debug.so*
-rwxr-xr-x 1 root root  23792 Jul 10 20:59 dib.so*
-rwxr-xr-x 1 root root  15408 Jul 10 20:59 dng.so*
-rwxr-xr-x 1 root root  11264 Jul 10 20:59 dot.so*
-rwxr-xr-x 1 root root  36304 Jul 10 20:59 dpx.so*
-rwxr-xr-x 1 root root  15456 Jul 10 20:59 ept.so*
-rwxr-xr-x 1 root root  15584 Jul 10 20:59 exr.so*
-rwxr-xr-x 1 root root  15480 Jul 10 20:59 fax.so*
-rwxr-xr-x 1 root root  23832 Jul 10 20:59 fits.so*
-rwxr-xr-x 1 root root  32176 Jul 10 20:59 gif.so*
-rwxr-xr-x 1 root root  11248 Jul 10 20:59 gradient.so*
-rwxr-xr-x 1 root root  19616 Jul 10 20:59 gray.so*
-rwxr-xr-x 1 root root  11168 Jul 10 20:59 hald.so*
-rwxr-xr-x 1 root root  19648 Jul 10 20:59 hdr.so*
-rwxr-xr-x 1 root root  15472 Jul 10 20:59 histogram.so*
-rwxr-xr-x 1 root root  11280 Jul 10 20:59 hrz.so*
-rwxr-xr-x 1 root root  15368 Jul 10 20:59 html.so*
-rwxr-xr-x 1 root root  23848 Jul 10 20:59 icon.so*
-rwxr-xr-x 1 root root  11184 Jul 10 20:59 info.so*
-rwxr-xr-x 1 root root  11328 Jul 10 20:59 inline.so*
-rwxr-xr-x 1 root root  15536 Jul 10 20:59 ipl.so*
-rwxr-xr-x 1 root root  15560 Jul 10 20:59 jbig.so*
-rwxr-xr-x 1 root root  11296 Jul 10 20:59 jnx.so*
-rwxr-xr-x 1 root root  23984 Jul 10 20:59 jp2.so*
-rwxr-xr-x 1 root root  49136 Jul 10 20:59 jpeg.so*
-rwxr-xr-x 1 root root  44648 Jul 10 20:59 json.so*
-rwxr-xr-x 1 root root  15344 Jul 10 20:59 label.so*
-rwxr-xr-x 1 root root  11232 Jul 10 20:59 mac.so*
-rwxr-xr-x 1 root root 216144 Jul 10 20:59 magick.so*
-rwxr-xr-x 1 root root  15392 Jul 10 20:59 map.so*
-rwxr-xr-x 1 root root  11224 Jul 10 20:59 mask.so*
-rwxr-xr-x 1 root root  32328 Jul 10 20:59 mat.so*
-rwxr-xr-x 1 root root  11160 Jul 10 20:59 matte.so*
-rwxr-xr-x 1 root root  32240 Jul 10 20:59 meta.so*
-rwxr-xr-x 1 root root  44856 Jul 10 20:59 miff.so*
-rwxr-xr-x 1 root root  11288 Jul 10 20:59 mono.so*
-rwxr-xr-x 1 root root  28072 Jul 10 20:59 mpc.so*
-rwxr-xr-x 1 root root  15456 Jul 10 20:59 mpeg.so*
-rwxr-xr-x 1 root root  2 Jul 10 20:59 mpr.so*
-rwxr-xr-x 1 root root 111360 Jul 10 20:59 msl.so*
-rwxr-xr-x 1 root root  15456 Jul 10 20:59 mtv.so*
-rwxr-xr-x 1 root root  11320 Jul 10 20:59 mvg.so*
-rwxr-xr-x 1 root root  11168 Jul 10 20:59 null.so*
-rwxr-xr-x 1 root root  11296 Jul 10 20:59 otb.so*
-rwxr-xr-x 1 root root  23824 Jul 10 20:59 palm.so*
-rwxr-xr-x 1 root root  19864 Jul 10 20:59 pango.so*
-rwxr-xr-x 1 root root  19416 Jul 10 20:59 pattern.so*
-rwxr-xr-x 1 root root  23896 Jul 10 20:59 pcd.so*
-rwxr-xr-x 1 root root  19696 Jul 10 20:59 pcl.so*
-rwxr-xr-x 1 root root  23808 Jul 10 20:59 pcx.so*
-rwxr-xr-x 1 root root  19736 Jul 10 20:59 pdb.so*
-rwxr-xr-x 1 root root  57088 Jul 10 20:59 pdf.so*
-rwxr-xr-x 1 root root  15456 Jul 10 20:59 pes.so*
-rwxr-xr-x 1 root root  15464 Jul 10 20:59 pgx.so*
-rwxr-xr-x 1 root root  44544 Jul 10 20:59 pict.so*
-rwxr-xr-x 1 root root  11304 Jul 10 20:59 pix.so*
-rwxr-xr-x 1 root root  11176 Jul 10 20:59 plasma.so*
-rwxr-xr-x 1 root root 160448 Jul 10 20:59 png.so*
-rwxr-xr-x 1 root root  44416 Jul 10 20:59 pnm.so*
-rwxr-xr-x 1 root root  11128 Jul 10 20:59 preview.so*
-rwxr-xr-x 1 root root  27864 Jul 10 20:59 ps2.so*
-rwxr-xr-x 1 root root  32056 Jul 10 20:59 ps3.so*
-rwxr-xr-x 1 root root  53312 Jul 10 20:59 psd.so*
-rwxr-xr-x 1 root root  48696 Jul 10 20:59 ps.so*
-rwxr-xr-x 1 root root  11352 Jul 10 20:59 pwp.so*
-rwxr-xr-x 1 root root  15480 Jul 10 20:59 raw.so*
-rwxr-xr-x 1 root root  23744 Jul 10 20:59 rgb.so*
-rwxr-xr-x 1 root root  11264 Jul 10 20:59 rgf.so*
-rwxr-xr-x 1 root root  15376 Jul 10 20:59 rla.so*
-rwxr-xr-x 1 root root  19576 Jul 10 20:59 rle.so*
-rwxr-xr-x 1 root root  11168 Jul 10 20:59 scr.so*
-rwxr-xr-x 1 root root  11280 Jul 10 20:59 sct.so*
-rwxr-xr-x 1 root root  15448 Jul 10 20:59 sfw.so*
-rwxr-xr-x 1 root root  23808 Jul 10 20:59 sgi.so*
-rwxr-xr-x 1 root root  23760 Jul 10 20:59 sixel.so*
-rwxr-xr-x 1 root root  11216 Jul 10 20:59 stegano.so*
-rwxr-xr-x 1 

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

--- Comment #7 from caulier.gil...@gmail.com ---
Hum i'm wrong, 7.3.0 is compiled with Magiea6, where 7.4.0 and later Mageia7...

Gilles

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

[okular] [Bug 447363] Kile crashes in Okular::Page::formFields() when rapidly switching between tabs using the keyboard shortcut

2021-12-23 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=447363

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #4 from Albert Astals Cid  ---
it's re-entering the closeDocument method because you press the shortcuts
faster than it takes for cancelling the running threads.

If you can reproduce this easily you need to add a bool in document that is "i
am closing" and then check it first thing in closedocument, if it's already
closing just return, if not set it to true and then set it to false at the end
of the function.

Can you check if that helps?

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

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

--- Comment #6 from caulier.gil...@gmail.com ---
When digiKam from AppImage is running, ImageMagick coders are here :

/tmp/.mount_digiKajEZNOc/usr/lib/modules-Q16HDRI/coders
[gilles@localhost coders]$ ll
total 3849
-rwxr-xr-x 1 root root  15448 Dec 23 19:02 aai.so*
-rwxr-xr-x 1 root root  15456 Dec 23 19:02 art.so*
-rwxr-xr-x 1 root root  19624 Dec 23 19:02 ashlar.so*
-rwxr-xr-x 1 root root  15464 Dec 23 19:02 avs.so*
-rwxr-xr-x 1 root root  31936 Dec 23 19:02 bgr.so*
-rwxr-xr-x 1 root root  48472 Dec 23 19:02 bmp.so*
-rwxr-xr-x 1 root root  15304 Dec 23 19:02 braille.so*
-rwxr-xr-x 1 root root  15496 Dec 23 19:02 cals.so*
-rwxr-xr-x 1 root root  19520 Dec 23 19:02 caption.so*
-rwxr-xr-x 1 root root  28008 Dec 23 19:02 cin.so*
-rwxr-xr-x 1 root root  15288 Dec 23 19:02 cip.so*
-rwxr-xr-x 1 root root  15352 Dec 23 19:02 clip.so*
-rwxr-xr-x 1 root root  31936 Dec 23 19:02 cmyk.so*
-rwxr-xr-x 1 root root  15416 Dec 23 19:02 cube.so*
-rwxr-xr-x 1 root root  19568 Dec 23 19:02 cut.so*
-rwxr-xr-x 1 root root 269936 Dec 23 19:02 dcm.so*
-rwxr-xr-x 1 root root  48760 Dec 23 19:02 dds.so*
-rwxr-xr-x 1 root root  15336 Dec 23 19:02 debug.so*
-rwxr-xr-x 1 root root  31952 Dec 23 19:02 dib.so*
-rwxr-xr-x 1 root root  15472 Dec 23 19:02 dng.so*
-rwxr-xr-x 1 root root  15392 Dec 23 19:02 dot.so*
-rwxr-xr-x 1 root root  40416 Dec 23 19:02 dpx.so*
-rwxr-xr-x 1 root root  15496 Dec 23 19:02 ept.so*
-rwxr-xr-x 1 root root  23840 Dec 23 19:02 exr.so*
-rwxr-xr-x 1 root root  15472 Dec 23 19:02 farbfeld.so*
-rwxr-xr-x 1 root root  15520 Dec 23 19:02 fax.so*
-rwxr-xr-x 1 root root  27960 Dec 23 19:02 fits.so*
-rwxr-xr-x 1 root root  15472 Dec 23 19:02 fl32.so*
-rwxr-xr-x 1 root root  36288 Dec 23 19:02 gif.so*
-rwxr-xr-x 1 root root  15368 Dec 23 19:02 gradient.so*
-rwxr-xr-x 1 root root  27832 Dec 23 19:02 gray.so*
-rwxr-xr-x 1 root root  15288 Dec 23 19:02 hald.so*
-rwxr-xr-x 1 root root  23776 Dec 23 19:02 hdr.so*
-rwxr-xr-x 1 root root  28224 Dec 23 19:02 heic.so*
-rwxr-xr-x 1 root root  19584 Dec 23 19:02 histogram.so*
-rwxr-xr-x 1 root root  15400 Dec 23 19:02 hrz.so*
-rwxr-xr-x 1 root root  15408 Dec 23 19:02 html.so*
-rwxr-xr-x 1 root root  32056 Dec 23 19:02 icon.so*
-rwxr-xr-x 1 root root  15312 Dec 23 19:02 info.so*
-rwxr-xr-x 1 root root  15464 Dec 23 19:02 inline.so*
-rwxr-xr-x 1 root root  23744 Dec 23 19:02 ipl.so*
-rwxr-xr-x 1 root root  23784 Dec 23 19:02 jbig.so*
-rwxr-xr-x 1 root root  15416 Dec 23 19:02 jnx.so*
-rwxr-xr-x 1 root root  28104 Dec 23 19:02 jp2.so*
-rwxr-xr-x 1 root root  57392 Dec 23 19:02 jpeg.so*
-rwxr-xr-x 1 root root  48736 Dec 23 19:02 json.so*
-rwxr-xr-x 1 root root  15280 Dec 23 19:02 kernel.so*
-rwxr-xr-x 1 root root  19472 Dec 23 19:02 label.so*
-rwxr-xr-x 1 root root  15352 Dec 23 19:02 mac.so*
-rwxr-xr-x 1 root root 220280 Dec 23 19:02 magick.so*
-rwxr-xr-x 1 root root  19496 Dec 23 19:02 map.so*
-rwxr-xr-x 1 root root  15392 Dec 23 19:02 mask.so*
-rwxr-xr-x 1 root root  32360 Dec 23 19:02 mat.so*
-rwxr-xr-x 1 root root  15296 Dec 23 19:02 matte.so*
-rwxr-xr-x 1 root root  40464 Dec 23 19:02 meta.so*
-rwxr-xr-x 1 root root  48976 Dec 23 19:02 miff.so*
-rwxr-xr-x 1 root root  15400 Dec 23 19:02 mono.so*
-rwxr-xr-x 1 root root  32208 Dec 23 19:02 mpc.so*
-rwxr-xr-x 1 root root  15240 Dec 23 19:02 mpr.so*
-rwxr-xr-x 1 root root 119608 Dec 23 19:02 msl.so*
-rwxr-xr-x 1 root root  15472 Dec 23 19:02 mtv.so*
-rwxr-xr-x 1 root root  15440 Dec 23 19:02 mvg.so*
-rwxr-xr-x 1 root root  15280 Dec 23 19:02 null.so*
-rwxr-xr-x 1 root root  15168 Dec 23 19:02 ora.so*
-rwxr-xr-x 1 root root  15416 Dec 23 19:02 otb.so*
-rwxr-xr-x 1 root root  27936 Dec 23 19:02 palm.so*
-rwxr-xr-x 1 root root  24000 Dec 23 19:02 pango.so*
-rwxr-xr-x 1 root root  19448 Dec 23 19:02 pattern.so*
-rwxr-xr-x 1 root root  28032 Dec 23 19:02 pcd.so*
-rwxr-xr-x 1 root root  27912 Dec 23 19:02 pcl.so*
-rwxr-xr-x 1 root root  32048 Dec 23 19:02 pcx.so*
-rwxr-xr-x 1 root root  23840 Dec 23 19:02 pdb.so*
-rwxr-xr-x 1 root root  65600 Dec 23 19:02 pdf.so*
-rwxr-xr-x 1 root root  15496 Dec 23 19:02 pes.so*
-rwxr-xr-x 1 root root  15488 Dec 23 19:02 pgx.so*
-rwxr-xr-x 1 root root  52696 Dec 23 19:02 pict.so*
-rwxr-xr-x 1 root root  15416 Dec 23 19:02 pix.so*
-rwxr-xr-x 1 root root  15320 Dec 23 19:02 plasma.so*
-rwxr-xr-x 1 root root 176920 Dec 23 19:02 png.so*
-rwxr-xr-x 1 root root  56712 Dec 23 19:02 pnm.so*
-rwxr-xr-x 1 root root  36080 Dec 23 19:02 ps2.so*
-rwxr-xr-x 1 root root  40288 Dec 23 19:02 ps3.so*
-rwxr-xr-x 1 root root  65704 Dec 23 19:02 psd.so*
-rwxr-xr-x 1 root root  52824 Dec 23 19:02 ps.so*
-rwxr-xr-x 1 root root  15488 Dec 23 19:02 pwp.so*
-rwxr-xr-x 1 root root  19600 Dec 23 19:02 raw.so*
-rwxr-xr-x 1 root root  31984 Dec 23 19:02 rgb.so*
-rwxr-xr-x 1 root root  15368 Dec 23 19:02 rgf.so*
-rwxr-xr-x 1 root root  15400 Dec 23 19:02 rla.so*
-rwxr-xr-x 1 root root  23688 Dec 23 19:02 rle.so*
-rwxr-xr-x 1 root root  15288 Dec 23 19:02 scr.so*
-rwxr-xr-x 1 root root  

[okular] [Bug 447409] okular crash when try to insert annotation stamp

2021-12-23 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=447409

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Crashes doing that on any  file or a particular file?

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

[k3b] [Bug 446900] Changing command line options for lame does not work (ripping mp3 from CD)

2021-12-23 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=446900

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/mult
   ||imedia/k3b/commit/bb5aedb0d
   ||80db412e4404fcc1ed6f2316028
   ||0008

--- Comment #5 from Albert Astals Cid  ---
Git commit bb5aedb0d80db412e4404fcc1ed6f23160280008 by Albert Astals Cid.
Committed on 23/12/2021 at 21:48.
Pushed by aacid into branch 'release/21.12'.

Fix changing command line encoder options not having effect until app restart

We have two plugins using the same config files so we need to reparse
the config each time we access it since it may have been changed by the
other plugin

M  +2-0plugins/encoder/external/k3bexternalencodercommand.cpp

https://invent.kde.org/multimedia/k3b/commit/bb5aedb0d80db412e4404fcc1ed6f23160280008

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

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

--- Comment #5 from caulier.gil...@gmail.com ---
Hum the native Linux version work as expected. So you are right, it's an
AppImage bundle specific problem.

Nothing as changed in AppImage build since 7.3.0 about ImageMagick if i
remember. Sure i recompiled from scratch the AppImage VM, but i use the same
dependencies versions than 7.3.0.

Gilles

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

[digikam] [Bug 447430] Cannot open FITS images - ImageMagick plug in mime types missing

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447430

--- Comment #4 from caulier.gil...@gmail.com ---
Hum the native Linux version work

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

[plasmashell] [Bug 447168] System tray in vertical mode does not wrap the menu indicator vertically

2021-12-23 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=447168

--- Comment #4 from Reuben  ---
Created attachment 144818
  --> https://bugs.kde.org/attachment.cgi?id=144818=edit
vertical

Good tip - so it does look like there is a vertical form factor available which
does the right thing. Is there a way to force a desktop widget to a particular
form factor?

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

2021-12-23 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #189 from Kevin Kofler  ---
The old kdelibs 3 code can be found here:
https://invent.kde.org/unmaintained/kdelibs/-/blob/KDE/3.5/kdecore/klocale.cpp
https://invent.kde.org/unmaintained/kdelibs/-/blob/KDE/3.5/kdecore/klocale.h

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

[digikam] [Bug 447437] Digikam::ImageQualityThread always crashing on macOS 12.1

2021-12-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=447437

Maik Qualmann  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[digikam] [Bug 447437] Digikam::ImageQualityThread always crashing on macOS 12.1

2021-12-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=447437

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
  Component|Tags-Pick   |Maintenance-Quality

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

2021-12-23 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #188 from Kevin Kofler  ---
Would it really be that much work to resurrect the old KLocale class from
kdelibs 3, forward-port it to Qt 5 or 6 and stuff it into a new Framework? Then
it would just be a matter of porting applications from QLocale to that
Framework. (For some, it might even just be a matter of finding the old porting
commit and reverting it, plus adding one dependency to the new Framework.)

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

[digikam] [Bug 447437] Digikam::ImageQualityThread always crashing on macOS 12.1

2021-12-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=447437

--- Comment #1 from Maik Qualmann  ---
Git commit fe00ef75a6c6857fd2d26c36f8719fca0908c653 by Maik Qualmann.
Committed on 23/12/2021 at 21:22.
Pushed by mqualmann into branch 'master'.

this could cause a double delete.
We pass QObject a parent pointer.

M  +4-3core/libs/dimg/filters/imgqsort/imagequalitythread.cpp

https://invent.kde.org/graphics/digikam/commit/fe00ef75a6c6857fd2d26c36f8719fca0908c653

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

[dolphin] [Bug 442774] Dolphin crashed after click on stop button of notification indicating the progress of compression to 7zip archive

2021-12-23 Thread Oliver
https://bugs.kde.org/show_bug.cgi?id=442774

--- Comment #14 from Oliver  ---
Created attachment 144817
  --> https://bugs.kde.org/attachment.cgi?id=144817=edit
New crash information added by DrKonqi

dolphin (21.12.0) using Qt 5.15.2

- What I was doing when the application crashed:

I compressed 3 folders to a .7z file, waited and then suddenly dolphin crashed. 
Tried 3 times, all with the same result.

-- Backtrace (Reduced):
#4  0x7f71bbe03253 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#5  0x7f71bbe0356e in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#6  0x7f71bbdff9f7 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#7  0x7f71bc8121a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#8  0x7f71bbddbf8a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5

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

[dolphin] [Bug 442774] Dolphin crashed after click on stop button of notification indicating the progress of compression to 7zip archive

2021-12-23 Thread Oliver
https://bugs.kde.org/show_bug.cgi?id=442774

Oliver  changed:

   What|Removed |Added

 CC||frequency...@gmail.com

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

[plasmashell] [Bug 447168] System tray in vertical mode does not wrap the menu indicator vertically

2021-12-23 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=447168

--- Comment #3 from Konrad Materka  ---
Hmm, this looks as expected behavior. Desktop widgets are always horizontal,
doesn't matter how tall you make them. As far as I know (but maybe I'm wrong)
it is not possible to configure orientation for desktop widgets.

You can play with different settings using this command:

plasmoidviewer --applet org.kde.plasma.systemtray

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

[krita] [Bug 447213] cut tool not working well within lasso tool

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=447213

--- Comment #5 from acc4commissi...@gmail.com ---
I'm not sure it's related, krita sometimes stuck in a state that you just see
the marching ants you made on the canvas that won't dissapear and can't
deselect, make a selection, move/copy/paste anything with selections etc.

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

[krusader] [Bug 445549] kioslave5 blocking umount

2021-12-23 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=445549

Nikita Melnichenko  changed:

   What|Removed |Added

 CC||nikita+...@melnichenko.name

--- Comment #2 from Nikita Melnichenko  ---
I'm on KF-5.85 and this doesn't repro. Is it possible for you to downgrade and
see if it's still happening? Otherwise, let's keep it open and see if it's
related to an upstream change in >= 5.86 as new version is getting stabilized
in different distros.

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

[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text

2021-12-23 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #187 from RJVB  ---
(In reply to Nate Graham from comment #182)
> To my knowledge, fixing this requires one of the following:
> 1. Change the Qt locale system to support the feature
> 2. Abandon the-in Qt locale system for this and implement a completely
> custom system, like the KLocale system we had in the KDE 4 days but moved
> away from in favor of QLocale
> 
> Either one would be a huge amount of work.

Isn't this exactly where OOC should make things straightforward if not easy?
Just how much work would it be to clone (inherit) QLocale, merge/port the
required functionality from KLocale (which I presume is or was in
kdelibs4support at some point) and then (once properly debugged) do a
search/replace on all the code in the frameworks, plasma and applications
repositories to use the new class instead of QLocale? The amount of change
could be huge, but maybe even that would be less than one might think if code
using QLocale always imports qlocal.h . In that case, only that header has to
be replaced with the new header, and the appropriate `using` expression.


[OT]
WHT happened to BKO? All of a sudden it looks as if designed for someone with a
visuomotor handicap and a huge screen?!
[/OT]

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

[krusader] [Bug 443054] krusader does not provide a bug reporting address

2021-12-23 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=443054

Nikita Melnichenko  changed:

   What|Removed |Added

 CC||nikita+...@melnichenko.name
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Nikita Melnichenko  ---
Are you on Wayland? The stack trace trace is pretty much unusable. The issue is
likely happened a long time before the actual crash.

> I experienced a crash of 4 componentes in same time
What do you mean?

> You cannot report this error because krusader does not provide a bug 
> reporting address.
This should not be happening. Is drkonqi installed? Where do you see this
message? Does Crash Reporting Assistant open for you?

For meaningful bug reports please read this:
https://wiki.gentoo.org/wiki/Debugging
I recommend enabling debugsyms environment for all Qt, KF and krusader
packages. If it feels complicated, you can at least put splitdebug
compressdebug into FEATURES in your make.conf and rebuild the world.

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

[konsole] [Bug 447447] New: The konsole ssh plugin don't save the username.

2021-12-23 Thread Miguel Angel
https://bugs.kde.org/show_bug.cgi?id=447447

Bug ID: 447447
   Summary: The konsole ssh plugin don't save the username.
   Product: konsole
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: miguel.angel.lopez.vice...@gmail.com
  Target Milestone: ---

SUMMARY

The ssh plugin don't save the username. 

When I set the ssh data, set the host, port and username, I can use it and it
works fine. But, when I restart konsole and use the saved connection, it don't
add the username, only host and port.

If I edit the connection, the username is empty.


STEPS TO REPRODUCE
1. Add ssh connection with username
2.  Restart console
3. Use connection

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Manjaro
KDE Plasma Version: 5.23.4

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

[digikam] [Bug 447013] No Local/.marble/plugins were loaded

2021-12-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=447013

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||7.5.0

--- Comment #12 from Maik Qualmann  ---
The problem of loading the Marble plugin has been fixed with the pre-release
version of digiKam-7.5.0 from December 23, 2021.

https://files.kde.org/digikam/

Maik

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

[lattedock] [Bug 445377] Latte-dock automaticly add a margin around element when the floating feature is used.

2021-12-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445377

--- Comment #7 from schul9lo...@outlook.fr ---
(In reply to Michail Vourlakos from comment #6)
> show me a full screenshot of your top panel when the margins are shown and
> describe afterwards what you consider an issue.

Here's a link to the screenshot :
https://imgur.com/a/rOuMdqg

As you can see on the screenshot I circled 2 things :
- First : on the top panel, you can clearly see margins above and underneath
the "task widget". Those are seens as "big" blue line above and underneath the
widget.
- Second : on the right of the screen, I clearly circle the width and length of
the margins that should be applied to this panel. Those 2 values are both set
to 0px.

Since the width and length value of the margins are both set to 0, there should
not be any margin applied to this panel.
As I said before, this issues only appear when I make the panel "float" by
increasing the value in the "screen edge" slider.

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

  1   2   3   >