[frameworks-kxmlgui] [Bug 379795] Konsole crashed on double right click

[Marco Martin]

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

Marco Martin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||notm...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Marco Martin  ---
fixed by 4690808e65f1abda5e779620672da14c830aaa89 in kxmlgui

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

[tellico] [Bug 379607] tellico crashes with segfault on start

[Robby Stephenson]

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

--- Comment #7 from Robby Stephenson  ---
Hmmm. There's still no pointer into a crash inside Tellico. This is a bit
weird. If we back up a bit, can you post the log file or output that you get
when you run cmake? Thanks

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

[krita] [Bug 379731] Touch screen

[Allie White]

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

--- Comment #2 from Allie White  ---
Okay thank you for your help

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

[plasmashell] [Bug 379936] plasma crash

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|general |Task Manager
   Assignee|k...@davidedmundson.co.uk|h...@kde.org

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

[plasmashell] [Bug 378508] when remove panel applet plasma crashed

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||dolo...@outlook.com

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

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

[plasmashell] [Bug 379924] Plasma crash when changing theme

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

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


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

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

[frameworks-kxmlgui] [Bug 379795] Konsole crashed on double right click

[rооt]

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

--- Comment #5 from rооt  ---
(In reply to Christoph Feck from comment #4)
> Regression in kxmlgui.
> 
> Could you check if https://phabricator.kde.org/D5900 fixes the crash?

Kubuntu 17.10 + KCI just updated, now no problem.

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

[plasmashell] [Bug 379936] New: plasma crash

[bugzilla_noreply]

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

Bug ID: 379936
   Summary: plasma crash
   Product: plasmashell
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: aaza...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.10.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
i was closing vlc (6-7 opened) and kde crashed when closing..

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f994c294800 (LWP 788))]

Thread 16 (Thread 0x7f98615d0700 (LWP 8460)):
#0  0x7f9944f05756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f994604b58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f988dd121d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f988dd169d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f988dd14249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#16 0x7f994604a6d8 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f9944eff2e7 in start_thread () at /usr/lib/libpthread.so.0
#18 0x7f994595d54f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f9861dd1700 (LWP 8459)):
#0  0x7f9944f05756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f994604b58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f988dd121d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f988dd169d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f988dd14249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f994604a6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f9944eff2e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f994595d54f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f98625d2700 (LWP 8458)):
#0  0x7f9944f05756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f994604b58b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f988dd121d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f988dd169d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f988dd16a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f988dd11263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f988dd16a32 in  () at 

[frameworks-kxmlgui] [Bug 379795] Konsole crashed on double right click

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|konsole-de...@kde.org   |kdelibs-b...@kde.org
Product|konsole |frameworks-kxmlgui
  Component|general |general

--- Comment #4 from Christoph Feck  ---
Regression in kxmlgui.

Could you check if https://phabricator.kde.org/D5900 fixes the crash?

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

[krita] [Bug 379931] Double ring and Lagging

[Boudewijn Rempt]

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

--- Comment #4 from Boudewijn Rempt  ---
You didn't attach an image to the bug report.

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

[Breeze] [Bug 368605] RTL Lang - the range line reversed

[bugzilla_noreply]

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

--- Comment #3 from ttv...@gmail.com ---
When I change the application style it's work fine

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

[dolphin] [Bug 379908] Duplicate kgpg entry in context menu.

[Paul]

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

Paul  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from Paul  ---
There was a duplicate *.desktop file in "/usr/share/kservices5/"

Removing that file solved the "problem".

Apologies for the erroneous bug report and thanks for your help.

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

[Breeze] [Bug 368605] RTL Lang - the range line reversed

[bugzilla_noreply]

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

ttv...@gmail.com changed:

   What|Removed |Added

   Platform|Other   |unspecified
   Assignee|now...@gmail.com|hugo.pereira.da.costa@gmail
   ||.com
Version|5.7.3   |5.9.5
Product|plasma-pa   |Breeze
  Component|kcm |QStyle
   Priority|NOR |VLO

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

[ksmserver] [Bug 379935] New: ksmserver-logout-greeter (ksmserver-logout-greeter)

[bugzilla_noreply]

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

Bug ID: 379935
   Summary: ksmserver-logout-greeter (ksmserver-logout-greeter)
   Product: ksmserver
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: ernestopereslo...@yahoo.es
  Target Milestone: ---

El error ocurre al intentar salir de Antergos KDE (Arch Linux)


Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal:
Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f04955b8840 (LWP 21679))]

Thread 4 (Thread 0x7f047cd6a700 (LWP 21682)):
#0  0x7f0489ac31c9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7f0489a7c870 in g_main_context_acquire () from
/usr/lib/libglib-2.0.so.0
#2  0x7f0489a7d865 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f0489a7dacc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f049187009b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7f04918198ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7f049163ba73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7f0493850025 in ?? () from /usr/lib/libQt5Qml.so.5
#8  0x7f04916406d8 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7f048b9ea2e7 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f0490f4f54f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f047daba700 (LWP 21681)):
#0  0x7f0490f4567d in poll () from /usr/lib/libc.so.6
#1  0x7f0489a7d9b6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f0489a7dacc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f049187009b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f04918198ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f049163ba73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f04923c9125 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f04916406d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f048b9ea2e7 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f0490f4f54f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f047f62a700 (LWP 21680)):
#0  0x7f0490f4567d in poll () from /usr/lib/libc.so.6
#1  0x7f048c0578e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f048c059679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f04819b5239 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f04916406d8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f048b9ea2e7 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f0490f4f54f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f04955b8840 (LWP 21679)):
[KCrash Handler]
#6  0x7f0490e96a10 in raise () from /usr/lib/libc.so.6
#7  0x7f0490e9813a in abort () from /usr/lib/libc.so.6
#8  0x7f0491626e21 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#9  0x7f0493f1f083 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/libQt5Quick.so.5
#10 0x7f0493f202a6 in ?? () from /usr/lib/libQt5Quick.so.5
#11 0x7f0493f20b25 in ?? () from /usr/lib/libQt5Quick.so.5
#12 0x7f0491d78d05 in QWindow::event(QEvent*) () from
/usr/lib/libQt5Gui.so.5
#13 0x7f0493f8d4a5 in QQuickWindow::event(QEvent*) () from
/usr/lib/libQt5Quick.so.5
#14 0x00408c21 in ?? ()
#15 0x7f049299e34c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#16 0x7f04929a5b61 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#17 0x7f049181b470 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#18 0x7f0491d6dd2d in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /usr/lib/libQt5Gui.so.5
#19 0x7f0491d6e93d in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/libQt5Gui.so.5
#20 0x7f0491d4a44b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/libQt5Gui.so.5
#21 0x7f0481a159e0 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#22 0x7f0489a7d7b7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x7f0489a7da20 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x7f0489a7dacc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x7f049187007f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#26 0x7f04918198ca in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#27 0x7f0491821e14 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#28 0x00405af2 in ?? ()
#29 0x7f0490e83511 

[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX

[Ivo Raisr]

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

--- Comment #18 from Ivo Raisr  ---
Follow up fix in SVN r16393.

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

[gwenview] [Bug 202414] allow to hide status bar and toolbar

[Valerio Pilo]

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

--- Comment #23 from Valerio Pilo  ---
I agree with you Andy, but it's a change that has to be planned and done
desktop-wide. Propose it!

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

[k3b] [Bug 379849] Rip fails to start when using clone mode and target exsists

[Chris]

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

Chris  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #6 from Chris  ---
Yesterday i had upgraded to 17.04.1 release of k3b and this issue seams to be
resolved as I don't get an overwrite prompt at all it just picks a new file
name 
if the file exists

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

[krita] [Bug 379931] Double ring and Lagging

[Meiio]

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

--- Comment #3 from Meiio  ---
Did you see the image?

On May 17, 2017 2:16 AM, "Boudewijn Rempt"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=379931
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
> 
> 
>  CC||b...@valdyas.org
>  Status|UNCONFIRMED |RESOLVED
>  Resolution|--- |INVALID
>
> --- Comment #2 from Boudewijn Rempt  ---
> That's the stabilizer. See https://docs.krita.org/
> Freehand_Brush_Tool#Smoothing
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[bugzilla_noreply]

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

--- Comment #34 from alvinhoc...@gmail.com ---
> I have a feeling that there is some bug in how we handle the events flow. We
> should first try to fix it, instead of giving the user an option to control
> such non-obvious property.
> 
> As a direction of further work, it might be a good idea to have a log of how
> many events are usually handled in 
> 
> KisStabilizerDelayedPaintHelper::stabilizerDelayedPaint() 
> 
> when isEndStroke is false.
> 
> If the number of events is always the same, then my theory is probably not
> correct. If it interleaves with zero like "10,0,11,0,9,0...", then my theory
> is correct.

I am taking a guess that the timer resolution may also affect the behaviour.
IIRC it isn't using a high-resolution timer so maybe there is some fuzziness
which depends on system load?

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

[plasma-nm] [Bug 361414] [RFE] Show more network details. e.g. DNS server is basic

[Martin Vysny]

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

--- Comment #10 from Martin Vysny  ---
I do not try to undermine the survey (haven't seen it actually). But the
"Details" pane currently shows the MAC address, which is arguably more
technical and less useful than the DNS server IP.

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[bugzilla_noreply]

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

alvinhoc...@gmail.com changed:

   What|Removed |Added

   Assignee|alvinhoc...@gmail.com   |krita-bugs-n...@kde.org

--- Comment #33 from alvinhoc...@gmail.com ---
Sorry but I don't have enough time to dig into this for now. If someone wants
to take this before I have the time again, please feel free to do that.

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

[Breeze] [Bug 379861] The Kontact icon is a wifi icon

[Jens Reuterberg]

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

--- Comment #2 from Jens Reuterberg  ---
Its based on the RSS and old Akregator icon which, when in monochrome becomes 
very "wifi icon" like (mostly because Wifi icons tend to be "anything with a 
signal symbol in it"). 

One idea would be to change the Akregator icon from scratch and remove the 
focus on the RSS symbol (the thing that looks like a wifi thing)

On Tuesday, 16 May 2017 19.15.08 CEST Daniel Vrátil wrote:
> https://bugs.kde.org/show_bug.cgi?id=379861
> 
> Daniel Vrátil  changed:
> 
>What|Removed |Added
> 
> Component|general |Icons
> Product|kontact |Breeze
> Version|5.5.1   |unspecified
>Assignee|kdepim-b...@kde.org |visual-des...@kde.org
>  CC||dvra...@kde.org,
> 
>||kain...@gmail.com
> 
> --- Comment #1 from Daniel Vrátil  ---
> I think you are referring to Akregator (RSS feed) icon, which looks like
> wifi icon tilted by 45 degrees. This is an icon provided by Breeze, not by
> Akregator, so reassigning to Breeze.

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

[ksysguard] [Bug 378629] No graphics in "CPU History" and "Network History"

[richardlm]

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

richardlm  changed:

   What|Removed |Added

 CC||cf...@kde.org,
   ||richard.l...@gmail.com

--- Comment #1 from richardlm  ---
Please stay with bug 218796

Also to help it solved you could do as in bug 218796 comment #17 requested

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[Dmitry Kazakov]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #32 from Dmitry Kazakov  ---
(In reply to RN from comment #31)

> Forcing the visual updates (what the delayed painter is doing) when the
> window manager can't keep up with visual updates in the first place is not
> going to give the expected result, it would stutter anyway.

Don't mix window updates rate, tablet events rate and painting rate. They are
three different things.

Tablet events rate is the rate we get the tablet events from the driver. In
normal situation the events come at rate 1 event per 7-14ms. Long window
updates may delay the events and they will start coming in bunches 4-5 events
per every 40-50ms.

Then we have "painting rate", that is a rate we generate dabs with the
stabilizer algorithm and pass them to the painting code.

After passing the points to the painting code, the painting code paints and
generates window updates, but the updates are not passed to the GPU directly.
They first compressed to not overload the pipeline with too many small updates,
and only after that are passed to the GPU (on GPUs supporting glFenceSync).
This final flow of updates in "painting rate" and it cannot be higher than the
GPU can handle.

Basically, the flow looks like that:

1) Tablet events come in bunches every 7-50 ms.
2) KisStabilizedEventsSampler delays the flow by 50ms. That allows it to group
the evens into 50ms groups and to adjust the time as if the events inside the
group were flowing uniformly (e.g. for group of 5 events, the sampler will
modify them as if they they were issues every 10ms).
3) These groups of events come to KisStabilizerDelayedPaintHelper, that
regroups the groups from the sampler into groups of 20ms (20ms == 40fps, which
should be enough for everyone(c)) and passes them to the painting code every 20
ms.

Now I see that a thing that can happen is that delayed painter is not
synchronized with the sampler. That is, it might happen that the delay helper
can have "empty" cycles, where the samples from the sampler are not ready yet.
To avoid the problem we should sync the timers of sampler and delay helper to
be a multiple of each other.


A quite test for this hypothesis might be to set:

stabilizerSampleSize=60
stabilizerDelayedPaintInterval=20

That is still not very "sync", but if it makes the things better then we should
move into this direction further. Probably, by merging the two timers into one.






> In Dmitry's case the timer interval would've grown
> until reaching 50ms or more.
> The timer is stopped when the stroke ends, and when a new stroke begins the
> timer interval starts at some default value (16ms for example, or 1ms like
> 2.9.11 although that might be too fast).

In feedback control systems theory it is called "proportional regulator". And
it it really a bad thing to use, unless there is no other choice. What if the I
accidentally have a delay of 200ms? Will all my further strokes be smoothed by
200ms? And if not, then we should do some PI-regulator, which is stable enough
and still does the job. It may have quite a lot of unexpected consequences.


> Whatever is decided, I think something should be added to the interface
> (maybe in Configure Krita -> Tablet Preferences), like spinboxes to set
> timer values so that users don't have to go and modify 'kritarc' themselves,
> and be able to quickly test different values without having to restart the
> program. Someone above mentioned having difficulty doing that, for example.
> Regards.

I have a feeling that there is some bug in how we handle the events flow. We
should first try to fix it, instead of giving the user an option to control
such non-obvious property.

As a direction of further work, it might be a good idea to have a log of how
many events are usually handled in 

KisStabilizerDelayedPaintHelper::stabilizerDelayedPaint() 

when isEndStroke is false.

If the number of events is always the same, then my theory is probably not
correct. If it interleaves with zero like "10,0,11,0,9,0...", then my theory is
correct.

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

[digikam] [Bug 374710] No dialogue opening on edit bookmarks in geolocation editor

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.6.0
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/95b5cec4970939d5068ca1
   ||3ce3e3198fc929cc5b
 Status|REOPENED|RESOLVED

--- Comment #10 from caulier.gil...@gmail.com ---
Git commit 95b5cec4970939d5068ca13ce3e3198fc929cc5b by Gilles Caulier.
Committed on 17/05/2017 at 10:04.
Pushed by cgilles into branch 'master'.

remove menu and toolbar bookmarks management from GPS bookmarks manager.
Now a first version suitable is available. More improvements will come later.
Import form older GPS bookmarks generated bu KF5::bookmarks run fine as well.
Related: bug 376687, bug 376074, bug 376391, bug 376407
FIXED-IN: 5.6.0

M  +11   -5utilities/geolocation/editor/bookmark/bookmarksdlg.cpp
M  +2-2utilities/geolocation/editor/bookmark/bookmarksmenu.cpp
M  +6-123  utilities/geolocation/editor/bookmark/bookmarksmngr.cpp
M  +0-2utilities/geolocation/editor/bookmark/bookmarksmngr.h
M  +1-1utilities/geolocation/editor/bookmark/gpsbookmarkowner.cpp
M  +23   -19   utilities/geolocation/editor/items/gpsimagelistcontextmenu.cpp

https://commits.kde.org/digikam/95b5cec4970939d5068ca13ce3e3198fc929cc5b

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

[digikam] [Bug 376074] Display-bookmarked-positions-on-the-map button doesn't work.

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.6.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/95b5cec4970939d5068ca1
   ||3ce3e3198fc929cc5b

--- Comment #11 from caulier.gil...@gmail.com ---
Git commit 95b5cec4970939d5068ca13ce3e3198fc929cc5b by Gilles Caulier.
Committed on 17/05/2017 at 10:04.
Pushed by cgilles into branch 'master'.

remove menu and toolbar bookmarks management from GPS bookmarks manager.
Now a first version suitable is available. More improvements will come later.
Import form older GPS bookmarks generated bu KF5::bookmarks run fine as well.
Related: bug 376687, bug 376391, bug 374710, bug 376407
FIXED-IN: 5.6.0

M  +11   -5utilities/geolocation/editor/bookmark/bookmarksdlg.cpp
M  +2-2utilities/geolocation/editor/bookmark/bookmarksmenu.cpp
M  +6-123  utilities/geolocation/editor/bookmark/bookmarksmngr.cpp
M  +0-2utilities/geolocation/editor/bookmark/bookmarksmngr.h
M  +1-1utilities/geolocation/editor/bookmark/gpsbookmarkowner.cpp
M  +23   -19   utilities/geolocation/editor/items/gpsimagelistcontextmenu.cpp

https://commits.kde.org/digikam/95b5cec4970939d5068ca13ce3e3198fc929cc5b

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

[digikam] [Bug 376687] GPS tagging usability of bookmarks

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.6.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/95b5cec4970939d5068ca1
   ||3ce3e3198fc929cc5b

--- Comment #4 from caulier.gil...@gmail.com ---
Git commit 95b5cec4970939d5068ca13ce3e3198fc929cc5b by Gilles Caulier.
Committed on 17/05/2017 at 10:04.
Pushed by cgilles into branch 'master'.

remove menu and toolbar bookmarks management from GPS bookmarks manager.
Now a first version suitable is available. More improvements will come later.
Import form older GPS bookmarks generated bu KF5::bookmarks run fine as well.
Related: bug 376074, bug 376391, bug 374710, bug 376407
FIXED-IN: 5.6.0

M  +11   -5utilities/geolocation/editor/bookmark/bookmarksdlg.cpp
M  +2-2utilities/geolocation/editor/bookmark/bookmarksmenu.cpp
M  +6-123  utilities/geolocation/editor/bookmark/bookmarksmngr.cpp
M  +0-2utilities/geolocation/editor/bookmark/bookmarksmngr.h
M  +1-1utilities/geolocation/editor/bookmark/gpsbookmarkowner.cpp
M  +23   -19   utilities/geolocation/editor/items/gpsimagelistcontextmenu.cpp

https://commits.kde.org/digikam/95b5cec4970939d5068ca13ce3e3198fc929cc5b

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

[digikam] [Bug 376407] Edit Bookmarks... Doesn't Do Anything

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.6.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/95b5cec4970939d5068ca1
   ||3ce3e3198fc929cc5b
 Status|REOPENED|RESOLVED

--- Comment #3 from caulier.gil...@gmail.com ---
Git commit 95b5cec4970939d5068ca13ce3e3198fc929cc5b by Gilles Caulier.
Committed on 17/05/2017 at 10:04.
Pushed by cgilles into branch 'master'.

remove menu and toolbar bookmarks management from GPS bookmarks manager.
Now a first version suitable is available. More improvements will come later.
Import form older GPS bookmarks generated bu KF5::bookmarks run fine as well.
Related: bug 376687, bug 376074, bug 376391, bug 374710
FIXED-IN: 5.6.0

M  +11   -5utilities/geolocation/editor/bookmark/bookmarksdlg.cpp
M  +2-2utilities/geolocation/editor/bookmark/bookmarksmenu.cpp
M  +6-123  utilities/geolocation/editor/bookmark/bookmarksmngr.cpp
M  +0-2utilities/geolocation/editor/bookmark/bookmarksmngr.h
M  +1-1utilities/geolocation/editor/bookmark/gpsbookmarkowner.cpp
M  +23   -19   utilities/geolocation/editor/items/gpsimagelistcontextmenu.cpp

https://commits.kde.org/digikam/95b5cec4970939d5068ca13ce3e3198fc929cc5b

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

[digikam] [Bug 376391] Add geolocation favorites to menu and shortcuts

[bugzilla_noreply]

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

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

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dig
   ||ikam/95b5cec4970939d5068ca1
   ||3ce3e3198fc929cc5b
   Version Fixed In||5.6.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from caulier.gil...@gmail.com ---
Git commit 95b5cec4970939d5068ca13ce3e3198fc929cc5b by Gilles Caulier.
Committed on 17/05/2017 at 10:04.
Pushed by cgilles into branch 'master'.

remove menu and toolbar bookmarks management from GPS bookmarks manager.
Now a first version suitable is available. More improvements will come later.
Import form older GPS bookmarks generated bu KF5::bookmarks run fine as well.
Related: bug 376687, bug 376074, bug 374710, bug 376407
FIXED-IN: 5.6.0

M  +11   -5utilities/geolocation/editor/bookmark/bookmarksdlg.cpp
M  +2-2utilities/geolocation/editor/bookmark/bookmarksmenu.cpp
M  +6-123  utilities/geolocation/editor/bookmark/bookmarksmngr.cpp
M  +0-2utilities/geolocation/editor/bookmark/bookmarksmngr.h
M  +1-1utilities/geolocation/editor/bookmark/gpsbookmarkowner.cpp
M  +23   -19   utilities/geolocation/editor/items/gpsimagelistcontextmenu.cpp

https://commits.kde.org/digikam/95b5cec4970939d5068ca13ce3e3198fc929cc5b

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

[kmail2] [Bug 379934] New: Citation indicator appears episodically and is discontinuous

[bugzilla_noreply]

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

Bug ID: 379934
   Summary: Citation indicator appears episodically and is
discontinuous
   Product: kmail2
   Version: 5.5.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: misc
  Assignee: kdepim-b...@kde.org
  Reporter: pie...@bouchet.eu.com
  Target Milestone: ---

I have 2 small problems with "answer" in kmail, the citation indicator does not
appear with each answer but random, and if I put alt gr 6, the vertical line is
discontinuous.

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

[KSystemLog] [Bug 379933] Switching to Apache log viewing causes error

[RNG]

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

--- Comment #1 from RNG  ---
FYI: I am running KSystemlog version 17.04.1

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

[KSystemLog] [Bug 379933] New: Switching to Apache log viewing causes error

[RNG]

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

Bug ID: 379933
   Summary: Switching to Apache log viewing causes error
   Product: KSystemLog
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: nicolas.ternis...@gmail.com
  Reporter: rga...@gmail.com
  Target Milestone: ---

When switching to view apache logs (Apache Log breaks, Apache Access Log
works), I get the following error: 

org.kde.kcoreaddons: doesn't know "/var/log/apache2/access.log"
org.kde.kcoreaddons: doesn't know "/var/log/apache2/error.log"
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "P Warning:  PHP Startup: Unable to load
dynamic library '/usr/lib/php/20151012/ds.so' - /usr/lib/php/20151012/ds.so:
undefined symbol: php_json_serializable_ce in Unknown on line 0" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "ssl:warn" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "ssl:warn" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "ssl:error" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "ssl:error" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "mpm_prefork:notice" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "core:notice" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "core:warn" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "core:warn" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "core:warn" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "core:warn" )
ksystemlog:  New Log Level detected: Please send this log file to the
KSystemLog developer to add it ( "core:warn" )

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

[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)

[Hao Zhang]

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

Hao Zhang  changed:

   What|Removed |Added

 CC||theivoryto...@gmail.com

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

[kio-extras] [Bug 379902] Samba shares no longer work

[bugzilla_noreply]

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

eva...@gmail.com changed:

   What|Removed |Added

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

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

[kio-extras] [Bug 379902] Samba shares no longer work

[bugzilla_noreply]

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

--- Comment #2 from eva...@gmail.com ---
Thanks for your reply - I had left the office before I read it. I had to reboot
my laptop into Windows at home to use a specific piece of software so obviously
I have a fresh boot of Mint this morning, and the bookmarks are working again.
I did install a few updates yesterday. Should have tried restarting, but I just
followed the instructions :)

Sorry for wasting time - now resolved - possibly an issue with updated to Mint
KDE installed between 14 May and 16 May?

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

[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled

[beojan]

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

--- Comment #8 from beojan  ---
*** Bug 378788 has been marked as a duplicate of this bug. ***

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

[QtCurve] [Bug 378788] Opening QtCurve settings crashes System Settings if global menu is enabled

[beojan]

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

beojan  changed:

   What|Removed |Added

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

--- Comment #1 from beojan  ---


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

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

[lokalize] [Bug 181145] Lokalize cannot create the mo files

[Daniele Scasciafratte]

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

--- Comment #23 from Daniele Scasciafratte  ---
That the same script shared by me on https://paste.kde.org/peummsmtk years ago
is not available anymore. And I forgot it to done it a patched version...

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

[krita] [Bug 379931] Double ring and Lagging

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #2 from Boudewijn Rempt  ---
That's the stabilizer. See https://docs.krita.org/Freehand_Brush_Tool#Smoothing

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

[krita] [Bug 379932] Double ring and Lagging

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---


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

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

[krita] [Bug 379931] Double ring and Lagging

[Boudewijn Rempt]

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

--- Comment #1 from Boudewijn Rempt  ---
*** Bug 379932 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 379930] kcm_keyboard kills ibus daemon, entirely breaking the keyboard

[Ralf Jung]

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

--- Comment #1 from Ralf Jung  ---
I verified that changing XkbHelper::preInitialize to not do anything fixes the
ibus-daemon trouble, at least as far as automatically starting it on launch is
concerned.

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

[valgrind] [Bug 379895] clock_gettime does not execute POST syscall wrapper

[Ivo Raisr]

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

--- Comment #7 from Ivo Raisr  ---
Good idea. Would be better to have patches upstream than sitting in your
computer.
If you are missing something for Solaris, let me know or create bugs. Syscall
wrappers tend to be the easy part...

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

[krita] [Bug 379932] New: Double ring and Lagging

[Meiio]

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

Bug ID: 379932
   Summary: Double ring and Lagging
   Product: krita
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: meiiota...@gmail.com
  Target Milestone: ---

Brush has formed a ring or two around the brush, lags and/or doesn't mark when
sketching. Turned on and off the instant preview mode and it does not make a
difference.

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

[valgrind] [Bug 379895] clock_gettime does not execute POST syscall wrapper

[Stefano Bonicatti]

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

--- Comment #6 from Stefano Bonicatti  ---
Well, the ones that i needed, ended up being implemented by you guys soon
later. Currently i have sync() which is implemented here, but missing in the
vanilla source code (it just has a PRE with a PRINT).
Other syscalls like ulimit, statfs and similar are still not implemented..
mainly because i didn't have the need for them for now.

I can try to implement them and file some patches at home (i use Solaris stuff
only at work).

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

[krita] [Bug 379931] New: Double ring and Lagging

[Meiio]

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

Bug ID: 379931
   Summary: Double ring and Lagging
   Product: krita
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: meiiota...@gmail.com
  Target Milestone: ---

Brush has formed a ring or two around the brush, lags and/or doesn't mark when
sketching. Turned on and off the instant preview mode and it does not make a
difference.

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

[plasmashell] [Bug 372604] Black rectangle in top right corner when switching virtual desktops

[Dmitry Ivanov]

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

Dmitry Ivanov  changed:

   What|Removed |Added

 CC||dm.vl.iva...@gmail.com

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

[dolphin] [Bug 379135] Dolphin crash when closing tab

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||2020cmitch...@gmail.com

--- Comment #3 from Elvis Angelaccio  ---
*** Bug 379913 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 379913] Dolphin Crashes When Searching With Multiple Tabs

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||elvis.angelac...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #1 from Elvis Angelaccio  ---


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

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

[dolphin] [Bug 379927] Disabling root access in dolphin is security theater

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||elvis.angelac...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #1 from Elvis Angelaccio  ---
(In reply to Jonwsb from comment #0)
> Disabling root access in dolphin is security theater and does nothing to
> actually make a system more secure. 

It fixes a root escalation attack, how is that not making the system more
secure.

> Also there is still a right click option
> to open folders as root which does not work anymore until this is reverted.

That's something that your distribution added, there is nothing we can do for
that.

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

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||jon...@gmail.com

--- Comment #17 from Elvis Angelaccio  ---
*** Bug 379927 has been marked as a duplicate of this bug. ***

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

[valgrind] [Bug 379895] clock_gettime does not execute POST syscall wrapper

[Ivo Raisr]

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

--- Comment #5 from Ivo Raisr  ---
A funny bug, indeed!

As regards the syscalls you implemented - is that something to be integrated,
yet?

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

[valgrind] [Bug 379895] clock_gettime does not execute POST syscall wrapper

[Stefano Bonicatti]

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

--- Comment #4 from Stefano Bonicatti  ---
Ah! I've implemented some syscall in the past, i've checked that PRE/POST were
correct but forgot to check the actual hooking!
Thank you for the quick fix, works now :).

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

[kde] [Bug 339270] KDE doesn't automatically launch the input method framework(e.g. ibus-daemon)

[Ralf Jung]

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

Ralf Jung  changed:

   What|Removed |Added

 CC||p...@ralfj.de

--- Comment #3 from Ralf Jung  ---
Not sure how this is supposed to work on Fedora; in Debian, ibus installs a
script in /etc/X11/Xsession.d/ which injects "im-launch" into the session
launch process.  I did not yet find out how or where im-launch starts
ibus-daemon, but well.

However, ibus still doesn't work in KDE -- not because it is not started, but
because it is killed immediately.  .xsession-errors:

  org.kde.kcm_keyboard: ibus successfully stopped

I reported this as bug 379930.

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

[systemsettings] [Bug 379930] New: kcm_keyboard kills ibus daemon, entirely breaking the keyboard

[Ralf Jung]

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

Bug ID: 379930
   Summary: kcm_keyboard kills ibus daemon, entirely breaking the
keyboard
   Product: systemsettings
   Version: 5.8.6
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: kcm_keyboard
  Assignee: unassigned-b...@kde.org
  Reporter: p...@ralfj.de
  Target Milestone: ---

I was having some trouble setting up ibus, which I first attributed to bugs in
ibus itself:  ibus would not start automatically
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862721) and would sometimes
quit on suspend-resume
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862717).  However, since
then, I have noticed that the following line appears in .xsession-errors every
time ibus breaks:

  org.kde.kcm_keyboard: ibus successfully stopped

The result of this is that keyboard input does not work -- effectively making
the machine unusable.

I assume there is/was a good reason for kcm_keyboard to kill the ibus daemon,
but right now, the net effect of this behavior is rather catastrophic.  As far
as I can tell, the only possible "fix" for me is to uninstall ibus :/

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

[kwin] [Bug 355920] plasma wayland session doesn't clear tty it uses.

[Gauthier POGAM--LE MONTAGNER]

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

Gauthier POGAM--LE MONTAGNER  changed:

   What|Removed |Added

 CC||kendos.ken...@gmail.com

--- Comment #3 from Gauthier POGAM--LE MONTAGNER  ---
I can confirm it's still the case with plasma 5.10 beta. The TTY2 remain
unusable after logging out of a plasma wayland session.

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

[kwayland-integration] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Gauthier POGAM--LE MONTAGNER]

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

Gauthier POGAM--LE MONTAGNER  changed:

   What|Removed |Added

 CC||kendos.ken...@gmail.com

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

[systemsettings] [Bug 361943] systemsettings - Workspace Theme - Desktop Theme - Get New Themes > Loading ... failed

[Cristiano Guadagnino]

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

Cristiano Guadagnino  changed:

   What|Removed |Added

 CC||crigu...@gmail.com

--- Comment #2 from Cristiano Guadagnino  ---
Same here on openSUSE Tumbleweed, on my work laptop.
Note that I reach the internet through an http proxy, correctly configured in
System Settings.

I can reach that xml file using a browser or wget.
Moreover, I can correctly use Get Hot New Stuff when I'm at home (no proxy).

I have to add that I have this error whenever the Get Hot New Stuff
functionality is involved, not only in this specific case.

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

[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced

[Gauthier POGAM--LE MONTAGNER]

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

Gauthier POGAM--LE MONTAGNER  changed:

   What|Removed |Added

 CC||kendos.ken...@gmail.com

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

[krdc] [Bug 379929] New: Current KRDC Size does not work when there are more than one tab (connections)

[Samuel A .]

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

Bug ID: 379929
   Summary: Current KRDC Size does not work when there are more
than one tab (connections)
   Product: krdc
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: RDP
  Assignee: uwol...@kde.org
  Reporter: 24m...@gmail.com
  Target Milestone: ---

Steps to reproduce:
1) Connect to machine A (RDP) - Current KRDC size
2) Connect to machine B (RDP) - Current KRDC size
!! The size is bigger since it does not take in account the tab space on the
top

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[RN]

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

--- Comment #31 from RN  ---
Hi Alvin, thank you for getting back to this.

I think the delayed painter you wrote is not going to help in this situation.
Let me explain.
According to this (https://phabricator.kde.org/T4182#62709), Dmitry observed
that the longest delay between window manager updates was about 50ms. So the
window manager was having slow updates while the stabilizer poll timer was
going fast (as they're threaded), accumulating the same position over several
times. That's what causes the bent lines problem.
But that was on his tests, on his system. Maybe some user's system will have
window manager delays of 60ms or more?

Forcing the visual updates (what the delayed painter is doing) when the window
manager can't keep up with visual updates in the first place is not going to
give the expected result, it would stutter anyway.

Therefore, I think the best possible timer interval to use as the default in
the preferences is: no value at all, make it dynamic. Compare the interval from
the previous and current tablet events (in KisToolFreehandHelper::paint), and
any time this interval is greater than the current stabilizer interval then
increase the timer interval to be equal to or greater than that. In Dmitry's
case the timer interval would've grown until reaching 50ms or more.
The timer is stopped when the stroke ends, and when a new stroke begins the
timer interval starts at some default value (16ms for example, or 1ms like
2.9.11 although that might be too fast).

-
Whatever is decided, I think something should be added to the interface (maybe
in Configure Krita -> Tablet Preferences), like spinboxes to set timer values
so that users don't have to go and modify 'kritarc' themselves, and be able to
quickly test different values without having to restart the program. Someone
above mentioned having difficulty doing that, for example.
Regards.

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

[Powerdevil] [Bug 358957] laptop won't hybrid-suspend when Plasma is running

[Lars Hilgenstock]

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

Lars Hilgenstock  changed:

   What|Removed |Added

 CC||lars.hilgenstock@tu-dortmun
   ||d.de

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

[frameworks-baloo] [Bug 379928] New: baloo crash on login

[jetojedno]

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

Bug ID: 379928
   Summary: baloo crash on login
   Product: frameworks-baloo
   Version: 5.26.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: ad...@different-perspectives.com
  Target Milestone: ---

Application: baloo_file (5.26.0)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.62-18.6-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
Reboot following Kmail lockup.
I noticed during reboot that baloo had previously crashed when machine came out
of sleep.

- Unusual behavior I noticed:
Very slow startup.  Desktop didn't appear for about a minute.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcfaaa0a880 (LWP 2924))]

Thread 3 (Thread 0x7fcf9eb9a700 (LWP 3040)):
#0  0x7fcfa854649d in poll () at /lib64/libc.so.6
#1  0x7fcfa4f50314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fcfa4f5042c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fcfa915032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fcfa90fdfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x0041629e in  ()
#6  0x7fcfa8f3a81e in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fcfa8f3d9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fcfa7580744 in start_thread () at /lib64/libpthread.so.0
#9  0x7fcfa854ed3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fcf9f69d700 (LWP 2931)):
#0  0x7fcfa4f4f84c in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7fcfa4f50230 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fcfa4f5042c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fcfa915032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fcfa90fdfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fcfa8f38f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fcfaa3011d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fcfa8f3d9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fcfa7580744 in start_thread () at /lib64/libpthread.so.0
#9  0x7fcfa854ed3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fcfaaa0a880 (LWP 2924)):
[KCrash Handler]
#6  0x7fcfa62451f1 in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x7fcfa97f184d in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x7fcfa97ef350 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x7fcfa9800721 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x0041e5b3 in  ()
#11 0x0041e66d in  ()
#12 0x7fcfa912a1c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x004286a5 in  ()
#14 0x0041ca56 in  ()
#15 0x7fcfa912a1c3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7fcfa9137112 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7fcfa912af34 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7fcfa910008c in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7fcfa90fffc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7fcfa914fc7e in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x7fcfa9150079 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7fcfa4f50134 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7fcfa4f50388 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7fcfa4f5042c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7fcfa915030c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7fcfa90fdfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#27 0x7fcfa9105ec6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x0040b600 in  ()
#29 0x7fcfa84856e5 in __libc_start_main () at /lib64/libc.so.6
#30 0x0040b699 in _start ()

Possible duplicates by query: bug 379685, bug 378054, bug 373626, bug 372328,
bug 370905.

Reported using DrKonqi

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

[krita] [Bug 379746] Black canvas if more than one Fisheye assist is used while zooming

[John]

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

--- Comment #4 from John  ---
Yes, I meant to say inactive.  :P

I certainly was not expecting an instant fix.  If there's any additional data
needed, let me know.  I'll experiment with a few other drivers.

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

[zanshin] [Bug 368728] Please ship translations

[Pino Toscano]

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

--- Comment #2 from Pino Toscano  ---
(In reply to Kevin Ottens from comment #1)
> Guidance would be welcome on the process to do that properly. Been hunting
> for documentation tonight but can't seem to find proper direction in our
> wikis. Been looking at our releaseme scripts but they badly break for me.

>From what I know, releaseme is more for gettext translations (.po files),
rather than Qt translations.  Unfortunately I have no experience with that, so
I'd suggest to ask to kde-core-devel/kde-frameworks/etc.

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

[krita] [Bug 379926] strong lag

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Status|UNCONFIRMED |RESOLVED
 OS|Windows CE  |MS Windows
 Resolution|--- |INVALID
   Platform|Windows CE  |MS Windows

--- Comment #1 from Boudewijn Rempt  ---
Hi Terry,

I'm sorry, but this isn't a useful bug report. A useful bug report includes
full information on the system you're experiencing the problem on, a
description of how to reproduce the problem and a clear problem, like a crash,
that can be fixed.

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