date:20170101

Re: konsole --version crashes

2017-01-01 Thread Dmitry Shachnev

Hi Kamaraju!

On Sun, Jan 01, 2017 at 04:15:54PM -0500, kamaraju kusumanchi wrote:
> > Thiago says that integration for these patches is likely to fail, so I want
> > to wait until the integration results first. Either the patches are OK and
> > they are applied upstream, or we get to know which bugs they have.
>
> Thanks Dmitry. What you mean by integration results? When do you
> expect to get it? Assuming that everything checks out with the
> patches, do you think the bug will be fixed in the next stable release
> when stretch is released?

I mean the continuous integration on Qt Gerrit (which runs the build and
auto tests on different platforms).

The status of https://codereview.qt-project.org/180231 and 232 is STAGED,
which means the integration is scheduled. I guess it should be run soon
as the EU holidays have ended.

And yes, I hope we will have this fix in Stretch.

--
Dmitry Shachnev

signature.asc
Description: PGP signature

Bug#849890: korganizer: korgac crashes every time I login into a KDE session

2017-01-01 Thread Kamaraju Kusumanchi

Package: korganizer
Version: 4:16.04.3-2
Severity: normal

Dear Maintainer,

Every time I login into a KDE session, korgac crashes with a segmentation
fault. Please find the backtrace from the crash handler below.

Application: korgac (korgac), signal: Segmentation fault
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 0x7fe013d69940 (LWP 2274))]

Thread 3 (Thread 0x7fe010887700 (LWP 2315)):
[KCrash Handler]
#6  0x7fe02e0043ef in QObject::disconnect (sender=0xcb7b3ab0,
signal=signal@entry=0x0, receiver=receiver@entry=0x7fe0040030f0,
method=method@entry=0x0) at kernel/qobject.cpp:2956
#7  0x7fe033000d50 in QObject::disconnect (member=0x0,
receiver=0x7fe0040030f0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:336
#8  QDBusConnectionPrivate::closeConnection (this=this@entry=0x7fe0040030f0) at
qdbusintegrator.cpp:1145
#9  0x7fe032fed7e2 in QDBusConnectionManager::run (this=0x7fe033062d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:188
#10 0x7fe02de04da8 in QThreadPrivate::start (arg=0x7fe033062d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#11 0x7fe026772464 in start_thread (arg=0x7fe010887700) at
pthread_create.c:333
#12 0x7fe02d5089df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fe011da7700 (LWP 2305)):
#0  0x7fe02d4ff56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fe02748a150 in poll (__timeout=-1, __nfds=1, __fds=0x7fe011da6b80)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0xcb75da80, cond=cond@entry=0xcb75dac0,
vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:479
#3  0x7fe02748bee9 in xcb_wait_for_event (c=0xcb75da80) at
../../src/xcb_in.c:693
#4  0x7fe013accb69 in QXcbEventReader::run (this=0xcb76e550) at
qxcbconnection.cpp:1343
#5  0x7fe02de04da8 in QThreadPrivate::start (arg=0xcb76e550) at
thread/qthread_unix.cpp:368
#6  0x7fe026772464 in start_thread (arg=0x7fe011da7700) at
pthread_create.c:333
#7  0x7fe02d5089df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fe013d69940 (LWP 2274)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe02de05c6b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0xcb79d6b0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0xcb793510,
mutex=mutex@entry=0xcb7934f0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fe02de0494e in QThread::wait (this=this@entry=0x7fe033062d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>,
time=time@entry=18446744073709551615) at thread/qthread_unix.cpp:698
#4  0x7fe032fed546 in QDBusConnectionManager::~QDBusConnectionManager
(this=0x7fe033062d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>, __in_chrg=) at qdbusconnection.cpp:157
#5  0x7fe032fed5d9 in (anonymous
namespace)::Q_QGS__q_manager::Holder::~Holder (this=,
__in_chrg=) at qdbusconnection.cpp:76
#6  0x7fe02d455920 in __run_exit_handlers (status=0, listp=0x7fe02d7b85d8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:83
#7  0x7fe02d45597a in __GI_exit (status=) at exit.c:105
#8  0x7fe02fcdf4a5 in
KDBusService::KDBusService(QFlags, QObject*) ()
from /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5
#9  0xcab2c535 in ?? ()
#10 0x7fe02d4402b1 in __libc_start_main (main=0xcab2c070, argc=1,
argv=0x7fff9e9ea898, init=, fini=,
rtld_fini=, stack_end=0x7fff9e9ea888) at ../csu/libc-start.c:291
#11 0xcab2c76a in _start ()


FWIW, I am running Debian Stretch (currently testing)

thanks
raju



-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages korganizer depends on:
ii  kdepim-runtime   4:16.04.2-2
ii  kf5-kdepimlibs-kio-plugins   4:16.04.2-2
ii  libc62.24-8
ii  libgcc1  1:6.2.1-5
ii  libkf5akonadicalendar5   16.04.2-2
ii  libkf5akonadicontact54:16.04.2-2
ii  libkf5akonadicore-bin4:16.04.3-3+b1
ii  libkf5akonadicore5   4:16.04.3-3+b1
ii  libkf5akonadimime5   4:16.04.2-2
ii  libkf5akonadinotes5  4:16.04.2-2
ii  libkf5akonadisearchpim5  16.04.3-1
ii  libkf5akonadiwidgets54:16.04.3-3+b1
ii

Re: Bug#1 Freeze

2017-01-01 Thread Jimmy Johnson


On 11/09/2016 12:20 AM, newbee...@nativobject.net wrote:

Le 09/11/2016 à 04:14, Jimmy Johnson a écrit :

On 11/07/2016 04:44 AM, Tim Ruehsen wrote:

With latest updates made today:

From time to time, KDE freezes. Any idea ?


Hi,
If it's an Intel video card and the kernel is 4.8 downgrade the kernel
to 4.7 and it will take care of the problem.

Same here !

Regards

Mourad



Mine is an Intel Mobile GM965/GL960 Integrated Graphics and it's now 
working swell with the Sid 4.8.0-2 kernel but not as quick to load as 
the 4.7.0-1 kernel which works with no problem.  In Stretch the 4.8.0-2 
kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile 
GM965/GL960 Integrated Graphics. Plasma and SDDM.

--
Jimmy Johnson

Ubuntu 16.04 LTS - Plasma 5.8.4 - AMD64 - EXT4 at sda22
Registered Linux User #380263

Bug#792594: libqt5qml5 requires SSE2 on i386

2017-01-01 Thread Guillem Jover

Hi!

On Sun, 2017-01-01 at 11:41:45 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> On domingo, 1 de enero de 2017 04:13:41 ART Guillem Jover wrote:
> [snip]
> > > In any case, because I need a patched Qt on my systems to be
> > > able to run many Qt applications at all, I'll have to rebase the patches
> > > and build local packages anyway. I'll try to send the rebased patches
> > > here for whoever else needs them, if I remember.
> > 
> > As I had to upgrade all the systems involved, I needed to update
> > the patches, which I did against 5.7.x and 5.8.x (git HEAD).
> > 
> > > If someone else wants access to the Qt Declaratives packages I'm
> > > building please say so, and I'll publish them on some repository.
> > 
> > This still stands.
> 
> And you are really willing to take care of this delta, so let's make it 
> official.

Ah, perfect thanks! And well, as long as I've got such hardware I'll
have to do that anyway, yes.

> The only thing I would like you to change in order to accept the patch is to 
> change the generic hasRequiredCpuSupport() for something more precise, maybe 
> something along cpuHasSse2Support() or alike. Yes, I know it's just details, 
> but helps while looking at the code.

I think we might have covered this in the past reviews, but in any
case I think that would be very confusing, because on non-i386 such
cpuHasSse2Support() function would need to return true, which is very
much not correct. :) I've left it as is, but reworked the text message
handling so that it's also generic now. Hope that qualms your concerns.

Actually, I didn't like that either, and reworked it even further (v2),
but I've not build tested that one yet.

Attached both updated patches, for which I've only built tested the first
one for now, but I'd not expect any run-time problems. But I'll try to do
that for the second one tomorrow.

Thanks,
Guillem
From 8020224f94ff24b6bafd59613427ed91bf8c341e Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Mon, 12 Oct 2015 01:45:37 +0200
Subject: [PATCH] Do not make lack of SSE2 support on x86-32 fatal

When an x86-32 CPU does not have SSE2 support (which is the case for
all AMD CPUs, and older Intel CPUs), fallback to use the interpreter,
otherwise use the JIT engine.

Even then, make the lack of SSE2 support on x86-32 fatal when trying
to instantiate a JIT engine, which does require it.

Refactor the required CPU support check and text into a new pair of
privately exported functions to avoid duplicating the logic, and do
so in functions instead of class members to avoid changing the class
signatures.

Version: 5.7.x
Bug-Debian: https://bugs.debian.org/792594
---
 src/qml/jit/qv4isel_masm.cpp|  3 +++
 src/qml/jit/qv4isel_masm_p.h| 19 +++
 src/qml/jsruntime/qv4engine.cpp |  1 +
 src/qml/qml/v8/qv8engine.cpp|  7 ---
 tools/qmljs/qmljs.cpp   |  7 +++
 5 files changed, 26 insertions(+), 11 deletions(-)

diff --git a/src/qml/jit/qv4isel_masm.cpp b/src/qml/jit/qv4isel_masm.cpp
index d047623ac..5be02998e 100644
--- a/src/qml/jit/qv4isel_masm.cpp
+++ b/src/qml/jit/qv4isel_masm.cpp
@@ -265,6 +265,9 @@ InstructionSelection::InstructionSelection(QQmlEnginePrivate *qmlEngine, QV4::Ex
 , compilationUnit(new CompilationUnit)
 , qmlEngine(qmlEngine)
 {
+if (!hasRequiredCpuSupport())
+qFatal("This program requires %s", getRequiredCpuSupportText());
+
 compilationUnit->codeRefs.resize(module->functions.size());
 }
 
diff --git a/src/qml/jit/qv4isel_masm_p.h b/src/qml/jit/qv4isel_masm_p.h
index 1e6ac1f51..0f48f9c01 100644
--- a/src/qml/jit/qv4isel_masm_p.h
+++ b/src/qml/jit/qv4isel_masm_p.h
@@ -59,6 +59,7 @@
 
 #include 
 #include 
+#include 
 #include 
 #include 
 
@@ -71,6 +72,24 @@ QT_BEGIN_NAMESPACE
 namespace QV4 {
 namespace JIT {
 
+Q_QML_PRIVATE_EXPORT inline bool hasRequiredCpuSupport()
+{
+#ifdef Q_PROCESSOR_X86_32
+return qCpuHasFeature(SSE2);
+#else
+return true;
+#endif
+}
+
+Q_QML_PRIVATE_EXPORT inline const char *getRequiredCpuSupportText()
+{
+#ifdef Q_PROCESSOR_X86_32
+return "an X86 processor that supports SSE2 extension, at least a Pentium 4 or newer";
+#else
+return "no specific processor features, something strange happened";
+#endif
+}
+
 class Q_QML_EXPORT InstructionSelection:
 protected IR::IRDecoder,
 public EvalInstructionSelection
diff --git a/src/qml/jsruntime/qv4engine.cpp b/src/qml/jsruntime/qv4engine.cpp
index 26f473a7a..5e4100ac0 100644
--- a/src/qml/jsruntime/qv4engine.cpp
+++ b/src/qml/jsruntime/qv4engine.cpp
@@ -162,6 +162,7 @@ ExecutionEngine::ExecutionEngine(EvalISelFactory *factory)
 
 #ifdef V4_ENABLE_JIT
 static const bool forceMoth = !qEnvironmentVariableIsEmpty("QV4_FORCE_INTERPRETER") ||
+  !JIT::hasRequiredCpuSupport() ||
   !OSAllocator::canAllocateExecutableMemory();
 if (forceMoth) {
 factory = new

Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines

2017-01-01 Thread Sandro Knauß

Hey,

> (temporarily not raising this bug to RC-level to allow initial testing
> migration)

thanks for that :)

> This package could not be built on (any) official buildd machine other than
> amd64 (which was a binary upload). This problem needs to be solved sooner or
> later.
>
> I tried to build it on my own x86_64 VPS (1GB mem + 4GB swap) and it is
> still experiencing FTBFS (OOM?).

well that is too less :) I think you need at least 8G RAM + 8G disk space. Yes 
it is that huge :)

> The root of FTBFS seems different on different architectures:

I already started to write mails to failing archs to get ideas, to get input 
on how to fix those issues.

https://lists.alioth.debian.org/pipermail/pkg-kde-talk/2016-December/
002455.html

At this thread some ideas pop up, that may help. If you have any additional 
ideas how to fix the problems, feel free to post those. I have very less 
experience in other platforms that amd64/i386 so open for input :)

Best Regards,

sandro

signature.asc
Description: This is a digitally signed message part.

Re: konsole --version crashes

2017-01-01 Thread kamaraju kusumanchi

On Sat, Dec 31, 2016 at 7:47 AM, Martin Steigerwald  wrote:
> Am Freitag, 30. Dezember 2016, 17:39:21 CET schrieb kamaraju kusumanchi:
>> On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano 
> wrote:
>> > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few
>> > race conditions which requires some (unmerged) patches (unmerged because
>> > they cause regression on windows), quoting:
>> > "https://codereview.qt-project.org/180231 and 232 at least"
>> >
>> > They are not apparently applied to the Qt packages in Debian.
>>
>> Thanks Luigi.
>>
>> What would be the next steps? Is it possible to include those two
>> patches in the Debian then?
>
> Both Lisandro and Mitya are in Cc of this mail already, so they are aware. You
> could create a bug report to ask for the inclusion of these patches in order
> to help that it doesn´t get lost. Or ping them on #debian-qt-kde IRC channel.

Thanks Martin. I reported the bug at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849877 so it does
not get lost.

Also, I noticed something since I originally reported the issue here.
When konsole crashes, some times it opens up the popup window with the
backtrace and some times it does not. The backtrace from the popup
window contains more information. You can find both backtraces in the
bug report.


raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: konsole --version crashes

2017-01-01 Thread kamaraju kusumanchi

On Sat, Dec 31, 2016 at 10:45 AM, Dmitry Shachnev  wrote:
> Hi all,
>
> On Sat, Dec 31, 2016 at 01:47:04PM +0100, Martin Steigerwald wrote:
>> Am Freitag, 30. Dezember 2016, 17:39:21 CET schrieb kamaraju kusumanchi:
>> > On Fri, Dec 30, 2016 at 8:57 AM, Luigi Toscano  
>> > wrote:
>> > > I spoke with the QtBus maintainer (Thiago Macieira) and he mentioned few
>> > > race conditions which requires some (unmerged) patches (unmerged because
>> > > they cause regression on windows), quoting:
>> > > "https://codereview.qt-project.org/180231 and 232 at least"
>> > >
>> > > They are not apparently applied to the Qt packages in Debian.
>> >
>> > Thanks Luigi.
>> >
>> > What would be the next steps? Is it possible to include those two
>> > patches in the Debian then?
>>
>> Both Lisandro and Mitya are in Cc of this mail already, so they are aware. 
>> You
>> could create a bug report to ask for the inclusion of these patches in order
>> to help that it doesn´t get lost. Or ping them on #debian-qt-kde IRC channel.
>
> Thiago says that integration for these patches is likely to fail, so I want
> to wait until the integration results first. Either the patches are OK and
> they are applied upstream, or we get to know which bugs they have.

Thanks Dmitry. What you mean by integration results? When do you
expect to get it? Assuming that everything checks out with the
patches, do you think the bug will be fixed in the next stable release
when stretch is released?

raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Bug#849877: konsole --version crashes

2017-01-01 Thread Kamaraju Kusumanchi

Package: konsole
Version: 4:16.08.2-2
Severity: normal

When I run "konsole --version", it crashes with the following errors

rajulocal@hogwarts ~ % konsole --version
konsole 16.08.2
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konsole path = /usr/bin pid = 12566
KCrash: Arguments: /usr/bin/konsole --version
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
zsh: suspended (signal)  konsole --version


Here is the backtrace from the popup window

Application: konsole (konsole), signal: Segmentation fault
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 0x7f2134ecc940 (LWP 12589))]

Thread 3 (Thread 0x7f2131027700 (LWP 12591)):
[KCrash Handler]
#6  0x7f214326b3ef in QObject::disconnect (sender=0x55da6ad15e60,
signal=signal@entry=0x0, receiver=receiver@entry=0x7f21240030f0,
method=method@entry=0x0) at kernel/qobject.cpp:2956
#7  0x7f2146c9ed50 in QObject::disconnect (member=0x0,
receiver=0x7f21240030f0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:336
#8  QDBusConnectionPrivate::closeConnection (this=this@entry=0x7f21240030f0) at
qdbusintegrator.cpp:1145
#9  0x7f2146c8b7e2 in QDBusConnectionManager::run (this=0x7f2146d00d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:188
#10 0x7f214306bda8 in QThreadPrivate::start (arg=0x7f2146d00d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#11 0x7f213f8d1464 in start_thread (arg=0x7f2131027700) at
pthread_create.c:333
#12 0x7f21466989df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f2132f0a700 (LWP 12590)):
#0  0x7f214668f56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f213fcf6150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f213fcf7ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-
gnu/libxcb.so.1
#3  0x7f2134c2fb69 in ?? () from /usr/lib/x86_64-linux-
gnu/libQt5XcbQpa.so.5
#4  0x7f214306bda8 in QThreadPrivate::start (arg=0x55da6acba2b0) at
thread/qthread_unix.cpp:368
#5  0x7f213f8d1464 in start_thread (arg=0x7f2132f0a700) at
pthread_create.c:333
#6  0x7f21466989df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f2134ecc940 (LWP 12589)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f214306cc6b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x55da6ad01ff0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x55da6ad01fd0,
mutex=mutex@entry=0x55da6ad01fb0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f214306b94e in QThread::wait (this=this@entry=0x7f2146d00d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>,
time=time@entry=18446744073709551615) at thread/qthread_unix.cpp:698
#4  0x7f2146c8b546 in QDBusConnectionManager::~QDBusConnectionManager
(this=0x7f2146d00d60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>, __in_chrg=) at qdbusconnection.cpp:157
#5  0x7f2146c8b5d9 in (anonymous
namespace)::Q_QGS__q_manager::Holder::~Holder (this=,
__in_chrg=) at qdbusconnection.cpp:76
#6  0x7f21465e5920 in __run_exit_handlers (status=status@entry=0,
listp=0x7f21469485d8 <__exit_funcs>,
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at
exit.c:83
#7  0x7f21465e597a in __GI_exit (status=status@entry=0) at exit.c:105
#8  0x7f214307b473 in QCommandLineParser::showVersion
(this=this@entry=0x55da6ad2b710) at tools/qcommandlineparser.cpp:1004
#9  0x7f214307c6fb in QCommandLineParser::process
(this=this@entry=0x55da6ad2b710, arguments=...) at
tools/qcommandlineparser.cpp:596
#10 0x7f214307c75f in QCommandLineParser::process
(this=this@entry=0x55da6ad2b710, app=...) at tools/qcommandlineparser.cpp:611
#11 0x7f21469759cb in kdemain (argc=, argv=)
at ./src/main.cpp:116
#12 0x7f21465d02b1 in __libc_start_main (main=0x55da6a154780 ,
argc=2, argv=0x7ffc2d688398, init=, fini=,
rtld_fini=, stack_end=0x7ffc2d688388) at ../csu/libc-start.c:291
#13 0x55da6a1547ba in _start ()


I am able to reproduce the problem consistently. It crashes everytime I run
konsole --version. However, the popup window that gives the backtrace comes up
sometimes and does not come up some other times. When there is no popup window,
I get the following backtrace from gdb

% gdb konsole
GNU gdb (Debian 7.11.1-2+b1) 7.11.1
...
Reading symbols from konsole...Reading symbols from /usr/lib/debug/.build-
id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done.
done.
(gdb) set args --version
(gdb) thread apply all backtrace
(gdb) r
Starting program:

Re: Plasma 5.8.5 coming and some other rough status information

2017-01-01 Thread Martin Steigerwald

Am Samstag, 31. Dezember 2016, 14:36:45 CET schrieb Héctor Sales Llamas:
> Hi, Martin:

> What version of Plasma will brings on Debian Stretch stable ?

From what I gathered:

5.8.x were x might be 5 or a higher number. 5.8 is LTS release.

Ciao,
-- 
Martin

Bug#849868: kde-plasma-desktop: Middle button causes yellow box that can't be removed

2017-01-01 Thread Nigel Horne

Package: kde-plasma-desktop
Version: 5:91
Severity: normal

Dear Maintainer,

If you press the middle button of your mouse on the desktop an annoying yellow
box appears with your clipeboard contents in it.  I say annoying because there's
no way to remove the box, no dismiss button or "quit" option.

   * What led up to the situation?
   Clikck middle button.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Right click, ps, look at task manager
   * What was the outcome of this action?
   No way to remove this pop-up
   * What outcome did you expect instead?
   A way to remove the pop-up


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/20 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps  4:16.08.3-1
ii  kde-runtime   4:16.08.3-1
ii  plasma-desktop4:5.8.2-1
ii  plasma-workspace  4:5.8.2-1
ii  udisks2   2.1.8-1
ii  upower0.99.4-4

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.8.2-1+b1
ii  sddm  0.13.0-1
ii  xserver-xorg  1:7.7+18

Versions of packages kde-plasma-desktop suggests:
ii  kde-l10n-engb [kde-l10n]  4:16.04.3-1

-- no debconf information

Bug#792594: libqt5qml5 requires SSE2 on i386

2017-01-01 Thread Lisandro Damián Nicanor Pérez Meyer

On domingo, 1 de enero de 2017 04:13:41 ART Guillem Jover wrote:
[snip]
> > I've found that the changes required for each minor version are rather
> > minimal.
> 
> This still is the case up to now. Well, with latest patches, the changes
> required were even more trivial.

Accroding to the diff this is indeed true.

> > In any case, because I need a patched Qt on my systems to be
> > able to run many Qt applications at all, I'll have to rebase the patches
> > and build local packages anyway. I'll try to send the rebased patches
> > here for whoever else needs them, if I remember.
> 
> As I had to upgrade all the systems involved, I needed to update
> the patches, which I did against 5.7.x and 5.8.x (git HEAD).
> 
> > If someone else wants access to the Qt Declaratives packages I'm
> > building please say so, and I'll publish them on some repository.
> 
> This still stands.

And you are really willing to take care of this delta, so let's make it 
official.

The only thing I would like you to change in order to accept the patch is to 
change the generic hasRequiredCpuSupport() for something more precise, maybe 
something along cpuHasSse2Support() or alike. Yes, I know it's just details, 
but helps while looking at the code.

Happy new year, Lisandro.

-- 
Yo quiero conocer el pensamiento de Dios, el resto son detalles.
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

signature.asc
Description: This is a digitally signed message part.

Bug#849854: [plasma-desktop] nm-applet cannot be interracted with from Plasma panel tray

2017-01-01 Thread Alex Dănilă


Package: plasma-desktop
Version: 4:5.8.4-1
Severity: normal

--- Please enter the report below this line. ---
Hi,
nm-applet can no longer be interacted with in newer builds of the KDE 
desktop. The icon is displayed correctly in the system tray (shows the 
quality of the wireless connection and updates correctly when the 
connection changes) but it cannot be interacted with. Click and right 
click have no effect.


nm-applet has worked correctly for quite a while, this is a new problem 
that may have appeared in the last months. Reproducible on computers 
with Intel, Radeon and Nvidia, if that matters in any way.


Thank you,
Alex

--- System information. ---
Architecture:
Kernel: Linux 4.8.0-2-amd64

Debian Release: stretch/sid
900 testing ftp.debian.org
500 stable security.debian.org
500 stable deb.opera.com
500 sid linux.dropbox.com
1 unstable ftp.debian.org

--- Package information. ---
Depends (Version) | Installed
=-+-== 


breeze | 4:5.8.4-1
kactivitymanagerd | 5.8.4-1
kde-cli-tools | 4:5.8.4-1
kded5 | 5.28.0-1
kio | 5.28.0-1
oxygen-sounds | 4:5.8.4-1
plasma-desktop-data (= 4:5.8.4-1) | 4:5.8.4-1
plasma-framework | 5.28.0-1
plasma-integration | 5.8.4-1
plasma-workspace | 4:5.8.4-1
polkit-kde-agent-1 | 4:5.8.4-1
qml-module-org-kde-draganddrop | 5.28.0-1
qml-module-org-kde-kcoreaddons | 5.28.0-1
qml-module-org-kde-kquickcontrols | 5.28.0-1
qml-module-org-kde-kquickcontrolsaddons | 5.28.0-1
qml-module-org-kde-kwindowsystem | 5.28.0-1
qml-module-org-kde-solid | 5.28.0-2
qml-module-qt-labs-folderlistmodel | 5.7.1-1
qml-module-qt-labs-settings | 5.7.1-1
libc6 (>= 2.15) |
libcanberra0 (>= 0.2) |
libfontconfig1 (>= 2.11) |
libgcc1 (>= 1:3.0) |
libkf5activities5 (>= 5.21.0) |
libkf5activitiesstats1 (>= 5.20) |
libkf5archive5 (>= 4.96.0) |
libkf5auth5 (>= 4.96.0) |
libkf5baloo5 (>= 5.15.0) |
libkf5bookmarks5 (>= 4.96.0) |
libkf5codecs5 (>= 4.96.0) |
libkf5completion5 (>= 4.97.0) |
libkf5configcore5 (>= 5.24.0) |
libkf5configgui5 (>= 5.25.0) |
libkf5configwidgets5 (>= 5.7.0+git20150228.0110+15.04) |
libkf5coreaddons5 (>= 5.4.0+git20141202.0008+15.04) |
libkf5dbusaddons5 (>= 4.99.0) |
libkf5emoticons-bin |
libkf5emoticons5 (>= 4.96.0) |
libkf5globalaccel5 (>= 5.10.0) |
libkf5guiaddons5 (>= 4.96.0) |
libkf5i18n5 (>= 5.0.0) |
libkf5iconthemes5 (>= 5.0.0) |
libkf5itemmodels5 (>= 5.14.0) |
libkf5itemviews5 (>= 4.96.0) |
libkf5jobwidgets5 (>= 4.96.0) |
libkf5kcmutils5 (>= 4.96.0) |
libkf5kdelibs4support5 (>= 4.99.0) |
libkf5kiocore5 (>= 5.2.0) |
libkf5kiofilewidgets5 (>= 4.96.0) |
libkf5kiowidgets5 (>= 5.24.0) |
libkf5newstuff5 (>= 5.27.0) |
libkf5notifications5 (>= 5.3.0+git20141030.0311) |
libkf5notifyconfig5 (>= 5.24.0) |
libkf5parts5 (>= 4.96.0) |
libkf5people5 |
libkf5peoplewidgets5 |
libkf5plasma5 (>= 5.2.0) |
libkf5plasmaquick5 (>= 4.98.0) |
libkf5quickaddons5 (>= 5.8.0+git20150324.0130+15.04) |
libkf5runner5 (>= 5.24.0) |
libkf5service-bin |
libkf5service5 (>= 5.2.0+git20140930) |
libkf5solid5 (>= 4.97.0) |
libkf5sonnetui5 (>= 4.96.0) |
libkf5wallet-bin |
libkf5wallet5 (>= 4.96.0) |
libkf5widgetsaddons5 (>= 5.3.0+git20141027.0844) |
libkf5windowsystem5 (>= 5.25.0) |
libkf5xmlgui5 (>= 4.98.0) |
libkfontinst5 |
libkfontinstui5 |
libkworkspace5-5 (>= 4:5.8.1) |
libpackagekitqt5-0 |
libphonon4qt5-4 (>= 4:4.8.0) |
libpulse-mainloop-glib0 (>= 0.99.1) |
libpulse0 (>= 0.99.1) |
libqt5concurrent5 (>= 5.6.0~rc) |
libqt5core5a (>= 5.7.0) |
libqt5dbus5 (>= 5.5.0~) |
libqt5gui5 (>= 5.7.0) |
libqt5network5 (>= 5.5.0~) |
libqt5printsupport5 (>= 5.5.0~) |
libqt5qml5 (>= 5.0.2) |
libqt5quick5 (>= 5.6.1) |
libqt5quickwidgets5 (>= 5.4.0) |
libqt5sql5 (>= 5.5.0~) |
libqt5svg5 (>= 5.6.0~beta) |
libqt5widgets5 (>= 5.5.0~) |
libqt5x11extras5 (>= 5.6.0) |
libqt5xml5 (>= 5.5.0~) |
libscim8v5 (>= 1.4) |
libstdc++6 (>= 5.2) |
libtaskmanager6 (>= 4:5.8.1) |
libx11-6 (>= 2:1.2.99.901) |
libx11-xcb1 |
libxcb-record0 |
libxcb-xkb1 |
libxcb1 |
libxcursor1 (>> 1.1.2) |
libxfixes3 |
libxi6 (>= 2:1.2.99.4) |
libxkbfile1 |
phonon4qt5 |


Recommends (Version) | Installed
==-+-===
bluedevil | 4:5.8.4-1
fonts-noto | 20161116-1
fonts-oxygen | 4:5.4.3-2
gtk3-engines-breeze | 5.8.4-1
kde-config-gtk-style | 4:5.8.4-1
kde-config-screenlocker | 5.8.4-1
kde-config-sddm | 4:5.8.4-1
kde-style-oxygen-qt5 | 4:5.8.4-1
kgamma5 | 5.8.4-1
khelpcenter | 4:16.08.3-1
khotkeys | 4:5.8.4-1
kinfocenter | 4:5.8.4-1
kio-extras | 4:16.08.3-1
kmenuedit | 4:5.8.4-1
kscreen | 4:5.8.4-1
ksshaskpass | 4:5.8.4-1
ksysguard | 4:5.8.4-1
kwin-x11 | 4:5.8.4-1
OR kwin |
kwrited | 4:5.8.4-1
libpam-kwallet5 | 5.8.4-1
plasma-discover | 5.8.3-1
plasma-pa | 4:5.8.4-1
powerdevil | 4:5.8.4-1
sni-qt | 0.2.7+15.10.20150729-2
systemsettings | 4:5.8.4-1
user-manager | 4:5.8.4-1


Package's Suggests field is empty.



-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
/tmp/reportbug-ng-plasma-desktop-YPf33y.txt
to the mail.

Processed: Re: Merging two bugs

2017-01-01 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> forcemerge 845662 849824
Bug #845662 [libqt5core5a] libqt5core5a: Segfault in QObject::disconnect
Bug #849824 [libqt5core5a] calibre crashed with SIGSEGV in QObject::disconnect()
Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-52988'.
Marked as found in versions qtbase-opensource-src/5.7.1~20161021+dfsg-6.
Merged 845662 849824
> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
845662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845662
849824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): Merging two bugs

2017-01-01 Thread Debian Bug Tracking System

Processing commands for cont...@bugs.debian.org:

> notfound 849824 2.71.0+dfsg-1
Bug #849824 [libqt5core5a] calibre crashed with SIGSEGV in QObject::disconnect()
There is no source info for the package 'libqt5core5a' at version 
'2.71.0+dfsg-1' with architecture ''
Unable to make a source version for version '2.71.0+dfsg-1'
No longer marked as found in versions 2.71.0+dfsg-1.
> severity 849824 important
Bug #849824 [libqt5core5a] calibre crashed with SIGSEGV in QObject::disconnect()
Severity set to 'important' from 'normal'
> merge 845662 849824
Bug #845662 [libqt5core5a] libqt5core5a: Segfault in QObject::disconnect
Unable to merge bugs because:
forwarded of #849824 is '' not 'https://bugreports.qt.io/browse/QTBUG-52988'
Failed to merge 845662: Did not alter merged bugs.

> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
845662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845662
849824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: konsole --version crashes

Bug#849890: korganizer: korgac crashes every time I login into a KDE session

Re: Bug#1 Freeze

Bug#792594: libqt5qml5 requires SSE2 on i386

Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines

Re: konsole --version crashes

Re: konsole --version crashes

Bug#849877: konsole --version crashes

Re: Plasma 5.8.5 coming and some other rough status information

Bug#849868: kde-plasma-desktop: Middle button causes yellow box that can't be removed

Bug#792594: libqt5qml5 requires SSE2 on i386

Bug#849854: [plasma-desktop] nm-applet cannot be interracted with from Plasma panel tray

Processed: Re: Merging two bugs

Processed (with 1 error): Merging two bugs

14 matches

Site Navigation

Mail list logo

Footer information