Package: juk
Version: 4:4.2.2-1
Severity: normal
I have set juk to start in the kde autostart directory; when the environment
loads, all apps in the directory start as expected except juk, below is the
backtrace (debugging symbols installed):
Application: JuK (juk), signal SIGSEGV
[Current
Package: kopete
Version: 4:4.2.2-1
Severity: wishlist
In the KDE 3 releases, kopete had support for this widely used protocol, but
it seems that in the new version it has been dropped. If possible, make
chatting in IRC via kopete possible in KDE4.
-- System Information:
Debian Release:
Package: ktorrent
Version: 3.2.1+dfsg.1-1
Severity: wishlist
It would be nice if the ktorrent developers implemented a plugin
similar to azureus's auto-speed
http://azureuswiki.com/index.php/Auto_Speed . With the
recommended settings given by the aplication options, ktorrent
utilizes most of
On Tuesday 19 May 2009 05:37:35 you wrote:
On Mon, 18 May 09 23:17, Jordan Manolov wrote:
Package: akregator
Version: 4:4.2.2-1
Severity: normal
After fetching feeds - about 75-100 - and marking them as read,
akregator always crashes. Here is the backtrace:
Application: Akregator
Package: akregator
Version: 4:4.2.2-1
Severity: normal
After fetching feeds - about 75-100 - and marking them as read,
akregator always crashes. Here is the backtrace:
Application: Akregator (akregator), signal SIGSEGV
Thread 1 (Thread 0xb4fae710 (LWP 12671)):
#0 0xb7f61424 in
Package: azureus
Version: 3.1.1.0-4
Severity: normal
After running for several days without being stopped, azureus uses about
70-75% of RAM, according to top. Azureus changelog reports that corrections
of memory consumption have been made in version 4 of the program. I suggest a
newer azureus
Package: kiten
Version: 4:3.5.9-2
Severity: wishlist
Currently, at least the version I am using (on Debian Testing), lacks one
feature: that is showing the order of the strokes when writing Kanji. I am
aware that implementing such a feature needs a lot of time and effort, but at
least some
Package: ruby-elisp
Version: 4.2
Severity: normal
When writing Ruby code in emacs, all variables are highlighted with one color;
what's more, placing a # sigh before a variable does not mark it as commented
out, when it should. Also, constants, methods and class names are with one
and the same
8 matches
Mail list logo
