[Planet KDE] [Bug 369450] Multiple monitor desktops & backgrounds are simply blank.

[Tim Bess via KDE Bugzilla]

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

--- Comment #1 from Tim Bess  ---
Okay from bizarre land -- I couldn't place a widget on those displays without
any background. However, I dragged over the network monitor widget onto display
1 and this disappeared. Okay, fine, dragged another one -- a couple flashes and
I suddenly have backgrounds that are individually controllable on displays #2
and #3 -- with every widget I attempted to drag over working. I'm sure this
triggered some kind of reset in some part of the display system given the brief
white flash. Or maybe the two have nothing to do with each other and the white
flash was its own reset? Not unhappy with this, but I haven't figured out a way
to get it back to its original blank state without reinstalling to duplicate.

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

[Discover] [Bug 369457] New: Discover

[dany via KDE Bugzilla]

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

Bug ID: 369457
   Summary: Discover
   Product: Discover
   Version: 5.7.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: danytum...@gmail.com

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

good friends kde neon to report this failure is never discover sample size
never install applications and hope you can solve this problem as much use
graphical installation.

Excuse my English I'm using google translator

Greetings from Venezuela

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

[Discover] [Bug 366264] Was doing upgrade in Plasma DIscover

[dany via KDE Bugzilla]

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

dany  changed:

   What|Removed |Added

 CC||danytum...@gmail.com

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

[valgrind] [Bug 369456] New: callgrind_control failed to find an active callgrind run.

[Alex via KDE Bugzilla]

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

Bug ID: 369456
   Summary: callgrind_control failed to find an active callgrind
run.
   Product: valgrind
   Version: 3.11.0
  Platform: Homebrew (Mac OS X)
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: callgrind
  Assignee: josef.weidendor...@gmx.de
  Reporter: alex_hit...@ngs.ru

I'm running callgrind with:
$ valgrind --tool=callgrind  --instr-atstart=no ./program_name

Then trying to enable profiling from other terminal:
$ callgrind_control -i on
No active callgrind runs detected.

The same with PID:
$ callgrind_control -i on 80627
Error: Callgrind task with PID/name '80627' not detected.

Valgrind in process list:
$ ps
  PID TTY   TIME CMD
 1021 ttys0000:00.32 -bash
80627 ttys0000:56.54 valgrind --tool=callgrind --instr-atstart=no
./program_name
 5280 ttys0020:00.24 -bash

Some additional info:
uname -a
Darwin macpc-1124 14.5.0 Darwin Kernel Version 14.5.0: Mon Aug 29 21:14:16 PDT
2016; root:xnu-2782.50.6~1/RELEASE_X86_64 x86_64

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

[Touchpad-KCM] [Bug 369355] Touchpad configuration applet crashes

[Rajeesh K V via KDE Bugzilla]

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

Rajeesh K V  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Rajeesh K V  ---


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

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

[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session

[Rajeesh K V via KDE Bugzilla]

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

Rajeesh K V  changed:

   What|Removed |Added

 CC||e...@theunixman.com

--- Comment #5 from Rajeesh K V  ---
*** Bug 369355 has been marked as a duplicate of this bug. ***

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

[valgrind] [Bug 369409] null pointer dereference in vgPlain_do_syscall

[ssl via KDE Bugzilla]

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

--- Comment #2 from ssl  ---
It crashed too when I built it from valgrind SVN source code.

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

[krita] [Bug 369451] brush angle tied to canvas rotation instead of being absolute

[via KDE Bugzilla]

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

--- Comment #3 from anim...@gmail.com ---
The tilt rotation issue was already reported there:
https://bugs.kde.org/show_bug.cgi?id=366289

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

[krita] [Bug 369012] crash when playing animation when document's size is larger than 30M (approx)

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #3 from Scott Petrovic  ---
I cannot get a crash with this. Followed the steps and tried toggling between
play and pause. I have an NVIDIA GT650M

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

[skrooge] [Bug 365724] Driver not loaded Driver not loaded

[via KDE Bugzilla]

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

--- Comment #19 from mspada...@yahoo.com ---
Sorry for the delay.  When I installed from your repo, I did install all the
available depends you provided, but still got the crash on startup.

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

[krita] [Bug 356153] Tool Options Drop-Down locked into top left corner of the screen when detached on Windows 8.1

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Scott Petrovic  ---
It is still doing this on my Windows 3.0.1.90 build. I am sure it is still a Qt
bug. Just marking as confirmed.

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

[krita] [Bug 368537] Save Group Layers does not export to folder specified

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
This seems to work for me on 3.0.1.90 on Windows. I created a group layer.
Saved it out to a folder, then the image is appearing in the correct folder.

Can you give in more detail what you re doing? It might be a problem with where
you are saving it or some other type of detail

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

[krita] [Bug 369308] UX issues with the startup splash screen / about dialog

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
This sounds like bugs in general. The links aren't clickable while Krita is
starting up. Also clicking on the splash screen on startup causes Krita to be
unresponsive and crash.

I would say we just need to disable any clicking behavior and hide any links
while Krita is starting up. Hopefully that will prevent any crashes from
happening.

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

[krita] [Bug 369191] Crash if I use next/previous key frame quickly (back and forth) and draw at the same time

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #3 from Scott Petrovic  ---
I just got this crash pretty quickly on the latest windows build.  3.0.1.90

Followed the steps pretty much perfectly and it happened withing a second or
two as soon as I started painting on the canvas.

For a graphics card, I have an NVIDIA GT650

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

[krita] [Bug 369451] brush angle tied to canvas rotation instead of being absolute

[via KDE Bugzilla]

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

--- Comment #2 from anim...@gmail.com ---
Also there's a problem with the brush being mirrored with mirrored canvas. It
might be related.

Also: all these issues happen if either tilt direction or tilt elevation is
selected for rotation.

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

[krita] [Bug 369451] brush angle tied to canvas rotation instead of being absolute

[via KDE Bugzilla]

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

anim...@gmail.com changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||anim...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from anim...@gmail.com ---
Actually it's even worse, like if the rotation of the brush depends on the
canvas rotation but the brush angle is not directly the same as the canvas
angle.

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

[krita] [Bug 367817] Krita crashes with specific animation workflow with keyframes

[Scott Petrovic via KDE Bugzilla]

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

--- Comment #2 from Scott Petrovic  ---
I just tested the latest Windows build that was generated a few hours from
downloads.kde.org. it is still crashing with those steps. Let me clarify the
steps a bit in case they weren't clear.

Steps to Reproduce.
0. Have the animation workspace open
1. Create a new document from the animation template. File > New > select
animation (selected Animation-Japanese-En). Click "use this template" button
2. right click frame 0 and click "new frame"
3. right click frame 1 and click "new frame"
4. turn on showing onion skin for the layer  
5. select frame 0
6. Krita crashes

I am on Windows 10 right now. I originally was on ubuntu when the crash
happened. I originally did this at the sprint. I thought Jouni also could
reproduce. it is a bit of a niche crash, so it probably isn't the highest
priority. Somone on IRC originally told me these steps.

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

[kdenlive] [Bug 369455] New: Version 16.08.1 breaks the Position and Zoom plugin

[via KDE Bugzilla]

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

Bug ID: 369455
   Summary: Version 16.08.1 breaks the Position and Zoom plugin
   Product: kdenlive
   Version: 16.08.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: r...@libertymail.net

After updating to Kdenlive version 16.08.1 the Position and Zoom plugin no
longer works.

Reproducible: Always

Steps to Reproduce:
1. Click on a clip in the timeline
2. In the video effects tab choose Crop and Transform => Position and Zoom
3. Add a couple of keyframes and then zoom in and out
4. Preview your clip (or render)

Actual Results:  
The red boarder and white dot will move, but the actual video clip is not
effected.

Expected Results:  
A zoom effect in the video preview and exported file.

Running up to date Fedora 24. Kdenlive installed via RPM Fusion. If you
downgrade Kdenlive to version 16.04.2, the plugin works.

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

[kmail2] [Bug 316036] autocompletion shows multiple identical results

[resplin via KDE Bugzilla]

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

--- Comment #5 from resplin  ---
I don't see this problem on recent releases.

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

[kdevelop] [Bug 369454] New: Crash when opening project

[Aleix Pol via KDE Bugzilla]

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

Bug ID: 369454
   Summary: Crash when opening project
   Product: kdevelop
   Version: 5.0.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aleix...@gmail.com

Application: kdevelop (5.0.1)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.3-2-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Was working on a session, saved my files and opened a project. Boom.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3942687840 (LWP 30154))]

Thread 14 (Thread 0x7f38f88cf700 (LWP 30547)):
#0  0x7f395172710f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f39514058e4 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f39514eef20 ) at
/home/apol/devel/frameworks/qt5/qtscript/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f3951405929 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
/home/apol/devel/frameworks/qt5/qtscript/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f3951721454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f3958b1c7df in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7f38e3306700 (LWP 30307)):
#0  0x7f395993dc40 in ?? () from /home/apol/devel/kde5/lib/libQt5Core.so.5
#1  0x7f394cb525b9 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7f394cb52f8b in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f394cb5317c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f395993e4db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /home/apol/devel/kde5/lib/libQt5Core.so.5
#5  0x7f39598eaf2a in
QEventLoop::exec(QFlags) () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#6  0x7f395971dfeb in QThread::exec() () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#7  0x7f3956bc7e34 in KDevelop::CompletionWorkerThread::run
(this=0x40df480) at
/home/apol/devel/frameworks/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#8  0x7f3959722a29 in ?? () from /home/apol/devel/kde5/lib/libQt5Core.so.5
#9  0x7f3951721454 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f3958b1c7df in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7f38faffd700 (LWP 30262)):
#0  0x7f3958b1348d in poll () from /usr/lib/libc.so.6
#1  0x7f394cb53066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f394cb5317c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f395993e4db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /home/apol/devel/kde5/lib/libQt5Core.so.5
#4  0x7f39598eaf2a in
QEventLoop::exec(QFlags) () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#5  0x7f395971dfeb in QThread::exec() () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#6  0x7f3959722a29 in ?? () from /home/apol/devel/kde5/lib/libQt5Core.so.5
#7  0x7f3951721454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f3958b1c7df in clone () from /usr/lib/libc.so.6

Thread 11 (Thread 0x7f3908b16700 (LWP 30227)):
#0  0x7f395172710f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f39597237db in QWaitCondition::wait(QMutex*, unsigned long) () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#2  0x7f395596a8df in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=0xccb6e0, th=0x7f38fc0013e0) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:594
#3  0x7f395596a760 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0xccb6e0,
th=0x7f38fc0013e0, threadWasBusy=false, suspendIfInactive=false,
justReturning=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:554
#4  0x7f39559757e4 in ThreadWeaver::WorkingHardState::applyForWork
(this=0xa12aa0, th=0x7f38fc0013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:66
#5  0x7f3955975a32 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:61
#6  0x7f395596aa4f in ThreadWeaver::Weaver::applyForWork (this=0xccb6e0,
th=0x7f38fc0013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:568
#7  0x7f395597596f in ThreadWeaver::WorkingHardState::applyForWork
(this=0xa12aa0, th=0x7f38fc0013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:73
#8  0x7f3955975a32 in non-virtual thunk to

[plasmashell] [Bug 354111] Plasma 5 login with multiple monitors is absurdly slow compared to 4.x

[Jimmy Berry via KDE Bugzilla]

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

--- Comment #19 from Jimmy Berry  ---
(In reply to Jimmy Berry from comment #18)
> (In reply to Jim Jones from comment #17)
> > (In reply to Jimmy Berry from comment #16)
> > > I do not see an appropriate status that I can set this issue, but
> > > "WAITINGFORINFO" definitely is not the case.
> > 
> > Did you try do disable the splash screen?
> 
> I am not sure how to accomplish such a feat. There does not appear to be any
> such setting in sddm via gui or config file. To what specifically are you
> referring?

Disabled in "systemsettings5 => workspace theme => splash screen" which does in
fact work around the issue.

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

[krita] [Bug 369447] The reload button stopped working.

[via KDE Bugzilla]

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

anim...@gmail.com changed:

   What|Removed |Added

 CC||anim...@gmail.com

--- Comment #1 from anim...@gmail.com ---
hmmm, I can't reproduce that (with a build from master, just updated..)
reload button works fine, both with or without dirty preset activated.

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

[skrooge] [Bug 368828] Ubuntu KF5 PPA xenial package still uses oxygen icon theme

[via KDE Bugzilla]

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

--- Comment #7 from dberg...@gmail.com ---
I get the same thing, but as you can see in the screenshot, running skrooge
from the terminal shows it's still looking for oxygen, and since I uninstalled
it on my machine, there are no icons in the main window.

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

[skrooge] [Bug 368828] Ubuntu KF5 PPA xenial package still uses oxygen icon theme

[via KDE Bugzilla]

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

--- Comment #6 from dberg...@gmail.com ---
Created attachment 101323
  --> https://bugs.kde.org/attachment.cgi?id=101323=edit
Screenshot of the bug

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

[plasmashell] [Bug 354111] Plasma 5 login with multiple monitors is absurdly slow compared to 4.x

[Jimmy Berry via KDE Bugzilla]

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

--- Comment #18 from Jimmy Berry  ---
(In reply to Jim Jones from comment #17)
> (In reply to Jimmy Berry from comment #16)
> > I do not see an appropriate status that I can set this issue, but
> > "WAITINGFORINFO" definitely is not the case.
> 
> Did you try do disable the splash screen?

I am not sure how to accomplish such a feat. There does not appear to be any
such setting in sddm via gui or config file. To what specifically are you
referring?

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

[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor

[nmset via KDE Bugzilla]

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

--- Comment #8 from nmset  ---
I 'm having these problems on one machine with nouveau.
No problems on two machines with fglrx, and another install with amdgpu-pro.

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

[korgac] [Bug 369452] New: korgac crashes when doing akonadictl restart

[Jan Binder via KDE Bugzilla]

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

Bug ID: 369452
   Summary: korgac crashes when doing akonadictl restart
   Product: korgac
   Version: 5.2.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: wh...@herr-der-mails.de

Application: korgac (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

In a terminal, just do akonadictl restart. 
Akonadi will stop and start again, kmail will show tha Akonadi unavailable
screen for a shor time and kograc will crash very reliably.

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7fc24b7fe700 (LWP 30730)):
#0  0x7fc26f2b1ee5 in g_main_context_prepare
(context=context@entry=0x7fc23c002eb0, priority=priority@entry=0x7fc24b7fdb40)
at ././glib/gmain.c:3511
#1  0x7fc26f2b28fb in g_main_context_iterate
(context=context@entry=0x7fc23c002eb0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3907
#2  0x7fc26f2b2aec in g_main_context_iteration (context=0x7fc23c002eb0,
may_block=1) at ././glib/gmain.c:3988
#3  0x7fc2770db51b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc27708319a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc276ea8e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc276eadd78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc26f7d5464 in start_thread (arg=0x7fc24b7fe700) at
pthread_create.c:333
#8  0x7fc2765b297f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fc24bfff700 (LWP 26993)):
#0  0x7fc2765a950d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc26f2b29d6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7fc244003020, timeout=, context=0x7fc244000990)
at ././glib/gmain.c:4226
#2  0x7fc26f2b29d6 in g_main_context_iterate
(context=context@entry=0x7fc244000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3922
#3  0x7fc26f2b2aec in g_main_context_iteration (context=0x7fc244000990,
may_block=1) at ././glib/gmain.c:3988
#4  0x7fc2770db51b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc27708319a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc276ea8e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc276eadd78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc26f7d5464 in start_thread (arg=0x7fc24bfff700) at
pthread_create.c:333
#9  0x7fc2765b297f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7fc258874700 (LWP 26992)):
#0  0x7fc2765a557d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc26f2f6c60 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fc258873a60, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fc26f2f6c60 in g_wakeup_acknowledge (wakeup=0x7fc24c0025a0) at
././glib/gwakeup.c:210
#3  0x7fc26f2b2485 in g_main_context_check
(context=context@entry=0x7fc25990, max_priority=2147483647,
fds=fds@entry=0x7fc250002e20, n_fds=n_fds@entry=1) at ././glib/gmain.c:3705
#4  0x7fc26f2b2974 in g_main_context_iterate
(context=context@entry=0x7fc25990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#5  0x7fc26f2b2aec in g_main_context_iteration (context=0x7fc25990,
may_block=1) at ././glib/gmain.c:3988
#6  0x7fc2770db51b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc27708319a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc276ea8e53 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fc276eadd78 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fc26f7d5464 in start_thread (arg=0x7fc258874700) at
pthread_create.c:333
#11 0x7fc2765b297f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fc259a85700 (LWP 26975)):
#0  0x7fc2765a950d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc26f2b29d6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7fc24c022130, timeout=, context=0x7fc24c000990)
at ././glib/gmain.c:4226
#2  0x7fc26f2b29d6 in 

[KScreen] [Bug 369422] Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kscr |http://commits.kde.org/kscr
   |een/7c3839083d4d2d77b63d0c2 |een/7d8ec60c60477d68e91e9bc
   |cde4ad87994380e9a   |68f334ff286cffc73

--- Comment #2 from Sebastian Kügler  ---
Git commit 7d8ec60c60477d68e91e9bc68f334ff286cffc73 by Sebastian Kügler.
Committed on 27/09/2016 at 22:31.
Pushed by sebas into branch 'Plasma/5.8'.

Increase precision of refresh rate

It's pretty common to have slightly different refresh rates, and since
this is currently hidden in the advanced section, more precision is OK.
FIXED-IN:5.8.0

M  +1-1kcm/src/outputconfig.cpp

http://commits.kde.org/kscreen/7d8ec60c60477d68e91e9bc68f334ff286cffc73

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

[KScreen] [Bug 369422] Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.8.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kscr
   ||een/7c3839083d4d2d77b63d0c2
   ||cde4ad87994380e9a

--- Comment #1 from Sebastian Kügler  ---
Git commit 7c3839083d4d2d77b63d0c2cde4ad87994380e9a by Sebastian Kügler.
Committed on 27/09/2016 at 22:28.
Pushed by sebas into branch 'master'.

Increase precision of refresh rate

It's pretty common to have slightly different refresh rates, and since
this is currently hidden in the advanced section, more precision is OK.
FIXED-IN:5.8.0

M  +1-1kcm/src/outputconfig.cpp

http://commits.kde.org/kscreen/7c3839083d4d2d77b63d0c2cde4ad87994380e9a

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

[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #35 from Wolfgang Bauer  ---
This should fix it though:
https://codereview.qt-project.org/#/c/140750/

And it fixes bug#359758 as well. ;-)

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

[KScreen] [Bug 369384] Dual Monitor: only unified output

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #5 from Sebastian Kügler  ---
So, what happens if you drag the HDMI2 SyncMaster output aside in the top
section?

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

[frameworks-kxmlgui] [Bug 369276] KActionCollection, menu/action reuse and the native Mac menubar

[Marko Käning via KDE Bugzilla]

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

Marko Käning  changed:

   What|Removed |Added

 CC||mk-li...@mailbox.org

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

[krita] [Bug 369451] New: brush angle tied to canvas rotation instead of being absolute

[via KDE Bugzilla]

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

Bug ID: 369451
   Summary: brush angle tied to canvas rotation instead of being
absolute
   Product: krita
   Version: 3.0.1
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: kaer...@gmail.com

when used with "tilt direction" the brush angle is tied to the canvas view
rotation. The brush angle is offset by the rotated canvas view, where in
precedent krita versions it was absolute, and easy to predict

Reproducible: Always

Steps to Reproduce:
1.select a brush with a "tilt direction" "rotation" sensor
2.rotate your canvas with shift+middle button or numpad
3.see how the angle is dependent of the canvas view

Actual Results:  
the brush angle is offset by the canvas view angle

Expected Results:  
the brush angle should remain absolute, and tied only to the stylus tilt
direction

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[via KDE Bugzilla]

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

--- Comment #5 from ker...@gmail.com ---
   Thanks for your support with this. I don't have multiple MLT or ffmpeg
installed. I don't believe it would be possible as I only use pacman (Arch's
package manager) to install programs. In Kdenlive configuration I added all
paths to ffplay, ffmpeg and all other paths correctly which I've checked with
pacman -Ql and whereis commands. 

   On the other hand I've tried Openshot (I think it also uses MLT) and it
imports videos without problem.

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

[kmymoney4] [Bug 369448] ofx import results in duplicate transactions

[Swj via KDE Bugzilla]

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

--- Comment #3 from Swj  ---
Yes, as you say, I did succeed with an OFX Direct Connect.
It would be nice if KMM would ask if I want to merge  similar transactions (
that have the same payee, date, and amount).  This would also handle cases
where transactions were entered manually or imported from some other money
program.

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

[Planet KDE] [Bug 369450] New: Multiple monitor desktops & backgrounds are simply blank.

[Tim Bess via KDE Bugzilla]

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

Bug ID: 369450
   Summary: Multiple monitor desktops & backgrounds are simply
blank.
   Product: Planet KDE
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: ranveeraggar...@gmail.com
  Reporter: timber...@gmail.com

I'm sure this is likely a duplicate and someone else running 3 monitors has
reported it, but search did not work for me. I run Neon-user with the latest
updates as of today, and any monitors that are are on the VGA displays simply
appear blank. They do not get desktop backgrounds, there is nothing that
appears when I left or right click on them and nothing happens. This is NOT a
fatal error. If I send an application to a second or third display -- the
application goes there and appears, and it has no issues with multiple desktops
working as far as displaying the applications, but those displays any without
an application also appears blank -- whether its cube or any other type of
switching. Hardware is a core i5 2800, HD6870 on the open source driver as AMD
hasn't released a new one - one main monitor on DVI, secondary monitors on VGA
to DVI adapter and display port to VGA adapter. They are real actual CRTs if
its makes any difference for the secondary displays. I haven't tested this with
multiple DVI displays or DVI+HDMI. 

Reproducible: Always

Steps to Reproduce:
1.Plug in VGA monitor as secondary display. (that one is blank with only 2)
2. Plus in VGA monitor as third display. (with 3 -- second two are blank)
3. Boot into actual session (no VM). 

Actual Results:  
Boom, same bug. Applications can be displayed on them, but backgrounds and
other functions (such as widgets) cannot be moved to them. The monitors do show
up under system settings, and otherwise function as intended. Maybe this is QT
bug upstream? Kwin? 

Expected Results:  
Expected similar behavior to plasma 5.6.5 where all displays show. Display bugs
like this should be a priority as they make an extremely bad impression on the
end user and may terminate someone doing any further testing if they think Neon
can't see their displays. 

KDE Neon User
Plasma 5.7.5
Frameworks 5.26.0
QT 5.7.0
Kernel 4.4.0-38
64 bit

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

[kmymoney4] [Bug 369448] ofx import results in duplicate transactions

[Jack via KDE Bugzilla]

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #2 from Jack  ---
I can confirm this is the problem.  In a downloaded qfx file, BOA uses
something like
201609101 but in a direct connect download, it uses
D2016254T1048539.  There are other differences also (at least in my
example) such as the file not including the  (which in the direct connect
seems only to be part of the  anyway, but it is the FITID difference that
causes KMM not to recognize the duplicate transaction.

Unfortunately, I predict 0% chance of getting BOA to fix this, since it seems
absolutely impossible to talk to anyone who knows anything and can do anything
except follow their script.  In any case, I'm really curious if anyone has any
idea why they re-enabled direct connect, after going to all that trouble to
discontinue it.

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

[kdenlive] [Bug 367448] git master - suggest replacing "Unset Preivew Zone" text with "Remove Preview Zone" in preview zone menu

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kden
   ||live/58270892e65c6044eadd2c
   ||20fe0cde9a190002f7
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Jean-Baptiste Mardelle  ---
Git commit 58270892e65c6044eadd2c20fe0cde9a190002f7 by Jean-Baptiste Mardelle.
Committed on 27/09/2016 at 21:45.
Pushed by mardelle into branch 'master'.

Rename "Unset/Clear preview zone to Remove..."
REVIEW: 129056

M  +2-0data/pics/CMakeLists.txt
A  +4-0data/pics/breeze-dark/dk_preview-remove-all.svg
A  +9-0data/pics/breeze-light/lt_preview-remove-all.svg
M  +1-0src/icons.qrc
M  +2-2src/mainwindow.cpp

http://commits.kde.org/kdenlive/58270892e65c6044eadd2c20fe0cde9a190002f7

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

[kmymoney4] [Bug 369449] line in ofx file imported switches payee to MEMO

[Bob Ewart via KDE Bugzilla]

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

Bob Ewart  changed:

   What|Removed |Added

 CC||jinni...@bobsown.net

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

[kmymoney4] [Bug 369449] New: line in ofx file imported switches payee to MEMO

[Bob Ewart via KDE Bugzilla]

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

Bug ID: 369449
   Summary:  line in ofx file imported switches payee to
MEMO
   Product: kmymoney4
   Version: 4.8.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: jinni...@bobsown.net

File->Import->OFX
Chase credit card ofx downloads recently added a blank  line to a
transaction.

DEBIT
201609...[0:GMT]
-nn.nn
201609...
AMAZON MKTPLACE PMTS

null

In this case, the payee is 'null'.  If the  line is removed, it is
imported with 'AMAZON MKTPLACE PMTS' as payee

Note: When you are not doing online import, you don't have the option of what
field to use as payee

Reproducible: Always

Steps to Reproduce:
1. Add a  line to one transaction between  and   lines
2. File->Import-OFX
3. select the test file

Actual Results:  
The payee is shown as whatever is in the MEMO

Expected Results:  
Should always be what is in the NAME

If there is no MEMO line the payee is set to the NAME field even if there is a
CATEGORY

I'm running 4.8.0 compiled from source on openSUSE 13.2.  It also happened on
4.72.

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

[kmymoney4] [Bug 369448] ofx import results in duplicate transactions

[Jack via KDE Bugzilla]

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

--- Comment #1 from Jack  ---
When you say you did an OFX update, did you download a new file, or did you
actually succeed with an OFX Direct Connect?  If the latter, I suspect that the
download included transaction IDs (which KMM uses to uniquely identify
downloaded transactions) which were NOT present in the previously downloaded
qfx file.  If that is the case, then you should not have this problem again,
unless mixing direct connect downloaded transactions with those imported from
file.

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

[krita] [Bug 369400] onion skins do not show up

[via KDE Bugzilla]

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

--- Comment #2 from trishhuyn...@gmail.com ---
(In reply to joupent from comment #1)
> The problem may be the bad default onion skin settings we had in the 3.0
> release. Please check that the top of the onion skins docker has highlights
> on the appropriate relative frame numbers (e.g. -1, 0 and 1). You can toggle
> the state by clicking each number. The defaults have been fixed in 3.0.1,
> although old settings may persist.

Ah, I see now! Thank you!

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

[krita] [Bug 369400] onion skins do not show up

[via KDE Bugzilla]

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

trishhuyn...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

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

[systemsettings] [Bug 369423] I went to update? Click and got this?

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Christoph Feck  ---
Please report this issue to the bug tracker of your distribution.

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

[kmymoney4] [Bug 369448] New: ofx import results in duplicate transactions

[Swj via KDE Bugzilla]

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

Bug ID: 369448
   Summary: ofx import results in duplicate transactions
   Product: kmymoney4
   Version: 4.8.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: onlinebanking
  Assignee: kmymoney-de...@kde.org
  Reporter: s...@pobox.com

I previously had downloaded and imported a qfx file from the Bank of America
website for, for my BOA credit card.  Today I did an ofx update which resulted
in many duplicate transactions in my BOA credit card ledger.

Reproducible: Always

Steps to Reproduce:
1. have a BOA credit card account
2.download and run .qfx file from www.bankofamerica.com
3. do account.update account to run ofx import.

Actual Results:  
many duplicate transactions in my BOA credit card ledger

Expected Results:  
duplicate transactions to be recognized and ignored

The ofx wasn't working for a long time with BOA, now it started working again

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

[systemsettings] [Bug 369436] All controls for sound are up and running no sound comes out

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||cf...@kde.org
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Christoph Feck  ---
Please ask for help in a forum of your distribution.

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

[krita] [Bug 369447] New: The reload button stopped working.

[wolthera via KDE Bugzilla]

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

Bug ID: 369447
   Summary: The reload button stopped working.
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com

The reload button, for reloading presets that have been dirtied... stopped
working. It still works in the alpha. I started noticing weirdness in the
preset-chooser branch, but cannot recall clearly if it's fully preset there.

Reproducible: Always

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

[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor

[Lemmiwinks via KDE Bugzilla]

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

--- Comment #7 from Lemmiwinks  ---
Which graphics driver are you using? Are we all using nouveau?

I renamed kmail2rc in .~/.config/ to kmail2rc.old and got the following error
when starting kmail:

bash-4.3$ kmail
"Tag 'a' is not defined in message {<__kuit_internal_top__>KMail has many
powerful features that are described in th...}."
"Tag 'br' is not defined in message {<__kuit_internal_top__>Thank you,The
KMail Team}."
this does not work on a KActionCollection containing actions!
QXcbConnection: XCB error: 3 (BadWindow), sequence: 632, resource id: 33823512,
major code: 40 (TranslateCoords), minor code: 0
nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch21: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch21: buf  0002 0004 0004 
*** Error in `kmail': double free or corruption (fasttop): 0x559f6e7105b0
***
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
KCrash: Application 'kmail' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Unable to start Dr. Konqi

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

[kdenlive] [Bug 360084] 15.13.0 git master - Audio is not synced with 4k UHD video during playback -- video plays faster (sample clip included)

[Jesse via KDE Bugzilla]

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

--- Comment #11 from Jesse  ---
Confirmed, playing the sample video I provided using melt reproduces this issue
(and it was on a laptop workstation with integrated graphics). ffplay is
slightly closer to syncronicity, but the video is still playing slightly
faster. Playing the same video file in VLC player or Dragon Player doesn't
reproduce the issue.

So... this is an MLT issue? Do I submit a bug to Dan and MLT for testing?

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

[kdenlive] [Bug 366679] git master - Left-clicking track header shouldn't automatically highlight the "Properties" Widget

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Jesse  ---
Wegwerf fixed this with a recent patch, it is now optional via a checkbox in
the configuration window. Problem solved! Thanks guys. Closing bug.

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

[kdevplatform] [Bug 354706] comitting single file change first tries to commit all changed files

[Nicolas Werner via KDE Bugzilla]

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

Nicolas Werner  changed:

   What|Removed |Added

 Resolution|INVALID |FIXED

--- Comment #5 from Nicolas Werner  ---
Can't reproduce it any more. Seems to be fixed and work as intended now.

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

[valgrind] [Bug 369446] valgrind crashes on unknown fcntl command

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101322
  --> https://bugs.kde.org/attachment.cgi?id=101322=edit
Don't crash, but warn and return EINVAL on unknown fcntl command.

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

[valgrind] [Bug 369446] New: valgrind crashes on unknown fcntl command

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369446
   Summary: valgrind crashes on unknown fcntl command
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

When encountering an unknown fcntl command valgrind crashes with an assertion
message: valgrind: m_syswrap/syswrap-linux.c:5490
(vgSysWrap_linux_sys_fcntl_before): Assertion 'Unimplemented functionality'
failed.

Valgrind should just warn the user the fcntl command is unimplemented and
return EINVAL like the kernel would.

LTP testcases/kernel/syscalls/fcntl/fcntl13

Reproducible: Always

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

[muon] [Bug 369301] Muon doesn't find packages after installing a package

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
(In reply to Tony from comment #1)
> I used to have a similar issue (before i ditch it and went full terminal...)
> and it was related to muon building a search index.  Let it do its think,
> close and open it again, that's what worked for me.

The search doesn't start to work even if you wait until it finishes rebuilding
the index. Only restart helps.

But it would still be a bug even if it started working after rebuilding the
index had completed. Somehow other package managers don't have this problem.

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

[kdenlive] [Bug 367448] git master - suggest replacing "Unset Preivew Zone" text with "Remove Preview Zone" in preview zone menu

[Wegwerf via KDE Bugzilla]

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

--- Comment #3 from Wegwerf  ---
Nah, quick'n'easy fix, just changing two text strings. And I prefer consistent
UI experience myself. :)

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

[konqueror] [Bug 369445] New: reCAPTHCA

[mr . FIX via KDE Bugzilla]

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

Bug ID: 369445
   Summary: reCAPTHCA
   Product: konqueror
   Version: 4.14.3
  Platform: FreeBSD Ports
OS: FreeBSD
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: 380671842...@sms.kyivstar.net

Application: konqueror (4.14.3)
KDE Platform Version: 4.14.3
Qt Version: 4.8.7
Operating System: FreeBSD 10.3-RELEASE amd64
Distribution (Platform): FreeBSD Ports

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

...try to send SMS via web intarface. When push reCAPTCHA service radio button
(I`m not a robot), all  Konqueror windows was closed.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
[Current thread is 1 (Thread 829435c00 (LWP 101410/kdeinit4))]

Thread 4 (Thread 809406400 (LWP 101190/kdeinit4)):
[KCrash Handler]
#8  0x00082022274d in KHTMLPart::document () from
/usr/local/lib/libkhtml.so.5
#9  0x0008204651e1 in KJS::Identifier::qstring () from
/usr/local/lib/libkhtml.so.5
#10 0x0008204660bf in KJS::Identifier::qstring () from
/usr/local/lib/libkhtml.so.5
#11 0x00080219f7a3 in QObject::event () from
/usr/local/lib/qt4/libQtCore.so.4
#12 0x00080281183d in QApplicationPrivate::notify_helper () from
/usr/local/lib/qt4/libQtGui.so.4
#13 0x000802812faa in QApplication::notify () from
/usr/local/lib/qt4/libQtGui.so.4
#14 0x000800c747d7 in KApplication::notify () from
/usr/local/lib/libkdeui.so.5
#15 0x00080218c596 in QCoreApplication::notifyInternal () from
/usr/local/lib/qt4/libQtCore.so.4
#16 0x0008021bb853 in QEventDispatcherUNIXPrivate::processThreadWakeUp ()
from /usr/local/lib/qt4/libQtCore.so.4
#17 0x0008021b95c1 in QEventDispatcherGlib::QEventDispatcherGlib () from
/usr/local/lib/qt4/libQtCore.so.4
#18 0x0008079e4458 in g_main_context_dispatch () from
/usr/local/lib/libglib-2.0.so.0
#19 0x0008079e4794 in g_main_context_pending () from
/usr/local/lib/libglib-2.0.so.0
#20 0x0008079e4824 in g_main_context_iteration () from
/usr/local/lib/libglib-2.0.so.0
#21 0x0008021b9171 in QEventDispatcherGlib::processEvents () from
/usr/local/lib/qt4/libQtCore.so.4
#22 0x0008028b2cad in QX11Info::isCompositingManagerRunning () from
/usr/local/lib/qt4/libQtGui.so.4
#23 0x000802189bbf in QEventLoop::exec () from
/usr/local/lib/qt4/libQtCore.so.4
#24 0x00080218cb4d in QCoreApplication::exec () from
/usr/local/lib/qt4/libQtCore.so.4
#25 0x000816f95270 in kdemain () from
/usr/local/lib/libkdeinit4_konqueror.so
#26 0x0040a636 in ?? ()
#27 0x0040ae91 in ?? ()
#28 0x00407f1a in ?? ()
#29 0x00407ae5 in ?? ()
#30 0x00404d1f in ?? ()
#31 0x00080063 in ?? ()
#32 0x in ?? ()

Thread 3 (Thread 821cdd000 (LWP 101331/kdeinit4)):
#0  0x000803ed506c in pthread_mutex_unlock () from /lib/libthr.so.3
#1  0x0008079e1635 in g_main_context_acquire () from
/usr/local/lib/libglib-2.0.so.0
#2  0x0008079e4617 in g_main_context_pending () from
/usr/local/lib/libglib-2.0.so.0
#3  0x0008079e4824 in g_main_context_iteration () from
/usr/local/lib/libglib-2.0.so.0
#4  0x0008021b91a0 in QEventDispatcherGlib::processEvents () from
/usr/local/lib/qt4/libQtCore.so.4
#5  0x000802189bbf in QEventLoop::exec () from
/usr/local/lib/qt4/libQtCore.so.4
#6  0x000802089f39 in QThread::exec () from
/usr/local/lib/qt4/libQtCore.so.4
#7  0x00080c9d8214 in KIO::HostInfo::setTTL () from
/usr/local/lib/libkio.so.5
#8  0x00080208bb4c in QThreadStorageData::finish () from
/usr/local/lib/qt4/libQtCore.so.4
#9  0x000803ece855 in pthread_create () from /lib/libthr.so.3
#10 0x in ?? ()

Thread 2 (Thread 82efa2800 (LWP 101406/kdeinit4)):
#0  0x000803eda13c in pthread_cleanup_pop () from /lib/libthr.so.3
#1  0x000803ed859e in _pthread_cond_wait () from /lib/libthr.so.3
#2  0x000823ace6cb in vlc_cond_timedwait () from
/usr/local/lib/libvlccore.so.8
#3  0x000823a8d678 in input_Read () from /usr/local/lib/libvlccore.so.8
#4  0x000823a8df07 in input_Read () from /usr/local/lib/libvlccore.so.8
#5  0x000803ece855 in pthread_create () from /lib/libthr.so.3
#6  0x in ?? ()

Thread 1 (Thread 829435c00 (LWP 101410/kdeinit4)):
#0  0x000804231e9a in _write () from /lib/libc.so.7
#1  0x0008042318b7 in getdtablesize () from /lib/libc.so.7
#2  0x0008042314a8 in fflush () from /lib/libc.so.7
#3  0x00080420fc30 in __swbuf () from /lib/libc.so.7
#4  0x000823ac6571 in vlc_LogSet () from /usr/local/lib/libvlccore.so.8
#5  0x000823ac6248 in vlc_vaLog () from /usr/local/lib/libvlccore.so.8
#6  0x000823ac6125 in vlc_Log () from /usr/local/lib/libvlccore.so.8
#7  0x000829c168c7 in vlc_entry_license__2_2_0b () from

[krita] [Bug 369444] No pen pressure with Ugee M708

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #3 from Boudewijn Rempt  ---
I cannot help that. Without hardware, it's impossible to fix. No matter what
other applications that use other toolkits do.

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

[kdenlive] [Bug 367448] git master - suggest replacing "Unset Preivew Zone" text with "Remove Preview Zone" in preview zone menu

[Jesse via KDE Bugzilla]

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

--- Comment #2 from Jesse  ---
Dude, you are on a ROLL! :)

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

[kmymoney4] [Bug 369438] Allow selection of OFX tag to use for Payee, even if account not mapped

[Bob Ewart via KDE Bugzilla]

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

Bob Ewart  changed:

   What|Removed |Added

 CC||jinni...@bobsown.net

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

[krita] [Bug 369444] No pen pressure with Ugee M708

[via KDE Bugzilla]

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

--- Comment #2 from st...@tdrtax.co.uk ---
Shame. It works just fine in gimp, blender etc. It's only Krita that there's no
pressure.

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

[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played

[Try Again via KDE Bugzilla]

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

--- Comment #15 from Try Again  ---
Tested on git head, works in both preview and render modes.

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

[krita] [Bug 369413] Make it possible to have brushes bigger then 1000 pixels

[Bollebib via KDE Bugzilla]

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

--- Comment #2 from Bollebib  ---
A second size slider perhaps? that you can add in the toolbar settings?

another way would be like the brush pattern  scale dropdown of x1 ,x2,x10 to
change the slider scale


not very elegant but it could work

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

[krita] [Bug 369444] No pen pressure with Ugee M708

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |LATER

--- Comment #1 from Boudewijn Rempt  ---
I'm sorry, but that log simply means that the driver is only sending mouse
events to Krita. If we're not getting tablet events, there's nothing we can do.
Especially since Ugee hasn't supplied test hardware. When they do, we can look
into the problem, but at the moment, it's out of our hands.

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

[digikam] [Bug 355861] Sort images by lens model

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 355838] Sort images by orientation mode

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 350098] Sort images on photograph specific metadata

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 368468] digiKam hanging at start up with a collection that has >100000 sub folders

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #7 from Maik Qualmann  ---
Now here less than 1 minute for 10.000 albums. But I think 100.000 albums are
not really to handle.

Maik

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

[digikam] [Bug 326404] Unable to select picture in map search view

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 368468] digiKam hanging at start up with a collection that has >100000 sub folders

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #6 from Maik Qualmann  ---
Git commit 4ebe5585c7f9c37842c541304cdd0e63912c7cb8 by Maik Qualmann.
Committed on 27/09/2016 at 20:34.
Pushed by mqualmann into branch 'master'.

optimization ImageAlbumFilterModel

M  +55   -13   libs/models/imagealbumfiltermodel.cpp
M  +5-0libs/models/imagealbumfiltermodel.h

http://commits.kde.org/digikam/4ebe5585c7f9c37842c541304cdd0e63912c7cb8

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

[muon] [Bug 369301] Muon doesn't find packages after installing a package

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #1 from Tony  ---
I used to have a similar issue (before i ditch it and went full terminal...)
and it was related to muon building a search index.  Let it do its think, close
and open it again, that's what worked for me.

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

[kdenlive] [Bug 368235] Timeline hanging at startup

[Wegwerf via KDE Bugzilla]

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

--- Comment #2 from Wegwerf  ---
Benoit, we cannot reproduce; there's unfortunately almost no chance of fixing
this. I suspect something in your Ubuntu setup. Which overall window theme did
you install? A Gnome one or the KDE Frameworks 5 one?

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

[kdenlive] [Bug 369058] Kenlive crashing when files are imported

[Wegwerf via KDE Bugzilla]

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

--- Comment #4 from Wegwerf  ---
The crash happens here:

Thread 11 (Thread 0x7f55427fc700 (LWP 14608)): [KCrash Handler] #5
0x7f55a53a7a3c in _dl_relocate_object () from /lib64/ld-linux-x86-64.so.2
#6 0x7f55a53afac1 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2

This looks like there is something wrong with overall shared library setup. Do
you have multiple MLT and/or ffmpeg versions installed? Do Kdenlive's
configuration properly point to the corresponding MLT and ffmpeg binaries and
shared libraries?

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

[kdenlive] [Bug 367448] git master - suggest replacing "Unset Preivew Zone" text with "Remove Preview Zone" in preview zone menu

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||wegwerf-1-...@gmx.de
   Assignee|j...@kdenlive.org |wegwerf-1-...@gmx.de
 Ever confirmed|0   |1

--- Comment #1 from Wegwerf  ---
Patch submitted, https://git.reviewboard.kde.org/r/129056/

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

[valgrind] [Bug 369441] New: bad lvec argument crashes process_vm_readv/writev syscall wrappers

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369441
   Summary: bad lvec argument crashes process_vm_readv/writev
syscall wrappers
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

LTP testcases/kernel/syscalls/cma/process_vm01 crashes valgrind:

==3940== Syscall param process_vm_readv(lvec) points to unaddressable byte(s)
==3940==at 0x4129977: syscall (in /usr/lib/libc-2.23.so)
==3940==by 0x804A414: test_process_vm_readv (process_vm.h:42)
==3940==by 0x804A414: cma_test_params_read (process_vm01.c:137)
==3940==by 0x8049E33: cma_test_iov_invalid (process_vm01.c:294)
==3940==by 0x8049E33: cma_test_errnos (process_vm01.c:410)
==3940==by 0x8049E33: main (process_vm01.c:91)
==3940==  Address 0x is not stack'd, malloc'd or (recently) free'd
==3940== 
--3940-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exit
ing
--3940-- si_code=1;  Faulting address: 0x3;  sp: 0x628dde4c

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==3940==at 0x380A3E79: vgSysWrap_linux_sys_process_vm_readv_before
(syswrap-linux.c:5012)

==3961== Syscall param process_vm_writev(lvec) points to unaddressable byte(s)
==3961==at 0x4129977: syscall (in /usr/lib/libc-2.23.so)
==3961==by 0x804A3C4: test_process_vm_writev (process_vm.h:55)
==3961==by 0x804A3C4: cma_test_params_write (process_vm01.c:145)
==3961==by 0x8049E33: cma_test_iov_invalid (process_vm01.c:294)
==3961==by 0x8049E33: cma_test_errnos (process_vm01.c:410)
==3961==by 0x8049E33: main (process_vm01.c:91)
==3961==  Address 0x is not stack'd, malloc'd or (recently) free'd
==3961== 
--3961-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exit
ing
--3961-- si_code=1;  Faulting address: 0x3;  sp: 0x629a8e4c

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==3961==at 0x380A40F9: vgSysWrap_linux_sys_process_vm_writev_before
(syswrap-linux.c:5050)


Reproducible: Always

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

[plasma-integration] [Bug 369319] Black screen in Plasma Wayland session

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #1 from Tony  ---
I have a gtx 760 i've tried "nouveau.noaccel=1" due to "hangs" i was getting on
wayland as well,  the black screen happens due it. Don't boot with it.

 Sadly i dont know a "workaround", in my case i just don't dare to click on
anything on the "panel" when i am on wayland else my pc hangs.

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

[krita] [Bug 369444] New: No pen pressure with Ugee M708

[via KDE Bugzilla]

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

Bug ID: 369444
   Summary: No pen pressure with Ugee M708
   Product: krita
   Version: 3.0.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: st...@tdrtax.co.uk

Drawing with the Ugee M708 gives no pressure sensitivity. Only a solid stroke
(regardless of pen chosen)

Reproducible: Always

Steps to Reproduce:
1. Start Krita
2. Draw
3.

Actual Results:  
No pen pressure is recognised

Expected Results:  
Variable pressure

Debugging output:

lsmod

[code]
Module  Size  Used by
uinput 20480  1
rfcomm 61440  4
fuse   98304  1
bnep   20480  2
msr16384  0
rc_msi_digivox_ii  16384  0
snd_hda_codec_realtek69632  1
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
tda18271   45056  1
af9013 28672  1
nvidia_drm 53248  1
nvidia_modeset765952  6 nvidia_drm
nvidia  11866112  92 nvidia_modeset
snd_hda_codec_hdmi 45056  1
uvcvideo   86016  0
btusb  40960  0
btrtl  16384  1 btusb
videobuf2_vmalloc  16384  1 uvcvideo
btbcm  16384  1 btusb
btintel16384  1 btusb
videobuf2_memops   16384  1 videobuf2_vmalloc
snd_usb_audio 151552  1
videobuf2_v4l2 20480  1 uvcvideo
bluetooth 454656  29 bnep,btbcm,btrtl,btusb,rfcomm,btintel
videobuf2_core 36864  2 uvcvideo,videobuf2_v4l2
snd_usbmidi_lib28672  1 snd_usb_audio
usblp  20480  0
videodev  151552  3 uvcvideo,videobuf2_core,videobuf2_v4l2
snd_rawmidi28672  1 snd_usbmidi_lib
rfkill 20480  3 bluetooth
snd_seq_device 16384  1 snd_rawmidi
media  32768  2 uvcvideo,videodev
dvb_usb_af9015 28672  0
kvm_amd69632  0
dvb_usb_v2 32768  1 dvb_usb_af9015
dvb_core  106496  1 dvb_usb_v2
input_leds 16384  0
rc_core24576  4 rc_msi_digivox_ii,dvb_usb_v2,dvb_usb_af9015
led_class  16384  1 input_leds
kvm   507904  1 kvm_amd
evdev  24576  34
joydev 20480  0
mousedev   20480  0
mac_hid16384  0
irqbypass  16384  1 kvm
pcspkr 16384  0
psmouse   118784  0
drm_kms_helper118784  1 nvidia_drm
r8169  77824  0
drm   294912  4 drm_kms_helper,nvidia_drm
mii16384  1 r8169
k10temp16384  0
syscopyarea16384  1 drm_kms_helper
sysfillrect16384  1 drm_kms_helper
sysimgblt  16384  1 drm_kms_helper
fb_sys_fops16384  1 drm_kms_helper
snd_hda_intel  32768  3
snd_hda_codec 106496  4
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_hda_core   65536  5
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
snd_pcm86016  5
snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
snd_timer  28672  1 snd_pcm
snd65536  20
snd_hda_codec_realtek,snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
i2c_nforce216384  0
soundcore  16384  1 snd
shpchp 32768  0
wmi16384  0
fjes   28672  0
button 16384  0
acpi_cpufreq   20480  0
tpm_tis20480  0
tpm36864  1 tpm_tis
sch_fq_codel   20480  2
vboxnetadp 28672  0
pci_stub   16384  1
vboxpci24576  0
vboxnetflt 28672  0
vboxdrv   385024  3 vboxnetadp,vboxnetflt,vboxpci
hid_uclogic16384  0
hid_kye16384  0
loop   28672  0
it87   45056  0
hwmon_vid  16384  1 it87
ip_tables  24576  0
x_tables   28672  1 ip_tables
ext4  516096  6
crc16  16384  2 ext4,bluetooth
jbd2   90112  1 ext4
mbcache16384  7 ext4
hid_generic16384  0
usbhid 45056  0
hid   114688  4 hid_generic,hid_uclogic,hid_kye,usbhid
sr_mod 24576  0
cdrom  49152  1 sr_mod
sd_mod 36864  9
uas24576  0
usb_storage61440  1 uas
ata_generic16384  0
pata_acpi  

[krita] [Bug 369443] New: Unable to navigate in layer stack past any mask layer via hotkey

[rvz3366 via KDE Bugzilla]

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

Bug ID: 369443
   Summary: Unable to navigate in layer stack past any mask layer
via hotkey
   Product: krita
   Version: 3.0.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: rvz03...@xzsok.com

Any mask layer is dead stop in stack while navigating via hotkeys next/previous
layer. If hotkey is pressed for autorepeating it can skim through mask layers.

Reproducible: Always

Steps to Reproduce:
1. Create mask layer.
2. Try to navigate through it in layer stack via activate next/previous layer
hotkeys.
3. Hotkeys stop working when mask layer (Transparent, Transform, Filter mask,
Local selection)  is selected.


Expected Results:  
It should be possible to navigate through mask layers via hotkeys.

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

[dolphin] [Bug 369442] New: Crash when copying directory from tarball

[via KDE Bugzilla]

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

Bug ID: 369442
   Summary: Crash when copying directory from tarball
   Product: dolphin
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: linus.kardell+kdeb...@gmail.com

Application: dolphin (15.12.3)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

Copying the eclipse-installer directory from the eclipse neon tarball (viewing
it as a directory) and pasting it outside.
Can't get it to happen again with the same file, but it happened again once
with a different file.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcb8e01f7c0 (LWP 878))]

Thread 4 (Thread 0x7fcb65dae700 (LWP 882)):
#0  0x7fcb80fc7cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fcb80f854b9 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fcb80f85d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fcb80f85f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fcb87c41f4b in QEventDispatcherGlib::processEvents
(this=0x7fcb68e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fcb87bf189b in QEventLoop::exec (this=this@entry=0x7fcb65dade10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7fcb87a3802a in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7fcb87a3c859 in QThreadPrivate::start (arg=0x1faa9a0) at
thread/qthread_unix.cpp:344
#8  0x7fcb832f80a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fcb8d8ef02d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fcb6700 (LWP 880)):
#0  0x7fcb80fc7cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fcb80f856a1 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fcb80f85dcf in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fcb80f85f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fcb87c41f4b in QEventDispatcherGlib::processEvents
(this=0x7fcb680008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fcb87bf189b in QEventLoop::exec (this=this@entry=0x7fcb6fffede0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7fcb87a3802a in QThread::exec (this=this@entry=0x7fcb882bfd00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x7fcb88056465 in QDBusConnectionManager::run (this=0x7fcb882bfd00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:196
#8  0x7fcb87a3c859 in QThreadPrivate::start (arg=0x7fcb882bfd00 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
#9  0x7fcb832f80a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7fcb8d8ef02d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fcb75ec9700 (LWP 879)):
#0  0x7fcb8d8e6bfd in poll () from /lib64/libc.so.6
#1  0x7fcb806d1422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fcb806d300f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fcb78a55469 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fcb87a3c859 in QThreadPrivate::start (arg=0x1870ea0) at
thread/qthread_unix.cpp:344
#5  0x7fcb832f80a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fcb8d8ef02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fcb8e01f7c0 (LWP 878)):
[KCrash Handler]
#6  QVariant::userType (this=this@entry=0x0) at kernel/qvariant.cpp:1875
#7  0x7fcb88061cb6 in QDBusConnectionPrivate::deliverCall
(this=0x7fcb68009dc0, object=0x1f32720, msg=..., metaTypes=..., slotIdx=7) at
qdbusintegrator.cpp:924
#8  0x7fcb87c1cdc6 in QObject::event (this=0x1f32720, e=) at
kernel/qobject.cpp:1263
#9  0x7fcb88d40a9c in QApplicationPrivate::notify_helper (this=, receiver=0x1f32720, e=0x7fcb680099a0) at kernel/qapplication.cpp:3799
#10 0x7fcb88d47a20 in QApplication::notify (this=0x7ffc603378d0,
receiver=0x1f32720, e=0x7fcb680099a0) at kernel/qapplication.cpp:3556
#11 0x7fcb87bf35c5 in QCoreApplication::notifyInternal2
(receiver=0x1f32720, event=event@entry=0x7fcb680099a0) at
kernel/qcoreapplication.cpp:988
#12 0x7fcb87bf5623 in QCoreApplication::sendEvent (event=0x7fcb680099a0,
receiver=) at kernel/qcoreapplication.h:231
#13 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x183c910) at
kernel/qcoreapplication.cpp:1649
#14 

[skrooge] [Bug 368828] Ubuntu KF5 PPA xenial package still uses oxygen icon theme

[Stephane MANKOWSKI via KDE Bugzilla]

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

--- Comment #5 from Stephane MANKOWSKI  ---
Hi,
I don't understand! As you can see, skrooge-kf5 is not using oxygen package:
If I launch the following command line:
apt-cache depends skrooge-kf5   
The result is:
skrooge-kf5
  Dépend: libc6
  Dépend: libgcc1
  Dépend: libgrantlee-templates5
  Dépend: libkf5archive5
  Dépend: libkf5completion5
  Dépend: libkf5configcore5
  Dépend: libkf5configgui5
  Dépend: libkf5configwidgets5
  Dépend: libkf5coreaddons5
  Dépend: libkf5dbusaddons5
  Dépend: libkf5i18n5
  Dépend: libkf5iconthemes5
  Dépend: libkf5itemviews5
  Dépend: libkf5kdelibs4support5
  Dépend: libkf5kiocore5
  Dépend: libkf5kiofilewidgets5
  Dépend: libkf5newstuff5
  Dépend: libkf5notifications5
  Dépend: libkf5notifyconfig5
  Dépend: libkf5parts5
  Dépend: libkf5service-bin
  Dépend: libkf5service5
  Dépend: libkf5textwidgets5
  Dépend: libkf5wallet-bin
  Dépend: libkf5wallet5
  Dépend: libkf5widgetsaddons5
  Dépend: libkf5xmlgui5
  Dépend: libofx6
  Dépend: libqca-qt5-2
  Dépend: libqt5concurrent5
  Dépend: libqt5core5a
  Dépend: libqt5dbus5
 |Dépend: libqt5gui5
  Dépend: libqt5gui5-gles
  Dépend: libqt5printsupport5
  Dépend: libqt5qml5
 |Dépend: libqt5quick5
  Dépend: libqt5quick5-gles
 |Dépend: libqt5quickwidgets5
  Dépend: libqt5quickwidgets5-gles
  Dépend: libqt5script5
  Dépend: libqt5sql5
  Dépend: libqt5svg5
  Dépend: libqt5webkit5
  Dépend: libqt5widgets5
  Dépend: libqt5xml5
  Dépend: libsqlcipher0
  Dépend: libstdc++6
  Dépend: 
libqt5core5a
  Dépend: sqlite3
sqlite3:i386
  Dépend: sqlcipher
sqlcipher:i386
  Dépend: libqca2-plugin-ossl
  Dépend: libqt5sql5-sqlite
  Dépend: libgrantlee-core0
  Dépend: libqjson0
  Dépend: xsltproc
xsltproc:i386
  Dépend: skrooge-kf5-common
  Dépend: kio
  Dépend: kinit
  Dépend: qtdeclarative5-controls-plugin
  Dépend: frameworkintegration
  Dépend: breeze-icon-theme
  Recommande: weboob

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

[valgrind] [Bug 369441] bad lvec argument crashes process_vm_readv/writev syscall wrappers

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101321
  --> https://bugs.kde.org/attachment.cgi?id=101321=edit
Don't check bad iovec array in process_vm_readv/writev.

The TODO comment already said what to do.

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

[kdenlive] [Bug 369428] Crashing on first launch on relatively fresh Arch install

[Jacob Kauffmann via KDE Bugzilla]

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

Jacob Kauffmann  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jacob Kauffmann  ---
Wow, I'm very sorry to be a bother, but since I saw VLC mentioned a few times
in the traceback, I uninstalled phonon-qt5-vlc and replaced it with
phonon-qt5-gstreamer, and now Kdenlive opens fine. I'm still happy to help
debug if anyone wants to get things working properly with the VLC backend, but
my problem is resolved.

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

[plasmashell] [Bug 353975] Black screen on second display.

[Vangelis via KDE Bugzilla]

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

Vangelis  changed:

   What|Removed |Added

 CC||cyberan...@gmail.com

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

[kmymoney4] [Bug 277041] "Pay to" text box unexpectedly changes when changing field from OFX import

[Thomas Baumgart via KDE Bugzilla]

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

--- Comment #3 from Thomas Baumgart  ---
Maybe Mike (the OP) can drop a note about the current state.

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

[digikam] [Bug 369321] Translation of digikam + showfoto docbooks missing in digikam-5.2.0 tarball

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/scra
   ||tch/mwiesweg/digikam-sc/699
   ||2e99ce8362c3bef5840f1969de5
   ||68b109c0b1
   Version Fixed In||5.3.0

--- Comment #17 from caulier.gil...@gmail.com ---
Git commit 6992e99ce8362c3bef5840f1969de568b109c0b1 by Gilles Caulier.
Committed on 27/09/2016 at 18:32.
Pushed by cgilles into branch 'master'.

extraction of list of handbook files is done automatically, parsing
documentation git repository contents
The documentation translations can be now included in next tarball release
5.3.0
FIXED-IN: 5.3.0
CCMAIL: neoclust@gmail.com

M  +10   -160  project/release/fetch_l10n_doc.rb

http://commits.kde.org/scratch/mwiesweg/digikam-sc/6992e99ce8362c3bef5840f1969de568b109c0b1

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

[kmail2] [Bug 369440] New: Kmail crashed when moved one subfoler to another

[Ilpo Kantonen via KDE Bugzilla]

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

Bug ID: 369440
   Summary: Kmail crashed when moved one subfoler to another
   Product: kmail2
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: i...@iki.fi

Application: kmail (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-38-generic i686
Distribution: Ubuntu 16.04.1 LTS

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

I moved an subfoler to another (one level higher) and Kmail crashed. Platform
Kubuntu 16.04.1 updated online from Kubuntu 14.10.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xaa930ac0 (LWP 3851))]

Thread 19 (Thread 0x9e36bb40 (LWP 3909)):
#0  0xb638cf11 in socketNotifierSourceCheck (source=0xa730a410) at
kernel/qeventdispatcher_glib.cpp:70
#1  0xb39cfaca in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb39d00a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb39d0244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb638db14 in QEventDispatcherGlib::processEvents (this=0xa7345890,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0xb6332953 in QEventLoop::processEvents (this=0x9e36b194, flags=...) at
kernel/qeventloop.cpp:128
#6  0xb6332daa in QEventLoop::exec (this=0x9e36b194, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb6158f1d in QThread::exec (this=0x94168c8) at thread/qthread.cpp:503
#8  0xb6158ff8 in QThread::run (this=0x94168c8) at thread/qthread.cpp:570
#9  0xb615e43b in QThreadPrivate::start (arg=0x94168c8) at
thread/qthread_unix.cpp:331
#10 0xb3b172b5 in start_thread (arg=0x9e36bb40) at pthread_create.c:333
#11 0xb5e6f16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 18 (Thread 0x9eb6cb40 (LWP 3906)):
#0  0xb39ccf62 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb39cf55b in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb39d0014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb39d0244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb638db14 in QEventDispatcherGlib::processEvents (this=0x8ed9f50,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0xb6332953 in QEventLoop::processEvents (this=0x9eb6c194, flags=...) at
kernel/qeventloop.cpp:128
#6  0xb6332daa in QEventLoop::exec (this=0x9eb6c194, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb6158f1d in QThread::exec (this=0x938bbb0) at thread/qthread.cpp:503
#8  0xb6158ff8 in QThread::run (this=0x938bbb0) at thread/qthread.cpp:570
#9  0xb615e43b in QThreadPrivate::start (arg=0x938bbb0) at
thread/qthread_unix.cpp:331
#10 0xb3b172b5 in start_thread (arg=0x9eb6cb40) at pthread_create.c:333
#11 0xb5e6f16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 17 (Thread 0x9f966b40 (LWP 3885)):
#0  0xb3a164b8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb39cfabf in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb39d00a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb39d0244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb638db14 in QEventDispatcherGlib::processEvents (this=0xa9a09cc0,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0xb6332953 in QEventLoop::processEvents (this=0x9f966194, flags=...) at
kernel/qeventloop.cpp:128
#6  0xb6332daa in QEventLoop::exec (this=0x9f966194, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb6158f1d in QThread::exec (this=0x90ef6c0) at thread/qthread.cpp:503
#8  0xb6158ff8 in QThread::run (this=0x90ef6c0) at thread/qthread.cpp:570
#9  0xb615e43b in QThreadPrivate::start (arg=0x90ef6c0) at
thread/qthread_unix.cpp:331
#10 0xb3b172b5 in start_thread (arg=0x9f966b40) at pthread_create.c:333
#11 0xb5e6f16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 16 (Thread 0xa0208b40 (LWP 3876)):
#0  0xb3a164b8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb39cf116 in g_main_context_release () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb39d00bb in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb39d0244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb638db14 in QEventDispatcherGlib::processEvents (this=0xa850b200,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0xb6332953 in QEventLoop::processEvents (this=0xa0208194, flags=...) at
kernel/qeventloop.cpp:128
#6  0xb6332daa in QEventLoop::exec (this=0xa0208194, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb6158f1d in QThread::exec (this=0x92137c8) at thread/qthread.cpp:503
#8  0xb6158ff8 in QThread::run (this=0x92137c8) at 

[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel

[muzuiget via KDE Bugzilla]

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

--- Comment #8 from muzuiget  ---
Oh, I am using dual monitors, this bug annoy me almost a year, finally I found
out what cause this problem, and know which keyword to search then go into this
issue.

The reason is "You can't add second system tray after plamsashell started".

After you click "Add Panel -> Default Panel" to add second panel, plamsashell
will eat all your memory in a few seconds, then your desktop nearly freezing.

Test on Fedora 24, with package "plasma-desktop.x86_64", version 5.7.5-1.fc24.

After so many times to run "sleep 15 && killall -s KILL plasmashell" then
testing. I found out the reason which I said above;

When you click the menuitem, plasmashell will execute the file
/usr/share/plasma/layout-templates/org.kde.plasma.desktop.defaultPanel/contents/layout.js,
after comment out the line

panel.addWidget('org.kde.plasma.systemtray');

The new panel added normally without the system tray;

Then I do more digging, and found out a file
/usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/main.qml 

Item {
id: root

Layout.minimumWidth: internalSystray.Layout.minimumWidth
Layout.minimumHeight: internalSystray.Layout.minimumHeight

Plasmoid.preferredRepresentation: Plasmoid.fullRepresentation
property Item internalSystray

Component.onCompleted: {
root.internalSystray = plasmoid.nativeInterface.internalSystray;

if (root.internalSystray == null) {
return;
}
root.internalSystray.parent = root;
root.internalSystray.anchors.fill = root;
}

Connections {
target: plasmoid.nativeInterface
onInternalSystrayChanged: {
root.internalSystray =
plasmoid.nativeInterface.internalSystray;
root.internalSystray.parent = root;
root.internalSystray.anchors.fill = root;
}
}
}

I am not know qml programming, but I guess "org.kde.plasma.private.systemtray"
is really system tray widget and it's a singltion, and
"org.kde.plasma.systemtray" just a "proxy/container type" widget, the latter
share the same former instance.  When add second system tray, that will be two
"org.kde.plasma.private.systemtray" instance. It look like there are a
recursive call between `onCompleted` and `onInternalSystrayChanged`. After
delete the two methods body, The new panel added normally without the system
tray too.

As I said I don't kown qml, So, I don't konw how to fix it. 

Luckily I konw JavaScript, after reading

https://userbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting#Update_scripts

Here is my workaround, to edit the layout.js, avoid to add system tray in new
panel.

replace the line

panel.addWidget('org.kde.plasma.systemtray');

to 

(function() {
for (var i = 0; i < panelIds.length; i++) {
var tmpPanel = panelById(panelIds[i]);
if (tmpPanel.id === panel.id) {
continue;
}
var trays = tmpPanel.widgets('org.kde.plasma.systemtray');
if (trays.length > 0) {
return;
}
}
panel.addWidget('org.kde.plasma.systemtray');
})();

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

[plasmashell] [Bug 354111] Plasma 5 login with multiple monitors is absurdly slow compared to 4.x

[via KDE Bugzilla]

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

--- Comment #17 from rauchwo...@gmx.net ---
(In reply to Jimmy Berry from comment #16)
> I do not see an appropriate status that I can set this issue, but
> "WAITINGFORINFO" definitely is not the case.

Did you try do disable the splash screen?

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

[neon] [Bug 365301] QtCreator installation fails

[Vangelis via KDE Bugzilla]

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

Vangelis  changed:

   What|Removed |Added

 CC||cyberan...@gmail.com

--- Comment #4 from Vangelis  ---
@Roman, is there a deb file in the link you provided?
I only found QT Creator binary files with a .run extension. They install and
work fine, but do not integrate with the package management in the system (as
expected).

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

[valgrind] [Bug 369439] S390x: Unhandled insns RISBLG/RISBHG and LDE/LDER

[Andreas Arnez via KDE Bugzilla]

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

--- Comment #1 from Andreas Arnez  ---
Created attachment 101320
  --> https://bugs.kde.org/attachment.cgi?id=101320=edit
Support LDE/LDER, and RISBHG/RISBLG

This patch adds support for the missing instructions.  In addition, it also
handles MVCIN and BRCTH and updates the instruction table.

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

[Touchpad-KCM] [Bug 369355] Touchpad configuration applet crashes

[Tony via KDE Bugzilla]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #2 from Tony  ---
I can confirm this happens on wayland, X is ok. In my case system settings dies
silently with no errors.

Worst i saw was on a virtual box vm where it hang the desktop.

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

[valgrind] [Bug 369439] New: S390x: Unhandled insns RISBLG/RISBHG and LDE/LDER

[Andreas Arnez via KDE Bugzilla]

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

Bug ID: 369439
   Summary: S390x: Unhandled insns RISBLG/RISBHG and LDE/LDER
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: ar...@linux.vnet.ibm.com

An upstream GCC may emit the hex floating-point instructions LDE and LDER (for
loading usual binary floating-point values), and LLVM may emit the high-word
facility instructions RISBLG and RISBHG.  All of these are currently not
handled by Valgrind.

Reproducible: Always

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

[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from David Edmundson  ---
thanks for reporting back.

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

[plasmashell] [Bug 366146] Plasma crashes when trying to add second panel

[Tony via KDE Bugzilla]

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

--- Comment #6 from Tony  ---
This one is fixed on Neon, for X and Wayland session. I can fill all corners of
the dekstop with "empty" and "default" panels with no crashes.

Plasma 5.8.90
Frameworks 5.27
Qt 5.7

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

[kmymoney4] [Bug 369438] New: Allow selection of OFX tag to use for Payee, even if account not mapped

[Jack via KDE Bugzilla]

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

Bug ID: 369438
   Summary: Allow selection of OFX tag to use for Payee, even if
account not mapped
   Product: kmymoney4
   Version: git (master)
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: ostrof...@users.sourceforge.net

If an account is mapped to an online account with libofx, under the
Edit/Account, Online Settings tab, Import Details subtab, there is a dropdown
"Payee's name is based on contents of the OFX tag" with choices of PAYEEID,
NAME, and MEMO.  This is not present under aqbanking or if the account is not
mapped, so it cannot be specified for OFX file imports.  

As it seems an increasing number of institutions making it increasingly
difficult for KMM to use OFX Direct Connect, this it becoming an increasingly
common issue.

Reproducible: Always

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

[kmymoney4] [Bug 277041] "Pay to" text box unexpectedly changes when changing field from OFX import

[Jack via KDE Bugzilla]

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

--- Comment #2 from Jack  ---
With no feedback or evidence it still happens, should this be closed?

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

[kdeplasma-addons] [Bug 369437] New: Pinned apps use monochrome icons like system tray

[郭云鹤]

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

Bug ID: 369437
   Summary: Pinned apps use monochrome icons like system tray
   Product: kdeplasma-addons
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Dashboard
  Assignee: h...@kde.org
  Reporter: guoyunhebr...@gmail.com
CC: plasma-b...@kde.org

Screenshot: http://imgur.com/on80sbp

On left side, bookmarked/pinned apps, including Amarok, KTorrent, Konversation,
use their system tray icons rather than colored icons.

Reproducible: Always

Steps to Reproduce:
1. Open application dashboard
2. Bookmark/pin those applications: Amarok, Konversation, KTorrent
3. See the icon shown in left bookmark panel

Actual Results:  
Amarok, Konversation, KTorrent use monochrome icons (for system tray).

Expected Results:  
They should use colored icons.

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

[kdenlive] [Bug 369180] git master - changing effects parameters doesn't affect preview render.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Jesse  ---
Hmm... I did some more testing off of a new project (instead of the one I was
using, originally), and it seems like everything is working fine. It could be
my project file.

In any case, the feature seems to be working, so I'm closing this bug. Thanks
JB!

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

[dolphin] [Bug 357651] No error message if file pasting failed

[Adam via KDE Bugzilla]

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

Adam  changed:

   What|Removed |Added

 CC||k...@xibo.at

--- Comment #1 from Adam  ---
I just encountered the same issue in Dolphin 16.08.0 (KDE Frameworks 5.26.0,
openSUSE Leap 42.2 beta), when dragging files in splitview from the hard disk
to a pen drive.

I was puzzled because just the second before I moved a smaller file and it
worked. If that were not the case, my work would be stalled. Would be cool if
this is fixed for 5.8 LTS, because i really like the new version :D  (coming
from mint/kde 4.14)

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

[systemsettings] [Bug 369436] New: All controls for sound are up and running no sound comes out

[John via KDE Bugzilla]

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

Bug ID: 369436
   Summary: All  controls  for  sound  are up  and running  no
sound comes out
   Product: systemsettings
   Version: 5.6.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: robledo...@yahoo.com

No  sound

Reproducible: Always


Actual Results:  
no  sound  showing it is on.

Expected Results:  
nothing

Just  to today.  Thank  for  helping.

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

[kwin] [Bug 369435] New: Splash screen does not disappear on primary monitor

[Rolf Eike Beer via KDE Bugzilla]

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

Bug ID: 369435
   Summary: Splash screen does not disappear on primary monitor
   Product: kwin
   Version: 5.7.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@opensource.sf-tec.de

I have a setup with 2 monitors. If I login the splash screen shows up on both
of them. After a few seconds the one on the primary monitor just stalls, while
the secondary monitor continues and finally disappears, showing the started
programs. I have to call "kwin_x11 --replace" to get the first monitor in a
working state.

Reproducible: Always

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