Subject: juk: crash at juk/filehandle.cpp:100
Package: juk
Version: 4:3.5.9-2
Severity: normal
*** Please type your report below this line ***
[Thread debugging using libthread_db enabled]
[New Thread 0xb60536c0 (LWP 25388)]
[KCrash handler]
#6 FileHandle (this=0xbfda0bd8, f...@0x8)
at /buil
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
Your message dated Tue, 24 Feb 2009 18:05:24 -0200
with message-id <200902241805.25562.perezme...@gmail.com>
and subject line Done: [kopete] Kopete crashes on session logout
has caused the Debian Bug report #505499,
regarding [kopete] Kopete crashes on session logout
to be marked as done.
This me
Your message dated Tue, 24 Feb 2009 18:09:49 -0200
with message-id <200902241809.49465.perezme...@gmail.com>
and subject line Done: Crashes on startup
has caused the Debian Bug report #469303,
regarding Crashes on startup
to be marked as done.
This means that you claim that the problem has been d
tag 516967 +moreinfo unreproducible
thanks
Hi!
I use kopete and recieve messages on a daily basis and have never seen this.
/Sune
On Tuesday 24 February 2009 20:06:55 Bastian Venthur wrote:
> Package: kdebase-runtime
> Version: 4:4.2.0-1
> Severity: important
>
>
> This is the error message, it
Your message dated Tue, 24 Feb 2009 21:47:18 +0100
with message-id <49a45cd6.8010...@debian.org>
and subject line Re: Bug#516612: kaddressbook: Post-Lenny gnokii SONAME bump
has caused the Debian Bug report #516612,
regarding kaddressbook: Post-Lenny gnokii SONAME bump
to be marked as done.
This
Package: kdebase-workspace-bin
Version: 4:4.2.0-2
--- Please enter the report below this line. ---
A better backtrace:
Application: Run Command Interface (krunner), signal SIGABRT
0x7fe0a19c08d1 in nanosleep () from /lib/libc.so.6
Current language: auto; currently c
Hi,
any idea how to approach this bug? I always get this message from
Drkonqi when receiving a message. The message itself is ok, kopete is
fully functional otherwise. The problem seams to be with the info-thingy
in the systray.
Cheers,
Bastian
Sune Vuorela schrieb:
> tag 516967 +moreinfo unre
On Tue, 24 Feb 09 21:53, Bastian Venthur wrote:
> Hi,
>
> any idea how to approach this bug? I always get this message from
Uhm, do you get no backtrace from DrKonqi?
Of not try to run knotify from gdb to get a backtrace (and don't forget
to have the relevant debug packages installed).
Greetings
Good morning dear debian-qt-kde team
I just wanted or want to say you thank you for your work on Qt and KDE
packaging for Debian.
Since years I use your packages private and in a school.
You're doing great work and I'm excited to see KDE 4.x coming to unstable and
testing.
Greets and thanks f
Package: kontact
Followup-For: Bug #490981
BUG: KMail crashes when printing to CUPS network printer
I think that I am the original reporter for this bug; if not, I filed a very
similar one. I've been able to print recently from within KMail without
crashing. Thanks.
-- System Information:
De
11 matches
Mail list logo
