[ktorrent] [Bug 344914] Crashed when adding some torrents
https://bugs.kde.org/show_bug.cgi?id=344914 Dmitry Bergstein changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 304206] Crash on Disk usage report
https://bugs.kde.org/show_bug.cgi?id=304206 --- Comment #5 from Dmitry Bergstein <bergst...@trickyplan.ru> --- Hm, looks like I have to upgrade to testing for 2.5. Unfortunately, I can't check it, I used standard debian package (1:2.4.0~beta3-2). -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 304206] Crash on Disk usage report
https://bugs.kde.org/show_bug.cgi?id=304206 Dmitry Bergstein <bergst...@trickyplan.ru> changed: What|Removed |Added CC||bergst...@trickyplan.ru -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 304206] Crash on Disk usage report
https://bugs.kde.org/show_bug.cgi?id=304206 --- Comment #3 from Dmitry Bergstein <bergst...@trickyplan.ru> --- Created attachment 99112 --> https://bugs.kde.org/attachment.cgi?id=99112=edit New crash information added by DrKonqi krusader (2.4.0-beta3 "Single Step") on KDE Platform 4.14.2 using Qt 4.8.6 - What I was doing when the application crashed: Just used Disk Usage with 2TB filesystem. -- Backtrace (Reduced): #6 QString (other=..., this=0x7ffc4aa4bb90) at /usr/include/qt4/QtCore/qstring.h:725 #7 KMimeTypeRepository::findMimeTypeByName (this=0xdece00, _name=..., options=options@entry=KMimeType::ResolveAliases) at ../../kdecore/services/kmimetyperepository.cpp:61 #8 0x7f85d9177673 in KMimeType::mimeType (name=..., options=KMimeType::ResolveAliases) at ../../kdecore/services/kmimetype.cpp:60 [...] #11 0x7f85d701248c in QApplicationPrivate::notify_helper (this=this@entry=0xb58600, receiver=receiver@entry=0x1277460, e=e@entry=0x7ffc4aa4bf90) at kernel/qapplication.cpp:4570 #12 0x7f85d7019b13 in QApplication::notify (this=this@entry=0x7ffc4aa4dd80, receiver=receiver@entry=0x1235a60, e=e@entry=0x7ffc4aa4c110) at kernel/qapplication.cpp:4252 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 359791] New: KControl crashed without visible reason
https://bugs.kde.org/show_bug.cgi?id=359791 Bug ID: 359791 Summary: KControl crashed without visible reason Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bergst...@trickyplan.ru Application: kdeconnectd (0.1) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Kali GNU/Linux 2.0 -- Information about the crash: - What I was doing when the application crashed: Absolutely nothing. Maybe, crash dump will be usable. One Padfone S connected. The crash does not seem to be reproducible. -- Backtrace: Application: kdeconnect (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5c8f1c4780 (LWP 2903))] Thread 3 (Thread 0x7f5c7c3b0700 (LWP 2905)): #0 0x7f5c8c0a5d3d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5c89662ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5c89662ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5c8cd48d37 in QEventDispatcherGlib::processEvents (this=0x7f5c740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5c8cd18271 in QEventLoop::processEvents (this=this@entry=0x7f5c7c3afe50, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5c8cd185d5 in QEventLoop::exec (this=this@entry=0x7f5c7c3afe50, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5c8cc0ce99 in QThread::exec (this=) at thread/qthread.cpp:538 #7 0x7f5c8cc0f70f in QThreadPrivate::start (arg=0x1b9c6d0) at thread/qthread_unix.cpp:349 #8 0x7f5c89b4a0a4 in start_thread (arg=0x7f5c7c3b0700) at pthread_create.c:309 #9 0x7f5c8c0ae87d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f5c79b73700 (LWP 2915)): #0 0x7f5c8c0a5d3d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5c89662ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5c89662ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5c8cd48d37 in QEventDispatcherGlib::processEvents (this=0x7f5c6c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5c8cd18271 in QEventLoop::processEvents (this=this@entry=0x7f5c79b72e00, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5c8cd185d5 in QEventLoop::exec (this=this@entry=0x7f5c79b72e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5c8cc0ce99 in QThread::exec (this=this@entry=0x1c7d720) at thread/qthread.cpp:538 #7 0x7f5c8ccf8ac3 in QInotifyFileSystemWatcherEngine::run (this=0x1c7d720) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f5c8cc0f70f in QThreadPrivate::start (arg=0x1c7d720) at thread/qthread_unix.cpp:349 #9 0x7f5c89b4a0a4 in start_thread (arg=0x7f5c79b73700) at pthread_create.c:309 #10 0x7f5c8c0ae87d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f5c8f1c4780 (LWP 2903)): [KCrash Handler] #6 0x7f5c8eddb1d7 in ?? () from /usr/lib/libkdeconnectcore.so.1 #7 0x7f5c8cd2e71c in QMetaObject::activate (sender=sender@entry=0x1a54b70, m=m@entry=0x7f5c8d07d7c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #8 0x7f5c8cd79bc0 in QIODevice::readyRead (this=this@entry=0x1a54b70) at .moc/release-shared/moc_qiodevice.cpp:104 #9 0x7f5c8b64055e in QAbstractSocketPrivate::canReadNotification (this=0x1a62b00) at socket/qabstractsocket.cpp:654 #10 0x7f5c8b64b1bd in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1151 #11 0x7f5c8dc0d48c in QApplicationPrivate::notify_helper (this=this@entry=0x19d8820, receiver=receiver@entry=0x150, e=e@entry=0x7ffc7b45ce50) at kernel/qapplication.cpp:4570 #12 0x7f5c8dc13fa8 in QApplication::notify (this=this@entry=0x7ffc7b45d180, receiver=receiver@entry=0x150, e=e@entry=0x7ffc7b45ce50) at kernel/qapplication.cpp:4356 #13 0x7f5c8e9851aa in KApplication::notify (this=0x7ffc7b45d180, receiver=0x150, event=0x7ffc7b45ce50) at ../../kdeui/kernel/kapplication.cpp:311 #14 0x7f5c8cd1971d in QCoreApplication::notifyInternal (this=0x7ffc7b45d180, receiver=0x150, event=event@entry=0x7ffc7b45ce50) at kernel/qcoreapplication.cpp:955 #15 0x7f5c8cd49380 in sendEvent (event=0x7ffc7b45ce50, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #16 socketNotifierSourceDispatch (source=0x19d80e0) at kernel/qeventdispatcher_glib.cpp:110 #17 0x7f5c89662c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f5c89662f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f5c89662ffc in
[systemsettings] [Bug 359779] New: System Settings crashed at startup
https://bugs.kde.org/show_bug.cgi?id=359779 Bug ID: 359779 Summary: System Settings crashed at startup Product: systemsettings Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bergst...@trickyplan.ru Application: systemsettings (4.11.13) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: Kali GNU/Linux 2.0 -- Information about the crash: - What I was doing when the application crashed: Just started System Settings from Main Menu lsusb Bus 008 Device 004: ID 0b05:17cf ASUSTek Computer, Inc. Bus 008 Device 003: ID 046d:0826 Logitech, Inc. HD Webcam C525 Bus 008 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 002: ID 17ef:6046 Lenovo Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 003 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub Bus 003 Device 002: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 006: ID 0665:6000 Cypress Semiconductor Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 1e7d:2e22 ROCCAT Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 005: ID 0bda:0161 Realtek Semiconductor Corp. Mass Storage Device Bus 007 Device 006: ID 1d57:ad02 Xenta SE340D PC Remote Control Bus 007 Device 004: ID 0424:2412 Standard Microsystems Corp. Bus 007 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 007 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 00:00.0 Host bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2 (rev 04) 00:01.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a (rev 04) 00:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a (rev 04) 00:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04) 00:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04) 00:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04) 00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04) 00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 06) 00:16.0 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #1 (rev 05) 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 06) 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06) 00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6) 00:1c.1 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 2 (rev b6) 00:1c.2 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 3 (rev b6) 00:1c.3 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 4 (rev b6) 00:1c.4 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 5 (rev b6) 00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 6 (rev b6) 00:1c.7 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 8 (rev b6) 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) 05:00.0 USB controller: ASMedia Technology
