[ktorrent] [Bug 459271] New: KTorrent crash frequently
https://bugs.kde.org/show_bug.cgi?id=459271 Bug ID: 459271 Summary: KTorrent crash frequently Classification: Unclassified Product: ktorrent Version: 22.08.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: marco.difre...@gmail.com Target Milestone: --- Application: ktorrent (22.08.1) (Compiled from sources) Qt Version: 5.15.5 Frameworks Version: 5.98.0 Operating System: Linux 5.19.5-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: The onlyu pattern I noticed is that it happens whan there are multiple (>1) downloads, but beside that no clear indication. When the problem starts, it keep happening after few minutes (sometime after <1 minute) and I have to keep re-opening it until I can finally finish the download and remove the items. When there is no torrent in the application, the problem doesn't happen. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted [KCrash Handler] #4 0x7fbeaa29056c in ?? () from /lib64/libc.so.6 #5 0x7fbeaa244a02 in raise () from /lib64/libc.so.6 #6 0x7fbeaa22f469 in abort () from /lib64/libc.so.6 #7 0x7fbeaa49d8b2 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/11.3.1/libstdc++.so.6 #8 0x7fbeaa4a95f6 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/11.3.1/libstdc++.so.6 #9 0x7fbeaa4a9661 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/11.3.1/libstdc++.so.6 #10 0x7fbeaa89005a in qTerminate() () from /usr/lib64/libQt5Core.so.5 #11 0x7fbeaa891c41 in ?? () from /usr/lib64/libQt5Core.so.5 #12 0x7fbeaa28e84a in ?? () from /lib64/libc.so.6 #13 0x7fbeaa311cec in ?? () from /lib64/libc.so.6 Thread 5 (Thread 0x7fbe7ebff640 (LWP 311926) "kt::ScanThread"): #1 0x7fbea8e7978e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbea8e798af in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbeaab2244e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fbeaaac427b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fbeaa8cf20e in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fbeaa8d03bf in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fbeaa28e84a in ?? () from /lib64/libc.so.6 #8 0x7fbeaa311cec in ?? () from /lib64/libc.so.6 Thread 4 (Thread 0x7fbe97fff640 (LWP 311923) "threaded-ml"): #1 0x7fbe9475c402 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7fbe9474d139 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7fbe9474d7e7 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7fbe9474d8a0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7fbe9475c4d9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7fbe946f7ffe in ?? () from /usr/lib64/pulseaudio/libpulsecommon-16.1.so #7 0x7fbeaa28e84a in ?? () from /lib64/libc.so.6 #8 0x7fbeaa311cec in ?? () from /lib64/libc.so.6 Thread 3 (Thread 0x7fbe977fe640 (LWP 311913) "Qt bearer threa"): #1 0x7fbea8e7978e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbea8e798af in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbeaab2244e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fbeaaac427b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fbeaa8cf20e in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fbeaa8d03bf in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fbeaa28e84a in ?? () from /lib64/libc.so.6 #8 0x7fbeaa311cec in ?? () from /lib64/libc.so.6 Thread 2 (Thread 0x7fbe9d5ff640 (LWP 311911) "QDBusConnection"): #1 0x7fbea8e7978e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbea8e798af in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbeaab2244e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fbeaaac427b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fbeaa8cf20e in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fbeabea04e7 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fbeaa8d03bf in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fbeaa28e84a in ?? () from /lib64/libc.so.6 #9 0x7fbeaa311cec in ?? () from /lib64/libc.so.6 Thread 1 (Thread 0x7fbea5a488c0 (LWP 311859) "ktorrent"): #1 0x7fbeaa8d0715 in QBasicMutex::lockInternal() () from /usr/lib64/libQt5Core.so.5 #2 0x7fbeaa8d0a52 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x7fbeacc9eddf in net::SocketMonitor::remove(net::TrafficShapedSocket*) () from /usr/lib64/libKF5Torrent.so.6 #4 0x0
[kmymoney] [Bug 501591] Error in function QMap MyMoneyStorageSql::fetchPayees(const QStringList&, bool) const : reading Payee
https://bugs.kde.org/show_bug.cgi?id=501591 --- Comment #2 from Marco Di Fresco --- llo, A few notes as requested: it was an upgrade from 5.1.3; the DB is MariaDB 5.5.68 (it is on a NAS, so I don't think I can upgrade it outside NAS firmware updates); here the columns in kmmPayees: id name reference email addressStreet addressCity addressZipcode addressState telephone notes defaultAccountId matchData matchIgnoreCase matchKeys Best regards. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 501591] Error in function QMap MyMoneyStorageSql::fetchPayees(const QStringList&, bool) const : reading Payee
https://bugs.kde.org/show_bug.cgi?id=501591 --- Comment #7 from Marco Di Fresco --- Done: https://bugs.gentoo.org/951486 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 501591] New: Error in function QMap MyMoneyStorageSql::fetchPayees(const QStringList&, bool) const : reading Payee
https://bugs.kde.org/show_bug.cgi?id=501591 Bug ID: 501591 Summary: Error in function QMap MyMoneyStorageSql::fetchPayees(const QStringList&, bool) const : reading Payee Classification: Applications Product: kmymoney Version: 5.1.92 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: marco.difre...@gmail.com Target Milestone: --- I got today the update from 5.13 to 5.1.92 on my Gentoo PC. Unfortunately when I start it I get the following error: Error in function QMap MyMoneyStorageSql::fetchPayees(const QStringList&, bool) const : reading Payee Driver = QMYSQL, Host = 192.168.0.12, User = marco, Database = KMyMoney-CHF Driver Error: Database Error No : Text: Error type 0 Executed: SELECT kmmPayees.id AS id, kmmPayees.name AS name, kmmPayees.reference AS reference, kmmPayees.email AS email, kmmPayees.addressStreet AS addressStreet, kmmPayees.addressCity AS addressCity, kmmPayees.addressZipcode AS addressZipcode, kmmPayees.addressState AS addressState, kmmPayees.telephone AS telephone, kmmPayees.notes AS notes, kmmPayees.defaultAccountId AS defaultAccountId, kmmPayees.matchData AS matchData, kmmPayees.matchIgnoreCase AS matchIgnoreCase, kmmPayees.matchKeys AS matchKeys, kmmPayeesPayeeIdentifier.identifierId AS identId, kmmPayees.idPattern AS idPattern, kmmPayees.urlTemplate AS urlTemplate FROM ( SELECT * FROM kmmPayees ) kmmPayees LEFT OUTER JOIN kmmPayeesPayeeIdentifier ON kmmPayees.Id = kmmPayeesPayeeIdentifier.payeeId ORDER BY kmmPayees.id, kmmPayeesPayeeIdentifier.userOrder; Query error No 1054: Unknown column 'kmmPayees.idPattern' in 'field list' QMYSQL: Unable to execute query Error type 2 /var/tmp/portage/app-office/kmymoney-5.1.92_p20250306/work/kmymoney-17859b4f0b2a654c11e8e209fdc7ea097c7f4ea5/kmymoney/plugins/sql/mymoneystoragesql.cpp:1338 Dismissing the error window lead to a fresh (empty) KMyMoney; therefore I cannot access my accounting. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 501591] Error in function QMap MyMoneyStorageSql::fetchPayees(const QStringList&, bool) const : reading Payee
https://bugs.kde.org/show_bug.cgi?id=501591 --- Comment #4 from Marco Di Fresco --- (In reply to Jack from comment #3) > The field it can't find was added four months ago, but only in master > branch, not the 5.1 branch, which is why it is not in your data. In the > short term, using any version of KMyMoney from the 5.1 branch should be able > to read your existing database. You can either dig up the 5.1.3 ebuild from > git, or use the 5.1.3 appimage I mentioned above. > Separately, we'll have to figure out why the new version didn't recognize > that your database needed to be updated, and get that code added. OK, thanks. Should I also open a bug report on Gentoo? Since 5.1.92 is now the only version on their tree, other may have the same problem too and therefore they should revert back to 5.1.3 until migrating-version is available. -- You are receiving this mail because: You are watching all bug changes.
