[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 158476] KTorrent is big bug... It crashed more than 30 times for
From:       Nikita Manovich <nikita.manovich () gmail ! com>
Date:       2008-02-29 7:55:19
Message-ID: 20080229075519.20526.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=158476         




------- Additional Comments From nikita.manovich gmail com  2008-02-29 08:55 -------
May be you are right...

1. All reports are the same (I use standard package from SuSE 10.3):
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of \
proper backtraces, or the stack frame was seriously corrupted in the crash.

System configuration startup check disabled.

[?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

2. May be console output will be useful for you (I got it several minutes ago \
especially for you): process 10009: arguments to dbus_connection_close() were \
incorrect, assertion "connection->generation == _dbus_current_generation" failed in \
file dbus-connection.c line 2740. This is normally a bug in some application using \
the D-Bus library.  D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'ktorrent' crashing...

3. I have serious reason don't use last version for a while.

4. I see a lot of code. I know that pretty code can't crash every time then you click \
on a button. And of course you are right... I have to submit a bug report without all \
the idiocy and personal attacks. I told it was nerves.

5. I believe you spend own free time for support the product, but why you don't  \
respect time of users which use your program... You have a very big responsibility... \
Your program is used by millions of people. From my point of view I can't release \
product which is not tested at all. If you are a very responsible and highly \
responsive maintainer... you understand me...

I believe that the bug-report isn't useful for you and it is time to close it. Think \
about the bug report as a customer feedback. If you customer orientation person you \
will not get such report in the future from other users.


[prev in list] [next in list] [prev in thread] [next in thread]