![]() Registered Member ![]()
|
Hi Everyone. First off i just want to say I like Ktorrent its awesome. I've had some problems with crashes in the past and was able to fix them. The problem I'm having now is that Ktorrent seems to cleanly shut its self down automatically. I can not find any crash events/logs that I am able to spot. I currently running Suse 10.2, I've turned off all power saving options including screen saver. If anyone can help me find a log to post for review that would be great.
Thanks in advance. |
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
|
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
it was running well for a couple of days without error, then I added some downloads and it happened again. here is the output of the terminal screen:
(gdb) run --nofork Starting program: /opt/kde3/bin/ktorrent --nofork (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47459145824704 (LWP 5894)] [New Thread 1082132800 (LWP 5912)] [New Thread 1090525504 (LWP 5913)] [Thread 1090525504 (LWP 5913) exited] [Thread 1082132800 (LWP 5912) exited] [New Thread 1082132800 (LWP 10296)] [New Thread 1090525504 (LWP 10297)] [New Thread 1098918208 (LWP 11826)] [Thread 1098918208 (LWP 11826) exited] [New Thread 1098918208 (LWP 11827)] [New Thread 1107310912 (LWP 11882)] [Thread 1107310912 (LWP 11882) exited] [New Thread 1107310912 (LWP 11883)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1107310912 (LWP 11883)] 0x00002b29f43bf7da in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3 (gdb) bt #0 0x00002b29f43bf7da in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3 #1 0x00002b29f43acf04 in dbus_error_has_name () from /usr/lib64/libdbus-1.so.3 #2 0x00002b29f43b16c1 in dbus_message_get_reply_serial () from /usr/lib64/libdbus-1.so.3 #3 0x00002b29f43ab49e in dbus_connection_send () from /usr/lib64/libdbus-1.so.3 #4 0x00002b29f43bb009 in dbus_threads_init () from /usr/lib64/libdbus-1.so.3 #5 0x00002b29f43bbd47 in dbus_threads_init () from /usr/lib64/libdbus-1.so.3 #6 0x00002b29f43bc2ef in dbus_threads_init () from /usr/lib64/libdbus-1.so.3 #7 0x00002b29f43bac6a in dbus_threads_init () from /usr/lib64/libdbus-1.so.3 #8 0x00002b29f43ab448 in dbus_connection_send () from /usr/lib64/libdbus-1.so.3 #9 0x00002b29f43bcad1 in dbus_watch_handle () from /usr/lib64/libdbus-1.so.3 #10 0x00002b29f4196c4b in avahi_simple_poll_dispatch () from /usr/lib64/libavahi-common.so.3 #11 0x00002b29f419718d in avahi_simple_poll_loop () from /usr/lib64/libavahi-common.so.3 #12 0x00002b29f4197b2e in avahi_threaded_poll_start () from /usr/lib64/libavahi-common.so.3 #13 0x00002b29ecfe909e in start_thread () from /lib64/libpthread.so.0 #14 0x00002b29ed7cc4cd in clone () from /lib64/libc.so.6 #15 0x0000000000000000 in ?? () (gdb) |
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
Make sure that the capacity of the home partition on your Hard Disk is not being exceeded, if it has then after few minutes Ktorrent will shut down, when partitioning your Hard Disk, make sure you allocate the maximum possible space for the home partition.
The only Linux distro that can handle this problem is OpenSuse, it will not allow further downloading or will issue warning that what you are going to down load exceed that capacity of the partition. The best option is to reinstall, than do bug fixing.My solution was to use a USB disk, with 250 GB, and down load to it. But there is problem, you need to get the older type USB enclosure, as the latest chip on these USBs only reads, doesn't write, that is, you can copy and past to linux but not other way round. Another way is to create a folder on the DESKTOP, just give it a name like DOWNLOADS etc, then go to Ktorrent setup, click on General then tick the check box, that say: "AUTOMATICALLY save Downloads to:" Brows , pick the desktop, then the folder created, and everything will go there, you can then right click on the folde, click properties, and it will show the available space for downloading, but you have to do this when you first installed the Ktorrent, otherwise the information wont indicated the true amount of downloads that are on the home partition, as some of it has gone into the Ktorrent's default folder. As well, in the setup, Click downloads, and on the forth line from top, start downloads on low diskspace, make sure you pick Don't start. We tested this on PClinxOS, Fedora, MEPIS and Suse, using a 20GB Hard Disk, after the capacity was exceeded, the first two, did exactly what is mentioned in first post here, but the MEPIS one just went berserk, it no longer accepted the name and pass word among other unpredictable somersaults. Suse managed to prevent excess down loading. and issued warning messages. |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]