[KEXI] [Bug 408853] Crash on Form Design, probably with check boxes and yes/no fields.

2019-07-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=408853

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[krita] [Bug 410015] brushes on krita are moving incorrectly

2019-07-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=410015

Bug Janitor Service  changed:

   What|Removed |Added

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

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

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

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

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

[krusader] [Bug 409473] Computer shutdown gets cancelled

2019-07-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=409473

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

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

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

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

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

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

[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text

2019-07-20 Thread Princeton
https://bugs.kde.org/show_bug.cgi?id=409968

Princeton  changed:

   What|Removed |Added

 CC||princeton...@yahoo.com

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

[kdevelop] [Bug 409596] Adding a lambda as a template argument in a header where the template parameter is a function pointer type causes a crash.

2019-07-20 Thread Matti
https://bugs.kde.org/show_bug.cgi?id=409596

Matti  changed:

   What|Removed |Added

Summary|Adding a lambda as a|Adding a lambda as a
   |template argument in a  |template argument in a
   |specific project (of mine)  |header where the template
   |causes a crash when trying  |parameter is a function
   |to parse a file.|pointer type causes a
   ||crash.

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

[valgrind] [Bug 323431] Unhandled AMD XOP instruction vpcmov VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB

2019-07-20 Thread Anthony Romano
https://bugs.kde.org/show_bug.cgi?id=323431

Anthony Romano  changed:

   What|Removed |Added

 CC||romanoanthony...@gmail.com

--- Comment #8 from Anthony Romano  ---
Created attachment 121654
  --> https://bugs.kde.org/attachment.cgi?id=121654=edit
support vpcmov

Hi, I've been hitting this one recently and it's in a lot of my system
libraries, so I added vpcmov support.

After I wrote this patch I poked around the bug tracker and realized I wrote a
broken XOP decoding patch for TBM bextr under a different account nearly six
years ago. It was ignored for a while and by the time it got any attention from
maintainers I had stopped relying on libvex internals for work. The bug was
later consolidated to another issue
(https://bugs.kde.org/show_bug.cgi?id=381819); there was modest traffic about 2
years ago, but I wasn't copied on it. Since there wasn't any progress at the
time, I changed my compiler settings to use bdver1 to avoid XOP TBM
instructions so it never came up again for me. My understanding is there's now
a VEX encoding for bextr.

The new attached patch piggybacks on PFX_VEX, introducing ESC_M8 instead of
incorrectly reusing the VEX ESC constants and adding PFX_XOP; it correctly
handles the pop case where XOP decoding should be abandoned. Adding the
alternative XOP bextr encoding from the other issue should be simple once
there's an XOP decode path.

Thanks.

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

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401677

sepulchrewra...@protonmail.com changed:

   What|Removed |Added

 Attachment #121408|0   |1
is obsolete||

--- Comment #19 from sepulchrewra...@protonmail.com ---
Created attachment 121653
  --> https://bugs.kde.org/attachment.cgi?id=121653=edit
New error on Samsung S9 after compatibility check fixed

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

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401677

--- Comment #18 from sepulchrewra...@protonmail.com ---
Note that I haven't uploaded these changes, not entirely certain of myself
regarding pushing fixes to this project. The change was simply to make the
.equals call convert any manufacturer string to all lower-case, and change the
compared value from "Samsung" to "samsung"

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

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401677

sepulchrewra...@protonmail.com changed:

   What|Removed |Added

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

--- Comment #17 from sepulchrewra...@protonmail.com ---
Right, I've made some further changes. The MANUFACTURER string on Samsung is
not capitalised, at least on my phone. However, even once that's been changed,
it still errors when retrieving MMS content as msg_box isn't available in the
database for MMS messages

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

[krita] [Bug 410055] New: filter layer and filter mask pop ups are locked to the center of the screen with dark opaque screen overlay

2019-07-20 Thread Toby
https://bugs.kde.org/show_bug.cgi?id=410055

Bug ID: 410055
   Summary: filter layer and filter mask pop ups are locked to the
center of the screen with dark opaque screen overlay
   Product: krita
   Version: 4.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Filter Layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: tobywills...@gmail.com
  Target Milestone: ---

SUMMARY
The filter layer and filter mask layers pop ups are locked centrally to the
screen and have a dark opaque screen overlay that hinders any accurate colour
adjustments being made due to the dark overlay.

Versions:
It's worth noting that v4.2.1 works as I expect with no overlay and the pop ups
being moveable with click and drag.
All versions after v4.2.1 have the locked position and screen overlay problem

The overlay problem is similar to Bug 384870 but it's not environmental as the
v4.2.1 version works fine along side the newer versions (v4.2.2 & v4.2.3) that
do not


STEPS TO REPRODUCE
1. open or create a file with a normal drawing layer
2. use the small '+' icon in the layer docker to create either a filter layer
or a filter mask on the drawing layer
3. the popup and overlay appear

OBSERVED RESULT

The popup appears and is not moveable from the center position with click and
drag.
When trying to move it by click and drag the whole app shrinks and moves on
drag

When the pop up is visible the whole screen has the dark opaque overlay, this
makes any colour changes (i.e saturation) from within the filter layer pop ups
hard as you cannot accurately see what the changing colours are due to the dark
overlay.

This is also happening when you go to edit either an existing filter layer or
mask layer but this happens in all the mentioned versions here


EXPECTED RESULT
the popup windows should to be moveable around the screen on click and drag
with no dark screen overlay.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubunutu 18.04.2 LTS
(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.

[kdeconnect] [Bug 409802] Can't access to ExtSdCard

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409802

--- Comment #2 from liv...@penserpouragir.org ---
I did not know about File system expose you suggest me.
Unforyunately, I just lost my device, the old one I had in backup as not
sdcard. 
Them can't try what you speak about, since I foud it again or get another ...
Thanks for your contribution it will help one day.

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

[kate] [Bug 410054] impliment macros

2019-07-20 Thread Zakhar
https://bugs.kde.org/show_bug.cgi?id=410054

--- Comment #1 from Zakhar  ---
In addition to the mentioned feature the macro should permit user to play a
macro an ammount of times set by user or until end of file is reached which
would cease playing the macro.

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

[kate] [Bug 410054] New: impliment macros

2019-07-20 Thread Zakhar
https://bugs.kde.org/show_bug.cgi?id=410054

Bug ID: 410054
   Summary: impliment macros
   Product: kate
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: zakhar.nasi...@gmail.com
  Target Milestone: ---

It would be ideal to implement macros into Kwrite text editor. The ideal type
is found in Notepad++ which permits users to record, save and replay macros.

Recording macros involves selecting the record macros button and every
keystroke thereafter is recorded. The record macros button has a hotkey in
notepad++ which is CTRL+SHIFT+R and stop recording macros is CTRL+SHIFT+S the
hotkey to play a currently selected macro is CTRL+SHIFT+P the macro feature
replays all keystrokes recorded by a macro. Macros accelerates editing.

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

[krita] [Bug 410053] Krita closes with Assert in kis_shortcut_matcher.cpp

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410053

--- Comment #2 from katearche...@yandex.ru ---
(In reply to Tymond from comment #1)
> Links to other bug reports mentioning the same assert: 
> 
> bug 410045
> 
> bug 410048

Strange, I was searching through the bugtracker with the assert text and got no
results :( Yes, the text is the same although I wasn't using a text tool at all
nor filters when I got these crashes, only drawing and moving
selections/groups.

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

[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text

2019-07-20 Thread Toby
https://bugs.kde.org/show_bug.cgi?id=409968

--- Comment #7 from Toby  ---
Created attachment 121652
  --> https://bugs.kde.org/attachment.cgi?id=121652=edit
try to save file after pop up has been dismissed

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

[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text

2019-07-20 Thread Toby
https://bugs.kde.org/show_bug.cgi?id=409968

--- Comment #6 from Toby  ---
(In reply to Tymond from comment #4)
> When I pressed Ignore, it appeared right afterwards again - maybe after one
> more action, and it didn't have an end - Krita had to be restarted (I
> *guess* there was an possibility to save the image, but since those error
> messages was really disrupting and happens one after another, it is possible
> that the user may not be able to do so).

Yes I get the same, if I click 'ignore'the message goes away but then if I
click anything it comes back, this then happens all the time until I close
Krita and reopen it. 
If I dismiss the pop up and then click 'File' to try to save the image I get 2
popups with the same message (attached screenshot)

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

[krita] [Bug 410053] Krita closes with Assert in kis_shortcut_matcher.cpp

2019-07-20 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=410053

Tymond  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com

--- Comment #1 from Tymond  ---
Links to other bug reports mentioning the same assert: 

bug 410045

bug 410048

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

[krita] [Bug 410045] Crash after current tool confusion.

2019-07-20 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=410045

Tymond  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com

--- Comment #2 from Tymond  ---
Links to the bug reports mentioning the same assert: 

bug 409968 

bug 410053

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

[krita] [Bug 410053] New: Krita closes with Assert in kis_shortcut_matcher.cpp

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410053

Bug ID: 410053
   Summary: Krita closes with Assert in kis_shortcut_matcher.cpp
   Product: krita
   Version: 4.2.3
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: katearche...@yandex.ru
  Target Milestone: ---

Created attachment 121651
  --> https://bugs.kde.org/attachment.cgi?id=121651=edit
assert error screenshot

SUMMARY
It happens on random occasions, Krita 4.2.3 throws a window saying "SAFE
ASSERT(krita): "!m_d->readyShortcut" in file C:\...\kis_shortcut_matcher.cpp,
line 579". 

I literally have no idea what is causing it, but I've noticed that it is
sometimes happens when I use move tool via shortcut(V). It can happen in two
minutes after I open Krita or it can happen after an hour or two so there is no
definitive pattern that I can find so far. On two or three occasions this error
popped up after a window "please wait until image operation is finished". That
window was doing nothing(or at least no progress indication was visible and it
wasnt going away by itself) and clicking close would lead to this assert window
too.

Clicking ignore do nothing and the same error is being thrown again and again.
Clicking close is just closing Krita without being able to save file etc.

I've got this error on windows 10, krita 4.2.3. On ubuntu I wasn't able to
repeat the mistake so far(although I wasn't that persistent on that front). On
previous Krita versions I never had such error and wasn't able to reproduce it.

The krita_crash.log has no info on this crash.
In the attachment the screenshot of the error.

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

[krita] [Bug 409564] Filter wave cut off on high amplitudes

2019-07-20 Thread vanyossi
https://bugs.kde.org/show_bug.cgi?id=409564

vanyossi  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

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

[yakuake] [Bug 410052] New: Commands for running instance via cli/yakuake-command

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410052

Bug ID: 410052
   Summary: Commands for running instance via cli/yakuake-command
   Product: yakuake
   Version: 3.0.5
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: vinzenz.hers...@gmail.com
  Target Milestone: ---

Hey,
first thank you for this nice piece of software. It makes my
all-day-computerlife so much easier! :)

However, i had the idea to make my bootprocess of my dev-enviroment a bit
faster. Everything what i write here should be in context to the already
running instance. I imagine something like a bash-script, that would execute

yakuake --new-tab="Whatevername" --run="/usr/bin/cat /dev/urandom"

I don't like to do specifications here, as i am not shure about qt/kf's
argument-system works atm, but those both commands would be very usefull, at
least to me ;)

What i also can imagine as usefull is maybe split screens and run commands in
them or even bind in shortcuts.. i think, if it would be coupled with
shortcuts, allmost all possibilitys would be already avaible. but not shure
this makes sense in your structure.

Would be a dream for productivity and repeated stuff! :)

Best regards

Vinzenz

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

[kdeconnect] [Bug 409870] KDE Connect v1.12.93 problem exporting phone file system

2019-07-20 Thread Jon
https://bugs.kde.org/show_bug.cgi?id=409870

--- Comment #3 from Jon  ---
Addendum: when I tested 18.04, I used the install .iso for testing. Since then,
I've upgraded my machine to the 18.04.2 release of Kubuntu and tried using
kdeconnect.  It gave a message of Root>run>user> [phone id ] > primary does not
exist (using the 1.12.93 version of the Android app freshly installed from the
Google Play Store).  After trial of many things, I found that I had to go to
the vertical "..." in the top right, choose "Plugin settings", "Filesystem
expose", select "primary/primary:" by holding it for a few seconds, then delete
it using the garbage can in the top right.  I then chose "Add storage location"
and added SanDisk SD card, which again gave "primary/primary:" and again paired
with the laptop and the "primary" directory was now populated with
subdirectories that could be browsed.

It's not clear why this extra configuration is necessary---it might be deleting 
leftover configuration from previous trials.  Still, I'm documenting this in
case someone else has a similar issue.

This problem persists and requires the same actions across an uninstall and
re-install of the Android app from the store.

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

[drkonqi] [Bug 409807] Some checkboxes and their labels are misaligned

2019-07-20 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=409807

Harald Sitter  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/drk
   ||onqi/5a59721d7efe89adbfad2d
   ||ec39878d65c2655228
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Harald Sitter  ---
Git commit 5a59721d7efe89adbfad2dec39878d65c2655228 by Harald Sitter.
Committed on 20/07/2019 at 22:32.
Pushed by sitter into branch 'master'.

wrap the details example label+spacer in a container widget

Summary:
this way we can control both their visibility in a single call. with the
previous code we'd only set the label as hidden and leave a dangling
spacer to mess with the layout.

Test Plan:
- segv dolphin -> report -> layout shows example
- segv systemsettings5 -> report -> layout shows no example but is correctly
spaced

Reviewers: #plasma, apol

Reviewed By: apol

Subscribers: plasma-devel

Tags: #plasma

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

M  +2-1src/bugzillaintegration/reportassistantpages_base.cpp
M  +39   -37   src/bugzillaintegration/ui/assistantpage_bugawareness.ui

https://commits.kde.org/drkonqi/5a59721d7efe89adbfad2dec39878d65c2655228

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

[kdenlive] [Bug 367984] Clip Speed effect is lost after moving clips with speed fx applied, saving project, closing and opening it again

2019-07-20 Thread Alejandro tagle
https://bugs.kde.org/show_bug.cgi?id=367984

Alejandro tagle  changed:

   What|Removed |Added

 CC||hector.ta...@gmail.com

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

[plasmashell] [Bug 410051] whenever in going to check updates there is a windows open which say an internal error occured report this bug and no updates are shown

2019-07-20 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=410051

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #2 from David Edmundson  ---
The dialog says that's from Apper. 

That's not us.

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

[frameworks-kio] [Bug 410050] Add context menu item "Add to Places"

2019-07-20 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410050

Alexander Potashev  changed:

   What|Removed |Added

Summary|Add content menu item "Add  |Add context menu item "Add
   |to Places"  |to Places"

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

[plasmashell] [Bug 410051] whenever in going to check updates there is a windows open which say an internal error occured report this bug and no updates are shown

2019-07-20 Thread dhananjay
https://bugs.kde.org/show_bug.cgi?id=410051

dhananjay  changed:

   What|Removed |Added

   Assignee|aleix...@kde.org|dhananjaysawark...@gmail.co
   ||m

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

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

[plasmashell] [Bug 410051] New: whenever in going to check updates there is a windows open which say an internal error occured report this bug and no updates are shown

2019-07-20 Thread dhananjay
https://bugs.kde.org/show_bug.cgi?id=410051

Bug ID: 410051
   Summary: whenever in going to check updates there is a windows
open which say an internal error occured report this
bug and no updates are shown
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: dhananjaysawark...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

fixed it asap

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

[frameworks-kio] [Bug 410050] New: Add content menu item "Add to Places"

2019-07-20 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=410050

Bug ID: 410050
   Summary: Add content menu item "Add to Places"
   Product: frameworks-kio
   Version: 5.59.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Open/save dialogs
  Assignee: fa...@kde.org
  Reporter: aspotas...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
Please add content menu item "Add to Places" which is already available in
Dolphin, into file open/save dialogs.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text

2019-07-20 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=409968

Tymond  changed:

   What|Removed |Added

 CC||grapelo...@gmail.com

--- Comment #5 from Tymond  ---
*** Bug 410048 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 410048] Attempting to edit text causes an error

2019-07-20 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=410048

Tymond  changed:

   What|Removed |Added

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

--- Comment #1 from Tymond  ---


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

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

[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text

2019-07-20 Thread Tymond
https://bugs.kde.org/show_bug.cgi?id=409968

Tymond  changed:

   What|Removed |Added

 CC||tamtamy.tym...@gmail.com

--- Comment #4 from Tymond  ---
When I pressed Ignore, it appeared right afterwards again - maybe after one
more action, and it didn't have an end - Krita had to be restarted (I *guess*
there was an possibility to save the image, but since those error messages was
really disrupting and happens one after another, it is possible that the user
may not be able to do so).

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

[plasmashell] [Bug 410049] plasmashell crashes on right click on favorite apps in Kicker

2019-07-20 Thread Alex Bradatan
https://bugs.kde.org/show_bug.cgi?id=410049

Alex Bradatan  changed:

   What|Removed |Added

 CC||alex.bradata...@yahoo.it
   Keywords||usability

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

[plasmashell] [Bug 410049] New: plasmashell crashes on right click on favorite apps in Kicker

2019-07-20 Thread Alex Bradatan
https://bugs.kde.org/show_bug.cgi?id=410049

Bug ID: 410049
   Summary: plasmashell crashes on right click on favorite apps in
Kicker
   Product: plasmashell
   Version: 5.16.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: alex.bradata...@yahoo.it
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 121649
  --> https://bugs.kde.org/attachment.cgi?id=121649=edit
The backtrace of the crash

SUMMARY
I just came back from a suspend. I opened the Kicker and right clicked on an
icon in the favorites bar (the one on the right) and plasmashell crashed.

STEPS TO REPRODUCE
The crash does not seem to be reproducible.

OBSERVED RESULT
plasmashell crashed with a segfault.

EXPECTED RESULT
plasmashell shouldn't have crashed

SOFTWARE/OS VERSIONS
Application: plasmashell (5.16.3)
Qt Version: 5.13.0
Frameworks Version: 5.60.0
Operating System: Linux 5.2.1-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

ADDITIONAL INFORMATION
I am running an Nvida card on the latest drivers.
Attaching backtrace.

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

[kde-cli-tools] [Bug 408632] kde-open functions incorrectly when given a URL with a port (opens a URL with port as the line number)

2019-07-20 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=408632

David Faure  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde
   |-cli-tools/6d86fd4534174645 |-cli-tools/42ef318a9d1c454f
   |09860b7be8c3cbf0e4a8d27b|96b60181d8231a59233720ea

--- Comment #7 from David Faure  ---
Git commit 42ef318a9d1c454f96b60181d8231a59233720ea by David Faure, on behalf
of Gleb Popov.
Committed on 20/07/2019 at 20:27.
Pushed by dfaure into branch 'Plasma/5.16'.

kioclient: Don't convert `:x:y` to `?line=x=y` for URLs starting with
remote schemes.

Test Plan: `kioclient5 exec http://localhost:9000` now works correctly.

Subscribers: plasma-devel, #frameworks

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

M  +9-0kioclient/urlinfo.h

https://commits.kde.org/kde-cli-tools/42ef318a9d1c454f96b60181d8231a59233720ea

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

[krita] [Bug 410048] New: Attempting to edit text causes an error

2019-07-20 Thread Tate
https://bugs.kde.org/show_bug.cgi?id=410048

Bug ID: 410048
   Summary: Attempting to edit text causes an error
   Product: krita
   Version: 4.2.3
  Platform: Other
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Tool/Text
  Assignee: krita-bugs-n...@kde.org
  Reporter: grapelo...@gmail.com
  Target Milestone: ---

SUMMARY
Attempting to edit text when you close the text box re-opens it, how ever it
makes an error message pop up twice with the only options to ignore (which
makes the program impossible to use, as nothing functions) or to abort, which
shuts down the entire program with no option of saving your file. 

STEPS TO REPRODUCE
1.Use the text tool to write anything
2.Hit 'save' and 'close'
3.Double click it to re-open text tool

OBSERVED RESULT
An error message reading 
""Krita has encounterd an internal error: 

SAFE ASSERT (krita) "!m_d->readyShortcut" in file
C:/Packaging/workspace/Krita_Release_Windows64_Build/krita/libs/ui/imput/kis_shortcut_matcher.cpp,
line 579

Please report a bug to developers!

Press ignore to try to continue.
Press abort to see developers information (all unsaved data will be lost)""

Screenshot: https://i.imgur.com/cZbukXi.png

EXPECTED RESULT
Opening the text box and allowing user to change and edit the text without any
crashing or errors. 

SOFTWARE
Windows:10

ADDITIONAL INFORMATION
I use Krita via steam. The specific canvas size I was using when I found this
issue was 2018x1152 and while I doubt it has any affect I was using the font
"Lemon"

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

[krita] [Bug 410047] New: Gui Update, Brush color problem

2019-07-20 Thread Krzysztof Mazur
https://bugs.kde.org/show_bug.cgi?id=410047

Bug ID: 410047
   Summary: Gui Update, Brush color problem
   Product: krita
   Version: 4.2.3
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: m.krzysz...@gmail.com
  Target Milestone: ---

SUMMARY

Problem with updating gui of brush size


STEPS TO REPRODUCE
1. Fire up Krita 4.2.3
2. Create new canvas 1920x1200 300PPI
3. Select brush Texture_Normal_App from All category
4. Press and hold shift
5. Move mouse to resize
6. The size in toolbar doesn't update, select another brush
7. Press hold shift move mouse to resize
8. Size of brush in toolbar updates
9. The color of Brush Texture_Normal_Map is always blue
10. Change color of Brush Texture_Normal_Map to yellow
11. Paint on canvas (it paints in blue)
12. Use color picker on painted in blue shows yellow

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10 x64 build 1903
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: bundled with Krita

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

[digikam] [Bug 409952] "Image" menu is missing

2019-07-20 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=409952

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
   Version Fixed In||6.2.0
 Status|REPORTED|RESOLVED

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

[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.

2019-07-20 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=409919

--- Comment #9 from Martin Flöser  ---
I assume the problem lies in a library. Either Qt or a KDE Framework.
Unfortunately I do not know which part is responsible here. So I would suggest
to report against an application so that they can investigate.

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

[krita] [Bug 410045] Crash after current tool confusion.

2019-07-20 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=410045

Boudewijn Rempt  changed:

   What|Removed |Added

Version|unspecified |git master
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
this is another instancce of the assert popping up about ending a stroke. We've
been getting a lot of those lately.

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

[kdenlive] [Bug 410046] New: left / right does not work, to show next frame

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410046

Bug ID: 410046
   Summary: left / right does not work, to show next frame
   Product: kdenlive
   Version: 19.04.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: bernh...@dedera.de
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. start the programm
2. insert video files
3. bring file to time line 
4. want to move 1 frame with ›left‹

OBSERVED RESULT

nothing happens, no move 


EXPECTED RESULT

should move 


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
ubuntu 19.04
(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 354802] Desktop Icon position gets scrambled sometimes on reboot.

2019-07-20 Thread Valdo
https://bugs.kde.org/show_bug.cgi?id=354802

--- Comment #54 from Valdo  ---
I'm not yet able to tell if this bug is solved with Plasma 5.12.8 or not...
All I can observe is that:
- icons seem to use more space (wider) than before.
- moving icons to the bottom of the desktop (bottom right of the screen, close
to the taskbar) is very imprecise. Icons end up "somewhere else" most of the
time, but rarely where I intend to drop them. Very frustrating.
Anyway, I'm curious about last section of file
~/.config/plasma-org.kde.plasma.desktop-appletsrc. It's named [ScreenMapping]
and seem to contain two subsections:
itemsOnDisabledScreens=[...]
screenMapping=[...]
I couldn't find any technical description of these sections (in case there is
one available somewhere, please tell me so), but I'm surprised to see that some
files are referenced in the 1st subsection ("itemsOnDisabledScreens="), while I
never connected any other physical screen to my PC in the last few years... So
what does "disabled screens" mean? Note: most of referenced files are no longer
present on my desktop (i.e. already moved elsewhere or trashed).
2nd subsection ("screenMapping=") references a very long list of files stored
in sub-sub-subfolders of my desktop. What for?... It also appears that none of
these files are present on my desktop today.
I'm tempted to manually remove them from file
~/.config/plasma-org.kde.plasma.desktop-appletsrc, but what would be the risk
of doing so?...

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

[krita] [Bug 410045] New: Crash after current tool confusion.

2019-07-20 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=410045

Bug ID: 410045
   Summary: Crash after current tool confusion.
   Product: krita
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com
  Target Milestone: ---

Application: krita (4.3.0-prealpha (git 535b60a))

Qt Version: 5.12.3
Frameworks Version: 5.60.0
Operating System: Linux 4.15.0-54-generic x86_64
Distribution: KDE neon User Edition 5.16

-- Information about the crash:
- What I was doing when the application crashed:

I had just been buzy with the colorize mask (editing tool). Then I wanted to do
some regular strokes with the regular brush, but for some reason Krita kept
making colorize masks on the new layer despite me using the brush tool, and
after a while of this I just couldn't make any strokes anymore. As I tried to
get response from the application, Krita crashed.

When the new colorize masks had been made, those triggered a 'prefilter'
operation, and I had canceled those as I was trying to delete the newly made
colorize mask.

-- Backtrace:
Application: Krita (krita), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa5476dbe80 (LWP 16156))]

Thread 18 (Thread 0x7fa4c18f4700 (LWP 29578)):
#0  0x7fa539a14ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fa4c18f3ba0, expected=0, futex_word=0x608009505b70) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa4c18f3c60, mutex=0x608009505b20,
cond=0x608009505b48) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x608009505b48, mutex=0x608009505b20,
abstime=0x7fa4c18f3c60) at pthread_cond_wait.c:667
#3  0x7fa53aa72d36 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa53aa73096 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa53aa70740 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa53aa6bc72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa539a0e6db in start_thread (arg=0x7fa4c18f4700) at
pthread_create.c:463
#8  0x7fa53a15388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7fa4c30f9700 (LWP 29577)):
#0  0x7fa539a14ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fa4c30f8ba0, expected=0, futex_word=0x608008d1cff4) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa4c30f8c60, mutex=0x608008d1cfa0,
cond=0x608008d1cfc8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x608008d1cfc8, mutex=0x608008d1cfa0,
abstime=0x7fa4c30f8c60) at pthread_cond_wait.c:667
#3  0x7fa53aa72d36 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa53aa73096 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa53aa70740 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa53aa6bc72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa539a0e6db in start_thread (arg=0x7fa4c30f9700) at
pthread_create.c:463
#8  0x7fa53a15388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fa4cfd23700 (LWP 29576)):
#0  0x7fa539a14ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fa4cfd22ba0, expected=0, futex_word=0x6080095059f4) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa4cfd22c60, mutex=0x6080095059a0,
cond=0x6080095059c8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x6080095059c8, mutex=0x6080095059a0,
abstime=0x7fa4cfd22c60) at pthread_cond_wait.c:667
#3  0x7fa53aa72d36 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa53aa73096 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa53aa70740 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa53aa6bc72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa539a0e6db in start_thread (arg=0x7fa4cfd23700) at
pthread_create.c:463
#8  0x7fa53a15388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7fa4d0524700 (LWP 29575)):
#0  0x7fa539a14ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fa4d0523ba0, expected=0, futex_word=0x608001d02970) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa4d0523c60, mutex=0x608001d02920,
cond=0x608001d02948) at pthread_cond_wait.c:533
#2  

[Powerdevil] [Bug 410044] New: keys to adjust the screen brightness do not work on Neon unstable edition

2019-07-20 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=410044

Bug ID: 410044
   Summary: keys to adjust the screen brightness do not work on
Neon unstable edition
   Product: Powerdevil
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

SUMMARY
nothing happens when I press the keys to adjust the screen brightness.

STEPS TO REPRODUCE
1. start plasma
2. press a keyboard key to adjust the screen brightness
3. 


EXPECTED RESULT
the keys to adjust the screen brightness work

SOFTWARE/OS VERSIONS
WOperating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3

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

[KScreen] [Bug 358689] [X11] Support Qt 5.6 new highdpi environment variable

2019-07-20 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=358689

--- Comment #11 from David Edmundson  ---
That patch also expands on what breaks

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

[plasma-nm] [Bug 410043] Speed of wired network is slower on Plasma + NetworkManager

2019-07-20 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=410043

--- Comment #1 from Patrick Silva  ---
Detailed info:

I have two computers connected to the same router through a cable,
each one runs two systems.
Desktop:
Arch Linux + Plasma 5.16.3 + Network Manager
Void Linux + Plasma 5.16.3 + Network Manager

Laptop:
Arch Linux + Gnome 3.32.2 + Network Manager
Neon unstable edition + Network Manager

Both Arch and Void installed on desktop computer have
exactly the same problem: internet speed
drops to one third after suspend/resume cycle. Rebooting
is the only way to get the correct internet speed again.

Neon unstable edition always give me one third of the expected
internet speed when I use the ethernet adapter.
Wireless adapter always gives me the correct internet speed,
even after suspend/resume cycle.
Arch + Gnome installed on the same laptop always gives me
the correct internet speed even after resume/suspend cycle
regardless of whether I use ethernet or wireless adapter.

I solved the problem with slower internet speed after suspend/resume
on Arch + Plasma running on my desktop by replacing Network Manager with wicd.

Therefore, all systems running Plasma + Network Manager have issues
with the speed of wired network.
That's why I think that maybe there is some problem between Plasma and Network
Manager.

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

[plasma-nm] [Bug 410043] New: Speed of wired network is slower on Plasma + NetworkManager

2019-07-20 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=410043

Bug ID: 410043
   Summary: Speed of wired network is slower on Plasma +
NetworkManager
   Product: plasma-nm
   Version: 5.16.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. start plasma session
2. connection your machine to a wired network
3. suspend and resume your system

OBSERVED RESULT
explained above

EXPECTED RESULT
network speed is always correct

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 5.1.16-050116-generic

Operating System: Arch Linux
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60
Qt Version: 5.13
Kernel Version: 5.2.1.arch1-1

Operating System: void 
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13
Kernel Version: 5.1.16_1

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

[kde] [Bug 410042] Krita has encountered an internal error:

2019-07-20 Thread rissa
https://bugs.kde.org/show_bug.cgi?id=410042

--- Comment #1 from rissa  ---
it only shows up on the latest version 4.2.3

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

[kscreenlocker] [Bug 410040] music player prevent lock screen

2019-07-20 Thread Guo Yunhe
https://bugs.kde.org/show_bug.cgi?id=410040

--- Comment #2 from Guo Yunhe  ---
In JuK, I found the related code:

QDBusInterface *pmInterface = new QDBusInterface(
 
QStringLiteral("org.kde.Solid.PowerManagement"),
 
QStringLiteral("/org/freedesktop/PowerManagement/Inhibit"),
 
QStringLiteral("org.freedesktop.PowerManagement.Inhibit"),
  QDBusConnection::sessionBus()
  );

It only inhibit power management.

Power management sets the automatic screen lock after N minutes. And it is
inhibited. This will prevent everything: turn off screen, lock screen, sleep.
But for music player, it only needs to prevent sleep. Do you know if such a
DBus interface exists?

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

[kde] [Bug 410042] New: Krita has encountered an internal error:

2019-07-20 Thread rissa
https://bugs.kde.org/show_bug.cgi?id=410042

Bug ID: 410042
   Summary: Krita has encountered an internal error:
   Product: kde
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ciesta.ri...@gmail.com
  Target Milestone: ---

SUMMARY
Krita has encountered an internal error:


Krita has encountered an internal error:

SAFE ASSERT (krita): "!m_d->readyShortcut" in file
C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\ui\input\kis_shortcut_matcher.cpp,
line 579

Please report a bug to developers!

Press Ignore to try to continue.
Press Abort to see developers information (all unsaved data will be lost)

I'm using windows 10 and that message keeps coming up since I've updated to
4.2.3. Please help

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

[kscreenlocker] [Bug 410040] music player prevent lock screen

2019-07-20 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=410040

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
KDE Screensaver does not block because of music players.

/If/ that's happening it means the music player is explicitly requesting to
block the screensaver.

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

[okular] [Bug 410041] New: I can not click in a reference if I use a marker

2019-07-20 Thread Agustín Kanashiro
https://bugs.kde.org/show_bug.cgi?id=410041

Bug ID: 410041
   Summary: I can not click in a reference if I use a marker
   Product: okular
   Version: 1.7.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: akanash...@gmail.com
  Target Milestone: ---

Created attachment 121648
  --> https://bugs.kde.org/attachment.cgi?id=121648=edit
I can't click on the reference if I mark it with Okular tool

SUMMARY
I have a PDF file that has many references (urls and pages) but if I mark that
reference with a color/line I can not click on the reference

STEPS TO REPRODUCE
1. Click on a reference
2. Mark the sentence that contains the reference


OBSERVED RESULT
Can not click on the reference

EXPECTED RESULT
The reference should be clickable

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE 4.19-59-1
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION

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

[kscreenlocker] [Bug 410040] New: music player prevent lock screen

2019-07-20 Thread Guo Yunhe
https://bugs.kde.org/show_bug.cgi?id=410040

Bug ID: 410040
   Summary: music player prevent lock screen
   Product: kscreenlocker
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: i...@guoyunhe.me
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
If music player (JuK) is playing, KDE will not lock screen after no user input
for a long time.

I think music player should only prevent sleep, not lock screen. People may use
bluetooth headphone, they are away from computer when listening to music.
Preventing lock screen is dangerous. This is different from the use case of
video player.

STEPS TO REPRODUCE
1. Start JuK.
2. Play music loop.
3. Wait until screen lock happen.

OBSERVED RESULT
Screen will never be locked.

EXPECTED RESULT
Screen should still be locked.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20190717
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0
Kernel Version: 5.1.16-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.2 GiB

ADDITIONAL INFORMATION

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

[krita] [Bug 410015] brushes on krita are moving incorrectly

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=410015

--- Comment #2 from ldoug...@gmail.com ---
(In reply to Boudewijn Rempt from comment #1)
> I'm sorry, but without a whole lot more detail, we cannot help you, because
> this is obviously something specific for your system and not a bug anyone
> else is running into. In fact, your report has so little detail I don't even
> know what I should ask you. Maybe make a screen recording? Make sure it
> shows the entire Krita window.

Im sorry ill try to be more specific  what i mean is, when i move my bamboo
pen on my tablet, the krita brushes dont move along with my bamboo pen, and
when i try to draw like a circle or something, the brushes on krita wont draw a
circle. I didnt start having this problem until about two days ago but before
that i was drawing everything the same way i try to now, only the brushes had
no trouble keeping up with my bamboo pen

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

[korgac] [Bug 379026] reminder shows dialog for past events

2019-07-20 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=379026

Filipus Klutiero  changed:

   What|Removed |Added

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

--- Comment #4 from Filipus Klutiero  ---
See comment #3

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

[korganizer] [Bug 317656] Korganizer alert reminders are not reliable (they're lost after logout)

2019-07-20 Thread Filipus Klutiero
https://bugs.kde.org/show_bug.cgi?id=317656

Filipus Klutiero  changed:

   What|Removed |Added

 CC||chea...@gmail.com

--- Comment #8 from Filipus Klutiero  ---
Having used KOrganizer for 15 years, I can definitely confirm that its
reminders are unreliable. However, I never understood how to reproduce loss,
and I could not reproduce with a logout. Both a reminder I set to trigger while
my session was closed and one set to trigger after I opened a new session
"popped up" fine, under Kubuntu 19.04 (KOrganizer 5.10.3, KDE Frameworks
5.56.0).

Can one of you still reproduce this, and if so, which distribution do you use?
And if so, does this affect events only or todo-s too?

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

[LabPlot2] [Bug 410039] New: OPJ import does not recognize fit plots

2019-07-20 Thread Uwe Stöhr
https://bugs.kde.org/show_bug.cgi?id=410039

Bug ID: 410039
   Summary: OPJ import does not recognize fit plots
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

Created attachment 121647
  --> https://bugs.kde.org/attachment.cgi?id=121647=edit
Origin file testcase

- import the attached OPJ file

It consists of 6 fit plats (linear fits).

result: I get 6 xy-curves and no fit plots.

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

[okular] [Bug 409710] Continuous view gets stuck when multiple tabs are used

2019-07-20 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=409710

--- Comment #3 from Albert Astals Cid  ---
Could you upload a video/gif somewhere (record with peek for example) showing
exactly what you do?

Maybe your instructions are unclear or i did not follow them correctly, having
a video would help in that regard.

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

[yakuake] [Bug 410038] New: Shift+Tab is reported as ambiguous in Yakuake

2019-07-20 Thread Gleb Popov
https://bugs.kde.org/show_bug.cgi?id=410038

Bug ID: 410038
   Summary: Shift+Tab is reported as ambiguous in Yakuake
   Product: yakuake
   Version: 3.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: 6year...@gmail.com
  Target Milestone: ---

I had Shift+Tab combination set to the "Next Session" action. After full system
upgrade pressing this combination in Yakuake pops out a 'An ambiguous key
sequence' error.

I tried opening Konsole's shortcuts and removed Shift+Tab action there, but
that didn't helped. I also gone through every tab in "Global shortcuts" in
System Settings with no success.


STEPS TO REPRODUCE
1. Open 2 tabs in Yakuake.
2. Set "Next Session" to "Shift+Tab"
3. Try switching between tabs using this key combination.

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

[kate] [Bug 398998] Allow kioclient exec to open kwrite/kate documents at specified cursor

2019-07-20 Thread Gleb Popov
https://bugs.kde.org/show_bug.cgi?id=398998

Gleb Popov <6year...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #12 from Gleb Popov <6year...@gmail.com> ---
Fixed with https://phabricator.kde.org/D22525

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

[kde-cli-tools] [Bug 408632] kde-open functions incorrectly when given a URL with a port (opens a URL with port as the line number)

2019-07-20 Thread Gleb Popov
https://bugs.kde.org/show_bug.cgi?id=408632

Gleb Popov <6year...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||-cli-tools/6d86fd4534174645
   ||09860b7be8c3cbf0e4a8d27b
 Status|REPORTED|RESOLVED

--- Comment #6 from Gleb Popov <6year...@gmail.com> ---
Git commit 6d86fd453417464509860b7be8c3cbf0e4a8d27b by Gleb Popov.
Committed on 20/07/2019 at 15:19.
Pushed by arrowdodger into branch 'master'.

kioclient: Don't convert `:x:y` to `?line=x=y` for URLs starting with
remote schemes.

Test Plan: `kioclient5 exec http://localhost:9000` now works correctly.

Subscribers: plasma-devel, #frameworks

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

M  +9-0kioclient/urlinfo.h

https://commits.kde.org/kde-cli-tools/6d86fd453417464509860b7be8c3cbf0e4a8d27b

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

[okular] [Bug 409710] Continuous view gets stuck when multiple tabs are used

2019-07-20 Thread Mebus
https://bugs.kde.org/show_bug.cgi?id=409710

--- Comment #2 from Mebus  ---
Hallo,

now I tried Okular version 1.7.2, which I installed via Flatpak. The same thing
still happens. I have to toggle the "continuous view" checkbox sometimes to
have a continuous view again after I switched the tab. And after that I cannot
scroll in the other tab. Neither with Page up / Page down nor with my mouse.

I scaled one of the PDFs to fit the viewable space inside Okular.

Mebus

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

[kdenlive] [Bug 410037] New: Tabs in dialog window when I can select new video are broken

2019-07-20 Thread Kacper Paczos
https://bugs.kde.org/show_bug.cgi?id=410037

Bug ID: 410037
   Summary: Tabs in dialog window when I can select new video are
broken
   Product: kdenlive
   Version: 19.04.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: kacper-pac...@linux.pl
  Target Milestone: ---

Created attachment 121646
  --> https://bugs.kde.org/attachment.cgi?id=121646=edit
Example

SUMMARY
Tabs in dialog windows to select new video aren't work. When i click, nothing
is changeing. See image in attach.

STEPS TO REPRODUCE
1. Launch Kdenlive (for example) from flatpak
2. Try to add new video
3. Try to use tabs (like Video or Documents)

OBSERVED RESULT
Nothing is changing, folder is the same like was when i clicked which of tabs.

EXPECTED RESULT
It should be work

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux Mint Cinnamon
(available in About System)
KDE Plasma Version: flatpak version
KDE Frameworks Version: KDE 5.59.0
Qt Version: Qt 5.12.4 (zbudowane na 5.12.4)

ADDITIONAL INFORMATION
I used flatpak version on non kde DE.

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

[korganizer] [Bug 410036] New: KOrganizer closing out of the blue

2019-07-20 Thread André Padilha
https://bugs.kde.org/show_bug.cgi?id=410036

Bug ID: 410036
   Summary: KOrganizer closing out of the blue
   Product: korganizer
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: padilha.an...@gmail.com
  Target Milestone: ---

Application: korganizer (5.9.3)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-5-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Inserting items in the task list

- Unusual behavior I noticed:
Application closing for the third time during the activity above

- Custom settings of the application:
None, excet using mail config from system settings.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3b80aaea80 (LWP 10126))]

Thread 8 (Thread 0x7f3ad2462700 (LWP 10265)):
#0  0x7f3b8642be69 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3b863e1675 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b863e206b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b863e225c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3b891dc87b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3b8918a27b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3b88fd9ec6 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3b88fe3aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 7 (Thread 0x7f3b63fff700 (LWP 10147)):
#0  0x7f3b86f6d00c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3b84a72e6a in ?? () from /lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f3b84a72e89 in ?? () from /lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f3b6d4e1700 (LWP 10141)):
#0  0x7f3b86f6d00c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3b6daf5e03 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#2  0x7f3b6daf5b57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#3  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f3b7d029700 (LWP 10133)):
#0  0x7f3b8642be84 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3b863e1fed in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b863e225c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b891dc87b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3b8918a27b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3b88fd9ec6 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3b88fe3aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f3b7d879700 (LWP 10130)):
#0  0x7f3b88cb0819 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f3b863e2136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3b863e225c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3b891dc87b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3b8918a27b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3b88fd9ec6 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3b88fe3aa7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3b86f66fa3 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x7f3b88cbb4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f3b7eda2700 (LWP 10128)):
#0  0x7f3b8a795320 in ?? () from /lib64/ld-linux-x86-64.so.2
#1  0x7f3b8a79a1f8 in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2
#2  0x7f3b88fe2e26 in ?? () from 

[kate] [Bug 362810] 15.12.3: Spelling - "Add to dictionary" does not remember added words

2019-07-20 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=362810

Ahmad Samir  changed:

   What|Removed |Added

 CC||a.samir...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #9 from Ahmad Samir  ---


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

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

[kate] [Bug 408291] Automatic Spellchecking fails after file is modified and reloaded

2019-07-20 Thread Ahmad Samir
https://bugs.kde.org/show_bug.cgi?id=408291

Ahmad Samir  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #6 from Ahmad Samir  ---
*** Bug 362810 has been marked as a duplicate of this bug. ***

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

[kdeconnect] [Bug 409079] Cant open filesystem on Android device

2019-07-20 Thread Axel Braun
https://bugs.kde.org/show_bug.cgi?id=409079

Axel Braun  changed:

   What|Removed |Added

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

--- Comment #3 from Axel Braun  ---
Android version is 8.0.0 , KDE Connect App is 1.12.93

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

[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409919

--- Comment #8 from marcantoine_manning...@outlook.com ---
Thanks Yogesh Marwaha, that what I wanted to say. It's not minimizing, it's
restoring to the non-fullscreen size.

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

[krita] [Bug 406992] The translations from kitemviews aren't loaded.

2019-07-20 Thread Karl Ove Hufthammer
https://bugs.kde.org/show_bug.cgi?id=406992

Karl Ove Hufthammer  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Karl Ove Hufthammer  ---
And using the German translation, the “What’s This?” translation (which comes
from Qt) is also shown as translated. Since things seem to (now) work, I’m
closing this bug.

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

[krita] [Bug 406992] The translations from kitemviews aren't loaded.

2019-07-20 Thread Karl Ove Hufthammer
https://bugs.kde.org/show_bug.cgi?id=406992

Karl Ove Hufthammer  changed:

   What|Removed |Added

 CC||k...@huftis.org

--- Comment #2 from Karl Ove Hufthammer  ---
FWIW, the ‘Search:’ string is shown as translated for me. This is on Linux,
using the latest Git version and the Norwegian Nynorsk translation.

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

[BalooWidgets] [Bug 409989] Additional Information -> Rating always shows a 0/5 rating

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=409989

Nate Graham  changed:

   What|Removed |Added

  Component|view-engine: general|general
Product|dolphin |BalooWidgets
 CC||n...@kde.org
   Assignee|dolphin-bugs-n...@kde.org   |stefan.bruens@rwth-aachen.d
   ||e
Version|19.04.3 |19.04.0

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

[KScreen] [Bug 353418] External display is overlapped with laptop's screen on boot

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=353418

Nate Graham  changed:

   What|Removed |Added

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

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

[KScreen] [Bug 394625] Monitor hidden under another monitor

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=394625

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||n...@kde.org

--- Comment #1 from Nate Graham  ---


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

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

[KScreen] [Bug 353418] External display is overlapped with laptop's screen on boot

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=353418

Nate Graham  changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #12 from Nate Graham  ---
*** Bug 394625 has been marked as a duplicate of this bug. ***

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

[KScreen] [Bug 358689] [X11] Support Qt 5.6 new highdpi environment variable

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=358689

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #10 from Nate Graham  ---
There's a patch that implements this feature:
https://phabricator.kde.org/D12405

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

[KScreen] [Bug 358689] Support Qt 5.6 new highdpi environment variable

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=358689

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[KScreen] [Bug 358689] [X11] Support Qt 5.6 new highdpi environment variable

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=358689

Nate Graham  changed:

   What|Removed |Added

Summary|Support Qt 5.6 new highdpi  |[X11] Support Qt 5.6 new
   |environment variable|highdpi environment
   ||variable

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

[KScreen] [Bug 397499] [wayland] Show Warnings for 2X on Non HDPI Screens

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=397499

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
   Keywords||usability

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

[frameworks-kinit] [Bug 345175] Launching non-existent executable leads to misleading/non-userfriendly result/message

2019-07-20 Thread David Faure
https://bugs.kde.org/show_bug.cgi?id=345175

David Faure  changed:

   What|Removed |Added

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

--- Comment #1 from David Faure  ---
Thanks for the report.
This no longer happens because plasma/krunner don't go through kdeinit anymore.

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

[KScreen] [Bug 365749] kscreen kcm: orientation should be under advanced

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=365749

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |INTENTIONAL
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Nate Graham  ---
For tablets, the solution is auto-rotation, which is working or will eventually
work on Wayland. I agree that this is now basic functionality for the KCM. The
KCM itself is a fairly nerdy thing that regular users won't generally have a
reason to go to, so IMO it's okay for it to display stuff like this in it.

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

[frameworks-kio] [Bug 409740] KIO-FTP can't connect to some FTP servers with Turkish locale

2019-07-20 Thread NXiss7
https://bugs.kde.org/show_bug.cgi?id=409740

--- Comment #1 from NXiss7  ---
It turns out that the application ignores the case (using toUpperCase()
function of java.lang.String) .
But on Turkish locale, lower-case 'i' converted to upper-case 'İ' instead of
'I' thus client receives "Command not implemented" result.
I assume this bug would cause problems on other servers that run with Turkish
locale.

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

[Falkon] [Bug 409622] Falkon doesn't scale normally in Wayland in KDE

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=409622

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #8 from Nate Graham  ---
All right, then this is actually working properly when you use the appropriate
scaling setting.

Fractional scaling on Wayland is in progress right now, with a patch submitted:
https://phabricator.kde.org/D22468

So once that's in, you should be able to use your favorite fractional scale
factor and hare everything just work properly.

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

[frameworks-kio] [Bug 409740] KIO-FTP can't connect to some FTP servers with Turkish locale

2019-07-20 Thread NXiss7
https://bugs.kde.org/show_bug.cgi?id=409740

NXiss7  changed:

   What|Removed |Added

Summary|KIO-FTP can't connect to|KIO-FTP can't connect to
   |some Android FTP servers|some FTP servers with
   ||Turkish locale

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

[krita] [Bug 410035] Suddenly the brushes don't color anymore. I try to color and the cursor remains still.

2019-07-20 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=410035

wolthera  changed:

   What|Removed |Added

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

--- Comment #1 from wolthera  ---
Hey, we're going to need a bit more of an explaination of the problem before we
can help you, though it's nice of your to include the system info for
bugreports.

Does this only happen with a single file? Are you sure you didn't activate the
eraser? Any other odd behaviour?

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

[krita] [Bug 410035] New: Suddenly the brushes don't color anymore. I try to color and the cursor remains still.

2019-07-20 Thread Peppe
https://bugs.kde.org/show_bug.cgi?id=410035

Bug ID: 410035
   Summary: Suddenly the brushes don't color anymore. I try to
color and the cursor remains still.
   Product: krita
   Version: 4.2.3
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush Engine/Bristle
  Assignee: krita-bugs-n...@kde.org
  Reporter: peppe.b-...@hotmail.it
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION
OpenGL Info

  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GTX 970/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 419.35" 
  Shading language:  "4.60 NVIDIA" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:QSurfaceFormat(version 4.6, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 4.6
 Supports deprecated functions true 
 is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsAngleD3D11: true 
  isQtPreferAngle: false 
== log ==
 Supported renderers: QFlags(0x2|0x4|0x8) 
Surface format preference list: 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
2 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
4 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
2 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
2 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
4 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
4 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
8 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
8 
* QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2,
stencilBufferSize 8, samples -1, 

[frameworks-ktexteditor] [Bug 409978] Double usage of Ctrl+Shift+V

2019-07-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=409978

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kte
   ||xteditor/0fb0e618bb0cd7a49c
   ||782d0ef28e64d57adcf010
 Resolution|--- |FIXED
   Version Fixed In||5.61
 Status|REPORTED|RESOLVED

--- Comment #4 from Nate Graham  ---
Git commit 0fb0e618bb0cd7a49c782d0ef28e64d57adcf010 by Nate Graham.
Committed on 20/07/2019 at 13:35.
Pushed by ngraham into branch 'master'.

Re-map default "Switch input mode" shortcut to not confict with konsolepart

Summary:
kateview's "Switch input mode" feature is currently bound to {key Ctrl Shift
V}. This
causes two problems:
1. When the embedded konsolepart is visible, both it and Kate claim the same
shortcut so neither one works
2. At other times, it's easily possible to accidentally enter vi mode when you
mean to paste due to residual muscle memory from having pasted test in Konsole
recently

For these reasons, this patch changes the default shortcut to {key Ctrl Alt V},
which
is also kind of more elegant anyway since it now uses the {key Alt} key and
triggers
alternate input modes.
FIXED-IN: 5.61

Test Plan:
1. Compile
2. Open Kate
3. Hit {key Ctrl Shift V} and see that nothing happens
4. Copy some text
5. Open embedded Konsole and paste text with {key Ctrl Shift V} and see that it
works
6. Hit {key Ctrl Alt V} and see that it enters vi mode

Reviewers: #kate, #ktexteditor, cullmann

Reviewed By: #kate, #ktexteditor, cullmann

Subscribers: cullmann, kwrite-devel, kde-frameworks-devel

Tags: #kate, #frameworks

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

M  +1-1src/view/kateview.cpp

https://commits.kde.org/ktexteditor/0fb0e618bb0cd7a49c782d0ef28e64d57adcf010

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

[kdeconnect] [Bug 409079] Cant open filesystem on Android device

2019-07-20 Thread Erik Duisters
https://bugs.kde.org/show_bug.cgi?id=409079

Erik Duisters  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||e.duiste...@gmail.com

--- Comment #2 from Erik Duisters  ---
What version of the app are you running on Android and what version of Android
do you have on your phone?

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

[krita] [Bug 410034] New: Gradient labels are not translated (and two are not translatable)

2019-07-20 Thread Karl Ove Hufthammer
https://bugs.kde.org/show_bug.cgi?id=410034

Bug ID: 410034
   Summary: Gradient labels are not translated (and two are not
translatable)
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Translation
  Assignee: krita-bugs-n...@kde.org
  Reporter: k...@huftis.org
  Target Milestone: ---

SUMMARY
The text ‘Foreground to Transparent’ and ‘Foreground to Background’, which
appears when you click on the ‘Gradients’ icons on the toolbar are not
translatable, i.e., they don’t appear as a string in the krita.pot file.

Also, for the gradient names that *are* translatable in the krita.pot file,
e.g. ‘GPS Fire Blueish’ and ‘GPS Nature random greens’, the translations are
not actually used in the UI; they strings are always shown in English.



STEPS TO REPRODUCE
1. Launch Krita in a language different than English, e.g. Norwegian Nynorsk:
‘LANGUAGE=nn krita’
2. Click the ‘Gradients’ icon on the toolbar
3. Read the text ‘Foreground to Transparent’ or ‘Foreground to Background’
(English)
4. Check that the corresponding strings are missing from the POT file:
https://websvn.kde.org/*checkout*/trunk/l10n-kf5/templates/messages/extragear-graphics/krita.pot
5. Click on one of the other gradients, e.g. ‘GPS Nature random greens’.
6. Observe that the gradient name is shown in English, even though the string
is translated in the PO file:
https://websvn.kde.org/*checkout*/trunk/l10n-kf5/nn/messages/extragear-graphics/krita.po


OBSERVED RESULT
Strings are missing from POT file.
Translations from PO file are not used.

EXPECTED RESULT
All gradient name strings should available for translation in the POT file.
The translations in the PO file should be shown in the actual UI.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20190717
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0
Kernel Version: 5.1.16-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz
Memory: 15,6 GiB

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

[okular] [Bug 306855] Support Javascript

2019-07-20 Thread João Netto
https://bugs.kde.org/show_bug.cgi?id=306855

João Netto  changed:

   What|Removed |Added

 Blocks|242617  |


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=242617
[Bug 242617] Okular does not play animated pdf files
-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 242617] Okular does not play animated pdf files

2019-07-20 Thread João Netto
https://bugs.kde.org/show_bug.cgi?id=242617

João Netto  changed:

   What|Removed |Added

 Depends on|306855  |
 Resolution|--- |FIXED
   Version Fixed In||1.9
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://invent.kde.org/kde/
   ||okular/merge_requests/10
 CC||joaonetto...@gmail.com

--- Comment #11 from João Netto  ---
This is now fixed and should work with Poppler > 0.79

Link to merge request:

https://invent.kde.org/kde/okular/merge_requests/10


Referenced Bugs:

https://bugs.kde.org/show_bug.cgi?id=306855
[Bug 306855] Support Javascript
-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 403772] Support animation from latex package 'animate'

2019-07-20 Thread João Netto
https://bugs.kde.org/show_bug.cgi?id=403772

João Netto  changed:

   What|Removed |Added

 CC||joaonetto...@gmail.com
  Latest Commit||https://invent.kde.org/kde/
   ||okular/merge_requests/10
 Status|REPORTED|RESOLVED
   Version Fixed In||1.9
 Resolution|--- |FIXED

--- Comment #2 from João Netto  ---
This is now fixed and should work with Poppler > 0.79.

Link to merge request:

https://invent.kde.org/kde/okular/merge_requests/10

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

[Falkon] [Bug 408981] missing MSVCR120.dll

2019-07-20 Thread kavol
https://bugs.kde.org/show_bug.cgi?id=408981

kavol  changed:

   What|Removed |Added

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

--- Comment #3 from kavol  ---
(In reply to Stephan from comment #2)
> I could resolve the problem here. It was to install "Microsoft Visual C++
> 2013 Resdistributable (X64) 12.0.30501". I also installed the (X86) version
> as well to be sure (running 64-bit Windows 10). 
> After that Falkon startet as desired.
> 
> @kavol: I would like to know if this helps You to get Falkon running on Your
> system.

well, yes, using the older version 2013 helps, thanks ...

> If it does, I would be pleased if You could close the case.

... however, I'd prefer not to close this until the Falkon download webpage
informs about the dependency (and possibly also where to get it, as finding
something at Microsoft site is not that straightforward)

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

[frameworks-ktexteditor] [Bug 409978] Double usage of Ctrl+Shift+V

2019-07-20 Thread Matthias
https://bugs.kde.org/show_bug.cgi?id=409978

--- Comment #3 from Matthias  ---
Thanks a lot. Goes that upstream? I vote for it. Thanks Nate :)

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

[kdeconnect] [Bug 405702] kdeconnectd crashes if Android permissions are changed while devices are un-paired

2019-07-20 Thread Erik Duisters
https://bugs.kde.org/show_bug.cgi?id=405702

Erik Duisters  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Erik Duisters  ---
Fixed by commit 362b0ba2e2607678b3915bf385b5feac1867e86c

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

[lokalize] [Bug 409532] The directory tree view disappears afeter some time, and only standalone files are shown (XFCE))

2019-07-20 Thread Simon Depiets
https://bugs.kde.org/show_bug.cgi?id=409532

--- Comment #1 from Simon Depiets  ---
Hello,
I tried a few language on the gimp doc repository and couldn't reproduce, which
language was it ?
Are you sure you are not filtering files fully translated either ? (Ctrl+T)
Thanks

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

[Falkon] [Bug 409622] Falkon doesn't scale normally in Wayland in KDE

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409622

mcadoo.c...@gmail.com changed:

   What|Removed |Added

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

--- Comment #7 from mcadoo.c...@gmail.com ---
(In reply to Nate Graham from comment #6)
> Sure. But does Falkon scale as expected with 2x?
> 
> If so, then the solution would be to use this system once fractional scaling
> on Wayland is turned on, which is actually pretty soon.

Yes. Falkon scale will scale with 2x system display setting. But I don't see
any scale options like 1.3x or 1.4x. Now I changed falkon default zoom setting.
Thank you for your attention.

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

[digikam] [Bug 406428] Video preview - no sound

2019-07-20 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=406428

--- Comment #44 from Maik Qualmann  ---
I also think that the "capi" entry is not relevant to this problem. Rather,
those missing the linked libs, especially "libpthread.so.0".

Maik

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

[dolphin] [Bug 410032] Items in right click-menu are not translated

2019-07-20 Thread mthw0
https://bugs.kde.org/show_bug.cgi?id=410032

mthw0  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||matejm98m...@gmail.com

--- Comment #2 from mthw0  ---
(In reply to Antonio Rojas from comment #1)
> Those are Qt strings, do you have qt5-translations installed?

I did not, thanks. It was strange to me that something wasn't translated even
though translation for this app is otherwise complete. Do you by any chance
know why did they (KDE team) make it like this? I mean there already are
strings like these in the translation files.

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

[kate] [Bug 332935] jump to mark doesn't work with dead keys keyboard

2019-07-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=332935

mcadoo.c...@gmail.com changed:

   What|Removed |Added

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

--- Comment #9 from mcadoo.c...@gmail.com ---
Dead key doesn't work in GVim. Thanks

Keyboard: French (AZERT)

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

[dolphin] [Bug 410032] Items in right click-menu are not translated

2019-07-20 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=410032

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #1 from Antonio Rojas  ---
Those are Qt strings, do you have qt5-translations installed?

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

  1   2   >