date:20190130

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

Bug ID: 403794
   Summary: For components no function of the context menu entries
Component, Port and Artifact
   Product: umbrello
   Version: 2.27.1 (KDE Applications 18.12.1)
  Platform: Other
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

The menu items mentioned have no function in component and deployment diagrams.

STEPS TO REPRODUCE
1. start umbrello
2. add component diagram
3. add component
4. select component
5. right click on component
6. select Artifact, Component or Port

OBSERVED RESULT
The mentioned functions are not supported

EXPECTED RESULT
The functions should perform the requested action

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 42.3
KDE Frameworks Version: 5.54
Qt Version: 5.11

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

[KBibTeX] [Bug 403793] New: error in saving unicode-8

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

Bug ID: 403793
   Summary: error in saving unicode-8
   Product: KBibTeX
   Version: 0.8.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Loading/saving files
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: mb.schie...@arcor.de
  Target Milestone: ---

SUMMARY
error in saving unicode-8

STEPS TO REPRODUCE
1. input autor: R{\r{u}}{\v{z}}i{\v{c}}ka ;
2. kbibtex changes this in Růžička - right ;
3. save the bibfile and find:
   author = "R{\r u}{\zcaron}i{\v c}ka"
4. latex stops with error

OBSERVED RESULT
   author = "R{\r u}{\zcaron}i{\v c}ka"

EXPECTED RESULT
autor: "R{\r{u}}{\v{z}}i{\v{c}}ka" ;

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: opensuse Leap 15.0
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.45.0
Qt Version: 5.9.4

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher

2019-01-30 Thread josselin

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

--- Comment #35 from josselin  ---
what I understand is that is a bug with my graphics card driver i915 am
I wrong ? when I was on opensuse I"ve had also dozen messages with
unitialized urandom read issues - due to lack of entropy as I may
understand. Where from issues like those may come to?

Le jeu. 31 janv. 2019 à 08:20, josselin neveux  a
écrit :

> so what do I have to do to fix it? tell me please.
>
> Le ven. 18 janv. 2019 à 00:23, Christoph Feck 
> a écrit :
>
>> https://bugs.kde.org/show_bug.cgi?id=391613
>>
>> --- Comment #33 from Christoph Feck  ---
>> *** Bug 403014 has been marked as a duplicate of this bug. ***
>>
>> --
>> You are receiving this mail because:
>> You are on the CC list for the bug.
>
>
>
> --
>
> Ma boite mail est protégée et nettoyée par cleanfox.io
> 
>

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

[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher

2019-01-30 Thread josselin

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

--- Comment #34 from josselin  ---
so what do I have to do to fix it? tell me please.

Le ven. 18 janv. 2019 à 00:23, Christoph Feck  a
écrit :

> https://bugs.kde.org/show_bug.cgi?id=391613
>
> --- Comment #33 from Christoph Feck  ---
> *** Bug 403014 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[latte-dock] [Bug 403788] Firefox - No option to open private window

2019-01-30 Thread Michail Vourlakos

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

--- Comment #4 from Michail Vourlakos  ---
Can you reproduce with a plasma panel and a plasma taskmanager?

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

2019-01-30 Thread Andras

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

--- Comment #76 from Andras  ---
Also at kdesrc-build --initial-setup I got

Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
m/(\${ <-- HERE MODULE})|(\$MODULE\b)/ at /usr/bin/kdesrc-build line 4759.

Let me know how should I proceed.

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

[kwin] [Bug 403777] Using a shortcut to kill a window in present windows view.

2019-01-30 Thread Martin Flöser

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

Martin Flöser  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #1 from Martin Flöser  ---
Present Windows is not intended for closing windows.

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

2019-01-30 Thread Andras

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

--- Comment #75 from Andras  ---
(In reply to Nate Graham from comment #74)
(Ignore, not question but I hove to note what is it that some still assumes
this place is a miserable playground? So ridiculous LMAO.)
It's nothing serious, I write this because it's just so absurd that I'd gladly
try to build it as you kindly described although believe it or not, for 5 hours
already http://archive.neon.kde.org/user currently isn't available. Obviously
the server is down, unbelievable. Anyhow I'll try later. Also thank you for the
guidance.

"E: The repository 'http://archive.neon.kde.org/user bionic Release' no longer
has a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details."

Let me know if it's possibly not the server but something locally on my (two)
system though.

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

[kdenlive] [Bug 396274] Cannot fold or zoom/unzoom audio tracks

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

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.

[kwin] [Bug 402766] kwin crash for no apparent reason

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |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.

[kdenlive] [Bug 397250] All slowmotion effects in project lost upon saving

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

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.

[kdenlive] [Bug 395803] Rotoscopy undo not working

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[kdenlive] [Bug 396110] "clip problems" window keeps popping up on opening a project despite all clips are in place

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

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 400924] disable clip still doesn't work

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

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

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

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

[krita] [Bug 402347] cursor not change after using mirror tool

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

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

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

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

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

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

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

[kdenlive] [Bug 378576] Kdenlive crashes opening project archive

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

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

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

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

[krita] [Bug 403254] brushstroke

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

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

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

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

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

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

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

[kdenlive] [Bug 397253] Opening error when double click project file

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

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 403277] Krita crashes when changing layer styles

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

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

[frameworks-kirigami] [Bug 403792] PassiveNotification UI element does not work and should be deleted

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

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=388086

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

[frameworks-kirigami] [Bug 388086] showPassiveNotification() should be able to have a close button

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

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=403792

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

[Discover] [Bug 403791] Replace all passivenotification messages with InlineMessages

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

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=403792

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

[frameworks-kirigami] [Bug 403792] PassiveNotification UI element does not work and should be deleted

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

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=403791

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

[frameworks-kirigami] [Bug 403792] New: PassiveNotification UI element does not work and should be deleted

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

Bug ID: 403792
   Summary: PassiveNotification UI element does not work and
should be deleted
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: n...@kde.org
  Target Milestone: Not decided

This UI element displays a tiny pop-up message that disappears automatically
after a few seconds. It does not work and should be removed.

Anything worth showing to the user should not time out after a few seconds or
else it will be missed and the user will be confused and frustrated. If the
message can safely be missed because it's timed out before the user sees or
comprehends it, the it wasn't important enough to show the user.

Furthermore, The UI element's existence encourages abuse by developers.
Discover inappropriately uses PassiveNotifications for everything (Bug 403791),
resulting in important error messages that never get seen by the user and a
neverending stream of un-actionable program status messages that make users
feel nervous and unhappy.

I recommend deleting this UI paradigm and instead recommending the use of
InlineMessages, which are useful because they don't disappear before you've
read them, and they come in multiple colors that convey information about the
message's severity.

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

[Discover] [Bug 403791] New: Replace all passivenotification messages with InlineMessages

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

Bug ID: 403791
   Summary: Replace all passivenotification messages with
InlineMessages
   Product: Discover
   Version: 5.14.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: n...@kde.org
  Target Milestone: ---

Created attachment 117756
  --> https://bugs.kde.org/attachment.cgi?id=117756=edit
Error message that disappeared one second later

Attached is a screenshot showing the error message that Discover displayed
tonight after a failed update (see Bug 403790). Because it was implemented as a
passivenotification, the error message disappeared approximately one second
after I took the screenshot. If I had not been watching and ready with
Spectacle, I would have missed it entirely and been left confused and
frustrated.

These passivenotification messages are awful for the following reasons:

1. They disappear after a few seconds so you can miss them if you're not
staring at Discover while it does its thing
2. Even if you are, they'll probably disappear before you're done reading and
comprehending them
3. Even if you do manage to read and comprehend them, since they've
disappeared, you can't write down the text or copy it for the purpose of
pasting into a web search so you can figure out what to do about the problem
4. They're a totally unfamiliar, alien UI. No other KDE program displays error
messages in tooltip-like pop-ups that disappear after a few seconds

Every time we would display a passivenotification, let's instead use a Kirigami
InlineMessage or a Kirigami overlay sheet, which are both much nicer because
they're persistent and attention-getting.

For any message where this would not be appropriate because it would be really
annoying, that's a sign that we shouldn't be emitting any user-visible error
message at all because it's just noise, not a real error message.

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

[neon] [Bug 403790] Update failure: archive is not yet available?

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

--- Comment #1 from Nate Graham  ---
Created attachment 117755
  --> https://bugs.kde.org/attachment.cgi?id=117755=edit
`pkmon` log of update progress

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

[neon] [Bug 403790] New: Update failure: archive is not yet available?

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

Bug ID: 403790
   Summary: Update failure: archive is not yet available?
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: n...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 117754
  --> https://bugs.kde.org/attachment.cgi?id=117754=edit
Archive is not yet available error

I tried to update my Neon Dev Unstable VM today and repeatedly got the
following error message (see attached screenshot) from Discover. This
reproduced four times.

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

[latte-dock] [Bug 403788] Firefox - No option to open private window

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

Ben Daines  changed:

   What|Removed |Added

   Platform|Other   |Manjaro

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

[latte-dock] [Bug 403788] Firefox - No option to open private window

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

Ben Daines  changed:

   What|Removed |Added

 CC||benjamindai...@gmail.com

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

[latte-dock] [Bug 403788] Firefox - No option to open private window

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

--- Comment #3 from Ben Daines  ---
Created attachment 117753
  --> https://bugs.kde.org/attachment.cgi?id=117753=edit
Chromium .desktop

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

[latte-dock] [Bug 403788] Firefox - No option to open private window

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

--- Comment #2 from Ben Daines  ---
Created attachment 117752
  --> https://bugs.kde.org/attachment.cgi?id=117752=edit
Firefox .desktop

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

[latte-dock] [Bug 403788] Firefox - No option to open private window

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

--- Comment #1 from Ben Daines  ---
Created attachment 117751
  --> https://bugs.kde.org/attachment.cgi?id=117751=edit
Chrome Context Menu

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

[krita] [Bug 403789] New: crashes and freezes

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

Bug ID: 403789
   Summary: crashes and freezes
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: joey.ca...@gmail.com
  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

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

[latte-dock] [Bug 403788] New: Firefox - No option to open private window

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

Bug ID: 403788
   Summary: Firefox - No option to open private window
   Product: latte-dock
   Version: 0.8.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: benjamindai...@gmail.com
  Target Milestone: ---

Created attachment 117750
  --> https://bugs.kde.org/attachment.cgi?id=117750=edit
Firefox Context Menu

SUMMARY
When right clicking Firefox in the dock there is no option to open a new
private window (or a new window for that matter), just the generic "start new
instance"

STEPS TO REPRODUCE
1. Add Firefox to the plasmoid
2. Right click
3. Observe the lack of afore mentioned option 

OBSERVED RESULT
No option is provided to open a new private window 

EXPECTED RESULT
The desktop actions listed in Firefox's .desktop file should be listed when
right clicking the launcher in Latte.  They are present when this is done with
Chromium, but not for Firefox.  The appropriate desktop action is in the
.desktop file for Firefox, but they are not picked up by Latte.   

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
I'm attaching screenshots of the results I'm seeing, as well as the .desktop
files for Firefox and Chromium

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

[unknown] [Bug 196935] Software sources crashes when marking line with software path

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

joey.ca...@gmail.com changed:

   What|Removed |Added

 CC||joey.ca...@gmail.com

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

[krita] [Bug 403787] New: #ResourceFilters

2019-01-30 Thread susellee

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

Bug ID: 403787
   Summary: #ResourceFilters
   Product: krita
   Version: unspecified
  Platform: Other
OS: OS X
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: susel...@gmail.com
  Target Milestone: ---

SUMMARY
The Resource Filters section is not rendering any results. Krita Version 3.3.3

STEPS TO REPRODUCE
1. Go to the Resource Filters section
2. Type any brush or blender that you want and press enter
3. 

OBSERVED RESULT

No results comes up.


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.

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

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

--- Comment #74 from Nate Graham  ---
(In reply to lega99 from comment #72)
> (In reply to Nate Graham from comment #70)
> I remember when Kali Distribution users were begging to
> be allowed to work with Dolphin as root, they were rejected
You have old information. I fixed that last year: Bug 387974

For anyone who wants to give this a shot, we have fairly good documentation:
https://community.kde.org/Get_Involved/development

It's not that much more than this:

mkdir -p ~/kde
cd ~/kde
git clone git://anongit.kde.org/kdesrc-build.git
cd kdesrc-build
kdesrc-build --initial-setup
- Ubuntu/Kubuntu/Neon: sudo apt build-dep plasma-discover
- Fedora: sudo dnf builddep plasma-discover
- Arch & openSUSE: can't remember, sorry
kdesrc-build discover --include-dependencies
cd ~/kde/src/*/*/discover
git checkout plasma/5.14
kdesrc-build discover --resume-from discover
source ~/kde/build/*/*/discover/prefix.sh
plasma-discover

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

2019-01-30 Thread Wyatt Childers

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

--- Comment #73 from Wyatt Childers  ---
(In reply to lega99 from comment #72)
> (In reply to Nate Graham from comment #70)
> > The stakes are a good bit higher than just you not being able to use
> > Discover for 12 more days: the next version of Debian Stable is going to
> > ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all
> > the Debian users are going to be exposed to this issue if we can't provide a
> > hotfix. That's why I'm asking for testing--so we can know if the proposed
> > fix works.
> I am a retired but I remember when Kali Distribution users were begging to
> be allowed to work with Dolphin as root, they were rejected, as we all know
> Kali is based on Debian. Then Kali users got advice from Plasma developer to
> do it themselves.

What?

> The stakes are a good bit higher than just you not being able to use
> Discover for 12 more days: the next version of Debian Stable is going to
> ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all
> the Debian users are going to be exposed to this issue if we can't provide a
> hotfix. That's why I'm asking for testing--so we can know if the proposed
> fix works.

Unfortunately I can't, no longer have the issue as I got the updated packages
from neon developer edition.

> The problem persists on my system but unfortunately I don't know how to 
> compile source code reverting a commit. :(

Do you know how to compile from source? If it's just the reverting a commit
part, that's relatively simple. You just go to the directory where you've got a
copy of the source code and run `git revert ` or in this case `git
revert 2bd91b93357318c4f7dd96b2f6e7a07dd74494c8`.

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

2019-01-30 Thread lega99

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

--- Comment #72 from lega99  ---
(In reply to Nate Graham from comment #70)
> The stakes are a good bit higher than just you not being able to use
> Discover for 12 more days: the next version of Debian Stable is going to
> ship with Plasma 5.14.5, which means Discover 5.14.5, which means that all
> the Debian users are going to be exposed to this issue if we can't provide a
> hotfix. That's why I'm asking for testing--so we can know if the proposed
> fix works.
I am a retired but I remember when Kali Distribution users were begging to be
allowed to work with Dolphin as root, they were rejected, as we all know Kali
is based on Debian. Then Kali users got advice from Plasma developer to do it
themselves.

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

[print-manager] [Bug 397125] print-manager should provide information regarding where the password is getting sent and the characteristics of the server

2019-01-30 Thread Steven De Herdt

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

--- Comment #9 from Steven De Herdt  ---
(In reply to Michael Weghorn from comment #8)
> @Steven: Are you currently looking at this? If so, feel free to take over
> anything you can user from my "demo". Otherwise, I can have another look and
> create a change on Phabricator as well. Whatever fits better for you...

That's considerate of you Michael, but I haven't done any more work than
exploring the source and experimenting a bit with cups.  So on the contrary,
I'm happy someone who seems to know what they're doing is working on this. 
Please go ahead and submit a patch!

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

[kdeconnect] [Bug 403786] New: KDE Connect crashes on start

2019-01-30 Thread Carlos Massucci

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

Bug ID: 403786
   Summary: KDE Connect crashes on start
   Product: kdeconnect
   Version: 1.3.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: albertv...@gmail.com
  Reporter: duffm...@gmail.com
  Target Milestone: ---

SUMMARY
Kdeconnect crashes on start.

STEPS TO REPRODUCE
1. Open kdeconnect
2. Click refresh (Atualizar in portuguese)

OBSERVED RESULT
It does not locate any device. KDE GUI keeps on screen but without any device.

EXPECTED RESULT
My Android device should apear.

SOFTWARE/OS VERSIONS
uname -a:

Linux Neon 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux

KDEconnect version: 1.3.3-0xneon+18.04+bionic+build10

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
I have installed KDE Neon this week.

Application: kdeconnectd (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3c69c4d800 (LWP 6255))]

Thread 4 (Thread 0x7f3c4e0b7700 (LWP 6258)):
#0  0x7ffe6a0ab979 in ?? ()
#1  0x7ffe6a0abc30 in clock_gettime ()
#2  0x7f3c670bcea6 in __GI___clock_gettime (clock_id=1, tp=0x7f3c4e0b6b80)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f3c679da951 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3c679d9189 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3c679db7a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3c61b13f51 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f3c61b144e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f3c61b1464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f3c679db04b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f3c6797f30a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f3c677aabba in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f3c677b5adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f3c6385a6db in start_thread (arg=0x7f3c4e0b7700) at
pthread_create.c:463
#14 0x7f3c670ad88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f3c4e8b8700 (LWP 6257)):
#0  0x7f3c670a0bf9 in __GI___poll (fds=0x7f3c48020400, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3c61b14539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3c61b1464c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3c679db04b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3c6797f30a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3c677aabba in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3c6619ce45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f3c677b5adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3c6385a6db in start_thread (arg=0x7f3c4e8b8700) at
pthread_create.c:463
#9  0x7f3c670ad88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3c57d95700 (LWP 6256)):
#0  0x7f3c670a0bf9 in __GI___poll (fds=0x7f3c57d94ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3c5ffda747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f3c5ffdc36a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3c5ad55ed9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f3c677b5adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3c6385a6db in start_thread (arg=0x7f3c57d95700) at
pthread_create.c:463
#6  0x7f3c670ad88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f3c69c4d800 (LWP 6255)):
[KCrash Handler]
#6  0x7f3c66d1d277 in
QSslCertificate::subjectInfo(QSslCertificate::SubjectInfo) const () from
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#7  0x7f3c6983cfa0 in KdeConnectConfig::deviceId() () from
/usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1
#8  0x7f3c6984075a in NetworkPacket::createIdentityPacket(NetworkPacket*)
() from /usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1
#9  0x7f3c69820ae6 in LanLinkProvider::broadcastToNetwork() () from
/usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1
#10 0x7f3c679b018f in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f3c679bce47 in

[okular] [Bug 403755] Highlight does not work on rotated pages

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

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

--- Comment #2 from Viorel-Cătălin Răpițeanu  ---
Confirmed this behaviour using:

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.90
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0-3

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

[systemsettings] [Bug 402930] After you use the image picker to change the background image, your chosen image appears in the picker, but disappears if you navigate away from the KCM and then go back

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

--- Comment #6 from Nate Graham  ---
It turns out that the breakage I encountered while trying patches to fix this
bug is a pre-existing issue that was not introduced with my patch:
https://github.com/sddm/sddm/issues/1132

Both patches actually worked!

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

[plasmashell] [Bug 403785] New: Viewing certain wifi access points, restarted plasmashell

2019-01-30 Thread Daryn

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

Bug ID: 403785
   Summary: Viewing certain wifi access points, restarted
plasmashell
   Product: plasmashell
   Version: 5.12.7
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mrhamm...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.7)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-44-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

-- Information about the crash:
I was constantly refreshing the wifi access points list to check when a certain
one was going to vanish, since I unplugged the router broadcasting it. Then
plasmashell just restarted on me (full blackscreen, seconds later desktop
slowly starting re-appearing). I am filing a bug report as an in case it is
something needing to be addressed, I couldn't get it to happen again by doing
the same steps, unless I just didn't do it as long as before (just constant
refresh's of the list, while scrolling the list). It might have just as well
been too much running on my computer, such as program conflicts.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fce9ff11800 (LWP 1579))]

Thread 19 (Thread 0x7fcd911fc700 (LWP 27414)):
#0  0x7fce98d839f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55621f14bfd4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fce98d839f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55621f14bf80, cond=0x55621f14bfa8) at pthread_cond_wait.c:502
#2  0x7fce98d839f3 in __pthread_cond_wait (cond=0x55621f14bfa8,
mutex=0x55621f14bf80) at pthread_cond_wait.c:655
#3  0x7fce99bfd59b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce9d9826a8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fce9d982b0a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fce99bfc16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce98d7d6db in start_thread (arg=0x7fcd911fc700) at
pthread_create.c:463
#8  0x7fce994f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 18 (Thread 0x7fcd91ffd700 (LWP 22991)):
#0  0x7fce98d839f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fce8402a460) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fce98d839f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fce8402a410, cond=0x7fce8402a438) at pthread_cond_wait.c:502
#2  0x7fce98d839f3 in __pthread_cond_wait (cond=0x7fce8402a438,
mutex=0x7fce8402a410) at pthread_cond_wait.c:655
#3  0x7fce99bfd59b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce9d9826a8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fce9d982b0a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fce99bfc16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce98d7d6db in start_thread (arg=0x7fcd91ffd700) at
pthread_create.c:463
#8  0x7fce994f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7fcd927fe700 (LWP 22904)):
#0  0x7fce98d839f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fcd8400e724) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fce98d839f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7fcd8400e6d0, cond=0x7fcd8400e6f8) at pthread_cond_wait.c:502
#2  0x7fce98d839f3 in __pthread_cond_wait (cond=0x7fcd8400e6f8,
mutex=0x7fcd8400e6d0) at pthread_cond_wait.c:655
#3  0x7fce99bfd59b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fce9d9826a8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fce9d982b0a in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fce99bfc16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fce98d7d6db in start_thread (arg=0x7fcd927fe700) at
pthread_create.c:463
#8  0x7fce994f788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fcd92fff700 (LWP 22903)):
#0  0x7fce994eabf9 in __GI___poll (fds=0x7fcd84001b30, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fce8efdb451 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7fce8efcce10 in pa_mainloop_poll () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fce8efcd4a0 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fce8efcd530 in pa_mainloop_run () at

[okular] [Bug 403782] Okular trying to save a PDF to an URL location

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

Viorel-Cătălin Răpițeanu  changed:

   What|Removed |Added

Version|unspecified |1.6.1
 CC||rapiteanu.cata...@gmail.com
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Viorel-Cătălin Răpițeanu  ---
I can confirm that this behaviour is reproducing with the latest 1.6.1 version.

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

[Falkon] [Bug 403684] SpeedDial - Add option to lock dials positions

2019-01-30 Thread Alexander Browne

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

Alexander Browne  changed:

   What|Removed |Added

 CC||alexan...@elcste.com

--- Comment #1 from Alexander Browne  ---
I agree with this suggestion!

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

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

--- Comment #71 from Patrick Silva  ---
The problem persists on my system but unfortunately I don't know how to compile
source code reverting a commit. :(

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

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

--- Comment #70 from Nate Graham  ---
The stakes are a good bit higher than just you not being able to use Discover
for 12 more days: the next version of Debian Stable is going to ship with
Plasma 5.14.5, which means Discover 5.14.5, which means that all the Debian
users are going to be exposed to this issue if we can't provide a hotfix.
That's why I'm asking for testing--so we can know if the proposed fix works.



I will reiterate my call for testing: if anyone here is experiencing this issue
in Plasma 5.14.5 and has the ability to compile from source and test a patch,
could that person/those persons try building Discover from the Plasma/5.14
branch with this commit reverted:
https://cgit.kde.org/discover.git/commit/?h=Plasma/5.14=2bd91b93357318c4f7dd96b2f6e7a07dd74494c8

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

[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available

2019-01-30 Thread lega99

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

--- Comment #69 from lega99  ---
(In reply to Nate Graham from comment #68)


I would compile, but I do not know. I tried to compile the last corrected
correction but I failed. I worked in a way that Dr.Calsav Ilic showed me when I
successfully compiled a correction of the holidays in the Serbian calendar. Now
it can not be compiled in this way. A new plasma is coming out in 12 days, we
waited for the first updates, failed, we are waiting for a new plasma, says
Aldin in the cartoon: patience Siago

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

[kwin] [Bug 403702] Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher

2019-01-30 Thread Matt

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

--- Comment #6 from Matt  ---
Again, noticing some interesting aspects to this that were I had failed to
notice earlier. Locking the session and re-entering, or simply closing the lid
and re-opening it  will return the meta key to its intended function.

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

[kwin] [Bug 403702] Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher

2019-01-30 Thread Matt

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

--- Comment #5 from Matt  ---
META KEYPRESS WHEN META KEY IS WORKING:

KeyPress event, serial 40, synthetic NO, window 0x421,
root 0x168, subw 0x0, time 3689931, (166,-19), root:(1199,10),
state 0x0, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x421,
root 0x168, subw 0x0, time 3690089, (166,-19), root:(1199,10),
state 0x40, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False



RADIO KEYPRESS

KeyPress event, serial 40, synthetic NO, window 0x21,
root 0x168, subw 0x0, time 3850405, (164,-12), root:(1197,17),
state 0x0, keycode 255 (keysym 0x1008ffb5, XF86RFKill), same_screen YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x21,
root 0x168, subw 0x0, time 3850405, (164,-12), root:(1197,17),
state 0x0, keycode 255 (keysym 0x1008ffb5, XF86RFKill), same_screen YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

META KEYPRESS AFTER RADIO SWITCH

KeyPress event, serial 40, synthetic NO, window 0x421, 
   root 0x168, subw 0x0, time 77107, (167,-21), root:(1200,8), 
   state 0x0, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES, 
   XLookupString gives 0 bytes:  
   XmbLookupString gives 0 bytes:  
   XFilterEvent returns: False 

KeyRelease event, serial 40, synthetic NO, window 0x421, 
   root 0x168, subw 0x0, time 78026, (167,-21), root:(1200,8), 
   state 0x40, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES, 
   XLookupString gives 0 bytes:  
   XFilterEvent returns: False

NOTE: As I was running xev, there was one instance where the Meta Key did not
fail as described. However, after a restart, it returned to the previously
stated semi-functionality

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

[dolphin] [Bug 403784] New: ssh X forwarding: clicking a file opens window on remote

2019-01-30 Thread Abhishek Anand

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

Bug ID: 403784
Summary: ssh X forwarding: clicking a file opens window on
remote
Product: dolphin
Version: 18.12.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: abhishek.anand.i...@gmail.com
CC: elvis.angelac...@kde.org
Target Milestone: ---

SUMMARY
When dolphin is opened over SSH X forwarding, clicking on a file (e.g. abc.png)
opens the corresponding graphical application on the DISPLAY of the remote
machine (DISPLAY=:0) and not on of the SSH client.

STEPS TO REPRODUCE
1. ssh -Y remote
2. dolphin .
3. click on a .png file

OBSERVED RESULT
the gwenview window opens on the remote machine.

EXPECTED RESULT
the gwenview window should open on the client

SOFTWARE/OS VERSIONS
Windows:
MacOS:
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
Most likely, it affects all versions of plasma.
Instead of directly opening the clicked file, it seems dolphin sends a message
to plasmashell to open the file; dolphin is not the parent of the new graphical
process (e.g. gwenview, the parent is plasmashell.
plasmashell uses DISPLAY=:0. so the new window opens on the remote machine.
https://unix.stackexchange.com/questions/496814/ssh-x-forwarding-gui-window-opens-on-remote?noredirect=1

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

[dolphin] [Bug 403784] ssh X forwarding: clicking a file opens window on remote

2019-01-30 Thread Abhishek Anand

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

Abhishek Anand  changed:

   What|Removed |Added

 CC||abhishek.anand.iitg@gmail.c
   ||om

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

[frameworks-kwidgetsaddons] [Bug 399681] allow date picker date to roll across month boundaries

2019-01-30 Thread Jack

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

--- Comment #6 from Jack  ---
OK, my bad for not digging deeper.  The + and - do exactly what I want.  

The doc which you link to is also identical in stable5, which just reminds me
how far behind I am in updating the manual for 5.x.

This is already a wishlist - should I reassign to KMM specifically to extend
the +/- behavior to the up and down arrow keys, and optionally, the up and down
arrows to the right of the line edit.

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

[kmymoney] [Bug 402801] Time to find another checking program as Tags is screwing up Kmymoney.

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

--- Comment #10 from deanmalb...@yahoo.com ---
Thomas,

I have tried build #161 appimage and it does not work.  Changes were supposedly
made in build #162 but the appimage failed to be captured.  I have been waiting
for a newer build that has a completed appimage, but all builds from 162 to 165
failed.
I can't test the issues until a completed appimage is available.

Dean Albert

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

--- Comment #9 from Thomas Baumgart  ---
The remaining issues are:

2) usage issue (we wait for feedback from original poster)
3) I don't know what that should be since I cannot duplicate it
4) wishlist item: make tags a plugin which can be disabled

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

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

[frameworks-syntax-highlighting] [Bug 395079] mediatype operator "prefers-reduced-motion" will break logical structure of highlighting

2019-01-30 Thread Dominik Haumann

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

--- Comment #2 from Dominik Haumann  ---
Can you please attach a screenshot with the broken version? In my version it
looks fine.

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

[latte-dock] [Bug 403780] Panel shadow appears after clicking on plasmoid with drop-down list

2019-01-30 Thread Michail Vourlakos

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

--- Comment #1 from Michail Vourlakos  ---
(In reply to zomial from comment #0)
> Created attachment 117747 [details]
> Demonstration of the bug on the global menu plasmoid
> 
> SUMMARY
> When we click on plasmoid with drop-down list/menu (e.g. Application Menu,
> Global Menu, System Tray etc.), even if the panel shadow if off, it becomes
> visible. When the drop-down menu is collapsed, the shadow is invisible
> again, as expected. 
>

concerning the applets pop-ups such as System tray, calendars, Application
Launchers etc. this is intentional because all of these popups contain shadows
from the plasma theme and as such for consistency Latte also draws them


for the Global Menu I agree the effect is not that nice and the shadow shouldnt
be drawn, probably a blacklist for that applet should take place...

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

[frameworks-syntax-highlighting] [Bug 382950] Indenter: Lua "function " keyword picked up in string

2019-01-30 Thread Dominik Haumann

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

Dominik Haumann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||de...@the-user.org
 Status|REPORTED|CONFIRMED

--- Comment #1 from Dominik Haumann  ---
@Jonathan, since you are the author of the lua.js, could you have a look into
this?
https://phabricator.kde.org/source/ktexteditor/browse/master/src/script/data/indentation/lua.js

I guess with functions like document.isCode(), isString(), isComment() etc.
this probabl can easily be fixed. See API in:
https://phabricator.kde.org/source/ktexteditor/browse/master/src/script/katescriptdocument.h

See also:
https://docs.kde.org/stable5/en/applications/katepart/dev-scripting.html

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

[kmymoney] [Bug 400761] Cannot open files on MacOS

2019-01-30 Thread Matthias Jung

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

--- Comment #8 from Matthias Jung  ---
yes here it is: 

```
QPainter::begin: Paint device returned engine == 0, type: 2
WebConnect: Try to connect to WebConnect server
WebConnect: Connect to server failed
WebConnect: Running in server mode
Custom icons were not found in any of the following
QStandardPaths::AppDataLocation:
"/Users/myzinsky/Library/Application Support/kmymoney"
"/Users/packaging/Craft/BinaryCache/macos-64-clang/share/kmymoney"
"/Library/Application Support/kmymoney"
"/Users/myzinsky/Desktop/kmymoney.app/Contents/Resources"
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QFSFileEngine::open: No file name specified
Plugins: budgetview loaded
Plugins: checkprinting loaded
QIODevice::read (QFile,
"/Volumes/kmymoney-master-253-macos-64-clang/kmymoney.app/Contents/Resources/checkprinting/check_template.html"):
device not open
Plugins: csvexporter loaded
Plugins: csvimporter loaded
Plugins: forecastview loaded
Plugins: gncimporter loaded
Plugins: icalendarexporter loaded
Plugins: kbanking loaded
3:2019/01/30
22-04-33:gwen(55767):/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/gwenhywfar/work/gwenhywfar-4.20.0/src/base/plugin.c:
 379: Plugin "dir" not found.
3:2019/01/30
22-04-33:(null)(55767):/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/aqbanking/work/aqbanking-5.7.8/src/libs/aqbanking/banking_cfg.c:
  77: Could not create ConfigMgr[dir:///Users/myzinsky/.aqbanking/settings].
Maybe the gwenhywfar plugins are not installed?
3:2019/01/30
22-04-33:(null)(55767):/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/aqbanking/work/aqbanking-5.7.8/src/libs/aqbanking/banking_cfg.c:
 100: No config manager. Maybe the gwenhywfar plugins are not installed
correctly?
KBankingPlugin: No AqB4 config found.
KBankingPlugin: No AqB3 config found.
3:2019/01/30
22-04-33:aqbanking(55767):/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/aqbanking/work/aqbanking-5.7.8/src/libs/aqbanking/banking_cfg.c:
 712: No config manager. Maybe the gwenhywfar plugins are not installed
correctly?
Error on online init (-1).
Could not initialize KBanking online banking interface
Plugins: ofximporter loaded
Plugins: onlinejoboutboxview loaded
Plugins: qifexporter loaded
Plugins: qifimporter loaded
Plugins: reconciliation report loaded
Plugins: reportsview loaded
Plugins: sqlstorage loaded
Plugins: xmlstorage loaded
Couldn't start kuiserver from org.kde.kuiserver.service:
QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus
server")
kf5.kio.core: couldn't create slave: "Can not find 'kioslave' executable at
'/Users/myzinsky/Desktop/kmymoney.app/Contents/MacOS,
/Users/myzinsky/Desktop/kmymoney.app/Contents/libexec,
/Users/packaging/Craft/BinaryCache/macos-64-clang/lib/libexec/kf5'"
```

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

[plasmashell] [Bug 403783] Laptop running Plasma slows down when 2nd monitor is plugged in via HDMI

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

--- Comment #1 from techxga...@outlook.com ---
Just confirmed that VGA doesn't suffer from that same problem

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

[kmail2] [Bug 403007] KMail crashes by selecting freshly arrived unread mails

2019-01-30 Thread Christoph Feck

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

--- Comment #11 from Christoph Feck  ---
KMail uses the Chromium web engine (via QtWebEngine) to display mails. This web
engine internally uses OpenGL from multiple threads, which the Nouveau OpenGL
driver fails to handle.

Other KDE applications do not use QtWebEngine.

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

[plasmashell] [Bug 403783] New: Laptop running Plasma slows down when 2nd monitor is plugged in via HDMI

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

Bug ID: 403783
   Summary: Laptop running Plasma slows down when 2nd monitor is
plugged in via HDMI
   Product: plasmashell
   Version: 5.14.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: techxga...@outlook.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 117748
  --> https://bugs.kde.org/attachment.cgi?id=117748=edit
Screenshot of KSysGuard with montor plugged in via HDMI

SUMMARY
A laptop running Plasma slows down significantly when a secondary monitor is
plugged in via HDMI.  Doesn't seem to slow down when plugged in via VGA.

STEPS TO REPRODUCE
1. Plug the the monitor to the laptop via HDMI
2. You'll notice the sluggish performance immediately
3. 

OBSERVED RESULT
Clock frequency stays at <1GHz most of the time.

EXPECTED RESULT
Performance shouldn't degrade

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
Intel Core i7-4510U
16GB RAM

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

[okular] [Bug 403782] New: Okular trying to save a PDF to an URL location

2019-01-30 Thread avlas

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

Bug ID: 403782
   Summary: Okular trying to save a PDF to an URL location
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

SUMMARY

Not sure this is an issue of okular (or kio or ...), but when saving a pdf file
in okular that was loaded via an URL with ctrl+shift+s (save as), okular
defaults the path to the URL as if it was a local path.


STEPS TO REPRODUCE
1. Open Okular
2. Open file
3. Set a URL to a pdf file, e.g.,
https://www.biorxiv.org/content/biorxiv/early/2019/01/27/
4. Save the PDF file (save as ctrl + shift +s)

OBSERVED RESULT

Okular tries to save the above PDF file to
https://www.biorxiv.org/content/biorxiv/early/2019/01/27/

EXPECTED RESULT

Okular should default to a local path (e.g., $HOME, or Downloads, or Documents,
or last path used) instead of the original remote URL


SOFTWARE/OS VERSIONS

KDE neon 5.14
Plasma 5.14.5
Qt 5.11.2
Frameworks 5.54.0
Linux 4.18.0-14-generic
64 bits

ADDITIONAL INFORMATION

Copying Info from About System should have an option to copy in English to ease
bug reporting ;)

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

[kmymoney] [Bug 400761] Cannot open files on MacOS

2019-01-30 Thread Thomas Baumgart

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

Thomas Baumgart  changed:

   What|Removed |Added

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

--- Comment #7 from Thomas Baumgart  ---
Do you see any output if you start the application on a command line? If so,
can you share it here?

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

[kmymoney] [Bug 400761] Cannot open files on MacOS

2019-01-30 Thread Matthias Jung

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

--- Comment #6 from Matthias Jung  ---
I can save a new file, but I cannot open it.

Is there anything that I could do to figure out what happens?

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

[neon] [Bug 403781] Okular crashes on startup

2019-01-30 Thread soundconjurer

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

soundconjurer  changed:

   What|Removed |Added

   Platform|unspecified |Kubuntu Packages

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

[neon] [Bug 403781] New: Okular crashes on startup

2019-01-30 Thread soundconjurer

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

Bug ID: 403781
   Summary: Okular crashes on startup
   Product: neon
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Snaps
  Assignee: sit...@kde.org
  Reporter: palemastervolr...@gmail.com
CC: neon-b...@kde.org
  Target Milestone: ---

SUMMARY
Starting Okular snap crashes now.

STEPS TO REPRODUCE
1. Open okular or open a pdf.
2. Wait for it to load.
3. Observe error message.

OBSERVED RESULT
Dialogue Message:
Unable to find the Okular component: Cannot load library
/snap/okular/39/usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so:
(libKF5JSApi.so.5: cannot open shared object file: No such file or directory)

EXPECTED RESULT
Okular starts normally.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04 LTS

ADDITIONAL INFORMATION

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

[latte-dock] [Bug 403780] Panel shadow appears after clicking on plasmoid with drop-down list

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

zom...@yandex.ru changed:

   What|Removed |Added

 CC||zom...@yandex.ru

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

[latte-dock] [Bug 403780] New: Panel shadow appears after clicking on plasmoid with drop-down list

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

Bug ID: 403780
   Summary: Panel shadow appears after clicking on plasmoid with
drop-down list
   Product: latte-dock
   Version: git (master)
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: zom...@yandex.ru
  Target Milestone: ---

Created attachment 117747
  --> https://bugs.kde.org/attachment.cgi?id=117747=edit
Demonstration of the bug on the global menu plasmoid

SUMMARY
When we click on plasmoid with drop-down list/menu (e.g. Application Menu,
Global Menu, System Tray etc.), even if the panel shadow if off, it becomes
visible. When the drop-down menu is collapsed, the shadow is invisible again,
as expected. 

STEPS TO REPRODUCE
1. Turn off the panel shadow (Appearance - Background - The "shadow" button is
unpressed)
2. Add a plasmoid with drop-down list to dock/panel
3. Click on that plasmoid with left mouse button

OBSERVED RESULT
Panel now has a shadow.

EXPECTED RESULT
Panel shouldn't have a shadow, because we turned it off in the settings.

SOFTWARE/OS VERSIONS
Latte Dock: 0.8.75 (git)
Linux/KDE Plasma: 
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
Also I compiled from source this kwin patch
(https://github.com/alex47/KDE-Rounded-Corners), which rounds corners of
borderless windows, but due a bug in this patch it also makes corners round on
other entities (not only windows), so when I click on a plasmoid with a
drop-down list panel now have round corners too. Maybe a shadow and round
corners appears due the same reason.

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

[dolphin] [Bug 403779] Iinfo

2019-01-30 Thread Klaudio Berger

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

--- Comment #1 from Klaudio Berger  ---
Created attachment 117746
  --> https://bugs.kde.org/attachment.cgi?id=117746=edit
Screenshot of the Information Panel 01

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

[dolphin] [Bug 403779] New: Iinfo

2019-01-30 Thread Klaudio Berger

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

Bug ID: 403779
   Summary: Iinfo
   Product: dolphin
   Version: 18.12.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: klaudiober...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Created attachment 117745
  --> https://bugs.kde.org/attachment.cgi?id=117745=edit
Screenshot of the Information Panel

The "Information Panel" cant be fixed in position, every time i restart Dolphin
the panel is out of position.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.14
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.2
Kernel Version: 4.13.0-45-generic and 4.20.0-1-default

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

[kded-appmenu] [Bug 403778] New: Menu displayed twice

2019-01-30 Thread Lach Sławomir

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

Bug ID: 403778
   Summary: Menu displayed twice
   Product: kded-appmenu
   Version: 5.14.5
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: menu popup
  Assignee: plasma-b...@kde.org
  Reporter: sla...@lach.art.pl
  Target Milestone: ---

SUMMARY
After upgrading to libreoffice 6.2.0.3, writter displays, when pressing menu
button on titlebar.
Distribution: OpenSuSE Tumbleweed.
Other part of LibreOffice suite wasn't tested and other distros than OpenSuSE
TW wasn't tested.

STEPS TO REPRODUCE
1. Update system, using zypper dup (as root)
2. After update turn on putting menu in titlebar
3. Run Writter

OBSERVED RESULT
Menu is displayed twice - one below previous.

EXPECTED RESULT
Only single menu is displayed (each option is present only one in menu)


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

ADDITIONAL INFORMATION
I'm not an expert, but there's work to support LibreOffice menu in titlebar.
Maybe LibreOffice team integrate ones' code with newer menu standards.

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

[ark] [Bug 402824] Ark doesn’t show progression when creating an archive

2019-01-30 Thread ariasuni

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

--- Comment #2 from ariasuni  ---
The reported behavior affects all kinds of archives.

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

[kwin] [Bug 403777] New: Using a shortcut to kill a window in present windows view.

2019-01-30 Thread Jakub Strzelecki

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

Bug ID: 403777
   Summary: Using a shortcut to kill a window in present windows
view.
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kuba...@gmail.com
  Target Milestone: ---

SUMMARY
Additional more convineint way to close a window.

STEPS TO REPRODUCE
1. Go to present windows view.
2. Try to alt+f4 and middle mouse click.

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
Window closes.

SOFTWARE/OS VERSIONS
Windows: X
MacOS: X
Linux/KDE Plasma: 4.20.4 / 5.14.5
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
.

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

[kdeconnect] [Bug 403593] kdeconnectd crashes when receiving notifications from phone

2019-01-30 Thread Heiko Becker

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

Heiko Becker  changed:

   What|Removed |Added

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

--- Comment #2 from Heiko Becker  ---
Yes, that seems to have helped as far as I can tell. No crash in the last 3
days.

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

[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions

2019-01-30 Thread B Stewart

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

--- Comment #11 from B Stewart  ---
John,
You asked "Where do I find the 'shot change list'?"
you'll find it in the "Clip Properties" window, scroll down the icons to the
right of the window to the icon that looks like an eye "Analysis data".
This can be exported to a text file by clicking the middle icon under the
window.
The list looks like:-

shot_change_list=1=25382/0:0x0:0;300=7663;648=6540;827=5105;1416=7401;1716=6503

The number following each ";" is the frame number of each shot change. This has
to be divided by the framerate to create a time in seconds at which to set the
"guide" marks. If the framerates for the clip don't match the project a load of
low numbers seem to appear - don't know why.

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

[kwin] [Bug 403749] Drag-n-drop moves a maximized borderless origin position instead of restoring it when using a 1.5 display scale

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

--- Comment #4 from Viorel-Cătălin Răpițeanu  ---
Created attachment 117744
  --> https://bugs.kde.org/attachment.cgi?id=117744=edit
kwinrc file

I don't have any breezerc file.

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

[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions

2019-01-30 Thread B Stewart

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

--- Comment #10 from B Stewart  ---
Hi John,
I typed in a lng step by step how to do it as a reply to your post but you
must have added your last comment while I was typing and I lost it all.

The important steps are:-
1. Start with a fresh project.
2. Open one clip only.
3. Make sure the project framerate matches the clip framerate.
4. Add the clip to the timeline at time 0.
5. Right click the clip in the "Project Bin" and select "Clip Jobs/Automatic
scene split" and tick "Save result in metadata clip"
6. Wait until the progress bar finishes - can take a while for long clips.
7. Save the project - eg "Save As test" creaates test.kdenlive.
8. Run my script on the created file - a new file appears eg test_new.kdenlive.
9. Open the new file in kdenlive.

If its "oversensitive" ie you have markers early on where there is no scene
change, this happens if steps 3, 4 or 5 are not done in order!

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

[kwin] [Bug 403749] Drag-n-drop moves a maximized borderless origin position instead of restoring it when using a 1.5 display scale

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

--- Comment #3 from Viorel-Cătălin Răpițeanu  ---
(In reply to Vlad Zagorodniy from comment #2)
> Hmmm, can't reproduce. Could you please post your kwinrc and breezerc?
> 
> > 2. Add a 1.5 scale for your output
> So... This happens only with 1.5 scaling factor, right?

This reproduce on 2 different computers with 1.5 scale. This doesn't happen
when there isn't any scaling (scale 1).

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

[kdesrc-build] [Bug 402901] kdesrc-build --initial-setup reports "* No installer for linux!" when executing the command on Debian 9 stable and Fedora 29

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

Nate Graham  changed:

   What|Removed |Added

Summary|kdesrc-build|kdesrc-build
   |--initial-setup reports "*  |--initial-setup reports "*
   |No installer for linux!"|No installer for linux!"
   |when executing the command  |when executing the command
   |on Debian 9 stable  |on Debian 9 stable and
   ||Fedora 29

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

[Powerdevil] [Bug 403776] New: Powerdevil suddenly crashes during normal operation

2019-01-30 Thread mthw0

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

Bug ID: 403776
   Summary: Powerdevil suddenly crashes during normal operation
   Product: Powerdevil
   Version: 5.14.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jari...@hotmail.com
  Target Milestone: ---

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

See 'Log'

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.54
Qt Version: 5.12

ADDITIONAL INFORMATION
On wayland

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

[plasmashell] [Bug 393781] wallpaper cannot span multiple screens

2019-01-30 Thread P

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

P  changed:

   What|Removed |Added

 CC||pavila10...@gmail.com

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

[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions

2019-01-30 Thread John Bell

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

--- Comment #9 from John Bell  ---
I have got it so it created _new.kdenlive which has the original clip 
with markers at the scene changes it has found (a little more sensitive 
than I would expect, but that is an error in the right direction) but 
without splitting the scenes as it used to do with earlier versions of 
Kdenlive.  But I can live with this as a workaround.  New versions is 
being promised later this year - I hope this can be fixed in the base 
Kdenlive including the scene split. Somewhere they need to give guidance 
on making the project frame rate match the clip frame rate as it was not 
obvious to me at the time.

Thanks Brian,

John

On 1/30/19 1:24 PM, John wrote:
> Thanks Brian.  Where do I find the 'shot change list'?
>
> From your other email I think part of my problem may have been not 
> having the project frame rate match the clip frame rate, but fixing 
> that has not been a complete fix - still trying to make it work.
>
> I tried your script and again cannot find the output from it but I am 
> still looking ...
>
> John
>
> On 1/30/19 8:24 AM, B Stewart wrote:
>> https://bugs.kde.org/show_bug.cgi?id=389624
>>
>> B Stewart  changed:
>>
>>     What    |Removed |Added
>>  
>>
>>   CC| |every-...@outlook.com
>>
>> --- Comment #6 from B Stewart  ---
>> Created attachment 117730
>>    --> https://bugs.kde.org/attachment.cgi?id=117730=edit
>> screen shot after running my script
>>
>> This is also a problem for me, and it seems to have been around for a 
>> few
>> years!
>>
>> I'm currently using kdenlive 18.08.2 on Ubuntu 18.08
>>
>> I have a temporary workaround that works for me.
>>
>>
>> If the (Save result in clip metadata) is checked from (Clip 
>> Jobs/Automatic
>> scene split) then the clip is analysed (can take a few minutes to 
>> complete) and
>> the scene change frames are available as a "shot change list".
>> The number between each ";" and "=" is the frame number where the scene
>> changes.
>> This info is also available in the saved .kdenlive file.
>>
>> I have written a Python3 script (about 70 lines of code) which reads the
>> kdenlive file and creates a copy of it with "guide marks" at each 
>> shot change.
>> This can be opened with kdenlive, which then shows where all the shot 
>> changes
>> occur.
>>
>> It is a simple workaround to a problem that seems to have been around 
>> for ages.
>>
>

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

[Breeze] [Bug 403595] Icon request: histogram in LabPlot

2019-01-30 Thread Alexander Semke

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

--- Comment #4 from Alexander Semke  ---
(In reply to Nate Graham from comment #3)
> If you don't already know about it, allow me to introduce you to the
> Cuttlefish icon viewer app. It's really quite handy for browsing icons.
Dolphin in the symbol view with the activated preview usually does the job for
me. This time I just didn't think about checking what is already existing since
I assumed this icon is very "labplot specific" and requires a new icon
request...

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

[systemsettings] [Bug 403775] Impossible to reset cursor size to "Resolution dependent"

2019-01-30 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

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

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

[kdesrc-build] [Bug 402901] kdesrc-build --initial-setup reports "* No installer for linux!" when executing the command on Debian 9 stable

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |critical
   Priority|NOR |VHI

--- Comment #3 from Nate Graham  ---
Bumping priority since we also have a report of this on Fedora 29 with Qt
5.11.3, so for this one the problem is probably not that the System's Qt is too
old.

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

[krita] [Bug 403676] Converting vector layer to paint layer crops the content of the vector layer beyond canvas boundaries

2019-01-30 Thread mvowada

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

mvowada  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from mvowada  ---
Thanks. Assuming it is unwanted (i.e. size limits) I can confirm with 4.2.0 on
Ubuntu 14.04.

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

[umbrello] [Bug 403763] Displayed name of an interface in a component diagram is not updated

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

--- Comment #1 from Ralf Habacker  ---
Git commit 96d20006958d6f337ab4cd34957b1e8e901997b2 by Ralf Habacker.
Committed on 30/01/2019 at 18:55.
Pushed by habacker into branch 'Applications/18.12'.

Add test file for component diagram elements and associations

A  +248  -0models/diagrams/component/all-associations.xmi
A  +170  -0models/diagrams/component/all-elements.xmi

https://commits.kde.org/umbrello/96d20006958d6f337ab4cd34957b1e8e901997b2

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

[umbrello] [Bug 403763] Displayed name of an interface in a component diagram is not updated

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

Ralf Habacker  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/umb
   ||rello/0b46604faae48016f8dd7
   ||dcb34fdcb8c9857bd64
 Resolution|--- |FIXED
   Version Fixed In||2.27.2 (KDE Applications
   ||18.12.2)
 Status|REPORTED|RESOLVED

--- Comment #2 from Ralf Habacker  ---
Git commit 0b46604faae48016f8dd7dcb34fdcb8c9857bd64 by Ralf Habacker.
Committed on 30/01/2019 at 17:28.
Pushed by habacker into branch 'Applications/18.12'.

Fix 'Displayed name of an interface in a component diagram is not updated'
FIXED-IN:2.27.2 (KDE Applications 18.12.2)

M  +5-1umbrello/umlwidgets/floatingtextwidget.cpp

https://commits.kde.org/umbrello/0b46604faae48016f8dd7dcb34fdcb8c9857bd64

--- Comment #1 from Ralf Habacker  ---
Git commit 96d20006958d6f337ab4cd34957b1e8e901997b2 by Ralf Habacker.
Committed on 30/01/2019 at 18:55.
Pushed by habacker into branch 'Applications/18.12'.

Add test file for component diagram elements and associations

A  +248  -0models/diagrams/component/all-associations.xmi
A  +170  -0models/diagrams/component/all-elements.xmi

https://commits.kde.org/umbrello/96d20006958d6f337ab4cd34957b1e8e901997b2

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

[umbrello] [Bug 403761] Incorrect display of interface widgets in the component diagram when adding a second connection

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

--- Comment #3 from Ralf Habacker  ---
Git commit a9ce7bc064a0c0910f046427eb26ee0ff99f4154 by Ralf Habacker.
Committed on 30/01/2019 at 18:55.
Pushed by habacker into branch 'Applications/18.12'.

In AssociationWidget::widgetMoved() fix endless loop

The loop has been caused by UMLWidget::updateGeometry() updating related
associations too.

Fixup of commit d5cb5adb7fe517ea796f08afa0840ebb6507bd4f.

M  +4-4umbrello/umlwidgets/associationwidget.cpp
M  +5-2umbrello/umlwidgets/umlwidget.cpp
M  +1-1umbrello/umlwidgets/umlwidget.h

https://commits.kde.org/umbrello/a9ce7bc064a0c0910f046427eb26ee0ff99f4154

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

[systemsettings] [Bug 403775] New: Impossible to reset cursor size to "Resolution dependent"

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

Bug ID: 403775
   Summary: Impossible to reset cursor size to "Resolution
dependent"
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_cursortheme
  Assignee: plasma-b...@kde.org
  Reporter: bugsefor...@gmx.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. open system settings > Desktop theme > Cursors
2. set cursor size to 36, apply the new size and close system settings
3. reopen system settings > Desktop theme > Cursors
4. select "Resolution dependent" in "Size" dropdown

OBSERVED RESULT
it's impossible to apply the option selected because "Apply" button is disabled

EXPECTED RESULT
"Apply" button is enabled

SOFTWARE/OS VERSIONS
Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.15.80
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

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

[plasmashell] [Bug 403397] "Show only tasks that are minimized" setting does not work under X11

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

--- Comment #7 from Patrick Silva  ---
Created attachment 117742
  --> https://bugs.kde.org/attachment.cgi?id=117742=edit
plasma-org.kde.plasma.desktop-appletsrc file while the option is checked

Sorry, my mistake.

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

[systemsettings] [Bug 403774] New: New Colors KCM: Error message while breeze dark look and feel theme is used

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

Bug ID: 403774
   Summary: New Colors KCM: Error message while breeze dark look
and feel theme is used
   Product: systemsettings
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_colors
  Assignee: mwoehlke.fl...@gmail.com
  Reporter: bugsefor...@gmx.com
CC: jpwhit...@kde.org
  Target Milestone: ---

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

STEPS TO REPRODUCE
1. set breeze dark theme in system settings > Desktop Theme > Look and Feel
2. open system settings > Colors
3. 

OBSERVED RESULT
bar on top shows error message, see the screenshot.

EXPECTED RESULT
no error message

SOFTWARE/OS VERSIONS
Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.15.80
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

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

[kio-extras] [Bug 400650] kdeinit5 crashes in SMBSlave::fileSystemFreeSpace() when browsing smb:// in Dolphin

2019-01-30 Thread Alexander Potashev

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

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

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

[plasmashell] [Bug 403397] "Show only tasks that are minimized" setting does not work under X11

2019-01-30 Thread Eike Hein

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

--- Comment #6 from Eike Hein  ---
Very weird. The rc file doesn't even show the option as enabled.

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

[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions

2019-01-30 Thread John Bell

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

--- Comment #8 from John Bell  ---
Thanks Brian.  Where do I find the 'shot change list'?

 From your other email I think part of my problem may have been not 
having the project frame rate match the clip frame rate, but fixing that 
has not been a complete fix - still trying to make it work.

I tried your script and again cannot find the output from it but I am 
still looking ...

John

On 1/30/19 8:24 AM, B Stewart wrote:
> https://bugs.kde.org/show_bug.cgi?id=389624
>
> B Stewart  changed:
>
> What|Removed |Added
> 
>   CC||every-...@outlook.com
>
> --- Comment #6 from B Stewart  ---
> Created attachment 117730
>--> https://bugs.kde.org/attachment.cgi?id=117730=edit
> screen shot after running my script
>
> This is also a problem for me, and it seems to have been around for a few
> years!
>
> I'm currently using kdenlive 18.08.2 on Ubuntu 18.08
>
> I have a temporary workaround that works for me.
>
>
> If the (Save result in clip metadata) is checked from (Clip Jobs/Automatic
> scene split) then the clip is analysed (can take a few minutes to complete) 
> and
> the scene change frames are available as a "shot change list".
> The number between each ";" and "=" is the frame number where the scene
> changes.
> This info is also available in the saved .kdenlive file.
>
> I have written a Python3 script (about 70 lines of code) which reads the
> kdenlive file and creates a copy of it with "guide marks" at each shot change.
> This can be opened with kdenlive, which then shows where all the shot changes
> occur.
>
> It is a simple workaround to a problem that seems to have been around for 
> ages.
>

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

[plasmashell] [Bug 403397] "Show only tasks that are minimized" setting does not work under X11

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

--- Comment #5 from Patrick Silva  ---
Created attachment 117740
  --> https://bugs.kde.org/attachment.cgi?id=117740=edit
plasma-org.kde.plasma.desktop-appletsrc file

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

[kmail2] [Bug 403159] Blank page on print preview