Your message dated Fri, 7 May 2010 16:21:46 +0200
with message-id <20100507142146.ga31...@feivel.credativ.lan>
and subject line Closing
has caused the Debian Bug report #562974,
regarding quassel-client: Quassl client segfaults on first run
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
562974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quassel-client
Version: 0.5.1-1
Severity: grave
Justification: renders package unusable
When I install quassel-client from Debian sid and run it on
my system, I get the following output:
Quassel IRC: "0.5.1" "7cae1afb038d2222d318da11c3bce23c9240eed0"
# 0 quasselclient 0x082af322 Quassel::logBacktrace(QString const&)
# 1 quasselclient 0x08297f58 Quassel::handleSignal(int)
# 2 0x00e7e400 __kernel_sigreturn
# 3 libQtCore.so.4 0x00276750 QVariant::QVariant(QVariant const&)
# 4 libQtDBus.so.4 0x005ae6a0 QDBusPendingReplyData::argumentAt(int)
const
# 5 quasselclient 0x080f7137
DesktopNotificationBackend::DesktopNotificationBackend(QObject*)
# 6 quasselclient 0x080dc17a MainWin::init()
# 7 quasselclient 0x080d0806 QtUiApplication::init()
# 8 quasselclient 0x080ce296 main
# 9 libc.so.6 0x00730b35 __libc_start_main
# 10 quasselclient 0x080cd731 0x00000000
It seems to be segfaulting. Do you have any suggestions?
Does it work for others? If so, maybe there's something environmental
on my system it's allergic to, and we can get a fix upstreamed.
(I'm happy to let the maintainer or other Quassel developers log in to my
machine
to try things.)
-- Asheesh.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-8-generic (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages quassel-client depends on:
ii dbus-x11 1.2.14-3 simple interprocess messaging syst
ii libc6 2.10.1-7 GNU C Library: Shared libraries
ii libgcc1 1:4.4.0-6 GCC support library
ii libqt4-dbus 4:4.5.3-4 Qt 4 D-Bus module
ii libqt4-network 4:4.5.3-4 Qt 4 network module
ii libqt4-webkit 4:4.5.3-4 Qt 4 WebKit module
ii libqtcore4 4:4.5.3-4 Qt 4 core module
ii libqtgui4 4:4.5.3-4 Qt 4 GUI module
ii libstdc++6 4.4.0-6 The GNU Standard C++ Library v3
ii quassel-data 0.5.1-1 distributed IRC client using a cen
Versions of packages quassel-client recommends:
pn quassel-core <none> (no description available)
quassel-client suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
With 0.6.1-1 already in squeeze this bug appears to be juts forgotten and thus
can be closed. At least it says the bug was closed in 0.6.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
--- End Message ---
