[plasmashell] [Bug 358418] Allow widgets to optionally not snap to a grid

2023-04-17 Thread Thomas Murphy
https://bugs.kde.org/show_bug.cgi?id=358418

Thomas Murphy  changed:

   What|Removed |Added

 CC||t...@xequals.co.nz

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

[digikam] [Bug 468639] New: compiling 8.0.0 crashes on 'make install'

2023-04-17 Thread Bob Billson
https://bugs.kde.org/show_bug.cgi?id=468639

Bug ID: 468639
   Summary: compiling 8.0.0 crashes on 'make install'
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: r...@nodot.org
  Target Milestone: ---

SUMMARY
***
Compiling 8.0.0 from source doing 'sudo make install' crashes with error
complaining test-data directory already exists and is not empty.
***

STEPS TO REPRODUCE
1. cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/usr/local .
2. make -j`nproc`
3. sudo make install

OBSERVED RESULT

reb@grue:~/src/digikam/digikam-8.0.0$ sudo make install
[sudo] password for reb:
[  0%] Generating mo...
[  0%] Built target pofiles-651a6d3373c8feb286ebdb52b95b3370
[  0%] Generating ts...
[  0%] Built target tsfiles-651a6d3373c8feb286ebdb52b95b3370
make[2]: Circular CMakeFiles/test-data <- test-data dependency dropped.
make[2]: Circular test-data <- test-data dependency dropped.
[  0%] Checkout unit-test data repository. Please wait...
fatal: destination path '/home/reb/src/digikam/digikam-8.0.0/test-data' already
exists and is not an empty directory.
make[2]: *** [CMakeFiles/test-data.dir/build.make:73: test-data] Error 128
make[1]: *** [CMakeFiles/Makefile2:7123: CMakeFiles/test-data.dir/all] Error 2
make: *** [Makefile:146: all] Error 2


SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.11-grue (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-6500U CPU @ 2.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: Purism
Product Name: Librem 15 v3
System Version: 1.0

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

[Breeze] [Bug 468610] Desktop Icons cannot be moved freely around the desktop

2023-04-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=468610

Nate Graham  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |DOWNSTREAM

--- Comment #3 from Nate Graham  ---
Great, thanks for following up!

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

[kwin] [Bug 468578] Desktop Grid is extremely slow when using Lightly app theme

2023-04-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=468578

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |DOWNSTREAM
Summary|Desktop Grid is extremely   |Desktop Grid is extremely
   |slow|slow when using Lightly app
   ||theme

--- Comment #3 from Nate Graham  ---
Oh ok, cool!

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

[systemsettings] [Bug 468298] Clicking on list item for Google account does nothing

2023-04-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=468298

Nate Graham  changed:

   What|Removed |Added

   Priority|VHI |NOR

--- Comment #5 from Nate Graham  ---
I reproduced the issue on a distro-provided session with no source-built
packages being used, though. Regardless, lowering priority since no one else
seems to be able to reproduce the issue, so it can't be *that* common.

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

[digikam] [Bug 468618] Image quality sort - blink database settings

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468618

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

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from caulier.gil...@gmail.com ---
Under MacOS, this problem is not reproducible at all.

But with the native Linux (Kubuntu 22.04), it"s reproducible.

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

[systemsettings] [Bug 467922] kde settings crashed in QFontconfigDatabase::setupFontEngine()

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=467922

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

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

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

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

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

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

[kwin] [Bug 467973] visual glitch with PiP window tiled in half with another app

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=467973

--- Comment #4 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 468601] Segmentation fault when starting up

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=468601

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #3 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[kwin] [Bug 247353] [Tiling] KWin tiling with many windows can make the whole workspace unresponsive

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=247353

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[plasmashell] [Bug 455375] Possible regression in mimetype handling for recent files

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=455375

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

[kate] [Bug 468638] New: kate crashed while moving tab

2023-04-17 Thread Phil
https://bugs.kde.org/show_bug.cgi?id=468638

Bug ID: 468638
   Summary: kate crashed while moving tab
Classification: Applications
   Product: kate
   Version: 22.12.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: phils...@phlexo.com
  Target Milestone: ---

Application: kate (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.0.0-3-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.2 [KCrashBackend]

-- Information about the crash:
This crash occured when trying to move a tab from an existing kate window to
another.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault

[KCrash Handler]
#4  0x7fa642f9a5c7 in QWidget::raise (this=0x55c3c205de50) at
kernel/qwidget.cpp:11590
#5  0x7fa6431238d0 in QTabBarPrivate::setupMovableTab
(this=this@entry=0x55c3bfc6ea50) at widgets/qtabbar.cpp:2241
#6  0x7fa643123de7 in QTabBar::mouseMoveEvent (this=0x55c3bfc341b0,
event=0x7fff3514f110) at widgets/qtabbar.cpp:2147
#7  0x7fa642fa4db8 in QWidget::event (this=0x55c3bfc341b0,
event=0x7fff3514f110) at kernel/qwidget.cpp:9044
#8  0x7fa642f62fae in QApplicationPrivate::notify_helper
(this=this@entry=0x55c3bf7de920, receiver=receiver@entry=0x55c3bfc341b0,
e=e@entry=0x7fff3514f110) at kernel/qapplication.cpp:3640
#9  0x7fa642f6b552 in QApplication::notify (this=,
receiver=0x55c3bfc341b0, e=) at kernel/qapplication.cpp:3084
#10 0x7fa6420b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fa642f6965e in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x55c3bfc341b0, event=event@entry=0x7fff3514f110,
alienWidget=, nativeWidget=0x55c3bfc8f290,
buttonDown=buttonDown@entry=0x7fa6434a69f0 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2622
#12 0x7fa642fbdbd8 in QWidgetWindow::handleMouseEvent
(this=this@entry=0x55c3c02b5370, event=event@entry=0x7fff3514f3c0) at
kernel/qwidgetwindow.cpp:683
#13 0x7fa642fc0f60 in QWidgetWindow::event (this=0x55c3c02b5370,
event=0x7fff3514f3c0) at kernel/qwidgetwindow.cpp:300
#14 0x7fa642f62fae in QApplicationPrivate::notify_helper (this=, receiver=0x55c3c02b5370, e=0x7fff3514f3c0) at
kernel/qapplication.cpp:3640
#15 0x7fa6420b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fa64273d3ed in QGuiApplicationPrivate::processMouseEvent
(e=0x55c3bfcc9b10) at kernel/qguiapplication.cpp:2278
#17 0x7fa642711cac in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#18 0x7fa63c2fbeba in xcbSourceDispatch (source=) at
./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105
#19 0x7fa63ff1e7a9 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7fa63ff1ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fa63ff1eacc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fa642109836 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fa6420b017b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fa6420b82d6 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x55c3befd1e33 in ?? ()
#26 0x7fa641c4618a in __libc_start_call_main
(main=main@entry=0x55c3befd0fa0, argc=argc@entry=4,
argv=argv@entry=0x7fff3514fc58) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x7fa641c46245 in __libc_start_main_impl (main=0x55c3befd0fa0, argc=4,
argv=0x7fff3514fc58, init=, fini=,
rtld_fini=, stack_end=0x7fff3514fc48) at ../csu/libc-start.c:381
#28 0x55c3befd3a91 in ?? ()
[Inferior 1 (process 3300927) detached]

Reported using DrKonqi

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

[digikam] [Bug 468609] Loads heif only with 8 bits color depth

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468609

--- Comment #1 from caulier.gil...@gmail.com ---
Right, from Image MAgick, we can see :

gilles@U22:/mnt/data/Images/HEIF$ identify test.heif 
test.heif HEIC 3237x2007 3237x2007+0+0 10-bit YCbCr 0.020u 0:00.011

>From the console, when loading file on editor, libheif identify this file with
8 bits color depth:

digikam.dimg: "/mnt/data/Images/HEIF/test.heif" : "HEIF" file identified
digikam.dimg.heif: HEIF image size: ( 3237 x 2007 )
digikam.dimg.heif: Decoded HEIF image properties: size( 3237 x 2007 ), Alpha:
false , Color depth : 8
digikam.dimg.heif: HEIF data container: 0x55acd15cdb00
digikam.dimg.heif: HEIC bytes per line: 9728
digikam.dimg.heif: Color bytes depth: 8

So problem must be located in how we manage libheif in the HEIF loader, as
Image Magick which uses libheif too, is able to convert to PNG with preserving
the color depth :

gilles@U22:/mnt/data/Images/HEIF$ convert test.heif test.png
gilles@U22:/mnt/data/Images/HEIF$ identify test.png 
test.png PNG 3237x2007 3237x2007+0+0 16-bit sRGB 17.1832MiB 0.000u 0:00.000

Probably this code must be used :

https://github.com/ImageMagick/ImageMagick/blob/main/coders/heic.c#L354

In digiKam, we uses : 

https://invent.kde.org/graphics/digikam/-/blob/master/core/dplugins/dimg/heif/dimgheifloader_load.cpp#L389

Gilles Caulier

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

[digikam] [Bug 468637] Behaviour for network shares does not follow KDE's own recommendation

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468637

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
* KIO * Is not portable to non Unix systems and is the hell to bundle.

Gilles Caulier

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

[digikam] [Bug 468637] New: Behaviour for network shares does not follow KDE's own recommendation

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468637

Bug ID: 468637
   Summary: Behaviour for network shares does not follow KDE's own
recommendation
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Setup-Collections
  Assignee: digikam-bugs-n...@kde.org
  Reporter: spamless.9v...@simplelogin.com
  Target Milestone: ---

SUMMARY

As noted in https://bugs.kde.org/show_bug.cgi?id=227566, digiKam does not have
support for SMB shares, which was resolved by instructing users to explicitly
mount the folder natively. However, this recommendation is in direct conflict
with the resolution of https://bugs.kde.org/show_bug.cgi?id=464705 that one
should avoid using fstab and instead delegate network related file access to
KIO-fuse.

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

[konsole] [Bug 468636] New: Living white selections and scrolling glyphs

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468636

Bug ID: 468636
   Summary: Living white selections and scrolling glyphs
Classification: Applications
   Product: konsole
   Version: 20.12.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: orisis.kde.2...@distributedrebirth.love
  Target Milestone: ---

Created attachment 158182
  --> https://bugs.kde.org/attachment.cgi?id=158182=edit
maven unicode console output

SUMMARY
After an Allah glyph in text the remaining text and white space on the same
line change render width on selection.
When selecting Hebrew or Arab the glyphs mirror? on selection.

STEPS TO REPRODUCE
Added the project build output text

OBSERVED RESULT
https://www.youtube.com/watch?v=GB7s1J-2QO0

EXPECTED RESULT
Stable text

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

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=468635

--- Comment #3 from Aleix Pol  ---
Something I do in these cases is the following:
- start the system, switch to a tty (ctrl+alt+F3)
- log into your user
- run tmux (or screen or anything similar you prefer)
- ssh from another system
- attach to the tmux from the other system "tmux a"
- execute "startplasma-wayland"

There we should be able to see what's going on.

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

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635

--- Comment #2 from HD Scania  ---
Where to get logs for Wayland-related issues?
And will going frozen then having to reboot even be loggable? I'm quite unsure

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

[systemsettings] [Bug 468298] Clicking on list item for Google account does nothing

2023-04-17 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=468298

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org

--- Comment #4 from Harald Sitter  ---
Created attachment 158181
  --> https://bugs.kde.org/attachment.cgi?id=158181=edit
working live session

I'm inclined to say this is a Nate vs. DBus problem more than a bug. It works
just fine in the fedora live session

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

[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel

2023-04-17 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=455394

Harald Sitter  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REOPENED

--- Comment #18 from Harald Sitter  ---
Good thought. I'll try some more.

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

[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel

2023-04-17 Thread Thiago Macieira
https://bugs.kde.org/show_bug.cgi?id=455394

--- Comment #17 from Thiago Macieira  ---
(In reply to Harald Sitter from comment #16)
> Are you quite certain the config this happens with is from 5.27 (not older
> and incorrect from before 5.27)? I've been playing with the kcm for a while
> and haven't managed to get incorrect snapping out of it.

Yes, I am quite sure.

My guess is this is related to HighDPI: at 2x, the off-by-1 gets lost in the
rounding.

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

[kmymoney] [Bug 468191] Backup hanging

2023-04-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=468191

Jack  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #6 from Jack  ---
Thanks for letting us know.  Feel free to reopen if the problem happens again.
Note:  when replying to a bug by email, delete everything you are replying to,
as your entire message becomes the next comment, and it is not necessary to
include the previous comment, which can be seen right above.
Thanks.

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

[kmymoney] [Bug 468191] Backup hanging

2023-04-17 Thread Guy
https://bugs.kde.org/show_bug.cgi?id=468191

--- Comment #5 from Guy  ---
I installed the latest and it seems to have backed up the data.

Thanks,

Guy

On Sat, Apr 15, 2023 at 10:12 AM Guy Clements 
wrote:

> Thanks Jack. Let me update and I'll keep you posted.
>
> Guy
>
> On Fri, Apr 14, 2023, 5:02 PM Jack  wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=468191
>>
>> --- Comment #3 from Jack  ---
>> Guy,
>>
>> Please do let us know if the current version (5.1.3) works ok or if we
>> still
>> have some digging to do on Windows.  Particularly - without ticking the
>> "mount"
>> checkbox.
>>
>> Thanks.
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>

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

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=468635

Aleix Pol  changed:

   What|Removed |Added

Version|5.27.2  |5.27.4

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

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=468635

Aleix Pol  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
Version|unspecified |5.27.2
  Component|general |platform-drm
   Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
 Resolution|--- |WAITINGFORINFO
Product|plasma-wayland-protocols|kwin

--- Comment #1 from Aleix Pol  ---
I'm afraid we will need more information here. Can you maybe check if you can
find any errors on the user logs, maybe from the kwin_wayland process?

As is, this is not really actionable.

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

[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel

2023-04-17 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=455394

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org
 Resolution|--- |WAITINGFORINFO
 Status|REOPENED|NEEDSINFO

--- Comment #16 from Harald Sitter  ---
Are you quite certain the config this happens with is from 5.27 (not older and
incorrect from before 5.27)? I've been playing with the kcm for a while and
haven't managed to get incorrect snapping out of it.

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

[kate] [Bug 467168] KWrite forgets file history

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467168

--- Comment #4 from thwr...@gmail.com ---
Cleaning of ~/.config/kwriterc didn't help. I've just opened a .txt file from
Dolphin and my file history has been emptied.

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

[plasma-wayland-protocols] [Bug 468635] New: Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635

Bug ID: 468635
   Summary: Plasma/Wayland always goes frozen on an AMD APU
Classification: Plasma
   Product: plasma-wayland-protocols
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: hd-sca...@users.sf.net
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
***
AMD APU Zen2 Lucienne-G R4750G with 48GB SoDiMM DDR4
With Artix being installed and run an BtrFS partition on Samsung 980 PRO NVMe
SSD 1.82TiB with heatsink
KDE Plasma v5.27.4
Qt v5.15.9
KDE frameworks v5.105.0
Linux kernel 6.2.6-artix1-1
(Which commands to check for Wayland version?)
Trinity R14.0.13 (Never crashes)
XFCE R4.15.x (Never crashes)
(Not tested for Plasma/X11, but if doesn't crash or go frozen that often then
Wayland is to be blamed for being not that ready on AMD APU's :) )

Never Trinity or XFCE crashes so unlikely h/w fault, but too usually
Plasma/Wayland is that way mcuh unstable
Every time Plasma/Wayland gets into a crash, frozen and has to reboot always,
unable to even get into tty
***


STEPS TO REPRODUCE
1. Reboot in SDDM, and log in as a normal user on Plasma/Wayland
2. Operating Plasma as normal, but when idle Plasma/Wayland goes frozen
3. For going frozen and unable to even get into tty, reboot and let local
partitions force checked
4. Back to SDDM and log in again as a normal user, and leave Plasma/Wayland
idle for a few moments
5. Plasma/Wayland goes frozen again somewhy, so go for Plasma/X11 and/or sth
else like Trinity and/or XFCE
6. Upgrade your OS packages for Plasma and trace to up-to-date, Plasma/Wayland
still goes frozen somewhy

OBSERVED RESULT
Plasma/Wayland goes frozen at a random tme somewhy

EXPECTED RESULT
Plasma/Wayland no longer goes frozen for being idle for a few moments

SOFTWARE/OS VERSIONS
(Provided at top of this message)
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:

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

[kmymoney] [Bug 468633] segfault when hidding reconciliated transacion

2023-04-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=468633

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #2 from Jack  ---
I confirm the crash, now in all accounts I've tested.  BT looks the same as
posted above.  I'll try a git bisect, but probably not until tomorrow.
Confirmed with kmymoney 5.1.80-7f771f516.

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

[kscreenlocker] [Bug 468469] Disabling compositing doesn't affect the lock screen

2023-04-17 Thread Vladimir Potapov
https://bugs.kde.org/show_bug.cgi?id=468469

--- Comment #6 from Vladimir Potapov  ---
You need to disable the smooth change of background brightness before the
password entry line appears when you press any key on the locked screen.

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

[plasmashell] [Bug 468576] Middle-clicking certain widgets in a panel crashes plasmashell

2023-04-17 Thread Ryan Y
https://bugs.kde.org/show_bug.cgi?id=468576

--- Comment #2 from Ryan Y  ---
I'm using Breeze Dark.

Yes, it happens in the Wayland session too.

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

[kmymoney] [Bug 468633] segfault when hidding reconciliated transacion

2023-04-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=468633

--- Comment #1 from Jack  ---
I tested with a build from master from several days ago and had some very
strange results.  In one investment account, Ctl-R (do not show reconciled
transactions) had no effect - reconciled transactions remained displayed, and
no crash.  In the brokerage account for that investment account, Ctl-R did what
it is supposed to do, still no crash.  I then tested in a cash account and got
a crash.  I just updated git and am building again and will test with a wider
variety of accounts.

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

[kmymoney] [Bug 468108] ledger freeze on large account

2023-04-17 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=468108

--- Comment #22 from Jack  ---
Thanks Thomas.  I confirm this fix does seem work - no more delays with either
my own data or the test file.

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

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

2023-04-17 Thread Miren Radia
https://bugs.kde.org/show_bug.cgi?id=456210

Miren Radia  changed:

   What|Removed |Added

 CC|miren_ra...@yahoo.co.uk |

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

[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened

2023-04-17 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=468630

Albert Astals Cid  changed:

   What|Removed |Added

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

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

[krita] [Bug 468601] Segmentation fault when starting up

2023-04-17 Thread Kim Tore Jensen
https://bugs.kde.org/show_bug.cgi?id=468601

--- Comment #2 from Kim Tore Jensen  ---
(In reply to Dmitry Kazakov from comment #1)

> From the backtrace it seems like the problem is related to the custom build
> of Arch Linux package...

Hi Dmitry,

Reporting to the Arch Linux community revealed that Krita had a TIFF file in
the recent history that  was causing trouble.
I have identified the file in question, it is a 56MB file from NASA's infrared
camera satellite.
What would you like me to do?

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

[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468630

--- Comment #4 from flampin...@gmail.com ---
Created attachment 158179
  --> https://bugs.kde.org/attachment.cgi?id=158179=edit
error popup when trying to open file

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

[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468630

--- Comment #3 from flampin...@gmail.com ---
(In reply to Albert Astals Cid from comment #1)
> Please in the future do not report two different problems in the same issue,
> makes tracking them unnecessarily hard.
> 
> Also, can you please attach that cbz that you say we fail to open?

I apologize for two problems in one issue. The main problem is that .cbz files
containing .webp image/s cannot be opened. (everything else is not so
important)

I've added an example of a file that won't open.

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

[Spectacle] [Bug 451842] Spectacle Won't Work on Fedora - on Gnome

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=451842

--- Comment #4 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/spectacle/-/merge_requests/229

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

[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468630

--- Comment #2 from flampin...@gmail.com ---
Created attachment 158178
  --> https://bugs.kde.org/attachment.cgi?id=158178=edit
test .cbz file with one .webp image

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

[KScreen] [Bug 468627] Desktop and task manager off after screen waking up

2023-04-17 Thread joseteluisete
https://bugs.kde.org/show_bug.cgi?id=468627

joseteluisete  changed:

   What|Removed |Added

 CC||jos...@tutamail.com

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

[KScreen] [Bug 468627] Desktop and task manager off after screen waking up

2023-04-17 Thread joseteluisete
https://bugs.kde.org/show_bug.cgi?id=468627

joseteluisete  changed:

   What|Removed |Added

Summary|Desktop and task manager|Desktop and task manager
   |off after waking up |off after screen waking up

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

[okular] [Bug 468360] Some scanned PDF's with ocr are white but knows it is text

2023-04-17 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=468360

Albert Astals Cid  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #3 from Albert Astals Cid  ---
This is most probably a poppler bug, needs investigation

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

[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened

2023-04-17 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=468630

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Please in the future do not report two different problems in the same issue,
makes tracking them unnecessarily hard.

Also, can you please attach that cbz that you say we fail to open?

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

[kscreenlocker] [Bug 468181] X11: some french accentuated characters are not possible

2023-04-17 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=468181

Andrey  changed:

   What|Removed |Added

 CC||meven@kdemail.net

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

[kscreenlocker] [Bug 468181] X11: some french accentuated characters are not possible

2023-04-17 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=468181

Andrey  changed:

   What|Removed |Added

 CC||aleix...@kde.org

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

[plasmashell] [Bug 467909] Connecting external monitor and attempting to extend desktop caused plasma to crash in PlasmaQuick::ContainmentView::setContainment()

2023-04-17 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=467909

--- Comment #7 from Albert Astals Cid  ---
Git commit 45c22a0221937682f4496801a495458a00f76d3a by Albert Astals Cid, on
behalf of Volker Hilsheimer.
Committed on 17/04/2023 at 21:40.
Pushed by aacid into branch 'kde/5.15'.

QQuickItem: Fix effective visibility for items without parent

Items are visible if they are children of a visible parent, and not
explicitly hidden. The effectiveVisible member stores the state and is
updated when conditions that impact the item visibility changes.

The old code returned true for items outside a visual hierarchy, which
broke signal emission when items were removed from a parent, e.g.
because the parent got destroyed. With this change, items removed from
a visual hierarchy will emit the visibleChanged signal.

Note: QQuickItem initializes the effectiveVisible member to true, even
if the item was created without parent item. Visual items are required
to be added to a visual hierarchy via setParentItem. For this reason,
newly created items never emit visibleChanged when they are added to
a parent.

Adjust the QQuickItem::visible test - it creates an item hierarchy
without window. Such items are never visible, so add a window and
parent the test item hierarchy to the window's content item.

This fixes the expected failures in the tests. It does introduce an
incompatibility with QGraphicsView and QGraphicsItem, which continue
to return true from QGraphicsItem::isVisible for items that are not
in an item hierarchy.

[ChangeLog][Qt Quick][QQuickItem] The visible property of Items without
a parent now always returns false, and the visibleChanged signal gets
emitted when the parent item of a visible item becomes null.

Fixes: QTBUG-108213
Change-Id: If4b2947cefd1407853f0f29e6c3fdbd49fc9af65
Reviewed-by: Fabian Kosmale 
Reviewed-by: Shawn Rutledge 
(cherry picked from commit d1b9a4cacfb966cf0a37983d8f8044f3aedf5de3)
Related: bug 396359

M  +2-4src/quick/items/qquickitem.cpp
M  +2-0tests/auto/quick/qquickitem/tst_qquickitem.cpp

https://invent.kde.org/qt/qt/qtdeclarative/commit/45c22a0221937682f4496801a495458a00f76d3a

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

[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList

2023-04-17 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=396359

--- Comment #34 from Albert Astals Cid  ---
Git commit 45c22a0221937682f4496801a495458a00f76d3a by Albert Astals Cid, on
behalf of Volker Hilsheimer.
Committed on 17/04/2023 at 21:40.
Pushed by aacid into branch 'kde/5.15'.

QQuickItem: Fix effective visibility for items without parent

Items are visible if they are children of a visible parent, and not
explicitly hidden. The effectiveVisible member stores the state and is
updated when conditions that impact the item visibility changes.

The old code returned true for items outside a visual hierarchy, which
broke signal emission when items were removed from a parent, e.g.
because the parent got destroyed. With this change, items removed from
a visual hierarchy will emit the visibleChanged signal.

Note: QQuickItem initializes the effectiveVisible member to true, even
if the item was created without parent item. Visual items are required
to be added to a visual hierarchy via setParentItem. For this reason,
newly created items never emit visibleChanged when they are added to
a parent.

Adjust the QQuickItem::visible test - it creates an item hierarchy
without window. Such items are never visible, so add a window and
parent the test item hierarchy to the window's content item.

This fixes the expected failures in the tests. It does introduce an
incompatibility with QGraphicsView and QGraphicsItem, which continue
to return true from QGraphicsItem::isVisible for items that are not
in an item hierarchy.

[ChangeLog][Qt Quick][QQuickItem] The visible property of Items without
a parent now always returns false, and the visibleChanged signal gets
emitted when the parent item of a visible item becomes null.

Fixes: QTBUG-108213
Change-Id: If4b2947cefd1407853f0f29e6c3fdbd49fc9af65
Reviewed-by: Fabian Kosmale 
Reviewed-by: Shawn Rutledge 
(cherry picked from commit d1b9a4cacfb966cf0a37983d8f8044f3aedf5de3)
Related: bug 467909

M  +2-4src/quick/items/qquickitem.cpp
M  +2-0tests/auto/quick/qquickitem/tst_qquickitem.cpp

https://invent.kde.org/qt/qt/qtdeclarative/commit/45c22a0221937682f4496801a495458a00f76d3a

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

[okular] [Bug 468634] New: Okular defaults to printing on letter sized paper despite another format (A4) is preferred and more suitable

2023-04-17 Thread Bzzz
https://bugs.kde.org/show_bug.cgi?id=468634

Bug ID: 468634
   Summary: Okular defaults to printing on letter sized paper
despite another format (A4) is preferred and more
suitable
Classification: Applications
   Product: okular
   Version: 21.12.3
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: misc-kde...@wanhunglo.com
  Target Milestone: ---

SUMMARY
Okular defaults to printing on letter sized paper.
PDF pages are A4
$LC_ALL is de_DE.UTF-8 (and DIN A4 is literally a German industry standard
size)
$LC_PAPER is de_DE.UTF-8 (dito)
CUPS printer default is A4
Last document was printed in A4
Actual paper size in the printer is A4
And yet okular still defaults to letter size. every. single. time.


STEPS TO REPRODUCE
1. Open PDF
2. Ctrl P
3. Check printer settings
4. Be annoyed about "Letter" being chosen as default paper size, change it to
A4

OBSERVED RESULT
Printing A4 documents as letter on A4 paper yields strange page margins, so
these steps are necessary for each and every printed document

EXPECTED RESULT
Steps 3+4 become obsolete since A4 (or any other format you'd prefer) can be
set as default or is even chosen as default by using other means such as CUPS
default paper settings of the printer used or PDF page size

SOFTWARE/OS VERSIONS
Betriebssystem: Kubuntu 22.04
KDE-Plasma-Version: 5.24.7
KDE-Frameworks-Version: 5.92.0
Qt-Version: 5.15.3
Kernel-Version: 5.15.0-56-generic (64-bit)
Grafik-Plattform: X11

ADDITIONAL INFORMATION
Maybe a regression of #174354 - maybe not. Other non-KDE applications default
to A4 as they should (e.g. Firefox, Thunderbird, Chrome, Opera)

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

[unknown] [Bug 462405] subtitlecomposer crashes when choosing a different audio stream

2023-04-17 Thread Freedim
https://bugs.kde.org/show_bug.cgi?id=462405

Freedim  changed:

   What|Removed |Added

 CC||coocoola...@protonmail.ch

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

[unknown] [Bug 462405] subtitlecomposer crashes when choosing a different audio stream

2023-04-17 Thread Freedim
https://bugs.kde.org/show_bug.cgi?id=462405

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

subtitlecomposer (0.7.1) using Qt 5.15.8

Additionally, if one wants to switch the audio stream WHILE THE VIDEO IS
PAUSED, then the application hangs.

-- Backtrace (Reduced):
#7  0x7f6085785601 in KSelectAction::indexTriggered(int) () at
/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5
[...]
#9  0x7f60857855a1 in KSelectAction::triggered(int) () at
/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5
#10 0x7f60857881ec in KSelectAction::actionTriggered(QAction*) () at
/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5
[...]
#12 0x7f6084f6053f in QActionGroup::triggered(QAction*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
[...]
#14 0x7f6084f5c782 in QAction::triggered(bool) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

[kmymoney] [Bug 468633] New: segfault when hidding reconciliated transacion

2023-04-17 Thread Jonatan Cloutier
https://bugs.kde.org/show_bug.cgi?id=468633

Bug ID: 468633
   Summary: segfault when hidding reconciliated transacion
Classification: Applications
   Product: kmymoney
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: cloutier...@gmail.com
  Target Milestone: ---

Application: kmymoney (5.1.80-)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.8-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
When on the ledger with reconciled. If I got on the view menu and select "hide
reconcilated transaction" (my own translation) KMyMoney crash.

This is using the master from today

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault

[KCrash Handler]
#4  0x55ec99af17d8 in LedgerViewSettings::hideTransactionsBefore() const
(this=0x55eca32c16a0) at /build/kmymoney/views/ledgerviewsettings.cpp:130
#5  0x55ec99add021 in ::operator() (__closure=0x55eca2f01760,
__closure=0x55eca2f01760) at /build/kmymoney/views/ledgerviewpage.cpp:126
#6  QtPrivate::FunctorCall, QtPrivate::List<>, void,
LedgerViewPage::initModel():: >::call (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#7  QtPrivate::Functor,
0>::call, void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#8  QtPrivate::QFunctorSlotObject, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x55eca2f01750, r=, a=, ret=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#9  0x7f4b430bea71 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f4b430bea71 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f4b430c0fcf in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#12 0x7f4b430b1b56 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#13 0x7f4b43d78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#14 0x7f4b4308df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#15 0x7f4b430d84b3 in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#16 0x7f4b430d8aaa in  () at /usr/lib/libQt5Core.so.5
#17 0x7f4b40b0f53b in g_main_dispatch (context=0x7f4b2ee0) at
../glib/glib/gmain.c:3460
#18 g_main_context_dispatch (context=0x7f4b2ee0) at
../glib/glib/gmain.c:4200
#19 0x7f4b40b6c219 in g_main_context_iterate.constprop.0
(context=0x7f4b2ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#20 0x7f4b40b0e1a2 in g_main_context_iteration (context=0x7f4b2ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#21 0x7f4b430d8c6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#22 0x7f4b430866ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#23 0x7f4b43091219 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#24 0x55ec9982443d in runKMyMoney(QUrl const&, bool, QApplication&)
(file=..., noFile=noFile@entry=false, a=...) at /build/kmymoney/main.cpp:384
#25 0x55ec9981e6a7 in main(int, char**) (argc=,
argv=) at /build/kmymoney/main.cpp:293
[Inferior 1 (process 3813812) detached]

Reported using DrKonqi

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

[dolphin] [Bug 410310] Dolphin Create New doesn't create file

2023-04-17 Thread Philip Murray
https://bugs.kde.org/show_bug.cgi?id=410310

--- Comment #19 from Philip Murray  ---
I've just re-replicated the same problem by simply pasting a very large file
(5GB) into my home directory, then trying to create a new file whilst it is
being written. The above (1) issue happens.

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

[kscreenlocker] [Bug 468181] X11: some french accentuated characters are not possible

2023-04-17 Thread Mickaël B .
https://bugs.kde.org/show_bug.cgi?id=468181

Mickaël B.  changed:

   What|Removed |Added

Version|5.27.3  |5.27.4

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

[kscreenlocker] [Bug 468181] X11: some french accentuated characters are not possible

2023-04-17 Thread Mickaël B .
https://bugs.kde.org/show_bug.cgi?id=468181

--- Comment #9 from Mickaël B.  ---
No problem, I understand your position.
I'll try to use Wayland, as I said.
If I have to fallback to X11 for one reason or another, then I'll change the
password to avoid this bug.
However as you said, if someone has an idea...

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

[plasmashell] [Bug 463080] When switching to the display of months - an empty view

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=463080

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REOPENED|ASSIGNED

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

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

[kate] [Bug 467168] KWrite forgets file history

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467168

--- Comment #3 from thwr...@gmail.com ---
(In reply to Christoph Cullmann from comment #2)
> Can not reproduce that with 22.12.3 in either Kate nor KWrite, tried the
> trick to open a file via Dolphin, still works as intended here.

I tried to remove all lists of recent files from ~/.config/kwriterc. There were
two separate lists of recent files and one list of recent URLs. Now my list of
recent files is growing normally. Let's see if the problem has been fixed. The
new list is absent from kwriterc, by the way, i.e., it's stored somewhere else.

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

[digikam] [Bug 468626] Error in the description of the Rename options

2023-04-17 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=468626

--- Comment #3 from Nicofo  ---
Ah, OK, sorry for my misunderstanding.
But it was not so easy to understand I believe --> thank you for the added
clarifications.

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

[kdenlive] [Bug 468632] New: Crash when picking a library item

2023-04-17 Thread Xavier
https://bugs.kde.org/show_bug.cgi?id=468632

Bug ID: 468632
   Summary: Crash when picking a library item
Classification: Applications
   Product: kdenlive
   Version: 19.12.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: fjr...@hotmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Create a library item from a project
2. Load or create a new project
3. Go to library and pick the newest item


OBSERVED RESULT
Program crashes.

EXPECTED RESULT
Library item must be added to the project and the program shouldn't crash.

SOFTWARE/OS VERSIONS
Linux Mint Cinnamon 20.3

ADDITIONAL INFORMATION

>From GDB:
...

Loading bin playlist...
retain is valid
playlist is valid
init bin
Found  2 clips
dealing with bin clip 0
clip id "2"
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x5a998300] Value 1.00 for parameter
'seekable' out of range [-1 - 0]
[Nuevo Thread 0x7fffc77fe700 (LWP 283077)]
Loaded clip  "2" under id "2"
dealing with bin clip 1
clip id "3"
[matroska,webm @ 0x5a9b9d00] Value 1.00 for parameter 'seekable' out of
range [-1 - 0]
[matroska,webm @ 0x5ac03340] Value 1.00 for parameter 'seekable' out of
range [-1 - 0]
[Nuevo Thread 0x7fff859fc700 (LWP 283078)]
[Nuevo Thread 0x7fff851fb700 (LWP 283079)]
[Nuevo Thread 0x7fff849fa700 (LWP 283080)]
Loaded clip  "3" under id "3"
//
Trying to construct 5 tracks.

[Nuevo Thread 0x7fff73063700 (LWP 283081)]
[Nuevo Thread 0x7fff73022700 (LWP 283082)]
[Nuevo Thread 0x7fff72811700 (LWP 283083)]
[Nuevo Thread 0x7fff86b92700 (LWP 283084)]
### JOB finished 0
### JOB finished 2
### JOB finished 1
[Nuevo Thread 0x7fff62010700 (LWP 283085)]
### JOB finished 3
/// creatclipsfromlist
(QUrl("file:///home/fjrg76/.local/share/kdenlive/library/Main_title.mlt")) true
"-1"
/// createClipFromFile
"/home/fjrg76/.local/share/kdenlive/library/Main_title.mlt" "-1"
"/home/fjrg76/.local/share/kdenlive/library/Main_title.mlt"
/// final xml "\n /home/fjrg76/.local/share/kdenlive/library/Main_title.mlt\n\n"
/// requestAddBinClip "-1"
/// found id "4"
/// constructed 
/// added  true
/// creatclipsfromlist return false
### JOB finished 4
### loadjob COMMIT
### ProjectClip::setproducer
### ClipController::updateProducer
### ClipController::addmasterproducer
Shader compile log: �
Shader compile log: �
kdenlive: ../src/dispatch_common.c:863: epoxy_get_proc_address: La declaración
`0 && "Couldn't find current GLX or EGL context.\n"' no se cumple.
### JOB finished 6
 * * * ** * * *
WARNING + + +
JOB NOT CORRECT FINISH:  6 

--Type  for more, q to quit, c to continue without paging--

Thread 12 "Thread (pooled)" received signal SIGABRT, Aborted.
[Cambiando a Thread 0x7fffacace700 (LWP 283052)]
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No existe el archivo o el
directorio.

(gdb) backtrace 
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x74c3d859 in __GI_abort () at abort.c:79
#2  0x74c3d729 in __assert_fail_base (
fmt=0x7fffe7bbcc1b "%s%s%s:%u: %s%sLa declaración `%s' no se cumple.\n%n",
assertion=0x7fffc5716768 "0 && \"Couldn't find current GLX or EGL
context.\\n\"", file=0x7fffc57166c0 "../src/dispatch_common.c", line=863, 
function=) at assert.c:92
#3  0x74c4efd6 in __GI___assert_fail (
assertion=0x7fffc5716768 "0 && \"Couldn't find current GLX or EGL
context.\\n\"", file=0x7fffc57166c0 "../src/dispatch_common.c", line=863, 
function=0x7fffc57167a0 "epoxy_get_proc_address") at assert.c:101
#4  0x7fffc56f4a9f in ?? () from /lib/x86_64-linux-gnu/libepoxy.so.0
#5  0x7fffc56d0d6f in ?? () from /lib/x86_64-linux-gnu/libepoxy.so.0
#6  0x7fffc57a0f22 in movit::ResourcePool::link_program(unsigned int,
unsigned int, std::vector, std::allocator >,
std::allocator,
std::allocator > > > const&) ()
   from /lib/x86_64-linux-gnu/libmovit.so.8
#7  0x7fffc57a4a7b in
movit::ResourcePool::compile_glsl_program(std::__cxx11::basic_string, std::allocator > const&,
std::__cxx11::basic_string, std::allocator >
const&, std::vector,
std::allocator >, std::allocator, std::allocator > > > const&) ()
   from /lib/x86_64-linux-gnu/libmovit.so.8
#8  0x7fffc5794313 in
movit::EffectChain::compile_glsl_program(movit::Phase*) () from
/lib/x86_64-linux-gnu/libmovit.so.8
#9  0x7fffc5798c72 in movit::EffectChain::construct_phase(movit::Node*,
std::map,
std::allocator > >*) ()
   from /lib/x86_64-linux-gnu/libmovit.so.8
#10 

[kate] [Bug 429818] Autoscroll file a bit to show line context when searching

2023-04-17 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=429818

Andrew Shark  changed:

   What|Removed |Added

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

--- Comment #4 from Andrew Shark  ---
Still valid feature request for Kate 22.12.3

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

[valgrind] [Bug 468401] [PATCH] Add a style file for clang-format

2023-04-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=468401

Paul Floyd  changed:

   What|Removed |Added

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

--- Comment #4 from Paul Floyd  ---
commit 1b3430761f6bda43b8187dbd342b34cb5c99df3f (HEAD -> master, origin/master,
origin/HEAD)
Author: Paul Floyd 
Date:   Mon Apr 17 22:05:30 2023 +0200

Bug 468401 - [PATCH] Add a style file for clang-format

Patch submitted by:
Petr Pavlu 

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

[kate] [Bug 429818] Autoscroll file a bit to show line context when searching

2023-04-17 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=429818

Andrew Shark  changed:

   What|Removed |Added

Version|20.08.2 |22.12.3

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

[digikam] [Bug 468624] Inaccessible remote database causes boot time to take several minutes without even displaying the startup splashscreen

2023-04-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=468624

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Created attachment 158176
  --> https://bugs.kde.org/attachment.cgi?id=158176=edit
database-error

Such a window already exists, which appears for me after less than 1 second.
See the screenshot.

Maik

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

[valgrind] [Bug 468575] Add support for RISC-V

2023-04-17 Thread Petr Pavlu
https://bugs.kde.org/show_bug.cgi?id=468575

--- Comment #9 from Petr Pavlu  ---
(In reply to Paul Floyd from comment #8)
> hginfo fails on several systems
> TLS is, well, tricky
> 
> Are the other failures "reaonable"?

The following is a short summary why the remaining tests fail. However, I'm not
sure yet for any of them what is their underlying problem and still need to do
proper investigation.

> gdbserver_tests/hginfo   (stderrB)

The output has information about an extra lock inside _rtld_local. Likely a
duplicate of bug 87.

> gdbserver_tests/hgtls(stdoutB)

Fails because GDB is not able to determine an address of the variable 'local'.
The test used to pass on my system, possibly something compiler-related.

> memcheck/tests/cdebug_zlib_gnu   (stderr)

Produced backtrace contains rubbish 'at 0x: main (ng long int:3)'
instead of 'at 0x: main (cdebug.c:3)'.

> memcheck/tests/linux/stack_changes   (stdout)
> memcheck/tests/linux/stack_changes   (stderr)

Lots of unexpected invalid writes reported from hello() -> printf().

> memcheck/tests/pointer-trace (stderr)

The second mmap() call in the test unexpectedly fails with -EINVAL.

> memcheck/tests/sh-mem-random (stdout)
> memcheck/tests/sh-mem-random (stderr)

Another unexpected mmap() failure.

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

[Elisa] [Bug 468631] New: Embedded items move upwards and on top of the embedded view title (e.g. "Genres") if sidebar leaves icons mode

2023-04-17 Thread Jack Hill
https://bugs.kde.org/show_bug.cgi?id=468631

Bug ID: 468631
   Summary: Embedded items move upwards and on top of the embedded
view title (e.g. "Genres") if sidebar leaves icons
mode
Classification: Applications
   Product: Elisa
   Version: 22.12.3
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: jackhill3...@gmail.com
  Target Milestone: ---

Created attachment 158175
  --> https://bugs.kde.org/attachment.cgi?id=158175=edit
View selector after entering and leaving icons-mode

SUMMARY

STEPS TO REPRODUCE
1. Make "Genres" the embedded view
2. Shrink the main window until the sidebar goes into icons mode
3. Enlarge the main window until the sidebar leaves icons mode

OBSERVED RESULT
Embedded items overlay the header text

EXPECTED RESULT
Embedded items do not overlay header text

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230416
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.2.10-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

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

[valgrind] [Bug 468606] build: remove "Valgrind relies on GCC" check/output

2023-04-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=468606

Paul Floyd  changed:

   What|Removed |Added

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

--- Comment #2 from Paul Floyd  ---
commit 41a7f59a8838a042813ac20fe1472e55e9bd5697 (HEAD -> master, origin/master,
origin/HEAD)
Author: Paul Floyd 
Date:   Mon Apr 17 21:53:23 2023 +0200

Bug 374596 - inconsistent RDTSCP support on x86_64

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

[okular] [Bug 468630] New: .cbz files containing .webp or .tiff cannot be opened

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468630

Bug ID: 468630
   Summary: .cbz files containing .webp or .tiff cannot be opened
Classification: Applications
   Product: okular
   Version: 22.12.3
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Comicbook backend
  Assignee: okular-de...@kde.org
  Reporter: flampin...@gmail.com
  Target Milestone: ---

SUMMARY
When I try to open a file (.cbz) containing .webp, a message pops up that the
file cannot be opened.

STEPS TO REPRODUCE
1. create any .webp file
2. zip the file with 7z
3. change the file extension from .zip to .cbz
4. try to open the file

OBSERVED RESULT
message: "file cannot be opened"

EXPECTED RESULT
the file opens without problems as if it were if it contained .jpg or .png

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
Okular cant open .webp files either (if you try drag and drop). However the
site (https://okular.kde.org/) says it should be supported.
Okular can open an .tiff file (drag and drop), but if you zip this file and
rename it to .cbz and try to open it, an error will appear.

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

[kwin] [Bug 443661] Cursor shows smaller cursor on titlebars (Wayland session)

2023-04-17 Thread Dragoon Aethis
https://bugs.kde.org/show_bug.cgi?id=443661

Dragoon Aethis  changed:

   What|Removed |Added

 CC||k...@dragonic.eu

--- Comment #3 from Dragoon Aethis  ---
One more +1, happens with OpenZone theme too:
- https://github.com/ducakar/openzone-cursors
- https://www.opendesktop.org/p/99/

I don't have any display scaling enabled (1440p native at 100%), did not force
font DPI either. The cursor gets downscaled a little when hovering over any
window chrome or the KWin debug console.

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

[digikam] [Bug 468626] Error in the description of the Rename options

2023-04-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=468626

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||8.1.0
  Latest Commit||https://invent.kde.org/grap
   ||hics/digikam/commit/a15bdcb
   ||dc2a1085b18f22eed3e53ed0442
   ||975e7b
 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Maik Qualmann  ---
Git commit a15bdcbdc2a1085b18f22eed3e53ed0442975e7b by Maik Qualmann.
Committed on 17/04/2023 at 19:45.
Pushed by mqualmann into branch 'master'.

add possible rename options to the description
FIXED-IN: 8.1.0

M  +1-1NEWS
M  +3-3   
core/utilities/advancedrename/parser/options/sequencenumberoption.cpp

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

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

[krita] [Bug 464257] Layer effects not saved if they're the only thing changed.

2023-04-17 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=464257

--- Comment #7 from Tiar  ---
Master bug of the uuid issue (all issues where the layer style of the
duplicated layer is the same as the layer style of the original layer) is bug
457553.

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

[krita] [Bug 457553] Duplicating layers with layer styles, and changing style on new layer results in wrong serialization and both layer have same layer styles after load.

2023-04-17 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=457553

Tiar  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||9c847ba5c8ec912bf3c4d318ed5
   ||c654a89400418
 Resolution|--- |FIXED

--- Comment #5 from Tiar  ---
Fixed in 9c847ba5c8ec912bf3c4d318ed5c654a89400418.

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

[krita] [Bug 457553] Duplicating layers with layer styles, and changing style on new layer results in wrong serialization and both layer have same layer styles after load.

2023-04-17 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=457553

Tiar  changed:

   What|Removed |Added

 CC||knowz...@pokemail.net

--- Comment #4 from Tiar  ---
*** Bug 451385 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 451385] Copy and pasting a layer with an existing layerstyle fails to save changes

2023-04-17 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=451385

Tiar  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||tamtamy.tym...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #3 from Tiar  ---


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

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

[kwin] [Bug 468547] Second monitor have no hdmi signal after waking from sleep

2023-04-17 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=468547

--- Comment #4 from Andrew Shark  ---
It is some kind unstable. This time after first sleep the hdmi mon worked
normal. Then after second sleep it was not working. Then after third sleep it
was working again.

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

[kwin] [Bug 468547] Second monitor have no hdmi signal after waking from sleep

2023-04-17 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=468547

--- Comment #3 from Andrew Shark  ---
Created attachment 158174
  --> https://bugs.kde.org/attachment.cgi?id=158174=edit
drm_info after sleep (hdmi monitor not working)

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

[kwin] [Bug 468547] Second monitor have no hdmi signal after waking from sleep

2023-04-17 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=468547

--- Comment #2 from Andrew Shark  ---
Created attachment 158173
  --> https://bugs.kde.org/attachment.cgi?id=158173=edit
drm_info before sleep (both monitors working)

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

[valgrind] [Bug 468606] build: remove "Valgrind relies on GCC" check/output

2023-04-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=468606

Paul Floyd  changed:

   What|Removed |Added

 CC||pjfl...@wanadoo.fr

--- Comment #1 from Paul Floyd  ---
You didn't add the patch. Do you mean removing

# Check for the compiler support
if test "${GCC}" != "yes" ; then
   AC_MSG_ERROR([Valgrind relies on GCC to be compiled])
fi

?

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

[Akonadi] [Bug 450217] (SEGV) Crash in Akonadi::Server::AkonadiServer::connectionDisconnected

2023-04-17 Thread Tim D
https://bugs.kde.org/show_bug.cgi?id=450217

Tim D  changed:

   What|Removed |Added

 CC||veeh...@zoho.com

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

[frameworks-kxmlgui] [Bug 461937] Kate doesn't retain last non-maximised window size after closing it in maximised state

2023-04-17 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=461937

Christoph Cullmann  changed:

   What|Removed |Added

Product|kate|frameworks-kxmlgui
  Component|application |general
Version|22.08.3 |unspecified
   Assignee|kwrite-bugs-n...@kde.org|kdelibs-b...@kde.org

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

[digikam] [Bug 425263] Blur Level on Face Detection

2023-04-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=425263

Maik Qualmann  changed:

   What|Removed |Added

 CC||simon.gasch...@gmx.de

--- Comment #2 from Maik Qualmann  ---
*** Bug 468629 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 468629] Exclude individual images from face recognition

2023-04-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=468629

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Maik Qualmann  ---


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

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

[kwin] [Bug 465252] Disabling "middle-click paste" breaks pasting URL from Firefox to other apps

2023-04-17 Thread Dragoon Aethis
https://bugs.kde.org/show_bug.cgi?id=465252

Dragoon Aethis  changed:

   What|Removed |Added

 CC||k...@dragonic.eu

--- Comment #6 from Dragoon Aethis  ---
Relevant downstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1791417

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

[digikam] [Bug 468629] New: Exclude individual images from face recognition

2023-04-17 Thread Simon Gaschler
https://bugs.kde.org/show_bug.cgi?id=468629

Bug ID: 468629
   Summary: Exclude individual images from face recognition
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: simon.gasch...@gmx.de
  Target Milestone: ---

The recognition of faces is very good, as long as you haven't assigned blurry
images of a person. To improve facial recognition, it would be helpful to be
able to exclude individual images from the recognition.

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

[digikam] [Bug 468626] Error in the description of the Rename options

2023-04-17 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=468626

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Everything is correct, some options only refer to "c" for example [c,step]
others refer to option "f" for example.

Maik

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

[kate] [Bug 466316] Sidebar section arrangement forgotten when switching sessions

2023-04-17 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=466316

Christoph Cullmann  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||cullm...@kde.org
 Ever confirmed|0   |1

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

[plasmashell] [Bug 468628] New: Plasmashell memory usage increase steadly over time.

2023-04-17 Thread Miguel Rozsas
https://bugs.kde.org/show_bug.cgi?id=468628

Bug ID: 468628
   Summary: Plasmashell memory usage increase steadly over time.
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mig...@rozsas.eng.br
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 158172
  --> https://bugs.kde.org/attachment.cgi?id=158172=edit
output of: 'while /bin/true ; do date >> tmp/plasmashell_mem.log; ps -e -o
comm,%cpu,cputime,etime,rss,%mem | grep -E  "plasmashell|COMMAND" | tee -a
tmp/plasmashell_mem.log; sleep 30m; done'

SUMMARY
Plamashell starts using about 400kbytes of memory and after 5:30h it is using
more than 8G ! 
Must be a memory leak somewhere.


STEPS TO REPRODUCE
I collected the memory used by plasmasheel with a simple script. The data is
attached.
Note that, between 12:00h and 13:30h it was my lunch time, the computer was
idle, even so, the memory usage increased from 3665792 to 5375696 bytes.
After 5:30h since the KDE was started it was using 8142588 bytes.


OBSERVED RESULT
Memory usage increase over time.

EXPECTED RESULT
A more discrete usage of memory.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230413
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.2.10-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: ASUS

ADDITIONAL INFORMATION
Please , see the attached file. It has the used plasmashell memory in 30m
intervals.

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

[KScreen] [Bug 468627] New: Desktop and task manager off after waking up

2023-04-17 Thread joseteluisete
https://bugs.kde.org/show_bug.cgi?id=468627

Bug ID: 468627
   Summary: Desktop and task manager off after waking up
Classification: Plasma
   Product: KScreen
   Version: 5.27.4
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: jos...@tutamail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Activate Screen Energy Saving
· System Settings > Hardware > Power Management > Energy Saving > Screen Energy
Saving: 1 minute (or more)
2. Wait until the screen turns off
3. Move the mouse or press a key to wake up the screen

OBSERVED RESULT
The Desktop and the Task manager are off. I don't see them.
The mouse and the keyboard work normally.
I see the opened applications and can change from one to the next with
Meta+Tab.
I can also launch applications with the keyboard (Meta+E = Dolphin for example)

EXPECTED RESULT
The Desktop and the Mask Manager are normally restored.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel: 6.1.23-1

ADDITIONAL INFORMATION
Intel i9 9900 CPU. GPU UHD 630 (integrated). 32 GB RAM.
One monitor is connected with DVI and a TV is connected with HDMI.
I think this last piece of information is very important. I don't know if this
bug happens using only 1 monitor.

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

[krita] [Bug 467729] Opening Layer Styles editor resets gradient overlay colors if 0. Foreground to Background is selected and document hasn't been saved/closed/reopened.

2023-04-17 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=467729

--- Comment #1 from Tiar  ---
Relevant: bug 445135 and commit 46e8344d6fa2deebb9d5e6da59f9b6d9bc7f6f2c

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

[kate] [Bug 467048] Exported default shortcuts are missing entries like "copy"

2023-04-17 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=467048

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org
 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #1 from Christoph Cullmann  ---
Tried that, works for me, contains stuff like

edit_copy=Ctrl+C; Ctrl+Ins
edit_copy_html=none
edit_create_multi_cursor_down=Ctrl+Alt+Down
edit_create_multi_cursor_from_sel=Alt+Shift+I
edit_create_multi_cursor_up=Ctrl+Alt+Up
edit_cut=Ctrl+X; Shift+Del
edit_deselect=Ctrl+Shift+A
edit_filter=Ctrl+\\
edit_find=Ctrl+F
edit_find_multicursor_all_occurrences=Ctrl+Alt+Shift+J
edit_find_multicursor_next_occurrence=Alt+J
edit_find_next=F3
edit_find_prev=Shift+F3
edit_find_selected=Ctrl+H
edit_find_selected_backwards=Ctrl+Shift+H
edit_paste=Ctrl+V; Shift+Ins
edit_paste_selection=Ctrl+Shift+Ins

KDE Frameworks 
Version 5.105.0

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

[Discover] [Bug 468162] Deployments appearing in all searches

2023-04-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=468162

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

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

[kate] [Bug 467168] KWrite forgets file history

2023-04-17 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=467168

Christoph Cullmann  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Cullmann  ---
Can not reproduce that with 22.12.3 in either Kate nor KWrite, tried the trick
to open a file via Dolphin, still works as intended here.

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

[kate] [Bug 467160] Kate segfaulted when closing

2023-04-17 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=467160

Christoph Cullmann  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||cullm...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Christoph Cullmann  ---
I reviewed the code, see no reason why this should crash there and can't
reproduce.

If somebody can reproduce this with e.g. master, please re-open.

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

[digikam] [Bug 468626] Error in the description of the Rename options

2023-04-17 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=468626

Nicofo  changed:

   What|Removed |Added

Version|unspecified |8.0.0

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

[digikam] [Bug 468626] New: Error in the description of the Rename options

2023-04-17 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=468626

Bug ID: 468626
   Summary: Error in the description of the Rename options
Classification: Applications
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: AdvancedRename-dialog
  Assignee: digikam-bugs-n...@kde.org
  Reporter: nic...@tuxfamily.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. In the rename tool window, click on the "Show a list of all available
options" button
2. Al the options are listed, amongs other;
  #[options,start]Sequence number (custom start) 
  #[options,step] Sequence number (custom step) 
3. I suppose that second line is wrong (a unique number in brackets is
considered as the custom start and not the custom step: example: #[3])

4. Note: but the following syntax is missing in the description (a sequence
number with custom start but without options is valid): 
  #[start] Sequence number (custom start) 

Note: see image of the error: https://imgur.com/Et6K1BZ

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

[plasmashell] [Bug 468608] Autostart programs do not launch on login

2023-04-17 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=468608

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---
Can you run `kreadconfig5 --file startkderc --group General --key systemdBoot`
in a terminal window and see what it says? If it says "true", then try the
following:

1. Run `kwriteconfig5 --file startkderc --group General --key systemdBoot
false` in a terminal window
2. reboot

If that fixes the issue, we know it's a problem with the systemd autostart
stuff. Then please re-enable systemd boot by deleting the file
~/.config/startkderc, and then reboot again.

After the reboot, please run
`/usr/lib/systemd/user-generators/systemd-xdg-autostart-generator` in a
terminal and and paste the text that appears, if anything.

Thanks!

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

[kdiff3] [Bug 468492] KDiff3 crashes when used as Git mergetool

2023-04-17 Thread michael
https://bugs.kde.org/show_bug.cgi?id=468492

michael  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from michael  ---
Thanks the bug seems only to trigger if wordwrap is on I generally have it off.
Which explains why I haven't run into it before.

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

[digikam] [Bug 468616] Customizable statusbar information

2023-04-17 Thread Petr Schonmann
https://bugs.kde.org/show_bug.cgi?id=468616

--- Comment #3 from Petr Schonmann  ---
Ok, then. Should be possible to have at least this info in statusbar
${LAST_DIR_OF_FILEPATH}/${FILENAME} ?

For example

/mnt/snorlax/Photos/Scan/digikam.blah > Scan/digikam.blah

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

[kwin] [Bug 468625] New: Can't use virtual desktops after update

2023-04-17 Thread maxlefou
https://bugs.kde.org/show_bug.cgi?id=468625

Bug ID: 468625
   Summary: Can't use virtual desktops after update
Classification: Plasma
   Product: kwin
   Version: 5.27.4
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: buttbad...@gmail.com
  Target Milestone: ---

Created attachment 158171
  --> https://bugs.kde.org/attachment.cgi?id=158171=edit
A video showing the behavior

SUMMARY
First, sorry if it's posted in the wrong category. Fact is, I'm not actually
sure what exactly cause the glitch to happen. I assumed it's KWin since it's
what I use but maybe I mistake.

Since the recent updates, I cannot use virtual desktops anymore. Only one
desktop works. Any additional desktop will make it black, with no bars or
widgets, making it impossible to leave it without the key shortcuts. Windows
can still appear in this desktop if they are moved to it.

STEPS TO REPRODUCE
1. Start the Plasma desktop
2. Add a virtual desktop if there's none
3. Switch to this virtual desktop

OBSERVED RESULT
The virtual desktop is completely black. Doesn't display any widgets, bar or
wallpaper. The mouse still shows, and a window that is moved to this desktop
will behave normally. When maximized in this desktop, the window acts like if
there were no bars at all. The only way to get out of this desktop is to use
the key shortcuts. Happens to every additional virtual desktops created. Right
click doesn't work either.

EXPECTED RESULT
The virtual desktop should show with the bars, widgets and wallpaper and should
be fully functional.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.2.11
(available in About System)
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Using X11. Haven't tried on Wayland and can't use it anyway.

ADDITIONAL INFORMATION
I included a video showing the behavior

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

[frameworks-kio] [Bug 465454] plasmashell crashes in QTextDocument::docHandle with google chrome youtube video behind web proxy

2023-04-17 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=465454

--- Comment #24 from Fushan Wen  ---
Git commit 35ef5262cdd275bcd872c07445ec1f31131b3d84 by Fushan Wen.
Committed on 17/04/2023 at 17:53.
Pushed by fusionfuture into branch 'master'.

dataengines/mpris2: don't recreate PlayerControl for the same container

It's unnecessary and inefficient.


(cherry picked from commit 402ebdbde1348b7e5a5e4c4ed7b6fed366fc80b6)

M  +4-0dataengines/mpris2/multiplexedservice.cpp
M  +5-0dataengines/mpris2/playercontrol.h

https://invent.kde.org/plasma/plasma-workspace/commit/35ef5262cdd275bcd872c07445ec1f31131b3d84

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

[digikam] [Bug 468624] New: Inaccessible remote database causes boot time to take several minutes without even displaying the startup splashscreen

2023-04-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=468624

Bug ID: 468624
   Summary: Inaccessible remote database causes boot time to take
several minutes without even displaying the startup
splashscreen
Classification: Applications
   Product: digikam
   Version: 8.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Database-Mysql
  Assignee: digikam-bugs-n...@kde.org
  Reporter: michael2macdon...@gmail.com
  Target Milestone: ---

SUMMARY
When the remote MySQL database is inaccessible, Digikam takes several minutes
to boot before it displays an error because of the inaccessible database.
During this time, the startup splash screen does not display and there is no
indication that the program has started which can cause the user to attempt to
start the program again and result in multiple instances of Digikam being
started.

STEPS TO REPRODUCE
1. Setup digikam with a remote database
2. Shutdown the database server, turn off wifi, or do similar action to prevent
a connection to the server
3. Start digikam

OBSERVED RESULT
Digikam starts, but no splash screen is displayed and it takes 1-2 minutes
before the database connection error window appears.

EXPECTED RESULT
Startup splash should show while it is trying to connect to the database. If
possible (I understand practical limitations when it comes to setting the
time-out duration for trying to connect to servers), decrease the duration
before it times out and displays the error. An alternative would be to open a
loading window or display a loading status if the database does not connect
within 2 seconds, but before the connection time-out, to inform the user that
it is trying to connect to the database. For example: "Failed to connect to
database... Retrying for X seconds..."

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

  1   2   3   >