[kwin] [Bug 432326] GTK apps maximized on start are too high - bottom of the window is not seen

2021-02-01 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=432326

--- Comment #4 from Andrey  ---
(In reply to Nate Graham from comment #2)
> Also seen on X11 (Bug 432096), so maybe this isn't a Wayland-specific issue?
Hm, the symptoms for the Qt-based/X11 app look the same, but still this one
probably Wayland-specific bug because I can't reproduce it for FF on XWayland
(but didn't try it on X11).

Someone with more specific experience should review, though.

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

[valgrind] [Bug 431157] PPC_FEATURE2_SCV needs to be masked in AT_HWCAP2

2021-02-01 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=431157

Carl Love  changed:

   What|Removed |Added

 Attachment #134552|0   |1
is obsolete||

--- Comment #14 from Carl Love  ---
Created attachment 135358
  --> https://bugs.kde.org/attachment.cgi?id=135358&action=edit
patch to add support for the scv instruction

I have updated the scv support patch.  The new patch adds the needed support to
parse the scv instruction in guest_ppc_toIR.c.  It adds the needed support to
call the sc or the scv instruction in the power assembly system call wrapper
function, fixes up the setting of the at_restart and in_complete_to_committed
variables and finally adds a test case for the sc and scv instructions.  

The patch has been tested on Power 8 BE, Power 8 LE, Power 9 (ISA 3.0) with
kernel support for the scv instruction, Power 9 (ISA 3.0) without kernel
support for the scv instruction and on a prototype ISA 3.1 hardware.  The patch
works without adding new regression errors.

Julian can you please review the patch.  Thanks.

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

[kwin] [Bug 432326] GTK apps maximized on start are too high - bottom of the window is not seen

2021-02-01 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=432326

--- Comment #5 from Andrey  ---
Workaround: press Restore button of window's header, and then maximize it
again.

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

[kwin] [Bug 432096] Scribus maximized window bigger than screen

2021-02-01 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=432096

Andrey  changed:

   What|Removed |Added

 CC||butir...@gmail.com

--- Comment #12 from Andrey  ---
Is workaround with restore/maximize works for this case?
https://bugs.kde.org/show_bug.cgi?id=432326#c5

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

[ksplash] [Bug 432321] ksplashqml PID: 2046 Signal: Segmentation fault

2021-02-01 Thread Fedora User
https://bugs.kde.org/show_bug.cgi?id=432321

--- Comment #2 from Fedora User  ---
This is my first bug submission so bear with me.
How do I collect the back trace?

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

[krita] [Bug 432403] New: I cannot draw with my huion pen anymore, i think i press something by accident and now i can only draw with my mouse, also my pen its now moving slow on krita.

2021-02-01 Thread Ethan Jaramillo
https://bugs.kde.org/show_bug.cgi?id=432403

Bug ID: 432403
   Summary: I cannot draw with my huion pen anymore, i think i
press something by accident and now i can only draw
with my mouse, also my pen its now moving slow on
krita.
   Product: krita
   Version: 4.4.2
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: ethanjaramill...@gmail.com
  Target Milestone: ---

SUMMARY
I cannot draw with my huion pen anymore, i think i press something by accident
and now i can only draw with my mouse, also my pen its now moving slow on
krita.

STEPS TO REPRODUCE
1. I just open krita, create a new document
2. Try to draw with my pen
3. Nothing happens unless i use my mouse

OBSERVED RESULT
It doesn´t let me draw with my funcional pen and it only lets me draw with my
mouse, i erase all my settings, erase the app and downloaded again and the
problem persists. 

EXPECTED RESULT
I should be able to draw with my pen like i used to.

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

ADDITIONAL INFORMATION
Don´t send me to the forum just help me with a solution.
The forum doesn´t have an answer.
I just downloaded krita today and i was exploring it. 
My pen works just fine in other apps.

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

[systemsettings] [Bug 427444] System Settings crashes in QQmlData::wasDeleted() when navigating to a different KCM while on the Screen Locker KCM's Appearance page

2021-02-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=427444

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||5.79
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kirigami/-/commit/b4
   ||a6c562cde4e064494e261bc3f64
   ||000cbf628a5
 Resolution|--- |FIXED

--- Comment #12 from Nate Graham  ---
Oh right, it's fixed by that, yeah.

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

[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta

2021-02-01 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=432367

--- Comment #4 from Andrey  ---
Leonard, this is probably because the shortcuts of these layouts do not match.
I wonder if you had similar problems with the same layouts but in different
order?

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

[krita] [Bug 432403] I cannot draw with my huion pen anymore, i think i press something by accident and now i can only draw with my mouse, also my pen its now moving slow on krita.

2021-02-01 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=432403

Tiar  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 CC||tamtamy.tym...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #1 from Tiar  ---
Hi, please do go to krita-artists.org with this type of an issue. Also where
did you get the link to here? In Krita -> Help? Or some other place?

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

[krita] [Bug 432403] I cannot draw with my huion pen anymore, i think i press something by accident and now i can only draw with my mouse, also my pen its now moving slow on krita.

2021-02-01 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=432403

--- Comment #2 from Tiar  ---
The reason we close issues like that and send them to the forum is because we
cannot help everyone with this issue: there are 9 paid members of Krita team
(all could better spend their time actually coding) and roughly 3 millions of
Krita users. On the forum there are volunteers and experienced Krita users that
can help you. And in any case, you should start from *searching* the forum for
similar issues. https://reddit.com/r/krita is a good place to look for issues
like that, too (although right now there are too many people asking for help
and too little people helping, too, so don't expect a quick answer there,
either. But reddit have seen all possible issues with tablet you can get -
yours, too - and has solutions for them).

In any case, we are not required to give anyone support, due to the license of
Krita that you agreed upon when installing. And this is strictly
development-oriented website, which we cannot use for user support.

And the reason this is a user support issue is because this kind of issue is
usually solved by configuring either Krita or the system. You can check here
for clues:
https://docs.krita.org/en/contributors_manual/user_support.html#quick-solutions 

I'm sorry that this is not the answer you wanted, but I cannot help you here.

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

[kmymoney] [Bug 432400] In the "Accounts" Section, there is no sub-list for Investments accounts

2021-02-01 Thread Jan
https://bugs.kde.org/show_bug.cgi?id=432400

--- Comment #2 from Jan  ---
Both single-click+Enter and double-click open the ledger of the account.  Not a
workaround.

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

[kmymoney] [Bug 432400] In the "Accounts" Section, there is no sub-list for Investments accounts

2021-02-01 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=432400

--- Comment #3 from Jack  ---
Try a select and then either right arrow or plus sign "+".

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

[Discover] [Bug 412632] discover crash on start

2021-02-01 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=412632

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #9 from Aleix Pol  ---
I can't find any crash since Plasma 5.16. Please reopen if you can reproduce in
a maintained version of the software.

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

[Discover] [Bug 426339] Discover: add option to hide deps (only show explicitly installed by user packages) in "installed" tab

2021-02-01 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=426339

--- Comment #1 from Aleix Pol  ---
You should only have installed applications.

Which items are bothering you?

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

[kmymoney] [Bug 432400] In the "Accounts" Section, there is no sub-list for Investments accounts

2021-02-01 Thread Jan
https://bugs.kde.org/show_bug.cgi?id=432400

--- Comment #4 from Jan  ---
I assume "select" means single-click.  Nothing happens when hitting + or right
arrow after selecting an investment account.

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

[plasmashell] [Bug 432404] New: [Feature Request] Add settings for which power/session buttons are displayed

2021-02-01 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=432404

Bug ID: 432404
   Summary: [Feature Request] Add settings for which power/session
buttons are displayed
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: justin.zo...@gmail.com
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Running git master with new kickoff.

I'd like to be able to change the Sleep/Restart/Shut Down buttons to an order
and selection of my choosing.

e.g. Logout Restart Shutdown.

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

[krita] [Bug 432403] I cannot draw with my huion pen anymore, i think i press something by accident and now i can only draw with my mouse, also my pen its now moving slow on krita.

2021-02-01 Thread Ethan Jaramillo
https://bugs.kde.org/show_bug.cgi?id=432403

--- Comment #3 from Ethan Jaramillo  ---
   Ok thanks I hope I can get a solution otherwise I should start looking
   for another app like krita.

    Mensaje original 
   De: Tiar 
   Fecha: lun., 1 feb. 2021 19:44
   Para: ethanjaramill...@gmail.com
   Asunto: [krita] [Bug 432403] I cannot draw with my huion pen anymore,
   i
   think i press something by accident and now i can only draw with my
   mouse,
   also my pen its now moving slow on krita.

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

 --- Comment #2 from Tiar  ---
 The reason we close issues like that and send them to the forum is
 because we
 cannot help everyone with this issue: there are 9 paid members of
 Krita team
 (all could better spend their time actually coding) and roughly 3
 millions of
 Krita users. On the forum there are volunteers and experienced
 Krita users that
 can help you. And in any case, you should start from *searching*
 the forum for
 similar issues. https://reddit.com/r/krita is a good place to look
 for issues
 like that, too (although right now there are too many people
 asking for help
 and too little people helping, too, so don't expect a quick answer
 there,
 either. But reddit have seen all possible issues with tablet you
 can get -
 yours, too - and has solutions for them).

 In any case, we are not required to give anyone support, due to
 the license of
 Krita that you agreed upon when installing. And this is strictly
 development-oriented website, which we cannot use for user
 support.

 And the reason this is a user support issue is because this kind
 of issue is
 usually solved by configuring either Krita or the system. You can
 check here
 for clues:

https://docs.krita.org/en/contributors_manual/user_support.html#quick-solutions

 I'm sorry that this is not the answer you wanted, but I cannot
 help you here.

 --
 You are receiving this mail because:
 You reported the bug.

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

[krita] [Bug 432287] New RGBA brushes causing black pixels

2021-02-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=432287

--- Comment #5 from levi21sanc...@gmail.com ---
No, I'm new to digital art in general and never really gave much thought to the
color spacing

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

[krita] [Bug 432334] krita deleted process during save

2021-02-01 Thread Tiar
https://bugs.kde.org/show_bug.cgi?id=432334

Tiar  changed:

   What|Removed |Added

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

--- Comment #1 from Tiar  ---
Hi, can you please attach Help -> Show Krita log for bug reports? And please
tell me how your file was called.

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

[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys

2021-02-01 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=418352

--- Comment #16 from Dominik Haumann  ---
@Allan: you likely already tested with Qt 5.15.1 or so back then, right?

I'd assume this issue is fixed then.

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

[kate] [Bug 432325] kate scrollbar doesn't take into account line length

2021-02-01 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=432325

--- Comment #1 from Dominik Haumann  ---
Unfortunately that is by design.

If we want to support that, then Kate would have to layout all lines in the
document to know exactly how many wrapped lines are in the view.

Layouting all lines can be really slow since Kate supports right-to-left
languages as well. We already have issues about Kate being slow for very long
lines. Adding support for this behavior would make it worse.

The only possible workaround would be that Kate knows it has only ascii content
(special case), since then with a fixed font we'd know exactly how long a line
would really be.

Currently, we always decided to not add such a special case... So we have to
live with it.

Scrolling with the mouse wheel should work, though.

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

[kate] [Bug 432298] kate will hold the device busy while the file had closed before on this device

2021-02-01 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=432298

--- Comment #1 from Dominik Haumann  ---
What plugins do you use? Projects plugin? LSP plugin? Does it work when you
disable plugins and restart Kate?

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

[kwin] [Bug 400987] XWayland application focus extremely inconsistent

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=400987

--- Comment #61 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 431729] Visual issues after hibernation with multi monitor setup: Panel spans over to 2nd monitor and wallpapers change

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=431729

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

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

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

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

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

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

[Spectacle] [Bug 431734] Crash while making rectangular screenshot with spectacle

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=431734

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

[dolphin] [Bug 406028] Folder right-click menu is missing items in the folder panel

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=406028

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #17 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 406647] Alternative Navigation Trough Windows won't work past first instance

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=406647

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #13 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 412514] XWayland apps input issue with fractional scaling

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412514

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[kwin] [Bug 412249] Random freezing with Radeon VII

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412249

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kwin] [Bug 412642] kwin closed unexpectedly

2021-02-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=412642

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[dolphin] [Bug 432405] New: Photo Meta Data such as "Data Photographed" Not Showing Up

2021-02-01 Thread Al
https://bugs.kde.org/show_bug.cgi?id=432405

Bug ID: 432405
   Summary: Photo Meta Data such as "Data Photographed" Not
Showing Up
   Product: dolphin
   Version: 19.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: hapog94...@mado34.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

When I choose "date photographed" in the details view for non-corrupt JPEG (and
possibly other type) photos, this column is blank even though there is valid
metadata embedded in these photos. I've read other posts on this for hours, and
nothing helps, including changing the baloo setting for indexing files. This
behavior was also observed in version 20, however I can't use that from
Discover on my setup for some reason and it has other issues. 

STEPS TO REPRODUCE
1. Navigate to a folder of photos, jpeg for example
2. Change view to detail view mode
3. Enable column "date photographed". 

OBSERVED RESULT

All are empty, even with valid metadata. 


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION

I tried reinstalling baloo, to no effect. The running of 

balooctl status

yields a running baloo instance as desired. Running

balooshow image.jpg

shows all of the desired metadata, which is peculiar and probably very
significant. 





Let me know how I can help.

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

[dolphin] [Bug 432406] New: Cannot open file with non-ascii name when LC_ALL is not set

2021-02-01 Thread Tusooa Zhu
https://bugs.kde.org/show_bug.cgi?id=432406

Bug ID: 432406
   Summary: Cannot open file with non-ascii name when LC_ALL is
not set
   Product: dolphin
   Version: 20.08.3
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: tus...@vista.aero
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

Trying to open a file whose absolute path contains non-ascii will prompt that
the file does not exist. Setting LC_ALL to a utf-8 locale seems to be a
workaround.

STEPS TO REPRODUCE
1. `touch 测试`
2. `locale`
3. Try to open that file in dolphin
4. (unset LC_CTYPE;export LANG=en_CA.UTF-8;dolphin) and try again
5. (unset LC_CTYPE;export LC_ALL=en_CA.UTF-8;dolphin) and try again


OBSERVED RESULT

2. 
] locale
LANG=en_CA.UTF-8
LC_CTYPE=zh_CN.UTF-8
LC_NUMERIC="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_PAPER="en_CA.UTF-8"
LC_NAME="en_CA.UTF-8"
LC_ADDRESS="en_CA.UTF-8"
LC_TELEPHONE="en_CA.UTF-8"
LC_MEASUREMENT="en_CA.UTF-8"
LC_IDENTIFICATION="en_CA.UTF-8"
LC_ALL=

3,4: Pops up a dialog with "Unable to run the command specified. The file or
folder /home/tusooa/测试 does not exist."

5: Pops up a dialog to choose an application to open that file. After choosing
one (/usr/bin/emacsclient), the file is successfully opened.

EXPECTED RESULT

3,4 should behave like 5.

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

ADDITIONAL INFORMATION

This only applies to opening files, not directories.

The file can be trashed properly.

It seems to matter only when an external program is needed to open the file.

Konqueror seems to also suffer from this bug. However, the LC_ALL trick will do
nothing to it. Also it does not happen when you are opening an html file in
Konqueror.

I am not sure whether this is a Dolphin and Konqueror bug, or this is a kio
bug. If my judgement is wrong, please move it to the right product.

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

[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation

2021-02-01 Thread Szczepan Hołyszewski
https://bugs.kde.org/show_bug.cgi?id=406725

Szczepan Hołyszewski  changed:

   What|Removed |Added

 CC||rula...@wp.pl

--- Comment #7 from Szczepan Hołyszewski  ---
"Remember properties for each folder" remembers ALL properties for each folder:
the view type (list / compact list / tree), icon size, etc. This is
undesirable. I want to be able to use common properties for all folders, EXCEPT
for thumbnailer settings which I DO want to be able to override per directory.

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

[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation

2021-02-01 Thread Szczepan Hołyszewski
https://bugs.kde.org/show_bug.cgi?id=406725

--- Comment #8 from Szczepan Hołyszewski  ---
Also what is REALLY desired here is the ability to completely and consistently
DENY the thumbnailing subsystem ACCESS to certain files. This isn't what "Show
thumbnails" checkbox does: it prevents thumbnails from being shown in the
dolphin directory view, but when you hover on a file, Dolphin will still
generate its thumbnail and show it in the properties pane. What is desired is
the ability to **prevent the thumbnail file under the .cache directory from
ever possibly being created**, and **this** should work per-directory.

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

[konqueror] [Bug 432407] New: Crash on exit

2021-02-01 Thread Wolfgang Reh
https://bugs.kde.org/show_bug.cgi?id=432407

Bug ID: 432407
   Summary: Crash on exit
   Product: konqueror
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: wolfgang@aon.at
  Target Milestone: ---

Application: konqueror (20.12.1)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.10-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
 Closed the Konquerer after looking at a Website. Did not do much on the
Website, just looking for a short time on it.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault

[KCrash Handler]
#4  0x7fa1635806ef in q_createNativeChildrenAndSetParent(QWidget const*) ()
at /lib64/libQt5Widgets.so.5
#5  0x7fa1635807c0 in q_createNativeChildrenAndSetParent(QWidget const*) ()
at /lib64/libQt5Widgets.so.5
#6  0x7fa1635807c0 in q_createNativeChildrenAndSetParent(QWidget const*) ()
at /lib64/libQt5Widgets.so.5
#7  0x7fa1635807c0 in q_createNativeChildrenAndSetParent(QWidget const*) ()
at /lib64/libQt5Widgets.so.5
#8  0x7fa1635807c0 in q_createNativeChildrenAndSetParent(QWidget const*) ()
at /lib64/libQt5Widgets.so.5
#9  0x7fa16357de58 in QWidgetPrivate::create() () at
/lib64/libQt5Widgets.so.5
#10 0x7fa16357e29e in QWidget::create(unsigned long long, bool, bool) () at
/lib64/libQt5Widgets.so.5
#11 0x7fa16358c7eb in QWidget::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#12 0x7fa163f47dbd in KXmlGuiWindow::event(QEvent*) () at
/lib64/libKF5XmlGui.so.5
#13 0x7fa16354aec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#14 0x7fa1628cbbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#15 0x7fa1635a76a1 in QWidgetWindow::event(QEvent*) () at
/lib64/libQt5Widgets.so.5
#16 0x7fa16354aec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#17 0x7fa1628cbbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#18 0x7fa162d11105 in QWindowPrivate::create(bool, unsigned long long) ()
at /lib64/libQt5Gui.so.5
#19 0x7fa162d11388 in QWindow::winId() const () at /lib64/libQt5Gui.so.5
#20 0x7fa16426976b in KJobWindows::setWindow(KJob*, QWindow*) () at
/lib64/libKF5JobWidgets.so.5
#21 0x7fa164269942 in KJobWidgets::setWindow(KJob*, QWidget*) () at
/lib64/libKF5JobWidgets.so.5
#22 0x7fa1642ebe18 in
KIO::AccessManager::createRequest(QNetworkAccessManager::Operation,
QNetworkRequest const&, QIODevice*) () at /lib64/libKF5KIOWidgets.so.5
#23 0x7fa0c4177231 in
KDEPrivate::MyNetworkAccessManager::createRequest(QNetworkAccessManager::Operation,
QNetworkRequest const&, QIODevice*) () at
/usr/lib64/qt5/plugins/kf5/parts/kwebkitpart.so
#24 0x7fa16320d159 in QNetworkAccessManager::get(QNetworkRequest const&) ()
at /lib64/libQt5Network.so.5
#25 0x7fa036b1bb92 in
WebCore::QNetworkReplyHandler::sendNetworkRequest(QNetworkAccessManager*,
WebCore::ResourceRequest const&) () at /lib64/libQt5WebKit.so.5
#26 0x7fa036b1c956 in WebCore::QNetworkReplyHandler::start() () at
/lib64/libQt5WebKit.so.5
#27 0x7fa036b188f7 in WebCore::QNetworkReplyHandlerCallQueue::flush()
[clone .part.0] () at /lib64/libQt5WebKit.so.5
#28 0x7fa036b1e96f in WebCore::ResourceHandle::start() () at
/lib64/libQt5WebKit.so.5
#29 0x7fa036a52c00 in
WebCore::ResourceHandle::create(WebCore::NetworkingContext*,
WebCore::ResourceRequest const&, WebCore::ResourceHandleClient*, bool, bool) ()
at /lib64/libQt5WebKit.so.5
#30 0x7fa0358a327b in
WebResourceLoadScheduler::createPingHandle(WebCore::NetworkingContext*,
WebCore::ResourceRequest&, bool) () at /lib64/libQt5WebKit.so.5
#31 0x7fa0368bf826 in WebCore::PingLoader::loadImage(WebCore::Frame&,
WebCore::URL const&) () at /lib64/libQt5WebKit.so.5
#32 0x7fa0368f5e4b in
WebCore::CachedResourceLoader::requestImage(WebCore::CachedResourceRequest&) ()
at /lib64/libQt5WebKit.so.5
#33 0x7fa0368b5f52 in WebCore::ImageLoader::updateFromElement() () at
/lib64/libQt5WebKit.so.5
#34 0x7fa0364933a9 in WebCore::HTMLImageElement::selectImageSource() () at
/lib64/libQt5WebKit.so.5
#35 0x7fa0365b7853 in
WebCore::Element::attributeChanged(WebCore::QualifiedName const&,
WTF::AtomicString const&, WTF::AtomicString const&,
WebCore::Element::AttributeModificationReason) () at /lib64/libQt5WebKit.so.5
#36 0x7fa0365e1ced in
WebCore::Element::didAddAttribute(WebCore::QualifiedName const&,
WTF::AtomicString const&) () at /lib64/libQt5WebKit.so.5
#37 0x7fa036cc0be3 in WebCore::setJSHTMLImageEl

[kontact] [Bug 432371] KMail: CRTL-Enter does not work if cursor in address-field

2021-02-01 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=432371

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 CC||mon...@kde.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Laurent Montel  ---
nope it doesn't work before as I don't want to send by error and email as it's
easy to press CTRL+ENTER.
So it's a normal feature.
Regards

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

[digikam] [Bug 432048] XMP People/Face tags with no associated regions are ignored [patch]

2021-02-01 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=432048

Maik Qualmann  changed:

   What|Removed |Added

 Attachment #135357|0   |1
is obsolete||

--- Comment #23 from Maik Qualmann  ---
Created attachment 135359
  --> https://bugs.kde.org/attachment.cgi?id=135359&action=edit
writeMSPhotoRegion2.patch

Patch #2

Maik

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

[kmymoney] [Bug 432399] Quantities missing in Investments Section

2021-02-01 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=432399

Thomas Baumgart  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Baumgart  ---
Did you try to click on the header with the right mouse button? There you can
enable/disable the display of symbol, value, quantity and price.

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

[systemsettings] [Bug 431197] Sub-pixel anti-aliasing is not being applied

2021-02-01 Thread nyanpasu64
https://bugs.kde.org/show_bug.cgi?id=431197

nyanpasu64  changed:

   What|Removed |Added

 CC||nyanpas...@tuta.io

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

[kate] [Bug 418352] Kate crashes when moving selections of text with Crtl+Shift+Arrow keys

2021-02-01 Thread Allan Sandfeld
https://bugs.kde.org/show_bug.cgi?id=418352

--- Comment #17 from Allan Sandfeld  ---
(In reply to Dominik Haumann from comment #16)
> @Allan: you likely already tested with Qt 5.15.1 or so back then, right?
> 
> I'd assume this issue is fixed then.

In October I probably tested with 5.15.2, but yes, couldn't reproduce.

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

[ksysguard] [Bug 432220] Scale should not be cumulative

2021-02-01 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=432220

David Redondo  changed:

   What|Removed |Added

 CC||k...@david-redondo.de

--- Comment #3 from David Redondo  ---
So what you are seeing is technically correct but that each of the memory
sensors has a theoretic maximum of the full amount of RAM in your system. In
reality however the sum of all sensors would never exceed the amount RAM in
your system.

For now you probably want to set the limit manually.

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

[digikam] [Bug 432048] XMP People/Face tags with no associated regions are ignored by Digikam (Person Shown, MWG Face name, MS People Tag)

2021-02-01 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=432048

Maik Qualmann  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #20 from Maik Qualmann  ---
I see a breach of the standard in writing people names without facial regions.
If you show me an official document that describes this, we will implement it.
Just because Microsoft does it that way, we won't implement it. Even if digiKam
attaches great importance to sharing metadata with other programs, we should
adhere to standards. DigiKam puts all options in your hands to correct your
images (YOLO face recognition for the smallest faces, etc.) and to write back
standard-compliant metadata. I plan to support the new People Shown tag in
digiKam-7.3.0. That should solve your problem with Windows Photo Gallery.

Maik

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

[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423864

--- Comment #5 from BingMyBong  ---
(In reply to David Edmundson from comment #3)
> Fixed for 5.20

Hi,  i'm using 5.20.5 and its still not working.  i've tried removing the
widget and reinstalling but its the same result, Logout = shutdown.

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

[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=423864

--- Comment #6 from BingMyBong  ---
(In reply to BingMyBong from comment #5)
> (In reply to David Edmundson from comment #3)
> > Fixed for 5.20
> 
> Hi,  i'm using 5.20.5 and its still not working.  i've tried removing the
> widget and reinstalling but its the same result, Logout = shutdown.

SORRY... IGNORE THIS - ADDED IT TO THE WRONG BUG

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

[plasmashell] [Bug 363318] Lock / Logout Widget

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=363318

BingMyBong  changed:

   What|Removed |Added

 CC||bingmyb...@btinternet.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from BingMyBong  ---


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

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

[plasmashell] [Bug 424426] Logout defaults to shutting down once pressed

2021-02-01 Thread BingMyBong
https://bugs.kde.org/show_bug.cgi?id=424426

BingMyBong  changed:

   What|Removed |Added

 CC||richard.l...@gmail.com

--- Comment #16 from BingMyBong  ---
*** Bug 363318 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 432370] New: Crash when deleting currently used custom cursors

2021-02-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=432370

Bug ID: 432370
   Summary: Crash when deleting currently used custom cursors
   Product: systemsettings
   Version: 5.20.5
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: seplexf...@tutanota.com
  Target Milestone: ---

Application: systemsettings5 (5.20.5)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.9-1-default x86_64
Windowing system: X11
Distribution: openSUSE Tumbleweed

-- Information about the crash:
- What I was doing when the application crashed:
I have installed custom cursors.
Applied the installed cursors.
Restarted the settings app.
And deleted the cursors. (not from the store,  but from the cursors menu in
settings)

- Custom settings of the application:
I have a bunch of themes, maybe it's my fault

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault

[KCrash Handler]
#4  QString::QString (other=..., this=0x7ffe30a7f788) at
/usr/include/qt5/QtCore/qstring.h:1093
#5  CursorTheme::name (this=0x0) at
/usr/src/debug/plasma5-workspace-5.20.5-3.1.x86_64/kcms/cursortheme/xcursor/cursortheme.h:65
#6  operator() (roles=..., end=..., start=..., __closure=0x55a747152660) at
/usr/src/debug/plasma5-workspace-5.20.5-3.1.x86_64/kcms/cursortheme/kcmcursortheme.cpp:103
#7  QtPrivate::FunctorCall,
QtPrivate::List&>,
void, CursorThemeConfig::CursorThemeConfig(QObject*, const
QVariantList&)::&)> >::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#8  QtPrivate::Functor&)>, 3>::call const&>, void> (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#9 
QtPrivate::QFunctorSlotObject&)>, 3, QtPrivate::List&>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x55a747152650, r=, a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#10 0x7f9775d818c6 in QtPrivate::QSlotObjectBase::call (a=0x7ffe30a7f900,
r=0x55a74874abd0, this=0x55a747152650) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate (sender=0x55a74297c180, signal_index=3,
argv=argv@entry=0x7ffe30a7f900) at kernel/qobject.cpp:3886
#12 0x7f9775d7ac20 in QMetaObject::activate
(sender=sender@entry=0x55a74297c180, m=m@entry=0x7f977602df40
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe30a7f900)
at kernel/qobject.cpp:3946
#13 0x7f9775ce5ec5 in QAbstractItemModel::dataChanged
(this=this@entry=0x55a74297c180, _t1=..., _t2=..., _t3=...) at
.moc/moc_qabstractitemmodel.cpp:557
#14 0x7f9743def18e in CursorThemeModel::setData (this=0x55a74297c180,
index=..., value=..., role=) at
/usr/src/debug/plasma5-workspace-5.20.5-3.1.x86_64/kcms/cursortheme/xcursor/thememodel.cpp:152
#15 0x7f9775d16579 in QSortFilterProxyModel::setData
(this=this@entry=0x55a748674cb0, index=..., value=...,
role=role@entry=614718202) at itemmodels/qsortfilterproxymodel.cpp:2262
#16 0x7f97735c80b5 in QQmlDMAbstractItemModelData::setValue (value=...,
role=614718202, this=0x55a747ed96d0) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/src/qmlmodels/qqmladaptormodel.cpp:421
#17 QQmlDMCachedModelData::metaCall (this=0x55a747ed96d0, call=,
id=, arguments=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/src/qmlmodels/qqmladaptormodel.cpp:298
#18 0x7f9774d21de0 in QQmlPropertyData::writeProperty (flags=...,
value=0x7ffe30a7fc00, target=0x55a747ed96d0, this=0x55a747821b38) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:285
#19 QQmlPropertyPrivate::write (object=object@entry=0x55a747ed96d0,
property=..., value=..., context=, flags=..., flags@entry=...)
at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/src/qml/qml/qqmlproperty.cpp:1305
#20 0x7f9774c4f11b in QV4::QObjectWrapper::setProperty
(engine=0x55a747c60500, object=0x55a747ed96d0, property=0x55a747821b38,
value=...) at /usr/include/qt5/QtCore/qflags.h:120
#21 0x7f9774c4fb17 in QV4::QObjectWrapper::setQmlProperty (value=...,
revisionMode=QV4::QObjectWrapper::IgnoreRevision, name=,
object=0x55a747ed96d0, qmlContext=, engine=0x55a747c60500) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:435
#22 QV4::QObjectWrapper::setQmlProperty (engine=0x55a747c60500,
qmlContext=, object=0x55a747ed96d0, name=,
revisionMode=QV4::QObjectWrapper::IgnoreRevision, value=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:418
#23 0x7f9774c4fcb5 in QV4::QObjectWrapper::virtualPut (m=0x7f97591d1640,
id=..., value=..., receiver=0x7f97591d1640) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2-2.1.x86_64/s

[krita] [Bug 432362] Crash when creating a new document

2021-02-01 Thread Sharaf
https://bugs.kde.org/show_bug.cgi?id=432362

Sharaf  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/grap
   ||hics/krita/commit/300d55c0a
   ||4c9b5bd0d4cf6d5073cd20d6ac7
   ||b740

--- Comment #1 from Sharaf  ---
Git commit 300d55c0a4c9b5bd0d4cf6d5073cd20d6ac7b740 by Sharaf Zaman.
Committed on 01/02/2021 at 08:59.
Pushed by szaman into branch 'master'.

Android: url can be empty

M  +11   -11  
3rdparty/ext_qt/0049-Android-Workarounds-to-explicitly-handle-content-URI.patch

https://invent.kde.org/graphics/krita/commit/300d55c0a4c9b5bd0d4cf6d5073cd20d6ac7b740

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

[kontact] [Bug 432371] New: KMail: CRTL-Enter does not work if cursor in address-field

2021-02-01 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=432371

Bug ID: 432371
   Summary: KMail: CRTL-Enter does not work if cursor in
address-field
   Product: kontact
   Version: 5.16.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: axel.br...@gmx.de
  Target Milestone: ---

SUMMARY
the shortcode CRTL-Enter is frequently used as command to send a mail.
This work if the cursor is in the text part of the mail (composer?), but not if
it is in an address field.
Not sure, but I seem to remember that this worked before, so this is a
regression in 5.6.x

Operating System: openSUSE Tumbleweed 20210126
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

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

[gwenview] [Bug 432330] Incorrect rendering of SVG

2021-02-01 Thread Madhav Kanbur
https://bugs.kde.org/show_bug.cgi?id=432330

Madhav Kanbur  changed:

   What|Removed |Added

 CC||abcd...@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #2 from Madhav Kanbur  ---
This appears to be an upstream bug in QT itself. I've filed a bug report here -
https://bugreports.qt.io/browse/QTBUG-90803

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

[krita] [Bug 432287] New RGBA brushes causing black pixels

2021-02-01 Thread Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=432287

--- Comment #4 from Halla Rempt  ---
Okay, then that might still be the reason. Is there a reason why you're working
in 32 bits floating point?

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

[plasmashell] [Bug 432364] [systemd] plasma-ksmserver.service blocks boot if ksplash is disabled

2021-02-01 Thread Usarin Heininga
https://bugs.kde.org/show_bug.cgi?id=432364

--- Comment #4 from Usarin Heininga  ---
Just adding a '&' to the original line doesn't work because systemd doesn't
understand shell commands. Changing the line to ExecStartPost=-/usr/bin/sh
"/usr/lib/qt5/bin/qdbus org.kde.KSplash /KSplash org.kde.KSplash.setStage
ksmserver &" works fine. You will get some extra error messages in the log
though. Since the whole bootup thing might change in the future I would just
use the shell encapsulating with a '&' at the end. The
plasma-ksplash-ready.service can stay like it was, it doesn't stall the boot,
it just creates some error messages.

Regards

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

[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen

2021-02-01 Thread Gurenko Alex
https://bugs.kde.org/show_bug.cgi?id=385882

Gurenko Alex  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 CC||agure...@protonmail.com
   Assignee|h...@kde.org|agure...@protonmail.com
 Status|RESOLVED|REOPENED

--- Comment #14 from Gurenko Alex  ---
Created attachment 135345
  --> https://bugs.kde.org/attachment.cgi?id=135345&action=edit
yakuake-on-wayland-f33

 I still have exactly this problem on Fedora 33 KDE (Plasma 5.20.5) on both my
Desktop (Ryzen + RX 5700XT) and laptop (Intel + Intel UHD).
 The overlap issue is also happening on my Pinebook Pro with Manjaro (on
wayland).

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

[elisa] [Bug 430089] Elisa closes unexpectedly during listening to music

2021-02-01 Thread CF
https://bugs.kde.org/show_bug.cgi?id=430089

--- Comment #6 from CF  ---
Created attachment 135346
  --> https://bugs.kde.org/attachment.cgi?id=135346&action=edit
New crash information added by DrKonqi

elisa (20.12.1) using Qt 5.15.2

- What I was doing when the application crashed:

I just opened elisa and after displaying it crashed. Sometimes it starts and
crash changing track

-- Backtrace (Reduced):
#4  0x7f94e10c8693 in QMapNodeBase::nextNode (this=0x7f94b405bf80) at
tools/qmap.cpp:58
#5  0x7f94e29a665e in FileScanner::scanProperties(QString const&,
DataTypes::TrackDataType&) () from
/usr/lib/x86_64-linux-gnu/elisa/libelisaLib.so.0
#6  0x7f94e29a792a in FileScanner::scanOneFile(QUrl const&, QFileInfo
const&) () from /usr/lib/x86_64-linux-gnu/elisa/libelisaLib.so.0
#7  0x7f94e29a7fcc in FileScanner::scanOneFile(QUrl const&) () from
/usr/lib/x86_64-linux-gnu/elisa/libelisaLib.so.0
[...]
#9  0x7f94e108dfb2 in QThreadPoolThread::run (this=0x55f7a5512270) at
thread/qthreadpool.cpp:100

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

[elisa] [Bug 430089] Elisa closes unexpectedly during listening to music

2021-02-01 Thread CF
https://bugs.kde.org/show_bug.cgi?id=430089

CF  changed:

   What|Removed |Added

 CC||cere...@gmail.com

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

[plasmashell] [Bug 432372] New: QML widgets don't reserve enough space for text with a point font size.

2021-02-01 Thread Usarin Heininga
https://bugs.kde.org/show_bug.cgi?id=432372

Bug ID: 432372
   Summary: QML widgets don't reserve enough space for text with a
point font size.
   Product: plasmashell
   Version: 5.20.90
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: usarinheini...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

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

SUMMARY


STEPS TO REPRODUCE
1. open the font settings page.
2. change the font size to any size with a half, 10.5 or 11.5.

OBSERVED RESULT
All QML based widgets don't reserve enough space for the text.
Apparently the internal algorithm works with a rounded down value to resize the
widgets.

EXPECTED RESULT
All qml based widgets should reserve enough space for the text.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu Hirsute
(available in About System)
KDE Plasma Version: 5.20.90
KDE Frameworks Version: 5.78
Qt Version: 5.15

ADDITIONAL INFORMATION

This is also the case in Ubuntu Focal and Groovy.

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

[digikam] [Bug 432048] XMP People/Face tags with no associated regions are ignored by Digikam (Person Shown, MWG Face name, MS People Tag)

2021-02-01 Thread José Oliver-Didier
https://bugs.kde.org/show_bug.cgi?id=432048

José Oliver-Didier  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #21 from José Oliver-Didier  ---
Excuse my persistence, but the People Tags Schema 1.2 is Microsoft's own
creation you can find the specification here:
https://docs.microsoft.com/en-us/windows/win32/wic/-wic-people-tagging#schema-reference

Per the specification the face area (rectangle they call it) is marked as
optional:
MPReg:Rectangle "optional : Stores the rectangle that identifies the person
within the photo. The rectangle is stored as four comma-delimited decimal
values. The first two values specify the top left coordinate; the final two
specify the height and width of the rectangle. The decimal values must be
normalized to 1."

Again, this is for Microsoft's People Tags only. As the Metadata Working Group
last Specification requires a face region.

Unfortunately, Windows Photo Gallery does not read "People Shown" tag.

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

[Discover] [Bug 432373] New: Discover application crashes when opened

2021-02-01 Thread Alvaro Gonzalez
https://bugs.kde.org/show_bug.cgi?id=432373

Bug ID: 432373
   Summary: Discover application crashes when opened
   Product: Discover
   Version: 5.12.8
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: kort...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.12.8)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 5.4.0-51-generic x86_64
Distribution: Ubuntu 18.04.5 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Trying to opèn Discover, both from the launch menu and from the system tray
notification (updates notified)

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0f46008800 (LWP 17874))]

Thread 13 (Thread 0x7f0efce71700 (LWP 17897)):
#0  0x7ffd0d77099a in clock_gettime ()
#1  0x7f0f415efd36 in __GI___clock_gettime (clock_id=1, tp=0x7f0efce70b20)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f0f41f1c1c1 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f0f41f1a9f9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0f41f1afd5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0f41f1cc3c in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0f3bdcab28 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f0f3bdcb4fb in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f0f3bdcb6dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f0f41f1c8ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f0f41ec190a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f0f41ce023a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f0f41ce517d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f0f3def36db in start_thread (arg=0x7f0efce71700) at
pthread_create.c:463
#14 0x7f0f415e071f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f0efda88700 (LWP 17896)):
#0  0x7f0f3def9fb9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0efda87c40, expected=0, futex_word=0x7f0ef8009a90) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f0f3def9fb9 in __pthread_cond_wait_common (abstime=0x7f0efda87d00,
mutex=0x7f0ef8009a40, cond=0x7f0ef8009a68) at pthread_cond_wait.c:533
#2  0x7f0f3def9fb9 in __pthread_cond_timedwait (cond=0x7f0ef8009a68,
mutex=0x7f0ef8009a40, abstime=0x7f0efda87d00) at pthread_cond_wait.c:667
#3  0x7f0f41ce6468 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0f41ce253d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0f41ce517d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0f3def36db in start_thread (arg=0x7f0efda88700) at
pthread_create.c:463
#7  0x7f0f415e071f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f0efe289700 (LWP 17890)):
#0  0x7f0f3def9fb9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0efe288c40, expected=0, futex_word=0x7f0ef8006fc0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f0f3def9fb9 in __pthread_cond_wait_common (abstime=0x7f0efe288d00,
mutex=0x7f0ef8006f70, cond=0x7f0ef8006f98) at pthread_cond_wait.c:533
#2  0x7f0f3def9fb9 in __pthread_cond_timedwait (cond=0x7f0ef8006f98,
mutex=0x7f0ef8006f70, abstime=0x7f0efe288d00) at pthread_cond_wait.c:667
#3  0x7f0f41ce6468 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f0f41ce253d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f0f41ce517d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f0f3def36db in start_thread (arg=0x7f0efe289700) at
pthread_create.c:463
#7  0x7f0f415e071f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f0eff0a6700 (LWP 17888)):
#0  0x7f0f3def9fb9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f0eff0a5c40, expected=0, futex_word=0x7f0ef80042f0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f0f3def9fb9 in __pthread_cond_wait_common (abstime=0x7f0eff0a5d00,
mutex=0x7f0ef80042a0, cond=0x7f0ef80042c8) at pthread_cond_wait.c:533
#2  0x7f0f3def9fb9 in __pthread_cond_timedwait (cond=0x7f0ef80042c8,
mutex=0x7f0ef80042a0, abstime=0x7f0eff0a5d00) at pthread_cond_wait.c:667
#3  0x7f0f41ce6468 in Q

[plasmashell] [Bug 432374] New: Rearranging icons in Icons-only task manager results in random unexpected behaviour

2021-02-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=432374

Bug ID: 432374
   Summary: Rearranging icons in Icons-only task manager results
in random unexpected behaviour
   Product: plasmashell
   Version: 5.18.5
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: milos.djordje...@htecgroup.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 135348
  --> https://bugs.kde.org/attachment.cgi?id=135348&action=edit
Video that shows what happens exactly

SUMMARY

Moving pinned apps on icons-only task manager moves them at random. I uploaded
a video in attachment to showcase this behaviour better.

STEPS TO REPRODUCE
1. Pin several apps to icons-only task manager
2. Move them around to rearrange them
3. Click on one of them and drag it to the left or right

OBSERVED RESULT

When dragging one app, sometimes it works, sometimes when moving one app the
other is moving, also it an happen that when one app is moved to a new position
to the left or to the right other apps around it rearrange at random.

EXPECTED RESULT

When dragged to the desired location they should be placed there and other apps
around should not move.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 20.04 (64-bit)
KDE Plasma Version: 5.18.5 
KDE Frameworks Version: 5.68.0 
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Kernel: 5.4.0-65

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

[systemsettings] [Bug 427444] System Settings crashes in QQmlData::wasDeleted() when navigating to a different KCM while on the Screen Locker KCM's Appearance page

2021-02-01 Thread Mattes D
https://bugs.kde.org/show_bug.cgi?id=427444

Mattes D  changed:

   What|Removed |Added

 CC||kde-b...@xoft.cz

--- Comment #7 from Mattes D  ---
I think I'm getting the same bug - after opening the Settings -> Workspace
Behavior -> Screen Locking and clicking the (Appearance) Configure button,
clicking on any other pane in the Settings app will crash the app.

This is the relevant part of the backtrace, as given to me (for some reason the
automatic crash handler is unable to install some of the debug symbol files):

Thread 1 (Thread 0x7f798dbea8c0 (LWP 182391)):
[KCrash Handler]
#4  0x7f79915979be in
QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*,
QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*,
QQmlPropertyData**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#5  0x7f7991571cf2 in
QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*,
QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f7991572644 in
QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*,
QV4::ExecutionEngine*, QV4::Value*) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f79915b887c in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f79915be02f in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f799154b24d in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f79916f0fa7 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f79916948ae in QQmlBoundSignalExpression::evaluate(void**) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f7991695948 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f79916d064d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f7991672fbf in QQmlData::signalEmitted(QAbstractDeclarativeData*,
QObject*, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7f7992764245 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f7991690fe9 in QQmlContextData::emitDestruction() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#17 0x7f799169100f in QQmlContextData::emitDestruction() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#18 0x7f799169100f in QQmlContextData::emitDestruction() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#19 0x7f799169100f in QQmlContextData::emitDestruction() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#20 0x7f799169100f in QQmlContextData::emitDestruction() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#21 0x7f79916910fd in QQmlContextData::invalidate() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#22 0x7f7991690d9b in QQmlContextData::destroy() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#23 0x7f7991690f4d in QQmlContext::~QQmlContext() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#24 0x7f7991690f6d in QQmlContext::~QQmlContext() () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#25 0x7f7992757cbe in QObjectPrivate::deleteChildren() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f79927626e6 in QObject::~QObject() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f7991e3a8ed in
KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from
/lib/x86_64-linux-gnu/libKF5Declarative.so.5
#28 0x7f7993cbd055 in KQuickAddons::ConfigModule::~ConfigModule() () from
/lib/x86_64-linux-gnu/libKF5QuickAddons.so.5
#29 0x7f79557cdca6 in ScreenLockerKcm::~ScreenLockerKcm
(this=0x5566831943a0, __in_chrg=) at ./kcm/kcm.h:43
#30 ScreenLockerKcm::~ScreenLockerKcm (this=0x5566831943a0,
__in_chrg=) at ./kcm/kcm.h:43
#31 0x7f7993de8cc7 in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#32 0x7f7993de8cfd in ?? () from /lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#33 0x7f7993deecf8 in KCModuleProxy::deleteClient() () from
/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#34 0x7f7993deee01 in KCModuleProxy::~KCModuleProxy() () from
/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#35 0x7f7993deef9d in KCModuleProxy::~KCModuleProxy() () from
/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#36 0x7f7992757cbe in QObjectPrivate::deleteChildren() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#37 0x7f79933695b6 in QWidget::~QWidget() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#38 0x7f79933697ad in QWidget::~QWidget() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#39 0x7f7992757cbe in QObjectPrivate::deleteChildren() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#40 0x7f79933695b6 in QWidget::~QWidget() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#41 0x7f79934cdd7d in QScrollArea::~QScrollArea() () from
/lib/x86_64-linux-gn

[systemsettings] [Bug 427444] System Settings crashes in QQmlData::wasDeleted() when navigating to a different KCM while on the Screen Locker KCM's Appearance page

2021-02-01 Thread Mattes D
https://bugs.kde.org/show_bug.cgi?id=427444

--- Comment #8 from Mattes D  ---
Forgot to add to my report the OS versions:
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Processors: 12 × AMD Ryzen 5 PRO 4650G with Radeon Graphics
Memory: 13,6 GiB of RAM
Graphics Processor: AMD RENOIR

Let me know if I can be of any further help.

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

[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2021-02-01 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #41 from Attila  ---
(In reply to RJVB from comment #39)
> A pure text email of 35Mb is massive too, but eating around 4Gb of RAM for
> that isn't just massive. That's what you meant, right, not 4Mb for
> displaying just the part that fits in your window (which would seem
> reasonable)? 4Gb, that's about 120 times the size of the email.

Yes I mean 4.317.684 K (QtWebEngineProcess).

> I knew KMail would become a powerkids' tool with the design decision to use
> a full-fledged-browser-in-a-widget (QtWebEngine) for rendering everything
> including pure text emails but I wasn't expecting this. Then again, I don't
> usually get this kind of long letters by email so I have no idea how any
> other MUA would handle them.

I get this kind of long emails every day. This is the output from backup
scripts executed by Cron.

> If the account you got this email on has a web/browser interface it would be
> interesting to estimate the resources an actual browser (GChrome or
> Chromium) would use to display it, for comparison.

Unfortunately this account doesn't have a Web-Interface, but I did a test on
another account with Web-Interface.
The plain text has a size of 20 MiB.

In Comparison:
QtWebEngineProcess (KMail) is eating 1.609.232 K.
Firefox (Web-Interface) is eating 156.204 K.

Firefox can display this e-mail within 2 seconds and I can scroll very smooth
through  the content by dragging the scrollbar.

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

[Akonadi] [Bug 431077] Failure to send email message from Kmail using Google SMTP

2021-02-01 Thread Jebin
https://bugs.kde.org/show_bug.cgi?id=431077

Jebin  changed:

   What|Removed |Added

 CC||jebin12...@gmail.com

--- Comment #1 from Jebin  ---
I am facing the same issue as well. Same OS configuration as OP.

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

[Discover] [Bug 431886] Discover "Housekeeping" - Wishlist

2021-02-01 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=431886

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org

--- Comment #3 from Harald Sitter  ---
The archives cache is a cache see `man apt.conf`

The installed kernel topic is tricky though.
The apt in ubuntu 22.04 will eventually fix that [1] with a new option that
will be on for packagekit by default, the apt in 20.04 doesn't have that
feature.

Apt currently only has a sledge hammer version [2] which is technically
accessible by setting autoremove on remove transactions (which discover does
not do). That would, as far as I understand the code, remove all dangling
packages with aptcc, albeit only when removing something not when upgrading. So
it'd only be somewhat helpful anyway and I'm not quite sure it's entirely safe
to use - the kernel use case is fine there are guards in place, but everything
else might get nuked.

In conclusion I'm leaning towards closing this as an upstream bug and its been
fixed upstream already but won't arrive in neon before 2022.
Somewhat relatedly I do already have plans to add space monitoring for /boot to
prevent the user from running out of space for kernel updates without warning.

[1]
https://salsa.debian.org/apt-team/apt/-/commit/944baec85a7496c1595242a31f6b1b37530451a5
[2] https://github.com/hughsie/PackageKit/issues/201

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

[extra-cmake-modules] [Bug 432375] New: Fails to fetch translations (regexp produces incorrect repository name)

2021-02-01 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=432375

Bug ID: 432375
   Summary: Fails to fetch translations (regexp produces incorrect
repository name)
   Product: extra-cmake-modules
   Version: 5.78.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ecm-bugs-n...@kde.org
  Reporter: j...@kdenlive.org
  Target Milestone: ---

SUMMARY
The current releasescript fails to fetch translations for Kdenlive.

STEPS TO REPRODUCE
1. Configure Kdenlive using the cmake param: -DKDE_L10N_SYNC_TRANSLATIONS=ON
2. On terminal it prints: found 0 elements for kdenlive


OBSERVED RESULT
No translations are downloaded/installed.


EXPECTED RESULT
Translations working

Problem is that our invent repository is:
multimedia/kdenlive

But the ecm regexp filters out '/', so we end up with reponame=kdenlive.
Changing the regexp in KDECMakeSettings.cmake line 310:

string(REGEX MATCHALL ".+kde\\.org[:\\/]([-A-Za-z0-9\\/]+)(.git)?\\s*" ""
${giturl})

to (remove the "/" filter):

string(REGEX MATCHALL ".+kde\\.org[:]([-A-Za-z0-9\\/]+)(.git)?\\s*" ""
${giturl})

Produces a correct repo name (multimedia/kdenlive) and translations are then
correctly installed.

If it helps, the command:
git remote get-url --all origin
produces this output:
g...@invent.kde.org:multimedia/kdenlive.git



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.

[extra-cmake-modules] [Bug 432375] Fails to fetch translations (regexp produces incorrect repository name)

2021-02-01 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=432375

--- Comment #1 from Jean-Baptiste Mardelle  ---
This is linked to this commit:
https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/693781d22e98057d83eac2b2c85d04063202f26f

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

[kwin] [Bug 425586] [Wayland] KDE does not detect a second monitor

2021-02-01 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=425586

--- Comment #41 from Zamundaaa  ---
Good news, someone in another bug report already tested it and it does indeed
fix it! Enjoy your tearing free secondary monitors in 5.21 :)

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

[kwin] [Bug 425586] [Wayland] KDE does not detect a second monitor

2021-02-01 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=425586

Zamundaaa  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/b50f7478769c |ma/kwin/commit/2c6d19fec141
   |1b50b48d5f0e9201a8e4b7e275e |3244938bc997373e5f75df2c1ad
   |f   |a
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #42 from Zamundaaa  ---
Git commit 2c6d19fec1413244938bc997373e5f75df2c1ada by Xaver Hugl.
Committed on 01/02/2021 at 11:26.
Pushed by zamundaaa into branch 'master'.

Only release shared buffers right before the next frame

M  +0-3plugins/platforms/drm/abstract_egl_drm_backend.h
M  +8-22   plugins/platforms/drm/egl_gbm_backend.cpp
M  +0-1plugins/platforms/drm/egl_gbm_backend.h

https://invent.kde.org/plasma/kwin/commit/2c6d19fec1413244938bc997373e5f75df2c1ada

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

[kwin] [Bug 425586] [Wayland] KDE does not detect a second monitor

2021-02-01 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=425586

Zamundaaa  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/2c6d19fec141 |ma/kwin/commit/27e7dba1c47a
   |3244938bc997373e5f75df2c1ad |7ccaf3b66bbdb7ee0ef6eb4a746
   |a   |3

--- Comment #43 from Zamundaaa  ---
Git commit 27e7dba1c47a7ccaf3b66bbdb7ee0ef6eb4a7463 by Xaver Hugl.
Committed on 01/02/2021 at 11:27.
Pushed by zamundaaa into branch 'Plasma/5.21'.

Only release shared buffers right before the next frame


(cherry picked from commit 2c6d19fec1413244938bc997373e5f75df2c1ada)

M  +0-3plugins/platforms/drm/abstract_egl_drm_backend.h
M  +8-22   plugins/platforms/drm/egl_gbm_backend.cpp
M  +0-1plugins/platforms/drm/egl_gbm_backend.h

https://invent.kde.org/plasma/kwin/commit/27e7dba1c47a7ccaf3b66bbdb7ee0ef6eb4a7463

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

[konsole] [Bug 432376] New: Issues with reflow (links and highlighting)

2021-02-01 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=432376

Bug ID: 432376
   Summary: Issues with reflow (links and highlighting)
   Product: konsole
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: martin.sandsm...@kde.org
  Target Milestone: ---

Created attachment 135349
  --> https://bugs.kde.org/attachment.cgi?id=135349&action=edit
highlighted the link, and then tried to remove the highlight

Several different issues with reflow code, so far the text highlighting seems
broken (it doesn't un-highlight whatever I've highlighted) and for some reason
I randomly get double height text.

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

[kwin] [Bug 431968] Plasma 5.21 wayland crashes and has render issues

2021-02-01 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=431968

--- Comment #27 from Zamundaaa  ---
If you have more questions not directly related to this bug you can use the
direct message function on Reddit. Thanks again for testing :)

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

[kwin] [Bug 431968] Plasma 5.21 wayland crashes and has render issues

2021-02-01 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=431968

Zamundaaa  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/kwin/commit/f8d9b3bc6cc8
   ||ee5ee57ce78d2d1368b77ce90f5
   ||c
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #28 from Zamundaaa  ---
Git commit f8d9b3bc6cc8ee5ee57ce78d2d1368b77ce90f5c by Xaver Hugl.
Committed on 01/02/2021 at 11:28.
Pushed by zamundaaa into branch 'master'.

Actually use a linear buffer format for multi-GPU

M  +12   -20   plugins/platforms/drm/egl_gbm_backend.cpp
M  +0-2plugins/platforms/drm/egl_gbm_backend.h

https://invent.kde.org/plasma/kwin/commit/f8d9b3bc6cc8ee5ee57ce78d2d1368b77ce90f5c

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

[kwin] [Bug 431968] Plasma 5.21 wayland crashes and has render issues

2021-02-01 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=431968

Zamundaaa  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
   |ma/kwin/commit/f8d9b3bc6cc8 |ma/kwin/commit/9679beace6dd
   |ee5ee57ce78d2d1368b77ce90f5 |44c2910988f2139f357eb657d84
   |c   |e

--- Comment #29 from Zamundaaa  ---
Git commit 9679beace6dd44c2910988f2139f357eb657d84e by Xaver Hugl.
Committed on 01/02/2021 at 11:35.
Pushed by zamundaaa into branch 'Plasma/5.21'.

Actually use a linear buffer format for multi-GPU


(cherry picked from commit f8d9b3bc6cc8ee5ee57ce78d2d1368b77ce90f5c)

M  +12   -20   plugins/platforms/drm/egl_gbm_backend.cpp
M  +0-2plugins/platforms/drm/egl_gbm_backend.h

https://invent.kde.org/plasma/kwin/commit/9679beace6dd44c2910988f2139f357eb657d84e

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

[konsole] [Bug 432376] Issues with reflow (links and highlighting)

2021-02-01 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=432376

--- Comment #1 from Martin Sandsmark  ---
Created attachment 135350
  --> https://bugs.kde.org/attachment.cgi?id=135350&action=edit
double line height, also seems to randomly remove the text entirely sometimes

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

[konsole] [Bug 432376] Issues with reflow (links and highlighting)

2021-02-01 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=432376

--- Comment #2 from Martin Sandsmark  ---
Just to clarify the title: this is related to the new "reflowing" of the scroll
history thing.

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

[krunner] [Bug 432377] New: KRunner calculator wrongly interpret hex numbers starting with digit as multiplication

2021-02-01 Thread Mykola Krachkovsky
https://bugs.kde.org/show_bug.cgi?id=432377

Bug ID: 432377
   Summary: KRunner calculator wrongly interpret hex numbers
starting with digit as multiplication
   Product: krunner
   Version: 5.20.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: calculator
  Assignee: alexander.loh...@gmx.de
  Reporter: w01dn...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY

KRunner's calculator seems interpret hex numbers starting with digit as a
multiplication leading to zero result.

STEPS TO REPRODUCE
1. Open KRunner
2. Type `=0x20`

OBSERVED RESULT
0

EXPECTED RESULT
32

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210130
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.9-1-default
OS Type: 64-bit

ADDITIONAL INFORMATION

It seems krunner's calculator may interpret `x` as multiplication, e.g.
`=4x5`->`20`. If this is needed for anyone, still `0x4` as multiplication is
pointless, so IMHO, it's better to keep `0x` prefix just for hex numbers and
interpret `x` as multiplication only when there is non-zero value before `x`.

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

[krunner] [Bug 432377] KRunner calculator wrongly interpret hex numbers starting with digit as multiplication

2021-02-01 Thread Alexander Lohnau
https://bugs.kde.org/show_bug.cgi?id=432377

Alexander Lohnau  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/plas
   ||ma/plasma-workspace/-/commi
   ||t/292d9d19250a81757128666c6
   ||b3784c41b3e1697
   Version Fixed In||5.21

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

[krunner] [Bug 432377] KRunner calculator wrongly interpret hex numbers starting with digit as multiplication

2021-02-01 Thread Alexander Lohnau
https://bugs.kde.org/show_bug.cgi?id=432377

Alexander Lohnau  changed:

   What|Removed |Added

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

--- Comment #1 from Alexander Lohnau  ---
Already fixed with
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/571

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

[krunner] [Bug 432377] KRunner calculator wrongly interpret hex numbers starting with digit as multiplication

2021-02-01 Thread Mykola Krachkovsky
https://bugs.kde.org/show_bug.cgi?id=432377

--- Comment #2 from Mykola Krachkovsky  ---
Thanks!

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

[okular] [Bug 335975] mobi file is not fully displayed

2021-02-01 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=335975

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

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

[Breeze] [Bug 426696] Icons for mobi, azw and azw3 files

2021-02-01 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=426696

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

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

[kdeconnect] [Bug 432378] New: feature request: bind to (listen on) specified network interface

2021-02-01 Thread V
https://bugs.kde.org/show_bug.cgi?id=432378

Bug ID: 432378
   Summary: feature request: bind to (listen on) specified network
interface
   Product: kdeconnect
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: v...@robolab.it
  Target Milestone: ---

SUMMARY

by default kdeconnectd listens on all network interfaces which might not be
good in terms of security. It would be better to add an option to specify one
interface for kdeconnectd to bind to, for example - a private LAN/WLAN or an
encrypted VPN between the phone and the computer.

STEPS TO REPRODUCE
1. start kdeconnectd
2. run "netstat -tulpan | grep kdeconnect"

OBSERVED RESULT

kdeconnect listens on all interfaces


EXPECTED RESULT

listen on all interfaces if kdeconnectd was started without arguments;
if started as e.g. "kdeconnectd -i eth0" then listen on eth0 interface only, or
"kdeconnectd -i tun0" then listen on tun0 interface only.

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

[plasmashell] [Bug 432374] Rearranging icons in Icons-only task manager results in random unexpected behaviour

2021-02-01 Thread Paul
https://bugs.kde.org/show_bug.cgi?id=432374

Paul  changed:

   What|Removed |Added

 CC||pip@gmx.com

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

[Breeze] [Bug 432246] Cantata crashes with breeze

2021-02-01 Thread David Redondo
https://bugs.kde.org/show_bug.cgi?id=432246

David Redondo  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #11 from David Redondo  ---
Reopen because commit was reverted

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

[extra-cmake-modules] [Bug 432375] Fails to fetch translations (regexp produces incorrect repository name)

2021-02-01 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=432375

Harald Sitter  changed:

   What|Removed |Added

 CC||sit...@kde.org

--- Comment #2 from Harald Sitter  ---
I don't understand this.
If we removed the leading slash option we'd no longer parse https urls
correctly.

That said I also can't reproduce your problem.

λ ajax /tmp → cat test.cmake
function(foo giturl)
string(REGEX MATCHALL ".+kde\\.org[:\\/]([-A-Za-z0-9\\/]+)(.git)?\\s*" ""
${giturl})
message("${CMAKE_MATCH_1}")
endfunction()

foo("https://invent.kde.org/multimedia/kdenlive";)
foo("g...@invent.kde.org:multimedia/kdenlive")


λ ajax /tmp → cmake -P test.cmake
multimedia/kdenlive
multimedia/kdenlive

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

[partitionmanager] [Bug 426170] KDE Partition Manager shows no disks/doesn't request su permissions to see them

2021-02-01 Thread cluwedo
https://bugs.kde.org/show_bug.cgi?id=426170

--- Comment #11 from cluwedo  ---
I installed lxqt-desktop together with sddm. 
I connect from a Windows 10 system using the Windows RDP client. As far as I
know no display manager is involved in this case. But my knowledge is
insufficient to give a professional opinion on that.

I installed XRDP as described here: http://c-nergy.be/blog/?p=15978
To run lxqt on connect I created the file .xsession and added the command
startlxqt to it. It's the only command in there.

When I run sudo /usr/lib/kauth/libexec/kpmcore_externalcommand I have to enter
my password. After some seconds the command terminates without error messages.

In which list can I find org.kde.kpmcore.helperinterface?

When partitionmanager is running "ps aux" gives me the following list:

USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root   1  0.0  0.0 169964 14024 ?Ss   Jan31   0:10 /sbin/init
root   2  0.0  0.0  0 0 ?SJan31   0:00 [kthreadd]
root   3  0.0  0.0  0 0 ?I<   Jan31   0:00 [rcu_gp]
root   4  0.0  0.0  0 0 ?I<   Jan31   0:00 [rcu_par_gp]
root   6  0.0  0.0  0 0 ?I<   Jan31   0:00
[kworker/0:0H-kblockd]
root   9  0.0  0.0  0 0 ?I<   Jan31   0:00
[mm_percpu_wq]
root  10  0.0  0.0  0 0 ?SJan31   0:00
[ksoftirqd/0]
root  11  0.0  0.0  0 0 ?IJan31   0:06 [rcu_sched]
root  12  0.0  0.0  0 0 ?SJan31   0:00
[migration/0]
root  13  0.0  0.0  0 0 ?SJan31   0:00
[idle_inject/0]
root  14  0.0  0.0  0 0 ?SJan31   0:00 [cpuhp/0]
root  15  0.0  0.0  0 0 ?SJan31   0:00 [cpuhp/1]
root  16  0.0  0.0  0 0 ?SJan31   0:00
[idle_inject/1]
root  17  0.0  0.0  0 0 ?SJan31   0:00
[migration/1]
root  18  0.0  0.0  0 0 ?SJan31   0:00
[ksoftirqd/1]
root  20  0.0  0.0  0 0 ?I<   Jan31   0:00
[kworker/1:0H-kblockd]
root  21  0.0  0.0  0 0 ?SJan31   0:00 [cpuhp/2]
root  22  0.0  0.0  0 0 ?SJan31   0:00
[idle_inject/2]
root  23  0.0  0.0  0 0 ?SJan31   0:00
[migration/2]
root  24  0.0  0.0  0 0 ?SJan31   0:00
[ksoftirqd/2]
root  26  0.0  0.0  0 0 ?I<   Jan31   0:00
[kworker/2:0H-kblockd]
root  27  0.0  0.0  0 0 ?SJan31   0:00 [cpuhp/3]
root  28  0.0  0.0  0 0 ?SJan31   0:00
[idle_inject/3]
root  29  0.0  0.0  0 0 ?SJan31   0:00
[migration/3]
root  30  0.0  0.0  0 0 ?SJan31   0:00
[ksoftirqd/3]
root  32  0.0  0.0  0 0 ?I<   Jan31   0:00
[kworker/3:0H-events_highpri]
root  33  0.0  0.0  0 0 ?SJan31   0:00 [cpuhp/4]
root  34  0.0  0.0  0 0 ?SJan31   0:00
[idle_inject/4]
root  35  0.0  0.0  0 0 ?SJan31   0:00
[migration/4]
root  36  0.0  0.0  0 0 ?SJan31   0:00
[ksoftirqd/4]
root  38  0.0  0.0  0 0 ?I<   Jan31   0:00
[kworker/4:0H-kblockd]
root  39  0.0  0.0  0 0 ?SJan31   0:00 [cpuhp/5]
root  40  0.0  0.0  0 0 ?SJan31   0:00
[idle_inject/5]
root  41  0.0  0.0  0 0 ?SJan31   0:00
[migration/5]
root  42  0.0  0.0  0 0 ?SJan31   0:00
[ksoftirqd/5]
root  44  0.0  0.0  0 0 ?I<   Jan31   0:00
[kworker/5:0H-kblockd]
root  45  0.0  0.0  0 0 ?SJan31   0:00 [kdevtmpfs]
root  46  0.0  0.0  0 0 ?I<   Jan31   0:00 [netns]
root  47  0.0  0.0  0 0 ?SJan31   0:00
[rcu_tasks_kthre]
root  48  0.0  0.0  0 0 ?SJan31   0:00 [kauditd]
root  49  0.0  0.0  0 0 ?SJan31   0:00 [khungtaskd]
root  50  0.0  0.0  0 0 ?SJan31   0:00 [oom_reaper]
root  51  0.0  0.0  0 0 ?I<   Jan31   0:00 [writeback]
root  52  0.0  0.0  0 0 ?SJan31   0:00 [kcompactd0]
root  53  0.0  0.0  0 0 ?SN   Jan31   0:00 [ksmd]
root  54  0.0  0.0  0 0 ?SN   Jan31   0:00 [khugepaged]
root 101  0.0  0.0  0 0 ?I<   Jan31   0:00
[kintegrityd]
root 102  0.0  0.0  0 0 ?I<   Jan31   0:00 [kblockd]
root 103  0.0  0.0  0 0 ?I<   Jan31   0:00
[blkcg_punt_bio]
root 106  0.0  0.0  0 0 ?I<   Jan31   0:00 [tpm_dev_wq]
root 107  0.0  0.0  0 0 ?I<  

[ktouch] [Bug 404918] Hangul is not input.

2021-02-01 Thread Kishore Gopalakrishnan
https://bugs.kde.org/show_bug.cgi?id=404918

Kishore Gopalakrishnan  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

[partitionmanager] [Bug 426170] KDE Partition Manager shows no disks/doesn't request su permissions to see them

2021-02-01 Thread cluwedo
https://bugs.kde.org/show_bug.cgi?id=426170

--- Comment #12 from cluwedo  ---
If I run GParted an authentication window opens: 'Authentication is required to
run the GParted Editor as root'. After authentication GParted starts and finds
all available devices.

Partitionmanager does not show an authentication window. Is this as it should
be?

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

[extra-cmake-modules] [Bug 432375] Fails to fetch translations (regexp produces incorrect repository name)

2021-02-01 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=432375

--- Comment #3 from Jean-Baptiste Mardelle  ---
Oh... sorry for the noise. The problem actually is that I was trying to fetch
translations using an older version of KDE Frameworks (5.68). This version
contains a different REGEXP :

string(REGEX MATCHALL ".+[:\\/]([-A-Za-z0-9]+)(.git)?\\s*" "" ${giturl})

https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/v5.68.0/kde-modules/KDECMakeSettings.cmake#L324

Which breaks as described in my report. You are right, the REGEXP is now
correct and the bug is fixed. It's just that we cannot build with translations
on previous Frameworks versions older than 5.76...

And there doesn't seem to be a way to override the project name extracted by
the regexp..

But I guess nothing can be done...

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

[digikam] [Bug 432369] Wrong time for mp4 in _almost_ all places, metadata differs from filesystem/other apps. DB issues?

2021-02-01 Thread Thomas
https://bugs.kde.org/show_bug.cgi?id=432369

--- Comment #4 from Thomas  ---
I have tested a bit more.

I transferred a fresh file from my phone and imported into digikam.
Exiftool reports:

[tomteverkstan] ~/digibug
(13:44) (digitest:2) $ exiftool -time:all -G0:1 VID_20210201_085801.mp4 
[ExifTool]  Now : 2021:02:01 13:48:20+01:00
[File:System]   File Modification Date/Time : 2021:02:01 09:03:52+01:00
[File:System]   File Access Date/Time   : 2021:02:01 09:04:44+01:00
[File:System]   File Inode Change Date/Time : 2021:02:01 09:04:22+01:00
[QuickTime] Create Date : 2021:02:01 07:58:01
[QuickTime] Modify Date : 2021:02:01 07:58:01
[QuickTime:Track1] Track Create Date: 2021:02:01 07:58:01
[QuickTime:Track1] Track Modify Date: 2021:02:01 07:58:01
[QuickTime:Track1] Media Create Date: 2021:02:01 07:58:01
[QuickTime:Track1] Media Modify Date: 2021:02:01 07:58:01
[QuickTime:Track2] Track Create Date: 2021:02:01 07:58:01
[QuickTime:Track2] Track Modify Date: 2021:02:01 07:58:01
[QuickTime:Track2] Media Create Date: 2021:02:01 07:58:01
[QuickTime:Track2] Media Modify Date: 2021:02:01 07:58:01

The correct time is 08:58, and that is what digikam says. So, it appears files
are recorded in UTC time, and digikam adds +1h based on my system timezone,
like you said.

But, why not for images then?
This image:
 20201003_163739-IMG-P20.jpg
[ExifTool]  Now : 2021:02:01 13:54:02+01:00
[File:System]   File Modification Date/Time : 2020:10:03 16:37:39+02:00
[File:System]   File Access Date/Time   : 2021:02:01 13:44:12+01:00
[File:System]   File Inode Change Date/Time : 2021:02:01 13:44:08+01:00
[EXIF:IFD0] Modify Date : 2020:10:03 16:37:39
[EXIF:ExifIFD]  Date/Time Original  : 2020:10:03 16:37:39
[EXIF:ExifIFD]  Create Date : 2020:10:03 16:37:39
[EXIF:ExifIFD]  Sub Sec Time: 220008
[EXIF:ExifIFD]  Sub Sec Time Original   : 220008
[EXIF:ExifIFD]  Sub Sec Time Digitized  : 220008
[Composite] Create Date : 2020:10:03 16:37:39.220008
[Composite] Date/Time Original  : 2020:10:03 16:37:39.220008
[Composite] Modify Date : 2020:10:03 16:37:39.220008

is displayed with the correct time. 16:37. Not 17:37. So, why is +1 hour not
added there? Are images not treated as UTC?

I have the setting "View -> Sort Items -> By Creation Date".
This led me to believe that it would use either EXIF:Create Date, or
QuickTime:Create Date for images and movies respectively. But it appears it
also edits the date for video files based on, like you say, if it is a phone.
This seems odd to me given the setting. Can this be toggled somewhere?

I would much rather just set all my file dates correctly, and adjust digikam
accordingly, than the other way around. Especially when videos and images are
treated differently.

I uploaded my test file here:
https://drive.google.com/file/d/1NvMmgS1JWxdjaPPhICXxJVZ_2Fqxh_8t/view?usp=sharing

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

[partitionmanager] [Bug 426170] KDE Partition Manager shows no disks/doesn't request su permissions to see them

2021-02-01 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=426170

--- Comment #13 from Andrius Štikonas  ---
(In reply to cluwedo from comment #12)
> If I run GParted an authentication window opens: 'Authentication is required
> to run the GParted Editor as root'. After authentication GParted starts and
> finds all available devices.
> 
> Partitionmanager does not show an authentication window. Is this as it
> should be?

It's not partitionmanager that shows an authentication window but
kpmcore_externalcommand helper. And it closes because for some reason it can't
register dbus session (might be distro or host config related, since it works
in most distros).

By the way there were quite some changes in 4.2.0 in kpmcore_externalcommand
helper, so it would be good if somebody try that.

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

[systemsettings] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off

2021-02-01 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=432107

--- Comment #10 from Wolfgang Bauer  ---
(In reply to Claudius Ellsel from comment #9)
> Then this issue still remains relevant for KDE in my opinion. Basically I
> think it will be beneficial to for example have a fourth option that will
> use the BIOS setting (or/and another one that restores this setting from the
> previous session).
I'm not sure it's possible from the KDE/Plasma side, and I don't see why Plasma
should change it to be different than on the login screen.

That's my opinion, of course.

> Ideally openSUSE would "upstream" the things they do for this and then use
> the setting from KDE instead of relying on a hidden service for this.
That has no relevance to KDE though. It's a service that runs on boot and also
affects text mode.

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

[extra-cmake-modules] [Bug 432375] Fails to fetch translations (regexp produces incorrect repository name)

2021-02-01 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=432375

Harald Sitter  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #4 from Harald Sitter  ---
Well, the problem here is that along with the invent migration the community
somehow decided that repo names will be non-unique moving forward which is why
the original regex is actually no longer working. Because of the non-uniqueness
policy releaseme cannot assume that 'phone', the output of the old regex, is
indeed the same as 'maui/phone' as there may have been a completely unrelated
repo 'plasma/phone' at some time in the past or future or current.

If you feel strongly about this you could get a discussion started on changing
this policy so repo names must be unique again. I know there are others that
have gotten annoyed by it and I also know that I have had to write extra code
at various places just to deal with this theoretical non-uniqueness. Having to
know that kdenlive is in multimedia/ isn't convenient on any level really.

I'm closing this bug as ECM is working correctly (technically anyway :S)

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

[Discover] [Bug 409136] Setting to adjust checking for updates frequency

2021-02-01 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=409136

Marcel  changed:

   What|Removed |Added

 CC||misterx.m...@gmail.com

--- Comment #4 from Marcel  ---
I would like to add to the already made suggestions the ability to chose to
disable or change frequency of checking for updates depending on package type.

For example disable checking for updates for system packages (e.g.:.deb, .rpm,
...) but keep or set an other frequency for flatpaks, snaps or fwupd packages.

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

[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2021-02-01 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #42 from Wolfgang Bauer  ---
(In reply to Attila from comment #41)
> Firefox can display this e-mail within 2 seconds and I can scroll very
> smooth through  the content by dragging the scrollbar.
Have you tried in Chromium though? (which is what QtWebEngine is based upon)

TBH, I think even QtWebKit would struggle with these large mails, according to
my experiences with OBS build logs... (KHTML served better in this regard, but
that's completely dead now)

Anyway, this is kind of a different problem than comment#35 (or comment#0).
I don't see how it could be fixed from the kmail side, except for not trying to
display mails larger than a certain size at all. (or maybe just display it as
plain text instead then, but that probably means a large rewrite of the code,
and I'm not sure it's possible at all)

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

[Breeze] [Bug 432333] Hibernate & network applet icon missing on Xfce

2021-02-01 Thread Or Schiro
https://bugs.kde.org/show_bug.cgi?id=432333

--- Comment #2 from Or Schiro  ---
Thanks Nate!

On Xfce 4.14 they are called:

Network:

- nm-device-wired.svg
- nm-no-connection.svg
- nm-nm-signal-00.svg
- nm-nm-signal-25.svg
- nm-nm-signal-50.svg
- nm-nm-signal-75.svg
- nm-nm-signal-100.svg

Hibernate:

- system-hibernate.svg

On Xfce 4.16 (upcoming) they are going to be called:

Hibernate:

- xfsm-hibernate

Network:

- org.xfce.gigolo

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

[konsole] [Bug 432379] New: undefined reference to KonsoleDebug() when building tests

2021-02-01 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=432379

Bug ID: 432379
   Summary: undefined reference to KonsoleDebug() when building
tests
   Product: konsole
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: martin.sandsm...@kde.org
  Target Milestone: ---

/usr/lib/ccache/bin/c++ -fdiagnostics-color=always -fno-operator-names
-fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security
-Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual
-Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op
-fdiagnostics-color=always -fsanitize=address -fno-omit-frame-pointer
-fno-optimize-sibling-calls -fsanitize=undefined -fno-omit-frame-pointer
-fno-optimize-sibling-calls -fno-operator-names -fno-exceptions -Wall -Wextra
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith
-Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla
-Wdate-time -Wsuggest-override -Wlogical-op -fdiagnostics-color=always
-fsanitize=address -fno-omit-frame-pointer -fno-optimize-sibling-calls
-fsanitize=undefined -fno-omit-frame-pointer -fno-optimize-sibling-calls
-pedantic -Wzero-as-null-pointer-constant -fsanitize=address
-fno-omit-frame-pointer -fno-optimize-sibling-calls -fsanitize=undefined
-fno-omit-frame-pointer -fno-optimize-sibling-calls -g -Wl,--enable-new-dtags
-Wl,--enable-new-dtags
src/autotests/CMakeFiles/KeyboardTranslatorTest.dir/KeyboardTranslatorTest_autogen/mocs_compilation.cpp.o
src/autotests/CMakeFiles/KeyboardTranslatorTest.dir/KeyboardTranslatorTest.cpp.o
-o bin/KeyboardTranslatorTest  -lasan  -lasan  -lasan  -lasan  -lasan  -lasan 
/usr/lib/libQt5Test.so.5.15.2  lib/libkonsoleprivate.a 
lib/libkonsoleprivate_core.a  lib/libkeyboardtranslator.a 
lib/libkonsolehelpers.a  lib/libkonsolecolorscheme.a  -lasan [... some
thousands of KF5 libs...]

/usr/bin/ld: lib/libkeyboardtranslator.a(KeyboardTranslatorReader.cpp.o): in
function `Konsole::KeyboardTranslatorReader::readNext()':
/home/sandsmark/src/konsole/build/../src/keyboardtranslator/KeyboardTranslatorReader.cpp:90:
undefined reference to `KonsoleDebug()'

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

[konsole] [Bug 432376] Issues with reflow (links and highlighting)

2021-02-01 Thread Martin Sandsmark
https://bugs.kde.org/show_bug.cgi?id=432376

--- Comment #3 from Martin Sandsmark  ---
just tried to build with asan and ubsan and it crashes immediately when it
tries to reflow, assuming it is related:

==131591==ERROR: AddressSanitizer: heap-use-after-free on address
0x6082f520 at pc 0x7f38df17a22b bp 0x7ffc78b00f80 sp 0x7ffc78b00f70
READ of size 1 at 0x6082f520 thread T0
#0 0x7f38df17a22a in QVarLengthArray::insert(unsigned
char const*, int, unsigned char const&)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x167c22a)
#1 0x7f38df16c48c in QVarLengthArray::insert(int,
unsigned char const&)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x166e48c)
#2 0x7f38df13c12d in Konsole::Screen::resizeImage(int, int)
../src/Screen.cpp:479
#3 0x7f38df0b9698 in Konsole::Emulation::setImageSize(int, int)
../src/Emulation.cpp:317
#4 0x7f38deed7843 in Konsole::Session::updateTerminalSize()
../src/session/Session.cpp:753
#5 0x7f38deed6495 in Konsole::Session::onViewSizeChange(int, int)
../src/session/Session.cpp:726
#6 0x7f38def1afe5 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Konsole::Session::*)(int,
int)>::call(void (Konsole::Session::*)(int, int), Konsole::Session*, void**)
/usr/include/qt/QtCore/qobjectdefs_impl.h:152

0x6082f520 is located 0 bytes inside of 89-byte region
[0x6082f520,0x6082f579)
freed by thread T0 here:
#0 0x7f38e0f9f0e9 in __interceptor_free
/build/gcc/src/gcc/libsanitizer/asan/asan_malloc_linux.cpp:123
#1 0x7f38df171e80 in QVarLengthArray::realloc(int, int)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x1673e80)
#2 0x7f38df1683fb in QVarLengthArray::resize(int)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x166a3fb)
#3 0x7f38df17a1d8 in QVarLengthArray::insert(unsigned
char const*, int, unsigned char const&)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x167c1d8)
#4 0x7f38df16c48c in QVarLengthArray::insert(int,
unsigned char const&)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x166e48c)
#5 0x7f38df13c12d in Konsole::Screen::resizeImage(int, int)
../src/Screen.cpp:479
#6 0x7f38df0b9698 in Konsole::Emulation::setImageSize(int, int)
../src/Emulation.cpp:317

previously allocated by thread T0 here:
#0 0x7f38e0f9f459 in __interceptor_malloc
/build/gcc/src/gcc/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x7f38df171901 in QVarLengthArray::realloc(int, int)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x1673901)
#2 0x7f38df1683fb in QVarLengthArray::resize(int)
(/home/sandsmark/src/konsole/build/bin/libkdeinit5_konsole.so+0x166a3fb)
#3 0x7f38df13da7b in Konsole::Screen::resizeImage(int, int)
../src/Screen.cpp:511
#4 0x7f38df0b9698 in Konsole::Emulation::setImageSize(int, int)
../src/Emulation.cpp:317

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

[kwin] [Bug 426450] [Wayland] (Optionally) disable new layout OSD

2021-02-01 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=426450

--- Comment #18 from Andrey  ---
Git commit 61be205a0dd98bc6a56c34697490a86ad5118231 by Andrey Butirsky.
Committed on 01/02/2021 at 13:39.
Pushed by butirsky into branch 'master'.

feat: add option to disable OSD on keyboard layout change

Counterpart commit with the same title is in P-D
Related: bug 376460

M  +5-3shell/osd.cpp
M  +2-1shell/osd.h

https://invent.kde.org/plasma/plasma-workspace/commit/61be205a0dd98bc6a56c34697490a86ad5118231

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

[kwin] [Bug 376460] OSD is annoying (layout switching) on Wayland

2021-02-01 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=376460

--- Comment #6 from Andrey  ---
Git commit 61be205a0dd98bc6a56c34697490a86ad5118231 by Andrey Butirsky.
Committed on 01/02/2021 at 13:39.
Pushed by butirsky into branch 'master'.

feat: add option to disable OSD on keyboard layout change

Counterpart commit with the same title is in P-D
Related: bug 426450

M  +5-3shell/osd.cpp
M  +2-1shell/osd.h

https://invent.kde.org/plasma/plasma-workspace/commit/61be205a0dd98bc6a56c34697490a86ad5118231

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

  1   2   3   4   >