date:20210326

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

--- Comment #11 from rubypain...@gmail.com ---
(In reply to emohr from comment #10)
> On which type of clip do you apply the rotoscope effect (MKV, MTS, and MP4)?
> 
> Does this clip have video and audio? If audio how many audio stream does the
> clip have?

Oh, my bad, sorry. It's a png, not a clip, with a transparency effect (0,750)
applied in the project bin.

When I'm editing the png in the timeline, I use the transform effect on it
(which is fine), then I use the rotoscope (which crashes KDENLIVE). The steps
to reproduce the crash is the same, just with a png, not a clip.

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

[kwin] [Bug 435002] XKB: Failed to compile keymap: Couldn't process include statement for 'latam(\0)'

2021-03-26 Thread Alberto Salvia Novella

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

Alberto Salvia Novella  changed:

   What|Removed |Added

   Platform|Other   |Manjaro

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

[kwin] [Bug 435002] New: XKB: Failed to compile keymap: Couldn't process include statement for 'latam(\0)'

2021-03-26 Thread Alberto Salvia Novella

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

Bug ID: 435002
   Summary: XKB: Failed to compile keymap: Couldn't process
include statement for 'latam(\0)'
   Product: kwin
   Version: 5.21.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libinput
  Assignee: kwin-bugs-n...@kde.org
  Reporter: es204904...@gmail.com
  Target Milestone: ---

LOG:
kwin_xkbcommon: XKB: Couldn't process include statement for 'latam(\0)'
kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
kwin_xkbcommon: XKB: Failed to compile xkb_symbols
kwin_xkbcommon: XKB: Failed to compile keymap

CAUSE:
In "~/.config/kxkbrc", "VariantList=\\0" automatically set as "\\0" on login.

WORK-AROUND:
Setting "VariantList=basic"

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

[ark] [Bug 435001] New: Ark does not preserve user generated xattrs (extended attributes) when editing/updating/saving

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

Bug ID: 435001
   Summary: Ark does not preserve user generated xattrs (extended
attributes) when editing/updating/saving
   Product: ark
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: funkybom...@gmail.com
CC: aa...@kde.org, rthoms...@gmail.com
  Target Milestone: ---

SUMMARY
Ark does not preserve user generated xattrs (extended attributes) when
editing/updating/saving a file.

STEPS TO REPRODUCE
1. Create a new TEST.zip file
--- You can do this by selecting any file in your home directory, right
clicking on it and selecting from the menu: "Compress"->"Here (as ZIP)"
2. Assign some user generated xattrs (such as Tags, Rating, Comment) to the
TEST.zip file
--- You can do this by right clicking on the new TEST.zip file, select
"Properties" from the menu, click the "Details" tab, and click on "Add..." to
select one of the existing tags or to type in a new tag. After the first tag
has been added, you can also click on "Edit..." to add/select extra tags. Click
Ok. Now our TEST.zip file should have user generated xattrs.
3. Edit/update/save the TEST.zip file
--- You can do this by adding another file in the TEST.zip file. Open the
TEST.zip file using Ark. Then select a new file from your home directory and
drag'n'drop it into Ark. The TEST.zip file should now contain *two* compressed
files. Close Ark.
4. After the above action (which triggered an edit/update/save of the
TEST.zip), the user generated xattrs of the TEST.zip have disappeared!  <--
This is an undesired behaviour. (bug)

OBSERVED RESULT
Following the above steps, the user generated xattrs of the TEST.zip file
disappear.

EXPECTED RESULT
The user generated xattrs of the TEST.zip should be preserved in all
edit/update/save scenarios.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Ark: 21.03.80
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.81
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Extension of the old bug:
https://bugs.kde.org/show_bug.cgi?id=116617

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

[okular] [Bug 419109] Preserve extended attributes when saving a file

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

funkybom...@gmail.com changed:

   What|Removed |Added

 CC||funkybom...@gmail.com

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

[kdenlive] [Bug 423574] Contrast renders grey video saturation makes less color

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[systemsettings] [Bug 386357] Minimal values of Delay and Rate in Keyboard Settings displayed with no value after re-opening

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

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

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

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

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

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

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

[systemsettings] [Bug 378297] Unable to set any Detailed Settings in Regional Settings

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

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

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

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

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

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

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

[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work

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

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

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

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

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

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

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

[kdenlive] [Bug 408583] Loading clips never completes

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[dolphin] [Bug 427118] Dolphin crashes when opening a folder mounted with sshfs

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kwin] [Bug 429104] Crash (back to SDDM) under probably rare circumstances on Wayland

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[krita] [Bug 434971] krita next 5.0.0 doesn't open

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

Bug Janitor Service  changed:

   What|Removed |Added

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

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

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

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

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

[plasmashell] [Bug 417732] KDEConnect reply to Signal message crashed on Wayland

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WORKSFORME

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

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

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

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

[kdenlive] [Bug 416677] What is the meaning of the track line painted red when this track is added?

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function

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

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

[kdenlive] [Bug 420544] Reproducable segfault

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[plasmashell] [Bug 418367] Plasmashell crashed when kdeconnect reconnected with device

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[ksmserver] [Bug 433325] Crashes after Screen Locks

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

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

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

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

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

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

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

[kdenlive] [Bug 414636] MP4 different from kdenlive

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kdenlive] [Bug 410115] Worked Perfectly on First Use, everytime I try to work with it after the timeline refuses to work.

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[klickety] [Bug 351544] Samegame 2.0 sometimes gives score of zero when you remove all balls

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

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

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

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

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

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

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

[kdenlive] [Bug 377492] Video Profiles vs Project settings issues

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[plasmashell] [Bug 417560] Entries from the context menu are not vertically centered

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

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

[kdenlive] [Bug 432689] Crash on right click in subtitle edit area

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

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

[systemsettings] [Bug 349810] Incorrect clock format for Norway

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

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

[Falkon] [Bug 433503] Falkon hangs and takes stops the OS from working

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

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

[kdenlive] [Bug 409121] kdenlive crashes on export videos

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

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

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

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

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

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

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

[kdenlive] [Bug 406785] Layout keeps re-sizing after I attempt to adjust it [video example included]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[korganizer] [Bug 434757] Cannot sync CalDAV calendars on iCloud

2021-03-26 Thread Nathan Murphree

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

--- Comment #3 from Nathan Murphree  ---
So anyhoo, I have a couple of theories here;

1. The login prompt produced by iCloud is being sent for each and every .ics
file, so as far as the davgroupware element is considered, it received a null
ics file (as it lacked basic ics structure).
2. davgroupware is not able to read the ics files produced by iCloud, possibly
due to a field present in the files themselves (this is unlikely).

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

[plasmashell] [Bug 435000] New: Crashed when i opened konsole

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

Bug ID: 435000
   Summary: Crashed when i opened konsole
   Product: plasmashell
   Version: 5.21.3
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jack080...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.21.3)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.10-arch1-1 x86_64
Windowing System: X11
Drkonqi Version: 5.21.3
Distribution: EndeavourOS

-- Information about the crash:
- What I was doing when the application crashed:
Tried to open konsole
- Unusual behavior I noticed:
Konsole's icon became too bright and no open animation after clicking it
- Custom settings of the application:
None

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x7fa8004d79a4 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#5  0x7fa7fa546ac4 in  () at
/usr/lib/qt/plugins/platforminputcontexts/libkimeplatforminputcontextplugin.so
#6  0x7fa7fa546c24 in  () at
/usr/lib/qt/plugins/platforminputcontexts/libkimeplatforminputcontextplugin.so
#7  0x7fa8004d7666 in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#8  0x7fa801176792 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#9  0x7fa8004d7a2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#10 0x7fa8008b1594 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() at /usr/lib/libQt5Gui.so.5
#11 0x7fa800886bb5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#12 0x7fa7fb3c416c in  () at /usr/lib/libQt5XcbQpa.so.5
#13 0x7fa7fe8bcf9c in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#14 0x7fa7fe910a49 in  () at /usr/lib/libglib-2.0.so.0
#15 0x7fa7fe8ba6f1 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#16 0x7fa800530691 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#17 0x7fa8004d63ac in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#18 0x7fa8004de844 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#19 0x55aceb7ff20b in  ()
#20 0x7fa7ffe9db25 in __libc_start_main () at /usr/lib/libc.so.6
#21 0x55aceb7ff33e in  ()
[Inferior 1 (process 2078) detached]

Possible duplicates by query: bug 434868, bug 434843, bug 434823, bug 434809,
bug 434789.

Reported using DrKonqi

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

[plasma-pa] [Bug 434769] Volume adjustment goes offset

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/plasma-pa/commit/52cb6b0 |ma/plasma-pa/commit/b0f7cfc
   |eecc3092708c207346a13a36e77 |cf80d00d9e76efa05d02bc2fc94
   |2a6bca  |b4318d

--- Comment #4 from Nate Graham  ---
Git commit b0f7cfccf80d00d9e76efa05d02bc2fc94b4318d by Nate Graham.
Committed on 27/03/2021 at 03:26.
Pushed by ngraham into branch 'Plasma/5.21'.

Round volume to avoid increasing or decreasing by more than stepSize

Sometimes when you increase or decrease the volume using the key on your
keyboard or a global shortcut, it will change by more than the stepSize.
For example when you're at 40% volume and go up when a stepSize of 5%,
sometimes it will change to 46% volume, not 45%.

The reason for this is that the Volume number we get from PulseAudio and
then manipulate is a float. So we have to round it down to avoid
accumulating errors over time. The percentage display function already
rounds, so let's do the same thing in the functions to increase and
decrease the volume.

We should also use Math.floor() rather than Math.round() to ensure
consistency in the values we're using.
FIXED-IN: 5.21.4


(cherry picked from commit 52cb6b0eecc3092708c207346a13a36e772a6bca)

M  +2-2applet/contents/ui/main.qml

https://invent.kde.org/plasma/plasma-pa/commit/b0f7cfccf80d00d9e76efa05d02bc2fc94b4318d

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

[kup] [Bug 434986] option to configure kup with a right click on the tray icon

2021-03-26 Thread Simon Persson

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

Simon Persson  changed:

   What|Removed |Added

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

--- Comment #1 from Simon Persson  ---
Hello! Thanks for taking the time to suggest an idea. In fact this was recently
added and will be part of the next released version.

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

[plasma-pa] [Bug 434769] Volume adjustment goes offset

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

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.21.4
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-pa/commit/52cb6b0
   ||eecc3092708c207346a13a36e77
   ||2a6bca

--- Comment #3 from Nate Graham  ---
Git commit 52cb6b0eecc3092708c207346a13a36e772a6bca by Nate Graham.
Committed on 22/03/2021 at 18:07.
Pushed by ngraham into branch 'master'.

Round volume to avoid increasing or decreasing by more than stepSize

Sometimes when you increase or decrease the volume using the key on your
keyboard or a global shortcut, it will change by more than the stepSize.
For example when you're at 40% volume and go up when a stepSize of 5%,
sometimes it will change to 46% volume, not 45%.

The reason for this is that the Volume number we get from PulseAudio and
then manipulate is a float. So we have to round it down to avoid
accumulating errors over time. The percentage display function already
rounds, so let's do the same thing in the functions to increase and
decrease the volume.

We should also use Math.floor() rather than Math.round() to ensure
consistency in the values we're using.
FIXED-IN: 5.21.4

M  +2-2applet/contents/ui/main.qml

https://invent.kde.org/plasma/plasma-pa/commit/52cb6b0eecc3092708c207346a13a36e772a6bca

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

[neon] [Bug 434999] Neon user edition does not boot on new Intel Tiger Lake laptop

2021-03-26 Thread Vishal Rao

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

--- Comment #1 from Vishal Rao  ---
Created attachment 137096
  --> https://bugs.kde.org/attachment.cgi?id=137096=edit
lshw output from ubuntu 20.04.2

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

[neon] [Bug 434999] Neon user edition does not boot on new Intel Tiger Lake laptop

2021-03-26 Thread Vishal Rao

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

Vishal Rao  changed:

   What|Removed |Added

 CC||vishal...@gmail.com

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

[neon] [Bug 434999] New: Neon user edition does not boot on new Intel Tiger Lake laptop

2021-03-26 Thread Vishal Rao

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

Bug ID: 434999
   Summary: Neon user edition does not boot on new Intel Tiger
Lake laptop
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: vishal...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 137095
  --> https://bugs.kde.org/attachment.cgi?id=137095=edit
dmesg output from ubuntu 20.04.2

Trying the latest Neon user ISO on a new HP Pavilion 14 laptop model dv0054tu
with Intel Core i5 1135G7 CPU and Iris Xe iGPU - Tiger Lake platform - does not
work - meaning it boots to blank screen - and unresponsive - after a few
moments pressing the power key immediately shuts down the laptop indicating
some sort of hang.

FYI, the stock Ubuntu 20.04 with the 5.4 kernel boots into live session, the
stock ubuntu 20.10 with kernel 5.8 boots and everything appears to work well.
Tried the new ubuntu 20.04.2 release which has kernel 5.8 and it works well.

This current Neon user ISO has the latest HWE kernel 5.8 yet it does not boot.

I have tried some kernel boot parameters like nomodeset along with
i915.modeset=0 but those didn't work.

I am unable to switch to TTY or anything to look at any logs etc. even if I
remove the "quiet splash" options there is just blank screen.

Any suggestions to troubleshoot/fix this issue?

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

[plasmashell] [Bug 434997] No way to delete recently-used Emojis

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

Nate Graham  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
   Version Fixed In||5.22
  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-desktop/commit/35
   ||a9c7a5d1787b627f27a388b0be4
   ||cefd94df78e
 Resolution|--- |FIXED

--- Comment #2 from Nate Graham  ---
Git commit 35a9c7a5d1787b627f27a388b0be4cefd94df78e by Nate Graham.
Committed on 27/03/2021 at 02:12.
Pushed by ngraham into branch 'master'.

[applets/emojier] Add a "Clear History" button

Most other places where we show the user their recently used/opened
stuff, there's an option to clear the history. But not in the Emoji
picker. We should offer one here too.
FIXED-IN: 5.22

M  +7-0applets/kimpanel/backend/ibus/emojier/emojier.cpp
M  +8-0applets/kimpanel/backend/ibus/emojier/ui/CategoryPage.qml
M  +1-1applets/kimpanel/backend/ibus/emojier/ui/emojier.qml

https://invent.kde.org/plasma/plasma-desktop/commit/35a9c7a5d1787b627f27a388b0be4cefd94df78e

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

[kwin] [Bug 433471] Cover Switch and Flip Switch animations works unreliably after upgrade to Plasma 5.21

2021-03-26 Thread Bharadwaj Raju

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

Bharadwaj Raju  changed:

   What|Removed |Added

 CC||bharadwaj.raju777@protonmai
   ||l.com

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

[Discover] [Bug 410972] [Arch] AUR support

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

2wxsy5823...@opayq.com changed:

   What|Removed |Added

 CC||jur...@outlook.de

--- Comment #6 from 2wxsy5823...@opayq.com ---
*** Bug 434994 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 434994] AUR support in Discover

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

2wxsy5823...@opayq.com changed:

   What|Removed |Added

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

--- Comment #1 from 2wxsy5823...@opayq.com ---


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

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

[systemsettings] [Bug 434998] New: No option to forget/reset frequently visited KCMs list

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

Bug ID: 434998
   Summary: No option to forget/reset frequently visited KCMs list
   Product: systemsettings
   Version: 5.21.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

Most other places where we show the user their recently used/opened stuff,
there's an option to clear the history. But not in the System Settings landing
page. We should offer one here too.

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

[plasmashell] [Bug 434997] No way to delete recently-used Emojis

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|REPORTED|ASSIGNED
 Ever confirmed|0   |1

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

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

[tellico] [Bug 428430] Please add TheTVDB.com as a data source

2021-03-26 Thread Robby Stephenson

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

Robby Stephenson  changed:

   What|Removed |Added

   Version Fixed In||3.4.1
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/offi
   ||ce/tellico/commit/b4212937f
   ||f2eeb000dfe66f4c92caf89b468
   ||302a

--- Comment #2 from Robby Stephenson  ---
Git commit b4212937ff2eeb000dfe66f4c92caf89b468302a by Robby Stephenson.
Committed on 27/03/2021 at 00:36.
Pushed by rstephenson into branch 'master'.

Add data source for TheTVDB
FIXED-IN: 3.4.1

M  +4-0ChangeLog
M  +1-0src/fetch/CMakeLists.txt
M  +2-1src/fetch/fetch.h
M  +2-0src/fetch/fetcherinitializer.cpp
A  +576  -0src/fetch/thetvdbfetcher.cpp [License: GPL (v2/3)]
A  +122  -0src/fetch/thetvdbfetcher.h [License: GPL (v2/3)]
M  +6-0src/tests/CMakeLists.txt
A  +81   -0src/tests/thetvdbfetchertest.cpp [License: GPL (v2/3)]
C  +11   -87   src/tests/thetvdbfetchertest.h [from: src/fetch/fetch.h - 056%
similarity]

https://invent.kde.org/office/tellico/commit/b4212937ff2eeb000dfe66f4c92caf89b468302a

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

[plasmashell] [Bug 434997] New: No way to delete recently-used Emojis

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

Bug ID: 434997
   Summary: No way to delete recently-used Emojis
   Product: plasmashell
   Version: 5.21.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Emoji Selector
  Assignee: plasma-b...@kde.org
  Reporter: n...@kde.org
  Target Milestone: 1.0

Most other places where we show the user their recently used/opened stuff,
there's an option to clear the history. But not in the Emoji picker. We should
offer one here too.

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

[dolphin] [Bug 434911] Dolphin opens two tabs if tabs are disabled

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
   Keywords||usability
 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED

--- Comment #3 from Nate Graham  ---
Great!

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

[plasmashell] [Bug 434996] New: discover is add to favourites

2021-03-26 Thread notrealname

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

Bug ID: 434996
   Summary: discover is add to favourites
   Product: plasmashell
   Version: master
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: smurtaza...@outlook.com
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
every restart discover is add to favourites
every time i change activity discover is added to favourites

STEPS TO REPRODUCE
1. remove discover from favourites 
2. restart or change activity
3. discover is in your favourites

OBSERVED RESULT
discover in fav

EXPECTED RESULT
fav to stay the same

Operating System: Manjaro Linux
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.6-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11

ADDITIONAL INFORMATION
it is a bug in all application launcher/menu

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

[plasmashell] [Bug 434932] Emoji Selector should enter the selected Emojis directly

2021-03-26 Thread Alejandro Díaz

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

Alejandro Díaz  changed:

   What|Removed |Added

 CC||ealejan...@outlook.com

--- Comment #2 from Alejandro Díaz  ---
A low-effort solution might be to implement the app in such a way that:

1. Opening the app leaves you in the search emoji field (so you can search the
emoji you want right away)
2. Allowing to change the selected emoji with the keyboard (arrow keys) without
losing focus on the search field
3. Copying the selected emoji on 
4. Having the app close after pressing enter (which should return focus to the
app that was being used)


That would result in a workflow:

1. Alt + .
2. Type desired emoji (or select from recent with arrow keys)
3. Press 
4. Ctrl + v
(important: hands never leave the keyboard)

This would be less disruptive and roughly imitates the way Spectacle works
(Print Scr shortcut)

All the functionality needed is already implemented in the app for this work.
(minus the fact that the recent emoji view doesn't allow search and seems you
can't search the recen emojis at all)

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

[lokalize] [Bug 434995] New: wish: Check for simple string features and compare original text and translation

2021-03-26 Thread Frank Steinmetzger

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

Bug ID: 434995
   Summary: wish: Check for simple string features and compare
original text and translation
   Product: lokalize
   Version: 20.12.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: editor
  Assignee: sdepi...@gmail.com
  Reporter: war...@gmx.de
CC: sha...@ukr.net
  Target Milestone: ---

Dear devs,

I just finished reviewing a bigger po file which had lots of discrepancies
between original and translated language in terms of how the strings ended. In
particular, there were many inconsistencies regarding the full stop in many
tooltip texts. This made me think that this is a rather easy thing to spot
programmatically and write up a wish about it.

Especially in larger files with either many strings (in large applications) or
with huge texts (think handbooks) checking such details is tedious work and
thus is usually not done in one session. I can imagine it would be of great
assistance if there were an automated process that gathers some simple string
metrics and compares them between the two languages in a file.

Some metrics I can think of:
- the ending of the string (punctuation mark)
- number of sentences
- number of line breaks
- the number of placeholders ("%" + number)
- presence of plural forms
- presence and count of HTML tags (not necessarily entities such as , but
structural things like ,  or )

Ideally, those metrics can all be toggled by the user, because not all are
applicable to every use case. For example, comparing the number of sentences is
not useful when translating long paragraphs of a documentation handbook,
because sometimes the text needs to be restructured due to language
peculiarities.

Once a metrics mismatch between a string’s two languages is found, the entry is
marked in some way. Perhaps as a new status. A string that currently would be
shown as Finished, but has a mismatch, is instead marked as Caution (or a
better-fitting term). For any translation status other than Finished, I think
the user has to look at the string anyways, so in such cases there is no need
to point him towards the metrics.

I also don’t think it’s necessary to show this in the project overview. First
and foremost of course due to the performance impact. But also because, as I
said, it is rather dependent on the context and those metrics are not really a
quantitative measure, but rather a qualitative one for a quick overview or for
a final sanity check before committing the file. Thus it would suffice to do
the comparison only in the editor tab of an individual file.

What do you think?

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

[ksmserver] [Bug 434369] Login after logout hangs for 3 minutes

2021-03-26 Thread medin

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

medin  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0
 Status|NEEDSINFO   |REPORTED

--- Comment #10 from medin  ---

Without systemd startup : 


=> Wayland
Wayland always starts desktop without failing or being stuck even if it
generates these crashes (coredumpctl)
/usr/bin/akonadi_maildir_resource
/usr/bin/kwalletd5
/usr/lib/baloorunner
/usr/lib/kactivitymanagerd
/usr/bin/korgac
/usr/bin/akonadi_migration_agent
/usr/bin/akonadi_newmailnotifier_agent
/usr/bin/kalarm
/usr/bin/akonadi_followupreminder_agent
/usr/bin/akonadi_maildispatcher_agent
/usr/bin/yakuake
/usr/bin/akonadi_notes_agent
/usr/bin/akonadi_mailfilter_agent
/usr/bin/akonadi_sendlater_agent
/usr/bin/akonadi_unifiedmailbox_agent
/usr/bin/msm_kde_notifier
/usr/bin/akregator


=> X11
With X11 it fails a lot with little success to logout then login, it generates
this crash (coredumpctl)
/usr/bin/kglobalaccel5

When it fails (which is often) it becomes either stuck infinitely at boot
splash or takes many minutes to show desktop.




With systemd startup : 


=> Wayland
Wayland always starts desktop without failing or being stuck even if it
generates these crashes (coredumpctl)
/usr/lib/kf5/klauncher
/usr/bin/kded5
/usr/bin/kwalletd5
/usr/bin/yakuake
/usr/bin/kded5
/usr/bin/akregator
/usr/lib/xdg-desktop-portal-kde
/usr/bin/ksplashqml


=> X11
With X11 it fails (not always) and generates this crash (coredumpctl)
/usr/bin/kglobalaccel5

When it fails (which is often) it becomes either stuck infinitely at boot
splash or takes many minutes to show desktop.

And running thissystemd-analyze shows :
systemd-analyze  --user  blame
50.983s plasma-ksmserver.service
39.376s plasma-ksplash-ready.service
31.259s plasma-plasmashell.service  
30.843s plasma-restoresession.service

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

[krita] [Bug 434993] Angle selector widget in status bar incorrectly denotes 180 degrees at certain ranges of rotation

2021-03-26 Thread Deif Lou

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

Deif Lou  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/krita/commit/3404cb669 |hics/krita/commit/66822cda7
   |8c46488ae70ca55a1c4838aac27 |311881678a95748e0d363de8c47
   |6bec|ee88

--- Comment #3 from Deif Lou  ---
Git commit 66822cda7311881678a95748e0d363de8c47ee88 by Deif Lou.
Committed on 26/03/2021 at 23:28.
Pushed by deiflou into branch 'krita/4.3'.

Fix angle range in the angle selector in status bar and overview docker

(cherry picked from commit 60047275c25495d50bebfd3e77a8516ed6a9f619)

M  +1-1libs/ui/kis_statusbar.cc
M  +2-8plugins/dockers/overview/overviewdocker_dock.cpp

https://invent.kde.org/graphics/krita/commit/66822cda7311881678a95748e0d363de8c47ee88

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

[krita] [Bug 434993] Angle selector widget in status bar incorrectly denotes 180 degrees at certain ranges of rotation

2021-03-26 Thread Deif Lou

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

Deif Lou  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/3404cb669
   ||8c46488ae70ca55a1c4838aac27
   ||6bec
 Resolution|--- |FIXED

--- Comment #2 from Deif Lou  ---
Git commit 3404cb6698c46488ae70ca55a1c4838aac276bec by Deif Lou.
Committed on 26/03/2021 at 23:30.
Pushed by deiflou into branch 'master'.

Fix angle range in the angle selector in status bar and overview docker

M  +1-1libs/ui/kis_statusbar.cc
M  +2-8plugins/dockers/overview/overviewdocker_dock.cpp

https://invent.kde.org/graphics/krita/commit/3404cb6698c46488ae70ca55a1c4838aac276bec

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

[Discover] [Bug 434994] New: AUR support in Discover

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

Bug ID: 434994
   Summary: AUR support in Discover
   Product: Discover
   Version: 5.21.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: jur...@outlook.de
CC: aleix...@kde.org
  Target Milestone: ---

Hey dear KDE team,

Would it be possible to add an option for AUR support in Discover? That would
be a lot better for me because then I wouldn't have to use two different
applications to manage different software.

Thanks for all that nice software and many greetings :)


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

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

[krunner] [Bug 390266] Krunner window width should be adjustible

2021-03-26 Thread Dashon

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

--- Comment #7 from Dashon  ---
I'm also intrested in an adjustable width. I tried playing around with
QT_SCALE_FACTOR, but while it makes things bigger. It doesn't solve the cutoff
issue.

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

[krunner] [Bug 390266] Krunner window width should be adjustible

2021-03-26 Thread Dashon

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

Dashon  changed:

   What|Removed |Added

 CC||dashonww...@pm.me

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

[krita] [Bug 434993] Angle selector widget in status bar incorrectly denotes 180 degrees at certain ranges of rotation

2021-03-26 Thread Deif Lou

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

Deif Lou  changed:

   What|Removed |Added

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

--- Comment #1 from Deif Lou  ---
Just for the record, this bug is also present in the overview docker and was
kind of present before the angle widget was introduced. I copied some code from
the overview docker angle handling, which uses the range [-180, 180]. The
problem is that the range of the canvas rotation is [-360, 360] so there is a
mismatch between the acual angle an the angle shown in the slider (now angle
selector) in the overview docker. This behavior got propagated to the angle
selector in the status bar, as I copied the code from the overview docker.
The solution is to change the ranges of the angle selectors both in the status
bar and the overview docker.

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

[ksmserver] [Bug 434369] Login after logout hangs for 3 minutes

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

--- Comment #9 from storagebi...@gmail.com ---
The problem occurs only with x11, never wayland.

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

[dolphin] [Bug 434911] Dolphin opens two tabs if tabs are disabled

2021-03-26 Thread Yan

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

--- Comment #2 from Yan  ---
Yes to both, then let's wait for merge

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working on X11

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

--- Comment #17 from 80p3fy7...@cloud-mail.top ---
(In reply to Andrey from comment #16)
> (In reply to 80p3fy75dc from comment #14)
> > "Alt+`" works for me on Wayland but not on X11. Tried with English US and
> > French keymap (both work on Wayland, both fail on X11).
> 
> Was your US layout configured first in the list, or it doesn't matter?

I'm getting the same behaviors regardless of the layout order. Tried with
French first and US second, then US first and French second.

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

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-03-26 Thread Michael Pyne

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

--- Comment #7 from Michael Pyne  ---
If it occurs in multiple programs it is likely a style bug (presumably breeze).

If you're up to it, you could try running kmail as "kmail -style fusion" to try
a different theme (Qt has a "Fusion" theme built-in) and see if the black
square still comes up at random intervals.

Note that KMail will look a bit different if you run it this way since the
style is different.

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

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-03-26 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #6 from David Edmundson  ---
Can you see if "killall xembedsniproxy" fixes it?

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working on X11

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

Andrey  changed:

   What|Removed |Added

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

--- Comment #16 from Andrey  ---
(In reply to 80p3fy75dc from comment #14)
> "Alt+`" works for me on Wayland but not on X11. Tried with English US and
> French keymap (both work on Wayland, both fail on X11).

Was your US layout configured first in the list, or it doesn't matter?

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working on X11

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

Andrey  changed:

   What|Removed |Added

Summary|Custom shortcuts containing |Custom shortcuts containing
   |accented keys ("é" "è" "ç"  |accented keys ("é" "è" "ç"
   |"à") aren't working at all  |"à") aren't working on X11

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #15 from Andrey  ---
Ah, sorry - switching desktop should be Global shortcuts too.
Well, I see why it works now - these symbols seem are actually a Latin script
letters, just with diacritics. All these letters must be presented in Qt::Key
set: https://doc.qt.io/qt-5/qt.html#Key-enum, so current layout doesn't need to
be switched internally for the conversion.

The problem began with non-Latin symbols not represented in Qt::Key set.
So this is actually a different issue than Bug 375518 :)
Thank you for cooperation!

Let's leave it open since you saying it still an issue for X11.

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

80p3fy7...@cloud-mail.top changed:

   What|Removed |Added

URL||`

--- Comment #14 from 80p3fy7...@cloud-mail.top ---
(In reply to Andrey from comment #13)
> Please note Global and Local (app-specific) shortcuts might behave
> differently.
> bug 375518 is specific to Global shortcuts, so it's worth trying to override
> anything there, e.g KWin's standard Alt+` shortcut with Atl+È etc. and see
> if it works.

I've just tried.

With French keymap, "Alt+É" as custom shortcut for "Alt+`" ("Walk Through
Windows of Current Application) work fine here on Wayland. Doesn't work on X11.

"Alt+`" works for me on Wayland but not on X11. Tried with English US and
French keymap (both work on Wayland, both fail on X11).

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

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-03-26 Thread Christophe Giboudeaux

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

--- Comment #5 from Christophe Giboudeaux  ---
I don't see it anymore since months.

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #13 from Andrey  ---
Please note Global and Local (app-specific) shortcuts might behave differently.
bug 375518 is specific to Global shortcuts, so it's worth trying to override
anything there, e.g KWin's standard Alt+` shortcut with Atl+È etc. and see if
it works.

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

[krita] [Bug 434993] New: Angle selector widget in status bar incorrectly denotes 180 degrees at certain ranges of rotation

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

Bug ID: 434993
   Summary: Angle selector widget in status bar incorrectly
denotes 180 degrees at certain ranges of rotation
   Product: krita
   Version: 4.4.3
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: tomtomtomreportin...@gmail.com
  Target Milestone: ---

SUMMARY
When rotating the canvas through other means besides the angle selector widget
in the status bar, the spinbox starts incorrectly indicating an angle of about
180 degrees when rotating into a certain range. This occurs both with canvas
input shortcuts and with the View -> Canvas -> Rotate actions.

STEPS TO REPRODUCE
1. Using canvas input shortcuts, rotate the canvas clockwise towards 180
degrees.

OBSERVED RESULT
* If using discrete steps, rotating clockwise past 180 degrees will make the
spinbox continue to denote 180 degrees until 0 degrees is reached. Similar
behavior happens in the inverse when rotating counterclockwise.
* If using smoothed canvas input rotation, the spinbox will "snap" to an 180
degree angle while rotating towards and out of it.

In both cases, there is no functional impact. The widget's spinbox merely
displays the wrong angle.

EXPECTED RESULT
The correct angle should be displayed in the spinbox.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.12.9 (Appimage)  

ADDITIONAL INFORMATION
Since this angle indicator was not displayed in the status bar in previous
versions, it is technically not a regression.

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

[okular] [Bug 252596] okular printing options not working when printing to file (pdf/ps)

2021-03-26 Thread Grósz Dániel

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

Grósz Dániel  changed:

   What|Removed |Added

 CC||groszdaniel...@gmail.com

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

[systemsettings] [Bug 434988] "Shift" key cannot be used with some shortcuts combinations

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

--- Comment #2 from 80p3fy7...@cloud-mail.top ---
(In reply to Andrey from comment #1)
> Could you check if it differs on Wayland?

I've just tried on Wayland and it doesn't make any difference unfortunately.
Same behavior than on X11.

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

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-03-26 Thread Charles Samuels

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

--- Comment #4 from Charles Samuels  ---
The same problem appears to exist in qBittorrent


In both cases, it seems to be over a QSplitter.

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #12 from 80p3fy7...@cloud-mail.top ---
I've just tried on Wayland and all the accented keys work just fine here. I can
successfully switch to desktop 2 with "Meta+É", to Desktop 7 with "Meta+È", to
Desktop 9 with "Meta+Ç", to Desktop 10 with "Meta+À"

So the issue is only occurring on X11.

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

[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files

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

--- Comment #1 from Andrey  ---
Just a note - the key mapping GUI doesn't necessary have to operate on XKB
level.
For trivial physical keys remapping, much simpler would be to change keycodes
they produce. It can be done via udev hwdb:
https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes:

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

[kwin] [Bug 434992] New: Switching keyboard layouts stopped working completely on X11

2021-03-26 Thread t3n3t

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

Bug ID: 434992
   Summary: Switching keyboard layouts stopped working completely
on X11
   Product: kwin
   Version: 5.21.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: t3...@yandex.ru
  Target Milestone: ---

SUMMARY

Switching keyboard layouts stopped working completely on X11.


STEPS TO REPRODUCE
1. Add secondary keyboard language layout (in my case i use US and RU).
2. Try to switch it via hotkey or system tray applet.

OBSERVED RESULT
US layout remains unchanged, only way to switch is to manually do it via
setxkbmap.

EXPECTED RESULT
Switch to another layout.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Arch Linux, Kernel: 5.11.9-arch1-1, 
KDE Plasma Version: Plasma 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Switching keyboard layouts does work in Plasma Wayland session, any other DE/WM
like Gnome(both X11 and Wayland), i3wm, awesomewm, XFCE. It doesn't work
anymore in Plasma X11 session exclusively. Tried full reinstall, switching
users, etc - nothing fixes this behaviour.

This bug breaks workflow in Plasma X11 session completely for multi-language
users.

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

[kwin] [Bug 422645] Often when Firefox starts, desktop content briefly shifts down and right

2021-03-26 Thread Matej Mrenica

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

Matej Mrenica  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Matej Mrenica  ---
It was originally on Wayland but I can't reproduce anymore.

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

[gcompris] [Bug 434991] New: Solar system units for days and years are inconsistent (and wrong)

2021-03-26 Thread Karl Ove Hufthammer

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

Bug ID: 434991
Summary: Solar system units for days and years are inconsistent
(and wrong)
Product: gcompris
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jaz...@gmail.com
Reporter: k...@huftis.org
Target Milestone: ---

SUMMARY
The answers in the solar system activity have inconsistent units, and the
numbers don’t always correspond to the units used. Some questions use ‘days’,
others ‘Earth days’. Some questions use ‘years’, other ‘Earth years’. For the
questions that use ‘days’, the answer is actually wrong: The numbers listed
seem to correspond the number of Earth days, not the number of days. (Though I
haven’t checked all questions.)

For example, the question ‘How long is a year on Mercury?’ have the response
options in ‘days’ units, ‘365 days’, ‘433 days’, ‘88 days’ and ‘107 days’, with
‘88 days’ as the ‘correct’ answer. But the *actual* correct answer is ‘88 Earth
days’ (which is actually only 0.5 (solar) *day*, since Mercury spins so
incredibly slowly). Source:
https://solarsystem.nasa.gov/planets/mercury/in-depth/
On the other hand, the question ‘How long is one rotation on Mercury?’
(correctly) lists the response options in ‘Earth days’ units, with ‘59 Earth
days’ as the correct response.

(BTW, note that this is different than the ‘Day’ value listed on the NASA site.
The ‘Day’ is the number of *solar* days, i.e. the time needed for the sun to
return to the same place in the sky, which is 176 Earth days, but the planet
only needs ~59 Earth days to complete a rotation.)

The same hold for the ‘years’ value. This needs to be changed to ‘Earth years’.
(If not, the answer to all the questions would obviously all be ‘1 year’ …)

STEPS TO REPRODUCE
1. Launch the solary system activity.
2. Click on a planet.
3. Answer the questions until you get a ‘How long is one rotation on PLANET?’
or ‘How long does it take for PLANET to make one revolution around the Sun?’.

OBSERVED RESULT
Some response options are days, some Earth days, some years and some Earth
years.

EXPECTED RESULT
The only two response options should be Earth days and Earth years. (Except for
the questions about Earth itself; then they can be ‘days’. I think having
‘Earth days’ here would be confusing, though not incorrect.)

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

[digikam] [Bug 434990] Facetags in HTML-Gallery

2021-03-26 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

Version|7.1.0   |7.2.0
   Severity|normal  |wishlist
 CC||metzping...@gmail.com

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #11 from 80p3fy7...@cloud-mail.top ---
(In reply to Andrey from comment #10)
> (In reply to 80p3fy75dc from comment #8)
> > "é" "è" "ç" and "à" can all be typed without any additional modifiers with
> > French layout (AZERTY) 
> > 
> > "É" "È" "Ç" and "À" only require caps lock turned on, as you would expect.
> > No additional modifiers either.
> > 
> So does your report belong to upper or lower case, or both?

System Settings Shortcuts section will always register the upper-case ("É" ;
"È" ; "Ç" "À") even if you press "é" ; "è", "ç" or "à".

This is true for any letter, at least for me. Press "Meta+m" and it will
register as "Meta+M", press "Meta+y" and it will register as "Meta+Y" and so
on.

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

[akregator] [Bug 429444] Cannot delete feeds or folders

2021-03-26 Thread Tomas Trnka

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

Tomas Trnka  changed:

   What|Removed |Added

   Assignee|kdepim-b...@kde.org |tomastr...@gmx.com

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

[akregator] [Bug 429444] Cannot delete feeds or folders

2021-03-26 Thread Tomas Trnka

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

Tomas Trnka  changed:

   What|Removed |Added

 CC||tomastr...@gmx.com
 Status|CONFIRMED   |ASSIGNED
  Component|feed parser |general

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

[kate] [Bug 391208] Kwrite needlessly asks whether to save or discard changes

2021-03-26 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

   Version Fixed In||5.81
  Latest Commit||https://invent.kde.org/fram
   ||eworks/ktexteditor/commit/1
   ||274d1d59f3f601946fb5bc8e1a6
   ||0b8c7478c3ec
 Resolution|INTENTIONAL |FIXED

--- Comment #2 from Christoph Cullmann  ---
Git commit 1274d1d59f3f601946fb5bc8e1a60b8c7478c3ec by Christoph Cullmann, on
behalf of Nate Graham.
Committed on 26/03/2021 at 20:01.
Pushed by cullmann into branch 'master'.

Don't warn about unsaved changes when closing if blank and unsaved

In the case where the document is marked as modified, but is both blank
and unsaved, there's no reason to pester the user about unsaved changes
because there are no unsaved changes. So in this case, let's not bug
them about it.
FIXED-IN: 5.81

M  +4-1src/document/katedocument.cpp

https://invent.kde.org/frameworks/ktexteditor/commit/1274d1d59f3f601946fb5bc8e1a60b8c7478c3ec

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

[systemsettings] [Bug 434988] "Shift" key cannot be used with some shortcuts combinations

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

Andrey  changed:

   What|Removed |Added

 CC||butir...@gmail.com

--- Comment #1 from Andrey  ---
Could you check if it differs on Wayland?

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

[Discover] [Bug 434985] Discover error

2021-03-26 Thread Vili

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

--- Comment #2 from Vili  ---
* What's your distribution? Idk? (I just started to use linux)
* Do you have the required Discover backends installed (packagekit and maybe
flatpak)?  Idk?
* Does Discover work as expected after waiting some time? Yes.

Lähetetty iPhonesta

> Alois Wohlschlager  kirjoitti 26.3.2021 kello 21.10:
> 
> * What's your distribution?
> * Do you have the required Discover backends installed (packagekit and maybe
> flatpak)?
> * Does Discover work as expected after waiting some time?

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

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-03-26 Thread Charles Samuels

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

Charles Samuels  changed:

   What|Removed |Added

 CC||char...@derkarl.org

--- Comment #3 from Charles Samuels  ---
I get it too on Debian Bullseye. I'd include a screenshot, but it's pretty much
the same.

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

[digikam] [Bug 434990] New: Facetags in HTML-Gallery

2021-03-26 Thread Patrick

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

Bug ID: 434990
   Summary: Facetags in HTML-Gallery
   Product: digikam
   Version: 7.1.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Plugin-Generic-HTMLGallery
  Assignee: digikam-bugs-n...@kde.org
  Reporter: patr...@meizinger.de
  Target Milestone: ---

SUMMARY
Just have a question. Is it possible, or planed, to create a HTML-Gallery that
shows the face-tags when you touch the face with the mouse pointer, or you can
highlite all taged faces in one picture? 




STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

Andrey  changed:

   What|Removed |Added

 CC||butir...@gmail.com

--- Comment #10 from Andrey  ---
(In reply to 80p3fy75dc from comment #8)
> "é" "è" "ç" and "à" can all be typed without any additional modifiers with
> French layout (AZERTY) 
> 
> "É" "È" "Ç" and "À" only require caps lock turned on, as you would expect.
> No additional modifiers either.
> 
So does your report belong to upper or lower case, or both?

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

[plasma-pa] [Bug 434217] Keyboard mute key mutes all devices, not just the default device

2021-03-26 Thread Benjamin Xiao

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

--- Comment #8 from Benjamin Xiao  ---
Sorry for the delay, but I've finally got around to setting up a KDE dev
environment on a VM and it is all working now. I will start looking through the
source code and attempt a fix.

To avoid cluttering up this bug report with logistical questions, would the
best way to reach you be via the webchat.kde.org Matrix server?

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #9 from Andrey  ---
If it's bug 375518, I'm afraid I have a bad news - the second part of the fix
is on Qt side, and even if it's accepted - we won't get full fix until we port
to Qt 6.
That is something beyond technical issues.
https://codereview.qt-project.org/c/qt/qtbase/+/339895

But I see you are saying you run X11 - then it might be a different issue. Bug
375518 is wayland-specific as long as you first layout is US or like.
Anyway, I'll test the fix as soon I get a chance.

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

[Discover] [Bug 434985] Discover error

2021-03-26 Thread Alois Wohlschlager

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

Alois Wohlschlager  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||alo...@gmx-topmail.de
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Alois Wohlschlager  ---
Please specify more information, including the following:

* What's your distribution?
* Do you have the required Discover backends installed (packagekit and maybe
flatpak)?
* Does Discover work as expected after waiting some time?

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

[valgrind] [Bug 434775] drd/tests/swapcontext.c doesn't build with musl

2021-03-26 Thread Yi Fan Yu

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

--- Comment #3 from Yi Fan Yu  ---
I tried applying that patch to oe-core build and it still fails with this:

So musl does provide  as a header, but you cannot link to any of
the *context calls. The error is a linker failure.

```
/ala-lpggp31/yyu1/oe-core/build/tmp-musl/work/core2-64-oe-linux-musl/valgrind/3.17.0-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux-musl/../../libexec/x86_64-oe-linux-musl/gcc/x8:
|
/usr/src/debug/valgrind/3.17.0-r0/valgrind-3.17.0/memcheck/tests/linux/stack_changes.c:23:
undefined reference to `setcontext'
|
/ala-lpggp31/yyu1/oe-core/build/tmp-musl/work/core2-64-oe-linux-musl/valgrind/3.17.0-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux-musl/../../libexec/x86_64-oe-linux-musl/gcc/x8:
|
/usr/src/debug/valgrind/3.17.0-r0/valgrind-3.17.0/memcheck/tests/linux/stack_changes.c:31:
undefined reference to `getcontext'
|
/ala-lpggp31/yyu1/oe-core/build/tmp-musl/work/core2-64-oe-linux-musl/valgrind/3.17.0-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux-musl/../../libexec/x86_64-oe-linux-musl/gcc/x8:
|
/usr/src/debug/valgrind/3.17.0-r0/valgrind-3.17.0/memcheck/tests/linux/stack_changes.c:60:
undefined reference to `makecontext'
|
/ala-lpggp31/yyu1/oe-core/build/tmp-musl/work/core2-64-oe-linux-musl/valgrind/3.17.0-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux-musl/../../libexec/x86_64-oe-linux-musl/gcc/x8'
|
/ala-lpggp31/yyu1/oe-core/build/tmp-musl/work/core2-64-oe-linux-musl/valgrind/3.17.0-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux-musl/../../libexec/x86_64-oe-linux-musl/gcc/x8'
| collect2: error: ld returned 1 exit status

```

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #8 from 80p3fy7...@cloud-mail.top ---
(In reply to Andrey from comment #7)
> It's important how these accented keys ("é" "è" "ç" "à") are generated on
> keyboard.
> - If they are accessible as is, without any additional modifiers (on French
> layout) - that is definitely bug 375518.
> - If they are accessible via Shift or some other modifiers (just to type
> them, without shortcuts) - that might be combination of bug 375518 and some
> other issue.
> - If they are typing normally via dead keys - I'm not sure if that shortcuts
> was ever implemented at all.

"é" "è" "ç" and "à" can all be typed without any additional modifiers with
French layout (AZERTY) 

"É" "È" "Ç" and "À" only require caps lock turned on, as you would expect. No
additional modifiers either.

You can try yourself with a QWERTY keyboard and French layout using the numbers
row:

Press "2" for "é" and "É"
Press "7" for "è" and "È"
Press "9" for "ç" and "Ç"
Press "0" for "à" and "À"

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

[kwin] [Bug 422342] Corrupt Aurorae window decorations in wayland with scaling

2021-03-26 Thread Lucas Laprad

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

--- Comment #7 from Lucas Laprad  ---
I am still experiencing this issue on 3/26/21 with any scaling change.

KDE 5.21.3
KDE Frameworks: 5.80
QT: 5.15
Kernel: 5.11.6-1
Wayland
Intel / Nvidia GPU (MSI P65)

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

[ksysguard] [Bug 434989] Memory and Swap History plot does not consider Shared Memory

2021-03-26 Thread Gustavo

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

--- Comment #2 from Gustavo  ---
Created attachment 137094
  --> https://bugs.kde.org/attachment.cgi?id=137094=edit
Script that creates an array and copies it into shared memory

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

[ksysguard] [Bug 434989] Memory and Swap History plot does not consider Shared Memory

2021-03-26 Thread Gustavo

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

--- Comment #1 from Gustavo  ---
Created attachment 137093
  --> https://bugs.kde.org/attachment.cgi?id=137093=edit
My custom Application vs Allocated Memory plot

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

[plasma-systemmonitor] [Bug 434877] High CPU usage

2021-03-26 Thread Riccardo Robecchi

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

--- Comment #11 from Riccardo Robecchi  ---
The thing is this behaviour is not there on another desktop I own (to which I
have no access right now, due to it being in another country). There, KSysGuard
used ~3% CPU as it should.
Let's forget that for a moment though. I understand the complexity that lies
below showing these stats, but it seems to me like something very, very
inefficient happens in KSysGuard and System Monitor given that GNOME System
Monitor, which is equivalent in all respects to the KDE programs, uses ~5% CPU.
I don't know what it does differently, but it manages to offer the same basic
functionality while using a ton less resources.
I don't think that using >30% CPU to show you how much CPU is being used is in
any way acceptable or recommended (as Nate puts it, "a system monitoring app
should be as lightweight as possible to avoid mutating what it's measuring"). I
will stop using System Monitor and KSysGuard until progress is made on this
front as they are the main reason why my notebook's fans spin up and keep on
spinning as long as they stay open.

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

[ksysguard] [Bug 434989] New: Memory and Swap History plot does not consider Shared Memory

2021-03-26 Thread Gustavo

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

Bug ID: 434989
   Summary: Memory and Swap History plot does not consider Shared
Memory
   Product: ksysguard
   Version: 5.18.4
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: sanchezt...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 137092
  --> https://bugs.kde.org/attachment.cgi?id=137092=edit
Memory and Swap History plot (which is bugged)

SUMMARY
"Memory" line in the "Memory and Swap History" plot in the "System Load" tab
does not show actual allocated memory but only Application memory. Which I
think is misleading to someone who wants to know how much memory is available.

I've created a separate tab with both Application Memory and Allocated Memory
for comparison

STEPS TO REPRODUCE
1. run shared-memory-test.py (needs pytorch)
2. download it into a directory and "cd" into it
3. run "python3 -m venv venv; source venv/bin/activate, pip install
torch==1.8.1+cpu -f https://download.pytorch.org/whl/torch_stable.html;
4. run "python shared-memory-test.py"

OBSERVED RESULT
Check the Memory and Swap History  Plot, it will show it decreases when
actually the process moved a huge array into shared memory.
I'm attaching screenshots of what I see, both in my custom plot and the default
one.

EXPECTED RESULT
The Memory and Swap History plot should not show any decrease in ram usage at
all, since it's misleading.


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-70-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all

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

--- Comment #7 from Andrey  ---
It's important how these accented keys ("é" "è" "ç" "à") are generated on
keyboard.
- If they are accessible as is, without any additional modifiers (on French
layout) - that is definitely bug 375518.
- If they are accessible via Shift or some other modifiers (just to type them,
without shortcuts) - that might be combination of bug 375518 and some other
issue.
- If they are typing normally via dead keys - I'm not sure if that shortcuts
was ever implemented at all.

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

[krita] [Bug 421136] Build failure on arm archs

2021-03-26 Thread Constantine-D. Kardaris

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

Constantine-D. Kardaris  changed:

   What|Removed |Added

 CC||ckarda...@gmail.com

--- Comment #20 from Constantine-D. Kardaris  ---
Hello, i got hit by the relevant change that came with krita 4.4.3 forcing
opengles based on cpu architecture while Qt is built with opengl.
On Gentoo aarch64, Qt built with gles2-only DISABLED, when canvas is loading
krita crashes with:

ASSERT (krita): "ASSERT failure in KisOpenGLImageTextures::updateTextureFormat:
"Unexpected KisOpenGL::hasOpenGLES returned false" (false)" in file
/var/tmp/portage/media-gfx/krita-4.4.3/work/krita-4.4.3/libs/ui/opengl/kis_opengl_image_textures.cpp,
line 557
Aborted

Reverting 2d92ee5b01a0069cc33debdcb3c29dc817c2d6f3 brings everything back to
normal.

I guess im going to switch Qt+Krita to opengles anyway but, on par with Alvin
Wong's comment, just matching cpu architecture is not enough.

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

[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all