Ubuntu
ktorrent package

ktorrent crashed with SIGSEGV in QPluginLoader::unload()

Bug #339935 reported by SergeyS on 2009-03-09

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	ktorrent (Ubuntu)	Invalid	Low	Unassigned

Bug Description

Binary package hint: ktorrent

I've got this after restarting the computer.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ktorrent
NonfreeKernelModules: nvidia
Package: ktorrent 3.2+dfsg.1-2ubuntu1
ProcCmdline: ktorrent -session 10d2c2a29d000123596923200000103790046_1236161740_184641
ProcEnviron:
LANGUAGE=ru_RU:ru:en_GB:en
PATH=(custom, no user)
LANG=ru_RU.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: ktorrent
StacktraceTop:
?? ()
?? () from /usr/lib/libQtCore.so.4
QPluginLoader::unload ()
QCA::PluginInstance::~PluginInstance ()
QCA::ProviderManager::unloadAll ()
Title: ktorrent crashed with SIGSEGV in QPluginLoader::unload()
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse logcheck lpadmin mail plugdev postfix postgres scanner ssh sudo uml-net users video

Tags:

Revision history for this message

SergeyS (ssedreev) wrote on 2009-03-09:

Dependencies.txt Edit (7.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (467 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (69.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (845 bytes, text/plain; charset="utf-8")
Registers.txt Edit (995 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (876 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-09: Symbolic stack trace

Stacktrace.txt (retraced) Edit (5.1 KiB, text/plain)

StacktraceTop:?? ()
?? () from /usr/lib/libQtCore.so.4
QPluginLoader::unload ()
QCA::PluginInstance::~PluginInstance ()
QCA::ProviderManager::unloadAll ()

Revision history for this message

Apport retracing service (apport) wrote on 2009-03-09: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (6.9 KiB, text/plain)

Changed in ktorrent:
importance:	Undecided → Medium

Jonathan Thomas (echidnaman) on 2009-04-07

visibility:

private → public

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2009-04-07:

Confirming due to duplicate.

Changed in ktorrent (Ubuntu):
importance:	Medium → Low
status:	New → Confirmed

Revision history for this message

Mauricio Ibáñez (mibanez) wrote on 2009-05-27:

I don't know if this comment is ok here; I decided to not open a new bug and append this info:

Bug 188447 – Crash when adjusting the max upload speed from systray menu (FIXED)
https://bugs.kde.org/show_bug.cgi?id=188447

My version of KTorrent in my KUbuntu crashes the same way it was reported there.

Revision history for this message

brentpieczynski (brentpieczynski) wrote on 2009-06-01:

This was loaded by KDE while I was attempting to start my Firefox3-Browser.

Revision history for this message

brentpieczynski (brentpieczynski) wrote on 2009-06-14:

This program prior to a previous day's shutdown did freeze up the machine while attempting to download an unidentified-file, which is why I believe this to be a possible security-threat. After I forced a shutdown then got an acceptable-quality of rest, this error did result after I chose to use KDE for this session only, it-is a matter of audio access on the computer that I chose to use KDE.

Would someone have the KTorrent window pop-up so I can have some idea of what's being downloaded, because I desire to know what is being saved to the internal hard-disk of my computer. This bug might be integrated with some other bugs, which are found in the system, which might cause this to be related to a security-difficulty even if, only indirectly.

Revision history for this message

Harald Sitter (apachelogger) wrote on 2010-04-12:

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!