Debian Bug report logs - #774860
quassel-core crashes on client connect

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Florian Kraus <flo@flotografiert.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: quassel-core crashes on client connect

Date: Thu, 08 Jan 2015 14:43:22 +0100

Package: quassel-core
Version: 0.8.0-1+deb7u3
Severity: normal

Dear Maintainer,

quasselcore (0.8.0-1+deb7u3 on wheezy) crashes when trying to connect to it
from a client (1:0.10.0-2.2 on jessie).
The initial configuration seems to work though, but after that it crashes.

2015-01-08 13:31:04 Info: SQLite Storage Backend is ready. Quassel Schema
Version: 17
2015-01-08 13:31:04 Info: Listening for GUI clients on IPv6 :: port 4242 using
protocol version 10
2015-01-08 13:31:14 Info: Client connected from ::FFFF:83EA:42BD%0
2015-01-08 13:31:15 Warning: Peer tried to send package larger than max package
size!
2015-01-08 13:31:15 Warning: Disconnecting ::FFFF:83EA:42BD%0
2015-01-08 13:31:15 Info: Non-authed client disconnected. ::FFFF:83EA:42BD%0
2015-01-08 13:31:15 Info: Client connected from ::FFFF:83EA:42BD%0
2015-01-08 13:31:15 Debug: Starting TLS for Client: ::FFFF:83EA:42BD%0
2015-01-08 13:31:15 Debug: Using compression for Client: ::FFFF:83EA:42BD%0
2015-01-08 13:31:15 Info: Client ::FFFF:83EA:42BD%0 initialized and
authenticated successfully as "ArtooDetoo" (UserId: 1).
2015-01-08 13:31:15 Debug: Quassel IRC:  "0.8.0"
"5988f4cd56e54fbe02e668fd48bf430e80f33f55"
2015-01-08 13:31:15 Debug: #  0 quasselcore          0x000000000054fa84
Quassel::logBacktrace(QString const&)
2015-01-08 13:31:15 Debug: #  1 quasselcore          0x00000000005370ef
Quassel::handleSignal(int)
2015-01-08 13:31:15 Debug: #  2 libc.so.6            0x00007f7e5a0e21e0
0x0000000000000000
2015-01-08 13:31:15 Debug: #  3 libQtScript.so.4     0x00007f7e5b3c7c5e
0x0000000000000000
2015-01-08 13:31:15 Debug: #  4 libQtScript.so.4     0x00007f7e5b44c629
0x0000000000000000
2015-01-08 13:31:15 Debug: #  5 libQtScript.so.4     0x00007f7e5b44cdec
0x0000000000000000
2015-01-08 13:31:15 Debug: #  6 libQtScript.so.4     0x00007f7e5b4ed380
0x0000000000000000
2015-01-08 13:31:15 Debug: #  7 libQtScript.so.4     0x00007f7e5b4ee2fe
QScriptEngine::QScriptEngine(QObject*)
2015-01-08 13:31:15 Debug: #  8 quasselcore          0x00000000004b4b75
CoreSession::CoreSession(UserId, bool, QObject*)
2015-01-08 13:31:15 Debug: #  9 quasselcore          0x0000000000480f99
SessionThread::run()
2015-01-08 13:31:15 Debug: # 10 libQtCore.so.4       0x00007f7e5bda4d0b
0x0000000000000000
2015-01-08 13:31:15 Debug: # 11 libpthread.so.0      0x00007f7e5bb0db50
0x0000000000000000
2015-01-08 13:31:15 Debug: # 12 libc.so.6            0x00007f7e5a18c7bd clone

Kind regards,
Florian Kraus



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.5 (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/dash
Init: systemd (via /run/systemd/system)

Message #10 received at 774860@bugs.debian.org (full text, mbox, reply):

From: Florian Kraus <flo@flotografiert.de>

To: 774860@bugs.debian.org

Subject: Re: Bug#774860: Acknowledgement (quassel-core crashes on client connect)

Date: Thu, 08 Jan 2015 14:50:58 +0100

Obviously reportbug placed my client's system information in the report,
which is not where the program crashes.

Here some info about the server:

Debian Release: Wheezy
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.41-042stab094.8

Send a report that this bug log contains spam.