Bug#913679: kopete: libjingle-call keeps crashing

2018-11-13 Thread Oswald Buddenhagen
Package: kopete
Version: 4:17.08.3-2
Severity: important

when an xmpp account is configured and "Enable libjingle support" is
enabled, kopete will spawn libjingle-call (being online is apparently
sufficient). this will immediately crash, leaving such an entry in
the journal:

Nov 14 00:23:30 host kernel: libjingle-call[6998]: segfault at 48 ip 
7fa8d882ec73 sp 7ffe90fdb610 error 4 in 
libcrypto.so.1.1[7fa8d87f1000+19f000]
Nov 14 00:23:30 host kernel: Code: 40 24 01 00 00 00 4c 89 e2 c7 40 50 01 00 00 
00 0f ae f0 e8 ff 35 fc ff 85 c0 74 6c e8 86 4c fc ff 48 89 43 70 48 85 c0 74 
2d <48> 8b 45 48 48 85 c0 74 74 48 89 df ff d0 85 c0 0f 84 a7 00 00 00 [...]

the executable will be instantly respawned, which on my system produces
about six entries per second. within some hours, the disk fills up,
rendering the system unusable.

the non-existing handling of the "keeps crashing" situation is certainly
an upstream issue. but the crash itself may be related to the packaging.

here's an actual backtrace:

#0  BIO_new (method=0x0) at ../crypto/bio/bio_lib.c:94
#1  0x555fe062667a in BIO_new_socket (socket=0x555fe17fee08) at 
./protocols/jabber/libjingle/talk/base/openssladapter.cc:123
#2  0x555fe0626fc3 in talk_base::OpenSSLAdapter::BeginSSL 
(this=this@entry=0x555fe17fef10) at 
./protocols/jabber/libjingle/talk/base/openssladapter.cc:345
#3  0x555fe0627122 in talk_base::OpenSSLAdapter::StartSSL 
(hostname=0x555fe17ff700 "kde.org", restartable=, 
this=0x555fe17fef10) at 
./protocols/jabber/libjingle/talk/base/openssladapter.cc:320
#4  talk_base::OpenSSLAdapter::StartSSL (this=0x555fe17fef10, 
hostname=0x555fe17ff700 "kde.org", restartable=) at 
./protocols/jabber/libjingle/talk/base/openssladapter.cc:307
#5  0x555fe0799413 in XmppSocket::StartTls (domainname=..., 
this=0x555fe17fdca0) at /usr/include/c++/8/bits/basic_string.h:2290
#6  XmppSocket::StartTls (this=0x555fe17fdca0, domainname=...) at 
./protocols/jabber/libjingle/talk/examples/login/xmppsocket.cc:227
#7  0x555fe07749e3 in buzz::XmppEngineImpl::StartTls (this=0x555fe17ff610, 
domain=...) at /usr/include/c++/8/bits/basic_string.h:1031
#8  0x555fe0777507 in buzz::XmppLoginTask::Advance 
(this=this@entry=0x555fe17ffe60) at 
./protocols/jabber/libjingle/talk/xmpp/jid.h:55
#9  0x555fe0777c20 in buzz::XmppLoginTask::Advance (this=0x555fe17ffe60) at 
./protocols/jabber/libjingle/talk/xmpp/xmpplogintask.cc:98
#10 buzz::XmppLoginTask::IncomingStanza (this=0x555fe17ffe60, 
element=element@entry=0x555fe1801a90, isStart=isStart@entry=false) at 
./protocols/jabber/libjingle/talk/xmpp/xmpplogintask.cc:85
#11 0x555fe0773c16 in buzz::XmppEngineImpl::IncomingStanza 
(this=0x555fe17ff610, stanza=0x555fe1801a90) at 
./protocols/jabber/libjingle/talk/xmpp/xmppengineimpl.cc:306
#12 0x555fe0777dbf in buzz::XmppStanzaParser::IncomingEndElement 
(name=, pctx=, this=0x555fe17ff628) at 
./protocols/jabber/libjingle/talk/xmpp/xmppstanzaparser.cc:93
#13 buzz::XmppStanzaParser::IncomingEndElement (this=0x555fe17ff628, 
pctx=, name=) at 
./protocols/jabber/libjingle/talk/xmpp/xmppstanzaparser.cc:82
#14 0x7f4731f203ff in doContent (parser=parser@entry=0x555fe17ff920, 
startTagLevel=startTagLevel@entry=0, enc=, s=, 
end=0x555fe18005cb "", nextPtr=0x555fe17ff950, haveMore=1 '\001')
at ../../src/lib/xmlparse.c:2924
#15 0x7f4731f214bc in contentProcessor (parser=0x555fe17ff920, 
start=, end=, endPtr=) at 
../../src/lib/xmlparse.c:2552
#16 0x7f4731f23a06 in XML_ParseBuffer (parser=0x555fe17ff920, len=50, 
isFinal=0) at ../../src/lib/xmlparse.c:1988
#17 0x555fe074d9c3 in buzz::XmlParser::Parse (this=0x555fe17ff640, 
data=, len=, isFinal=isFinal@entry=false) at 
./protocols/jabber/libjingle/talk/xmllite/xmlparser.cc:172
#18 0x555fe074dbe8 in buzz::XmlParser::Parse (this=, 
data=, len=, isFinal=isFinal@entry=false) at 
./protocols/jabber/libjingle/talk/xmllite/xmlparser.cc:169
#19 0x555fe0774cad in buzz::XmppStanzaParser::Parse (isFinal=false, 
len=, data=, this=) at 
./protocols/jabber/libjingle/talk/xmpp/xmppstanzaparser.h:52
#20 buzz::XmppEngineImpl::HandleInput (this=, bytes=, len=) at 
./protocols/jabber/libjingle/talk/xmpp/xmppengineimpl.cc:109
#21 0x555fe076fef4 in buzz::XmppClient::Private::OnSocketRead 
(this=0x555fe17fd370) at 
./protocols/jabber/libjingle/talk/xmpp/xmppclient.cc:350
#22 0x555fe0799805 in 
sigslot::signal0::operator() (this=0x555fe17fdd08) at 
/usr/include/c++/8/bits/stl_list.h:301
#23 XmppSocket::OnReadEvent (this=0x555fe17fdca0, socket=) at 
./protocols/jabber/libjingle/talk/examples/login/xmppsocket.cc:88
#24 0x555fe0626e58 in sigslot::signal1::operator() (a1=0x555fe17fef10, this=0x555fe17fef18) 
at /usr/include/c++/8/bits/stl_list.h:301
#25 talk_base::AsyncSocketAdapter::OnReadEvent (socket=, 
this=0x555fe17fef10) at ./protocols/jabber/libjingle/talk/base/asyncsocket.h:119
#26 talk_base::OpenSSLAdapter::OnReadEvent (this=0x555fe17fef10, 
socket=) at 

Bug#913644: /usr/bin/plasmashell: crash on startup

2018-11-13 Thread Arthur Marsh
Package: plasma-workspace
Version: 4:5.13.5-1+b1
Severity: important
File: /usr/bin/plasmashell

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Upgrading packages that plasmashell depended on.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Downgrading the packages.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Output from when attempting to run plasmashell now:

$ plasmashell
Invalid Context= "places" line for icon theme:  
"/usr/share/icons/DarkPurpy/48x48/places/"
org.kde.plasmaquick: Applet preload policy set to 1
Empty filename passed to function
last screen is < 0 so putting containment on screen  0
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/bin/plasmashell directly
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 21165
KCrash: Arguments: /usr/bin/plasmashell 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi directly
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
"Message recipient disconnected from message bus without replying"
QSystemTrayIcon::setVisible: No Icon set

[1]+  Stopped plasmashell


-- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.10-1+devuan1
ii  drkonqi  5.13.4-1
ii  frameworkintegration 5.51.0-1
ii  gdb  8.1-4+b1
ii  iso-codes4.1-1
ii  kactivitymanagerd5.13.5-1
ii  kded55.51.0-1
ii  kinit5.51.0-1
ii  kio  5.51.0-1
ii  kpackagetool55.51.0-1
ii  kwin-common  4:5.13.5-1+b1
ii  libappstreamqt2  0.12.3-1
ii  libc62.27-8
ii  libcln6  1.3.4-4
ii  libcolorcorrect5 4:5.13.5-1+b1
ii  libgcc1  1:8.2.0-9
ii  libgps23 3.17-5+b1
ii  libice6  2:1.0.9-2
ii  libkf5activities55.51.0-1
ii  libkf5auth5  5.51.0-1
ii  libkf5baloo5 5.51.0-1
ii  libkf5bookmarks5 5.51.0-1
ii  libkf5calendarevents55.51.0-1
ii  libkf5completion55.51.0-1
ii  libkf5config-bin 5.51.0-1
ii  libkf5configcore55.51.0-1
ii  libkf5configgui5 5.51.0-1
ii  libkf5configwidgets5 5.51.0-1
ii  libkf5coreaddons55.51.0-1
ii  libkf5crash5 5.51.0-1
ii  libkf5dbusaddons55.51.0-1
ii  libkf5declarative5   5.51.0-1
ii  libkf5globalaccel-bin5.51.0-1
ii  libkf5globalaccel5   5.51.0-1
ii  libkf5guiaddons5 5.51.0-1
ii  libkf5holidays5  1:5.51.0-1
ii  libkf5i18n5  5.51.0-1
ii  libkf5iconthemes55.51.0-1
ii  libkf5idletime5  5.51.0-1
ii  libkf5itemviews5 5.51.0-1
ii  libkf5jobwidgets55.51.0-1
ii  libkf5js55.51.0-1
ii  libkf5jsembed5   5.51.0-1
ii  libkf5kdelibs4support5   5.51.0-1
ii  libkf5kiocore5   5.51.0-1
ii  libkf5kiofilewidgets55.51.0-1
ii  libkf5kiogui55.51.0-1
ii  libkf5kiowidgets55.51.0-1
ii  libkf5networkmanagerqt6  5.51.0-1
ii  libkf5newstuff5  5.51.0-1
ii  libkf5notifications5 5.51.0-1

Bug#884956: HiDPI scaling is still broken with libqt5core5a 5.10.1+dfsg-6

2018-11-13 Thread Dmitry Shachnev
Hi Vincent and all!

On Sun, May 06, 2018 at 11:09:09AM +0200, Vincent Lefevre wrote:
> Control: reopen -1
> Control: found -1 5.10.1+dfsg-6
>
> The bug is still there. The upgrade of the qtbase-opensource-src
> packages to 5.10.1+dfsg-6 had no effect.

Can you please check if this is still an issue with qtbase 5.11.2+dfsg-4?

There have been some upstream changes in 5.11.x, plus I have backported
this commit [1] which may make things better.

[1]: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=5e6bbbc1b86905c4

--
Dmitry Shachnev


signature.asc
Description: PGP signature