Bug#285906: kopete: Kopete crashes when ignoring IRC 'query'
Package: kopete
Version: 4:3.3.1-2
Severity: important
When an IRC user initiates a query which causes a KNotify pop-up
notification, ignoring the notification causes Kopete to crash with a
SIGSEGV.
I'm sorry, but I don't have debugging enabled so I can't give a useful
stacktrace, but if nobody else can reproduce this bug then I'll
endeavour to produce a stacktrace.
Thanks,
James
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages kopete depends on:
ii kdelibs4 4:3.3.1-2 KDE core libraries
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi
ii libc6 2.3.2.ds1-19 GNU C Library: Shared libraries an
ii libfam0c102 2.7.0-6 client library to control the FAM
ii libgadu3 1:1.5-4 Gadu-Gadu protocol library - runti
ii libgcc1 1:3.4.3-4 GCC support library
ii libglib1.2 1.2.10-9 The GLib library of C routines
ii libgtk1.2 1.2.10-17 The GIMP Toolkit set of widgets fo
ii libice6 4.3.0.dfsg.1-9 Inter-Client Exchange library
ii libidn11 0.5.2-3 GNU libidn library, implementation
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libpcre3 4.5-1.1 Perl 5 Compatible Regular Expressi
ii libpng12-0 1.2.8rel-1 PNG library - runtime
ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v
ii libsm6 4.3.0.dfsg.1-9 X Window System Session Management
ii libstdc++5 1:3.3.5-3 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-9 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-9 X Window System miscellaneous exte
ii libxi6 4.3.0.dfsg.1-9 X Window System Input extension li
ii libxml2 2.6.11-5 GNOME XML library
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii libxslt1.1 1.1.8-5 XSLT processing library - runtime
ii xlibs 4.3.0.dfsg.1-9 X Keyboard Extension (XKB) configu
ii xmms 1.2.10-1.4 Versatile X audio player that look
ii zlib1g 1:1.2.2-4 compression library - runtime
-- no debconf information
Reply to: