[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#516967: marked as done ([kdebase-runtime] knotify always crashes on new messages in kopete)

Your message dated Tue, 6 Apr 2010 14:03:21 +0200
with message-id <201004061403.22180.ewoerner@kde.org>
and subject line Re: [kdebase-runtime] knotify always crashes on new messages in kopete
has caused the Debian Bug report #516967,
regarding [kdebase-runtime] knotify always crashes on new messages in kopete
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 owner@bugs.debian.org
immediately.)


-- 
516967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516967
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kdebase-runtime
Version: 4:4.2.0-1
Severity: important


This is the error message, it always appears when someone sends me a
message in kopete:

The application KNotify (knotify4) crashed and caused the signal 11
(SIGSEGV).
Please help us improve the software you use by filing a report at
http://bugs.kde.org. Useful details include how to reproduce the error,
documents that were loaded, etc.


Cheers,

Bastian



--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.28-1-686

Debian Release: 5.0
  500 unstable        ftp.de.debian.org
  500 unstable        debian-multimedia.org
    1 experimental    ftp.de.debian.org

--- Package information. ---
Depends                           (Version) | Installed
===========================================-+-===============
kdelibs5                       (>= 4:4.2.0) | 4:4.2.0-2
libasound2                      (>> 1.0.16) | 1.0.16-2
libc6                            (>= 2.7-1) | 2.9-3
libclucene0ldbl               (>= 0.9.20-1) | 0.9.20-3
libgcc1                        (>= 1:4.1.1) | 1:4.3.3-4
libjpeg62                                   | 6b-14
libopenexr6                      (>= 1.6.1) | 1.6.1-3
libphonon4                     (>= 4:4.3.0) | 4:4.3.0-2
libpulse0                        (>= 0.9.8) | 0.9.10-3
libqt4-dbus                      (>= 4.4.3) | 4.4.3-2
libqt4-qt3support                (>= 4.4.3) | 4.4.3-2
libqt4-svg                       (>= 4.4.3) | 4.4.3-2
libqt4-xml                       (>= 4.4.3) | 4.4.3-2
libqtcore4                       (>= 4.4.3) | 4.4.3-2
libqtgui4                        (>= 4.4.3) | 4.4.3-2
libsmbclient                   (>= 2:3.2.0) | 2:3.3.0-3
libsoprano4                     (>= 2.1.67) | 2.2.1+dfsg.1-1
libstdc++6                       (>= 4.2.1) | 4.3.3-4
libstreamanalyzer0               (>= 0.6.2) | 0.6.3-1
libstreams0                      (>= 0.5.5) | 0.6.3-1
libx11-6                                    | 2:1.1.5-2
libxcursor1                      (>> 1.1.2) | 1:1.1.9-1
libxine1                         (>= 1.1.8) | 1.1.16.1-2
kdebase-runtime-bin-kde4      (= 4:4.2.0-1) | 4:4.2.0-1
kdebase-runtime-data         (>= 4:4.2.0-1) | 4:4.2.0-1
kde-icons-oxygen             (>= 4:4.2.0-1) | 4:4.2.0-1
phonon-backend                              |

--- End Message ---
--- Begin Message --- 
Version: 4:4.3.4-1

The bug you reported has (most likely) been fixed in or before KDE SC 4.3.4

--- End Message ---
Reply to: