[systemsettings] [Bug 376603] New: Crash after changing composing engine to OpenGL 3.1

2017-02-17 Thread Artur
https://bugs.kde.org/show_bug.cgi?id=376603

Bug ID: 376603
   Summary: Crash after changing composing engine to OpenGL 3.1
   Product: systemsettings
   Version: 5.8.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: arturpol...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-15-generic x86_64
Distribution: Ubuntu Zesty Zapus (development branch)

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

Ubuntu 17.04 with kubuntu-desktop package installed ...
Change composing engine to OpenGL 3.1 and disabling screen lock

-- Backtrace:
Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6de9df58c0 (LWP 5085))]

Thread 4 (Thread 0x7f6db407e700 (LWP 5101)):
#0  0x7ffda2390ad7 in clock_gettime ()
#1  0x7f6de5ba7886 in __GI___clock_gettime (clock_id=1, tp=0x7f6db407da40)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f6de6331f71 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f6de64aeba9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6de64af155 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6de64b04fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6ddfd4df9d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f6ddfd4e9cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f6ddfd4ebbc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f6de64b0f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f6de645a88a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f6de6287fe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f6de45d4df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f6de628cc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f6de1e7d6ca in start_thread (arg=0x7f6db407e700) at
pthread_create.c:333
#15 0x7f6de5b990ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f6dcd7eb700 (LWP 5088)):
#0  0x7f6de5b8d10d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6ddfd4eaa6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6ddfd4ebbc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6de64b0f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6de645a88a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6de6287fe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6de6db45c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f6de628cc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6de1e7d6ca in start_thread (arg=0x7f6dcd7eb700) at
pthread_create.c:333
#9  0x7f6de5b990ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f6dd615d700 (LWP 5087)):
#0  0x7f6de5b8d10d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6de26f4c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6de26f68d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6dd86b4c49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f6de628cc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6de1e7d6ca in start_thread (arg=0x7f6dd615d700) at
pthread_create.c:333
#6  0x7f6de5b990ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f6de9df58c0 (LWP 5085)):
[KCrash Handler]
#6  0x7f6de44a7495 in QV4::WeakValue::free() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f6de4518152 in QV4::QObjectWrapper::destroyObject(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6de43aa69f in QV4::MemoryManager::sweep(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f6de43abaac in QV4::MemoryManager::~MemoryManager() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f6de4496e2b in QV4::ExecutionEngine::~ExecutionEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f6de45d68a6 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f6de45d69c9 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 

[kwin] [Bug 376593] Clean window buffer for areas outside the window's mask

2017-02-17 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=376593

--- Comment #3 from Michail Vourlakos  ---
Martin, thank you very much...

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

[kwin] [Bug 376602] New: Trans­lucency effect on menus d­oesn't work for Qt4 progr­ams

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376602

Bug ID: 376602
   Summary: Trans­lucency effect on menus d­oesn't work for Qt4
progr­ams
   Product: kwin
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sun...@hotmail.ru
  Target Milestone: ---

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

Translucency effect doesn't work for Qt4 programs

Reproducible: Always

Steps to Reproduce:
Desktop Behavior -> Desktop Effects -> Enable Translucency effect and go its
settings -> Make Menus more transparent.

Actual Results:  
Menus should become transparent

Expected Results:  
Qt4 programs don't have the effect.

Maybe its related to toolkit problem like previously
https://bugreports.qt.io/browse/QTBUG-8 but i'm not qualified to post in
there.

Qt5 and GTK3+ work, only Qt4 is effected.

Manjaro x64, updated to Qt 5.8(previously Qt 5.7) and plasma 5.9.2(previously
5.8.5)

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #22 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #21)
> If everything else fails, install it to /usr and reboot.
> 
> cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr ..
> make
> sudo make install

omg, yes this solve the problem. ksysguard behaves normally again, and no more
error message on journalctl.
also, many monitoring widgets (thermal monitor, cpu load) is functional again,
guess it depends on ksysguard.

but system load tab still not drawing cpu history & network history, only
memory & swap history functioning. but this issue happened long before kernel
4.9. i guess i'll search google first.

thanks dude, now should i change the status to resolved?

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #21 from Christoph Feck  ---
If everything else fails, install it to /usr and reboot.

cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr ..
make
sudo make install

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #20 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #19)
> I was referring to the attachment from comment #5. It clearly shows a crash,
> but the symbols are 'n/a' there.
> 
> Also, make sure ksysguard actually connects to your compiled version of
> ksysguardd, instead of the one from distribution packages.

how do i make sure compiled ksysguard connects to compiled ksysguardd? i have
google this, but no manual or explanation on this topic.

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #19 from Christoph Feck  ---
I was referring to the attachment from comment #5. It clearly shows a crash,
but the symbols are 'n/a' there.

Also, make sure ksysguard actually connects to your compiled version of
ksysguardd, instead of the one from distribution packages.

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

[Powerdevil] [Bug 376601] "Leave" overlay does not respect Polkit rule

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376601

patrickrif...@yandex.com changed:

   What|Removed |Added

Summary|Plasma 5 "Leave" overlay|"Leave" overlay does not
   |does not respect Polkit |respect Polkit rule
   |rule|

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

[Powerdevil] [Bug 376601] New: Plasma 5 "Leave" overlay does not respect Polkit rule

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376601

Bug ID: 376601
   Summary: Plasma 5 "Leave" overlay does not respect Polkit rule
   Product: Powerdevil
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: patrickrif...@yandex.com
  Target Milestone: ---

When a custom Polkit rule is set to disable sleep and hibernation the buttons
for both sleep and hibernate are removed from the Application Launcher's
"Leave" menu. However, upon selecting an option from the "Leave" menu the
splash screen that appears still has a "Suspend" button (although it doesn't
function). I would recommend that the splash screen respect the same Polkit
rule the Application Launcher does for consistency.

System Information:
OS: Arch Linux x86_64
KDE Plasma Version: 5.9.2
KDE Frameworks Version: 5.31.0
Qt Version: 5.8.0

Polkit rule contents (/etc/polkit-1/rules.d/10-disable-suspend.rules):

polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.suspend" ||
action.id == "org.freedesktop.login1.suspend-multiple-sessions" ||
action.id == "org.freedesktop.login1.hibernate" ||
action.id == "org.freedesktop.login1.hibernate-multiple-sessions")
{
return polkit.Result.NO;
}
});

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

[krita] [Bug 376373] Can't reach OK button in Configure Krita window

2017-02-17 Thread caetano
https://bugs.kde.org/show_bug.cgi?id=376373

caetano  changed:

   What|Removed |Added

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

--- Comment #3 from caetano  ---
I just found that on linux, when you can't reach the bottom of a window, you
just have to Alt+left click drag on it (in my case Meta instead of Alt)

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #18 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #17)
> Yes, but that backtrace has no debug symbols...

i built it using following commands within build directory inside ksysguard
project
[boes@ARCHHOME build]$cmake -DCMAKE_BUILD_TYPE=Debug ..
[boes@ARCHHOME build]$make
am i missing something here?

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #17 from Christoph Feck  ---
Yes, but that backtrace has no debug symbols...

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #16 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #15)
> The valgrind memcheck log does not show any reason for a crash. The 'invalid
> reads' and 'invalid writes' seem to be gone, so I am wondering if it crashes
> at all.

well, ksysguard itself is not crashing, but avrage cpu load, memory load, and
graphs in system load not drawing at all. and on the process list,
systemd-coredump keep surfacing continuously. after checking journalctl, it is
related to ksysguardd like in attachment 104076

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #15 from Christoph Feck  ---
The valgrind memcheck log does not show any reason for a crash. The 'invalid
reads' and 'invalid writes' seem to be gone, so I am wondering if it crashes at
all.

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #14 from boestari.r...@gmail.com ---
Created attachment 104087
  --> https://bugs.kde.org/attachment.cgi?id=104087=edit
valgrind ksysguard

here's the valgrind ksysguard output. i'm using flag --leak-check=full

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

[krita] [Bug 376487] Everything is slow

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376487

--- Comment #2 from hoangwave...@gmail.com ---
(In reply to Christoph Feck from comment #1)
> Which operating system? Which OpenGL drivers? Which tablet drivers? If you
> can make it to the settings dialog, try disabling the OpenGL canvas.

I am using Windows 7 and I have a Wacom Bamboo Tablet my driver is fine but the
whole program is so slow.

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #13 from Christoph Feck  ---
At cmake time, with -DCMAKE_BUILD_TYPE=Debug

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

[kdevplatform] [Bug 376600] crash on exit when same document is opened in multiple split views [Sublime::Document::closeViews]

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376600

Kevin Funk  changed:

   What|Removed |Added

  Component|general |sublime
Product|kdevelop|kdevplatform

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

[kdevelop] [Bug 376600] crash on exit when same document is opened in multiple split views [Sublime::Document::closeViews]

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376600

Kevin Funk  changed:

   What|Removed |Added

   Keywords||junior-jobs
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Summary|crash on exit when same |crash on exit when same
   |document is opened in   |document is opened in
   |multiple split views|multiple split views
   ||[Sublime::Document::closeVi
   ||ews]

--- Comment #1 from Kevin Funk  ---
Confirmed.

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Aetf
https://bugs.kde.org/show_bug.cgi?id=376595

Aetf <7437...@gmail.com> changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #8 from Aetf <7437...@gmail.com> ---
Hi Ion, from the backtrace it's not clear what's going wrong here. There's no
abnormal pointer access in the frame 0 of the backtrace. Could you also provide
the console output when crashing?

The debugger plugin related logs are disabled by default, you can enable it by
starting kdevelop like this inside console:

QT_LOGGING_RULES="kdevelop.debuggers.gdb.debug=true;kdevelop.debuggers.common.debug=true"
kdevelop

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

[ksshaskpass] [Bug 376318] Regression: passwords no longer remembered, asks every time I open a shell

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376318

--- Comment #2 from Christoph Feck  ---
We could not verify if the issue from bug 376228 is indeed a duplicate.

If your issue is not fixed with Plasma 5.9.3, please add a comment, ideally
with the debug output of the ksshaskpass program.

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-02-17 Thread Peter Wu
https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #8 from Peter Wu  ---
Created attachment 104086
  --> https://bugs.kde.org/attachment.cgi?id=104086=edit
debug patch

I have traced the issue into kpty, KPtyDevicePrivate::_k_canRead.

The ioctl(q->masterFd, FIONREAD, ) returns 0 available data.
Subsequently reading 0 bytes also returns 0 (with errno=0). This is considered
EOF which then prevents further read events from being reported.

tty_ioctl(4) documents FIONREAD as: "Get the number of bytes in the input
buffer."
Not sure if "0 available bytes" should be interpreted as EOF though for ptmx
devices.

Attached is a debug patch. I did not observe ioctl failing in the output. Put a
gdb breakpoint on the "!readBytes" block (line with
"readNotifier->setEnabled(false);") and invoke "call fflush(0)". If you
"return", the output is processed normally.

available 4095
fd=12 readBytes=4095 errno=0
available 4095
fd=12 readBytes=4095 errno=0
available 0
fd=12 readBytes=0 errno=0

Would you see any issues with returning false (without logging other warnings
nor emitting signals) when available==0? Surely if there is really an EOF
condition, read would return 0 which actually detects the EOF?

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

[ksshaskpass] [Bug 376228] git fails with "Unable to extract keyFile from phrase"

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376228

Christoph Feck  changed:

   What|Removed |Added

   Version Fixed In||5.9.3
  Latest Commit||https://commits.kde.org/kss
   ||haskpass/408c284f6a35694f7e
   ||6be76c3416b80f3ef7fdba
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Christoph Feck  ---
Git commit 408c284f6a35694f7e6be76c3416b80f3ef7fdba by Christoph Feck.
Committed on 18/02/2017 at 01:09.
Pushed by cfeck into branch 'Plasma/5.9'.

Fix git ssh password detection

Investigation and patch by Idekel Santana.
FIXED-IN: 5.9.3

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

M  +10   -1src/main.cpp

https://commits.kde.org/ksshaskpass/408c284f6a35694f7e6be76c3416b80f3ef7fdba

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

[plasmashell] [Bug 376551] Meta key fails to operate application launder when caps lock is on

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376551

0the0judge0+...@gmail.com changed:

   What|Removed |Added

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

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

[kdevelop] [Bug 376600] New: crash on exit when same document is opened in multiple split views

2017-02-17 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=376600

Bug ID: 376600
   Summary: crash on exit when same document is opened in multiple
split views
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de
  Target Milestone: ---

Application: kdevelop (5.1.40)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- open one document
- split the editor vew horizontally and vertically
- quit kdevelop

The crash can be reproduced every time.

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

Thread 23 (Thread 0x7fc2b90d1700 (LWP 30998)):
#0  0x7fc33ea9cc95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fc33ea9d6ab in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fc33ea9d89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fc34889f06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fc34884889a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fc34866aa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fc34685c925 in KDevelop::CompletionWorkerThread::run()
(this=0x171e820) at
/home/milian/projects/kf5/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:84
#7  0x7fc34866f6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fc342554454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fc347a677df in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7fc2c8b3d700 (LWP 30990)):
#0  0x7fc33eae2db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fc33ea9d184 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7fc33ea9d724 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fc33ea9d89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fc34889f06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fc34884889a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fc34866aa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fc34685c925 in KDevelop::CompletionWorkerThread::run()
(this=0x49c4fe0) at
/home/milian/projects/kf5/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:84
#8  0x7fc34866f6d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fc342554454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fc347a677df in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7fc2cb7fe700 (LWP 30963)):
#0  0x7fc34255a10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc34867058b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fc346437ed4 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=this@entry=0x4306460, th=0x7fc2c40013e0) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:594
#3  0x7fc346439440 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x4306460, th=, th@entry=0x7fc2c40013e0,
threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:554
#4  0x7fc34643ec46 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x4306800, th=0x7fc2c40013e0, wasBusy=) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:66
#5  0x7fc346437d69 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=, th=0x7fc2c40013e0, wasBusy=) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:568
#6  0x7fc34643bd94 in ThreadWeaver::Thread::run() (this=0x7fc2c40013e0) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/thread.cpp:103
#7  0x7fc34866f6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fc342554454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fc347a677df in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7fc2cbfff700 (LWP 30962)):
#0  0x7fc34255a10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc34867058b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fc346437ed4 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=this@entry=0x4306460, 

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #12 from boestari.r...@gmail.com ---
(In reply to Christoph Feck from comment #10)
> If it still crashes with the patch applied, please add a backtrace with full
> debug symbols, and ideally also a valgrind log (with debug symbols). Note
> that default packages in Arch do not have debug information, so you need to
> compile yourself, or test with a different distribution.

i know how to use valgrind, but how do i enable debug symbols? at compile time
or at running time?

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #11 from boestari.r...@gmail.com ---
(In reply to Rog131 from comment #8)
> (In reply to boestari.riko from comment #6)
> > Created attachment 104077 [details]
> > screenshot
> > 
> > so, i built the latest ksysguard from github and include your changes.
> > running ksysguard, well, nothing changes, it's still running with errors. i
> > include the screenshot. you can see at the bottom, ksysguard only shows
> > number of processes, and missing average cpu usage, memory usage, etc. and
> > in system load tab, the graph is not drawing at all. on previous comment, i
> > also include output of ksysguard and journalctl. sorry for triple post, i
> > have no idea how to attach multiple files here
> 
> Did you clean the $HOME/.local/share/ksysguard/ directory ?

cleaning that directory gave the same result.

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

[kaffeine] [Bug 376556] kaffeine does not find DVB-T2 channels

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376556

--- Comment #3 from yuli...@mailbox.org ---
(In reply to Mauro Carvalho Chehab from comment #2)
> Next time, please don't attach a zip file (or tarball). Instead, put
> each file inside it as a different attachment.
Ok.

> Ok, let's go by parts. The Realtek rtl2832 is a chip that always come with
> DVB-T internally, and supports only pure DVB-T. No DVB-T2 support. As the
> frontend is integrated with the demux on those devices, the Kernel
> recognizes it as frontend0.
> 
> Devices based on such chipset that supports other standards come with an
> extra chip for the frontend. In this case, Panasonic MN88473, with can do
> both DVB-T and DVB-T2.
> 
> As you're adding the same frequency table for both DVB-T and DVB-T2, I
> suspect that Kaffeine is using the first adapter (with supports only DVB-T)
> when seeking for channels. As far as I remember, I didn't add
> any special logic there that would make it so select the better adapter when
> scanning the file. So, it should just get the first available one.
> 
> You can easily test it by changing the adapter two for "no source" (or
> something different than "Automatischer Suchlauf").
> 
> With such change, when you ask to scan "Automatischer Suchlauf", it should
> use the second frontend (the Panasonic one).


When I set adapter 2 (RTL2832) DVB-T: No source
and adapter 1 (Panasonic MN88473) DVB-C: No source and DVB-T2: Automatischer
Suchlauf, then only DVB-T channels are found. Therewhile I can use 
$ dvb-fe-tool -a0 -f1 --get
and I see that the frequency changes and that it is always in DELIVERY_SYSTEM =
DVBT. But it uses the correct frontend (Panasonic MN88473) as far as I can see.

When I set adapter 2 (RTL2832) DVB-T: Automatischer Suchlauf
and adapter 1 (Panasonic MN88473) DVB-C: No source and DVB-T2: No source,  then
again only DVB-T channels are found. Therewhile I can use 
$ dvb-fe-tool -a0 -f0 --get
and I see that the frequency changes and that it is always in DELIVERY_SYSTEM =
DVBT. But this one of course can only do DVB-T only, as it is the wrong
frontend (RTL2832).

So I think that kaffeine uses the correctly the Panasonic MN88473, but fails to
search for DVB-T2 channels. 

May there be some information missing in the frequency table for scanning? Is
the frequency table used actually, if I say "Automatischer Suchlauf"?


> If this works, I'll take a look at the code and seek for a solution to do it
> automatically, but you'll likely need to test such patch, as I guess I don't
> have any RTL-based device with an extra DVB-T2 frontend.
I'd like to test patches.

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

[kwin] [Bug 359465] plasmashell unresponsive/freezes after resuming from suspend to RAM

2017-02-17 Thread rens
https://bugs.kde.org/show_bug.cgi?id=359465

rens  changed:

   What|Removed |Added

 CC||rens.groenewe...@xs4all.nl

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

[plasmashell] [Bug 376599] New: Plasma crashed on quickly switching to another virtual desktop and back

2017-02-17 Thread Edward
https://bugs.kde.org/show_bug.cgi?id=376599

Bug ID: 376599
   Summary: Plasma crashed on quickly switching to another virtual
desktop and back
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: edwardb_...@shaw.ca
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Switched to a different virtual desktop (using Pager) and immediately back.

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

Thread 19 (Thread 0x7f8b5e3df700 (LWP 6727)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f8b625da700 (LWP 31740)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f8b62ddb700 (LWP 31695)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f8b5fbe2700 (LWP 29208)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f8b61be6700 (LWP 3656)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f8bca7fc700 (LWP 3218)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f8bcb7fe700 (LWP 3170)):
#0  0x7f8cab8fc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8cac7e365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f8cb06db4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f8cb06db995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f8cac7e29e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8cab8f7734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f8cac0f6d3d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f8bc103e700 (LWP 2941)):
#0  0x7f8cac103184 in 

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485

--- Comment #10 from marcin.ba...@gmail.com ---
I attached profiling results on Nvidia and Intel.
Steps:
1. Start copy files in dolphin
2. Run command:
timeout [t]s ./apitrace trace --api gl plasmashell
where t = 30s, 50s

Because of attachments limit all files are available here:
https://mega.nz/#F!h8pgmRCQ!0F93jY7rTDiGIFWy8Nay4Q

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

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485

--- Comment #9 from marcin.ba...@gmail.com ---
Created attachment 104085
  --> https://bugs.kde.org/attachment.cgi?id=104085=edit
30s Intel apitrace

Command:
timeout 30s ./apitrace trace --api gl plasmashell

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

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485

--- Comment #7 from marcin.ba...@gmail.com ---
Created attachment 104083
  --> https://bugs.kde.org/attachment.cgi?id=104083=edit
30s Nvidia apitrace

Command:
timeout 30s ./apitrace trace --api gl plasmashell

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

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485

--- Comment #8 from marcin.ba...@gmail.com ---
Created attachment 104084
  --> https://bugs.kde.org/attachment.cgi?id=104084=edit
50s Intel apitrace

Command:
timeout 50s ./apitrace trace --api gl plasmashell

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595

Kevin Funk  changed:

   What|Removed |Added

 CC||7437...@gmail.com

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

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485

--- Comment #6 from marcin.ba...@gmail.com ---
Created attachment 104082
  --> https://bugs.kde.org/attachment.cgi?id=104082=edit
50s Nvidia apitrace

Command:
timeout 50s ./apitrace trace --api gl plasmashell

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

2017-02-17 Thread Egmont Koblinger
https://bugs.kde.org/show_bug.cgi?id=372991

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

--- Comment #7 from Egmont Koblinger  ---
I can second Hello71's observation: "taskset -c 0 konsole" works perfectly for
me. Looks like a race condition around multiple threads, or something like
this.

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

[frameworks-kio] [Bug 376581] fish protocol not working with link local ipv6 addresses

2017-02-17 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=376581

Elvis Angelaccio  changed:

   What|Removed |Added

Version|unspecified |5.29.0
Product|dolphin |frameworks-kio
  Component|general |general
 CC||kdelibs-b...@kde.org
   Assignee|dolphin-bugs-n...@kde.org   |fa...@kde.org

--- Comment #3 from Elvis Angelaccio  ---
This looks like a bug in KUrlNavigator, which reports the following (wrong) url
to Dolphin:

http://fish/user@fe80::308d:2a8a:7c16:4756%25enp3s0

Moving to kio for now.

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595

--- Comment #7 from Ian Haber  ---
if you need anything else from gdb, i still have it up and will get back to you
on monday.

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

[klipper] [Bug 376588] Simple menu

2017-02-17 Thread BRULE Herman
https://bugs.kde.org/show_bug.cgi?id=376588

--- Comment #2 from BRULE Herman  ---
If I do this I have 2 icon and entry into System Tray Settings are partially
empty and don't show the second icon, only klipper

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

[kwin] [Bug 376505] kwin compile error in Gentoo gcc-6.3.0, glibc-2.25

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376505

Christoph Feck  changed:

   What|Removed |Added

   Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595

--- Comment #6 from Ian Haber  ---
here is the backtrace. it also looks like i got a message saying 'breakpoint
doesn't contain required location/expression data'. maybe that has something to
do with it

Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.
0x7fffb263a07e in KDevMI::MI::MICommand::markAsCompleted() ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
(gdb) bt
#0  0x7fffb263a07e in KDevMI::MI::MICommand::markAsCompleted() ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
#1  0x7fffb263bd9d in KDevMI::MIDebugger::processLine(QByteArray const&) ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
#2  0x7fffb263b506 in KDevMI::MIDebugger::readyReadStandardOutput() ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
#3  0x7fffb263e308 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void (KDevMI::MIDebugger::*)()>::call(void
(KDevMI::MIDebugger::*)(), KDevMI::MIDebugger*, void**) ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
#4  0x7fffb263e1ca in void QtPrivate::FunctionPointer::call, void>(void
(KDevMI::MIDebugger::*)(), KDevMI::MIDebugger*, void**) ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
#5  0x7fffb263ded1 in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
   from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so
#6  0x75d35baf in QtPrivate::QSlotObjectBase::call (a=0x7fffcfa0,
r=0x6c72030, this=)
at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#7  QMetaObject::activate (sender=sender@entry=0x6c72120,
signalOffset=, 
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at
kernel/qobject.cpp:3698
#8  0x75d36537 in QMetaObject::activate (sender=sender@entry=0x6c72120, 
m=m@entry=0x75f4c400 ,
local_signal_index=local_signal_index@entry=5, 
argv=argv@entry=0x0) at kernel/qobject.cpp:3578
#9  0x75c34b63 in QProcess::readyReadStandardOutput
(this=this@entry=0x6c72120) at .moc/moc_qprocess.cpp:266
---Type  to continue, or q  to quit---
#10 0x75c3d0c2 in QProcessPrivate::tryReadFromChannel (this=0x6c72140,
channel=0x6c72270)
at io/qprocess.cpp:966
#11 0x75c3d540 in QProcessPrivate::_q_canReadStandardOutput
(this=) at io/qprocess.cpp:977
#12 QProcess::qt_static_metacall (_o=, _c=,
_id=, _a=0x7fffd1a0)
at .moc/moc_qprocess.cpp:133
#13 0x75d35d2a in QMetaObject::activate (sender=sender@entry=0x6c72ec0,
signalOffset=, 
local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fffd1a0) at kernel/qobject.cpp:3713
#14 0x75d36537 in QMetaObject::activate (sender=sender@entry=0x6c72ec0, 
m=m@entry=0x75f50780 ,
local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffd1a0) at kernel/qobject.cpp:3578
#15 0x75db524e in QSocketNotifier::activated
(this=this@entry=0x6c72ec0, _t1=82)
at .moc/moc_qsocketnotifier.cpp:134
#16 0x75d421cb in QSocketNotifier::event (this=0x6c72ec0, e=) at kernel/qsocketnotifier.cpp:260
#17 0x765fa05c in QApplicationPrivate::notify_helper
(this=this@entry=0x647190, 
receiver=receiver@entry=0x6c72ec0, e=e@entry=0x7fffd410) at
kernel/qapplication.cpp:3716
#18 0x765ff516 in QApplication::notify (this=0x7fffd970,
receiver=0x6c72ec0, e=0x7fffd410)
at kernel/qapplication.cpp:3499
#19 0x75d0738b in QCoreApplication::notifyInternal
(this=0x7fffd970, receiver=0x6c72ec0, 
event=event@entry=0x7fffd410) at kernel/qcoreapplication.cpp:965
#20 0x75d5dc95 in QCoreApplication::sendEvent (event=0x7fffd410,
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#21 socketNotifierSourceDispatch (source=0x7659a0) at
kernel/qeventdispatcher_glib.cpp:101
#22 0x7fffee394197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fffee3943f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fffee39449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x75d5d7cf in QEventDispatcherGlib::processEvents (this=0x765850,
flags=...)
at kernel/qeventdispatcher_glib.cpp:418
#26 0x75d04b4a in QEventLoop::exec (this=this@entry=0x7fffd620,
flags=..., flags@entry=...)
at kernel/qeventloop.cpp:204
#27 0x75d0cbec in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#28 0x0040e79e in main ()

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

[kwin] [Bug 376380] Plasma crashes while switching activities since upgrading to 5.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376380

--- Comment #3 from Christoph Feck  ---
Our crash reporting guide is at
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[dolphin] [Bug 376581] fish protocol not working with link local ipv6 addresses

2017-02-17 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=376581

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Yes, please. We need a backtrace with debug symbols (see
https://community.kde.org/Dolphin/FAQ/Crashes)

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

[kwin] [Bug 376254] Taskbar/transparency glitches with SDL2 programs running

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376254

--- Comment #5 from Christoph Feck  ---
If you can provide the information requested in comment #4, please add it.

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

[dolphin] [Bug 376577] Search crashes when started from root folder

2017-02-17 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=376577

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
(In reply to Alex from comment #0)
> To replicate:
> - open dolphin
> - go to root folder
> - search for .svg
> - wait a while
> 
> I can help providing some info if needed.

Yes, please. We need a backtrace with debug symbols (see
https://community.kde.org/Dolphin/FAQ/Crashes)

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

[dolphin] [Bug 376581] fish protocol not working with link local ipv6 addresses

2017-02-17 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=376581

--- Comment #2 from Elvis Angelaccio  ---
(In reply to Elvis Angelaccio from comment #1)
> Yes, please. We need a backtrace with debug symbols (see
> https://community.kde.org/Dolphin/FAQ/Crashes)

Sorry, wrong thread. Ignore this comment :p

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

[kwin] [Bug 375578] KDE file save menu do not appear in window switcher or window list using chrome or chromium

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=375578

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #4 from Christoph Feck  ---
No response, changing status. If you have new information, please add a
comment.

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

[plasmashell] [Bug 376237] Freeze on splash screen at login

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376237

nono31...@gmail.com changed:

   What|Removed |Added

   Severity|critical|normal

--- Comment #1 from nono31...@gmail.com ---
Deleting the content of .config, .cache and .local seems to have done the
trick.

I have not been stuck on the splashscreen of 5.8 for a few days now.
I'll try upgrading again to 5.9 and see after a couple of days if is fixed too
and stable.

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595

--- Comment #5 from Kevin Funk  ---
True, this got added just recently. I've restored compat with KF5 5.15 now.

See:
commit 2c775c07436107f90bec8ee16b73f4e5258f362d
Author: Kevin Funk 
Date:   Fri Feb 17 23:32:22 2017 +0100

Restore compat with KF5 5.15

The signal KUrlRequester::textEdited got only added in 5.21

Please try to compile again

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

[kaffeine] [Bug 376556] kaffeine does not find DVB-T2 channels

2017-02-17 Thread Mauro Carvalho Chehab
https://bugs.kde.org/show_bug.cgi?id=376556

--- Comment #2 from Mauro Carvalho Chehab  ---
Next time, please don't attach a zip file (or tarball). Instead, put
each file inside it as a different attachment.

(In reply to yulinux from comment #0)
> Created attachment 104060 [details]
> additional information like screenshots, lsusb, dmesg, uname, kaffeine
> --debug and dvb-fe-tool outputs
> 
> Hallo, 
> I have brought a cheap Chinese DVB-T2 device (casing of [1], but has a
> Panasonic MN88473 inside like [2]). Anyway, after copying the firmware into
> the right folder, the device seems to work, see dmesg.
> The device has two frontends, as shown in the pictures attached. And I use
> kaffeine from git and linux kernel 4.10RC8.

> When using tvheadend, it finds all DVB-T and DVB-T2 channels and all can be
> watched. So the kernel driver and the hardware should be fine.
> 
> Any idea what could be the problem? What could I test in order to debug the
> issue?

Ok, let's go by parts. The Realtek rtl2832 is a chip that always come with
DVB-T internally, and supports only pure DVB-T. No DVB-T2 support. As the
frontend is integrated with the demux on those devices, the Kernel
recognizes it as frontend0.

Devices based on such chipset that supports other standards come with an extra
chip for the frontend. In this case, Panasonic MN88473, with can do both DVB-T
and DVB-T2.

As you're adding the same frequency table for both DVB-T and DVB-T2, I suspect
that Kaffeine is using the first adapter (with supports only DVB-T) when
seeking for channels. As far as I remember, I didn't add
any special logic there that would make it so select the better adapter when
scanning the file. So, it should just get the first available one.

You can easily test it by changing the adapter two for "no source" (or
something different than "Automatischer Suchlauf").

With such change, when you ask to scan "Automatischer Suchlauf", it should use
the second frontend (the Panasonic one).

If this works, I'll take a look at the code and seek for a solution to do it
automatically, but you'll likely need to test such patch, as I guess I don't
have any RTL-based device with an extra DVB-T2 frontend.

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

[krita] [Bug 367842] Smudge Brush Radius could use a better sampling method.

2017-02-17 Thread lokesh
https://bugs.kde.org/show_bug.cgi?id=367842

lokesh  changed:

   What|Removed |Added

 CC||slokesh...@gmail.com

--- Comment #2 from lokesh  ---
Are artifacts like circular bands appearing when dragging it on canvas .
I would be glad to work on it . This would be my first time with krita . I
might 
need some help . thanks

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

[plasmashell] [Bug 376481] Shortcuts on the desktop no longer working

2017-02-17 Thread Roman S .
https://bugs.kde.org/show_bug.cgi?id=376481

--- Comment #1 from Roman S.  ---
Note: it might have been caused by wrong ebuilds - after today's updates the
problem does not exists anymore...

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595

--- Comment #4 from Ian Haber  ---
I get this build error when i attempt to build master. what module is
KUrlRequester in that i'm assuming i need to add to the list of things to
download and update.

/home/ian/kdesrc/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/widget/compilerswidget.cpp:81:34:
error: ‘textEdited’ is not a member of ‘KUrlRequester’
 connect(m_ui->compilerPath, ::textEdited, this,
::compilerEdited);

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

[krita] [Bug 376598] New: Lag, Crashing, Missing Textures, ect

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376598

Bug ID: 376598
   Summary: Lag, Crashing, Missing Textures, ect
   Product: krita
   Version: unspecified
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: emilydoris1...@yahoo.com
  Target Milestone: ---

I've had Krita for awhile. During 2.9, the lag wasn't bad, if I zoomed in on
the canvas it was fine, so I didn't worry about it. As soon as 3.0 and forward
was implemented, lag grew terrible,it constantly crashes (causing me to lose
work I've spent hours on if I don't save every five minutes) and I tend to find
missing textures for brush buttons/labels, which is a newer problem.I'd
appreciate any help that is available! Thank you!

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595

--- Comment #3 from Kevin Funk  ---
FWIW, master should build fine according to CI. If you want to switch branches
I *think* you should be able to use this:

module kdevelop
  branch-group kf5-qt5
...

If that doesn't work you can still simply just `git checkout 5.1; make; make
install` in both the kdevplatform + kdevelop dir.

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

[okular] [Bug 376574] Linked video in pdf doesn't work

2017-02-17 Thread Oliver Sander
https://bugs.kde.org/show_bug.cgi?id=376574

--- Comment #3 from Oliver Sander  ---
The problem is in the file videowidget.cpp, in the method
VideoWidget::Private::load().

There, starting in line 110 is says

QString url = movie->url();

Here, url is the movie location, namely http:/vmiklos.hu/file/small.mp4

The code continues:

QUrl newurl;
if ( QDir::isRelativePath( url ) )
{
newurl = document->currentDocument().adjusted(QUrl::RemoveFilename);
newurl.setPath( newurl.path() + url );
}

and sure enough, QDir::isRelativePath takes the content of 'url' to be a
relative path, because it does not start with '/'.   Hence the 'if' branch is
taken, and the document path is prepended to the movie part. Seems like the
code was not written with internet movies in mind.

Strangely enough, the code continues:

if ( newurl.isLocalFile() )
player->load( newurl );
else
player->load( newurl );

Surely that's not right?  Martin, you introduced this in d8fdb1494 , can you
please have a look?

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595

--- Comment #2 from Ian Haber  ---
so i've never been able to get a backtrace while using the appimage. I
attempted to build source today, but it seems there are build errors in master
at the moment. how do i set kdesrc-build to use branch 5.1 for kdevelop and
kdevplatform? 

I attempted to modify the .kdesrc-buildrc and set it to use branch 5.1, but it
attempts to use svn instead of git and then fails to update.

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

[kaffeine] [Bug 376556] kaffeine does not find DVB-T2 channels

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376556

--- Comment #1 from yuli...@mailbox.org ---
Just to clarify: It probably *is* the newer version of the device, but just in
another case. The case is actually a bit different compared to the older one,
it is labelled differently [1], which I missed.
But this is probably not relevant to this bug report.

[1]
http://www.ixbt.com/monitor/images/astrometa-digital-tv-dongle/astrometa-digital-tv-dongle-1.jpg

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

[krita] [Bug 376597] New: Text created using Multiline text tool disappears when reopening .kra file and cuases Krita to crash

2017-02-17 Thread Lia Min
https://bugs.kde.org/show_bug.cgi?id=376597

Bug ID: 376597
   Summary: Text created using Multiline text tool disappears when
reopening .kra file and cuases Krita to crash
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Text Tool
  Assignee: krita-bugs-n...@kde.org
  Reporter: liami...@gmail.com
  Target Milestone: ---

All text created using the text tool in multiline mode disappears from some
.kra files when they are reopened. It is not clear which file this happens to,
but the problem persists for those that are affected. (ie, new texts that are
typed in using multiline mode in these documents, either in a new text box or
in a pre-existing box, disappears when the file is saved, closed and reopened.) 
In addition, Krita will often freeze or crash when using multiline option to
create or edit texts -this problems happens across all documents.

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

[kdevelop] [Bug 376586] Kdevelop crashes during parsing on large PHP projects/files

2017-02-17 Thread robert
https://bugs.kde.org/show_bug.cgi?id=376586

--- Comment #2 from robert  ---
I will try without rebuilding my whole dev space.

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

[krita] [Bug 376596] crash while removing frames in the animation timeline

2017-02-17 Thread z-uo
https://bugs.kde.org/show_bug.cgi?id=376596

--- Comment #1 from z-uo  ---
okay after a few more test it crash every times with the copy of the file, so
I've put it here
https://nicolasbougere.cozycloud.cc/public/files/files/ab1e8a58e2a31d9afca2b473858ce0c6/attach/sdggxcbxcvxcv.kra
I also tried with the krita appimage with the same result
The step are (in the timeline) in the layer "jambe droite" select the frame 33 
with shift select the frame 11
right clic and remove frame
then it crash

If you first select the frame 11 then the 33 it works just fine...

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

[krita] [Bug 376596] New: crash while removing frames in the animation timeline

2017-02-17 Thread z-uo
https://bugs.kde.org/show_bug.cgi?id=376596

Bug ID: 376596
   Summary: crash while removing frames in the animation timeline
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: nicolas.boug...@z-uo.com
  Target Milestone: ---

I have a kra file who crash every times I try to remove like 10 frames on a
specific layer. 
Its a file with 8 animation layer and 30 frames on each.
I wanted to attach the file with the bug repport but I make a copy of the kra
file with my file manager and try the same operation, it doesn't crash, I
retried the first file who still crash.

I suspect something with the cache.
I'm not sure its enough information for you to investigate?

I'm using the ppa on ubuntu.

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

[krunner] [Bug 376547] Krunner crash while performing simple calculator operations

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376547

--- Comment #2 from emele...@gmail.com ---
(In reply to Kai Uwe Broulik from comment #1)
> Can you verify whether this still happens with KPackage 5.30 or later? I
> fixed a crash in there (Bug 374541) and the BT looks similar but not
> completely the same.

I will as soon as I 5.30 reaches downstream (fedora)

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

[kmymoney4] [Bug 376046] Missing icons in toolbar and payments panel on home page

2017-02-17 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=376046

NSLW  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmy
   ||money/3629183bf6ea42b59d566
   ||104bc6c63f2140e1b1d
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from NSLW  ---
Git commit 3629183bf6ea42b59d566104bc6c63f2140e1b1d by Łukasz Wojniłowicz.
Committed on 17/02/2017 at 20:15.
Pushed by wojnilowicz into branch 'master'.

Add more fallback icons
Signed-off-by: Łukasz Wojniłowicz 

M  +2-1kmymoney/dialogs/kimportdlg.cpp
M  +37   -9kmymoney/kmymoney.cpp
M  +2-2kmymoney/kmymoneyui.rc
M  +4-0kmymoney/kmymoneyutils.cpp
M  +12   -9kmymoney/views/khomeview.cpp
M  +8-2kmymoney/views/kreportsview.cpp

https://commits.kde.org/kmymoney/3629183bf6ea42b59d566104bc6c63f2140e1b1d

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

[kmymoney4] [Bug 372547] Unable to load some investments on KF5

2017-02-17 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=372547

NSLW  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/90e906fdadb22ec572c1e
   ||3f9324297943e5a930f
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from NSLW  ---
Git commit 90e906fdadb22ec572c1e3f9324297943e5a930f by Łukasz Wojniłowicz.
Committed on 17/02/2017 at 20:15.
Pushed by wojnilowicz into branch 'master'.

Allow importing single security investment statements

Summary:
Reuse security dialog to get imported security information.

Signed-off-by: Łukasz Wojniłowicz 

Reviewers: #kmymoney

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

Signed-off-by: Łukasz Wojniłowicz 

M  +57   -5kmymoney/plugins/csvimport/investmentwizardpage.cpp
M  +6-0kmymoney/plugins/csvimport/investmentwizardpage.h

https://commits.kde.org/kmymoney/90e906fdadb22ec572c1e3f9324297943e5a930f

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

[kmymoney4] [Bug 373966] Incorrect rates used during a report

2017-02-17 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=373966

NSLW  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kmy
   ||money/622dab3f94878c5015187
   ||95aa00c102d10562a1a
 Resolution|--- |FIXED

--- Comment #3 from NSLW  ---
Git commit 622dab3f94878c501518795aa00c102d10562a1a by Łukasz Wojniłowicz.
Committed on 17/02/2017 at 20:15.
Pushed by wojnilowicz into branch 'master'.

Revise investment transaction report

Summary:
Price of transaction should be taken from transaction and not from
stored prices.
Investment accounts should report asset split as main split for correct
amount value, as it contains fees.
Related: bug 365306
Signed-off-by: Łukasz Wojniłowicz 

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

Signed-off-by: Łukasz Wojniłowicz 

M  +99   -45   kmymoney/reports/querytable.cpp
M  +7-7kmymoney/reports/tests/querytable-test.cpp
M  +1-1kmymoney/reports/tests/reportstestcommon.cpp

https://commits.kde.org/kmymoney/622dab3f94878c501518795aa00c102d10562a1a

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

[kmymoney4] [Bug 365306] Investment Transactions report Price and Amount in error

2017-02-17 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=365306

NSLW  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kmy
   ||money/622dab3f94878c5015187
   ||95aa00c102d10562a1a
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from NSLW  ---
Git commit 622dab3f94878c501518795aa00c102d10562a1a by Łukasz Wojniłowicz.
Committed on 17/02/2017 at 20:15.
Pushed by wojnilowicz into branch 'master'.

Revise investment transaction report

Summary:
Price of transaction should be taken from transaction and not from
stored prices.
Investment accounts should report asset split as main split for correct
amount value, as it contains fees.
Related: bug 373966
Signed-off-by: Łukasz Wojniłowicz 

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

Signed-off-by: Łukasz Wojniłowicz 

M  +99   -45   kmymoney/reports/querytable.cpp
M  +7-7kmymoney/reports/tests/querytable-test.cpp
M  +1-1kmymoney/reports/tests/reportstestcommon.cpp

https://commits.kde.org/kmymoney/622dab3f94878c501518795aa00c102d10562a1a

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

[kmymoney4] [Bug 346001] Transactions in an investment account do not allow zero total fees

2017-02-17 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=346001

NSLW  changed:

   What|Removed |Added

   Version Fixed In||5.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmy
   ||money/6c8ea50f92eed6915f18f
   ||4ed4f75af1147476d4a

--- Comment #1 from NSLW  ---
Git commit 6c8ea50f92eed6915f18f4ed4f75af1147476d4a by Łukasz Wojniłowicz.
Committed on 17/02/2017 at 20:15.
Pushed by wojnilowicz into branch 'master'.

Allow zero total fees transactions

Summary:
The total amount of fees is unimportant. Important is that splits that
compose fee are not equall to zero.
FIXED-IN: 5.0
Signed-off-by: Łukasz Wojniłowicz 
Differential Revision: https://phabricator.kde.org/D4397

Signed-off-by: Łukasz Wojniłowicz 

M  +23   -6kmymoney/dialogs/investactivities.cpp
M  +8-0kmymoney/dialogs/investtransactioneditor.h

https://commits.kde.org/kmymoney/6c8ea50f92eed6915f18f4ed4f75af1147476d4a

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

[kmymoney4] [Bug 346003] Entries in an investment account that have a split transaction for fees show incorrectly

2017-02-17 Thread NSLW
https://bugs.kde.org/show_bug.cgi?id=346003

NSLW  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.0
  Latest Commit||https://commits.kde.org/kmy
   ||money/598c110125433a0ac7210
   ||fda10ba43811e239d8d
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from NSLW  ---
Git commit 598c110125433a0ac7210fda10ba43811e239d8d by Łukasz Wojniłowicz.
Committed on 17/02/2017 at 20:15.
Pushed by wojnilowicz into branch 'master'.

Prevent overwrite of assetAccountSplit

Summary:
FIXED-IN:5.0
Signed-off-by: Łukasz Wojniłowicz 
Differential Revision: https://phabricator.kde.org/D4399

Signed-off-by: Łukasz Wojniłowicz 

M  +7-1kmymoney/kmymoneyutils.cpp

https://commits.kde.org/kmymoney/598c110125433a0ac7210fda10ba43811e239d8d

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

[kdevelop] [Bug 376586] Kdevelop crashes during parsing on large PHP projects/files

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376586

Kevin Funk  changed:

   What|Removed |Added

  Component|Language Support: PHP   |Language Support:
   ||QML/JavaScript

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

[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376595

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Kevin Funk  ---
Please retrieve a backtrace of the crash.

See:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[kdevelop] [Bug 376586] Kdevelop crashes during parsing on large PHP projects/files

2017-02-17 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=376586

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Kevin Funk  ---
Crash inside the QML/JS parser plugin:

Thread 10 (Thread 0x7fe1abfff700 (LWP 1979)):
[KCrash Handler]
#6  0x7fe1a8b3d11a in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevqmljslanguagesupport.so
#7  0x7fe1a8b3d691 in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevqmljslanguagesupport.so
#8  0x7fe1a8b6c038 in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevqmljslanguagesupport.so
#9  0x7fe1a8b6db3c in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevqmljslanguagesupport.so
#10 0x7fe1a8b3b37c in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevqmljslanguagesupport.so
#11 0x7fe1a8b3db5a in  () at
/usr/lib/qt/plugins/kdevplatform/25/kdevqmljslanguagesupport.so


Could you please try to instal debugging symbols for this plugin and try to
reproduce the crash? Please send the backtrace another time.

See:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[plasmashell] [Bug 376540] plasmashell crashes when activating pim-plugin

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376540

--- Comment #2 from m...@johannes-tress.de ---
Sorry, but I couldn't identify the part, which is responsible for this bug. I
tried to get gdb plasmashell, but I got the message, that there are no
debugging symbols installed. After looking for plasmashell dbg I couldn't find
the respective package.

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

[krita] [Bug 375878] Eraser will not switch back to brush after turning Wacom pen back around

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375878

thejaz...@gmail.com changed:

   What|Removed |Added

 CC||thejaz...@gmail.com

--- Comment #12 from thejaz...@gmail.com ---
(In reply to aferguson1975 from comment #4)
> (In reply to aferguson1975 from comment #3)
> > I'm having exactly the same issue. Pick a brush, draws fine, flip pen to
> > eraser side, erases fine, flip pen back to pen side, stuck on eraser. Did a
> > clean install of Krita to see if that would fix it but the problem 
> > persisted.
> > 
> > OS: Win 10
> > GPU: NVidia GeForce GTX 960M
> > CPU: Intel Core i7
> > RAM: 16GB
> > Tablet: Wacom Intuos Pen and Touch CTH-480/s
> 
> I went back and installed an older version and the problem continued. I had
> to delete the Krita file from AppData to get it to go away.

I deleted the Krita file too but now it stays on the basic_tip_default brush
instead. And when I press E and flip the pen, it erases but then stays on
eraser mode until I choose a new brush again. Blehh

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

[krita] [Bug 376580] crash after working little while

2017-02-17 Thread basse
https://bugs.kde.org/show_bug.cgi?id=376580

--- Comment #2 from basse  ---
couple of more crashes just now..  this time I was testing how the whole
perspective assistant thing works.. I set up some assistant lines and tried to
figure out how to move the points after I had placed them... so I wasn't even
doing much... and then just noticed Krita is not responsive, and down we went
again. 

backtrace, well looks to be the same, so I'm not posting.

what is grid-config?

.b

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

[krita] [Bug 375503] MP4 render doesn't play in any program

2017-02-17 Thread Benedict W Mogendi
https://bugs.kde.org/show_bug.cgi?id=375503

--- Comment #16 from Benedict W Mogendi  ---
Thanks for the help everyone! (In reply to Dmitry Kazakov from comment #13)
> (In reply to yuknowmyemailnow from comment #12)
> > Both high10 and baseline worked. If you don't mind me asking, what does
> > changing those profile options do to the video?
> 
> They tell ffmpeg to use older versions of h264 codec for compressing the
> video. The difference between these versions is really subtle: older
> versions might work slower and has worse quality and compression, but they
> are recognized by a broader range of devices/players. Basically, you have
> two options: 
> 
> 1) Install the most modern codecs to your computer. Afair, there are a lot
> of "codec packs" available on Windows. Mind you, these videos might still
> not play on some (older) hardware players.
> 
> 2) Just use older codecs by choosing lower profiles.

Thank you!! This worked for me as well

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

[kwin] [Bug 376593] Clean window buffer for areas outside the window's mask

2017-02-17 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=376593

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Gräßlin  ---
The Qt documentation does not make much sense for X11. The mask uses the shape
extension https://www.x.org/releases/current/doc/xextproto/shape.html

The compositor has not much to do with it. You can easily see this by using
common shaped windows such as xeyes.

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

[klipper] [Bug 376588] Simple menu

2017-02-17 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=376588

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
The old menu is still available. Just start klipper.

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

[kdevelop] [Bug 376595] New: Kdevelop crashes on watch member variable

2017-02-17 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=376595

Bug ID: 376595
   Summary: Kdevelop crashes on watch member variable
   Product: kdevelop
   Version: 5.1.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: master.ha...@gmail.com
CC: niko.s...@gmail.com
  Target Milestone: ---

Kdevelop crashes whenever a breakpoint on a watched variable is tripped (if the
variable is a member variable). Local variables work as intended.

Steps to reproduce:
1. Debug program
2. set Break on change for that variable
3. Run until that variable changes
4. watch crash.

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

[kwin] [Bug 376593] Clean window buffer for areas outside the window's mask

2017-02-17 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=376593

--- Comment #1 from Michail Vourlakos  ---
it could be of course also an X11 painting issue that wayland would fix it...

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #10 from Christoph Feck  ---
If it still crashes with the patch applied, please add a backtrace with full
debug symbols, and ideally also a valgrind log (with debug symbols). Note that
default packages in Arch do not have debug information, so you need to compile
yourself, or test with a different distribution.

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

[krita] [Bug 376592] Krita crashing at start

2017-02-17 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=376592

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
I'm sorry, but to run Krita you need to have OSX 10.9 El Capitan at the
minimum; 10.8 is not supported.

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

[krita] [Bug 376594] New: crash while copying a rectangular selection of frame in the timeline

2017-02-17 Thread z-uo
https://bugs.kde.org/show_bug.cgi?id=376594

Bug ID: 376594
   Summary: crash while copying a rectangular selection of frame
in the timeline
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: nicolas.boug...@z-uo.com
  Target Milestone: ---

Make two layer in the animation timeline
put some frame on each layer
select all the frame from the tow layers
start a copy (with ctrl) in the upper layer
end the copy in the lower layer
and krita crash

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

[kwin] [Bug 376593] New: Clean window buffer for areas outside the window's mask

2017-02-17 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=376593

Bug ID: 376593
   Summary: Clean window buffer for areas outside the window's
mask
   Product: kwin
   Version: 5.9.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mvourla...@gmail.com
  Target Milestone: ---

Hello, 

there is the following issue with the Now Dock or the all new Latte Dock. As a
reference both are docks that animate with parabolic zoom their tasks and
plasmoids. They both use the QQuickWindow mask in order to free the areas of
the window that are not needed from the dock.
We have the following issue and we are trying to understand whichone's
responsibility is this case.

As you can see in the screenshot:
https://cloud.githubusercontent.com/assets/24593950/22618122/43503764-ead5-11e6-9eb6-141bbd907b2e.png

when the parabolic zoom starts, the mask of the window increases directly to
the maximum needed size but there are cases that the above painting is
happening.

By reading at: http://doc.qt.io/qt-5/qwindow.html#setMask

Window manager responsibility: "The window manager may or may not choose to
display any areas of the window not included in the mask"

Application responsibility: "it is the application's responsibility to clear to
transparent the areas that are not part of the mask."

from our part we dont paint the areas outside the mask for the above screenshot
to occur. Could you please provide with some wisdom, is this Qt, Kwin or our
dock fault?

with regards,
michail

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

[plasmashell] [Bug 376591] application menu: moving mouse cursor from submenu item to edge of main menu crashes plasmashell

2017-02-17 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=376591

S. Christian Collins  changed:

   What|Removed |Added

  Component|general |Application Menu (Kicker)

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

[i18n] [Bug 376243] Várias traduções estão em pt-pt

2017-02-17 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=376243

--- Comment #3 from Dr. Chapatin  ---
Muito estranho, pois, como eu disse antes, tudo isso estava traduzido para
pt-br até algumas versões do kde atrás.
Vamos aguardar que seja tudo traduzido então.

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

[kmenuedit] [Bug 345100] The menu editor doesn't properly save new icons for submenus

2017-02-17 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=345100

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

2017-02-17 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=360478

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

--- Comment #14 from S. Christian Collins  ---
In comment #1, Martin Klapetek mentioned that we can't know if the resolution
was changed by the user vs. some application.

Perhaps a way to solve this would be:
1. When a user adds or moves a widget, its position/dimensions are stored.
2. If a resolution change forces a widget to change position/dimensions, that
change should happen dynamically but not alter the stored widget position. That
way if a resolution is made smaller and then larger again, the widget's
original positioning is not lost.

I think the above conditions would best follow the user's intent. No need to be
storing per-resolution widget positions, which would make things more
complicated than they need to be.

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=376537

--- Comment #9 from Rog131  ---
At here: AMD FX-6100 (six core) & Arch Linux. With the Kernel 4.9.8 the core
numbering is 0,3,4,5,6,7 -> The Ksysguard is crashing


Downloading the Arch Ksysguard PKGBUILD:
https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/ksysguard

Applying the patch: patch -p1 -i /path/to/counter.diff

Wrapping the package: makepkg -e

Installing the package: pacman -U ksysguard-5.9.2-1-x86_64.pkg.tar.xz

Restarting the plasmashell: kquitapp5 plasmashell and then plasmashell

Testing the ksysguard -> The CPU History and the Network History are blank.

Cleaning (removing files from) the $HOME/.local/share/ksysguard/

Restarting the plasmashell and testing again - working - the core numbering is
a bit strange 1,4,5,6,7,8 : http://imgur.com/ys2ADg9

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

[krita] [Bug 376592] New: Krita crashing at start

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376592

Bug ID: 376592
   Summary: Krita crashing at start
   Product: krita
   Version: 3.1.2
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: mail.agust...@gmail.com
  Target Milestone: ---

Created attachment 104081
  --> https://bugs.kde.org/attachment.cgi?id=104081=edit
Crash Dump

When starting, Krita crash. 

For the record, I installed the beta version first (but it also crashed). Then
when the 3.1.2 version was available, I installed it, but same result. 

I attached the crash dump.

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

[ksysguard] [Bug 376537] ksysguardd crashed on kernel 4.9

2017-02-17 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=376537

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #8 from Rog131  ---
(In reply to boestari.riko from comment #6)
> Created attachment 104077 [details]
> screenshot
> 
> so, i built the latest ksysguard from github and include your changes.
> running ksysguard, well, nothing changes, it's still running with errors. i
> include the screenshot. you can see at the bottom, ksysguard only shows
> number of processes, and missing average cpu usage, memory usage, etc. and
> in system load tab, the graph is not drawing at all. on previous comment, i
> also include output of ksysguard and journalctl. sorry for triple post, i
> have no idea how to attach multiple files here

Did you clean the $HOME/.local/share/ksysguard/ directory ?

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

[i18n] [Bug 376243] Várias traduções estão em pt-pt

2017-02-17 Thread Luiz Fernando Ranghetti
https://bugs.kde.org/show_bug.cgi?id=376243

Luiz Fernando Ranghetti  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||elchev...@opensuse.org

--- Comment #2 from Luiz Fernando Ranghetti  ---
Olá,

Procurando essas strings descobrimos (com a ajuda do pessoal do #kde-brasil)
que se tratam de strings sem tradução ainda, com isto o sistema usa pt-pt como
fallback, como por exemplo na "Configurar o Ecrã":

#: package/contents/ui/main.qml:558
#, fuzzy
#| msgid " Desktop"
msgid "Configure Desktop"
msgstr "Atualiza área de trabalho"

está como fuzzy, ou seja não traduzida

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

[krita] [Bug 376544] Filter masks are not considered while exporting

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376544

--- Comment #2 from pessio...@hotmail.it ---
Hi, it has the same problem, but I noticed that for both 3.1.2 and the nightly
you can resolve it by adding an empty level on the document..

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

[plasmashell] [Bug 376591] application menu: moving mouse cursor from submenu item to edge of main menu crashes plasmashell

2017-02-17 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=376591

--- Comment #1 from S. Christian Collins  ---
Created attachment 104080
  --> https://bugs.kde.org/attachment.cgi?id=104080=edit
video showing the bug

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

[plasmashell] [Bug 376591] New: application menu: moving mouse cursor from submenu item to edge of main menu crashes plasmashell

2017-02-17 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=376591

Bug ID: 376591
   Summary: application menu: moving mouse cursor from submenu
item to edge of main menu crashes plasmashell
   Product: plasmashell
   Version: 5.9.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: s_chriscoll...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.2)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.4.0-62-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
The easiest way to see what is happening is to watch the attached video.

I am able to get plasmashell to crash pretty consistenly using the "Application
Menu" style menu launcher by doing the following:
1. Hover the mouse cursor over a menu category that contains one or more
sub-menus.
2. Hover the sub-menu to see its contents.
3. Hover over the top application in that sub-menu.
4. Move the mouse up above the opened sub-menu, to the left and position the
cursor on top of the right edge of the main menu where the little arrows are.

Most of the time when I perform this maneuver, plasmashell crashes. There might
be other factors (position of menu entry, etc.) that affect how easy this is to
reproduce. I am also using a GeForce GTX 970 with the NVIDIA proprietary video
driver version 367.57.

Unfortunately, despite having plasma-workspace-dbg installed, the crash handler
complains that it can't find the debug symbols for plasmashell, so I'm not sure
how useful the backtrace will be.

The crash can be reproduced every time.

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

Thread 15 (Thread 0x7fbad2efd700 (LWP 13989)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbbb6a179fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x4474750) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x4474610,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fbbb9a3a47d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7fbbb9a3ad55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fbbb6a16b48 in QThreadPrivate::start (arg=0x4474590) at
thread/qthread_unix.cpp:368
#6  0x7fbbb58bc6ba in start_thread (arg=0x7fbad2efd700) at
pthread_create.c:333
#7  0x7fbbb632382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fbadd3f7700 (LWP 13988)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbbb6a179fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x30acb90) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x3032370,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fbbb9a3a47d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7fbbb9a3ad55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fbbb6a16b48 in QThreadPrivate::start (arg=0x30322f0) at
thread/qthread_unix.cpp:368
#6  0x7fbbb58bc6ba in start_thread (arg=0x7fbadd3f7700) at
pthread_create.c:333
#7  0x7fbbb632382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fbad3ffe700 (LWP 13945)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbbb6a179fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3d90970) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x3e87450,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fbbb9a3a47d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7fbbb9a3ad55 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fbbb6a16b48 in QThreadPrivate::start (arg=0x3e873d0) at
thread/qthread_unix.cpp:368
#6  0x7fbbb58bc6ba in start_thread (arg=0x7fbad3ffe700) at
pthread_create.c:333
#7  0x7fbbb632382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fbadcbf6700 (LWP 13944)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbbb6a179fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x3bf04e0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x3bf0320,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fbbb9a3a47d in ?? () from 

[klipper] [Bug 376590] New: Unable to paste but entry into klipper

2017-02-17 Thread BRULE Herman
https://bugs.kde.org/show_bug.cgi?id=376590

Bug ID: 376590
   Summary: Unable to paste but entry into klipper
   Product: klipper
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: alpha_one_...@first-world.info
  Target Milestone: ---

Hello,

I select a text into kwrite, ctrl c, close kwrite.
I open again kwrite: menu paste or ctrl v don't work. I need select another
entry into klipper and again my last entry to do it.
My options is:
[ ] Prevent empty clipboard
[X] Ignore images
[X] Ignore selection
I had change:
[ ] -> [X] Save clipboard contents on exit

Cheers,

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

[kmail2] [Bug 376589] Layout destroyed after clicking link with HiDPI

2017-02-17 Thread Thiago Macieira
https://bugs.kde.org/show_bug.cgi?id=376589

--- Comment #1 from Thiago Macieira  ---
Created attachment 104078
  --> https://bugs.kde.org/attachment.cgi?id=104078=edit
"Before" screenshot

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

[kmail2] [Bug 376589] Layout destroyed after clicking link with HiDPI

2017-02-17 Thread Thiago Macieira
https://bugs.kde.org/show_bug.cgi?id=376589

--- Comment #2 from Thiago Macieira  ---
Created attachment 104079
  --> https://bugs.kde.org/attachment.cgi?id=104079=edit
"After" screenshot

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

[kmail2] [Bug 376589] New: Layout destroyed after clicking link with HiDPI

2017-02-17 Thread Thiago Macieira
https://bugs.kde.org/show_bug.cgi?id=376589

Bug ID: 376589
   Summary: Layout destroyed after clicking link with HiDPI
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: thi...@kde.org
  Target Milestone: ---

When clicking a link in an email in KMail, the message view layout is destroyed
and cannot be recovered unless you close KMail's main window and open it again.
This happens for *every* link, but only happens on HiDPI screens
(QT_SCREEN_SCALE_FACTOR=2 or higher).

This has been happening since the switch to QtWebEngine. It has never worked
with it.

Steps to reproduce:
1) close kmail (killall kmail to be sure)
2) from a terminal, open kmail in HiDPI mode: QT_SCREEN_SCALE_FACTOR=2 kmail
3) select an email that has a web link
4) click it

Expected results:
Browser opens and KMail window remains as it was before clicking the link (see
"before" screenshot)

Actual results:
Browser opens, but KMail window layout is destroyed (see "after" screenshot).

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

  1   2   3   >