[plasmashell] [Bug 363932] Device Notifier fails to ignore LUKS volume despite solid rules

2020-04-06 Thread Matt Whitlock
https://bugs.kde.org/show_bug.cgi?id=363932

Matt Whitlock  changed:

   What|Removed |Added

 CC||k...@mattwhitlock.name

--- Comment #3 from Matt Whitlock  ---
I have the same issue, though my LUKS volumes are non-removable (and I have
Device Notifier configured to show all devices). Despite that I have set
UDISKS_IGNORE="1" on my LUKS volumes, Device Notifier still shows them. As in
Comment 2, solid-hardware5 shows 'StorageAccess.ignored' and
'StorageVolume.ignored' are both true.

Device Notifier respects the 'ignored' hints on my non-LUKS volumes, but it
apparently ignores the hint on LUKS volumes.

I am on Plasma 5.18.3.

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

[digikam] [Bug 419744] 7.0.0-beta3 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #12 from Maik Qualmann  ---
Starting from a new configuration where all metadata write operations are
deactivated and only activated by the user, the previous behavior was an error.
We will include information about this in the release announcement for
digiKam-7.0.0.
I tested again whether the image is changed if the option is deactivated, no it
will not. They may have written geological tags in the image, the setting for
tags and geological information are separate and will be treated as such.

Maik

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

[kdenlive] [Bug 403224] Freeze when opening projects or creating clips

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403224

ero...@gmail.com changed:

   What|Removed |Added

Version|18.12.1 |19.12.2
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||ero...@gmail.com

--- Comment #4 from ero...@gmail.com ---
Confirm with version kdenlive-19.12.2-x86_64.appimage. When interface config
default all work good. When I change interface composition then close kdenlive
then open, result:
1) Freezed when adding clip to project.
2) Freezed when opening exist project.

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

[kcalc] [Bug 419775] precedence is wrong for unary operator

2020-04-06 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=419775

Christoph Feck  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

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

[digikam] [Bug 419744] 7.0.0-beta3 Geolocation Editor does not save new location

2020-04-06 Thread hmueller
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #11 from hmueller  ---
> Like all other metadata write operations, the default setting is deactivated.

I personally to not like this default setting, as writing these data to the
image was the default before. Without this bug I would not notice this change
and live on in the belief that all my images store the correct location.

Another bug is, that without the write GPS option the image file gets touched
(no change, I made a diff, but file date and time are set to the current) so my
cloud service uploads this file to the server. This confused me in the first
time. This should be avoided imho.

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

[konversation] [Bug 335109] Change the default logging directory from ~/logs to where logs are generally saved

2020-04-06 Thread Justin
https://bugs.kde.org/show_bug.cgi?id=335109

--- Comment #3 from Justin  ---
Thanks!

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

[digikam] [Bug 419744] 7.0.0-beta3 Geolocation Editor does not save new location

2020-04-06 Thread hmueller
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #10 from hmueller  ---
Hi Maik,
you are up early! :-)
Just to make it complete. The following options are set (and if not noted here
they are not set):
All options in section "Write This Information to the Metadata".
In "Reading and Writing Metadata"
- Update file modification timestamp when files are modified
- Rescan file when files are modified

The Rescan option did not have had an impact if checked or not.

I will test your change as soon as the Mac version has been compiled and
uploaded.
Holger

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

[okular] [Bug 419356] Default pageview (e.g. fit page, fit width) does not register sometimes

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419356

norwegian_panca...@protonmail.ch changed:

   What|Removed |Added

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

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

[konversation] [Bug 335109] Change the default logging directory from ~/logs to where logs are generally saved

2020-04-06 Thread Peter Simonsson
https://bugs.kde.org/show_bug.cgi?id=335109

Peter Simonsson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kon
   ||versation/103e441fe9ccd6d77
   ||d782afcd3cbd347ece0172c

--- Comment #2 from Peter Simonsson  ---
Git commit 103e441fe9ccd6d77d782afcd3cbd347ece0172c by Peter Simonsson.
Committed on 07/04/2020 at 04:46.
Pushed by psn into branch 'master'.

Change default logging directory

Use ~/.local/share/konversation/logs by default instead of creating the
logs directory directly in the home directory.

M  +1-1src/config/konversation.kcfg

https://commits.kde.org/konversation/103e441fe9ccd6d77d782afcd3cbd347ece0172c

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

[krita] [Bug 418600] i cannot put sounds on krita and i dont know what to do, it says error and i tried with diferent types of audios but its always error please help

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418600

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[elisa] [Bug 417468] The right part of elisa shows gibberish chars (maybe GB2312 encoding problem )

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=417468

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

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

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

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

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

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

[kdenlive] [Bug 418525] Application: Kdenlive (kdenlive), signal: Segmentation fault

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418525

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[krita] [Bug 418596] Animation does not play properly higher than about 10-15 fps (effects audio as well)

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418596

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kdenlive] [Bug 383122] Kdenlive crashes on playback

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=383122

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[Spectacle] [Bug 419148] Screenshots saved to the clipboard are cleared after 5 seconds/when the notification disappears

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=419148

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

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

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

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

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

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

[kmymoney] [Bug 419113] Data displayed in scheduled transaction and home page are sometimes not consistent

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=419113

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

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

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

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

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

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

[digikam] [Bug 419771] A possible configuration for automatically scanning for new added pictures?

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419771

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
You can activate in the settings of the collections that digiKam automatically
scans external added images at runtime. The monitoring of the albums is
deactivated in the newer version via default, but can be activated again.

Maik

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

[kdenlive] [Bug 395183] recording in clip monitor always crashes kdenlive

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=395183

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=416461

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

[elisa] [Bug 408480] Albums, artists and songs view empty on first start

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=408480

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

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

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

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

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

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

[krita] [Bug 419161] I have Krita 3.1.3, whenever I try to make a new project, the program starts crashing.

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=419161

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

[kio-extras] [Bug 371278] Dolphin crashed in QList::detach() when opening smb location

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=371278

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

[Discover] [Bug 418848] Crash after installing a theme

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=418848

--- 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 419146] Dolphin crashes on split screen cut and paste

2020-04-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=419146

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

[digikam] [Bug 419744] 7.0.0-beta3 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||digikam/commit/ced318151c7b
   ||7d537147805c52d19187ff8b936
   ||a
   Version Fixed In||7.0.0
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #9 from Maik Qualmann  ---
Git commit ced318151c7b7d537147805c52d19187ff8b936a by Maik Qualmann.
Committed on 07/04/2020 at 04:23.
Pushed by mqualmann into branch 'master'.

do not reload metadata under digiKam in the Geolocation Editor
FIXED-IN: 7.0.0

M  +2-1NEWS
M  +5-2   
core/dplugins/generic/metadata/geolocationedit/dialog/geolocationedit.cpp

https://invent.kde.org/kde/digikam/commit/ced318151c7b7d537147805c52d19187ff8b936a

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

[digikam] [Bug 419744] 7.0.0-beta3 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

Maik Qualmann  changed:

   What|Removed |Added

Summary|7.0.0-beta2 Geolocation |7.0.0-beta3 Geolocation
   |Editor does not save new|Editor does not save new
   |location|location

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

[choqok] [Bug 419776] Mastodon OAuth login missing param

2020-04-06 Thread Frederick Yin
https://bugs.kde.org/show_bug.cgi?id=419776

Frederick Yin  changed:

   What|Removed |Added

 CC||fakef...@protonmail.ch

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

[choqok] [Bug 419776] New: Mastodon OAuth login missing param

2020-04-06 Thread Frederick Yin
https://bugs.kde.org/show_bug.cgi?id=419776

Bug ID: 419776
   Summary: Mastodon OAuth login missing param
   Product: choqok
   Version: 1.7.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Mastodon
  Assignee: scarp...@kde.org
  Reporter: fakef...@protonmail.ch
  Target Milestone: ---

SUMMARY
When I tried logging in, Mastodon web dumped this error message: 
```
en.doorkeeper.errors.messages.invalid_request.missing_param
```

STEPS TO REPRODUCE
1. Open choqok after a fresh install 
2. Click "yes" in the "...Would you like to add your account now?" dialog
3. `Accounts` tab -> `Add` combo button -> `Mastodon social` (which is a
misleading name)
4. Fill in `Credentials`, for example user@mastodon.technology
5. Click `Authenticate with Mastodon Service`
6. Browser launches, goes to
https://mastodon.technology/oauth/authorize?client_id_uri=urn:ietf:wg:oauth:2.0:oob_type=code=read%20write%20follow=[random
8-char str]

OBSERVED RESULT
Notice that the `client_id` param in that URL is empty. In functioning apps,
this should be some random gibberish long string. Doorkeeper, which handles
OAuth in Mastodon, refuses entry. The web interface reads
`en.doorkeeper.errors.messages.invalid_request.missing_param`, and won't let me
authorize choqok.

EXPECTED RESULT
`client_id` should contain something. Mastodon web should ask me to authorize
choqok.

SOFTWARE/OS VERSIONS
Linux: 5.6.2
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.2

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

[okular] [Bug 419673] Add a tab overview / improve tab switching

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419673

--- Comment #1 from 2wxsy5823...@opayq.com ---
Will the following patch help? It shows the document title as tooltip when one
hovers at the tab.

https://invent.kde.org/kde/okular/-/merge_requests/151

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

[kcalc] [Bug 419775] New: precedence is wrong for unary operator

2020-04-06 Thread Michael Tsang
https://bugs.kde.org/show_bug.cgi?id=419775

Bug ID: 419775
   Summary: precedence is wrong for unary operator
   Product: kcalc
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: mikl...@gmail.com
  Target Milestone: ---

SUMMARY

The calculator messes up with the precedence with unary operators in scientific
mode.

Assume that I want to calculate 1/(1/12+1/6). The expected result is 4.

STEPS TO REPRODUCE
Click the buttons below in sequence
( 1 2 1/x + 6 1/x ) 1/x

OBSERVED RESULT
The screen displays 0 after +, 0.1667 after ), and 6 after the final
1/x


EXPECTED RESULT
The screen displays 0.08333 after +, 0.25 after ), and 4 after the
final 1/x

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

ADDITIONAL INFORMATION

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

[okular] [Bug 419774] New: Allow to export PDF content as xliff for translation then reimport it

2020-04-06 Thread Thiago Sueto
https://bugs.kde.org/show_bug.cgi?id=419774

Bug ID: 419774
   Summary: Allow to export PDF content as xliff for translation
then reimport it
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: herzensch...@gmail.com
  Target Milestone: ---

This is a very specific functionality only available in two proprietary, paid,
Windows applications in the entire market as far as I know, InfixPDF and
FlexiPDF. I can easily guess it's difficult to implement.
If Okular had this functionality and it worked well, it would be the go-to
application for translators on Linux and possibly on Windows too.

The use case is fairly common for translators:
* The translator receives a PDF from a client
* The tool exports the PDF content (including information about its position)
as XLIFF, a standardized file format used for professional translation with
many translation tools
* The translator translates the XLIFF file
* The file is then reimported to the PDF
* The text is put into its original place in the PDF, even if a bit out of
place
* The translator delivers the translated PDF to the client

This is more efficient than PDF > DOCX/ODT conversion which is also common in
the translation industry, mostly because it usually does not render as many
translation issues in CAT tools such as excessive tags, so the translation
process itself is easier despite requiring PDF editing in the end.

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

[kwin] [Bug 419061] Wayland: Can't hotplug displays through docking stations

2020-04-06 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=419061

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #5 from Aleix Pol  ---
https://phabricator.kde.org/D28642

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

[systemsettings] [Bug 419773] Unable to change default application to open HTTP(S) links if only browser is deleted and another installed

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419773

--- Comment #1 from jmsharvey...@gmail.com ---
Demonstration: https://youtu.be/_w-Qw5aN0Ls

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

[systemsettings] [Bug 419773] New: Unable to change default application to open HTTP(S) links if only browser is deleted and another installed

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419773

Bug ID: 419773
   Summary: Unable to change default application to open HTTP(S)
links if only browser is deleted and another installed
   Product: systemsettings
   Version: 5.18.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jmsharvey...@gmail.com
  Target Milestone: ---

SUMMARY
If you have the default URL application set to your browser, remove it, and
install another browser, you cannot change that setting. This is the window I
am talking about: https://i.imgur.com/1RDaIAu.png


STEPS TO REPRODUCE
1. Set your (only) browser to the default application
2. Uninstall the browser
3. Install another browser

OBSERVED RESULT

Won't register that a setting has changed, meaning that you can't apply the
setting. Opening URLs will use the "in an application based on the contents of
the URL" option instead of the intended browser

EXPECTED RESULT

Able to change setting to new browser and apply. All URLs open in the browser.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Arch Linux/plasma-desktop 5.18.4.1-1
(available in About System)
KDE Plasma Version: 5.18.4.1-1
KDE Frameworks Version: 5.68.0-1
Qt Version: 5.14.2-1

ADDITIONAL INFORMATION
None

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

[marble] [Bug 411140] Example MarbleWidget will not exit when closed

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=411140

d...@kaosx.us changed:

   What|Removed |Added

 CC||d...@kaosx.us

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

[systemsettings] [Bug 419772] New: Transparency error in Fedora 32 Beta

2020-04-06 Thread Mederim
https://bugs.kde.org/show_bug.cgi?id=419772

Bug ID: 419772
   Summary: Transparency error in Fedora 32 Beta
   Product: systemsettings
   Version: 5.18.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mederimmedei...@hotmail.com
  Target Milestone: ---

Application: systemsettings5 (5.18.3)

Qt Version: 5.13.2
Frameworks Version: 5.68.0
Operating System: Linux 5.6.2-300.fc32.x86_64 x86_64
Windowing system: X11
Distribution: "Fedora release 32 (Thirty Two)"

-- Information about the crash:
- What I was doing when the application crashed: I Was in configurations, try
to put a transparency effect on in my windows, but every time i click on the
configuration of transparency, the configurations just crash and close

The crash can be reproduced every time.

-- Backtrace:
Application: Configurações do Sistema (systemsettings5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb83ef4b800 (LWP 3806))]

Thread 10 (Thread 0x7fb81507a700 (LWP 3827)):
#0  0x7fb8413e80d9 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7fb841398e2b in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7fb8413999bb in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#3  0x7fb841399bc3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fb843587fa3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fb84353b58b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fb8433b0597 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fb8426c9d89 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#8  0x7fb8433b1866 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7fb841d14432 in start_thread () from /lib64/libpthread.so.0
#10 0x7fb84303a9d3 in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7fb817fff700 (LWP 3816)):
#0  0x7fb84302fb6f in poll () from /lib64/libc.so.6
#1  0x7fb841399a8d in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#2  0x7fb841399bc3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb843587fa3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb84353b58b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb8433b0597 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb8426c9d89 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fb8433b1866 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb841d14432 in start_thread () from /lib64/libpthread.so.0
#9  0x7fb84303a9d3 in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fb81e0ed700 (LWP 3815)):
#0  0x7fb84302fb6f in poll () from /lib64/libc.so.6
#1  0x7fb841399a8d in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#2  0x7fb841399bc3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fb843587fa3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fb84353b58b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fb8433b0597 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fb8426c9d89 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fb8433b1866 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fb841d14432 in start_thread () from /lib64/libpthread.so.0
#9  0x7fb84303a9d3 in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fb81ea99700 (LWP 3813)):
#0  0x7fb841d1ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb82a514fcb in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#2  0x7fb82a514a9b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#3  0x7fb841d14432 in start_thread () from /lib64/libpthread.so.0
#4  0x7fb84303a9d3 in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fb81f29a700 (LWP 3812)):
#0  0x7fb841d1ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb82a514fcb in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#2  0x7fb82a514a9b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#3  0x7fb841d14432 in start_thread () from /lib64/libpthread.so.0
#4  0x7fb84303a9d3 in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fb828f65700 (LWP 3811)):
#0  0x7fb841d1ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fb82a514fcb in util_queue_thread_func () from
/usr/lib64/dri/iris_dri.so
#2  0x7fb82a514a9b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so
#3  0x7fb841d14432 in start_thread () from /lib64/libpthread.so.0

[okular] [Bug 419732] Can not display CJK characters with Adobe's OTF Fonts

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419732

hanyd2...@163.com changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[okular] [Bug 419732] Can not display CJK characters with Adobe's OTF Fonts

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419732

hanyd2...@163.com changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |NOT A BUG

--- Comment #8 from hanyd2...@163.com ---
(In reply to Albert Astals Cid from comment #7)
> Before doing that make sure you installed poppler-data.
> 
> Because even if pacman says
> 
> poppler-data (optional) - encoding data to display PDF documents containing
> CJK characters
> 
> It would seem to me you don't have it installed

---

Thanks! `poppler-data` helped me solve this out!

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

[frameworks-kio] [Bug 419763] Cannot log in to webdav

2020-04-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=419763

Nate Graham  changed:

   What|Removed |Added

Product|dolphin |frameworks-kio
 CC||kdelibs-b...@kde.org,
   ||n...@kde.org
   Assignee|dolphin-bugs-n...@kde.org   |fa...@kde.org
Version|19.12.3 |5.68.0
  Component|general |WebDAV

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

[digikam] [Bug 419771] New: A possible configuration for automatically scanning for new added pictures?

2020-04-06 Thread Marcus
https://bugs.kde.org/show_bug.cgi?id=419771

Bug ID: 419771
   Summary: A possible configuration for automatically scanning
for new added pictures?
   Product: digikam
   Version: 6.4.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Albums-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: wellend...@posteo.de
  Target Milestone: ---

Using digikam since version two I will soon have 100.000 pictures in my
database. If I configure digikam to scan for new pictures at the start it takes
quite a long time, some minutes actually. I deactivated the scan at the start
and as I  sometimes import photographies with rapid-photo-downloader I manually
do a scan in the used folders.

I just thought: If the scan could get limited to the last 1 (or 2,3,4,10)
folders used or for folders used in the last 1 (or 2,3,4,10...) days in the
configuration an automatic scan could cover most cases of new added pictures.
at least for my usecase it would be great!

Thank you for this great peace of software!
Marcus

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

[kwin] [Bug 419746] Firefox Developer Edition icon is incorrectly set to the one of Firefox Release

2020-04-06 Thread ariasuni
https://bugs.kde.org/show_bug.cgi?id=419746

--- Comment #2 from ariasuni  ---
Created attachment 127340
  --> https://bugs.kde.org/attachment.cgi?id=127340=edit
result of xprop for a window of Firefox Developer Edition

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

[Discover] [Bug 419770] New: Clicking away from images can break scrolling

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419770

Bug ID: 419770
   Summary: Clicking away from images can break scrolling
   Product: Discover
   Version: 5.18.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: squidin...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
I have found that sometimes, on an application page when clicking on a
screenshot to make it larger then clicking away (on any space outside the
image) you can no longer scroll down that page. it appears to happen at random
slightly over 3/4 of the time.

STEPS TO REPRODUCE
1. open discover and select random application
2. select one of the screenshots for that application 
3. click away.
4. attempt to scroll (using mouse wheel or 2 fingers on trackpad) down
application page.
5. if you can scroll down go back to step 2 and repeat

OBSERVED RESULT
scrolling (tested with laptop trackpad) doesn't work, however you can still
move down the page by clicking and dragging.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.2

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

[krita] [Bug 419769] New: i have save a short animation ;quitte krita and want i want to open my document i can't find it

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419769

Bug ID: 419769
   Summary: i have save a short animation ;quitte krita and want i
want to open my document i can't find it
   Product: krita
   Version: 4.2.8
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: andrea.paum2...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1.created a new animation project
2.name and save the result

OBSERVED RESULT
saving lost 3 hours of work are desepired

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10
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.

[skrooge] [Bug 236794] Skrooge se plante quand je quitte

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=236794

andrea.paum2...@gmail.com changed:

   What|Removed |Added

 CC||andrea.paum2...@gmail.com

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

[Falkon] [Bug 393254] importing bookmarks from firefox does not create folders

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=393254

abogi...@gmail.com changed:

   What|Removed |Added

   Assignee|now...@gmail.com|abogi...@gmail.com

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

[Falkon] [Bug 393254] importing bookmarks from firefox does not create folders

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=393254

abogi...@gmail.com changed:

   What|Removed |Added

 CC||abogi...@gmail.com

--- Comment #1 from abogi...@gmail.com ---
Patch made. Awaiting review.

https://phabricator.kde.org/D28550

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

[kwin] [Bug 417936] Crash when dragging from a window

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=417936

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/26ce4869a09e0061061c3f1e2
   ||cf2333a4ab1eb02
 Resolution|DUPLICATE   |FIXED

--- Comment #5 from David Edmundson  ---
Git commit 26ce4869a09e0061061c3f1e2cf2333a4ab1eb02 by David Edmundson.
Committed on 06/04/2020 at 22:22.
Pushed by davidedmundson into branch 'master'.

[xwl] Fix crash if same data is requested twice

Summary:
m_dataRequests is a list of transfers for a given selection.
It exists primarily as a ref counting mechanism that matches up
transfers with selections.

If the same data is requested twice we would insert two items into the
list with matching timestamps for the original selection. This then
confuses the callback handling.

Test Plan:
kwin_wayland + chromium
drag and drop a URL onto desktopview. kwin used to crash here
Now a context menu now appears and I can add a link

Reviewers: #kwin

Subscribers: kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D28630

M  +1-2xwl/drag_x.cpp

https://commits.kde.org/kwin/26ce4869a09e0061061c3f1e2cf2333a4ab1eb02

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

[frameworks-bluez-qt] [Bug 419768] New: handover from bluetooth headphone connected to plasma to mobile phone broken

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419768

Bug ID: 419768
   Summary: handover from bluetooth headphone connected to plasma
to mobile phone broken
   Product: frameworks-bluez-qt
   Version: 5.68.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: slartibar...@gmail.com
  Target Milestone: ---

Hi,
i'm using fedora31 with copr zawertun repos for plasma 5.18.4
I have a Bose QC35 II bluetooth headphone connected to plasma and my mobile
phone.
Sound playing with phone as source is fine, stopping source on phone and
playing music in plasma (headphone switches over to plasma automatically) is
fine as well.

But, stopping the plasma sound source and playing music on the phone does not
switch back to the phone.

When i open pavucontrol and set the qc35 heapdhones to 'off' in
Configuration/profile, the music starts immediately from the phone.

This worked before seamlessly, any help with this? (i don't want to use
pavucontrol to disable the headphones...)

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

[krita] [Bug 419767] New: Pixel data reference layer(s) to select from

2020-04-06 Thread Aaron Lavarnway
https://bugs.kde.org/show_bug.cgi?id=419767

Bug ID: 419767
   Summary: Pixel data reference layer(s) to select from
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@ralek.art
  Target Milestone: ---

I work on pretty complicated scenes, sometimes with several hundred layers.
Since the only way to get the magic wand selector working correctly in my
environment is to hide all layers besides the lineart and a plain white
background, you can imagine how this can be extremely cumbersome.

It would be nice if you could check a box on a layer to mark it as a 'selection
reference' layer or similar, and in the magic wand/similar color/magnetic wand
selector tools have an option to 'limit to reference layer(s)'

if only one layer would be allowed at a time that would be a nice start, but if
multiple could be chosen that would make it even better.
Or even better, integrate it into the layer colors. No new UI needed, just have
it only reference layers with a certain color assigned to them.

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

[krita] [Bug 419766] New: Magic wand doesn't take into account alpha channel with the threshold

2020-04-06 Thread Aaron Lavarnway
https://bugs.kde.org/show_bug.cgi?id=419766

Bug ID: 419766
   Summary: Magic wand doesn't take into account alpha channel
with the threshold
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@ralek.art
  Target Milestone: ---

When using the magic wand tool, alpha channel is not calculated with the
threshold. This means if you try to select the inside of a transparently filled
circle, there will always be a gap where the semi-transparent anti-aliased
pixels do not get selected. This makes the magic wand tool useless with basic
lineart layers.
Expansion will not work as a solution for all lineart shapes.




Krita
  Version: 4.3.0-prealpha (git 44d8e02)

Qt
  Version (compiled): 5.12.7
  Version (loaded): 5.12.7

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.17134
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

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

[plasmashell] [Bug 417604] Scrolling direction inverted in some Plasma scrollviews

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=417604

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #7 from David Edmundson  ---
Debugged this a bit.

It seems Qt in QtWayland inverts the angle delta, but not the pixel delta.
This doesn't make much sense.

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

[Powerdevil] [Bug 419749] crash on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419749

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
   Keywords|drkonqi |wayland
 Ever confirmed|0   |1
 CC||k...@davidedmundson.co.uk

--- Comment #3 from David Edmundson  ---
Reproduced

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

[systemsettings] [Bug 419765] New: "None" icon looks pixelated

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419765

Bug ID: 419765
   Summary: "None" icon looks pixelated
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_splashscreen
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. open system settings > Startup and shutdown > Splash screen
2. 
3. 

OBSERVED RESULT
"None" icon looks pixelated. See the attached screenshot please.

EXPECTED RESULT
None" icon should be crisp

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

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

[systemsettings] [Bug 419765] "None" icon looks pixelated

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419765

--- Comment #1 from Patrick Silva  ---
Created attachment 127339
  --> https://bugs.kde.org/attachment.cgi?id=127339=edit
screenshot

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

[systemsettings] [Bug 419764] OSD to set multi-monitor mode should ignore all tiling shortcuts

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419764

Patrick Silva  changed:

   What|Removed |Added

 CC||plasma-b...@kde.org
Product|kwin|systemsettings
   Assignee|kwin-bugs-n...@kde.org  |kscreen-bugs-n...@kde.org
Version|git master  |unspecified
  Component|general |kcm_kscreen

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

[kwin] [Bug 419764] New: OSD to set multi-monitor mode should ignore all tiling shortcuts

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419764

Bug ID: 419764
   Summary: OSD to set multi-monitor mode should ignore all tiling
shortcuts
   Product: kwin
   Version: git master
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Created attachment 127338
  --> https://bugs.kde.org/attachment.cgi?id=127338=edit
screen recording

SUMMARY
As we can see in the attached screen recording, currently the OSD to set
multi-monitor mode is tiled when we press mete+any arrow. This OSD should
ignore all tiling shortcuts.

STEPS TO REPRODUCE
1. press meta+p
2. press meta+any arrow
3. 

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
Also reproducible with Plasma 5.18.4 on Arch Linux.

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

[frameworks-kirigami] [Bug 419514] Discover, Connections kcm and System Tray settings have unnecessary horizontal scroll bar after update to Qt 5.14.2

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419514

Patrick Silva  changed:

   What|Removed |Added

Summary|Discover and Connections|Discover, Connections kcm
   |kcm have unnecessary|and System Tray settings
   |horizontal scroll bar after |have unnecessary horizontal
   |update to Qt 5.14.2 |scroll bar after update to
   ||Qt 5.14.2

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

[okular] [Bug 419431] Images pasted into PDF document using Adobe Acrobat Reader DC do not display properly on screen.

2020-04-06 Thread Richard Ferguson
https://bugs.kde.org/show_bug.cgi?id=419431

--- Comment #15 from Richard Ferguson  ---
I get that and have been on the verge of Linux.  Just not enough pain yet
with Windows to push me over the edge, but there have been some close calls.

On Mon, Apr 6, 2020 at 2:08 PM Albert Astals Cid 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=419431
>
> Albert Astals Cid  changed:
>
>What|Removed |Added
>
> 
>  Resolution|WAITINGFORINFO  |---
>  Status|NEEDSINFO   |REPORTED
>
> --- Comment #14 from Albert Astals Cid  ---
> I'm sorry but I am not that interested in Windows myself. Maybe someone at
> kde-windows mailing list is.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[Akonadi] [Bug 419726] trying to change POP3 resource crashes

2020-04-06 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=419726

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Works fine here, can you run under valgrind to see if you get any interesting
log?

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

[okular] [Bug 419431] Images pasted into PDF document using Adobe Acrobat Reader DC do not display properly on screen.

2020-04-06 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=419431

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #14 from Albert Astals Cid  ---
I'm sorry but I am not that interested in Windows myself. Maybe someone at
kde-windows mailing list is.

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

[okular] [Bug 419447] Search does not match any accented character (diacritics)

2020-04-06 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=419447

--- Comment #10 from Albert Astals Cid  ---
(In reply to Jerome from comment #8)
> The PDF is generated by pdflatex.

I know latex has too many configuration options and one stupidly does it wrong,
search because there's one that does it right and writes a single character. 

> 
> I still think that is a bug, because one way I can start such a search is by
> copying accented characters from the document and pasting them into the
> search box. I don't know if that is one or two characters but whatever that
> string is in the PDF, I'd like to search for it.
> 
> > I have not been able to find any PDF viewer that can search à in this 
> > document
> 
> I have. It was the first one I tried: evince.

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

[Powerdevil] [Bug 419749] crash on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419749

--- Comment #2 from David Edmundson  ---
*** Bug 419761 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 419761] DiscoverNotifier crashed on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419761

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED

--- Comment #1 from David Edmundson  ---


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

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

[kactivitymanagerd] [Bug 419762] kactivitymanagerd crashed on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419762

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from David Edmundson  ---
It's in QtWayland, lets just have the one bug report

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

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

[Powerdevil] [Bug 419749] crash on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419749

--- Comment #1 from David Edmundson  ---
*** Bug 419762 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 419732] Can not display CJK characters with Adobe's OTF Fonts

2020-04-06 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=419732

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #7 from Albert Astals Cid  ---
Before doing that make sure you installed poppler-data.

Because even if pacman says

poppler-data (optional) - encoding data to display PDF documents containing CJK
characters

It would seem to me you don't have it installed

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

[digikam] [Bug 419744] 7.0.0-beta2 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #8 from Maik Qualmann  ---
Hmm, regardless of the database cleanup option, I can now actually reproduce a
problem when updating the database. I'll take a closer look at it tomorrow.

Maik

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

[kwin] [Bug 419746] Firefox Developer Edition icon is incorrectly set to the one of Firefox Release

2020-04-06 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=419746

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||k...@davidedmundson.co.uk
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from David Edmundson  ---
Please attach output of 
"xprop" and clicking on the firefox dev edition window

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

[dolphin] [Bug 419763] New: Cannot log in to webdav

2020-04-06 Thread DaCoEx
https://bugs.kde.org/show_bug.cgi?id=419763

Bug ID: 419763
   Summary: Cannot log in to webdav
   Product: dolphin
   Version: 19.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: dac...@public-files.de
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
Opening a remote webdav folder is not possible.
I followed the instructions for my remote server here:
https://kb.mailbox.org/display/MBOKBEN/WebDav+for+Linux?beecom.language=en

STEPS TO REPRODUCE
1. Open Dolphin
2. Go to network section (left side) & select webdav
3. Enter the URL (dav.mailbox.org)

OBSERVED RESULT
* On first time entering the details, the dialogue ask for the credentials
* The program tries to connect
* the folder is displayed as empty = no content
* meanwhile, if I log in via the provider's web interface, there is content


EXPECTED RESULT
Remote webdav folder with the contents.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-21-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz
Memory: 15,5 GiB of RAM


ADDITIONAL INFORMATION
System:
lsb_release --all
Description:Ubuntu Focal Fossa (development branch)

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

[plasmashell] [Bug 418411] [Wayland] Cursor appears as a black box.

2020-04-06 Thread Stefan K.
https://bugs.kde.org/show_bug.cgi?id=418411

--- Comment #5 from Stefan K.  ---
Hmm, I am unsure if it might be helpful.

I booted my system with the distribution kernel (4.15.0-70-generic) for some
reason and it made a difference. Though the changes (in the graphics subsystem)
to the current kernel could be too huge to help triage this bug.

The cursor is always rendered correctly.

If you switch from a Xwayland window to a native one it is in the foreground
but "inactive" (no focus).

If you switch from native window to XWayland it gets "active" (focus) as
expected.

If you do not cross the window protocol everything is okay.


(I updated KDE from .3 to 5.18.4 yesterday. I suppose this is not the
cause...?)

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

[Powerdevil] [Bug 419749] crash on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419749

Patrick Silva  changed:

   What|Removed |Added

Summary|crash when I swtiched to|crash on Wayland when I
   |"Extend to left"|swtiched to "Extend to
   |multi-monitor mode  |left" multi-monitor mode

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

[kactivitymanagerd] [Bug 419762] New: kactivitymanagerd crashed on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419762

Bug ID: 419762
   Summary: kactivitymanagerd crashed on Wayland when I swtiched
to "Extend to left" multi-monitor mode
   Product: kactivitymanagerd
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: bugsefor...@gmx.com
CC: plasma-b...@kde.org
  Target Milestone: ---

I was using Wayland session with an external monitor connected to hdmi port,
then I switched from "Swith to external monitor" to "Extend to left"
multi-monitor mode and plasma shown 4 crash notifications at the same time:
power devil, discover notifier, policykit kde agent and this one.

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

Application: kactivitymanagerd (kactivitymanagerd), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f7d3015cc80
(LWP 1206))]
[KCrash Handler]
#7  QtWayland::wl_output::handle_geometry (data=0x55796b555c30,
object=0x55796b555cd0, x=1920, y=0, physical_width=310, physical_height=170,
subpixel=0, make=0x55796b569e20 "LG Display", model=0x55796b569e30
"LVDS-1-desconhecido", transform=0) at qwayland-wayland.cpp:2212
#8  0x7f7d24d4bdae in ffi_call_unix64 () from
/usr/lib/x86_64-linux-gnu/libffi.so.6
#9  0x7f7d24d4b71f in ffi_call () from
/usr/lib/x86_64-linux-gnu/libffi.so.6
#10 0x7f7d253dae24 in wl_closure_invoke
(closure=closure@entry=0x55796b569d30, flags=flags@entry=1, target=, target@entry=0x55796b555cd0, opcode=opcode@entry=0, data=)
at ../src/connection.c:1006
#11 0x7f7d253d7659 in dispatch_event (display=display@entry=0x55796b54e560,
queue=) at ../src/wayland-client.c:1427
#12 0x7f7d253d8b24 in dispatch_queue (queue=0x55796b54e628,
display=0x55796b54e560) at ../src/wayland-client.c:1573
#13 wl_display_dispatch_queue_pending (display=0x55796b54e560,
queue=0x55796b54e628) at ../src/wayland-client.c:1815
#14 0x7f7d253d8b7c in wl_display_dispatch_pending (display=)
at ../src/wayland-client.c:1878
#15 0x7f7d2584f642 in QtWaylandClient::QWaylandDisplay::flushRequests
(this=0x55796b54e3c0) at qwaylanddisplay.cpp:208
#16 0x7f7d2d75edc9 in doActivate (sender=0x55796b57aec0,
signal_index=3, argv=0x7ffd02fd6e90) at kernel/qobject.cpp:3882
#17 0x7f7d2d7598a2 in QMetaObject::activate
(sender=sender@entry=0x55796b57aec0, m=m@entry=0x7f7d2dbf1bc0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd02fd6e90)
at kernel/qobject.cpp:3930
#18 0x7f7d2d7625c8 in QSocketNotifier::activated
(this=this@entry=0x55796b57aec0, _t1=, _t2=...) at
.moc/moc_qsocketnotifier.cpp:141
#19 0x7f7d2d762982 in QSocketNotifier::event (this=0x55796b57aec0,
e=0x7ffd02fd7160) at kernel/qsocketnotifier.cpp:266
#20 0x7f7d2eda28bc in QApplicationPrivate::notify_helper
(this=this@entry=0x55796b5456e0, receiver=receiver@entry=0x55796b57aec0,
e=e@entry=0x7ffd02fd7160) at kernel/qapplication.cpp:3684
#21 0x7f7d2eda9ac0 in QApplication::notify (this=0x7ffd02fd73f0,
receiver=0x55796b57aec0, e=0x7ffd02fd7160) at kernel/qapplication.cpp:3430
#22 0x7f7d2d723db8 in QCoreApplication::notifyInternal2
(receiver=0x55796b57aec0, event=0x7ffd02fd7160) at
kernel/qcoreapplication.cpp:1092
#23 0x7f7d2d723f8e in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7ffd02fd7160) at kernel/qcoreapplication.cpp:1487
#24 0x7f7d2d783c88 in socketNotifierSourceDispatch (source=0x55796b5ac7f0)
at kernel/qeventdispatcher_glib.cpp:107
#25 0x7f7d29c4c417 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f7d29c4c650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f7d29c4c6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f7d2d7830bc in QEventDispatcherGlib::processEvents
(this=0x55796b55d270, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7f7d2d72263a in QEventLoop::exec (this=this@entry=0x7ffd02fd7380,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#30 0x7f7d2d72bdb0 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1400
#31 0x55796af0bc95 in ?? ()
#32 0x7f7d2cd29b97 in __libc_start_main (main=0x55796af0bbf0, argc=1,
argv=0x7ffd02fd7528, init=, fini=,
rtld_fini=, stack_end=0x7ffd02fd7518) at ../csu/libc-start.c:310
#33 0x55796af0bd8a in _start ()

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

[Discover] [Bug 419761] DiscoverNotifier crashed on Wayland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419761

Patrick Silva  changed:

   What|Removed |Added

Summary|DiscoverNotifier crashed on |DiscoverNotifier crashed on
   |Waland when I swtiched to   |Wayland when I swtiched to
   |"Extend to left"|"Extend to left"
   |multi-monitor mode  |multi-monitor mode

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

[Discover] [Bug 419761] DiscoverNotifier crashed on Waland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419761

Patrick Silva  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[Discover] [Bug 419761] New: DiscoverNotifier crashed on Waland when I swtiched to "Extend to left" multi-monitor mode

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419761

Bug ID: 419761
   Summary: DiscoverNotifier crashed on Waland when I swtiched to
"Extend to left" multi-monitor mode
   Product: Discover
   Version: 5.18.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifier
  Assignee: aleix...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

SUMMARY
I was using Wayland session with an external monitor connected to hdmi port,
then I switched from "Swith to external monitor" to "Extend to left"
multi-monitor mode and plasma shown 4 crash notifications at the same time:
power devil, kactivitymanagerd, policykit kde agent and this one.

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1


Thread 6 (Thread 0x7f38b0178700 (LWP 1494)):
#0  0x7f38cea45c96 in __libc_send (fd=fd@entry=5,
buf=buf@entry=0x7f38b0176e60, len=len@entry=32, flags=flags@entry=0)
at ../sysdeps/unix/sysv/linux/send.c:28
#1  0x7f38d13fc381 in (anonymous
namespace)::ProcessNetlinkRequest >::operator() (bufsize=8192,
this=, func=..., buf=0x7f38a8011038 "\024", hdr=0x7f38b0176e60,
sock=5) at kernel/qnetworkinterface_linux.cpp:163
#2  0x7f38d13fc381 in (anonymous
namespace)::processNetlinkRequest > (l=..., bufsize=8192, buf=0x7f38a8011038
"\024", hdr=0x7f38b0176e60, sock=5) at kernel/qnetworkinterface_linux.cpp:218
#3  0x7f38d13fc381 in getInterfaces (buf=0x7f38a8011038 "\024", sock=5) at
kernel/qnetworkinterface_linux.cpp:274
#4  0x7f38d13fc381 in QNetworkInterfaceManager::scan() (this=) at kernel/qnetworkinterface_linux.cpp:446
#5  0x7f38d13edc35 in QNetworkInterfaceManager::allInterfaces()
(this=) at kernel/qnetworkinterface.cpp:118
#6  0x7f38d13ee484 in QNetworkInterface::allInterfaces() () at
kernel/qnetworkinterface.cpp:876
#7  0x7f38af532986 in QGenericEngine::doRequestUpdate()
(this=0x55c49fae58c0) at qgenericengine.cpp:286
#8  0x7f38cf350b06 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const
(this=this@entry=0x7f38b0177430, object=object@entry=0x55c49fae58c0,
connectionType=Qt::DirectConnection, 
connectionType@entry=Qt::AutoConnection, returnValue=..., val0=...,
val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=...,
val9=...) at kernel/qmetaobject.cpp:2294
#9  0x7f38cf3529f8 in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument)
(obj=0x55c49fae58c0, member=member@entry=0x7f38d1479f25 "requestUpdate",
type=type@entry=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=...,
val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at
kernel/qmetaobject.cpp:1515
#10 0x7f38d13da74b in QMetaObject::invokeMethod(QObject*, char const*,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument) (val9=..., val8=..., val7=..., val6=...,
val5=..., val4=..., val3=..., val2=..., val1=..., val0=...,
member=0x7f38d1479f25 "requestUpdate", obj=)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:461
#11 0x7f38d13da74b in QNetworkConfigurationManagerPrivate::pollEngines()
(this=0x55c49fac21f0) at bearer/qnetworkconfigmanager_p.cpp:493
#12 0x7f38d146e585 in
QNetworkConfigurationManagerPrivate::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=) at
.moc/moc_qnetworkconfigmanager_p.cpp:132
#13 0x7f38cf379dc9 in doActivate(QObject*, int, void**)
(sender=0x7f38a8010590, signal_index=3, argv=0x7f38b01779e0)
at kernel/qobject.cpp:3882
#14 0x7f38cf3748a2 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x7f38a8010590, m=m@entry=0x7f38cf80cd00
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7f38b01779e0) at kernel/qobject.cpp:3930
#15 0x7f38cf37dba7 in QTimer::timeout(QTimer::QPrivateSignal)
(this=this@entry=0x7f38a8010590, _t1=...) at .moc/moc_qtimer.cpp:205
#16 0x7f38cf37df08 in QTimer::timerEvent(QTimerEvent*)
(this=0x7f38a8010590, e=) at kernel/qtimer.cpp:257
#17 0x7f38cf371df3 in QObject::event(QEvent*) (this=0x7f38a8010590,
e=0x7f38b0177b50) at kernel/qobject.cpp:1361
#18 0x7f38cf33eda1 in doNotify (event=0x7f38b0177b50,
receiver=0x7f38a8010590) at kernel/qcoreapplication.cpp:1182
#19 

[digikam] [Bug 416470] Suggestion: Make Album TreeView more explorer like

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=416470

--- Comment #6 from Maik Qualmann  ---
No, this option has not yet made it into the GUI.

Maik

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

[kwin] [Bug 419760] frame rate drops if blur and transparency effects are enabled, blur background is enabled in Konsole and Konsole window is maximized

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419760

--- Comment #1 from Patrick Silva  ---
Created attachment 127336
  --> https://bugs.kde.org/attachment.cgi?id=127336=edit
frame rate when Konsole is maximized

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

[kwin] [Bug 419760] frame rate drops if blur and transparency effects are enabled, blur background is enabled in Konsole and Konsole window is maximized

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419760

Patrick Silva  changed:

   What|Removed |Added

Version|git master  |5.18.4
   Platform|Other   |Archlinux Packages

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

[digikam] [Bug 419744] 7.0.0-beta2 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #7 from Maik Qualmann  ---
It is the option to clean up the database, this will write the content of the
metadata in the image back into the database. And we have the old position.
This option was not intended to be activated permanently, I tend to deactivated
this option for every new digiKam session.

Maik

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

[kwin] [Bug 419760] New: frame rate drops to 30fps if blur and transparency effects are enabled, blur background is enabled in Konsole and Konsole window is maximized

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419760

Bug ID: 419760
   Summary: frame rate drops to 30fps if blur and transparency
effects are enabled, blur background is enabled in
Konsole and Konsole window is maximized
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Created attachment 127335
  --> https://bugs.kde.org/attachment.cgi?id=127335=edit
frame rate when Konsole is not maximized

SUMMARY
This issue affects both X11 and Wayland sessions.
On X11, frame rate drops from 60 to 45 fps, on Wayland from 60 to 30 fps.

STEPS TO REPRODUCE
1. enable transparency and blur effects
2. enable blur in Konsole settings (right-click > edit current profile >
"appearance" section.
Click on "Edit" button, check "Blur background", click "Ok" button, click on
"Ok" button again
3.  maximize Konsole window

OBSERVED RESULT
frame rate drops. Compare the screenshots taken on Wayland when Konsole is not
maximized and when it is maximized.

EXPECTED RESULT
frame rate should not drop after the steps above

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.15.0 beta3

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

[kwin] [Bug 419760] frame rate drops if blur and transparency effects are enabled, blur background is enabled in Konsole and Konsole window is maximized

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419760

Patrick Silva  changed:

   What|Removed |Added

Summary|frame rate drops to 30fps   |frame rate drops if blur
   |if blur and transparency|and transparency effects
   |effects are enabled, blur   |are enabled, blur
   |background is enabled in|background is enabled in
   |Konsole and Konsole window  |Konsole and Konsole window
   |is maximized|is maximized

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

[digikam] [Bug 419744] 7.0.0-beta2 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #6 from Maik Qualmann  ---
What are your metadata settings exactly? Reread the metadata  on change? Clean
up the database when reading again? Sidecar? Collection monitoring for external
changes active?

Maik

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

[digikam] [Bug 416470] Suggestion: Make Album TreeView more explorer like

2020-04-06 Thread hmueller
https://bugs.kde.org/show_bug.cgi?id=416470

--- Comment #5 from hmueller  ---
Just wanted to know, if the new configuration option is in the code meanwhile.
Hope this still gets added for 7.0.0 ...
Thanks
Holger

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

[digikam] [Bug 419744] 7.0.0-beta2 Geolocation Editor does not save new location

2020-04-06 Thread hmueller
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #5 from hmueller  ---
I reinstalled the latest version and I see the new option setting for
geolocation information (GPS). If I set this option, new position is updated
(to database and image). If I do not set this option it is again not written to
image AND not to database (on Mac OSX)! It remains on the old position.

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

[digikam] [Bug 419744] 7.0.0-beta2 Geolocation Editor does not save new location

2020-04-06 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #4 from Maik Qualmann  ---
I have just tested it again, it works as expected, even without an active write
option, the new position is taken because the geolocation data is always
written to the database. The metadata will of course remain unchanged in the
image. If you read the metadata again, you will have the old coordinates again.

Maik

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

[kwin] [Bug 419759] Set multi-monitor mode to "Unify outputs", disconnect external monitor, turn it off and reconnect it: kwin_wayland crashes.

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419759

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

Thread 11 (Thread 1092.1147):
#0  0x7f60c3d8b9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f60c1953fb8 )
at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f60c1953f68
, cond=0x7f60c1953f90
)
at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=cond@entry=0x7f60c1953f90
, mutex=mutex@entry=0x7f60c1953f68
)
at pthread_cond_wait.c:655
#3  0x7f60c165e944 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f60c1945ec0 )
at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#4  0x7f60c165e989 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#5  0x7f60c3d856db in start_thread (arg=0x7f60767fc700) at
pthread_create.c:463
#6  0x7f60c1d9588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 1092.1146):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f60c26cad44 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=, op=0, addr=) at thread/qfutex_p.h:116
#2  QtLinuxFutex::futexWait >
(expectedValue=, futex=...) at thread/qfutex_p.h:135
#3  futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593,
curValue=, u=...) at thread/qsemaphore.cpp:219
#4  futexSemaphoreTryAcquire (timeout=-1, n=n@entry=1, u=...) at
thread/qsemaphore.cpp:262
#5  QSemaphore::acquire (this=this@entry=0x555d001b6050, n=n@entry=1) at
thread/qsemaphore.cpp:326
#6  0x7f60abf22d7a in QtVirtualKeyboard::HunspellWorker::run
(this=0x555d001b6030) at hunspellworker.cpp:744
#7  0x7f60c26c87ec in QThreadPrivate::start (arg=0x555d001b6030) at
thread/qthread_unix.cpp:342
#8  0x7f60c3d856db in start_thread (arg=0x7f6076ffd700) at
pthread_create.c:463
#9  0x7f60c1d9588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 1092.1144):
#0  0x7f60c3d8b9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x555cffefcb20) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x555cffefcad0,
cond=0x555cffefcaf8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=cond@entry=0x555cffefcaf8,
mutex=mutex@entry=0x555cffefcad0) at pthread_cond_wait.c:655
#3  0x7f60c26ced9b in QWaitConditionPrivate::wait (deadline=...,
this=0x555cffefcad0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x555cffefc938,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f60c26cef19 in QWaitCondition::wait (this=this@entry=0x555cffefc940,
mutex=mutex@entry=0x555cffefc938, time=time@entry=18446744073709551615)
at thread/qwaitcondition_unix.cpp:208
#6  0x7f607d6de8eb in FileInfoThread::run (this=0x555cffefc928) at
fileinfothread.cpp:231
#7  0x7f60c26c87ec in QThreadPrivate::start (arg=0x555cffefc928) at
thread/qthread_unix.cpp:342
#8  0x7f60c3d856db in start_thread (arg=0x7f6077fff700) at
pthread_create.c:463
#9  0x7f60c1d9588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 1092.1143):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f60c26cad44 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=, op=0, addr=) at thread/qfutex_p.h:116
#2  QtLinuxFutex::futexWait >
(expectedValue=, futex=...) at thread/qfutex_p.h:135
#3  futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593,
curValue=, u=...) at thread/qsemaphore.cpp:219
#4  futexSemaphoreTryAcquire (timeout=-1, n=n@entry=1, u=...) at
thread/qsemaphore.cpp:262
#5  QSemaphore::acquire (this=this@entry=0x555d005e9fc0, n=n@entry=1) at
thread/qsemaphore.cpp:326
#6  0x7f60abf22d7a in QtVirtualKeyboard::HunspellWorker::run
(this=0x555d005e9fa0) at hunspellworker.cpp:744
#7  0x7f60c26c87ec in QThreadPrivate::start (arg=0x555d005e9fa0) at
thread/qthread_unix.cpp:342
#8  0x7f60c3d856db in start_thread (arg=0x7f607cab6700) at
pthread_create.c:463
#9  0x7f60c1d9588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 1092.1142):
#0  0x7f60c1d88bf9 in __GI___poll (fds=0x7f60800029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f60b916a5c9 in ?? () from
target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f60b916a6dc in g_main_context_iteration () from
target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f60c29170bc in QEventDispatcherGlib::processEvents
(this=0x7f608b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x7f60c28b663a in QEventLoop::exec (this=this@entry=0x7f6088f8bd80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7f60c26c7317 in QThread::exec (this=this@entry=0x555d0005b510) at
thread/qthread.cpp:536
#6  0x7f60bdabc605 in QQmlThreadPrivate::run (this=0x555d0005b510) at
qml/ftw/qqmlthread.cpp:155
#7  0x7f60c26c87ec in 

[kwin] [Bug 419759] New: Set multi-monitor mode to "Unify outputs", disconnect external monitor, turn it off and reconnect it: kwin_wayland crashes.

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419759

Bug ID: 419759
   Summary: Set multi-monitor mode to "Unify outputs", disconnect
external monitor, turn it off and reconnect it:
kwin_wayland crashes.
   Product: kwin
   Version: git master
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. start Wayland session
2. connect an external monitor to hdmi port and turn it on
3. set multi-monitor mode to "Unify outputs"
4. disconnect the hdmi cable from hdmi port
5. turn off the external monitor by pressing its physical on/off button
6. reconnect the external monitor to hdmi port

OBSERVED RESULT
kwin_wayland crashes

EXPECTED RESULT
no crash

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1

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

[digikam] [Bug 419744] 7.0.0-beta2 Geolocation Editor does not save new location

2020-04-06 Thread hmueller
https://bugs.kde.org/show_bug.cgi?id=419744

--- Comment #3 from hmueller  ---
Maybe it is not written to the metadata, but the new location is completely
lost. If you close the geo editor the image in right map view is at it's old
location. I will try the new setting option. Have to reinstall the latest
version ... will send an update after that.

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

[krita] [Bug 419758] New: Using transform tool on a vector layer causes the layer to appear invisible.

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419758

Bug ID: 419758
   Summary: Using transform tool on a vector layer causes the
layer to appear invisible.
   Product: krita
   Version: unspecified
  Platform: Other
OS: Windows CE
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Layers/Vector
  Assignee: krita-bugs-n...@kde.org
  Reporter: kirb...@hotmail.com
  Target Milestone: ---

SUMMARY
Using transform tool on a vector layer causes the layer to appear invisible.

STEPS TO REPRODUCE
1. Attempted to use liquify tool.
2. Pressing "apply" causes the layer to disappear.
3. Any other transformation does the same.

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 419757] New: Laptop HDMI screen can't keep as primary screen.

2020-04-06 Thread Leonardo
https://bugs.kde.org/show_bug.cgi?id=419757

Bug ID: 419757
   Summary: Laptop HDMI screen can't keep as primary screen.
   Product: plasmashell
   Version: 5.18.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: leonei...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Using a second HDMI screen the KDE plasma can't remember the main screen after
some actions.

STEPS TO REPRODUCE
1. Connect a HDMI screen to the Notebook and set to use both screens to
extended.
2. Open Screen configuration manager
3. Clck on HDMI screen image so select it.
4. Check primary/main checkbox.
5. Now the HDMI is working as primary screen and the "notebook screen" as
secondary.
6. ...
6. Now using the keyboard shortcut(fn) select to use only one screen(any one). 
7. Now again with fn shortcut set to use both screens to extended.

OBSERVED RESULT
The primary/main screen is not the HDMI screen previouly configured.
It is like plasma had lost the configuration.

EXPECTED RESULT
Plasma should remember the primary screen always.
One time the HDMI screen is the primary it should be every time we turn on the
laptop or connect the screen.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.18
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1
Kernel Version: 5.3.0-42-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7,7 GiB

ADDITIONAL INFORMATION

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

[Powerdevil] [Bug 419756] New: crash when I tried to set "Unify outputs" multi-monitor mode on Wayland

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419756

Bug ID: 419756
   Summary: crash when I tried to set "Unify outputs"
multi-monitor mode on Wayland
   Product: Powerdevil
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

Application: org_kde_powerdevil (2.0.0)

Qt Version: 5.14.1
Frameworks Version: 5.69.0
Operating System: Linux 5.3.0-45-generic x86_64
Windowing system: Wayland
Distribution: KDE neon Unstable Edition

-- Information about the crash:
- What I was doing when the application crashed:
I was using Wayland session with an external monitor connected to hdmi port.
I tried to set monitor mode to "Unify outputs" mode then Plasma shown
notification about powerdevil crash.
kded5 and DiscoverNotifier also crashed at the same time.

-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal:
Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fad72e9bc80
(LWP 1222))]
[KCrash Handler]
#7  0x0041 in  ()
#8  0x7fad62711dae in ffi_call_unix64 () at
/usr/lib/x86_64-linux-gnu/libffi.so.6
#9  0x7fad6271171f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#10 0x7fad62da0e24 in wl_closure_invoke
(closure=closure@entry=0x7fad5000b0a0, flags=flags@entry=1, target=, target@entry=0x561bbaed5380, opcode=opcode@entry=1, data=)
at ../src/connection.c:1006
#11 0x7fad62d9d659 in dispatch_event (display=display@entry=0x561bbae33b50,
queue=) at ../src/wayland-client.c:1427
#12 0x7fad62d9eb24 in dispatch_queue (queue=0x561bbae33c18,
display=0x561bbae33b50) at ../src/wayland-client.c:1573
#13 0x7fad62d9eb24 in wl_display_dispatch_queue_pending
(display=0x561bbae33b50, queue=0x561bbae33c18) at ../src/wayland-client.c:1815
#14 0x7fad62d9eb7c in wl_display_dispatch_pending (display=)
at ../src/wayland-client.c:1878
#15 0x7fad63215642 in QtWaylandClient::QWaylandDisplay::flushRequests()
(this=0x561bbae339b0) at qwaylanddisplay.cpp:208
#16 0x7fad7024bdc9 in doActivate(QObject*, int, void**)
(sender=0x561bbae8d0d0, signal_index=3, argv=0x7ffc50ab7ee0) at
kernel/qobject.cpp:3882
#17 0x7fad702468a2 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x561bbae8d0d0, m=m@entry=0x7fad706debc0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc50ab7ee0)
at kernel/qobject.cpp:3930
#18 0x7fad7024f5c8 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x561bbae8d0d0,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#19 0x7fad7024f982 in QSocketNotifier::event(QEvent*) (this=0x561bbae8d0d0,
e=0x7ffc50ab7fc0) at kernel/qsocketnotifier.cpp:266
#20 0x7fad70210db8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x561bbae8d0d0, event=0x7ffc50ab7fc0) at
kernel/qcoreapplication.cpp:1092
#21 0x7fad70210f8e in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=event@entry=0x7ffc50ab7fc0) at
kernel/qcoreapplication.cpp:1487
#22 0x7fad70270c88 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x561bbae91730) at kernel/qeventdispatcher_glib.cpp:107
#23 0x7fad6a8f7417 in g_main_context_dispatch () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fad6a8f7650 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fad6a8f76dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7fad702700bc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x561bbae421b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#27 0x7fad7020f63a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffc50ab81e0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:225
#28 0x7fad70218db0 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1400
#29 0x561bba2547ff in  ()
#30 0x7fad6f816b97 in __libc_start_main (main=0x561bba254640, argc=1,
argv=0x7ffc50ab83d8, init=, fini=,
rtld_fini=, stack_end=0x7ffc50ab83c8) at ../csu/libc-start.c:310
#31 0x561bba25486a in _start ()

Possible duplicates by query: bug 419749, bug 391109, bug 386166, bug 377347,
bug 377346.

Reported using DrKonqi

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

[Falkon] [Bug 419755] New: Firefox sync support in falkon

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=419755

Bug ID: 419755
   Summary: Firefox sync support in falkon
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: sk.griffi...@gmail.com
  Target Milestone: ---

SUMMARY
A sync service is very handy in case one owns multiple devices. Instead of
developing a completely new service, it is possible to use existing solutions,
such as firefox sync. If it is also capable of syncing between falkon, firefox
desktop and firefox android (especially firefox android), it will be much more
useful.

ADDITIONAL INFORMATION
Eolie browser  has a working implementation
of firefox sync. It is available via additional optional packages, so anyone
not willing to to have it should have no problem. Also hopefully, optional
packages will also not cause any licence issues

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

[plasmashell] [Bug 419754] New: Plasma crashed on Wayland after I connect an external monitor to hdmi port while I was using a tty

2020-04-06 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=419754

Bug ID: 419754
   Summary: Plasma crashed on Wayland after I connect an external
monitor to hdmi port while I was using a tty
   Product: plasmashell
   Version: master
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugsefor...@gmx.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.18.80)

Qt Version: 5.14.1
Frameworks Version: 5.69.0
Operating System: Linux 5.3.0-45-generic x86_64
Windowing system: Wayland
Distribution: KDE neon Unstable Edition

-- Information about the crash:
- What I was doing when the application crashed:
start Wayland session
switch to  tty
do login with the same usr account used to start Plasma session
connect an external monitor to hdmi port
go back to Plasma session
Result: only cursor is visible, plasma crashed

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fcb1f578c80
(LWP 1188))]
[KCrash Handler]
#7  0x7fcb0c964dc0 in QtWaylandClient::QWaylandWindow::setVisible(bool)
(this=this@entry=0x562a9c8368d0, visible=) at
qwaylandwindow.cpp:423
#8  0x7fcb01c6b5f4 in QtWaylandClient::QWaylandEglWindow::setVisible(bool)
(this=0x562a9c8368d0, visible=) at
../../../../hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:167
#9  0x7fcb19b69dc3 in QWindowPrivate::setVisible(bool)
(this=0x562a988498d0, visible=) at kernel/qwindow.cpp:408
#10 0x562a95adfa13 in ShellCorona::addOutput(QScreen*)
(this=0x562a96e7d130, screen=) at ./shell/shellcorona.cpp:1311
#11 0x7fcb1959dfe7 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffe9a2426e0, r=0x562a96e7d130, this=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#12 0x7fcb1959dfe7 in doActivate(QObject*, int, void**)
(sender=0x7ffe9a242e20, signal_index=9, argv=0x7ffe9a2426e0) at
kernel/qobject.cpp:3870
#13 0x7fcb195988a2 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7fcb1a2d35a0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe9a2426e0)
at kernel/qobject.cpp:3930
#14 0x7fcb19b52882 in QGuiApplication::screenAdded(QScreen*)
(this=, _t1=) at .moc/moc_qguiapplication.cpp:389
#15 0x7fcb19b3af82 in
QWindowSystemInterface::handleScreenAdded(QPlatformScreen*, bool)
(ps=, isPrimary=isPrimary@entry=false) at
kernel/qwindowsysteminterface.cpp:815
#16 0x7fcb0c95b11b in
QtWaylandClient::QWaylandDisplay::handleScreenInitialized(QtWaylandClient::QWaylandScreen*)
(this=0x562a96e5e750, screen=, screen@entry=0x562a986de290) at
qwaylanddisplay.cpp:269
#17 0x7fcb0c966026 in QtWaylandClient::QWaylandScreen::maybeInitialize()
(this=0x562a986de290) at qwaylandscreen.cpp:91
#18 0x7fcb125d6dae in ffi_call_unix64 () at
/usr/lib/x86_64-linux-gnu/libffi.so.6
#19 0x7fcb125d671f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#20 0x7fcb17d6ae24 in wl_closure_invoke
(closure=closure@entry=0x562a978b8270, flags=flags@entry=1, target=, target@entry=0x562a9c84cd80, opcode=opcode@entry=2, data=)
at ../src/connection.c:1006
#21 0x7fcb17d67659 in dispatch_event (display=display@entry=0x562a96e5e890,
queue=) at ../src/wayland-client.c:1427
#22 0x7fcb17d68b24 in dispatch_queue (queue=0x562a96e5e958,
display=0x562a96e5e890) at ../src/wayland-client.c:1573
#23 0x7fcb17d68b24 in wl_display_dispatch_queue_pending
(display=0x562a96e5e890, queue=0x562a96e5e958) at ../src/wayland-client.c:1815
#24 0x7fcb17d68b7c in wl_display_dispatch_pending (display=)
at ../src/wayland-client.c:1878
#25 0x7fcb0c959642 in QtWaylandClient::QWaylandDisplay::flushRequests()
(this=0x562a96e5e750) at qwaylanddisplay.cpp:208
#26 0x7fcb1959ddc9 in doActivate(QObject*, int, void**)
(sender=0x562a96e758a0, signal_index=4, argv=0x7ffe9a242ba0) at
kernel/qobject.cpp:3882
#27 0x7fcb195988a2 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x562a96e758a0, m=m@entry=0x7fcb19a30240
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3930
#28 0x7fcb1955f4b3 in QAbstractEventDispatcher::awake()
(this=this@entry=0x562a96e758a0) at .moc/moc_qabstracteventdispatcher.cpp:149
#29 0x7fcb195c20fb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x562a96e758a0, flags=...) at kernel/qeventdispatcher_glib.cpp:430
#30 0x7fcb1956163a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffe9a242cc0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:225
#31 0x7fcb1956adb0 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1400
#32 0x562a95ac2058 in main(int, char**) (argc=,
argv=) at 

[plasmashell] [Bug 418483] Pinned apps move when launched as if using the behavior of the non-Icons-Only Task Manager

2020-04-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=418483

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In|5.19.0  |5.18.5

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

[systemsettings] [Bug 419745] WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client

2020-04-06 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=419745

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com

--- Comment #1 from Jan Grulich  ---
What is the mode set to in the "Wi-Fi" tab when configuring the connection? Do
you use Access Point or Adhoc? Can you change it to the other one, like to
Access Point when using Adhoc and vice versa and try if it makes a difference?

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

[frameworks-kio] [Bug 76380] Trashing files on other partitions and disks that are mounted without UID=USERID, GID=USERGROUPID, FMASK=177, DMASK=077 copies them to the Trash directory on /

2020-04-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=76380

len...@vivaldi.net changed:

   What|Removed |Added

 CC||len...@vivaldi.net

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

[plasma-nm] [Bug 419737] Graphical glitch in "Connections - system settings module"

2020-04-06 Thread Jan Grulich
https://bugs.kde.org/show_bug.cgi?id=419737

Jan Grulich  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||jgrul...@redhat.com
 Resolution|--- |FIXED
   Version Fixed In||5.19.0

--- Comment #1 from Jan Grulich  ---
This will be fixed in Plasma 5.19.

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

[kate] [Bug 419719] Crash when repeating pgrep operation back-to-back

2020-04-06 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=419719

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org,
   ||s...@helsinki.fi

--- Comment #1 from Christoph Cullmann  ---
CC search plugin maintainer:

Kåre, looks like we have some race condition.

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

[plasmashell] [Bug 418483] Pinned apps move when launched as if using the behavior of the non-Icons-Only Task Manager

2020-04-06 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=418483

Marco Martin  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla
   |sma-workspace/627920bdfe14e |sma-workspace/ac0124c48ce68
   |17620a4d1ee99c7d10b028b26bf |5db42ef0a99ce48e4b86621ed12

--- Comment #9 from Marco Martin  ---
Git commit ac0124c48ce685db42ef0a99ce48e4b86621ed12 by Marco Martin.
Committed on 06/04/2020 at 18:54.
Pushed by mart into branch 'Plasma/5.18'.

use the decoded url for launcherPosition

Summary:
launchersOrder and the actual url data can be different:
in case of preferred:/ urls launcherorder will have that for
(for serialization) and the actual appdata url will be decoded as for
instance Applications:firefox.desktop.
this url is the one that needs to be compared to know the actual
launcher order

Test Plan: firefox stays in first position when pinned as preferred://browser

Reviewers: #plasma, ngraham

Reviewed By: ngraham

Subscribers: ngraham, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D28632

M  +1-1libtaskmanager/launchertasksmodel.cpp

https://commits.kde.org/plasma-workspace/ac0124c48ce685db42ef0a99ce48e4b86621ed12

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

[ark] [Bug 419750] Fails to compress without giving any error message

2020-04-06 Thread Mark Smith
https://bugs.kde.org/show_bug.cgi?id=419750

--- Comment #2 from Mark Smith  ---
Actually I figured out the archive is created properly. What tricked me into
thinking the archiving failed was

1. The progress bar stops abruptly halfway through
2. The archive properties after opening in Ark do not match with what Dolphin
shows (maybe it only looks at the first child folder while Dolphin looks at all
of them? I dunno)

The archive is created properly. I uncompressed the archive and everything was
there. I think this can be closed and ignored if this inconsistency is
intended. The progress bar does stop abruptly though sometimes and it totally
looks like it crashed or failed halfway through.

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

  1   2   3   4   >