date:20220101

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

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

   What|Removed |Added

   Version Fixed In||7.5.0

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

[digikam] [Bug 381597] Show camera make and model in icon view.

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

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

   What|Removed |Added

   Version Fixed In||7.5.0

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

[digikam] [Bug 376330] Add new option to "Print title" for Presentation tool

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

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

   What|Removed |Added

Summary|"Move to bottom/top"|Add new option to "Print
   |buttons, d and "Print |title" for Presentation
   |title" for presentation |tool
Version|5.5.0   |7.5.0

--- Comment #2 from caulier.gil...@gmail.com ---
1/ Move buttons are present since a while in this plugin.
2/ Drag and drop are not possible, but a '+' button allow to add new items
quickly in the list.
3/ Print Title option still missing in the plugin.

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

[digikam] [Bug 432526] Include Platform Input Context Qt plugin in AppImage bundle

2022-01-01 Thread Tyson Tan

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

--- Comment #8 from Tyson Tan  ---
Thank you, Gilles! :D

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

[kstars] [Bug 447753] Kstars crashes connecting to Ekos on MacOS

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

--- Comment #8 from Castor Fu  ---
Sorry, the whole mount error was a red herring because of not copying enough of
the environment over.  

This looks like a better trace:
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x42d80)
  * frame #0: 0x7fff209ac552 libsystem_platform.dylib`_platform_strlen + 18
frame #1: 0x000100019d13 kstars`QDebug::operator<<(char const*)
[inlined] QString::fromUtf8(str="", size=-1) at qstring.h:706:63 [opt]
frame #2: 0x000100019d06 kstars`QDebug::operator<<(char
const*)(this=0x7ffeefbfd458, t="") at qdebug.h:159:62 [opt]
frame #3: 0x0001000de2cc
kstars`INDIListener::registerProperty(this=0x00013893e030, prop=Property @
0x7ffeefbfd4a0) at indilistener.cpp:241:33 [opt]
frame #4: 0x0001000e0613 kstars`QtPrivate::QSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
[inlined] QtPrivate::FunctorCall,
QtPrivate::List, void, void
(INDIListener::*)(INDI::Property)>::call(f=, o=,
arg=)(INDI::Property), INDIListener*, void**) at
qobjectdefs_impl.h:152:13 [opt]
frame #5: 0x0001000e05dc kstars`QtPrivate::QSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
[inlined] void QtPrivate::FunctionPointer::call,
void>(f=, o=, arg=)(INDI::Property),
INDIListener*, void**) at qobjectdefs_impl.h:185:13 [opt]
frame #6: 0x0001000e05dc kstars`QtPrivate::QSlotObject,
void>::impl(which=, this_=, r=,
a=, ret=) at qobjectdefs_impl.h:418:17 [opt]
frame #7: 0x000104180d39 QtCore`QObject::event(this=0x00013893e030,
e=0x00012c2996f0) at qobject.cpp:1314:18 [opt]
frame #8: 0x000103356586
QtWidgets`QApplicationPrivate::notify_helper(this=, rece

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

[digikam] [Bug 432526] Include Platform Input Context Qt plugin in AppImage bundle

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

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

   What|Removed |Added

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

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

[digikam] [Bug 435897] Package fcitx support for digikam's appimage

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

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

   What|Removed |Added

   Version Fixed In||7.5.0
 Resolution|DUPLICATE   |FIXED

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

[digikam] [Bug 387482] Color names for Clean Frames theme are not translatable

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

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

   What|Removed |Added

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

--- Comment #3 from caulier.gil...@gmail.com ---
I check with French and German translations under MacOS, and both are "Clean
Frames" theme translated in the plugin now.

I close this file now.

Gilles Caulier

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

[digikam] [Bug 297316] translations and docs off by default

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

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

   What|Removed |Added

  Component|Documentation   |Tarball-Compilation

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

[digikam] [Bug 297316] translations and docs off by default

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

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

   What|Removed |Added

   Version Fixed In||7.5.0

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

[systemsettings] [Bug 447783] Plasma uses a language that has been removed and is no longer in the installed language list

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

doggoofsp...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from doggoofsp...@gmail.com ---
(In reply to Patrick Silva from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 420268 ***

Nope, although both of our reports say that the problem is the use of a removed
language, I was aware of bug#420268 and emphasised the fact that the language
dissapeared from the menu while in bug#420268 the language remains

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

[frameworks-ktexteditor] [Bug 446189] Arrow keys sometimes wrongly extend selection

2022-01-01 Thread Kishore Gopalakrishnan

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

Kishore Gopalakrishnan  changed:

   What|Removed |Added

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

--- Comment #2 from Kishore Gopalakrishnan  ---
I can no longer reproduce this on KDE Neon Unstable, so I'll mark this as
fixed.

SOFTWARE VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-43-generic (64-bit)
Graphics Platform: X11
Processors: 2 × AMD EPYC-Rome Processor
Memory: 1.9 GiB of RAM
Graphics Processor: virgl

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

[konsole] [Bug 441902] Splitting the view resizes whole window in a dual monitor setup

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

white...@gmail.com changed:

   What|Removed |Added

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

--- Comment #9 from white...@gmail.com ---
As I mentioned in my previous comments, this is still happening to me.

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

[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows

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

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

   What|Removed |Added

Version|7.3.0   |7.4.0

--- Comment #15 from caulier.gil...@gmail.com ---
Hi and happy new year.

with next 7.5.0, we update internal KF5 framework from 5.84 to 5.89. Please
double check with this version for Windows to see if it can fix the problem..
Installer is here ::

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

Thanks in advance

Gilles Caulier

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

[digikam] [Bug 431063] Hanging Process After Closing Application in MS Windows

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

ds.ba...@gmail.com changed:

   What|Removed |Added

 CC||ds.ba...@gmail.com

--- Comment #14 from ds.ba...@gmail.com ---
Same issue with 7.4.0 (Stable Release) in Windows 11 and Windows 10

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

[Spectacle] [Bug 446882] Right click when taking a rectangular screenshot reports failure when using "On click" setting on X11

2022-01-01 Thread Bharadwaj Raju

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

Bharadwaj Raju  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/grap
   ||hics/spectacle/commit/2f9bb
   ||bfc2000dd118ea7fdeb2b8ffa28
   ||b65f0c71
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #8 from Bharadwaj Raju  ---
Git commit 2f9bbbfc2000dd118ea7fdeb2b8ffa28b65f0c71 by Bharadwaj Raju, on
behalf of Antonio Prcela.
Committed on 02/01/2022 at 05:46.
Pushed by bharadwaj-raju into branch 'release/21.12'.

Do not show error message when canceling with rightclick while in rectangluar
mode

Don't treat it as an error when 'on click' is enabled and a user presses right
mouse
click while taking a screenshot with rectangluar mode, instead of drawing a
rectangle
with left click.
Instead, treat it as a simple cancel without failure.

M  +3-1src/SpectacleCore.cpp

https://invent.kde.org/graphics/spectacle/commit/2f9bbbfc2000dd118ea7fdeb2b8ffa28b65f0c71

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

[kstars] [Bug 447753] Kstars crashes connecting to Ekos on MacOS

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

--- Comment #7 from Castor Fu  ---
Hmm, I've tried adding some debug statements, and I can't seem to get it to
crash when running it within the VM, but after turning on logging in the mount
code, I see the following on a crash (the XX lines are ones added by me).  It
looks like maybe there's a race installing some code that mountbox.qml is
using?On successful runs I don't see the warnings about modules not being
installed.


[2022-01-01T21:05:28.425 PST INFO ][   org.kde.kstars.ekos] -
"Telescope Simulator is online."
[2022-01-01T21:05:28.455 PST DEBG ][ org.kde.kstars.ekos.mount] - XXA 
QObject(0x0)
[2022-01-01T21:05:28.619 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:4:1: module "QtQuick.Controls.Styles" is not
installed
 import QtQuick.Controls.Styles 1.4
 ^
[2022-01-01T21:05:28.620 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:3:1: module "QtQuick.Layouts" is not installed
 import QtQuick.Layouts 1.1
 ^
[2022-01-01T21:05:28.620 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:2:1: module "QtQuick.Controls" is not installed
 import QtQuick.Controls 1.4
 ^
[2022-01-01T21:05:28.620 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:4:1: module "QtQuick.Controls.Styles" is not
installed
 import QtQuick.Controls.Styles 1.4
 ^
[2022-01-01T21:05:28.621 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:3:1: module "QtQuick.Layouts" is not installed
 import QtQuick.Layouts 1.1
 ^
[2022-01-01T21:05:28.621 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:2:1: module "QtQuick.Controls" is not installed
 import QtQuick.Controls 1.4
 ^
[2022-01-01T21:05:28.621 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:4:1: module "QtQuick.Controls.Styles" is not
installed
 import QtQuick.Controls.Styles 1.4
 ^
[2022-01-01T21:05:28.621 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:3:1: module "QtQuick.Layouts" is not installed
 import QtQuick.Layouts 1.1
 ^
[2022-01-01T21:05:28.621 PST WARN ][   default] -
qrc:/qml/mount/mountbox.qml:2:1: module "QtQuick.Controls" is not installed
 import QtQuick.Controls 1.4
 ^
[2022-01-01T21:05:28.624 PST DEBG ][ org.kde.kstars.ekos.mount] - XXY  
QQuickItem(0)  m_BaseObj QQuickItem(0)
[2022-01-01T21:05:28.624 PST DEBG ][ org.kde.kstars.ekos.mount] - XXX
m_leftRightCheck null

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

[lattedock] [Bug 447609] Super/meta randomly stops opening application menu widget in latte top panel

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

--- Comment #2 from antint...@gmail.com ---
(In reply to Michail Vourlakos from comment #1)
> Probably a kwin issue. I never have such issue in my system. It should also
> be reproducable with plasma panels. Users have reported that usually occurs
> after opening a computer after sleeping it. Nothing related to Latte.
> 
> Take also note that Latte does not require from you to set a shortcut.
> 
> Waiting concrete way to reproduce.

So should I file another bug under kwin? I'm not 100% sure, but I think I
remember a few times where the bug occurred randomly during normal usage with
screen on, so I'm not sure how to find a concrete way to reproduce it.

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

[frameworks-plasma] [Bug 447092] Google chrome application icons are shown as Google Chrome icon after upgrading frameworks

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

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

[okular] [Bug 447023] Unable to open certain .cbr files

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

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

[kontact] [Bug 446746] Cannot find any shared object files

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

--- Comment #7 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 444560] the pressure doesn't work

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

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

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

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

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

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

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

[konsole] [Bug 441902] Splitting the view resizes whole window in a dual monitor setup

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

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

[docs] [Bug 447812] New: Konsole SSH Manager plugin

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

Bug ID: 447812
   Summary: Konsole SSH Manager plugin
   Product: docs
   Version: unspecified
  Platform: unspecified
OS: Unspecified
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Missing Content
  Assignee: kde-doc-engl...@kde.org
  Reporter: 2wxsy5823...@opayq.com
  Target Milestone: ---

SUMMARY

Konsole has a SSH Manager plugin (added in [1]), and is already available in
stable versions, but I cannot find any documentation regarding the plugin at
[2].


[1]
https://invent.kde.org/utilities/konsole/-/commit/05484db2883319e211e87054a891843279ace358
[2] https://docs.kde.org/stable5/en/konsole/konsole/konsole.pdf

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

[ksmserver] [Bug 436318] Save session doesn't work under Wayland

2022-01-01 Thread Kishore Gopalakrishnan

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

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

[Spectacle] [Bug 447811] New: Spectacle when run with "-bcr" on the commandline always saves a file

2022-01-01 Thread Kelvie Wong

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

Bug ID: 447811
   Summary: Spectacle when run with "-bcr" on the commandline
always saves a file
   Product: Spectacle
   Version: 21.08.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: kel...@kelvie.ca
CC: k...@david-redondo.de
  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
***


STEPS TO REPRODUCE
1. Run `spectacle -bcr` in the commandline, to take a rectangular area, and
copy it to the clipboard without prompts.
2. Select a rectangular area


OBSERVED RESULT

The screenshot is in the clipboard, but it is also saved in ~/Pictures (which
is my default save location, but I do not have spectacle configured to auto
save screenshots)

EXPECTED RESULT

There not be a PNG file in my ~/Pictures directory, just the clipboard.

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

ADDITIONAL INFORMATION

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

[konsole] [Bug 447810] Font is not rendered using a fixed grid causing alignment issues

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

--- Comment #1 from xsr...@gmail.com ---
(In reply to xsrvmy from comment #0)
> Created attachment 145035 [details]
> Example of bug, note the misalignment
> 
> 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
> ***
> Unlike other terminals, Konsole doesn't appear to follow a strict grid. This
> means that weird behaviour happens if a fallback font is wider/narrower than
> the original.
> 
> STEPS TO REPRODUCE
> 1. Download victor mono font and set it as the Konsole font
> 2. Type in multiple lunate epsilons (ϵ)
> 
> OBSERVED RESULT
> Assuming the fallback font has a more standard width, the cursor becomes
> misaligned with the text. Additionally, comparing with adjacent column 
> 
> EXPECTED RESULT
> 
> 
> SOFTWARE/OS VERSIONS
> Linux/KDE Plasma: 
> (available in About System)
> KDE Plasma Version: 5.23.4-1
> KDE Frameworks Version: 5.89.0-1
> Qt Version: 5.15.2
> (Note: these are pacman package versions, I'm using sway at the moment)
> 
> ADDITIONAL INFORMATION

(Oops didn't finish my sentence)
Additionally, comparing with the adjacent row, the text is not grid aligned.

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

[konsole] [Bug 447810] New: Font is not rendered using a fixed grid causing alignment issues

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

Bug ID: 447810
   Summary: Font is not rendered using a fixed grid causing
alignment issues
   Product: konsole
   Version: 21.12.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: xsr...@gmail.com
  Target Milestone: ---

Created attachment 145035
  --> https://bugs.kde.org/attachment.cgi?id=145035=edit
Example of bug, note the misalignment

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
***
Unlike other terminals, Konsole doesn't appear to follow a strict grid. This
means that weird behaviour happens if a fallback font is wider/narrower than
the original.

STEPS TO REPRODUCE
1. Download victor mono font and set it as the Konsole font
2. Type in multiple lunate epsilons (ϵ)

OBSERVED RESULT
Assuming the fallback font has a more standard width, the cursor becomes
misaligned with the text. Additionally, comparing with adjacent column 

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.23.4-1
KDE Frameworks Version: 5.89.0-1
Qt Version: 5.15.2
(Note: these are pacman package versions, I'm using sway at the moment)

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 447783] Plasma uses a language that has been removed and is no longer in the installed language list

2022-01-01 Thread Patrick Silva

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

Patrick Silva  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||bugsefor...@gmx.com
 Resolution|--- |DUPLICATE

--- Comment #1 from Patrick Silva  ---


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

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

[systemsettings] [Bug 420268] Removed language reappears in the languages list after re-login and is applied to Plasma

2022-01-01 Thread Patrick Silva

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

Patrick Silva  changed:

   What|Removed |Added

 CC||doggoofsp...@gmail.com

--- Comment #12 from Patrick Silva  ---
*** Bug 447783 has been marked as a duplicate of this bug. ***

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

[Elisa] [Bug 447809] New: Categories out of order after choosing embedding

2022-01-01 Thread plentz

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

Bug ID: 447809
   Summary: Categories out of order after choosing embedding
   Product: Elisa
   Version: 21.12.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: rplen...@gmail.com
  Target Milestone: ---

Created attachment 145034
  --> https://bugs.kde.org/attachment.cgi?id=145034=edit
A screenshot of an active Elisa window. In the left, the category "Tracks" is
selected but the albums are displayed instead. Both "Tracks" and "Albums" are
circled red.

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


STEPS TO REPRODUCE
1. Open Elisa configuration (Ctrl+Shit+,)
2. Chose any category to embed
3. Apply and then change to default settings (no embed category)

OBSERVED RESULT
After reload the category embedded, it is pushed to the end of the columns but
still behave as the default sidebar. (When clicking on Tracks, it goes to
Albums; Files to Artists; etc)

EXPECTED RESULT
The name of the category should go back to its place.

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

ADDITIONAL INFORMATION
If you keep changing categories they keep scrambled at the end of the sidebar.

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

[systemsettings] [Bug 447808] New: Integrate mozc to Keyboard layout

2022-01-01 Thread dvdnet89

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

Bug ID: 447808
   Summary: Integrate mozc to Keyboard layout
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_keyboard
  Assignee: plasma-b...@kde.org
  Reporter: tantonoda...@gmail.com
CC: butir...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  I click Super button
2.  Chose System Language 
3. Chose Japanese layout with mozc

OBSERVED RESULT
There is no selection to chose mozc by default

EXPECTED RESULT
I should choose mozc as a default input for japanese

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  KDE Neon 5.23 User edition
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version:  5.89
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Mozc become de-facto most widespread way to input Japanese language because
user can convert the characters easily and it will be really helpful if we can
use it in advance instead of install this feature externally.

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

[krita] [Bug 447807] New: Document.refreshProjection() does not refresh for Fill Layers

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

Bug ID: 447807
   Summary: Document.refreshProjection() does not refresh for Fill
Layers
   Product: krita
   Version: 5.0.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: jung...@hotmail.com
  Target Milestone: ---

SUMMARY
When using the Python Scripting to modify parameters for a Fill Layer, the fill
layer does not update after calling refreshProjection().

STEPS TO REPRODUCE
1.  Create a new document.
2.  Create a new Fill Layer. Choose any color except green (because my example
script will try to make it green)
3.  Run the following script:

## SCRIPT START ##
from krita import *
import xml.etree.ElementTree as ET

activeDoc = Krita.instance().activeDocument()
node = activeDoc.nodeByName("Fill Layer 1")
config = node.filterConfig()
properties = config.properties()
xmlObj = ET.fromstring(properties["color"])
xmlObj[0].set("r", "0.00")
xmlObj[0].set("g", "1.00")
xmlObj[0].set("b", "0.00")
result = ET.tostring(xmlObj, encoding="unicode")
properties["color"] = result
config.setProperty("color", properties["color"])
node.setGenerator("color", config)
activeDoc.refreshProjection()
## SCRIPT END ##

OBSERVED RESULT
The Fill Layer remains the old color. It will update correctly if you right
click the layer and go to "Properties".

EXPECTED RESULT
The Fill Layer color change should be reflected on the canvas.

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

ADDITIONAL INFORMATION
I have reproduced this issue on 2 different machines:
- Core i9 Desktop on Windows 10
- Core i7 Wacom MobileStudio Pro on Windows 10

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

[krita] [Bug 447806] New: "Enable native file dialogs" setting is enabled by default for appimages, despite the fact that the file picker will not display previews in that case

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

Bug ID: 447806
   Summary: "Enable native file dialogs" setting is enabled by
default for appimages, despite the fact that the file
picker will not display previews in that case
   Product: krita
   Version: 5.0.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: tomtomtomreportin...@gmail.com
  Target Milestone: ---

SUMMARY
I did not realize this until after a talk with a friend who had this setting
enabled, and thus didn't realize file picker previews were a feature: For
appimage users, "Enable native file dialogs" is enabled by default, despite the
fact that having it enabled will grant an inferior file picker, such that the
previews on the side of the file picker will not display at all.

STEPS TO REPRODUCE
1. Open Krita with a fresh profile.
2. File -> Open and select an image.

OBSERVED RESULT
There is no preview due to the fact that "Enable native file dialogs" is
enabled by default.

EXPECTED RESULT
"Enable native file dialogs" should be disabled by default for appimages if it
gives an objectively inferior experience. Or, if this is considered a bug with
the setting itself, then the preview should properly display regardless of what
the setting is set to.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.12.12 (appimage)

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

[systemsettings] [Bug 447764] Configure Firewall crashed while viewing connections

2022-01-01 Thread Nicolas Fella

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

Nicolas Fella  changed:

   What|Removed |Added

   Assignee|aleix...@kde.org|plasma-b...@kde.org
 CC||nicolas.fe...@gmx.de,
   ||tcanabr...@kde.org
Product|kde-cli-tools   |systemsettings
  Component|general |kcm_firewall

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

[krita] [Bug 447805] New: File picker previews don't properly render small images

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

Bug ID: 447805
   Summary: File picker previews don't properly render small
images
   Product: krita
   Version: 5.0.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: tomtomtomreportin...@gmail.com
  Target Milestone: ---

SUMMARY
The added preview for the 5.0's appimage's file picker does not properly
display small images, seeming to give a zoomed-in rendering.

STEPS TO REPRODUCE
1. Create a 100x100 canvas.
2. Draw some stuff.
3. Save the file.
4. Observe the thumbnail in File -> Open.

OBSERVED RESULT
The thumbnail gives a zoomed-in rendering of the image.

EXPECTED RESULT
The thumbnail should give an accurate impression of the image.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.12.12 (appimage)

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

[digikam] [Bug 447674] Add "Rotate Face Tags" feature

2022-01-01 Thread Sergejs

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

--- Comment #2 from Sergejs  ---
Thanks for the suggestion Maik,

I thought about it and experimented some more until I arrived to conclusion
that a fully automatic solution is not worth it - basically using digiKam's
advanced search together with the simple "Rotate Face Tags" function would be
fast enough that I would not bother testing and risking potential damage any
fully automatic script can cause.

I described the desired workflow in detail here:
https://userbase.kde.org/Digikam/Tutorials/Switch_from_Microsoft_OneDrive_or_WLPG_to_digiKam#Semi-automated_approach

The main point is - simple "Rotate Face Tags" function would be my preferred
tool both for single file corrections and for fixing whole collection at once.


PS, I would be happy if some digiKam experts look through the tutorials I wrote
over the holidays (2 new and 1 revised). If you see any mistakes or can suggest
a better approach. I keep on polishing them as I find mistakes and new tricks,
but I am sure there is more to be done. I would like to eventually make them
into video tutorials, but only when I am more confident that the tutorials are
good.

Thank you for all your work!

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

[ark] [Bug 440135] cli7zplugin: add support for original 7-zip

2022-01-01 Thread Albert Astals Cid

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

--- Comment #2 from Albert Astals Cid  ---
Please use invent.kde.org for patches.

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

[kstars] [Bug 447753] Kstars crashes connecting to Ekos on MacOS

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

--- Comment #6 from Castor Fu  ---
(In reply to Castor Fu from comment #2)
> It doesn't actually need to involve a remote ekos.  If I select the default
> simulators ekos profile and launch it, kstars crashes.

Here's a better stack trace after running on a copy I built:
VM Regions Near 0:
--> 
__TEXT  108e45000-109c29000[ 13.9M] r-x/r-x SM=COW 
/Users/*/kstars.app/Contents/MacOS/kstars

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtCore   0x00010cff8e0a
QObject::setProperty(char const*, QVariant const&) + 26 (qobject.cpp:4031)
1   0x0001091b7176 Ekos::Mount::Mount()
+ 6598 (mount.cpp:209)
2   0x000108fadd08
Ekos::Manager::initMount() + 72 (manager.cpp:2435)
3   0x000108fa567e
Ekos::Manager::setTelescope(ISD::GDInterface*) + 414 (manager.cpp:1443)
4   org.qt-project.QtCore   0x00010cff89c4
QtPrivate::QSlotObjectBase::call(QObject*, void**) + 21
(qobjectdefs_impl.h:398) [inlined]
5   org.qt-project.QtCore   0x00010cff89c4 void
doActivate(QObject*, int, void**) + 1124 (qobject.cpp:3886)
6   0x000108ea0bcf
INDIListener::newTelescope(ISD::GDInterface*) + 63 (moc_indilistener.cpp:413)
7   0x000108f23845
INDIListener::registerProperty(INDI::Property) + 789 (indilistener.cpp:260)
8   0x000108f25913
QtPrivate::FunctorCall,
QtPrivate::List, void, void
(INDIListener::*)(INDI::Property)>::call(void
(INDIListener::*)(INDI::Property), INDIListener*, void**) + 55
(qobjectdefs_impl.h:152) [inlined]
9   0x000108f25913 void
QtPrivate::FunctionPointer::call,
void>(void (INDIListener::*)(INDI::Property), INDIListener*, void**) + 55
(qobjectdefs_impl.h:185) [inlined]
10  0x000108f25913
QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*,
QObject*, void**, bool*) + 179 (qobjectdefs_impl.h:418)
11  org.qt-project.QtCore   0x00010cff0d39
QObject::event(QEvent*) + 745 (qobject.cpp:1314)
12  org.qt-project.QtWidgets0x00010c1c6586
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
(qapplication.cpp:3632)
13  org.qt-project.QtWidgets0x00010c1c7940
QApplication::notify(QObject*, QEvent*) + 480
14  org.qt-project.QtCore   0x00010cfc8117
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 167
(qcoreapplication.cpp:1063)
15  org.qt-project.QtCore   0x00010cfc9228
QCoreApplication::sendEvent(QObject*, QEvent*) + 21 (qcoreapplication.cpp:1458)
[inlined]
16  org.qt-project.QtCore   0x00010cfc9228
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 792
(qcoreapplication.cpp:1817)
17  libqcocoa.dylib 0x00010e6296f8
QCocoaEventDispatcherPrivate::processPostedEvents() + 312
(qcocoaeventdispatcher.mm:904)
18  libqcocoa.dylib 0x00010e629e18
QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 40
(qcocoaeventdispatcher.mm:927)
19  com.apple.CoreFoundation0x7fff20a6137c
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
20  com.apple.CoreFoundation0x7fff20a612e4 __CFRunLoopDoSource0
+ 180
21  com.apple.CoreFoundation0x7fff20a610c6
__CFRunLoopDoSources0 + 340
22  com.apple.CoreFoundation0x7fff20a5fa8c __CFRunLoopRun + 893

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

[konsole] [Bug 441803] Konsole does not allow to change default profile, but creates new profile instead, leading to cumbersome "New Tab" workflow

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

tomash...@gmail.com changed:

   What|Removed |Added

 CC||tomash...@gmail.com

--- Comment #4 from tomash...@gmail.com ---
(In reply to Alain Knaff from comment #3)
> 
> This wouldn't still fix the issue about the extra click needed in "New Tab",
> as long as that original "Built-in" profile stays visible.

Indeed. A more sensible solution would be to create a user-modifiable profile
for new users and hide the default one. New profiles would be automatically
created with the default settings. There could be an action "Reset to default"
(on the right, would reset the selected profile to default) and "Copy profile"
that would make an identical profile from the selected one - I think I do not
need to explain why this would be useful.

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

[konsole] [Bug 447804] New: "Defaults" in "Configure Toolbars" and "Configure Keyboard" behave inconsistently

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

Bug ID: 447804
   Summary: "Defaults" in "Configure Toolbars" and "Configure
Keyboard" behave inconsistently
   Product: konsole
   Version: 21.12.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: tomash...@gmail.com
  Target Milestone: ---

How to reproduce:

1) Change some keyboard shortcut and change the default toolbars.
2) Press default in each of the configuration windows.

What would you expect:
1) The behaviour would be the same

What happens
1) When you press Defaults in "Configure Keyboard Shortcuts", there is no
dialog and the shortcuts get reset immediately.
2) When you press Defaults in "Configure Toolbars", you get a dialog aksing you
whether you want to reset the toolbars. When you say yes, it resets the
toolbars and the Keyboard shortcuts.

What should happen:
1) it asks whether wou want to reset the shortcuts
2) It does not reset the keyboard shortcuts.

(I have not tried what happens when you press Defaults in the general
settings).

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

[konsole] [Bug 447785] No close tab or view action for either toolbar or keyboard shortcuts

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

--- Comment #7 from tomash...@gmail.com ---
(In reply to Ahmad Samir from comment #6)
> In the keyboard shortcuts dialog the action is called "close session", I
> think we should augment the name to make easier to find.

Indeed. I thought I must be missing somewhere when I could not find it but it
was not clear to me that "session" is a "view". It is also sometimes referred
to as split or splitters (in settings ÷ Tab Bar / Splitters, the tab is called
"Splits"). So it is four words for the same concept, I think,  (Close Session
closes a view/split, not a tab). "View" is used in the action like "Split view"
or "Detach view".

What would be good, I think, is:
1) Unify on one word for split/splitters/view/session and use that throughout.
2) In Configure Konsole > Tab Bar /Splitter > Appearance, the first two tabs
(Appearance and Behaviour) refer to Tab Bar, but it is not really clear (first
option is "Show" - what is it that I am going to show?). I think it would make
sense to either join Appearance and Behaviour (which has just three options
anyway) into one tab called "Tab Bar" - or alternatively move Splitters from
"Tab Bar / Splitters" to a new category on its own.

By the way, I somehow managed to create three toolbars. Is that supposed to be
possible? They were named differently (Main Toolbar  and  and
Session Toolbar ). Then I pressed the Defaults buttons and I got just
two toolbars.

I also tried playing with the toolbard a bit and I do not get much the
difference. They have different actions avaialbe to them but the logic of the
division does not make much sense to me. Things regarding the splits and change
of focus would make more sense in the Session Toolbar (what they do depends on
which split is focused) and why for example is "Create New Profile" in Session
Toolbar?

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

[frameworks-knotifications] [Bug 447803] New: Wanted: option to have notification actions register as activation/start calls to window system

2022-01-01 Thread Friedrich W. H. Kossebau

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

Bug ID: 447803
   Summary: Wanted: option to have notification actions register
as activation/start calls to window system
   Product: frameworks-knotifications
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: kosse...@kde.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Use case: 
In a chat application when showing a notification about a new message, the
default action is to "Open" the respective view which holds the new message:

auto *msg = KNotification::event(...);
msg->setDefaultAction(i18n("Open"));
connect(msg, ::defaultActivated, window, [] {
window->show();
window->raise();
KWindowSystem::activateWindow(window->winId());
});

If the window is currently on another virtual desktop, given the intent of the
user to open/see the new message when activating the action, one would expect
that the window system/shell switches the virtual desktop as needed to show the
window.

Instead at least with KWin/Plasma on these calls only the window is highlighted
on the taskbar, but the virtual desktop not switched. So the user has to do a
further action (e.g. click the highlighted window entry) to finally get to the
window.

Assumption: this might be related to focus stealing handling? So there needs to
be some way for the notification system to tell the window system that the
window activation requested by the application is due to a start/activation
like event from the notification. Possibly something with X11 startup
id/Wayland activation token?

Seen in Konversation & NeoChat.

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

[marble] [Bug 447802] New: Please add CyclOSM Map

2022-01-01 Thread Klaumi Klingsporn

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

Bug ID: 447802
   Summary: Please add CyclOSM Map
   Product: marble
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: klaumi...@gmx.de
  Target Milestone: ---

Created attachment 145033
  --> https://bugs.kde.org/attachment.cgi?id=145033=edit
marble-map-package for CyclOSM

Please add CyclOSM as downloadable Map!
***
For a few years now there is a new rendering layer for Cyclist beside the API
requiring OpenCycleMap: The CycOSM.
Would be nice to have this in Marble (at least as downloadable extra map). It
has some improvements over the OpenCycleMap as it e.g. shows Camping-Sites
which is nice to have when planning a cycling-tour.

Over christmas I built a marble-mappackage for this map, which I'll try to add
to this bug. But you can also find it at:
https://www.klaumikli.de/Archiv/CyclOSM-marblemap.zip
as well as a german installation instruction at:
https://www.klaumikli.de/Linux/Howtos/Mable-CycleMaps.html.

As described there I was not able to prove if the display of the maps legend
works, because in my marble version (21.08 from Debian testing) the display of
map legends is buggy at all  (may be bug#439013 ?).

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

[ark] [Bug 440135] cli7zplugin: add support for original 7-zip

2022-01-01 Thread Max

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

Max  changed:

   What|Removed |Added

Summary|Feature request: Plugin for |cli7zplugin: add support
   |upstream 7-zip  |for original 7-zip

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

[ark] [Bug 440135] Feature request: Plugin for upstream 7-zip

2022-01-01 Thread Max

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

Max  changed:

   What|Removed |Added

 CC||m...@freebsd.org

--- Comment #1 from Max  ---
Created attachment 145032
  --> https://bugs.kde.org/attachment.cgi?id=145032=edit
support for 7-zip

There's no need for another plugin, existing plugin with this patch applied can
work with Linux version of 7-zip, assuming 7-zip package provides 7z
executable.
The patch relaxes regexp to match version string any of p7zip and 7-zip:

p7zip output:

7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=ru_RU.UTF-8,Utf16=on,HugeFiles=on,64 bits,8 CPUs
x64)


7-zip output:

7-Zip (z) 21.07 (x64) : Copyright (c) 1999-2021 Igor Pavlov : 2021-12-26
 64-bit locale=ru_RU.UTF-8 Threads:8

With this patch Ark can use any of them:

ark.cli7z: Loaded cli_7z plugin
ark.cli7z: Setting up parameters...
ark.cli7z: p7zip version "16.02" detected

ark.cli7z: Loaded cli_7z plugin
ark.cli7z: Setting up parameters...
ark.cli7z: p7zip version "21.07" detected

Perhaps, "p7zip" string should be replace with "7-Zip" to avoid confusion.

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

[kmymoney] [Bug 438973] Cannot right click and Go To a counterparty split if it is a category

2022-01-01 Thread Jack

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

--- Comment #3 from Jack  ---
I'm wondering if this is related to a similar problem I've recently noticed. 
For an investment transaction which uses or produces funds, in the investment
account, I can right click and see a link to go to the brokerage account.  In
the brokerage account, however, I only see a link back to the investment
account for buy or sell transactions, not for dividend type transactions, where
I only see a link to go to the category.  Is it possible this fix cause the
problem I am seeing?  Should I open as a separate bug?

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

[systemsettings] [Bug 355399] Make number of recent files to show globally configurable

2022-01-01 Thread shenlebantongying

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

shenlebantongying  changed:

   What|Removed |Added

 CC||shenlebantongy...@gmail.com

--- Comment #13 from shenlebantongying  ---
This bug become more relevant since the introduction of "Ctrl+Shift+I to open
command plate".

I wish I can just increase the limit to 1000, so that I can open any old PDF
from command plate blazing fast/

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

[okular] [Bug 435073] Okular uses wrong DPI scaling with multi-monitor setups

2022-01-01 Thread Pieter-Jan Briers

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

--- Comment #2 from Pieter-Jan Briers  ---
This bug seems to have been made less bad since I reported it. It's still not
100% fixed (icons are still scaled wrong, and moving the window between
monitors seems to not cause the PDF view to re-render immediately thus scaling
poorly until you zoom or something) but it's definitely usable now!

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

[kwin] [Bug 447797] Mouse cursor glitching upon switching states in the Wayland session

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

--- Comment #1 from unixst...@protonmail.com ---
I launched kwin_wayland with --exit-with-session konsole as well as with the
WAYLAND_DEBUG=1 environment variable. This is the output (a bit trimmed). I
tried to reproduce the issue (and successfully so!) by causing the cursor state
to change.

[195565,571] wl_callb...@31.done(322477)
[195565,580]  -> wl_buffer@36.destroy()
[195565,771]  -> wl_buffer@38.release()
[195566,248]  -> wl_surface@13.frame(new id wl_callback@31)
[195566,260]  -> wl_surface@13.set_buffer_scale(1)
[195566,272]  -> wl_surface@13.frame(new id wl_callback@34)
[195566,304]  -> zwp_linux_dmabuf_v1@25.create_params(new id
zwp_linux_buffer_params_v1@35)
[195566,315]  -> zwp_linux_buffer_params...@35.add(fd 39, 0, 0, 4096, 16777215,
4294967295)
[195566,331]  -> zwp_linux_buffer_params_v1@35.create_immed(new id
wl_buffer@33, 1024, 768, 808669784, 0)
[195566,345]  -> zwp_linux_buffer_params_v1@35.destroy()
[195566,348]  -> wl_surface@13.attach(wl_buffer@33, 0, 0)
[195566,356]  -> wl_surface@13.damage_buffer(210, 100, 616, 1)
[195566,364]  -> wl_surface@13.damage_buffer(209, 101, 618, 113)
[195566,372]  -> wl_surface@13.damage_buffer(209, 214, 637, 444)
[195566,383]  -> wl_surface@13.damage_buffer(209, 658, 618, 20)
[195566,391]  -> wl_surface@13.damage_buffer(210, 678, 616, 1)
[195566,408]  -> wl_surface@13.commit()
[195566,515]  -> wl_callb...@44.done(322478)
[195566,529]  -> wl_display@1.delete_id(44)
[195566,593] wl_display@1.delete_id(44)
[195566,607] wl_buffer@38.release()
[195566,611] wl_callb...@44.done(322478)
[195575,763] wl_display@1.delete_id(36)
[195575,778] wl_display@1.delete_id(35)
[195575,811] wl_pointer@19.motion(322489, 693,00, 658,00)
[195577,254] wl_display@1.delete_id(31)
[195577,264] wl_display@1.delete_id(34)
[195577,279] wl_callb...@31.done(322490)
[195578,328] wl_buffer@29.release()
[195578,334] wl_callb...@34.done(322490)
[195578,339]  -> wl_buffer@29.destroy()
[195578,605]  -> wl_surface@13.frame(new id wl_callback@34)
[195578,615]  -> wl_surface@13.set_buffer_scale(1)
[195578,624]  -> wl_surface@13.frame(new id wl_callback@31)
[195578,647]  -> zwp_linux_dmabuf_v1@25.create_params(new id
zwp_linux_buffer_params_v1@35)
[195578,656]  -> zwp_linux_buffer_params...@35.add(fd 39, 0, 0, 4096, 16777215,
4294967295)
[195578,669]  -> zwp_linux_buffer_params_v1@35.create_immed(new id
wl_buffer@36, 1024, 768, 808669784, 0)
[195578,679]  -> zwp_linux_buffer_params_v1@35.destroy()
[195578,683]  -> wl_surface@13.attach(wl_buffer@36, 0, 0)
[195578,690]  -> wl_surface@13.damage_buffer(210, 100, 616, 1)
[195578,698]  -> wl_surface@13.damage_buffer(209, 101, 618, 577)
[195578,705]  -> wl_surface@13.damage_buffer(210, 678, 616, 1)
[195578,716]  -> wl_surface@13.commit()
[195582,664] wl_display@1.delete_id(29)
[195582,673] wl_display@1.delete_id(35)
[195582,690] wl_pointer@19.motion(322496, 693,00, 659,00)
[195590,602] wl_display@1.delete_id(34)
[195590,612] wl_display@1.delete_id(31)
[195590,631] wl_callb...@34.done(322504)
[195615,851] wl_pointer@19.motion(322529, 692,00, 659,00)
[195710,824] wl_pointer@19.motion(322624, 692,00, 660,00)
[195717,713] wl_pointer@19.motion(322631, 691,00, 660,00)
[195788,945] wl_pointer@19.motion(322702, 690,00, 660,00)
[195806,836] wl_pointer@19.motion(322720, 690,00, 661,00)
[195832,803] wl_pointer@19.motion(322746, 689,00, 661,00)
[195869,849] wl_pointer@19.motion(322783, 689,00, 662,00)
[195881,871] wl_pointer@19.motion(322795, 688,00, 662,00)
[195911,724] wl_pointer@19.motion(322825, 687,00, 662,00)
[195912,634] wl_pointer@19.motion(322826, 687,00, 663,00)
[195938,100] wl_pointer@19.motion(322851, 686,00, 663,00)
[195947,736] wl_pointer@19.motion(322861, 686,00, 664,00)
[195986,798] wl_pointer@19.motion(322900, 685,00, 664,00)
[196013,993] wl_pointer@19.motion(322927, 685,00, 665,00)
[196074,856] wl_pointer@19.motion(322988, 684,00, 665,00)
[196082,714] wl_pointer@19.motion(322996, 684,00, 666,00)
[196118,766] wl_pointer@19.motion(323032, 683,00, 666,00)
[196119,666] wl_pointer@19.motion(323033, 683,00, 667,00)
[196147,847] wl_pointer@19.motion(323061, 683,00, 668,00)
[196147,917]  -> wl_pointer@19.set_cursor(1531, wl_surface@18, 4, 4)
[196147,929]  -> wl_surface@18.attach(wl_buffer@28, 0, 0)
[196147,938]  -> wl_surface@18.set_buffer_scale(1)
[196147,943]  -> wl_surface@18.damage_buffer(0, 0, 32, 32)
[196147,951]  -> wl_surface@18.commit()
[196148,404] wl_buffer@23.release()
[196151,808] wl_pointer@19.motion(323065, 682,00, 668,00)
[196188,891] wl_pointer@19.motion(323102, 682,00, 669,00)
[196201,795] wl_pointer@19.motion(323115, 681,00, 669,00)
[196218,771] wl_pointer@19.motion(323132, 681,00, 670,00)
[196763,852] wl_pointer@19.motion(323677, 680,00, 670,00)
[196830,800] wl_pointer@19.motion(323744,

[kmymoney] [Bug 446990] Wayland: Tooltip on date input fields steals focus, prevents entering data

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

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

[kmymoney] [Bug 446990] Wayland: Tooltip on date input fields steals focus, prevents entering data

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

--- Comment #5 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/office/kmymoney/-/merge_requests/141

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

[digikam] [Bug 447793] Database socket specification when trying to connect to mariadb server

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

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

   What|Removed |Added

   Version Fixed In||7.5.0
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 377626] Email image not working

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

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

   What|Removed |Added

 Resolution|DOWNSTREAM  |FIXED
   Version Fixed In||7.5.0

--- Comment #10 from caulier.gil...@gmail.com ---
Fixed with #414000

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

[digikam] [Bug 414959] Send by email with Thunderbird does not work anymore

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

--- Comment #43 from jo...@petri.us ---
(In reply to caulier.gilles from comment #36)
> Jonah,
> 
> Please test without to use a separated bash script to run thunderbird.
> 
> With last commits, we have disabled LD_PRELOAD on the separated QProcess
> call, so i don't understand how this settings can appear on your computer.
> 

Hello Gilles,
I have tested again today with digiKam-7.5.0-20220101T175533-x86-64.appimage
and I find the same thing - the environment is not correct in the sublaunched
thunderbird.  If I go back to my script which unsets the two environment
variables, then it works as expected.
Is there a way I can help debug further?

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

[konsole] [Bug 447785] No close tab or view action for either toolbar or keyboard shortcuts

2022-01-01 Thread Ahmad Samir

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

--- Comment #6 from Ahmad Samir  ---
In the keyboard shortcuts dialog the action is called "close session", I think
we should augment the name to make easier to find.

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

[systemsettings] [Bug 423401] Unable to open http/https URLs based on URL contents

2022-01-01 Thread Michael Tsang

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

Michael Tsang  changed:

   What|Removed |Added

 CC||mikl...@gmail.com

--- Comment #4 from Michael Tsang  ---
I'll need the old system settings back as my intention is to open http:// link
according to the actual file type. For example, I don't want PDFs through HTTP
link to be shown in Firefox!

Moreover, this now causes Konqueror to open Firefox when an http:// link is
typed into the URL as well.

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

[plasmashell] [Bug 447801] Auto hide, window can cover and window goes below doesn't work in a middle screen edge using multiple monitors.

2022-01-01 Thread Michael Tsang

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

--- Comment #1 from Michael Tsang  ---
Created attachment 145031
  --> https://bugs.kde.org/attachment.cgi?id=145031=edit
Screenshow showing panel isn't covered by window

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

[plasmashell] [Bug 447801] New: Auto hide, window can cover and window goes below doesn't work in a middle screen edge using multiple monitors.

2022-01-01 Thread Michael Tsang

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

Bug ID: 447801
   Summary: Auto hide, window can cover and window goes below
doesn't work in a middle screen edge using multiple
monitors.
   Product: plasmashell
   Version: 5.22.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: mikl...@gmail.com
  Target Milestone: 1.0

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


STEPS TO REPRODUCE
1. Connect multiple monitors
2. Create a panel on a screen edge where monitors join
3. Set it to window can cover

OBSERVED RESULT
Window doesn't cover the panel


EXPECTED RESULT
Window covers the panel


SOFTWARE/OS VERSIONS

Linux: Ubuntu 21.10
(available in About System)
KDE Plasma Version: 5.22.5


ADDITIONAL INFORMATION

See screenshot for details. All 3 panels are set to "screen can cover".

possibly related to #351175 and #368872 and #399312.

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

[krita] [Bug 447800] New: Brush 'Flow' value is incorrectly reflected between Brush HUD and Quick Settings Docker

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

Bug ID: 447800
   Summary: Brush 'Flow' value is incorrectly reflected between
Brush HUD and Quick Settings Docker
   Product: krita
   Version: 5.0.0
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: pent...@outlook.com
  Target Milestone: ---

Created attachment 145030
  --> https://bugs.kde.org/attachment.cgi?id=145030=edit
On-Screen HUD showing incorrect Flow value

SUMMARY
***
Selecting a Flow value in the Quick Settings Docker will not be reflected in
the On-Canvas Brush Editor HUD. Only zero (0) or one (1.00) value will be shown
in the HUD.
***


STEPS TO REPRODUCE
1. Bring up the Quick Settings Docker and switch to the Flow tab.
2. Right click on the canvas to bring up the On-Canvas Brush Editor HUD.
3. Show the brush parameter popup (or whatever it is called within the HUD) by
clicking on the right pointing arrow. This popup will show and allow you to set
various brush values, eg opacity, size, flow, etc for the selected brush.
4. Edit this popup so that the Brush Flow parameter will be shown, if not
visible.
5. Make sure both the Quick Settings Docker and the On-Canvas Brush Editor HUD
is visible at the same time and in the Quick Settings Docker click on a Flow
percentage. The selected Flow value will not be reflected in the On-Canvas
Brush Editor HUD Flow field. If you select 0.1 - 40% Flow value in the Quick
Settings Docker, the Flow value in the HUD will be zero. If you select 50 -
100% Flow value in the Quick Settings Docker, the flow value in the HUD will be
1.00.

OBSERVED RESULT
If you select 0.1 - 40% Flow value in the Quick Settings Docker, the Flow value
in the HUD will be zero. If you select 50 - 100% Flow value in the Quick
Settings Docker, the flow value in the HUD will be 1.00.


EXPECTED RESULT
The Quick Settings Docker displays percentages, but the On-Canvas Brush Editor
HUD displays float values. Possibly some conversion issue, but the On-Canvas
Brush Editor HUD should display the correct float value for the Flow that
corresponds to the percentage value selected in the Quick Settings Docker.

In the attached screenshot, 40% Flow value is selected in the Quick Settings
Docker, yet 0.00 Flow value is showing in the On-Canvas Brush Editor HUD.

SOFTWARE/OS VERSIONS

macOS: Mojave 10.14.6

ADDITIONAL INFORMATION

SESSION: 26 Dec 2021 19:03:43 +0100. Executing
/Applications/krita.app/Contents/MacOS/krita

Krita Version: 5.0.0, Qt version compiled: 5.12.12, loaded: 5.12.12. Process
ID: 1154
-- -- -- -- -- -- -- --
26 Dec 2021 19:03:43 +0100: Style: fusion. Available styles: macintosh,
Windows, Fusion
26 Dec 2021 19:07:24 +0100: Created image "Unnamed", 2560 * 1440 pixels, 72
dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc).
Layers: 2
27 Dec 2021 04:34:31 +0100: CLOSING SESSION

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

[plasmashell] [Bug 447272] system tray icon overlapping each other

2022-01-01 Thread Konrad Materka

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

Konrad Materka  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[dolphin] [Bug 447799] New: Dolphin crashes while trying to eject a disc

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

Bug ID: 447799
   Summary: Dolphin crashes while trying to eject a disc
   Product: dolphin
   Version: 21.08.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: gm...@mykolab.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (21.08.3)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.11-200.fc35.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 35 (KDE Plasma)
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Dolphin crashes sometimes when trying to eject a real disc while it is busy.
When I force to eject by pressing the button sometimes the system can also hang
and Terminal is really sloppy, shutdown isn't working or is very slow. (much
rarer)

System: Fedora 35 KDE Spin

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  0x7f18e30b068d in Solid::StorageAccess::d_func (this=)
at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/src/solid/devices/frontend/storageaccess.h:35
#7  Solid::StorageAccess::filePath (this=0x0) at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/src/solid/devices/frontend/storageaccess.cpp:53
#8  0x5617e56350dc in PlacesItemModel::slotStorageTearDownDone
(this=0x5617e69678e0, error=3848490880, errorData=...) at
/usr/src/debug/dolphin-21.08.3-1.fc35.x86_64/src/panels/places/placesitemmodel.cpp:454
#9  0x7f18e18723e9 in QtPrivate::QSlotObjectBase::call (a=0x7fffe9cf4830,
r=, this=0x5617e6cc1bb0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate (sender=0x5617e6b1f1d0, signal_index=4,
argv=0x7fffe9cf4830) at kernel/qobject.cpp:3886
#11 0x7f18e186d367 in QMetaObject::activate
(sender=sender@entry=0x5617e6b1f1d0, m=m@entry=0x7f18e311e120
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffe9cf4830)
at kernel/qobject.cpp:3946
#12 0x7f18e30a1d0f in Solid::OpticalDrive::ejectDone
(this=this@entry=0x5617e6b1f1d0, _t1=, _t2=..., _t3=...) at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/redhat-linux-build/src/solid/KF5Solid_autogen/H3VFCUX2PL/moc_opticaldrive.cpp:294
#13 0x7f18e30a9649 in Solid::OpticalDrive::qt_static_metacall
(_o=0x5617e6b1f1d0, _c=, _id=, _a=0x7fffe9cf4a10)
at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/redhat-linux-build/src/solid/KF5Solid_autogen/H3VFCUX2PL/moc_opticaldrive.cpp:162
#14 0x7f18e1872430 in doActivate (sender=0x5617e6c90090,
signal_index=4, argv=0x7fffe9cf4a10) at kernel/qobject.cpp:3898
#15 0x7f18e186d367 in QMetaObject::activate
(sender=sender@entry=0x5617e6c90090, m=m@entry=0x7f18e311b880
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffe9cf4a10)
at kernel/qobject.cpp:3946
#16 0x7f18e309c806 in Solid::Backends::UDisks2::OpticalDrive::ejectDone
(_t3=..., _t2=..., _t1=Solid::DeviceBusy, this=0x5617e6c90090) at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/redhat-linux-build/src/solid/KF5Solid_autogen/EYXUHNKS25/moc_udisksopticaldrive.cpp:227
#17 Solid::Backends::UDisks2::OpticalDrive::slotEjectDone (errorString=...,
error=2, this=0x5617e6c90090) at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/src/solid/devices/backends/udisks2/udisksopticaldrive.cpp:117
#18 Solid::Backends::UDisks2::OpticalDrive::qt_static_metacall
(_o=_o@entry=0x5617e6c90090, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=6, _a=_a@entry=0x7fffe9cf4b70) at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/redhat-linux-build/src/solid/KF5Solid_autogen/EYXUHNKS25/moc_udisksopticaldrive.cpp:117
#19 0x7f18e309cd83 in Solid::Backends::UDisks2::OpticalDrive::qt_metacall
(this=0x5617e6c90090, _c=QMetaObject::InvokeMetaMethod, _id=6,
_a=0x7fffe9cf4b70) at
/usr/src/debug/kf5-solid-5.89.0-1.fc35.x86_64/redhat-linux-build/src/solid/KF5Solid_autogen/EYXUHNKS25/moc_udisksopticaldrive.cpp:206
#20 0x7f18e1b501eb in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#21 0x7f18e1868f49 in QObject::event (this=0x5617e6c90090,
e=0x7f18c000fda0) at kernel/qobject.cpp:1314
#22 0x7f18e23e6443 in QApplicationPrivate::notify_helper (this=, receiver=0x5617e6c90090, e=0x7f18c000fda0) at
kernel/qapplication.cpp:3632
#23 0x7f18e183e7d8 in QCoreApplication::notifyInternal2
(receiver=0x5617e6c90090, event=0x7f18c000fda0) at
kernel/qcoreapplication.cpp:1064
#24 0x7f18e1841d46 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5617e6114df0) at
kernel/qcoreapplication.cpp:1821
#25

[kid3] [Bug 447798] New: crash on "rewrite tags" when album frame is shown in file list

2022-01-01 Thread Reuben

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

Bug ID: 447798
   Summary: crash on "rewrite tags" when album frame is shown in
file list
   Product: kid3
   Version: 3.9.x
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: uflei...@users.sourceforge.net
  Reporter: reuben.ka...@gmail.com
  Target Milestone: ---

Application: kid3 (3.9.0)

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.14.13-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:

1.Open an album in kid3
2.in file list, add Album frame.
3.Select all files.
4. RMB menu - select "Rewrite Tags"
-- crash

The crash can be reproduced every time.

-- Backtrace:
Application: Kid3 (kid3), signal: Segmentation fault

[KCrash Handler]
#4  0x0020 in  ()
#5  0x7f2916c06bc1 in  () at /usr/lib/kid3/plugins/libtaglibmetadata.so
#6  0x7f293f2be2e8 in TaggedFileSystemModel::data(QModelIndex const&, int)
const () at /usr/lib/kid3/libkid3-core.so
#7  0x7f293df115a9 in QSortFilterProxyModel::data(QModelIndex const&, int)
const () at /usr/lib/libQt5Core.so.5
#8  0x7f293ed140ba in
QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&)
const () at /usr/lib/libQt5Widgets.so.5
#9  0x7f293ed17c9b in QStyledItemDelegate::sizeHint(QStyleOptionViewItem
const&, QModelIndex const&) const () at /usr/lib/libQt5Widgets.so.5
#10 0x7f293ed639cd in QTreeView::indexRowSizeHint(QModelIndex const&) const
() at /usr/lib/libQt5Widgets.so.5
#11 0x7f293ed63bb2 in QTreeViewPrivate::itemHeight(int) const () at
/usr/lib/libQt5Widgets.so.5
#12 0x7f293ed58e9b in QTreeView::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Widgets.so.5
#13 0x7f293df6742f in  () at /usr/lib/libQt5Core.so.5
#14 0x7f293def35ca in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5
#15 0x7f293f27607c in FileProxyModel::onFileModificationChanged(QModelIndex
const&, bool) () at /usr/lib/kid3/libkid3-core.so
#16 0x7f293df673e3 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f293f2d3f38 in
TaggedFileSystemModel::fileModificationChanged(QModelIndex const&, bool) () at
/usr/lib/kid3/libkid3-core.so
#18 0x7f2916bf6fde in  () at /usr/lib/kid3/plugins/libtaglibmetadata.so
#19 0x7f293f2896ab in Kid3Application::saveDirectory() () at
/usr/lib/kid3/libkid3-core.so
#20 0x7f293f2d1fcc in  () at /usr/lib/kid3/libkid3-core.so
#21 0x7f293f2d3b6b in Kid3Application::qt_metacall(QMetaObject::Call, int,
void**) () at /usr/lib/kid3/libkid3-core.so
#22 0x7f2933e43c9e in  () at /usr/lib/libQt5Qml.so.5
#23 0x7f2933d1ddd7 in  () at /usr/lib/libQt5Qml.so.5
#24 0x7f2933d20f6b in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5
#25 0x7f2933d3e0c0 in  () at /usr/lib/libQt5Qml.so.5
#26 0x7f2933d40dbf in  () at /usr/lib/libQt5Qml.so.5
#27 0x7f2933cd3ed9 in  () at /usr/lib/libQt5Qml.so.5
#28 0x7f2933cd4bc0 in  () at /usr/lib/libQt5Qml.so.5
#29 0x7f2933d3e0c0 in  () at /usr/lib/libQt5Qml.so.5
#30 0x7f2933d40dbf in  () at /usr/lib/libQt5Qml.so.5
#31 0x7f2933cd3ed9 in  () at /usr/lib/libQt5Qml.so.5
#32 0x7f2933d258ef in  () at /usr/lib/libQt5Qml.so.5
#33 0x7f293df673e3 in  () at /usr/lib/libQt5Core.so.5
#34 0x7f2933ec7dee in QQmlTimer::event(QEvent*) () at
/usr/lib/libQt5Qml.so.5
#35 0x7f293ea8c1a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#36 0x55df87d4dd60 in  ()
#37 0x7f293df3689a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#38 0x7f293df37399 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#39 0x7f293df7db88 in  () at /usr/lib/libQt5Core.so.5
#40 0x7f293c8ff52c in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#41 0x7f293c9537b9 in  () at /usr/lib/libglib-2.0.so.0
#42 0x7f293c8fcc11 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#43 0x7f293df81a8a in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#44 0x7f293df2ea9b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#45 0x7f293df3a2c7 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#46 0x55df87d43591 in  ()
#47 0x7f293dafcb25 in __libc_start_main () at /usr/lib/libc.so.6
#48 0x55df87d43a5e in _start ()
[Inferior 1 (process 60549) detached]

Report to https://bugs.kde.org/SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See

[krita] [Bug 447771] “Shortcut Schemes” doesn’t change the keybindings

2022-01-01 Thread Lynx3d

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

Lynx3d  changed:

   What|Removed |Added

 CC||sk.and...@gmail.com

--- Comment #2 from Lynx3d  ---
*** Bug 447716 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 447716] photoshop shortcut scheme is not working due to incorrect photoshop_compatible.shortcuts

2022-01-01 Thread Lynx3d

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

Lynx3d  changed:

   What|Removed |Added

 CC||lynx.mw+...@gmail.com

--- Comment #2 from Lynx3d  ---


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

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

[kwin] [Bug 447797] New: Mouse cursor glitching upon switching states in the Wayland session

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

Bug ID: 447797
   Summary: Mouse cursor glitching upon switching states in the
Wayland session
   Product: kwin
   Version: 5.23.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: unixst...@protonmail.com
  Target Milestone: ---

SUMMARY

Whenever I log onto a Wayland session, hovering over links results in the mouse
cursor switching to the appropriate state, but while it does so, it briefly
moves to the side of where the cursor should actually be, before returning to
the correct position. This happens on both XWayland and Wayland applications,
Qt and GTK. I have tried to change compositor settings, but they don't seem to
help. I'm not using fractional scaling. This isn't my video, but it looks
exactly like this: https://www.youtube.com/watch?v=wCyTrt3TrAw

STEPS TO REPRODUCE
1. Switch to a Wayland session.
2. Use your mouse to hover over a link or anything else that changes the state
of the cursor.
3. Upon hovering over it, or moving the cursor away, it changes to the
appropriate state, but it does not transition smoothly. It moves to the size
for a brief second and returns to the correct position.

OBSERVED RESULT
Upon switching states, it jumps to the side for a small amount of time, then
switches to the correct state in the correct position.

EXPECTED RESULT
It should switch states without moving to the side or glitching.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  openSUSE Tumbleweed 20211228 snapshot.
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
The same issue also happens on other distributions, themes (including the
default Breeze theme, cursor and otherwise), but only on Wayland, not on xorg.
None of the compositor settings solve or help reduce the issue.

On RX 580 4gb.

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

[digikam] [Bug 447767] Face detection on Sony ARW files does not detect the correct face area

2022-01-01 Thread Maik Qualmann

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

--- Comment #8 from Maik Qualmann  ---
Git commit c3a56aff7d9cf1ad71992d1c3eb95faf8fa12224 by Maik Qualmann.
Committed on 01/01/2022 at 21:06.
Pushed by mqualmann into branch 'master'.

get face regions from half RAW image
limit the size for openCV to 2000px

M  +12   -2core/utilities/facemanagement/threads/facepreviewloader.cpp

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

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

[digikam] [Bug 447793] Database socket specification when trying to connect to mariadb server

2022-01-01 Thread jrobens

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

jrobens  changed:

   What|Removed |Added

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

--- Comment #2 from jrobens  ---
I could connect by using 127.0.0.1 instead of localhost.

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

[Breeze] [Bug 447796] Make highlights in Breeze GTK the same as in Breeze Qt

2022-01-01 Thread Photon

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

--- Comment #1 from Photon  ---
Created attachment 145029
  --> https://bugs.kde.org/attachment.cgi?id=145029=edit
Breeze Qt highlight

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

[Breeze] [Bug 447796] New: Make highlights in Breeze GTK the same as in Breeze Qt

2022-01-01 Thread Photon

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

Bug ID: 447796
   Summary: Make highlights in Breeze GTK the same as in Breeze Qt
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ncqm3...@anonaddy.me
  Target Milestone: ---

Created attachment 145028
  --> https://bugs.kde.org/attachment.cgi?id=145028=edit
Breeze GTK highlight

Currently, accent colors in Breeze GTK highlights are very bright and this
causes readability issues and eye strain when using the dark mode.

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

[kid3] [Bug 447795] option "use for playlist and folder names" in FileName Format string replacement breaks rename folder

2022-01-01 Thread Reuben

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

Reuben  changed:

   What|Removed |Added

Version|unspecified |3.9.x

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

[kid3] [Bug 447795] New: option "use for playlist and folder names" in FileName Format string replacement breaks rename folder

2022-01-01 Thread Reuben

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

Bug ID: 447795
   Summary: option "use for playlist and folder names" in FileName
Format string replacement breaks rename folder
   Product: kid3
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: uflei...@users.sourceforge.net
  Reporter: reuben.ka...@gmail.com
  Target Milestone: ---

SUMMARY
***
option "use for playlist and folder names" in FileName Format string
replacement breaks rename folder functionality
***


STEPS TO REPRODUCE
1. set option "use for playlist and folder names" in FileName Format string
replacement (it is by ddefault now it seems)
2. check there is string replacement "/" to "-"
3. try to rename folder with option %{artist}/%y - %{album}
OBSERVED RESULT
folder is renamed to %{artist}-%y - %{album}

EXPECTED RESULT
folder is renamed to %{artist}/%y - %{album}
replacement should apply inside the tokens, not to the whole string.

SOFTWARE/OS VERSIONS
Version 3.9.0
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 

KDE Frameworks Version: 
KDE Frameworks 
Version 5.89.0
Qt Version: 
Version 5.15.2 (built against 5.15.2)
ADDITIONAL INFORMATION

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

[kstars] [Bug 447753] Kstars crashes connecting to Ekos on MacOS

2022-01-01 Thread Rob

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

--- Comment #5 from Rob  ---
I am actually currently in the process making a bunch of changes to the script
to hopefully make our build as close to using the true craft recipes as
possible.  Then maybe I can get whatever changes are actually needed to get
accepted into craft so we can get binary factory builds.  So you might get a
failure just because I am trying some changes to the build right now.  But now
there are just a few recipes that are different than craft's recipes so if the
build fails on any of those recipes I didn't change, we can get craft people to
address it I think.

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

[systemsettings] [Bug 447794] New: Base color of weekends on the selected color scheme

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

Bug ID: 447794
   Summary: Base color of weekends on the selected color scheme
   Product: systemsettings
   Version: 5.23.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_clock
  Assignee: p...@taniwha.com
  Reporter: doggoofsp...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 145027
  --> https://bugs.kde.org/attachment.cgi?id=145027=edit
The problematic red text

SUMMARY
Right now weekends are painted a dark red color that is (if not hardcoded) not
based on the color scheme selected by the user. This can contrast problems,
especially when the background is dark. I'd also say that the red is needlessly
aggressive, but that's not as important

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

[digikam] [Bug 447793] Database socket specification when trying to connect to mariadb server

2022-01-01 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
When using an external MySQL database, digiKam does not set any socket options.
So this must be a problem with your MariaDB installation.
But you can enter the following in the connections options:

UNIX_SOCKET=/tmp/mysql.sock

Maik

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

[krusader] [Bug 375092] Crash when canceling confirmation to overwrite a file.

2022-01-01 Thread Andreas Nicolai

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

--- Comment #5 from Andreas Nicolai  ---
looks like the progress dialog is being terminated and the widget destroyed
(maybe the respective WINDOW flag is set?), and the original copy dialog tries
to access the now dangling pointer - either explicitely, or via signal-slot
connection.

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

[digikam] [Bug 447793] New: Database socket specification when trying to connect to mariadb server

2022-01-01 Thread jrobens

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

Bug ID: 447793
   Summary: Database socket specification when trying to connect
to mariadb server
   Product: digikam
   Version: 7.5.0
  Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Database
  Assignee: digikam-bugs-n...@kde.org
  Reporter: jrob...@interlated.com.au
  Target Milestone: ---

Created attachment 145026
  --> https://bugs.kde.org/attachment.cgi?id=145026=edit
Connection result

SUMMARY

I'd like to connect to a mariadb server that I have on the local machine. The
socket is not able to be specified and is wrong. 

My socket is in /tmp/mysql.sock. digikam is trying to use a socket in
/opt/digikam.org.x86_64/...


STEPS TO REPRODUCE
1. Install digikam
2. attempt to connect to the database
3. 

OBSERVED RESULT

Wrong socket path as per screen grab. I'm trying to connect via port 3306

EXPECTED RESULT

Connection successful


SOFTWARE/OS VERSIONS
Windows: 
macOS: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:41 PST 2021;
root:xnu-8019.61.5~1/RELEASE_ARM64_T6000 arm64

Qt Version: 
qt: stable 6.2.2 (bottled), HEAD
Cross-platform application and UI framework
https://www.qt.io/
/opt/homebrew/Cellar/qt/6.2.2 (12,257 files, 488.2MB) *
  Poured from bottle on 2021-12-14 at 07:23:24
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/qt.rb
License: GFDL-1.3-only and GPL-2.0-only and GPL-3.0-only and LGPL-2.1-only and
LGPL-3.0-only
==> Dependencies
Build: cmake ✘, ninja ✘, node ✘, pkg-config ✔
Required: assimp ✔, brotli ✔, dbus ✔, double-conversion ✔, freetype ✘, glib ✔,
hunspell ✔, icu4c ✔, jasper ✔, jpeg ✔, libb2 ✔, libpng ✔, libtiff ✔, md4c ✔,
pcre2 ✔, python@3.9 ✔, sqlite ✔, webp ✔, zstd ✔
==> Requirements
Build: Xcode ✔
==> Options
--HEAD
Install HEAD version
==> Analytics
install: 59,357 (30 days), 199,484 (90 days), 719,367 (365 days)
install-on-request: 29,463 (30 days), 96,768 (90 days), 266,095 (365 days)
build-error: 79 (30 days)


ADDITIONAL INFORMATION

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

[krusader] [Bug 375092] Crash when canceling confirmation to overwrite a file.

2022-01-01 Thread Andreas Nicolai

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

--- Comment #4 from Andreas Nicolai  ---
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krusader...
(No debugging symbols found in krusader)
(gdb) r
Starting program: /usr/bin/krusader 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
QCoreApplication::applicationDirPath: Please instantiate the QApplication
object first
[New Thread 0x71389700 (LWP 79844)]
[New Thread 0x7fffeb746700 (LWP 79845)]
[New Thread 0x7fffeaf45700 (LWP 79846)]
[New Thread 0x7fffea4cd700 (LWP 79848)]
21:34:05.059-debug default unknown@0 # System icon theme: "kf5_rcc_theme"
21:34:05.145-warning default unknown@0 # QWidget::insertAction: Attempt to
insert null action
21:34:05.146-warning default unknown@0 # QWidget::insertAction: Attempt to
insert null action
21:34:05.160-warning kf5.ki18n unknown@0 # Trying to convert empty
KLocalizedString to QString.
21:34:14.585-critical default unknown@0 # Couldn't start kuiserver from
org.kde.kuiserver.service:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
org.kde.kuiserver was not provided by any .service files")
21:34:17.365-warning default unknown@0 # ""

Thread 1 "krusader" received signal SIGSEGV, Segmentation fault.
0x557c1e2a in ?? ()
(gdb) where
#0  0x557c1e2a in ?? ()
#1  0x761b5458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x557bda76 in ?? ()
#3  0x557c34dd in ?? ()
#4  0x761b5458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x77332b0d in KJob::finished(KJob*, KJob::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#6  0x77333740 in KJob::finishJob(bool) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#7  0x776057ca in KIO::CopyJob::emitResult() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#8  0x77610402 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#9  0x776126eb in KIO::CopyJob::slotResult(KJob*) () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#10 0x761b5458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x77332c60 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#12 0x7733376b in KJob::finishJob(bool) () from
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#13 0x7767eaf8 in KIO::SimpleJob::slotFinished() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#14 0x776838ee in KIO::StatJob::slotFinished() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#15 0x761b5458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7764f252 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#17 0x7764cf4f in KIO::SlaveInterface::dispatch() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#18 0x77656152 in KIO::Slave::gotInput() () from
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#19 0x761b5458 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x761b5d5a in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x76bbea66 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x76bc80f0 in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7618993a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7618c5b8 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x761e1f67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x74ac817d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x74ac8400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x74ac84a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x761e1565 in

[krita] [Bug 439654] Bug : input stuck on panning after clicking/right-clicking on a floating window(brush list windows, brush settings windows, etc)

2022-01-01 Thread stephen

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

stephen  changed:

   What|Removed |Added

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

--- Comment #3 from stephen  ---
(In reply to Will Stephenson from comment #1)
> What actions do you have assigned to your pen nib/buttons? Which tablet is
> it?
> 
> Couldn't reproduce yet on 5.0.0beta5.

Greetings. I have assigned "right-click" and "switch brush" actions to my pen
buttons.
I use a Huion HS610.

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

[kstars] [Bug 447753] Kstars crashes connecting to Ekos on MacOS

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

--- Comment #4 from Castor Fu  ---
(In reply to Castor Fu from comment #3)
> Hoping to reproduce this with more info I tried to compile kstars on macos
> with rlancaste@'s script, but it fails in sonnet for me:
> 

This was a problem with macos 12.1's sdk.  Updating to the current
command-line-tools seems to have fixed the build break.  Hopefully it will
finish compiling in a bit.

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

[kwin] [Bug 447792] New: cmdline video option "reflect_x" isn't applied

2022-01-01 Thread Jakob Hauser

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

Bug ID: 447792
Summary: cmdline video option "reflect_x" isn't applied
Product: kwin
Version: 5.23.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: ja...@rocketmail.com
Target Milestone: ---

Created attachment 145025
--> https://bugs.kde.org/attachment.cgi?id=145025=edit
Screenshot showing the issue

SUMMARY
On device samsung-serranove, the screen natively shows a mirrored image.
Flipping the screen in the kernel is not implemented yet. In distribution
postmarketOS we compensate this by adding "video=540x960,reflect_x" to the boot
cmdline [1].

On Plasma Mobile with KWin version 5.22.4, the screen is ok after boot. When
rotating the device, auto-rotate rotates the screen. This results in a mirrored
image.

With KWin version 5.23.4, the screen shows a mirrored image right after boot.
It remains mirrored after auto-rotation.

Between those versions, at 5.22.90, there was a commit "drm: Use KScreen's json
files to set up the initial output composition" [2]. So I guess in KWin 5.22.4
the configuration was first read from ~/.config/kwinrc and upon auto-rotation
it was read from ~/.local/share/kscreen/. In KWin 5.23.4 it's read from
~/.local/share/kscreen/. right away.

Using the package "drm_info" to have a better insight, I can see that on KWin
5.22.4 after boot the "rotation" property of the drm plane 0 is at "(rotate-0 |
reflect-x)". After auto-rotation it's changed to "(rotate-0)" only. On KWin
5.23.4 it's on "(rotate-0)" only from the beginning.

As far as I can see, KScreen doesn't support screen flipping/reflecting [3]
[4]. Presumably because of this, the reflect-x of the drm plane get's lost as
soon as KScreen comes in.

Well, I guess this comes down to KScreen missing this feature.

[1] https://www.kernel.org/doc/html/v5.15/fb/modedb.html
[2] https://invent.kde.org/plasma/kwin/-/merge_requests/944
[3]
https://invent.kde.org/plasma/libkscreen/-/blob/v5.23.4/backends/kwayland/waylandoutputdevice.cpp#L101
[4]
https://invent.kde.org/plasma/kwin/-/blob/v5.23.4/src/plugins/platforms/drm/drm_backend.cpp#L445-467

STEPS TO REPRODUCE
Unfortunately, this cannot be reproduced on many desktops or laptops. Many
cards don't support refect-x. Whether it's supported can be checked by
installing package drm-info, type "drm_info | less", checking if "rotation"
property is listed for plane 0 and if it's capable to do "reflect-x". On Debian
or Ubuntu, the package is available on bullseye and hirsute or higher.

If the card is able to do reflect-x, the issue can be reproduced artificiallly.
I could not test this because my desktop/laptop cards don't support
"reflect-x".
1. Make sure in Plasma Settings -> Display -> the rotation is set to "No
Roation".
2. Get the screen resolution, e.g. by something like cat
/sys/class/graphics/fb0/modes.
3. Add something like "video=1280x1024,reflect_x" to the boot cmdline.
4a. On KWin 5.22.4, after reboot, the screen should be
flipped/reflected/mirrored. When now going to Plasma Settings -> Display ->
change the rotation to something, the "reflect-x" will get lost and the screen
isn't mirrored anymore.
4b. On KWin 5.23.4, when reaching Plasma after reboot, "reflect-x" will get
lost directly.

OBSERVED RESULT
On KWin 5.23.4, boot cmdline video parameter "reflect_x" gets lost. Also there
seems no other possibility to flip the screen.

On KWin 5.22.4, this happens after rotating the screen (KScreen).

EXPECTED RESULT
Ability to reflect/flip the screeen if needed, e.g. by cmdline video parameter
"reflect_x".

SOFTWARE/OS VERSIONS
Operating System: postmarketOS v21.12 / Plasma Mobile
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-msm8916 (armv7)
OS Type: 32-bit
Graphics Platform: Wayland
Processors: 4 × 1.2 GHz Quad-core Cortex-A53
Memory: 1.4 GiB of RAM
Graphics Processor: Adreno 305

ADDITIONAL INFORMATION
none

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

[plasmashell] [Bug 447791] Plasma black screen or crash at login

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

--- Comment #1 from opensuse.lietuviu.ka...@gmail.com ---
For me this bug seems like some race condition. I am testing this in
VirtualBox, seems this bug is regardless virtualbox modules installation or
without them.
Besides, if I login into Plasma after Ctrl+Alt+Backspace, one more unusual
thing: no option to reboot, shutdown or hibernate among logout options.

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

[plasmashell] [Bug 447791] New: Plasma black screen or crash at login

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

Bug ID: 447791
   Summary: Plasma black screen or crash at login
   Product: plasmashell
   Version: 5.18.7
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: opensuse.lietuviu.ka...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 145024
  --> https://bugs.kde.org/attachment.cgi?id=145024=edit
logs.txt

Application: plasmashell (5.18.6)

Qt Version: 5.12.7
Frameworks Version: 5.76.0
Operating System: Linux 5.3.18-59.37-default x86_64
Windowing system: X11
Distribution: openSUSE Leap 15.3

-- Information about the crash:
- What I was doing when the application crashed:
I just login in SDDM (automatic login without passwod), for some seconds I see
splash screen with more than half percentage of progress bar passed, finally
either black screen appears (most often) or sometimes I press
Ctrl+Alt+Backspace to restart sessions and after that I can load full Plasma
desktop.

- Unusual behavior I noticed:
No Kwin window decorations. Even if I see black screen, most often I can press
Alt+F2, and in this way open program (e.g. konsole).
I use X (xcb), not Wayland.
In logs I can see:
kglobalaccel5[1489]: qt.qpa.xcb: could not connect to display :0

I also see:
systemd[1]: No hostname configured.
systemd[1]: Set hostname to .
NetworkManager[969]:   [1641065313.0076] policy: set-hostname: set
hostname to 'localhost.localdomain' (Error reverse-resolving “10.0.2.15”: Name
or service not known)
systemd-hostnamed[981]: Changed hostname to 'localhost.localdomain'

I doubt where host name change helps...
This is LiveDVD system.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[KCrash Handler]
#4  ScreenPool::ScreenPool (this=0x563d4c2c24f0, config=..., parent=) at
/usr/src/debug/plasma5-workspace-5.18.6-bp153.4.2.3.x86_64/shell/screenpool.cpp:48
#5  0x563d4a559f61 in ShellCorona::ShellCorona (this=0x563d4c2b2000,
parent=) at
/usr/src/debug/plasma5-workspace-5.18.6-bp153.4.2.3.x86_64/shell/shellcorona.cpp:105
#6  0x563d4a52f59b in main (argc=, argv=) at
/usr/src/debug/plasma5-workspace-5.18.6-bp153.4.2.3.x86_64/shell/main.cpp:150
[Inferior 1 (process 1776) detached]

Possible duplicates by query: bug 447781, bug 447773, bug 447752, bug 447751,
bug 447749.

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

[konqueror] [Bug 434173] Konqueror automatic spell checking not working with WebEngine

2022-01-01 Thread David Faure

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/netw
   ||ork/konqueror/commit/7cc349
   ||a1d6a1ff7ed54fc887f1abf911b
   ||20b1398

--- Comment #6 from David Faure  ---
Git commit 7cc349a1d6a1ff7ed54fc887f1abf911b20b1398 by David Faure, on behalf
of Stefano Crocco.
Committed on 01/01/2022 at 19:53.
Pushed by dfaure into branch 'master'.

Perform spellchecker setup on creation

M  +3-11   webenginepart/src/spellcheckermanager.cpp
M  +0-3webenginepart/src/spellcheckermanager.h

https://invent.kde.org/network/konqueror/commit/7cc349a1d6a1ff7ed54fc887f1abf911b20b1398

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

[digikam] [Bug 417885] Problems on Windows Subsystem for Linux

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

--- Comment #26 from spam-recei...@web.de ---
Looks all okay-ish:

```

$ pwd
/home/thomas/squashfs-root/usr/lib

$ ll libQt5Core.so.5
-rwxr-xr-x 1 thomas thomas 6715872 Jan  1 17:39 libQt5Core.so.5*

$ ldd libQt5Core.so.5
     linux-vdso.so.1 (0x7fffd922b000)
     libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f9575bcd000)
     libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1
(0x7f9575b2)
     libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9575b1)
     libgthread-2.0.so.0 =>
/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x7f9575b0)
     libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x7f95759d)
     libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f95757e)
     libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f9575681000)
     libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f957566)
     libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f957546)
     /lib64/ld-linux-x86-64.so.2 (0x7f957627c000)
     libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3
(0x7f95753e)

```


Am 01.01.2022 um 20:24 schrieb bugzilla_nore...@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=417885
>
> --- Comment #25 from caulier.gil...@gmail.com ---
> I don't understand why this do not work.
>
> In your decompressed appimage content, go to the Qt5 library file and run ldd
> like this
>
> [gilles@localhost lib]$ pwd
> /tmp/.mount_digiKafKsuVU/usr/lib
>
> [gilles@localhost lib]$ ll libQt5Core.so.5
> -rwxr-xr-x 1 root root 6715872 Jan  1 19:50 libQt5Core.so.5*
>
> [gilles@localhost lib]$ ldd libQt5Core.so.5
>  linux-vdso.so.1 (0x7fff1cf29000)
>  libpthread.so.0 => /lib64/libpthread.so.0 (0x7f61ff4cc000)
>  libzstd.so.1 => /lib64/libzstd.so.1 (0x7f61ff3f1000)
>  libdl.so.2 => /lib64/libdl.so.2 (0x7f61ff3ec000)
>  libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 
> (0x7f61ff3e7000)
>  libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x7f61ff2bb000)
>  libstdc++.so.6 => /lib64/libstdc++.so.6 (0x7f61ff0eb000)
>  libm.so.6 => /lib64/libm.so.6 (0x7f61fefa6000)
>  libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f61fef8c000)
>  libc.so.6 => /lib64/libc.so.6 (0x7f61fedd2000)
>  /lib64/ld-linux-x86-64.so.2 (0x7f61ffb81000)
>  libpcre.so.1 => /lib64/libpcre.so.1 (0x7f61fed6)
>
> Note : this is mine from the last AppImage bundle 7.5.0 :
> digiKam-7.5.0-20220101T175533-x86-64.appimage
>
> GilleS Caulier
>

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

[konsole] [Bug 447785] No close tab or view action for either toolbar or keyboard shortcuts

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

--- Comment #5 from tcanabr...@kde.org ---
For doscoverability reasons I think we can add that to the menus.


Le sam. 1 janv. 2022 à 16:05,  a écrit :

> https://bugs.kde.org/show_bug.cgi?id=447785
>
> --- Comment #3 from tomash...@gmail.com ---
> Created attachment 145015
>   --> https://bugs.kde.org/attachment.cgi?id=145015=edit
> No setting for close tab in Configure Keyboard Shortcuts
>
> The problem is, I do not have the action for closing tab at all in
> Configure
> Keyboard Shortcuts (nor is it in the menus or avaiable to be put into a
> toolbar).
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

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

[konsole] [Bug 447785] No close tab or view action for either toolbar or keyboard shortcuts

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

--- Comment #4 from tcanabr...@kde.org ---
Ctrl + D is the escape code to kill the terminal / close the view.


Le sam. 1 janv. 2022 à 15:54,  a écrit :

> https://bugs.kde.org/show_bug.cgi?id=447785
>
> Bug ID: 447785
>Summary: No close tab or view action for either toolbar or
> keyboard shortcuts
>Product: konsole
>Version: 21.12.0
>   Platform: Other
> OS: Linux
> Status: REPORTED
>   Severity: normal
>   Priority: NOR
>  Component: general
>   Assignee: konsole-de...@kde.org
>   Reporter: tomash...@gmail.com
>   Target Milestone: ---
>
> I would like to be able to close a tab with CTRL+W. That does not seem to
> be
> possible at the moment. The same goes for the active view. Also there is no
> option to have these actions on the toolbar.
>
> There are ways to achieve these things, but not through toolbar or keyboard
> shortcuts, which frankly feels like a weird omission, so in case I am
> missing
> something, sorry for the noise.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

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

[systemsettings] [Bug 447790] New: If "Detailed Settings" is disabled, all the settings under it should be set to the value of "Region"

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

Bug ID: 447790
   Summary: If "Detailed Settings" is disabled, all the settings
under it should be set to the value of "Region"
   Product: systemsettings
   Version: 5.23.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: kcm_formats
  Assignee: plasma-b...@kde.org
  Reporter: doggoofsp...@gmail.com
CC: hanyo...@protonmail.com
  Target Milestone: ---

SUMMARY
If "Detailed Settings" is disabled, all the settings under it should be set to
the value of "Region". This would be great for quality of life. Right now for
me it defaults to en_US and that means that even if in my region Monday is the
first day of the week, all plasma calendars will show Sunday as the first day
of the week. 

This can and has probably lead to some confusion (Like what do you mean? My
region is correct, yet all the calendars are wrong) and implementing this
simple idea would save a lot of clicks and time (At least 10 clicks and a lot
of seconds spent trying to find your preferred locale for each setting.)

ADDITIONAL INFO
OK, I just realized that this has already been suggested in 2015 Bug#344589,
but it was closed as NOT_A_BUG after the reportee's valid point was ignored :/
Like yeah? Using region as the value of the greyed out detailed settings is way
more sensible and intuitive...

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

[dolphin] [Bug 277882] truncate filenames differently, i.e. in the middle

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

tomash...@gmail.com changed:

   What|Removed |Added

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

--- Comment #5 from tomash...@gmail.com ---
Actually, especially with this change:
https://invent.kde.org/system/dolphin/-/merge_requests/312 this feature request
still makes sense. Now the extension is shown when truncated, but otherwise it
is clipped from the end. But especially when several people shift files back
and forth, the filename often grows, ie.:
already_a_long_filename.docx
already_a_long_filename_revisions_by_A.docx
already_a_long_filename_revisions_by_A_changed_by_B.docx
etc.

In such cases, I would much rather loose a part of the filename in the middle
("a long filename") then the end (who did the revisions).

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

[kde] [Bug 447236] Entire desktop crashes and disappears

2022-01-01 Thread Rajinder Yadav

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

--- Comment #6 from Rajinder Yadav  ---
(gdb) bt
#0  QSGAreaAllocatorNode::isLeaf (this=0x18) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:93
#1  QSGAreaAllocator::deallocateInNode (this=this@entry=0x7f4668139020,
pos=..., node=0x18) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:170
#2  0x7f4703029fb6 in QSGAreaAllocator::deallocate
(this=this@entry=0x7f4668139020, rect=...)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:116
#3  0x7f47030304df in QSGOpenGLAtlasTexture::AtlasBase::remove
(this=0x7f4668139010, t=t@entry=0x7f4668a7e460)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:286
#4  0x7f470303062d in QSGOpenGLAtlasTexture::TextureBase::~TextureBase
(this=0x7f4668a7e460, __in_chrg=)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:516
#5  QSGOpenGLAtlasTexture::Texture::~Texture (this=0x7f4668a7e460,
__in_chrg=)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543
#6  0x7f4703030649 in QSGOpenGLAtlasTexture::Texture::~Texture
(this=0x7f4668a7e460, __in_chrg=)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543
#7  0x7f46ee7442bd in QScopedPointerDeleter::cleanup
(pointer=) at /usr/include/qt5/QtCore/qscopedpointer.h:60
#8  QScopedPointer
>::~QScopedPointer (this=, this=) at
/usr/include/qt5/QtCore/qscopedpointer.h:107
#9  Plasma::WindowTextureProvider::~WindowTextureProvider (this=, this=)
at
/usr/src/debug/plasma-framework-5.89.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149
#10 Plasma::WindowTextureProvider::~WindowTextureProvider (this=, this=)
at
/usr/src/debug/plasma-framework-5.89.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149
#11 0x7f470307a152 in QSGRenderThread::event (this=0x7f46f800d820,
e=0x557ad0b12de0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:493
#12 0x7f4703073b3f in QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x7f46f800d820)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:937
#13 0x7f4703075fd9 in QSGRenderThread::run (this=0x7f46f800d820) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053
#14 0x7f47013bddf1 in QThreadPrivate::start (arg=0x7f46f800d820) at
thread/qthread_unix.cpp:329
#15 0x7f4700f22427 in start_thread (arg=) at
pthread_create.c:435
#16 0x7f4700fab810 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

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

[okular] [Bug 359059] FictionBook: Incorrect whitespace treatment

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

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

[digikam] [Bug 417885] Problems on Windows Subsystem for Linux

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

--- Comment #25 from caulier.gil...@gmail.com ---
I don't understand why this do not work.

In your decompressed appimage content, go to the Qt5 library file and run ldd
like this 

[gilles@localhost lib]$ pwd 
/tmp/.mount_digiKafKsuVU/usr/lib

[gilles@localhost lib]$ ll libQt5Core.so.5 
-rwxr-xr-x 1 root root 6715872 Jan  1 19:50 libQt5Core.so.5*

[gilles@localhost lib]$ ldd libQt5Core.so.5 
linux-vdso.so.1 (0x7fff1cf29000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f61ff4cc000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x7f61ff3f1000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f61ff3ec000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x7f61ff3e7000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x7f61ff2bb000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x7f61ff0eb000)
libm.so.6 => /lib64/libm.so.6 (0x7f61fefa6000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f61fef8c000)
libc.so.6 => /lib64/libc.so.6 (0x7f61fedd2000)
/lib64/ld-linux-x86-64.so.2 (0x7f61ffb81000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7f61fed6)

Note : this is mine from the last AppImage bundle 7.5.0 :
digiKam-7.5.0-20220101T175533-x86-64.appimage

GilleS Caulier

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

[frameworks-kio] [Bug 447779] Creating a new file from templates requires root password

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

p3dima...@hotmail.it changed:

   What|Removed |Added

 CC|p3dima...@hotmail.it|

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

[frameworks-kio] [Bug 447779] Creating a new file from templates requires root password

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

p3dima...@hotmail.it changed:

   What|Removed |Added

 CC||p3dima...@hotmail.it

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

[digikam] [Bug 435897] Package fcitx support for digikam's appimage

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

--- Comment #5 from caulier.gil...@gmail.com ---
Hi Tyson,

New digiKam 7.5.0 pre-release AppImage bundle now include the famous Platform
Input Context Qt plugin : 

[gilles@localhost Downloads]$ ./digiKam-7.5.0-20220101T175533-x86-64.appimage
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--to enable all debug messages on the console, use 'export
QT_LOGGING_RULES="digikam*=true"'.
Check library libudev.so.0
Check library libxcb-dri3.so.0
Check library libcrypto.so.1.1
Check library libssl.so.1.1
-- Preloading shared libs:
:/usr/lib64/libxcb-dri3.so.0:/usr/lib64/libcrypto.so.1.1:/usr/lib64/libssl.so.1.1
Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found
Digikam::unloadQtTranslationFiles: Qt standard translations removed: 0
Digikam::loadStdQtTranslationFiles: Qt standard translations path:
"/tmp/.mount_digiKafKsuVU/usr/share/digikam/translations"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qt"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtbase"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qt_help"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtdeclarative"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtquickcontrols"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtquickcontrols2"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtmultimedia"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtwebengine"
Digikam::loadStdQtTranslationFiles: Loaded Qt standard translations "en_US"
from catalog "qtxmlpatterns"
Digikam::ApplicationSettings::setApplicationStyle: Switch to widget style: 
"breeze"
Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled
Digikam::AlbumManager::setDatabase: Database Parameters:
   Type:  "QSQLITE"
...

[gilles@localhost platforminputcontexts]$ pwd
/tmp/.mount_digiKafKsuVU/usr/plugins/platforminputcontexts

[gilles@localhost platforminputcontexts]$ ll
total 339
-rwxr-xr-x 1 root root  27152 Jan  1 19:51
libcomposeplatforminputcontextplugin.so*
-rwxr-xr-x 1 root root 180544 Jan  1 19:51
libfcitxplatforminputcontextplugin.so*  < 
-rwxr-xr-x 1 root root 139432 Jan  1 19:51
libibusplatforminputcontextplugin.so*

[gilles@localhost platforminputcontexts]$ 
[gilles@localhost ~]$ 

File to test is available at usual place : https://files.kde.org/digikam/

Please test and give us a feedback.

Best regards and happy new year

Gilles Caulier

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

[lattedock] [Bug 447689] top latte panel ignores OnAllVirtualDesktops after startup

2022-01-01 Thread Michail Vourlakos

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

--- Comment #15 from Michail Vourlakos  ---
best way to be sure is to clone the git repo and build either master
branch or v0.10 branch or you can wait for 0.10.7 to be released in a week.

Στις Σάβ 1 Ιαν 2022 στις 9:16 μ.μ., ο/η Andy3153 
έγραψε:

> https://bugs.kde.org/show_bug.cgi?id=447689
>
> --- Comment #14 from Andy3153  ---
> (In reply to Michail Vourlakos from comment #13)
> > feel free to test the patch
>
> Oh, sure! Could you please tell me how though? Is installing latte-dock-git
> from the AUR enough? Or do I need to manually clone the git repo and build
> it?
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

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

[digikam] [Bug 432526] Include Platform Input Context Qt plugin in AppImage bundle