[kdeconnect] [Bug 403934] New: KDE Connect on LG v30 not "seen" or "seen by" either of my Kubuntu 18.04 PC's

2019-02-04 Thread kerri
https://bugs.kde.org/show_bug.cgi?id=403934

Bug ID: 403934
   Summary: KDE Connect on LG v30 not "seen" or "seen by" either
of my Kubuntu 18.04 PC's
   Product: kdeconnect
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: kkellerma...@gmail.com
  Target Milestone: ---

I had KDE Connect on Kubuntu 16.04 paired with my LG v30's. Rebuilt my OS for
dual-boot Windows 10/Kubuntu 18.04 with clean installs of both. Both of my PC's
running KDE Connect "see" each other but do not "see" and cannot be "seen by"
either of my LG v30's - one rooted, one stock. This issue has persisted since
install. All of my devices are fully updated daily.

STEPS TO REPRODUCE
1. Verify both Kubuntu PC and Android phone are on same WiFi network.
2. Open KDE Connect settings on PC and KDE Connect Android app and refresh
device lists in both.
3. Re-installed Kubuntu app and Android apps.

EXPECTED RESULT
Devices should be visible and able to pair.

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 18.04
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5
Kernel Version: 4.15.0-45-generic

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

[kate] [Bug 402213] Git context menu items in Project Tree do not appear for filenames with umlauts

2019-02-04 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=402213

Dominik Haumann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Dominik Haumann  ---
Same issue as in bug #389415

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

[dolphin] [Bug 401145] Label of an already labeled removable device is not updated in the places panel if it was modified while Dolphin was running

2019-02-04 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=401145

Patrick Silva  changed:

   What|Removed |Added

Version|18.08.3 |18.12.1

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

[kate] [Bug 402213] Git context menu items in Project Tree do not appear for filenames with umlauts

2019-02-04 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=402213

Dominik Haumann  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kat
   ||e/4de6b812d23bc5e367e93678f
   ||fb5f47bf604101e
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Dominik Haumann  ---
Git commit 4de6b812d23bc5e367e93678ffb5f47bf604101e by Dominik Haumann.
Committed on 04/02/2019 at 20:55.
Pushed by dhaumann into branch 'master'.

Projects plugin: Properly support UTF-8 encoded umlauts in context menu

M  +11   -3addons/project/kateprojecttreeviewcontextmenu.cpp

https://commits.kde.org/kate/4de6b812d23bc5e367e93678ffb5f47bf604101e

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

[kate] [Bug 402213] Git context menu items in Project Tree do not appear for filenames with umlauts

2019-02-04 Thread Dominik Haumann
https://bugs.kde.org/show_bug.cgi?id=402213

Dominik Haumann  changed:

   What|Removed |Added

   Version Fixed In||19.04

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

[gwenview] [Bug 403935] New: Unable to view TARGA image

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403935

Bug ID: 403935
   Summary: Unable to view TARGA image
   Product: gwenview
   Version: 18.12.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: g...@protonmail.com
  Target Milestone: ---

Created attachment 117832
  --> https://bugs.kde.org/attachment.cgi?id=117832&action=edit
CS:GO tga screenshot generated by Steam

SUMMARY
I'm trying to open this TGA image -- it's an uncompressed screenshot of the
game Counter-Strike: GO, and it was generated by Steam --, but Gwenview is
unable to.

STEPS TO REPRODUCE
1. Try to open the image i've attached with gwenview using the command line
2. Image won't load

OBSERVED RESULT
Terminal shows me this:

QImageReader::read() using format hint "tga" failed: "Unknown error"
A bad Qt image decoder moved the buffer to 18 in a call to canRead()!
Rewinding.
Image format is actually "ico" not "tga"
QImageReader::read() using format hint "tga" failed: "Unknown error"
A bad Qt image decoder moved the buffer to 18 in a call to canRead()!
Rewinding.
Image format is actually "ico" not "tga"

Renaming its extension to .ico, gives me this:

QImageReader::read() using format hint "ico" failed: "Unknown error"
A bad Qt image decoder moved the buffer to 22 in a call to canRead()!
Rewinding.
Image format is actually "ico" not "ico"
QImageReader::read() using format hint "tga" failed: "Unknown error"
A bad Qt image decoder moved the buffer to 18 in a call to canRead()!
Rewinding.
Image format is actually "ico" not "tga"


EXPECTED RESULT
Image loads without errors


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 4.20.6
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0

ADDITIONAL INFORMATION
I have tried some different targa images from the internet [1], but upon
opening them I got the same errors

[1] http://netghost.narod.ru/gff/sample/images/tga/index.htm

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

[gwenview] [Bug 403935] Unable to view TARGA image

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403935

g...@protonmail.com changed:

   What|Removed |Added

 CC||g...@protonmail.com

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

[okular] [Bug 403848] Redundant warning on close for unmodified documents in multiple tabs view

2019-02-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=403848

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #5 from Albert Astals Cid  ---
I'm going to suggest you close this bug and start a new one with a subject that
clearly mentions logging out.

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

[okular] [Bug 403835] Print print empty pages

2019-02-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=403835

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||aa...@kde.org
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Albert Astals Cid  ---
Can you attach a document you had this problem with?

Also you totally failed to tell us which okular verison you are using.

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

[latte-dock] [Bug 403840] [feature] - option to enable/disable Meta pressed action

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403840

marinodiego.96+...@gmail.com changed:

   What|Removed |Added

 CC||marinodiego.96+...@gmail.co
   ||m

--- Comment #1 from marinodiego.96+...@gmail.com ---
I don't know if it is related, but if I have a panel with the application
launcher plus a dock with Latte plasmoid, it seems I can't use Meta+1,2,3 to
launch the plasmoid entries anymore. It works fine with the ubuntu ppa version,
it does not work with the git one (at least for me)

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

[latte-dock] [Bug 403840] [feature] - option to enable/disable Meta pressed action

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403840

--- Comment #2 from marinodiego.96+...@gmail.com ---
Actually it seems to be broken in any layout for me.

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

[kdenlive] [Bug 403936] New: Defish effect not working after adding clips

2019-02-04 Thread CzAndrew
https://bugs.kde.org/show_bug.cgi?id=403936

Bug ID: 403936
   Summary: Defish effect not working after adding clips
   Product: kdenlive
   Version: 18.12.1
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: czart.and...@gmail.com
  Target Milestone: ---

SUMMARY
The defish effect does not work after adding items to the timeline.

STEPS TO REPRODUCE
1. Create a new project, add a title clip to the project bin, then add it to
the timeline.
2. Add a video clip to the project bin, then add the video to the timeline
after the title clip.
3. Add defish effect to the video clip, then change the settings (in my case
amount: 770, type: stereorgaphic).

OBSERVED RESULT
The defish effect is not added to the video clip on the timeline. If I turn on,
and off the effect, it makes no difference.

EXPECTED RESULT
When I add the effect on the video clip, and change the values, the effect
should defisheye the video. The result should be seen in the preview window.
If I just add only the video to the timeline, then the effect works.

SOFTWARE/OS VERSIONS
Windows: Win10
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 403937] New: [r]

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403937

Bug ID: 403937
   Summary: [r]
   Product: latte-dock
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: marinodiego.96+...@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 403937] [Request] - disable monochrome effect when "force solid background when touching any window" is activated

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403937

marinodiego.96+...@gmail.com changed:

   What|Removed |Added

Summary|[r] |[Request] - disable
   ||monochrome effect when
   ||"force solid background
   ||when touching any window"
   ||is activated

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

[konqueror] [Bug 403938] New: Crash with allocine

2019-02-04 Thread BIGOT
https://bugs.kde.org/show_bug.cgi?id=403938

Bug ID: 403938
   Summary: Crash with allocine
   Product: konqueror
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: ggpoint...@wanadoo.fr
  Target Milestone: ---

Application: konqueror (4.14.16)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.13.0-36-generic x86_64
Distribution: Linux Mint 18.3 Sylvia

-- Information about the crash:
- What I was doing when the application crashed:
When I try to access www.allocine.fr from a Google search, Konqueror crashes
every time.

The crash can be reproduced every time.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f37a78ba900 (LWP 22045))]

Thread 3 (Thread 0x7f378531a700 (LWP 22068)):
#0  0x7f37a508974d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f37a217a38c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f377c0010c0, timeout=, context=0x16b0b20) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:4135
#2  0x7f37a217a38c in g_main_context_iterate (context=0x16b0b20,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3835
#3  0x7f37a217a712 in g_main_loop_run (loop=0x16b0ad0) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:4034
#4  0x7f3799acd9d6 in gdbus_shared_thread_func (user_data=0x16b0af0) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./gio/gdbusprivate.c:246
#5  0x7f37a21a0c55 in g_thread_proxy (data=0xee60f0) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gthread.c:780
#6  0x7f37a28636ba in start_thread (arg=0x7f378531a700) at
pthread_create.c:333
#7  0x7f37a509541d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f3785b1b700 (LWP 22067)):
#0  0x7f37a508527d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f37a21bd790 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f3785b1ac00, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7f37a21bd790 in g_wakeup_acknowledge (wakeup=0x16afa50) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gwakeup.c:210
#3  0x7f37a2179e74 in g_main_context_check
(context=context@entry=0x1789000, max_priority=2147483647,
fds=fds@entry=0x7f37780008c0, n_fds=n_fds@entry=1) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3632
#4  0x7f37a217a330 in g_main_context_iterate
(context=context@entry=0x1789000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3837
#5  0x7f37a217a49c in g_main_context_iteration (context=0x1789000,
may_block=may_block@entry=1) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:3901
#6  0x7f37a217a4d9 in glib_worker_main (data=) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gmain.c:5672
#7  0x7f37a21a0c55 in g_thread_proxy (data=0xfcea30) at
/build/glib2.0-7ZsPUq/glib2.0-2.48.2/./glib/gthread.c:780
#8  0x7f37a28636ba in start_thread (arg=0x7f3785b1b700) at
pthread_create.c:333
#9  0x7f37a509541d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f37a78ba900 (LWP 22045)):
[KCrash Handler]
#6  0x7f3788db6e90 in
KJS::PropertyMap::getPropertyNames(KJS::PropertyNameArray&,
KJS::PropertyMap::PropertyMode) const () at /usr/lib/libkjs.so.4
#7  0x7f3788dafbe4 in KJS::JSObject::getOwnPropertyNames(KJS::ExecState*,
KJS::PropertyNameArray&, KJS::PropertyMap::PropertyMode) () at
/usr/lib/libkjs.so.4
#8  0x7f3788da5ee8 in  () at /usr/lib/libkjs.so.4
#9  0x7f3788dca5db in  () at /usr/lib/libkjs.so.4
#10 0x7f3788dabe60 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /usr/lib/libkjs.so.4
#11 0x7f3788d909fc in  () at /usr/lib/libkjs.so.4
#12 0x7f3788dca5db in  () at /usr/lib/libkjs.so.4
#13 0x7f3788dabe60 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /usr/lib/libkjs.so.4
#14 0x7f3788dca5db in  () at /usr/lib/libkjs.so.4
#15 0x7f3788dabe60 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /usr/lib/libkjs.so.4
#16 0x7f3788dca5db in  () at /usr/lib/libkjs.so.4
#17 0x7f3788dabe60 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /usr/lib/libkjs.so.4
#18 0x7f3788dca5db in  () at /usr/lib/libkjs.so.4
#19 0x7f3788dabe60 in KJS::FunctionImp::callAsFunction(KJS::ExecState*,
KJS::JSObject*, KJS::List const&) () at /usr/lib/libkjs.so.4
#20 0x7f3788d909fc in  () at /usr/lib/libkjs.so.4
#21 0x7f3788dca5db in  () at /us

[latte-dock] [Bug 403937] [Request] - disable monochrome effect when "force solid background when touching any window" is activated

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403937

--- Comment #1 from marinodiego.96+...@gmail.com ---
SUMMARY
When "force solid background when touching any window" setting is activated, a
monochrome effect is also applied to the panel. I think it would be nice to
have the ability to choose if apply that, or just to force the solid
background.

STEPS TO REPRODUCE
1. Add a new panel
2. Activate "force solid background when touching any window" setting
3. Snap a window to the panel

OBSERVED RESULT
The panel background becomes solid and a monochrome effect is applied.

EXPECTED RESULT
The panel background becomes solid and the user can choose whether a monochrome
effect is applied or not.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.10
(available in About System)
KDE Plasma Version: 5.14.90
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.1

(previous comment was submitted by mistake)

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

[latte-dock] [Bug 403937] [Request] - disable monochrome effect when "force solid background when touching any window" is activated

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403937

marinodiego.96+...@gmail.com changed:

   What|Removed |Added

 CC||marinodiego.96+...@gmail.co
   ||m

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

[latte-dock] [Bug 403930] [Feature request] Auto-coloring for non-snapped windows

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403930

marinodiego.96+...@gmail.com changed:

   What|Removed |Added

 CC||marinodiego.96+...@gmail.co
   ||m

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

[okular] [Bug 403815] The bar is showing No Text

2019-02-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=403815

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
Your version is old, this was reported and then people said they could not
reproduce it with newer versions, so i'm going to close it.

If you can reproduce it with Okular 1.6 or newer please reopen.

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

[frameworks-knotifications] [Bug 403939] New: Build failure in the kdeorg/android-sdk

2019-02-04 Thread carl
https://bugs.kde.org/show_bug.cgi?id=403939

Bug ID: 403939
   Summary: Build failure in the kdeorg/android-sdk
   Product: frameworks-knotifications
   Version: 5.54.0
  Platform: Android
OS: unspecified
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: schwanc...@protonmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 117833
  --> https://bugs.kde.org/attachment.cgi?id=117833&action=edit
Debug output

SUMMARY

Build failure by executing the command given in
https://community.kde.org/Android/Environment_via_Container

docker run -ti --rm -v /tmp:/output kdeorg/android-sdk
/opt/helpers/build-generic okular 

I tried to add --stacktrace and --info to the command, but I didn't get any
additional input.

Debug output is in attachment

SOFTWARE/OS VERSIONS
Docker image kdeorg/android-sdk

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

[kdenlive] [Bug 403940] New: No warning for videos which is different from the project profile after adding a folder

2019-02-04 Thread CzAndrew
https://bugs.kde.org/show_bug.cgi?id=403940

Bug ID: 403940
   Summary: No warning for videos which is different from the
project profile after adding a folder
   Product: kdenlive
   Version: 18.12.1
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: czart.and...@gmail.com
  Target Milestone: ---

SUMMARY
Kdenlive doesn't warn for different project profile if a folder is added first
to the project bin.

STEPS TO REPRODUCE
1. Go to settings, and make sure that "Check if first added clip matches
project profile." is selected.
2. Create a new project, then create a folder in the project bin.
3. Add a video clip, which is different than the project. (for example the
resolution or fps is different)

OBSERVED RESULT
Kdenlive doesn't warn that the added video is different than the project.


EXPECTED RESULT
When the first video clip is added, kdenlive should warn that the video clip is
different than the project. 

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

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 403941] New: No cursor in title clip editor

2019-02-04 Thread CzAndrew
https://bugs.kde.org/show_bug.cgi?id=403941

Bug ID: 403941
   Summary: No cursor in title clip editor
   Product: kdenlive
   Version: 18.12.1
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: czart.and...@gmail.com
  Target Milestone: ---

SUMMARY
Cursor can't be seen in title clip editor.

STEPS TO REPRODUCE
1. create a new title clip
2. write something, then click on the middle of the text

OBSERVED RESULT
The cursor can't be seen

EXPECTED RESULT
The cursor should be seen like in other text editors.

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

ADDITIONAL INFORMATION
I'm using Kdenlive 18.12.1, but this bug is present in the older versions as
well.

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

[kmymoney] [Bug 403877] Program crashed; won't re-launch; provides error message

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403877

--- Comment #2 from k...@manuscripts.org.uk ---
Created attachment 117834
  --> https://bugs.kde.org/attachment.cgi?id=117834&action=edit
output from zgrep

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

[dolphin] [Bug 403931] TAB Key when renaming files

2019-02-04 Thread kiarfuzzy
https://bugs.kde.org/show_bug.cgi?id=403931

kiarfuzzy  changed:

   What|Removed |Added

 CC||kiarfu...@gmail.com

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

[systemsettings] [Bug 403932] Change Volume with mouse wheel

2019-02-04 Thread kiarfuzzy
https://bugs.kde.org/show_bug.cgi?id=403932

kiarfuzzy  changed:

   What|Removed |Added

 CC||kiarfu...@gmail.com

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

[konqueror] [Bug 65682] right-click then click title bar causes crash

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=65682

eliaschin...@gmail.com changed:

   What|Removed |Added

 CC||eliaschin...@gmail.com

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

[krita] [Bug 403942] New: crash by right click

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403942

Bug ID: 403942
   Summary: crash by right click
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: eliaschin...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. start krita 
2. right click
3. 

OBSERVED RESULT crashed because does not accept opengl 3.3 or higher


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 7
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 400513] [feature] - Request middle-click move to current desktop

2019-02-04 Thread Brian Snipes
https://bugs.kde.org/show_bug.cgi?id=400513

--- Comment #7 from Brian Snipes  ---
I don't think I personally would ever use the Show on All Desktops via a
middle-click. I would definitely use the Move to Current Desktop.

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

[okular] [Bug 403943] New: Entries in table of contents should be normalized (whitespace stripped)

2019-02-04 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=403943

Bug ID: 403943
   Summary: Entries in table of contents should be normalized
(whitespace stripped)
   Product: okular
   Version: 1.6.1
  Platform: unspecified
OS: unspecified
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: david.hu...@mailbox.org
  Target Milestone: ---

Created attachment 117835
  --> https://bugs.kde.org/attachment.cgi?id=117835&action=edit
Much whitespace in Contents panel

SUMMARY
For many documents, the Contents panel is not useful, because too many
whitespace is shown. It would be better to strip excess whitespace in every
item. (QString::simplified())

STEPS TO REPRODUCE
1. Open e. g.
http://www.vbg.de/SharedDocs/Medien-Center/DE/Broschuere/Themen/Bildschirm_und_Bueroarbeit/DGUV_Information_215-444_Sonnenschutz_im_Buero.pdf
2. Look at Contents panel
3. 

OBSERVED RESULT
Entries look like (' for wasted space)
1''Sonnens
2.1'Ausric
2.4''A
4.1.1'

EXPECTED RESULT
Entries look like (' not needed ;) )
1 Sonnenstrahlung
2.1 Ausrichtung des Gebäu...
2.4 Aufstellung eines Bi...
4.1.1 Außenjalousien

ADDITIONAL INFORMATION
Sorry, screenshot still without D18429.

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

[frameworks-baloo] [Bug 403902] Since I named an XML file .spx, Baloo crashes at every login

2019-02-04 Thread David Hurka
https://bugs.kde.org/show_bug.cgi?id=403902

David Hurka  changed:

   What|Removed |Added

 CC||david.hu...@mailbox.org

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

[kmymoney] [Bug 403877] Program crashed; won't re-launch; provides error message

2019-02-04 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=403877

--- Comment #3 from Jack  ---
That's very strange.  zgrep knows the file is compressed, uncompresses it, and
passes it to grep.  I don't know how, but it looks like your file might be
double compressed.  Can you try "file peter.kmy" to see what it says?   You
might then also try (as sequential commands) "cp peter.kmy x.gz" "gunzip x.gz"
"file x".  that x SHOULD be a plain ascii xml file.  If file says it is gzip
compressed, then you can try "zgrep A83 x" and we can go from there.

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

[kdenlive] [Bug 403944] New: Stabilizing 30fps clips in 60fps project problems

2019-02-04 Thread CzAndrew
https://bugs.kde.org/show_bug.cgi?id=403944

Bug ID: 403944
   Summary: Stabilizing 30fps clips in 60fps project problems
   Product: kdenlive
   Version: 18.12.1
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: czart.and...@gmail.com
  Target Milestone: ---

SUMMARY
In some specific cases stabilization does not produce good results if a 30fps
videoclip is stabilized in a 60fps project. The problem occurs when something
on the video moves from the opposite directions (for example when you're moving
form left to right, and a car moves from right to left). (Link to an example is
attached.)

STEPS TO REPRODUCE
1. Create a 60fps project.
2. Import a 30fps video to the project bin.
3. Stabilize the video, then add it to the timeline, then render the project.

OBSERVED RESULT
The moving objects are strange on the stabililized video when something on the
video moves from the opposite directions (for example when you're moving form
left to right, and a car moves from right to left). (Link to an example is
attached.)

EXPECTED RESULT
If the 30fps video is stabilized in a 30fps project, the result is a well
stabilized video.

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

ADDITIONAL INFORMATION
Well, you might ask why would I stabilize a 30fps video in a 60fps project. I
shoot lots of videos with an actioncamera, and when I have light I use 60fps,
but at night I use 30 fps. When I edit the videos, the final video will be a
60fps video, so I use both 30fps and 60fps videos in my project.
One possible solution would be to stabilize, and render the 30fps videos in a
30fps project one by one, but as I shoot lots of short clips, that would take
lots of time.
(My workaround is that I use a script in a linux virtual machine to stabilize
my videos automatically one after an another using ffmpeg, which doesn't change
the framerate. Then I add the stabilized videos to kdenlive.)

Here is a videoclip for demonstration: (the tuktuk and the second taxi looks
really strange)
https://drive.google.com/open?id=1Ro5ZC93Fg9xrcN60poHketisCzFm6Cg1

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

[muon] [Bug 403945] New: Crashed while getting an application.

2019-02-04 Thread Hermann Heraux
https://bugs.kde.org/show_bug.cgi?id=403945

Bug ID: 403945
   Summary: Crashed while getting an application.
   Product: muon
   Version: 5.4.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: hermy0...@yahoo.com
CC: silh...@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.

[kpdf] [Bug 83099] prints only blank pages

2019-02-04 Thread Jeff Fitzmaurice
https://bugs.kde.org/show_bug.cgi?id=83099

Jeff Fitzmaurice  changed:

   What|Removed |Added

 CC||jeffspl...@live.com

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

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

2019-02-04 Thread Jeff Fitzmaurice
https://bugs.kde.org/show_bug.cgi?id=403159

Jeff Fitzmaurice  changed:

   What|Removed |Added

 CC||jeffspl...@live.com

--- Comment #6 from Jeff Fitzmaurice  ---
I confirm this is happening in Fedora 29 64bit KDE using Kmail and Kontact. 
Print Preview turns a blank page.  Also, attempting a physical printed copy
turns a physical blank page.  I have all the latest updates.  Printing does not
work from Kmail via Kontact.

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

[Discover] [Bug 403946] New: Discover crashed sudenlly

2019-02-04 Thread zhustec
https://bugs.kde.org/show_bug.cgi?id=403946

Bug ID: 403946
   Summary: Discover crashed sudenlly
   Product: Discover
   Version: 5.14.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: zhus...@foxmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.14.5)

Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.20.6-arch1-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
I just open it and waiting for 5 min, it just crash without any operation.

The crash can be reproduced every time.

-- Backtrace:
Application: 发现者 (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9ea9657080 (LWP 5731))]

Thread 9 (Thread 0x7f9e8cab7700 (LWP 5749)):
#0  0x7f9eac761f5a in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#1  0x7f9eac76b4bc in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9eac76b62e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9eae4da5c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9eae48358c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9eae2c75c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9eae2c89cc in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9ead25ca9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9eadfb0b23 in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f9e8dff9700 (LWP 5741)):
[KCrash Handler]
#6  0x7f9ead976904 in  () at /usr/lib/libQt5Network.so.5
#7  0x7f9ead9751fb in  () at /usr/lib/libQt5Network.so.5
#8  0x7f9eae4afb62 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#9  0x7f9eaf38ae34 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#10 0x7f9eaf392671 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#11 0x7f9eae4848f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#12 0x7f9eae487998 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#13 0x7f9eae4dafd4 in  () at /usr/lib/libQt5Core.so.5
#14 0x7f9eac769a2f in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#15 0x7f9eac76b5e9 in  () at /usr/lib/libglib-2.0.so.0
#16 0x7f9eac76b62e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#17 0x7f9eae4da5a9 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#18 0x7f9eae48358c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#19 0x7f9eae2c75c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#20 0x7f9eae2c89cc in  () at /usr/lib/libQt5Core.so.5
#21 0x7f9ead25ca9d in start_thread () at /usr/lib/libpthread.so.0
#22 0x7f9eadfb0b23 in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f9e8e7fa700 (LWP 5740)):
#0  0x7f9eadfa5c21 in poll () at /usr/lib/libc.so.6
#1  0x7f9eac76b540 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9eac76b62e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9eae4da5c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9eae48358c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9eae2c75c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9eae2c89cc in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9ead25ca9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9eadfb0b23 in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f9e8effb700 (LWP 5737)):
#0  0x7f9eac76203f in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#1  0x7f9eac76b4bc in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9eac76b62e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9eae4da5c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9eae48358c in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9eae2c75c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9eafe0ce5b in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f9eae2c89cc in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9ead25ca9d in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f9eadfb0b23 in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f9e95aa6700 (LWP 5736)):
#0  0x7f9ead262afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9e960b8be4 in  () at /usr/lib/dri/i965_dri.so
#2  0x7f9e960b8908 in  () at /usr/lib/dri/i965_dri.so
#3  0x7f9ead25ca9d in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f9eadfb0b23 in clone () at /usr/lib/libc.so.

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

2019-02-04 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=403159

Kevin Kofler  changed:

   What|Removed |Added

 CC||kevin.kof...@chello.at

--- Comment #7 from Kevin Kofler  ---
I suspect that this is a bug in the QtWebEngine print method. I am seeing this
with QtWebEngine 5.11.3. Falkon also spits out a blank page when I try to print
directly to the printer. Printing to PDF works in Falkon (which uses the
dedicated printToPdf method in that case, which is a good idea, by the way,
because it will produce a normal PDF, whereas using the normal print method
will render that PDF to a bitmap per page and then produce a PDF containing the
bitmap(s)), but not in KMail (which, I guess, always uses the generic print
method).

This probably needs to be reported to Qt upstream if it isn't yet.

It would also be important to know whether it works with QtWebEngine 5.12.x. I
cannot easily test it at this time because we have no QtWebEngine 5.12.x builds
in Fedora yet.

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

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

2019-02-04 Thread Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=403159

Kevin Kofler  changed:

   What|Removed |Added

Summary|Blank page on print preview |Blank page on print and
   ||print preview

--- Comment #8 from Kevin Kofler  ---
I'm updating the summary because, sadly, not only the preview is blank.

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

[frameworks-kdesu] [Bug 389049] stuck with sudo and wrong password

2019-02-04 Thread Jiri Palecek
https://bugs.kde.org/show_bug.cgi?id=389049

Jiri Palecek  changed:

   What|Removed |Added

 CC||de.tec...@gmail.com

--- Comment #8 from Jiri Palecek  ---
*** Bug 292176 has been marked as a duplicate of this bug. ***

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

[kdesu] [Bug 292176] kdesu hang when wrong password is entered in sudo mode.

2019-02-04 Thread Jiri Palecek
https://bugs.kde.org/show_bug.cgi?id=292176

Jiri Palecek  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||jpale...@web.de
 Status|REPORTED|RESOLVED

--- Comment #27 from Jiri Palecek  ---


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

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

[kdesu] [Bug 170155] doesn't report wrong password

2019-02-04 Thread Jiri Palecek
https://bugs.kde.org/show_bug.cgi?id=170155

Jiri Palecek  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||jpale...@web.de
 Status|REPORTED|RESOLVED

--- Comment #4 from Jiri Palecek  ---


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

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

[frameworks-kdesu] [Bug 389049] stuck with sudo and wrong password

2019-02-04 Thread Jiri Palecek
https://bugs.kde.org/show_bug.cgi?id=389049

Jiri Palecek  changed:

   What|Removed |Added

 CC||kdeb...@whamra.com

--- Comment #9 from Jiri Palecek  ---
*** Bug 170155 has been marked as a duplicate of this bug. ***

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

[Breeze] [Bug 403229] Icon cache doesn't get automatically cleaned when a release has new/changed icons

2019-02-04 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=403229

--- Comment #5 from Nate Graham  ---
Filed some downstream bug reports for distros to adjust their packaging:

- https://bugs.archlinux.org/task/61632
- https://bugzilla.opensuse.org/show_bug.cgi?id=1124243
- https://bugs.launchpad.net/ubuntu/+source/breeze-icons/+bug/1814612

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

[Breeze] [Bug 403229] Icon cache doesn't get automatically cleaned when a release has new/changed icons

2019-02-04 Thread Eli Schwartz
https://bugs.kde.org/show_bug.cgi?id=403229

Eli Schwartz  changed:

   What|Removed |Added

 CC||eschwa...@archlinux.org

--- Comment #6 from Eli Schwartz  ---
I see no reason for Arch Linux to violate policy by having a package manager
modify something that isn't a package. We don't modify $HOME in our packaging,
and even mentioning the idea traditionally provokes a hair-trigger response
"only the worst ever packages would ever dare touch $HOME, what is this package
and can we have it deleted".

Why doesn't Breeze figure out based on hashes or timestamps, that the original
files have changed and an update is needed?

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

[Breeze] [Bug 403229] Icon cache doesn't get automatically cleaned when a release has new/changed icons

2019-02-04 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=403229

--- Comment #7 from Nate Graham  ---
Gotcha, we'll try to take care of it ourselves. My ignorance of packaging best
practices is definitely showing. :)

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

[Breeze] [Bug 403229] Icon cache doesn't get automatically cleaned when a release has new/changed icons

2019-02-04 Thread Eli Schwartz
https://bugs.kde.org/show_bug.cgi?id=403229

--- Comment #8 from Eli Schwartz  ---
It's anyway the wrong level to try implementing this -- how do you robustly log
into every user on the system regardless of their home directory, then execute
their bashrc, .pam_environment, and .config/environment.d (this one is a bit of
circular logic) in order to find out whether $XDG_CACHE_HOME has been set, and
finally delete `${XDG_CACHE_HOME:-$HOME/.cache}/icon-cache.kcache`?

I mean... you "could" do so, but it begins to become somewhat uncomfortable,
and the #1 place to find an overridden variable also introduces arbitrary code
execution. Even run as the user, there may be things there that users don't
want to be executed unless they are the ones logging in.

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

[latte-dock] [Bug 403840] [feature] - option to enable/disable Meta pressed action

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403840

tr...@yandex.com changed:

   What|Removed |Added

 CC||tr...@yandex.com

--- Comment #3 from tr...@yandex.com ---
(In reply to Michail Vourlakos from comment #0)
> Git version now supports Meta is pressed in order to show Latte Views with
> Shortcuts Badges to enhance usability. But there is a chance that this
> behavior breaks some user workflows so it should be better to be optional or
> at least have an option to disable it through Latte->Preferences

Can you give an example that it breaks something?
I think we shouldn't add a new option if we don't have an real issue with it.
Too many options could confuse users.

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

[latte-dock] [Bug 403840] [feature] - option to enable/disable Meta pressed action

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403840

--- Comment #4 from tr...@yandex.com ---
(In reply to marinodiego.96+kde from comment #2)
> Actually it seems to be broken in any layout for me.

Try right clicking on your dock that has Latte Plasmoid > Behavior > Activate
base on position...

In the current git version, that feature is disabled by default, we are
bringing it back.

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

[krita] [Bug 402909] My drawing will not finish rendering. It will not let me draw or save. please help.

2019-02-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402909

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.

[systemsettings] [Bug 399716] System Settings crashes on open, "Fatal error while loading the sidebar view qml component".

2019-02-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=399716

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

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

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

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

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

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

[krita] [Bug 402854] When i insert a pictures. Krita dont run. I cant insert a picture

2019-02-04 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=402854

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 403942] crash by right click

2019-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=403942

evali...@yahoo.com changed:

   What|Removed |Added

 CC||evali...@yahoo.com

--- Comment #1 from evali...@yahoo.com ---
---

Error occurred on Monday, February 4, 2019 at 22:23:11.

krita.exe caused an Access Violation at location 5CB61433 in module
atio6axx.dll Reading from location .

AddrPC   Params
5CB61433 0455E5D0 0001 0001 
atio6axx.dll!0x111433 DrvPresentBuffers+0xcc293
5CB610D2 06662045654B 145F0910 7FFDD620FC20 
atio6axx.dll!0x1110d2 DrvPresentBuffers+0xcbf32
5CEB86AA 0018 7FFE17421D76 000A 
atio6axx.dll!0x4686aa DrvPresentBuffers+0x42350a
7FFDD6007DC1 01E33BF0 28D60B70 7FFDF5043050 
libkritaui.dll!0x157dc1 KisOpenGLCanvas2::isBusy+0x41
7FFDD5EB5A79 0023AE9C 0023B030 004B0023B020 
libkritaui.dll!0x5a79 KisCanvas2::slotDoCanvasUpdate+0x19
7FFDD620FEE5 0023AF50 0023B030 13ED3DD0 
libkritaui.dll!0x35fee5 KisCanvas2::qt_static_metacall+0x2c5
7FFDF4CFBE7A 0A461DC8  1414BF50 
Qt5Core.dll!0x23be7a QMetaObject::activate+0x7fa
7FFE0ACA86B1  7FFDD5EC3C1C 145D2890 
libkritaglobal.dll!0x186b1 KisSignalCompressor::start+0xc1
7FFDD5EB5B90 28D60230 7FFDF4B41798 05CD78B0 
libkritaui.dll!0x5b90 KisCanvas2::updateCanvas+0x20
7FFDD5FCE98B 0F6526F8 0F6526E0 001E 
libkritaui.dll!0x11e98b KisSelectionDecoration::selectionChanged+0x1ab
7FFDF4CFBE7A 0650FC90  3FE0 
Qt5Core.dll!0x23be7a QMetaObject::activate+0x7fa
7FFDD6164B17 0062 7FFDF4AF0DCF 0023B3C0 
libkritaui.dll!0x2b4b17 KisMainWindow::windowFocused+0x37
7FFDF4CFBE7A 0023FBB0 112FC5C0 112FC5C0 
Qt5Core.dll!0x23be7a QMetaObject::activate+0x7fa
7FFDEBB0C8BC 145A5020 112FC5C0 0E5E4070 
Qt5Widgets.dll!0xc8bc QApplicationPrivate::setFocusWidget+0x1cc
7FFDEBB3E42C  145A53B0 0023FBB0 
Qt5Widgets.dll!0x3e42c QWidgetPrivate::paintSiblingsRecursive+0x73c
7FFDEBB0805E 0E60E770 10F390E0 006D0011 
Qt5Widgets.dll!0x805e
QApplicationPrivate::giveFocusAccordingToFocusPolicy+0x1ae
7FFDEBB10BE9  7FFDF4AF0DCF  
Qt5Widgets.dll!0x10be9 QApplication::notify+0x2179
7FFDD6139856 8000 C0678000  
libkritaui.dll!0x289856 KisApplication::notify+0x16
7FFDF4CD0E28 3FF0 0001  
Qt5Core.dll!0x210e28 QCoreApplication::notifyInternal2+0x198
7FFDEBB0E1E8 004C 145D4670 145D4670 
Qt5Widgets.dll!0xe1e8 QApplicationPrivate::sendMouseEvent+0x208
7FFDEBB58DC0 01EC1E50 7FFDF4CCFCBC 28D60730 
Qt5Widgets.dll!0x58dc0 QDesktopWidget::qt_metacall+0x2a50
7FFDEBB5B384 0023FBB0 01C6BA80 0001 
Qt5Widgets.dll!0x5b384 QDesktopWidget::qt_metacall+0x5014
7FFDEBB07AEC    
Qt5Widgets.dll!0x7aec QApplicationPrivate::notify_helper+0x9c
7FFDEBB0ED60 0023BEA0 7FFDF4AF0DCF 13E42860 
Qt5Widgets.dll!0xed60 QApplication::notify+0x2f0
7FFDD6139856 0001 7FFDF57BF864  
libkritaui.dll!0x289856 KisApplication::notify+0x16
7FFDF4CD0E28   0F05DA10 
Qt5Core.dll!0x210e28 QCoreApplication::notifyInternal2+0x198
7FFDF57A9451 01E68761 01E68748  
Qt5Gui.dll!0x39451 QGuiApplicationPrivate::processMouseEvent+0x721
7FFDF57AAF05 0023C238 01F3C660 00270724 
Qt5Gui.dll!0x3af05 QGuiApplicationPrivate::processWindowSystemEvent+0x105
7FFDF5781C30 00E6 0401 00270724 
Qt5Gui.dll!0x11c30 QWindowSystemInterface::sendWindowSystemEvents+0x370
7FFDF4D28A66 0401 0023C468 0023C498 
Qt5Core.dll!0x268a66 QEventDispatcherWin32Private::sendTimerEvent+0x666
7FFE171424FD 0084B610 0023C580 00270724 
USER32.dll!0x24fd UserCallWinProcCheckWow+0x149
7FFE17142357 01E33BF0 01E33BF0 0023C580 
USER32.dll!0x2357 DispatchMessageWorker+0x1a7
7FFDF4D27D5B 01F3C660 0024 01E2BC90 
Qt5Core.dll!0x267d5b QEventDispatcherWin32::processEvents+0x5cb
6A8DEF15 0080 0014 13A91320 
qwindows.dll!0x5ef15 qt_plugin_instance+0x28e5
7FFDF4CCF4EF  0001 7FFDF4E28100 
Qt5Core.dll!0x20f4ef QEventLoop::exec+0x13f
7FFDF4CD7F

[Breeze] [Bug 403229] Icon cache doesn't get automatically cleaned when a release has new/changed icons

2019-02-04 Thread Felix Miata
https://bugs.kde.org/show_bug.cgi?id=403229

Felix Miata  changed:

   What|Removed |Added

 CC||mrma...@earthlink.net

--- Comment #9 from Felix Miata  ---
This bug to me begs the question why Plasma caches so much in the first place.
Some of its caches seem so large that I'd expect less overall overhead reading
directly from disk into RAM rather than handling its multiple big caches,
create, read, store and include amongst other settings getting backed up from
the homedir.

-- 
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-02-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399981

stanko.lubo...@gmail.com changed:

   What|Removed |Added

 CC||stanko.lubo...@gmail.com

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

[systemsettings] [Bug 403947] New: System settings crash

2019-02-04 Thread Ryan
https://bugs.kde.org/show_bug.cgi?id=403947

Bug ID: 403947
   Summary: System settings crash
   Product: systemsettings
   Version: 5.14.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: im_drac...@hotmail.com
  Target Milestone: ---

Application: systemsettings5 (5.14.4)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.20.5-200.fc29.x86_64 x86_64
Distribution: "Fedora release 29 (Twenty Nine)"

-- Information about the crash:
- What I was doing when the application crashed:
switching between sections of the system-settings application

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1b3b82f940 (LWP 2884))]

Thread 12 (Thread 0x7f1adeffe700 (LWP 5021)):
#0  0x7f1b3c0202d8 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f1b3bfd78dc in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f1b3bfd82db in  () at /lib64/libglib-2.0.so.0
#3  0x7f1b3bfd84d0 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f1b3f2ff5ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f1b3f2ade0b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f1b3f115e86 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f1b40efaf59 in  () at /lib64/libQt5Qml.so.5
#8  0x7f1b3f11f2fb in  () at /lib64/libQt5Core.so.5
#9  0x7f1b3e69858e in start_thread () at /lib64/libpthread.so.0
#10 0x7f1b3ec5b6a3 in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f1addffc700 (LWP 5020)):
#0  0x7f1b3e69e73c in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1b3f11f923 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f1b412101c9 in  () at /lib64/libQt5Quick.so.5
#3  0x7f1b4121042a in  () at /lib64/libQt5Quick.so.5
#4  0x7f1b3f11f2fb in  () at /lib64/libQt5Core.so.5
#5  0x7f1b3e69858e in start_thread () at /lib64/libpthread.so.0
#6  0x7f1b3ec5b6a3 in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f1add7fb700 (LWP 5018)):
#0  0x7f1b3c0202ad in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7f1b3bfd836e in  () at /lib64/libglib-2.0.so.0
#2  0x7f1b3bfd84d0 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f1b3f2ff5ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f1b3f2ade0b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f1b3f115e86 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f1b40efaf59 in  () at /lib64/libQt5Qml.so.5
#7  0x7f1b3f11f2fb in  () at /lib64/libQt5Core.so.5
#8  0x7f1b3e69858e in start_thread () at /lib64/libpthread.so.0
#9  0x7f1b3ec5b6a3 in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f1ae79ff700 (LWP 4265)):
#0  0x7f1b3ec50421 in poll () at /lib64/libc.so.6
#1  0x7f1b3bfd83a6 in  () at /lib64/libglib-2.0.so.0
#2  0x7f1b3bfd84d0 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f1b3f2ff5ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f1b3f2ade0b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f1b3f115e86 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f1ae6c117db in KCupsConnection::run() () at /lib64/libkcupslib.so
#7  0x7f1b3f11f2fb in  () at /lib64/libQt5Core.so.5
#8  0x7f1b3e69858e in start_thread () at /lib64/libpthread.so.0
#9  0x7f1b3ec5b6a3 in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f1af7fff700 (LWP 3787)):
#0  0x7f1b3ec4bf84 in read () at /lib64/libc.so.6
#1  0x7f1b3c01ee90 in  () at /lib64/libglib-2.0.so.0
#2  0x7f1b3bfd7e9b in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f1b3bfd8350 in  () at /lib64/libglib-2.0.so.0
#4  0x7f1b3bfd8762 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#5  0x7f1b15f7110a in  () at /lib64/libgio-2.0.so.0
#6  0x7f1b3c0012aa in  () at /lib64/libglib-2.0.so.0
#7  0x7f1b3e69858e in start_thread () at /lib64/libpthread.so.0
#8  0x7f1b3ec5b6a3 in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f1af4da4700 (LWP 3786)):
#0  0x7f1b3ec4bf84 in read () at /lib64/libc.so.6
#1  0x7f1b3c01ee90 in  () at /lib64/libglib-2.0.so.0
#2  0x7f1b3bfd7e9b in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f1b3bfd8350 in  () at /lib64/libglib-2.0.so.0
#4  0x7f1b3bfd84d0 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f1b3bfd8521 in  () at /lib64/libglib-2.0.so.0
#6  0x7f1b3c0012aa in  () at /lib64/libglib-2.0.so.0
#7  0x7f1b3e69858e in start_thread () at /lib64/libpthread.so.0
#8  

[AudioCD-KIO] [Bug 313768] Please add support for opus codec

2019-02-04 Thread Yuri Chornoivan
https://bugs.kde.org/show_bug.cgi?id=313768

Yuri Chornoivan  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/aud
   ||iocd-kio/ed3eb5a6a3e9084139
   ||8f268d04b26dfa9ac3bf81

--- Comment #1 from Yuri Chornoivan  ---
Git commit ed3eb5a6a3e90841398f268d04b26dfa9ac3bf81 by Yuri Chornoivan.
Committed on 05/02/2019 at 06:15.
Pushed by yurchor into branch 'master'.

Add Opus support for KIO AudioCD
Differential Revision: https://phabricator.kde.org/D17734

M  +1-1CMakeLists.txt
M  +3-2HACKING
M  +5-4kcmaudiocd/kcmaudiocd.cpp
M  +1-0plugins/CMakeLists.txt
A  +27   -0plugins/opus/CMakeLists.txt
A  +3-0plugins/opus/Messages.sh
A  +59   -0plugins/opus/audiocd_opus_encoder.kcfg
A  +4-0plugins/opus/audiocd_opus_encoder.kcfgc
A  +257  -0plugins/opus/encoderopus.cpp [License: GPL (v2+)]
A  +76   -0plugins/opus/encoderopus.h [License: GPL (v2+)]
A  +446  -0plugins/opus/encoderopusconfig.ui

https://commits.kde.org/audiocd-kio/ed3eb5a6a3e90841398f268d04b26dfa9ac3bf81

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

[kmymoney] [Bug 403825] Transaction validity filter is reset when re-opening configuration

2019-02-04 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=403825

Thomas Baumgart  changed:

   What|Removed |Added

   Version Fixed In|4.8.4   |4.8.4, 5.0.4

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

[plasmashell] [Bug 401464] Activities + icons

2019-02-04 Thread Oleg Solovyov
https://bugs.kde.org/show_bug.cgi?id=401464

--- Comment #3 from Oleg Solovyov  ---
Found a clue:

FolderModel::filterAcceptsRow - (m_screen == 1) branch is missing
just adding
+ return false;
is not the solution, we need to have an additional statement there but I still
have not figured out it

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

<    1   2