[Rocs] [Bug 367647] Unsupported compiler flags passed to Clang

2016-09-05 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367647

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/rocs
   ||/624a6bc2118a9224089f3a7ee6
   ||5e2993efc1dc1c
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 624a6bc2118a9224089f3a7ee65e2993efc1dc1c by Andreas Cord-Landwehr.
Committed on 05/09/2016 at 13:41.
Pushed by cordlandwehr into branch 'Applications/16.08'.

Use BOOST_MATH_DISABLE_FLOAT128 to avoid operator problem.

The use of -fext-numeric-literals apparently is not supported
by Clang. Use correct Boost define to avoid use of custom
literals.

M  +0-1CMakeLists.txt
M  +2-0libgraphtheory/modifiers/topology.h

http://commits.kde.org/rocs/624a6bc2118a9224089f3a7ee65e2993efc1dc1c

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


[kdevelop] [Bug 368270] New: Crash when pressing ALT + ENTER in assistant dialog

2016-09-05 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368270

Bug ID: 368270
   Summary: Crash when pressing ALT + ENTER in assistant dialog
   Product: kdevelop
   Version: 5.0.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: kdevelop (5.0.0)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
When the crash happend, I was pressing ALT + ENTER in the assistant dialog.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff683638940 (LWP 807))]

Thread 21 (Thread 0x7ff608a4b700 (LWP 1954)):
#0  0x7ff69767509f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff697356ee4 in QTWTF::TCMalloc_PageHeap::scavengerThread()
(this=0x7ff69743d1a0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7ff697356f29 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7ff69766f464 in start_thread (arg=0x7ff608a4b700) at
pthread_create.c:333
#4  0x7ff69ea7130d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7ff609a4d700 (LWP 859)):
#0  0x7ff69ea6819d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff69288439c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7ff604002e40, timeout=, context=0x7ff604000990) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7ff69288439c in g_main_context_iterate
(context=context@entry=0x7ff604000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7ff6928844ac in g_main_context_iteration (context=0x7ff604000990,
may_block=may_block@entry=1) at
/build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7ff69f88b29b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff6040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7ff69f8391ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff609a4cbf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7ff69f66f2ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#7  0x7ff69cb19b9f in KDevelop::CompletionWorkerThread::run()
(this=0x43a1780) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#8  0x7ff69f673bd9 in QThreadPrivate::start(void*) (arg=0x43a1780) at
thread/qthread_unix.cpp:343
#9  0x7ff69766f464 in start_thread (arg=0x7ff609a4d700) at
pthread_create.c:333
#10 0x7ff69ea7130d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7ff621ffb700 (LWP 853)):
#0  0x7ff69767509f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff69f67497b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x27deb30) at
thread/qwaitcondition_unix.cpp:143
#2  0x7ff69f67497b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x25a3560, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7ff69b9364e6 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x27dea40, th=0x7ff60c003020) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:594
#4  0x7ff69b9361bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x27dea40, th=0x7ff60c003020, threadWasBusy=false,
suspendIfInactive=false, justReturning=false) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:554
#5  0x7ff69b93ebe7 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x25d2d60, th=0x7ff60c003020, wasBusy=false) at
/opt/kde/src/frameworks/threadweaver/src/workinghardstate.cpp:66
#6  0x7ff69b936300 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x27dea40, th=0x7ff60c003020, wasBusy=false) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:568
#7  0x7ff69b93ecea in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x25d2d60, th=0x7ff60c003020, wasBusy=false) at
/opt/kde/src/frameworks/threadweaver/src/workinghardstate.cpp:73
#8  0x7ff69b936300 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool)
(this=0x27dea40, th=0x7ff60c003020, wasBusy=false) at

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

2016-08-16 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364044

--- Comment #11 from Andreas Cord-Landwehr  ---
Sorry for the late reply, had a long struggle with the kscreen kcm not starting
up correctly (finally turned out to be caused by a mix of loaded Qt libs with
different SO versions...).
Back to topic: I can still reproduce the issue with Plasma/5.7 branch. Will
next update to Plasma/5.8 and test again.

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


[kdevelop] [Bug 365773] New: Crash when clicking at context dialog on container

2016-07-17 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365773

Bug ID: 365773
   Summary: Crash when clicking at context dialog on container
   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: cordlandw...@kde.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
What I was doing when the application crashed:
- hover mouse over any type/variable/function declaration
- in the context dialog click at the containing type
-> Crash

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3f32867940 (LWP 27599))]

Thread 13 (Thread 0x7f3ecbe74700 (LWP 27672)):
#0  0x7f3f3f7e3c22 in g_main_context_check
(context=context@entry=0x7f3ebb80b3e0, max_priority=2147483647,
fds=fds@entry=0x7f3ebb372cb0, n_fds=n_fds@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3614
#1  0x7f3f3f7e4340 in g_main_context_iterate
(context=context@entry=0x7f3ebb80b3e0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3837
#2  0x7f3f3f7e44ac in g_main_context_iteration (context=0x7f3ebb80b3e0,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#3  0x7f3f4c7e129b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3eb9696540, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3f4c78f1ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3ecbe73bf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#5  0x7f3f4c5c52ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#6  0x7f3f49a711b5 in KDevelop::CompletionWorkerThread::run()
(this=0x5926bd0) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f3f4c5c9bd9 in QThreadPrivate::start(void*) (arg=0x5926bd0) at
thread/qthread_unix.cpp:343
#8  0x7f3f445cd464 in start_thread (arg=0x7f3ecbe74700) at
pthread_create.c:333
#9  0x7f3f4b9c830d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f3ed97b2700 (LWP 27644)):
#0  0x7f3f4b9bf19d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3f3f7e439c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f3ec41b7dc0, timeout=, context=0x7f3ec40008c0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f3f3f7e439c in g_main_context_iterate
(context=context@entry=0x7f3ec40008c0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f3f3f7e44ac in g_main_context_iteration (context=0x7f3ec40008c0,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f3f4c7e129b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3ec4003ce0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f3f4c78f1ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3ed97b1c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#6  0x7f3f4c5c52ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#7  0x7f3f4c5c9bd9 in QThreadPrivate::start(void*) (arg=0x7f3f5170d718
) at
thread/qthread_unix.cpp:343
#8  0x7f3f445cd464 in start_thread (arg=0x7f3ed97b2700) at
pthread_create.c:333
#9  0x7f3f4b9c830d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f3eda925700 (LWP 27639)):
#0  0x7f3f445d309f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3f4c5ca97b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x24871a0) at
thread/qwaitcondition_unix.cpp:143
#2  0x7f3f4c5ca97b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x230d270, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f3f4888b546 in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=0x24870b0, th=0x7f3ed4001e20) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:594
#4  0x7f3f4888b21f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x24870b0, th=0x7f3ed4001e20, threadWasBusy=true,
suspendIfInactive=false, justReturning=false) at
/opt/kde/src/frameworks/threadweaver/src/weaver.cpp:554
#5  0x7f3f48893c47 in

[kdevelop] [Bug 365766] Crash when stopping unit test that segfaulted [KDevelop::OutputExecuteJob]

2016-07-17 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365766

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/1d87fc630265792235
   ||4a6fc49e2ce0b1d0d1f918

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 1d87fc6302657922354a6fc49e2ce0b1d0d1f918 by Andreas Cord-Landwehr.
Committed on 17/07/2016 at 12:27.
Pushed by cordlandwehr into branch '5.0'.

Do not assert if process survives kill.

Summary:
If process survives kill, an error message is already printed to
indicate the problem. Since we cannot hope to kill the process,
gracefully handle this case.

Test Plan: Manual testing.

Reviewers: #kdevelop, brauch

Reviewed By: #kdevelop, brauch

Subscribers: brauch, kdevelop-devel

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

M  +10   -4outputview/outputexecutejob.cpp

http://commits.kde.org/kdevplatform/1d87fc6302657922354a6fc49e2ce0b1d0d1f918

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


[kdevelop] [Bug 365766] New: Crash when stopping unit test that segfaulted [KDevelop::OutputExecuteJob]

2016-07-17 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365766

Bug ID: 365766
   Summary: Crash when stopping unit test that segfaulted
[KDevelop::OutputExecuteJob]
   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: cordlandw...@kde.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.25.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
Steps to reproduce:
- start a unit unit that enters a gdb session due to eg. a segfault
- whilte gdb is still starting, stop that unit test
- the appended crash occurs

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6695d09940 (LWP 23883))]

Thread 14 (Thread 0x7f6646ee9700 (LWP 23965)):
#0  0x7f66a7a7509f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f66a7756ee4 in QTWTF::TCMalloc_PageHeap::scavengerThread()
(this=0x7f66a783d1a0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f66a7756f29 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f66a7a6f464 in start_thread (arg=0x7f6646ee9700) at
pthread_create.c:333
#4  0x7f66aee6930d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f664549a700 (LWP 23942)):
#0  0x7f66afa62a28 in QMutex::unlock() (__m2=,
__m1=std::memory_order_release, __p2=0x0, __p1=@0x7f66454999b0: 0x1,
this=0x455a5d0) at /usr/include/c++/5/bits/atomic_base.h:752
#1  0x7f66afa62a28 in QMutex::unlock() (__m=std::memory_order_release,
__p2=0x0, __p1=@0x7f66454999b0: 0x1, this=0x455a5d0) at
/usr/include/c++/5/atomic:475
#2  0x7f66afa62a28 in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=0x1, _q_value=...) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:174
#3  0x7f66afa62a28 in QMutex::unlock() (currentValue=,
newValue=0x0, expectedValue=, this=this@entry=0x455a5d0) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:261
#4  0x7f66afa62a28 in QMutex::unlock() (current=,
this=this@entry=0x455a5d0) at thread/qmutex.h:91
#5  0x7f66afa62a28 in QMutex::unlock() (this=this@entry=0x455a5d0) at
thread/qmutex.cpp:277
#6  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(this=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:144
#7  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(this=, __in_chrg=) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:138
#8  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(this=0x455a5a0) at
../../include/QtCore/5.7.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:254
#9  0x7f66afc81a3d in postEventSourcePrepare(GSource*, gint*)
(s=0x7f66303c5e00, timeout=timeout@entry=0x7f6645499a34) at
kernel/qeventdispatcher_glib.cpp:259
#10 0x7f66a2c8592d in g_main_context_prepare
(context=context@entry=0x7f6630086a60, priority=priority@entry=0x7f6645499ac0)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3442
#11 0x7f66a2c862cb in g_main_context_iterate
(context=context@entry=0x7f6630086a60, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#12 0x7f66a2c864ac in g_main_context_iteration (context=0x7f6630086a60,
may_block=may_block@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#13 0x7f66afc8229b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f6630a21220, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#14 0x7f66afc301ca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6645499bf0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:210
#15 0x7f66afa662ac in QThread::exec() (this=) at
thread/qthread.cpp:511
#16 0x7f66acf121ef in KDevelop::CompletionWorkerThread::run()
(this=0x455c8a0) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#17 0x7f66afa6abd9 in QThreadPrivate::start(void*) (arg=0x455c8a0) at
thread/qthread_unix.cpp:343
#18 0x7f66a7a6f464 in start_thread (arg=0x7f664549a700) at
pthread_create.c:333
#19 0x7f66aee6930d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f66466e8700 (LWP 23914)):
#0  0x7f66aee5c17d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f66a2cc9740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f66466e7a90, __fd=) at

[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

2016-07-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365040

Andreas Cord-Landwehr  changed:

   What|Removed |Added

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

--- Comment #3 from Andreas Cord-Landwehr  ---
After some major cleanup of my .config and .local directories (grown since the
first Qt5 based pre-alpha versions), I cannot reproduce this issue anymore. So,
I will close it.

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


[kdevelop] [Bug 235283] Crash on deleting folder

2016-07-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=235283

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Andreas Cord-Landwehr  ---
Did not see this problem during the last couple of years.
Let's close it :)

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


[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

2016-07-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364044

--- Comment #7 from Andreas Cord-Landwehr  ---
I can still reproduce this issue with this patch. Do you need updated
information?
My Qt now is 5.7.

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


[frameworks-baloo] [Bug 361903] Assert "DocumentUrlDB::del"

2016-07-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361903

Andreas Cord-Landwehr  changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr  ---
Fixed by Pinak during the last Randa sprint.

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


[KScreen] [Bug 365040] kscreen KCM cannot be used if KSCREEN_BACKEND is not set

2016-07-04 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365040

--- Comment #2 from Andreas Cord-Landwehr  ---
You are right; I looked at the wrong code location. Here is a probably more
verbose output. I now generated a backtrace for getting the debug message:

kcmshell5(30793)/(kscreen) KScreen::BackendManager::startBackend: starting
external backend launcher for ""

At this point, I have (added an assert in
"/opt/kde/src/kde/workspace/libkscreen/src/backendmanager.cpp", line=291):
#5  0x7fffda2f3bc6 in KScreen::BackendManager::startBackend(QString const&,
QMap const&) (this=0x6af270, backend=..., arguments=...)
at /opt/kde/src/kde/workspace/libkscreen/src/backendmanager.cpp:291
#6  0x7fffda2f3aca in KScreen::BackendManager::requestBackend()
(this=0x6af270) at
/opt/kde/src/kde/workspace/libkscreen/src/backendmanager.cpp:276
#7  0x7fffda2fe5cb in KScreen::ConfigOperationPrivate::requestBackend()
(this=0x9265f0) at
/opt/kde/src/kde/workspace/libkscreen/src/configoperation.cpp:45
#8  0x7fffda30019e in KScreen::GetConfigOperation::start() (this=0x92bfd0)
at /opt/kde/src/kde/workspace/libkscreen/src/getconfigoperation.cpp:178
#9  0x7fffda315dcd in
KScreen::ConfigOperation::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=0x92bfd0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x92bd10)
at /opt/kde/build/kde/workspace/libkscreen/src/moc_configoperation.cpp:81
#10 0x74d8ad07 in QMetaCallEvent::placeMetaCall(QObject*)
(this=0x93afb0, object=0x92bfd0) at kernel/qobject.cpp:495
#11 0x74d8bda0 in QObject::event(QEvent*) (this=0x92bfd0, e=0x93afb0)
at kernel/qobject.cpp:1256
#12 0x7594a4f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x61a250, receiver=0x92bfd0, e=0x93afb0) at kernel/qapplication.cpp:3804
#13 0x759478bd in QApplication::notify(QObject*, QEvent*)
(this=0x7fffd1f0, receiver=0x92bfd0, e=0x93afb0) at
kernel/qapplication.cpp:3163
#14 0x74d51bfa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x92bfd0, event=0x93afb0) at kernel/qcoreapplication.cpp:1015
#15 0x74d55c30 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=0x92bfd0, event=0x93afb0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#16 0x74d52fe2 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x6190d0) at
kernel/qcoreapplication.cpp:1650
#17 0x74d52962 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1508
#18 0x74dcbb2c in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x672fb0) at kernel/qeventdispatcher_glib.cpp:270
#19 0x7fffed56a1a7 in g_main_context_dispatch (context=0x7fffdc0016f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3154
#20 0x7fffed56a1a7 in g_main_context_dispatch
(context=context@entry=0x7fffdc0016f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3769
#21 0x7fffed56a400 in g_main_context_iterate
(context=context@entry=0x7fffdc0016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3840
---Type  to continue, or q  to quit---
#22 0x7fffed56a4ac in g_main_context_iteration (context=0x7fffdc0016f0,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#23 0x74dcc305 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x67ceb0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#24 0x7fffe78cce86 in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x67ceb0, flags=...) at eventdispatchers/qeventdispatcher_glib.cpp:115
#25 0x74d4e570 in
QEventLoop::processEvents(QFlags)
(this=0x7fffd050, flags=...) at kernel/qeventloop.cpp:128
#26 0x74d4e86c in
QEventLoop::exec(QFlags) (this=0x7fffd050,
flags=...) at kernel/qeventloop.cpp:204
#27 0x74d52344 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1285
#28 0x7517d598 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1607
#29 0x759472a1 in QApplication::exec() () at
kernel/qapplication.cpp:2979
#30 0x77bd4210 in kdemain(int, char**) (_argc=2, _argv=0x7fffdb18)
at /opt/kde/src/kde/workspace/kde-cli-tools/kcmshell/main.cpp:294
#31 0x004009a8 in main(int, char**) (argc=2, argv=0x7fffdb18) at
/opt/kde/build/kde/workspace/kde-cli-tools/kcmshell/kcmshell5_dummy.cpp:3

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


[KScreen] [Bug 365040] New: kscreen KCM cannot be used if KSCREEN_BACKEND is not set

2016-07-03 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365040

Bug ID: 365040
   Summary: kscreen KCM cannot be used if KSCREEN_BACKEND is not
set
   Product: KScreen
   Version: git
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: kcm
  Assignee: se...@kde.org
  Reporter: cordlandw...@kde.org

If KSCREEN_BACKEND is not set, the KCM only shows "No kscreen backend found.
Please check your kscreen installation." A workaround is explicitly setting the
variable to e.g. "QScreen" or "XRandR".
Line 137 in libkscreen/src/configoperation.cpp explicitly asks for the value of
this env variable and has no fallback code if it is not set.
However, kscreen-doctor tells me the correct preferred backend for my system:

kscreen-doctor -b
Environment: 
  * KSCREEN_BACKEND is: [not set]
  * KSCREEN_BACKEND_INPROCESS : [not set]
Preferred KScreen backend : KSC_XRandR.so
Available KScreen backends:
  * KSC_Fake.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_Fake.so
  * KSC_KWayland.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_KWayland.so
  * KSC_QScreen.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_QScreen.so
  * KSC_XRandR.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_XRandR.so
  * KSC_XRandR11.so:
/opt/kde/install/kf5/lib/x86_64-linux-gnu/plugins/kf5/kscreen/KSC_XRandR11.so

Output of kscreen-console bug:
cordlandwehr@weatherwax:~/.local5$ kscreen-console bug
kscreen-console(26229)/(default) main: START: Requesting Config
kscreen-console(26229)/(kscreen) KScreen::BackendManager::startBackend:
starting external backend launcher for ""
kscreen-console(26229)/(default) configReceived: Received config. Took 278
milliseconds

xrandr --verbose==
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected 1920x1080+0+0 (0x4d) normal (normal left inverted right x axis y
axis) 309mm x 173mm
Identifier: 0x43
Timestamp:  66102451
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
BACKLIGHT: 426 
range: (0, 851)
Backlight: 426 
range: (0, 851)
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4d) 141.000MHz -HSync -VSync *current +preferred
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz
  1920x1080 (0xee) 138.500MHz +HSync -VSync
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz
v: height 1080 start 1083 end 1088 total    clock  59.93Hz
  1680x1050 (0xef) 146.250MHz -HSync +VSync
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz
  1680x1050 (0xf0) 119.000MHz +HSync -VSync
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz
  1600x1024 (0xf1) 103.125MHz +HSync +VSync
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz
  1400x1050 (0xf2) 122.000MHz +HSync +VSync
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz
  1600x900 (0xf3) 118.997MHz -HSync +VSync
h: width  1600 start 1696 end 1864 total 2128 skew0 clock  55.92KHz
v: height  900 start  901 end  904 total  932   clock  60.00Hz
  1280x1024 (0xf4) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1440x900 (0xf5) 106.500MHz -HSync +VSync
h: width  

[parley] [Bug 362799] can't write export file

2016-07-02 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362799

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||cordlandw...@kde.org
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Andreas Cord-Landwehr  ---
Could you provide the exact steps how you try to export your practice results?
E.g. the exact menu entry/button you use?

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


[parley] [Bug 364211] Parley crashes after creating a new file - everytime

2016-07-02 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364211

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||cordlandw...@kde.org
 Resolution|--- |WORKSFORME

--- Comment #2 from Andreas Cord-Landwehr  ---
Without a backtrace, unfortunately it is not possible to investigate this
problem. Following the given steps, I cannot reproduce the reported issue.
However, I *think* this problem is fixed (there is a recent fix). But this is
impossible to say without looking at a backtrace. Hence, I am closing this
report for now. If you can provide a backtrace as described in the above given
link, please feel free to re-open it.

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


[kmail2] [Bug 364721] KMail Crash every time I press "Enter" for completing a mail recipient.

2016-06-25 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364721

--- Comment #2 from Andreas Cord-Landwehr  ---
I can still reproduce it with yesterday night's master branch (updated
kdesrc-build groups kde-pimlibs and kde-pim; restarted Akonadi).

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


[kmail2] [Bug 364721] New: KMail Crash every time I press "Enter" for completing a mail recipient.

2016-06-24 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364721

Bug ID: 364721
   Summary: KMail Crash every time I press "Enter" for completing
a mail recipient.
   Product: kmail2
   Version: Git (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: cordlandw...@kde.org

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

As explained in the title: KMail Crash every time I press "Enter" for
completing a mail recipient.

(I am pasting only the problematic thread)

Thread 1 (Thread 0x7f0b08f4d940 (LWP 7992)):
[KCrash Handler]
#6  0x7f0b25457458 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f0b254588da in __GI_abort () at abort.c:89
#8  0x7f0b2610681e in qt_message_fatal(QtMsgType, QMessageLogContext
const&, QString const&) (context=..., message=...) at global/qlogging.cpp:1648
#9  0x7f0b26102cd6 in QMessageLogger::fatal(char const*, ...) const
(this=0x7ffce93e9570, msg=0x7f0b26435530 "ASSERT: \"%s\" in file %s, line %d")
at global/qlogging.cpp:790
#10 0x7f0b260fbe4e in qt_assert(char const*, char const*, int)
(assertion=0x7f0b292b6ace "!mReadingFinished", file=0x7f0b292b6a20
"/opt/kde/src/kde/pim/akonadi/src/core/jobs/job.cpp", line=69) at
global/qglobal.cpp:2999
#11 0x7f0b29224046 in Akonadi::JobPrivate::handleResponse(long long,
Akonadi::Protocol::Command const&) (this=0x63c8c20, tag=16, response=...) at
/opt/kde/src/kde/pim/akonadi/src/core/jobs/job.cpp:69
#12 0x7f0b291e5932 in Akonadi::SessionPrivate::handleCommand(long long,
Akonadi::Protocol::Command const&) (this=0x754abf0, tag=16, cmd=...) at
/opt/kde/src/kde/pim/akonadi/src/core/session.cpp:143
#13 0x7f0b291e7655 in Akonadi::Session::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x753f050,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7f0a90003090) at
/opt/kde/build/kde/pim/akonadi/src/core/moc_session.cpp:118
#14 0x7f0b26386d07 in QMetaCallEvent::placeMetaCall(QObject*)
(this=0x7f0a90002630, object=0x753f050) at kernel/qobject.cpp:495
#15 0x7f0b26387da0 in QObject::event(QEvent*) (this=0x753f050,
e=0x7f0a90002630) at kernel/qobject.cpp:1256
#16 0x7f0b271104f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x2196f80, receiver=0x753f050, e=0x7f0a90002630) at
kernel/qapplication.cpp:3804
#17 0x7f0b2710d8bd in QApplication::notify(QObject*, QEvent*)
(this=0x7ffce93ea6a0, receiver=0x753f050, e=0x7f0a90002630) at
kernel/qapplication.cpp:3163
#18 0x7f0b2634dbfa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x753f050, event=0x7f0a90002630) at kernel/qcoreapplication.cpp:1015
#19 0x7f0b26351c30 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=0x753f050, event=0x7f0a90002630) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#20 0x7f0b2634efe2 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x21905d0) at
kernel/qcoreapplication.cpp:1650
#21 0x7f0b2634e962 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1508
#22 0x7f0b263c7b2c in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x21e2df0) at kernel/qeventdispatcher_glib.cpp:270
#23 0x7f0b148e61a7 in g_main_context_dispatch (context=0x7f0b16f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3154
#24 0x7f0b148e61a7 in g_main_context_dispatch
(context=context@entry=0x7f0b16f0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3769
#25 0x7f0b148e6400 in g_main_context_iterate
(context=context@entry=0x7f0b16f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3840
#26 0x7f0b148e64ac in g_main_context_iteration (context=0x7f0b16f0,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#27 0x7f0b263c8305 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x21f30c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#28 0x7f0b08cf2e86 in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x21f30c0, flags=...) at eventdispatchers/qeventdispatcher_glib.cpp:115
#29 0x7f0b2634a570 in
QEventLoop::processEvents(QFlags)
(this=0x7ffce93ea5b0, flags=...) at kernel/qeventloop.cpp:128
#30 0x7f0b2634a86c in
QEventLoop::exec(QFlags) (this=0x7ffce93ea5b0,
flags=...) at kernel/qeventloop.cpp:204
#31 0x7f0b2634e344 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1285
#32 0x7f0b26943598 in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1607
#33 0x7f0b2710d2a1 in QApplication::exec() () at
kernel/qapplication.cpp:2979
#34 0x004058f8 in main(int, char**) (argc=1, argv=0x7ffce93ead28) at

[Artikulate] [Bug 364718] hangs when launched - no GUI appears

2016-06-24 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364718

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Andreas Cord-Landwehr  ---
I am afraid, this is a packaging problem (though one that is very hard to fix):
- the dependency QtGStreamer is linked against GStreamer 1.x API
- the dependency QtMultimedia is linked against GStreamer 0.10 API
Both GStreamer API versions are mutual exclusive in a program and cause it to
stop/deadlock. Your distribution would have to update the QtMultimedia
dependency to 1.x API. Yet that requires a big patch and a considerable amount
of work (I did this for the Debian packages). And as Qt4 slowly comes to end of
its life, I am not sure if your distribution want to invest that time.
Moreover, you use Artikulate still from a KDE SC 4 release. Newer versions
depending on Qt5 do not have this problem anymore, since we can avoid using
both at the same time.

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


[Artikulate] [Bug 364718] hangs when launched - no GUI appears

2016-06-24 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364718

--- Comment #2 from Andreas Cord-Landwehr  ---
Could you paste the output of "ldd `whereis artikulate`"?

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


[kdevelop] [Bug 317013] "Remove" and "rename" context menu items in "Project" toolview doesn't work

2016-06-18 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=317013

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME
 CC||cordlandw...@kde.org

--- Comment #7 from Andreas Cord-Landwehr  ---
Closing because of inactivity. If this is still a problem, please reopen.

I can remember this problem to exist in earlier version of the KF5 port, but
also cannot remember it anymore.

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


[kdevelop] [Bug 361068] Icon for Kdevelop

2016-06-18 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361068

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Andreas Cord-Landwehr  ---
Could you check that that the breeze icon package is installed?

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


[kdevelop] [Bug 364145] Crash in QML Parser while parsing QtDeclarative [DeclarationBuilder::closeAndAssignType]

2016-06-15 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364145

--- Comment #1 from Andreas Cord-Landwehr  ---
Created attachment 99520
  --> https://bugs.kde.org/attachment.cgi?id=99520=edit
The problematic file causing the assert

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


[krunner] [Bug 364342] New: KRunner crash by Akonadi's PIMContactsRunner

2016-06-15 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364342

Bug ID: 364342
   Summary: KRunner crash by Akonadi's PIMContactsRunner
   Product: krunner
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: cordlandw...@kde.org

Application: krunner (5.6.90)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
Crash occured when by opening KRunner.
See backtrace, it directly tells the reason.

-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fa5920b1900 (LWP 1521))]

Thread 13 (Thread 0x7fa58ed8a700 (LWP 1534)):
#0  0x7fa5a0c7adcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa59fabd382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fa58ed89b80) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7fa59fabd382 in _xcb_conn_wait (c=c@entry=0x218cb40,
cond=cond@entry=0x218cb80, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7fa59fabeff7 in xcb_wait_for_event (c=0x218cb40) at
../../src/xcb_in.c:693
#4  0x7fa591e0dadd in QXcbEventReader::run() (this=0x21971a0) at
qxcbconnection.cpp:1325
#5  0x7fa5a18d42e5 in QThreadPrivate::start(void*) (arg=0x21971a0) at
thread/qthread_unix.cpp:340
#6  0x7fa59d1e5454 in start_thread (arg=0x7fa58ed8a700) at
pthread_create.c:334
#7  0x7fa5a0c83e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fa58d444700 (LWP 1539)):
#0  0x7fa5990ab8e0 in g_main_context_prepare
(context=context@entry=0x7fa58990, priority=priority@entry=0x7fa58d443a80)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3424
#1  0x7fa5990ac2cb in g_main_context_iterate
(context=context@entry=0x7fa58990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#2  0x7fa5990ac4ac in g_main_context_iteration (context=0x7fa58990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#3  0x7fa5a1b80334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa588c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7fa5a1b02570 in
QEventLoop::processEvents(QFlags)
(this=0x7fa58d443c30, flags=...) at kernel/qeventloop.cpp:128
#5  0x7fa5a1b0286c in
QEventLoop::exec(QFlags) (this=0x7fa58d443c30,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fa5a18cc276 in QThread::exec() (this=0x7fa5a35f05e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#7  0x7fa5a3556860 in QDBusConnectionManager::run() (this=0x7fa5a35f05e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#8  0x7fa5a18d42e5 in QThreadPrivate::start(void*) (arg=0x7fa5a35f05e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#9  0x7fa59d1e5454 in start_thread (arg=0x7fa58d444700) at
pthread_create.c:334
#10 0x7fa5a0c83e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fa586b27700 (LWP 1562)):
#0  0x7fa5a0c7adcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa5990ac39c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fa57c002e70, timeout=, context=0x7fa57c000990) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7fa5990ac39c in g_main_context_iterate
(context=context@entry=0x7fa57c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7fa5990ac4ac in g_main_context_iteration (context=0x7fa57c000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fa5a1b80334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa57c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7fa5a1b02570 in
QEventLoop::processEvents(QFlags)
(this=0x7fa586b26c60, flags=...) at kernel/qeventloop.cpp:128
#6  0x7fa5a1b0286c in
QEventLoop::exec(QFlags) (this=0x7fa586b26c60,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7fa5a18cc276 in QThread::exec() (this=0x24210c0) at
thread/qthread.cpp:504
#8  0x7fa5a4350487 in QQmlThreadPrivate::run() (this=0x24210c0) at
qml/ftw/qqmlthread.cpp:141
#9  0x7fa5a18d42e5 in QThreadPrivate::start(void*) (arg=0x24210c0) at
thread/qthread_unix.cpp:340
#10 0x7fa59d1e5454 in start_thread (arg=0x7fa586b27700) at
pthread_create.c:334

[kdevelop] [Bug 364317] Crash when executing multiple tests

2016-06-15 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364317

Andreas Cord-Landwehr  changed:

   What|Removed |Added

Version|unspecified |git master
Summary|Crash when executing|Crash when executing
   |multiple tests (master  |multiple tests
   |branch) |

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


[kdevelop] [Bug 363931] Crash in CMake Background Parser [CMakeFunctionArgument::CMakeFunctionArgument, DeclarationBuilder::startVisiting]

2016-06-15 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363931

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Andreas Cord-Landwehr  ---
Daniel, can you retest with current master? The cmake parsing crash should be
fixed with b4263571146bab54459dd0aa122fc5dc604705d5. If not, please feel free
to re-open.

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


[kdevelop] [Bug 364317] New: Crash when executing multiple tests (master branch)

2016-06-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364317

Bug ID: 364317
   Summary: Crash when executing multiple tests (master branch)
   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: cordlandw...@kde.org

Application: kdevelop (4.90.92)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I started to run multiple unit tests from the ctest plugin at once (by run all
tests). Several popups where displayed that a unit test was already running,
asking to terminate a test.
When I clicked "kill", this crash appeared.

It is reproduceable.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4d13129940 (LWP 18344))]

Thread 18 (Thread 0x7f4d0eff1700 (LWP 18346)):
#0  0x7f4d2d398dcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4d1fc1e39c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4da580, timeout=, context=0x7f4d0990) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7f4d1fc1e39c in g_main_context_iterate
(context=context@entry=0x7f4d0990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7f4d1fc1e4ac in g_main_context_iteration (context=0x7f4d0990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7f4d2e25d334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4d08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f4d2e1df570 in
QEventLoop::processEvents(QFlags)
(this=0x7f4d0eff0bf0, flags=...) at kernel/qeventloop.cpp:128
#6  0x7f4d2e1df86c in
QEventLoop::exec(QFlags) (this=0x7f4d0eff0bf0,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f4d2dfa9276 in QThread::exec() (this=0x7f4d351b65e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#8  0x7f4d3511c860 in QDBusConnectionManager::run() (this=0x7f4d351b65e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#9  0x7f4d2dfb12e5 in QThreadPrivate::start(void*) (arg=0x7f4d351b65e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#10 0x7f4d249a0454 in start_thread (arg=0x7f4d0eff1700) at
pthread_create.c:334
#11 0x7f4d2d3a1e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f4cfb26b700 (LWP 18348)):
#0  0x7f4d249a63f8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f4d2dfb29d9 in QWaitConditionPrivate::wait_relative(unsigned long)
(this=0x3db30a0, time=1000) at thread/qwaitcondition_unix.cpp:126
#2  0x7f4d2dfb2a06 in QWaitConditionPrivate::wait(unsigned long)
(this=0x3db30a0, time=1000) at thread/qwaitcondition_unix.cpp:134
#3  0x7f4d2dfb27f5 in QWaitCondition::wait(QMutex*, unsigned long)
(this=0x3db0c88, mutex=0x3db0c90, time=1000) at
thread/qwaitcondition_unix.cpp:208
#4  0x7f4d2b2f60c3 in KDevelop::DUChainPrivate::CleanupThread::run()
(this=0x3db0c70) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#5  0x7f4d2dfb12e5 in QThreadPrivate::start(void*) (arg=0x3db0c70) at
thread/qthread_unix.cpp:340
#6  0x7f4d249a0454 in start_thread (arg=0x7f4cfb26b700) at
pthread_create.c:334
#7  0x7f4d2d3a1e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f4cf8a7b700 (LWP 18350)):
#0  0x7f4d2dfa5ea9 in
std::atomic::compare_exchange_strong(QMutexData*&, QMutexData*,
std::memory_order) (__m2=std::memory_order_acquire,
__m1=std::memory_order_acquire, __p2=0x1, __p1=@0x7f4cf8a7a870: 0x0,
this=0x45fe178) at /usr/include/c++/5/bits/atomic_base.h:752
#1  0x7f4d2dfa5ea9 in
std::atomic::compare_exchange_strong(QMutexData*&, QMutexData*,
std::memory_order) (this=0x45fe178, __p1=@0x7f4cf8a7a870: 0x0, __p2=0x1,
__m=std::memory_order_acquire) at /usr/include/c++/5/atomic:475
#2  0x7f4d2dfa5cbf in
QAtomicOps::testAndSetAcquire(std::atomic&,
QMutexData*, QMutexData*, QMutexData**) (_q_value=..., expectedValue=0x0,
newValue=0x1, currentValue=0x7f4cf8a7a908) at
../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:158
#3  0x7f4d2dfa5b9a in
QBasicAtomicPointer::testAndSetAcquire(QMutexData*, QMutexData*,
QMutexData*&) (this=0x45fe178, 

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

2016-06-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364044

--- Comment #5 from Andreas Cord-Landwehr  ---
Via kickoff -> Leave -> Suspend

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


[kdevelop] [Bug 364145] New: Crash in QML Parser while parsing QtDeclarative

2016-06-09 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364145

Bug ID: 364145
   Summary: Crash in QML Parser while parsing QtDeclarative
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fe6525b88c0 (LWP 11669))]

Thread 10 (Thread 0x7fe633307700 (LWP 11670)):
#0  0x7fe64ea72e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe6413c6c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fe6413c88d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fe6342a32c9 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#4  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe647c436fa in start_thread (arg=0x7fe633307700) at
pthread_create.c:333
#6  0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fe61f736700 (LWP 11672)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fe64f168598 in QWaitCondition::wait(QMutex*, unsigned long) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#2  0x7fe64c837958 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x31fcb60) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#3  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7fe647c436fa in start_thread (arg=0x7fe61f736700) at
pthread_create.c:333
#5  0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fe615a1f700 (LWP 11681)):
#0  __libc_disable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:98
#1  0x7fe64ea72e99 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7fe64674131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe64674142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe64f3aaa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe64f353212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7fe64f1627bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7fe64c1dd0f5 in ?? () from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Qml.so.5
#8  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#9  0x7fe647c436fa in start_thread (arg=0x7fe615a1f700) at
pthread_create.c:333
#10 0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fe6293f4700 (LWP 11693)):
#0  0x7fe646785a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe6467408a0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe64674124b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe64674142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe64f3aaa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe64f353212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7fe64f1627bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7fe647c436fa in start_thread (arg=0x7fe6293f4700) at
pthread_create.c:333
#9  0x7fe64ea7eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fe60d6a3700 (LWP 11697)):
#0  0x7fe646785a49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe646741418 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe64f3aaa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#3  0x7fe64f353212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7fe64f1627bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7fe64c99c27c in KDevelop::CompletionWorkerThread::run
(this=0x2477bc0) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#6  0x7fe64f16762f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7fe647c436fa in start_thread (arg=0x7fe60d6a3700) at

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

2016-06-08 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364044

--- Comment #2 from Andreas Cord-Landwehr  ---
Hi Sebas, restarting kded5 makes no change when I am in the state after
resuming on one monitor does not get a signal.

Output of kscreen-console bug:

cordlandwehr@weatherwax:/tmp$ kscreen-console bug
kscreen-console(30373)/(default) main: START: Requesting Config
kscreen-console(30373)/(kscreen) KScreen::BackendManager::startBackend:
starting external backend launcher for ""
kscreen-console(30373)/(default) configReceived: Received config. Took 47
milliseconds

xrandr --verbose==
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (0x4d) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x43
Timestamp:  131887559
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
BACKLIGHT: 426 
range: (0, 851)
Backlight: 426 
range: (0, 851)
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4d) 141.000MHz -HSync -VSync *current +preferred 
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz 
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz  
  1920x1080 (0xee) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0xef) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0xf0) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0xf1) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0xf2) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz
  1600x900 (0xf3) 118.997MHz -HSync +VSync
h: width  1600 start 1696 end 1864 total 2128 skew0 clock  55.92KHz
v: height  900 start  901 end  904 total  932   clock  60.00Hz
  1280x1024 (0xf4) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1440x900 (0xf5) 106.500MHz -HSync +VSync
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz
v: height  900 start  903 end  909 total  934   clock  59.89Hz
  1280x960 (0xf6) 108.000MHz +HSync +VSync
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz
v: height  960 start  961 end  964 total 1000   clock  60.00Hz
  1368x768 (0xf7) 85.860MHz -HSync +VSync
h: width  1368 start 1440 end 1584 total 1800 skew0 clock  47.70KHz
v: height  768 start  769 end  772 total  795   clock  60.00Hz
  1360x768 (0xf8) 84.750MHz -HSync +VSync
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz
v: height  768 start  771 end  781 total  798   clock  59.80Hz
  1360x768 (0xf9) 72.000MHz +HSync -VSync
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0xfa) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: height  864 start 

[frameworks-knewstuff] [Bug 340111] Get new themes/icons/styles fails with 'Network Error: (6)' message

2016-06-07 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=340111

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 CC||cordlandw...@kde.org

--- Comment #8 from Andreas Cord-Landwehr  ---
Hi Xavier, is the problem still present?

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


[frameworks-knewstuff] [Bug 342172] System Settings Add-On Installer Fails

2016-06-07 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=342172

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||cordlandw...@kde.org

--- Comment #9 from Andreas Cord-Landwehr  ---
Can you try to disable the network cache as explained in
https://bugs.kde.org/show_bug.cgi?id=348049 ?
It's possible that we have a duplicate bug report here.

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


[KScreen] [Bug 364044] New: Second screen in docking station keeps black after suspend

2016-06-07 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364044

Bug ID: 364044
   Summary: Second screen in docking station keeps black after
suspend
   Product: KScreen
   Version: git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: cordlandw...@kde.org

On my Lenovo Pro docking stations, I have one additional monitor connected.
After setting the laptop screen as primary and the additional screen as an
extended screen, I suspend the laptop.
When resuming the session, the laptop monitor is shown correctly. Yet the
second monitor says "no signal", even if kscreen tells me that it is enabled
and working.

The workaround to make the second monitor work again is: Disable the monitor in
kscreen, apply this, enabled the monitor again, apply again.

Reproducible: Always

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


[dolphin] [Bug 363982] New: QVector out of range access in kitemlistviewaccessible.cpp

2016-06-05 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363982

Bug ID: 363982
   Summary: QVector out of range access in
kitemlistviewaccessible.cpp
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

I got the following crash on my current Git-master version of dolphin:

Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb735da1940 (LWP 21360))]

Thread 4 (Thread 0x7fb732663700 (LWP 21363)):
#0  0x7fb742f1fdcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb73ed46382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fb732662b40) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7fb73ed46382 in _xcb_conn_wait (c=c@entry=0xa5d8a0,
cond=cond@entry=0xa5d8e0, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7fb73ed47ff7 in xcb_wait_for_event (c=0xa5d8a0) at
../../src/xcb_in.c:693
#4  0x7fb735afdadd in QXcbEventReader::run() (this=0xa67f70) at
qxcbconnection.cpp:1325
#5  0x7fb743b782e5 in QThreadPrivate::start(void*) (arg=0xa67f70) at
thread/qthread_unix.cpp:340
#6  0x7fb74023f454 in start_thread (arg=0x7fb732663700) at
pthread_create.c:334
#7  0x7fb742f28e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fb731283700 (LWP 21364)):
#0  0x7fb743b491de in QMutexLocker::QMutexLocker(QBasicMutex*)
(this=0x7fb731282920, m=0xaaa7a8) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:129
#1  0x7fb743e20aae in QThreadData::canWaitLocked() (this=0xaaa780) at
../../include/QtCore/5.6.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:247
#2  0x7fb743e23a6d in postEventSourcePrepare(GSource*, gint*)
(s=0x7fb7240012d0, timeout=0x7fb7312829b4) at
kernel/qeventdispatcher_glib.cpp:253
#3  0x7fb73b41092d in g_main_context_prepare
(context=context@entry=0x7fb724000990, priority=priority@entry=0x7fb731282a40)
at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3442
#4  0x7fb73b4112cb in g_main_context_iterate
(context=context@entry=0x7fb724000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3820
#5  0x7fb73b4114ac in g_main_context_iteration (context=0x7fb724000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x7fb743e24334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb7240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#7  0x7fb743da6570 in
QEventLoop::processEvents(QFlags)
(this=0x7fb731282bf0, flags=...) at kernel/qeventloop.cpp:128
#8  0x7fb743da686c in
QEventLoop::exec(QFlags) (this=0x7fb731282bf0,
flags=...) at kernel/qeventloop.cpp:204
#9  0x7fb743b70276 in QThread::exec() (this=0x7fb7441725e0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#10 0x7fb7440d8860 in QDBusConnectionManager::run() (this=0x7fb7441725e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#11 0x7fb743b782e5 in QThreadPrivate::start(void*) (arg=0x7fb7441725e0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#12 0x7fb74023f454 in start_thread (arg=0x7fb731283700) at
pthread_create.c:334
#13 0x7fb742f28e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb7238c3700 (LWP 21365)):
#0  0x7fb742f1bdad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb73b454740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fb7238c29a0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fb73b454740 in g_wakeup_acknowledge (wakeup=0x7fb7240025a0) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gwakeup.c:210
#3  0x7fb73b410e84 in g_main_context_check
(context=context@entry=0x7fb71c000990, max_priority=2147483647,
fds=fds@entry=0x7fb71c002e20, n_fds=n_fds@entry=1) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3632
#4  0x7fb73b411340 in g_main_context_iterate
(context=context@entry=0x7fb71c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3837
#5  0x7fb73b4114ac in g_main_context_iteration (context=0x7fb71c000990,
may_block=1) at /build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x7fb743e24334 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb71c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#7  0x7fb743da6570 in
QEventLoop::processEvents(QFlags)
(this=0x7fb7238c2c20, flags=...) at kernel/qeventloop.cpp:128
#8  0x7fb743da686c in

[kdevelop] [Bug 363713] Crash in QML Parser

2016-06-02 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363713

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||platform/6e56496997feebee5e
   ||3bde86c9b4823125156f46
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/46d2612955c8f390a7
   ||f657f1e7b257b51a7bd6c9
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 6e56496997feebee5e3bde86c9b4823125156f46 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 17:23.
Pushed by cordlandwehr into branch '5.0'.

Fix declaration name access if not fully parsed

Summary:
Fixes the crash in KDE bug #363713 that is caused by requesting code
completion on a not fully parsed QML file. For details, please see
backtrace in bug report.

Reviewers: mwolff, #kdevelop, kfunk

Reviewed By: #kdevelop, kfunk

Subscribers: kfunk, kdevelop-devel

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


http://commits.kde.org/kdevplatform/6e56496997feebee5e3bde86c9b4823125156f46

--- Comment #2 from Andreas Cord-Landwehr  ---
Git commit 46d2612955c8f390a7f657f1e7b257b51a7bd6c9 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:22.
Pushed by cordlandwehr into branch '5.0'.

Fix declaration name access if not fully parsed

Fixes the crash in KDE bug #363713 that is caused by requesting code
completion on a not fully parsed file. For details, please see
backtrace in bug report.

M  +3-0language/codecompletion/normaldeclarationcompletionitem.cpp

http://commits.kde.org/kdevplatform/46d2612955c8f390a7f657f1e7b257b51a7bd6c9

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


[kdevelop] [Bug 363707] Assert when parsing project

2016-06-01 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363707

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/b4263571146bab54459dd0
   ||aa122fc5dc604705d5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/bef8072e620ecaac9cdaf2
   ||7c1996167caa7f75b5
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr  ---
Git commit b4263571146bab54459dd0aa122fc5dc604705d5 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 05:13.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Summary:
Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

Reviewers: apol, #kdevelop

Reviewed By: apol, #kdevelop

Subscribers: kdevelop-devel

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


http://commits.kde.org/kdevelop/b4263571146bab54459dd0aa122fc5dc604705d5

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit bef8072e620ecaac9cdaf27c1996167caa7f75b5 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:54.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

M  +6-0projectmanagers/cmake/duchain/declarationbuilder.cpp

http://commits.kde.org/kdevelop/bef8072e620ecaac9cdaf27c1996167caa7f75b5

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


[kdevelop] [Bug 363707] Assert when parsing project

2016-06-01 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363707

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kdev
   ||elop/b4263571146bab54459dd0
   ||aa122fc5dc604705d5
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||elop/bef8072e620ecaac9cdaf2
   ||7c1996167caa7f75b5
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Andreas Cord-Landwehr  ---
Git commit b4263571146bab54459dd0aa122fc5dc604705d5 by Andreas Cord-Landwehr.
Committed on 02/06/2016 at 05:13.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Summary:
Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

Reviewers: apol, #kdevelop

Reviewed By: apol, #kdevelop

Subscribers: kdevelop-devel

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


http://commits.kde.org/kdevelop/b4263571146bab54459dd0aa122fc5dc604705d5

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit bef8072e620ecaac9cdaf27c1996167caa7f75b5 by Andreas Cord-Landwehr.
Committed on 01/06/2016 at 19:54.
Pushed by cordlandwehr into branch '5.0'.

Handle CMake methods/functions without arguments gracefully

Fixes crash from KDE bug #363707. For details see backtrace in
bug report.

M  +6-0projectmanagers/cmake/duchain/declarationbuilder.cpp

http://commits.kde.org/kdevelop/bef8072e620ecaac9cdaf27c1996167caa7f75b5

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


[kdevelop] [Bug 363707] Assert when parsing project

2016-05-30 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363707

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Component|Language Support: CPP   |Build tools: CMake
   |(Clang-based)   |

--- Comment #1 from Andreas Cord-Landwehr  ---
Looking again at the crash log, I think reassigning to the cmake build system
support more suited.

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


[kdevelop] [Bug 363713] New: Crash in QML Parser

2016-05-30 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363713

Bug ID: 363713
   Summary: Crash in QML Parser
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Crash in QML Parser while parsing project:

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

Thread 12 (Thread 0x7f69a65cc700 (LWP 19156)):
#0  0x7f69c1d37e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f69b468bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f69b468d8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f69a75682c9 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#4  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69baf086fa in start_thread (arg=0x7f69a65cc700) at
pthread_create.c:333
#6  0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f6992936700 (LWP 19158)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f69c242d598 in QWaitCondition::wait(QMutex*, unsigned long) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#2  0x7f69bfafc958 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x31d1140) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#3  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f69baf086fa in start_thread (arg=0x7f6992936700) at
pthread_create.c:333
#5  0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f6990907700 (LWP 19159)):
#0  0x7f69b9a4aa49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f69b9a058b9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f69b9a0624b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f69b9a0642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69c266fa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69c2618212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f69c24277bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7f69baf086fa in start_thread (arg=0x7f6990907700) at
pthread_create.c:333
#9  0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f6983fff700 (LWP 19162)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f69c1d37e82 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f69b9a0631c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f69b9a0642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f69c266fa9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69c2618212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f69c24277bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f69bfc6127c in KDevelop::CompletionWorkerThread::run
(this=0x2385150) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#8  0x7f69c242c62f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#9  0x7f69baf086fa in start_thread (arg=0x7f6983fff700) at
pthread_create.c:333
#10 0x7f69c1d43b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f6982292700 (LWP 19163)):
#0  0x7ffc833caa70 in ?? ()
#1  0x7ffc833cacfd in clock_gettime ()
#2  0x7f69c1d51fb6 in __GI___clock_gettime (clock_id=1, tp=0x7f6982291a20)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f69c24da196 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f69c266d599 in QTimerInfoList::updateCurrentTime() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f69c266daa5 in QTimerInfoList::timerWait(timespec&) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f69c266ee8e in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f69b9a058ad in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f69b9a0624b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f69b9a0642c in g_main_context_iteration () 

[kdevelop] [Bug 363707] New: Assert when parsing project

2016-05-30 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363707

Bug ID: 363707
   Summary: Assert when parsing project
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

The following assert happens every time when my current project is parsed:

Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f6b481438c0 (LWP 16253))]

Thread 9 (Thread 0x7f6b28e92700 (LWP 16254)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b36f51c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6b36f538d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6b29e2e2c9 in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#4  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b28e92700) at
pthread_create.c:333
#6  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f6b15200700 (LWP 16256)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f6b44cf3598 in QWaitCondition::wait(QMutex*, unsigned long) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#2  0x7f6b423c2958 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x16c9f00) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/duchain/duchain.cpp:282
#3  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b15200700) at
pthread_create.c:333
#5  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f6b0f076700 (LWP 16257)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b3c2cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6b3c2cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6b44f35a87 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b44ede212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b44ced7bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#7  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b0f076700) at
pthread_create.c:333
#8  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f6b069a4700 (LWP 16260)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b3c2cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6b3c2cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6b44f35a9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b44ede212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b44ced7bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f6b4252727c in KDevelop::CompletionWorkerThread::run (this=0x872150)
at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7f6b3d7ce6fa in start_thread (arg=0x7f6b069a4700) at
pthread_create.c:333
#9  0x7f6b44609b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f6b04c37700 (LWP 16261)):
#0  0x7f6b445fde8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6b3c2cc31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6b3c2cc42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6b44f35a9c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#4  0x7f6b44ede212 in
QEventLoop::exec(QFlags) () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#5  0x7f6b44ced7bc in QThread::exec() () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#6  0x7f6b4252727c in KDevelop::CompletionWorkerThread::run
(this=0x1b06580) at
/opt/nightly/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f6b44cf262f in ?? () from
/opt/Qt5.5.1/5.5/gcc_64/lib/libQt5Core.so.5
#8  0x7f6b3d7ce6fa in start_thread 

[Artikulate] [Bug 363250] It is empty on the GUI

2016-05-26 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363250

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/arti
   ||kulate/543d2b5bab2e114631b4
   ||c095bcb0a77bc1e918cf
 Resolution|--- |FIXED

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit 543d2b5bab2e114631b4c095bcb0a77bc1e918cf by Andreas Cord-Landwehr.
Committed on 26/05/2016 at 14:45.
Pushed by cordlandwehr into branch 'Applications/16.04'.

Load welcome screen when no course is available

M  +1-1src/qml/Main.qml

http://commits.kde.org/artikulate/543d2b5bab2e114631b4c095bcb0a77bc1e918cf

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


[kdevelop] [Bug 358907] Literal ampersands in toolview context-menu titles.

2016-05-18 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358907

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/a974f4193aa75f6ff5
   ||3b1ee3425fb950ec64dc3a

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit a974f4193aa75f6ff53b1ee3425fb950ec64dc3a by Andreas Cord-Landwehr.
Committed on 18/05/2016 at 18:32.
Pushed by cordlandwehr into branch '5.0'.

Fix Display of Ampersand in Context Menu

Use unprocessed window title that does not contain any ampersand
symbols for shortcuts.

M  +1-1sublime/idealdockwidget.cpp

http://commits.kde.org/kdevplatform/a974f4193aa75f6ff53b1ee3425fb950ec64dc3a

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


[kdevelop] [Bug 354748] GHNS "Get New Documentation" broken

2016-05-14 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354748

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/atti
   ||ca/d6118e0d79fc5b1abda3e2d1
   ||e506bb7bde160747
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Andreas Cord-Landwehr  ---
Git commit d6118e0d79fc5b1abda3e2d1e506bb7bde160747 by Andreas Cord-Landwehr.
Committed on 14/05/2016 at 13:52.
Pushed by cordlandwehr into branch 'master'.

Fix redirection of absolut Urls

Redirection only worked with relative urls. Yet, e.g. the http to https
redirection on KDE servers uses absolute paths, which resulted in an
empty url, since the reply attribute was not relative.

This patch adds a case distinction for redirecting absolute and relative
paths.
REVIEW: 127900

M  +7-2src/atticabasejob.cpp

http://commits.kde.org/attica/d6118e0d79fc5b1abda3e2d1e506bb7bde160747

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


[kdesrc-build] [Bug 362687] New: Enable kdesrc-build to handle Git Submodules

2016-05-05 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362687

Bug ID: 362687
   Summary: Enable kdesrc-build to handle Git Submodules
   Product: kdesrc-build
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: mp...@kde.org
  Reporter: cordlandw...@kde.org

Currently, kdesrc-build does not respect when Git repositories have submodules
and one has to checkout all of them by hand and update them by hand. I see two
possible ways how to provide this feature:
1) by default handle every repository as it had submodules: "git clone
--recursive" should not be disruptive as well as "git submodule update
--recursive" should not harm a repository with submodules IMHO
2) provide an option for the Git call of a module to specifically enable
submodule handling.

Reproducible: Always

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


[kontact] [Bug 361902] Assert when deleting mails (master branch)

2016-04-24 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361902

Andreas Cord-Landwehr  changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr  ---
After today's rebuild of PIM and its libraries, I cannot reproduce anymore.

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


[Baloo] [Bug 361903] New: Assert "DocumentUrlDB::del"

2016-04-17 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361903

Bug ID: 361903
   Summary: Assert "DocumentUrlDB::del"
   Product: Baloo
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: cordlandw...@kde.org
CC: pinak.ah...@gmail.com

Application: baloo_file_extractor (5.21.0)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.21.0
Operating System: Linux 4.4.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
Normal background run of Baloo directly after login. I got the attached crash
with the named assert.
Pleast tell me, if you need any additional information.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb6ec03d940 (LWP 26994))]

Thread 3 (Thread 0x7fb6dcb2e700 (LWP 26995)):
#0  0x7fb6e89a3e4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb6e3b59382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fb6dcb2db40) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7fb6e3b59382 in _xcb_conn_wait (c=c@entry=0x17c8f00,
cond=cond@entry=0x17c8f40, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7fb6e3b5aff7 in xcb_wait_for_event (c=0x17c8f00) at
../../src/xcb_in.c:693
#4  0x7fb6e03a98c1 in QXcbEventReader::run() (this=0x17d3550) at
qxcbconnection.cpp:1321
#5  0x7fb6e95b6cf1 in QThreadPrivate::start(void*) (arg=0x17d3550) at
thread/qthread_unix.cpp:340
#6  0x7fb6e7ad0454 in start_thread (arg=0x7fb6dcb2e700) at
pthread_create.c:334
#7  0x7fb6e89acecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb6d47a1700 (LWP 27049)):
#0  0x7fb6e985fef0 in QTimerInfoList::updateCurrentTime()
(this=0x7fb6cc002ed0) at kernel/qtimerinfo_unix.cpp:84
#1  0x7fb6e9860751 in QTimerInfoList::timerWait(timespec&)
(this=0x7fb6cc002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:381
#2  0x7fb6e986213b in timerSourcePrepareHelper(GTimerSource*, gint*)
(src=0x7fb6cc002e70, timeout=0x7fb6d47a09b4) at
kernel/qeventdispatcher_glib.cpp:126
#3  0x7fb6e98622e3 in timerSourcePrepare(GSource*, gint*)
(source=0x7fb6cc002e70, timeout=0x7fb6d47a09b4) at
kernel/qeventdispatcher_glib.cpp:159
#4  0x7fb6e43d28bd in g_main_context_prepare
(context=context@entry=0x7fb6cc000990, priority=priority@entry=0x7fb6d47a0a40)
at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3442
#5  0x7fb6e43d325b in g_main_context_iterate
(context=context@entry=0x7fb6cc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3820
#6  0x7fb6e43d343c in g_main_context_iteration (context=0x7fb6cc000990,
may_block=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901
#7  0x7fb6e9862d86 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb6cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#8  0x7fb6e97e4fc2 in
QEventLoop::processEvents(QFlags)
(this=0x7fb6d47a0bf0, flags=...) at kernel/qeventloop.cpp:128
#9  0x7fb6e97e52be in
QEventLoop::exec(QFlags) (this=0x7fb6d47a0bf0,
flags=...) at kernel/qeventloop.cpp:204
#10 0x7fb6e95aec86 in QThread::exec() (this=0x7fb6ec1c3f40 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#11 0x7fb6ec12a6c0 in QDBusConnectionManager::run() (this=0x7fb6ec1c3f40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#12 0x7fb6e95b6cf1 in QThreadPrivate::start(void*) (arg=0x7fb6ec1c3f40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#13 0x7fb6e7ad0454 in start_thread (arg=0x7fb6d47a1700) at
pthread_create.c:334
#14 0x7fb6e89acecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb6ec03d940 (LWP 26994)):
[KCrash Handler]
#6  0x7fb6e88f7478 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7fb6e88f88fa in __GI_abort () at abort.c:89
#8  0x7fb6e95a17ce in qt_message_fatal(QtMsgType, QMessageLogContext
const&, QString const&) (context=..., message=...) at global/qlogging.cpp:1645
#9  0x7fb6e959dc86 in QMessageLogger::fatal(char const*, ...) const
(this=0x7ffd6019a660, msg=0x7fb6e98cff38 "ASSERT failure in %s: \"%s\", file
%s, line %d") at global/qlogging.cpp:790
#10 0x7fb6e9596e61 in qt_assert_x(char const*, char const*, char const*,
int) (where=0x7fb6eb3b074b "DocumentUrlDB::del", what=0x7fb6eb3b0708 "This
folder still has sub-files in its cache. It cannot be deleted",
file=0x7fb6eb3b06b0 

[kontact] [Bug 361902] New: Assert when deleting mails (master branch)

2016-04-17 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361902

Bug ID: 361902
   Summary: Assert when deleting mails (master branch)
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: cordlandw...@kde.org

Application: kontact (5.2.42 pre (QtWebKit))
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.21.0
Operating System: Linux 4.4.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
I have the following with an updated Qt 5.6 from branch 5.6, KDEPIM and Akonadi
both from master branches, everything compiled during this day.

Sometimes when deleting or moving mails, I get the following assert. It does
not happen with every delete though. Thas assert corresponds to a move of three
mails of one thread in a threaded view (hotkey M).

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2cf7066900 (LWP 21047))]

Thread 26 (Thread 0x7f2ccf46c700 (LWP 21049)):
#0  0x7f2cf1d1997a in QList::iterator::operator*() const
(this=0x7f2ccf46b950) at
../../include/QtCore/../../src/corelib/tools/qlist.h:231
#1  0x7f2cf1d195b2 in QList::first() (this=0x7f2cc8002ed0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:335
#2  0x7f2cf1d1a23d in timerSourceCheckHelper(GTimerSource*)
(src=0x7f2cc8002e70) at kernel/qeventdispatcher_glib.cpp:140
#3  0x7f2cf1d1a31b in timerSourceCheck(GSource*) (source=0x7f2cc8002e70) at
kernel/qeventdispatcher_glib.cpp:167
#4  0x7f2ce5d21d61 in g_main_context_check
(context=context@entry=0x7f2cc8000990, max_priority=2147483647,
fds=fds@entry=0x7f2cc8014d70, n_fds=n_fds@entry=1) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3681
#5  0x7f2ce5d222d0 in g_main_context_iterate
(context=context@entry=0x7f2cc8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3837
#6  0x7f2ce5d2243c in g_main_context_iteration (context=0x7f2cc8000990,
may_block=1) at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901
#7  0x7f2cf1d1ad86 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f2cc80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#8  0x7f2cf1c9cfc2 in
QEventLoop::processEvents(QFlags)
(this=0x7f2ccf46bc30, flags=...) at kernel/qeventloop.cpp:128
#9  0x7f2cf1c9d2be in
QEventLoop::exec(QFlags) (this=0x7f2ccf46bc30,
flags=...) at kernel/qeventloop.cpp:204
#10 0x7f2cf1a66c86 in QThread::exec() (this=0x7f2cf71faf40 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:504
#11 0x7f2cf71616c0 in QDBusConnectionManager::run() (this=0x7f2cf71faf40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:181
#12 0x7f2cf1a6ecf1 in QThreadPrivate::start(void*) (arg=0x7f2cf71faf40
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:340
#13 0x7f2ce9640454 in start_thread (arg=0x7f2ccf46c700) at
pthread_create.c:334
#14 0x7f2cf0e64ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7f2c87013700 (LWP 21050)):
#0  0x7ffd6f7f09a9 in  ()
#1  0x7ffd6f7f0cd5 in clock_gettime ()
#2  0x7f2cf0e71a96 in __GI___clock_gettime (clock_id=1, tp=0x7f2c870128a0)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f2cf1b6c668 in qt_clock_gettime(clockid_t, timespec*) (clock=1,
ts=0x7f2c870128a0) at tools/qelapsedtimer_unix.cpp:105
#4  0x7f2cf1b6c716 in do_gettime(qint64*, qint64*) (sec=0x7f2c870128d8,
frac=0x7f2c870128d0) at tools/qelapsedtimer_unix.cpp:156
#5  0x7f2cf1b6c74a in qt_gettime() () at tools/qelapsedtimer_unix.cpp:165
#6  0x7f2cf1d17edc in QTimerInfoList::updateCurrentTime()
(this=0x7f2c80002cd0) at kernel/qtimerinfo_unix.cpp:84
#7  0x7f2cf1d18751 in QTimerInfoList::timerWait(timespec&)
(this=0x7f2c80002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:381
#8  0x7f2cf1d1a13b in timerSourcePrepareHelper(GTimerSource*, gint*)
(src=0x7f2c80002c70, timeout=0x7f2c87012a24) at
kernel/qeventdispatcher_glib.cpp:126
#9  0x7f2cf1d1a2e3 in timerSourcePrepare(GSource*, gint*)
(source=0x7f2c80002c70, timeout=0x7f2c87012a24) at
kernel/qeventdispatcher_glib.cpp:159
#10 0x7f2ce5d218bd in g_main_context_prepare
(context=context@entry=0x7f2c8990, priority=priority@entry=0x7f2c87012ab0)
at /build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3442
#11 0x7f2ce5d2225b in g_main_context_iterate
(context=context@entry=0x7f2c8990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3820

[Artikulate] [Bug 361571] Artikulate crashes on Start up

2016-04-11 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361571

--- Comment #3 from Andreas Cord-Landwehr  ---
Ubuntu packaging bug is now reported here:
https://bugs.launchpad.net/ubuntu/+source/artikulate/+bug/1569006

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


[Artikulate] [Bug 361571] Artikulate crashes on Start up

2016-04-10 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361571

Andreas Cord-Landwehr  changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Cord-Landwehr  ---
Could you try running Artikulate from command line (e.g., Konsole) and append
the console output to this bug report?

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


[dolphin] [Bug 360479] New: Crash when copy file into same folder

2016-03-13 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360479

Bug ID: 360479
   Summary: Crash when copy file into same folder
   Product: dolphin
   Version: 15.12.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org

Application: dolphin (15.12.1)
 (Compiled from sources)
Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
Happens every time:
1. mark file in some folder for copy (CTRL+C)
2. unmark file to past it into same folder (CTRL+V)
Dialog appears the file already exsists and Dolphin crashes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f40c044a940 (LWP 19857))]

Thread 3 (Thread 0x7f40bcf37700 (LWP 19858)):
#0  0x7f40cd556b6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f40c93ad382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f40bcf36b40) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x7f40c93ad382 in _xcb_conn_wait (c=c@entry=0x174a470,
cond=cond@entry=0x174a4b0, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x7f40c93aeff7 in xcb_wait_for_event (c=0x174a470) at
../../src/xcb_in.c:693
#4  0x7f40c01bbf01 in QXcbEventReader::run() (this=0x1754ad0) at
qxcbconnection.cpp:1229
#5  0x7f40ce1a9f0d in QThreadPrivate::start(void*) (arg=0x1754ad0) at
thread/qthread_unix.cpp:331
#6  0x7f40ca8a5284 in start_thread (arg=0x7f40bcf37700) at
pthread_create.c:333
#7  0x7f40cd55fa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f40b29e4700 (LWP 19859)):
#0  0x7f40cd552b7d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f40c5d18510 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f40b29e39a0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7f40c5d18510 in g_wakeup_acknowledge (wakeup=0x7f40b80015b0) at
/build/glib2.0-2.46.2/./glib/gwakeup.c:210
#3  0x7f40c5cd4cb4 in g_main_context_check
(context=context@entry=0x7f40ac000990, max_priority=2147483647,
fds=fds@entry=0x7f40ac003020, n_fds=n_fds@entry=1) at
/build/glib2.0-2.46.2/./glib/gmain.c:3632
#4  0x7f40c5cd5170 in g_main_context_iterate
(context=context@entry=0x7f40ac000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2.46.2/./glib/gmain.c:3837
#5  0x7f40c5cd52dc in g_main_context_iteration (context=0x7f40ac000990,
may_block=1) at /build/glib2.0-2.46.2/./glib/gmain.c:3901
#6  0x7f40ce44a71c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f40ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f40ce3d1078 in
QEventLoop::processEvents(QFlags)
(this=0x7f40b29e3c20, flags=...) at kernel/qeventloop.cpp:128
#8  0x7f40ce3d1374 in
QEventLoop::exec(QFlags) (this=0x7f40b29e3c20,
flags=...) at kernel/qeventloop.cpp:204
#9  0x7f40ce1a26bc in QThread::exec() (this=0x1c1a650) at
thread/qthread.cpp:503
#10 0x7f40ce1a285e in QThread::run() (this=0x1c1a650) at
thread/qthread.cpp:570
#11 0x7f40ce1a9f0d in QThreadPrivate::start(void*) (arg=0x1c1a650) at
thread/qthread_unix.cpp:331
#12 0x7f40ca8a5284 in start_thread (arg=0x7f40b29e4700) at
pthread_create.c:333
#13 0x7f40cd55fa4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f40c044a940 (LWP 19857)):
[KCrash Handler]
#6  0x7f40cf44a99c in QWeakPointer::data() const (this=0x270) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:588
#7  0x7f40cf461270 in QPointer::data() const (this=0x270) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:70
#8  0x7f40cf45ef50 in QPointer::operator QWidget*() const
(this=0x270) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:76
#9  0x7f40cf67e454 in QScrollArea::widget() const (this=0x7f40ce4bb180
) at widgets/qscrollarea.cpp:224
#10 0x7f40d3953d0f in KIO::RenameDialog::resizePanels()
(this=0x7ffdadbaf1f0) at
/opt/kde/src/frameworks/kio/src/widgets/renamedialog.cpp:589
#11 0x7f40d397159d in KIO::RenameDialog::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x7ffdadbaf1f0,
_c=QMetaObject::InvokeMetaMethod, _id=15, _a=0x21d10c0) at
/opt/kde/build/frameworks/kio/src/widgets/moc_renamedialog.cpp:137
#12 0x7f40ce40b3ed in QMetaCallEvent::placeMetaCall(QObject*)
(this=0x214e560, object=0x7ffdadbaf1f0) at kernel/qobject.cpp:486
#13 0x7f40ce40c468 in QObject::event(QEvent*) (this=0x7ffdadbaf1f0,
e=0x214e560) at kernel/qobject.cpp:1239
#14 0x7f40cf4a9853 in QWidget::event(QEvent*) (this=0x7ffdadbaf1f0,
event=0x214e560) at 

[Artikulate] [Bug 360013] Applications/15.12 depends on 5.4.3 qt5

2016-03-03 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360013

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
The hard build-dep was done before the dependency freeze of the 15.12 release.
So I do not see any problem with it. As of now we do not have a global policy
that defines the maximum Qt version one may depend on.
I agree that for convenience of the build system it would be good. But
Artikulate hard depends on Qt 5.5. The major requirement is the QtQuick
TreeView which was newly introduced in Qt 5.5. and porting away from it would
be a major refactoring of the whole UI (not possible in a bugfix release). A
smaller build dependency would work (e.g. 5.4, since ABI is compatible and the
application would *only* crash at runtime), but to make this
runtime-requirement obvious I want to keep it this way.

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


[parley] [Bug 350887] Error when trying to practise conjugations

2016-03-01 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=350887

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/parl
   ||ey/a6c0dbdbf6fdb0190e4dec88
   ||1154fd64d112a705
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit a6c0dbdbf6fdb0190e4dec881154fd64d112a705 by Andreas Cord-Landwehr,
on behalf of Hartmut Riesenbeck.
Committed on 01/03/2016 at 19:13.
Pushed by cordlandwehr into branch 'master'.

Fix practise conjugations.

To make practice conjugations work two bugs had to be fixed:

The first bug was caused by uninitialized member variable m_toTranslation
in EntryFilter constructor. This caused that DocumentSettings could
not be loaded and EntryFilter::m_tenses was empty (later in
EntryFilter::cleanupInvalid method). Changed constructor to initialize
m_toTranslation from Prefs::learningLanguage() and m_fromTranslation
from Prefs::knownLanguage(). The second was not necessary to load the
document settings, but was inserted for the sake of order.

The member m_tenses is used in EntryFilter::cleanupInvalid method to
remove entries which don't have any of the tenses which are configured
for practice. Now that document settings was not loaded propperly before,
m_tenses is empty. Because m_tenses was empty, all entries were removed
and the error dialog was shown.

After this was fixed, it came out that the conjugation prcatice widget
didn't display the verbs to_translation and from_translation. This was
caused by an incomplete initialisation of TestEntry objects in
EntryFilter::conjugationTestEntries method. This was fixed by init the
To- and From-Language of each new test enty from m_toTranslation and
m_fromTranslation of EntryFilter.
REVIEW: 127155

M  +6-0src/collection/entryfilter.cpp

http://commits.kde.org/parley/a6c0dbdbf6fdb0190e4dec881154fd64d112a705

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


[parley] [Bug 357624] Grammar download fails

2016-01-13 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357624

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/libk
   ||eduvocdocument/64b82e59632c
   ||be389986279a15dc5e9ed89e4f1
   ||b
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 64b82e59632cbe389986279a15dc5e9ed89e4f1b by Andreas Cord-Landwehr.
Committed on 13/01/2016 at 21:29.
Pushed by cordlandwehr into branch 'master'.

Fix download of remote URLs.

By downloading to a temporary file, file_copy must set to overwrite the
existing (temporary) file. Otherwise, it performs a safety abort. Since
the temporary file is ensured to be just created and not contain any
data, it can safely be overwritten.

M  +2-2keduvocdocument/keduvocdocument.cpp

http://commits.kde.org/libkeduvocdocument/64b82e59632cbe389986279a15dc5e9ed89e4f1b

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


[parley] [Bug 357508] Get new themes not working

2016-01-05 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357508

Andreas Cord-Landwehr  changed:

   What|Removed |Added

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

--- Comment #3 from Andreas Cord-Landwehr  ---
You have to set the XDG_CONFIG_DIRS environment variable for this to work.
Maybe you want to have a look at the "Runtime Setup" section in
https://community.kde.org/Frameworks/Building to have an overview of the
important environment variables you have to set when you are installing
self-compiled programs to custom paths.

I am closing this report, since this is not a program bug.

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


[parley] [Bug 357521] Clicking to Practice Overview leads to crash

2016-01-04 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357521

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||cordlandw...@kde.org
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Andreas Cord-Landwehr  ---
Sorry, I cannot reproduce this. Please install debug symbols for the package
that contains QtWidgets and then create a new backtrace that does not contain
any "??" values anymore. Otherwise it is not possible to see where the crash
originates from.
On some distributions the required package is called "qtbase5-dbg".

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


[parley] [Bug 351976] Missing Comment in desktop file

2016-01-01 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=351976

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/parl
   ||ey/73d44ec6e141eace6dea4de9
   ||be269eb7adc49c2c
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 73d44ec6e141eace6dea4de9be269eb7adc49c2c by Andreas Cord-Landwehr.
Committed on 01/01/2016 at 14:42.
Pushed by cordlandwehr into branch 'master'.

Add Comment to desktop file.

This is the tag line from the edu-website.

M  +1-0src/org.kde.parley.desktop

http://commits.kde.org/parley/73d44ec6e141eace6dea4de9be269eb7adc49c2c

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


[parley] [Bug 357385] Cannot edit existing collection

2016-01-01 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357385

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/libk
   ||eduvocdocument/1d14e946aacb
   ||395330e21c7b7696913fccaf255
   ||4
 Resolution|--- |FIXED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 1d14e946aacb395330e21c7b7696913fccaf2554 by Andreas Cord-Landwehr.
Committed on 01/01/2016 at 15:00.
Pushed by cordlandwehr into branch 'master'.

Make QString to QUrl conversions explicit.

This avoids silent conversions from file paths that are not provided in
url format and thus result in empty QUrl paths.

M  +3-1CMakeLists.txt
M  +4-4keduvocdocument/keduvocdocument.cpp
M  +2-2keduvocdocument/tests/converter.cpp

http://commits.kde.org/libkeduvocdocument/1d14e946aacb395330e21c7b7696913fccaf2554

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


[parley] [Bug 357385] Cannot edit existing collection

2016-01-01 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357385

--- Comment #6 from Andreas Cord-Landwehr  ---
Git commit 322cb7e34e3b7ca7ebf4caf4ed75b22fb51fd68d by Andreas Cord-Landwehr.
Committed on 01/01/2016 at 15:53.
Pushed by cordlandwehr into branch 'master'.

Use more robust comparison.

Solves popup error when saving new file.

M  +1-1src/parleydocument.cpp

http://commits.kde.org/parley/322cb7e34e3b7ca7ebf4caf4ed75b22fb51fd68d

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


[parley] [Bug 356233] File is not writeable when creating a new collection

2015-12-30 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356233

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/libk
   ||eduvocdocument/0cb9b9aea226
   ||4fc66d25fb6d93adc32c75dfef9
   ||7
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from Andreas Cord-Landwehr  ---
Git commit 0cb9b9aea2264fc66d25fb6d93adc32c75dfef97 by Andreas Cord-Landwehr.
Committed on 30/12/2015 at 18:54.
Pushed by cordlandwehr into branch 'master'.

Fix Save-As functionality.

File system operations like QFile require paths instead of URLs, which
is the difference between the uses of:
* url.toDisplayString -> file:///the/path
* url.toLocalFile -> /the/path
Correctly use toLocalFile for all file system calls.

M  +2-2keduvocdocument/keduvocdocument.cpp

http://commits.kde.org/libkeduvocdocument/0cb9b9aea2264fc66d25fb6d93adc32c75dfef97

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


[parley] [Bug 356233] File is not writeable when creating a new collection

2015-12-08 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356233

--- Comment #5 from Andreas Cord-Landwehr  ---
It's actually much easier than described there. (That description is mostly for
power-users.)
You can simply login in the webinterface at reviewboard.kde.org (using your KDE
identity account; you can create it yourself at identity.kde.org, in case you
do not have  one yet), select Parley as application and "kdeedu" as review
group, and submit the patch for review.

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


[parley] [Bug 356329] the is bug when opened editor

2015-12-06 Thread Andreas Cord-Landwehr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356329

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||cordlandw...@kde.org
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Andreas Cord-Landwehr  ---
That sounds to be two bugs:
1. (the simple one): linking against KCrash is missing and hence the DrKonqui
crash dialog is not started (this should be already fixed for the 15.12
release)
2. the application crashed.

For the second problem (the actual crash), more information are needed to be
able to fix it. Can you please do the following:
* run in a console "gdb parley"
* reproduce the crash in Parley
* in the gdb run type "bt full"
* attach the output of that gdb command to this bug report
(you can eventually close gdb with "quit).

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