Bug 406685

Summary:	KDE Instability of application termination
Product:	[Applications] ktorrent	Reporter:	Fergus <shopmail1>
Component:	general	Assignee:	Joris Guisson <joris.guisson>
Status:	RESOLVED WORKSFORME
Severity:	crash	Keywords:	drkonqi
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Fergus 2019-04-19 18:52:54 UTC

Application: ktorrent (5.1.0)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-47-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Killing orphaned Ktorrent process, as otherwise Ktorrent wound not start.
I have to do this every time after cloasing Ktorrent.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f63091ef800 (LWP 12125))]

Thread 3 (Thread 0x7f62eadee700 (LWP 12131)):
#0  0x00007f6303336bf9 in __GI___poll (fds=0x7f62dc002ee0, nfds=1, timeout=9503) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f62fd135539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f62fd13564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f63042359bb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f63041daa1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f6303ff923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f6303ffe17d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f62fec396db in start_thread (arg=0x7f62eadee700) at pthread_create.c:463
#8  0x00007f630334388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f62ebfff700 (LWP 12129)):
#0  0x00007f63033320b4 in __GI___libc_read (fd=11, buf=0x7f62ebffeb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007f62fd179cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f62fd135027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f62fd1354e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f62fd13564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f63042359bb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f63041daa1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f6303ff923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f6305662d45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007f6303ffe17d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f62fec396db in start_thread (arg=0x7f62ebfff700) at pthread_create.c:463
#11 0x00007f630334388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f63091ef800 (LWP 12125)):
[KCrash Handler]
#6  0x00007f6303336bf9 in __GI___poll (fds=0x5624c78e58e0, nfds=5, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29
#7  0x00007f62fd135539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007f62fd13564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007f630423599f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f63041daa1a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f63041e3ac4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00005624c62d202a in  ()
#13 0x00007f6303243b97 in __libc_start_main (main=0x5624c62cfd60, argc=1, argv=0x7fffb1835fd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb1835fc8) at ../csu/libc-start.c:310
#14 0x00005624c62d2a0a in _start ()

Reported using DrKonqi

Comment 1 Christoph Feck 2019-05-11 09:20:51 UTC

If KTorrent is already running, does clicking on its system tray icon show the window?

Comment 2 Fergus 2019-05-23 07:08:01 UTC

High Chris,

Apologies for delay; I ended up reinstalling the desktop; and the problem seems to have gone away.
No the icon wasn’t in the system tray; even though the process was still running.

There seems to be a lot of orphaned processes (not just torrent) which hadn’t been killed off on each reboot. I cleared these as well; and the problem seems to have gone away!

 I always make sure I do a controlled shutdown; as in the old days you used to end up with no directory structure left and a massive “lost+found” folder full of fragmented files!

Cheers

Fergus 

> On 11 May 2019, at 10:20, Christoph Feck <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=406685
> 
> --- Comment #1 from Christoph Feck <cfeck@kde.org> ---
> If KTorrent is already running, does clicking on its system tray icon show the
> window?
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

Comment 3 Christoph Feck 2019-06-18 09:45:07 UTC

Thanks for the update; changing status.