Bug#807902: konsole: segfault on exit

[Dominik George]

Package: konsole
Version: 4:15.08.3-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Recently, Konsole started crashing when closing the last tab and exiting:

Application: konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7ff3c82a51b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7ff3c829b5dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7ff3c829bc79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7ff3c82902ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7ff3c8290399 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x7ff3c7be2f52 in __run_exit_handlers (status=0, listp=0x7ff3c7f4b698 
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#12 0x7ff3c7be2fa5 in __GI_exit (status=) at exit.c:104
#13 0x7ff3c7bcd877 in __libc_start_main (main=0x400710 , argc=1, 
argv=0x7fffdd5d0328, init=, fini=, 
rtld_fini=, stack_end=0x7fffdd5d0318) at libc-start.c:325
#14 0x00400749 in _start ()

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: systemd (via /run/systemd/system)

Versions of packages konsole depends on:
ii  konsole-kpart   4:15.08.3-1
ii  libc6   2.21-4
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libqt5core5a5.5.1+dfsg-8
ii  libqt5gui5  5.5.1+dfsg-8
ii  libqt5widgets5  5.5.1+dfsg-8
ii  libstdc++6  5.3.1-3

konsole recommends no packages.

konsole suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJOBAEBCAA4BQJWbp8OMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pY+hBAA29FL7JlCDi1kwBf6bvzB
x4/OkPgdDfS1PPP4t0e3ry/f6vR26lfLEslNiNMGrKAiBms/FljWWcM2OojeqQUj
bKKNCOPEUX9AzVXTzbdLVX7EyNt9WuBfIYGkx0aL10IyVJoeH7Vhl9lnW5CN4DRL
MyFGtaoCuj7bZVip215PYEl+fVanXC9H8BopYjV1RudrYE93doyjJ4EfK/6UDKVr
K4KY5ZO46dFMfV6R8uTFG7kPwz/l1aHkDMbvk18ntlrZt0oNnfa34dh7zazlH0oJ
TxqT35tVeX8YKYon9tbssrsDTnHjisqiIcuvXr7MIlazo6KDhNltAv8cw3jEvj99
AiUdi6VG+1xdtkGEa7YcKs/6H+DG+SqpZhNfhwmkxB0G5k/aZZrIgFseLKGu1VHs
6KjEIMXEemDPALgic7BEKcAqVV1Pl6NFUe9JVhaJFXKaUTx9mCo3Js3QjWbV3zDy
9T2aBOjxtLBNVhDHGUjflsSadJnnTUk+bSLXUFNwn5b93yNXNvrThVaZ0pmoXsY4
OBkHwc4t4wXLct1GSHlFo9BcuQQA6aZx6Ifpr7zx8SRL7OxrW4I40pVAhlFKuw/i
uvkQS/Ejbbk95jqr30L/JFpBirYV2udwCtXXahIUkIjZ4W6VOF/YUIM9BDPPBt/z
UoBeYq1/YXNM+K7FT0D6/Kw=
=qN5i
-END PGP SIGNATURE-

Re: Just lost my digikam -- no longer installable :-(

[Steve M. Robbins]

On November 14, 2015 11:03:31 AM Steve M. Robbins wrote:

> The present package is not installable and, judging from the BTS, not
> buildable.  The last upload is about a year ago, though I see 4.12 in the
> VCS (2 months ago).  Upstream released 4.14 a month ago.  However it's
> unclear to me whether a 4.x version will even work with Sid's libraries
> (KDE Frameworks 5.13, Plasma 5.4 and Applications 15.04, according to
> https://wiki.debian.org/KDE). 

Despite what I wrote above, I note that package "kde5libs-dev" currently 
contains (on sid) "kde4libs (4:4.14.14-1)".  I admit this numbering scheme 
confuses me, but it seems that mainstream KDE is really using KDE 4.  (?)

Anyway, despite Eric V's advice to jump to digikam 5, I went ahead and did a 
local rebuild of digikam 4.14 and it seems to run fine.  

Question for the Debian-Qt-Kde folks: do you agree with upgrading to digikam 
4.14?  If so, what is the best way to get updated digikam in archive?   I have 
just sent a request to join the Alioth project.   If accepted, should I go 
ahead and update that?

Thanks,
-Steve


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

Bug#808001: cantor: add support for julia (julialang.org

[Hormet Yiltiz]

Package: cantor
Version: 4:4.14.2-3
Severity: wishlist

Dear Maintainer,

Julia is a high-level, high-performance dynamic programming language for 
technical computing, with syntax that is familiar to users of other technical 
computing environments. It provides a sophisticated compiler, distributed 
parallel execution, numerical accuracy, and an extensive mathematical function 
library.

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

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

Versions of packages cantor depends on:
ii  kde-runtime 4:15.08.3-1
ii  libc6   2.19-22
ii  libkdecore5 4:4.14.14-1
ii  libkdeui5   4:4.14.14-1
ii  libkio5 4:4.14.14-1
ii  libknewstuff3-4 4:4.14.14-1
ii  libkparts4  4:4.14.14-1
ii  libktexteditor4 4:4.14.14-1
ii  libqt4-xml  4:4.8.7+dfsg-5
ii  libqt4-xmlpatterns  4:4.8.7+dfsg-5
ii  libqtcore4  4:4.8.7+dfsg-5
ii  libqtgui4   4:4.8.7+dfsg-5
ii  libspectre1 0.2.7-3
ii  libstdc++6  5.2.1-23

Versions of packages cantor recommends:
ii  cantor-backend-kalgebra  4:4.14.2-3
ii  texlive-binaries 2015.20150524.37493-7
ii  texlive-latex-base   2015.20151116-1

Versions of packages cantor suggests:
pn  cantor-backend-lua
pn  cantor-backend-maxima 
ii  cantor-backend-octave 4:4.14.2-3
pn  cantor-backend-python2
pn  cantor-backend-qalculate  
ii  cantor-backend-r  4:4.14.2-3
pn  cantor-backend-sage   
pn  cantor-backend-scilab 

-- no debconf information

Bug#807902: konsole: segfault on exit

[Diederik de Haas]

On Monday 14 December 2015 11:51:01 Dominik George wrote:
> Package: konsole
> Version: 4:15.08.3-1
> Severity: normal
> 
> Recently, Konsole started crashing when closing the last tab and exiting:

With me it's not recently but has been happening for a while already.
Here's a stacktrace I just got with a Konsole crash:

Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f8ddf029657 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f8ddf02aa2a in __GI_abort () at abort.c:89
#8  0x7f8ddf067bb3 in __libc_message (do_abort=do_abort@entry=1, 
fmt=fmt@entry=0x7f8ddf1605f8 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
#9  0x7f8ddf06d00e in malloc_printerr (action=1, str=0x7f8ddf1606c0 "double 
free or corruption (out)", ptr=) at malloc.c:4965
#10 0x7f8ddf06d7eb in _int_free (av=, p=, 
have_lock=0) at malloc.c:3834
#11 0x7f8ddbc80aec in QMetaCallEvent::~QMetaCallEvent() 
(this=0x7f8dc4005780, __in_chrg=) at kernel/qobject.cpp:468
#12 0x7f8ddbc80b39 in QMetaCallEvent::~QMetaCallEvent() 
(this=0x7f8dc4005780, __in_chrg=) at kernel/qobject.cpp:476
#13 0x7f8ddbc57727 in QCoreApplication::removePostedEvents(QObject*, int) 
(receiver=0x1b9ed10, eventType=eventType@entry=0) at 
kernel/qcoreapplication.cpp:1670
#14 0x7f8ddbc82e42 in QObjectPrivate::~QObjectPrivate() (this=0x1b9f070, 
__in_chrg=) at kernel/qobject.cpp:235
#15 0x7f8ddbc82f69 in QObjectPrivate::~QObjectPrivate() (this=0x1b9f070, 
__in_chrg=) at kernel/qobject.cpp:246
#16 0x7f8ddbc8b558 in QObject::~QObject() (pointer=) at 
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:54
#17 0x7f8ddbc8b558 in QObject::~QObject() (this=0x1b9ed18, 
__in_chrg=) at 
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:101
#18 0x7f8ddbc8b558 in QObject::~QObject() (this=, 
__in_chrg=) at kernel/qobject.cpp:883
#19 0x7f8dcb556619 in QXcbConnection::~QXcbConnection() (this=0x1b9ed10, 
__in_chrg=) at qxcbconnection.cpp:635
#20 0x7f8dcb5580b6 in QXcbIntegration::~QXcbIntegration() (end=..., 
begin=...) at 
../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:317
#21 0x7f8dcb5580b6 in QXcbIntegration::~QXcbIntegration() (c=...) at 
../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:325
#22 0x7f8dcb5580b6 in QXcbIntegration::~QXcbIntegration() (this=0x1bb8d30, 
__in_chrg=) at qxcbintegration.cpp:190
#23 0x7f8dcb5581c9 in QXcbIntegration::~QXcbIntegration() (this=0x1bb8d30, 
__in_chrg=) at qxcbintegration.cpp:192
#24 0x7f8ddbf8d9a3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() 
(this=0x1bb9be0, __in_chrg=) at kernel/qguiapplication.cpp:1390
#25 0x7f8ddc544029 in QApplicationPrivate::~QApplicationPrivate() 
(this=0x1bb9be0, __in_chrg=) at kernel/qapplication.cpp:192
#26 0x7f8ddbc8b558 in QObject::~QObject() (pointer=) at 
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:54
#27 0x7f8ddbc8b558 in QObject::~QObject() (this=0x7ffe9f3752a8, 
__in_chrg=) at 
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:101
#28 0x7f8ddbc8b558 in QObject::~QObject() (this=, 
__in_chrg=) at kernel/qobject.cpp:883
#29 0x7f8ddc545e19 in QApplication::~QApplication() (this=0x7ffe9f3752a0, 
__in_chrg=) at kernel/qapplication.cpp:816
#30 0x7f8ddf3bb375 in kdemain(int, char**) (argc=1, argv=0x7ffe9f3753e8) at 
../../src/main.cpp:110
#31 0x7f8ddf016870 in __libc_start_main (main=0x400710 , 
argc=1, argv=0x7ffe9f3753e8, init=, fini=, 
rtld_fini=, stack_end=0x7ffe9f3753d8) at libc-start.c:291
#32 0x00400749 in _start () at ../sysdeps/x86_64/start.S:118


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

Bug#806689: vlc: crashed (SIGSEGV) after gnome-shell crash

[Lisandro Damián Nicanor Pérez Meyer]

On Sunday 13 December 2015 22:33:03 Sebastian Ramacher wrote:
> Control: retitle -1 QXcbConnection: XCB error when gnome-shell crashes
> Control: reassign -1 libqt5xcbqpa5 5.5.1+dfsg-8
> 
> On 2015-12-11 22:54:51, Paul Wise wrote:
> > On Fri, 2015-12-11 at 10:59 +0800, Paul Wise wrote:
> > > Unfortunately I can't reproduce the gnome-shell crash so I can't
> > > reproduce the bug using the test program. I ran the test program and
> > > attached/detached my external monitor but didn't get any crash.
> > > If this bug isn't useful, perhaps it should be closed?
> 
> I'll let the Qt 5 maintainers decide about that. Dmitry recently mentioned
> in #804964 that fixes for crashes in QXcbWindow were merged for Qt 5.6.

Hi! in the original bug report I saw:

[02050da8] qt4 interface debug: requesting exit...

Qt5 and Qt4 should not be mixed. This normally happens with qt4 plugins still 
being available, IIRC there was a cache thing that made vlc not remove t's qt4 
plugins. It can be of course an old string which didn't get updated :-/

Sebastian: do you know where this can come from?

Anyways as Sebastian said there are still rough edges wrt screen handling, 
which we will need to recheck in 5.6.

I would like to keep this open until we know the problem wasn't qt4 and qt5 
being mixed. If that wasn't the issue and we can't reproduce it then I think 
we better close it, and of course re opening it later if the bug still 
appears.

Kinds regards, Lisandro.

-- 
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#806689: vlc: crashed (SIGSEGV) after gnome-shell crash

[Sebastian Ramacher]

Hi

On 2015-12-14 16:57:34, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Sunday 13 December 2015 22:33:03 Sebastian Ramacher wrote:
> > Control: retitle -1 QXcbConnection: XCB error when gnome-shell crashes
> > Control: reassign -1 libqt5xcbqpa5 5.5.1+dfsg-8
> > 
> > On 2015-12-11 22:54:51, Paul Wise wrote:
> > > On Fri, 2015-12-11 at 10:59 +0800, Paul Wise wrote:
> > > > Unfortunately I can't reproduce the gnome-shell crash so I can't
> > > > reproduce the bug using the test program. I ran the test program and
> > > > attached/detached my external monitor but didn't get any crash.
> > > > If this bug isn't useful, perhaps it should be closed?
> > 
> > I'll let the Qt 5 maintainers decide about that. Dmitry recently mentioned
> > in #804964 that fixes for crashes in QXcbWindow were merged for Qt 5.6.
> 
> Hi! in the original bug report I saw:
> 
> [02050da8] qt4 interface debug: requesting exit...

qt4 is just the name of vlc's Qt module. In Debian (testing and unstable) it's
built against Qt 5:

$ ldd -r /usr/lib/vlc/plugins/gui/libqt4_plugin.so | grep Qt
libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 
(0x7f04d6d38000)
libQt5X11Extras.so.5 => /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5 
(0x7f04d6b22000)
libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 
(0x7f04d65d9000)
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 
(0x7f04d6101000)

Qt 4 and Qt 5 are not mixed.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: tagging 802861

[Debian Bug Tracking System]

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

> tags 802861 + stretch
Bug #802861 [src:kalzium] kalzium: FTBFS: gasCalculator.h: error: expected 
unqualified-id before numeric constant
Ignoring request to alter tags of bug #802861 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 802861

[Debian Bug Tracking System]

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

> tags 802861 + stretch
Bug #802861 [src:kalzium] kalzium: FTBFS: gasCalculator.h: error: expected 
unqualified-id before numeric constant
Added tag(s) stretch.
> thanks
Stopping processing here.

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