[Discover] [Bug 470325] New: Discover systray icon missing
https://bugs.kde.org/show_bug.cgi?id=470325 Bug ID: 470325 Summary: Discover systray icon missing Classification: Applications Product: Discover Version: 5.27.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jonr...@pacbell.net CC: aleix...@kde.org Target Milestone: --- SUMMARY The discover icon is missing from the system tray (except sometimes while discover is actually running) STEPS TO REPRODUCE 1. Start the system 2. Look in the system tray OBSERVED RESULT No discover icon in the system tray, either always or conditionally. No option in discover to put it there. EXPECTED RESULT Discover icon appears in the system tray when updates are available. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 469857] New: Kasts->Settings reports nothing
https://bugs.kde.org/show_bug.cgi?id=469857 Bug ID: 469857 Summary: Kasts->Settings reports nothing Classification: Applications Product: kasts Version: 23.01.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: jonr...@pacbell.net Target Milestone: --- SUMMARY Kasts->Settings shows the various items to be set: General, Storage, ... , About but no further info appears. STEPS TO REPRODUCE 1. Select Kasts->Settings 2. Select About (for example) 3. Look at the Kasts window. OBSERVED RESULT No info appears on the screen. EXPECTED RESULT Kasts version, etc. appears. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora-37: Fully up to date Qt Version: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: ASUS ADDITIONAL INFORMATION Kasts seems to run OK, despite the inability to see or set the settings. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465196] bash should complete okular README.md, but it doesn't
https://bugs.kde.org/show_bug.cgi?id=465196 Jonathan Ryshpan changed: What|Removed |Added CC||jonr...@pacbell.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465196] New: bash should complete okular README.md, but it doesn't
https://bugs.kde.org/show_bug.cgi?id=465196 Bug ID: 465196 Summary: bash should complete okular README.md, but it doesn't Classification: Applications Product: okular Version: 22.12.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: markdown backend Assignee: okular-de...@kde.org Reporter: jonr...@pacbell.net Target Milestone: --- SUMMARY bash should complete okular README.md, but it doesn't STEPS TO REPRODUCE 1. Using bash enter a directory in which there is a file named README.md 2. Enter READM on the keyboard OBSERVED RESULT Nothing happens. EXPECTED RESULT Bash should complete the name to README.md SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ===>(available in Info Center->About System) Just "About System" is not very informative to the average user KDE Plasma Version: Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have this fixed for README.md *or* README.MD, but not for both. (The syntax of the bash "complete" command is not so easy to understand.) SYSTEM INFO Kernel Version: 6.1.8-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: ASUS Product Name: All Series KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 464746] K3b crashes after opening a .iso file
https://bugs.kde.org/show_bug.cgi?id=464746 --- Comment #3 from Jonathan Ryshpan --- The word "Dolphin" is missing from the following line in my last comment. However the image is very strange: Opening it from causes K3B to reject it with the popup message "Error -- Could not open document". -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 464746] K3b crashes after opening a .iso file
https://bugs.kde.org/show_bug.cgi?id=464746 --- Comment #2 from Jonathan Ryshpan --- The file is available at: https://drive.google.com/file/d/1TH8nKX8AZHRWaFejigLViqMwQ9nKp-Tw/view?usp=share_link It was created by running K3B->Copy Medium->Options->Only Create Image on a disk of x-rays of my ankles. (I don't need to have my x-rays kept private, but would rather not have them posted on the web.) The disk appears to be self-starting on Windows and can be read in Linux using the Weasis program. It no longer causes K3B to crash. My system is now running normally; it's no longer slow to start programs. I have no idea why the system is working better, possibly some background process is no longer running. However the image is very strange: Opening it from causes K3B to reject it with the popup message "Error -- Could not open document". Opening it using K3B->More Actions->Desktop/.../Ankle-DiskImage-1.iso produces the popup message Type of image file is not recognizable. Do you want to burn it anyway? The file command doesn't recognize it: $ file Ankle-DiskImage-1.iso Ankle-DiskImage-1.iso: data Nevertheless the Dolphin "Open with Disk Image Mounter" command appears to mount the image correctly, and it's possible to burn a copy by answering "Do you want to burn it anyway?" with Yes. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 464746] New: K3b crashes after opening a .iso file
https://bugs.kde.org/show_bug.cgi?id=464746 Bug ID: 464746 Summary: K3b crashes after opening a .iso file Classification: Applications Product: k3b Version: 22.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@kde.org Reporter: jonr...@pacbell.net CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Application: k3b (22.12.1) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.7-200.fc37.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: I opened a .iso file. K3B reported Transferring in a pop up window; there was a long period during which the progress meter in the popup window movded slowly, then the pop up reported "Transferrind (Failed) Application closed unecpectedly" and K3b crashed. The system has been running extremely slowly before the crash, despite the fact that there doesn't seem to be a lot of CPU activity; my (very noisy) disk has been noisy lately. I have too many Firefox windows open, which seems to have something to do with slow system response. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: K3b (k3b), signal: Segmentation fault [KCrash Handler] #4 0x7fc393b75b8a in __memmove_avx_unaligned_erms () at /lib64/libc.so.6 #5 0x7fc3942dbc26 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #6 0x7fc395884e08 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () at /lib64/libKF5KIOCore.so.5 #7 0x7fc3942dbc26 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #8 0x7fc395866bf6 in KIO::SlaveInterface::data(QByteArray const&) () at /lib64/libKF5KIOCore.so.5 #9 0x7fc39586ef8b in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /lib64/libKF5KIOCore.so.5 #10 0x7fc395866aaa in KIO::SlaveInterface::dispatch() () at /lib64/libKF5KIOCore.so.5 #11 0x7fc395869311 in KIO::Slave::gotInput() () at /lib64/libKF5KIOCore.so.5 #12 0x7fc3942dbc26 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #13 0x7fc3942d2ec4 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7fc394faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7fc3942a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7fc3942ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #17 0x7fc3942f9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x7fc38f066cbf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x7fc38f0bc598 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #20 0x7fc38f063f40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7fc3942f938a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7fc3942a6cca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7fc3956a8195 in KJob::exec() () at /lib64/libKF5CoreAddons.so.5 #24 0x55dbb4d2e8db in K3b::ProjectManager::openProject(QUrl const&) () #25 0x55dbb4dd8b07 in K3b::MainWindow::openDocument(QUrl const&) [clone .isra.0] () #26 0x55dbb4d0930e in K3b::Application::processCmdLineArgs() [clone .part.0] () #27 0x7fc3942d2ec4 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #28 0x7fc394faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #29 0x7fc3942a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #30 0x7fc3942ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #31 0x7fc3942f9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #32 0x7fc38f066cbf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #33 0x7fc38f0bc598 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #34 0x7fc38f063f40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #35 0x7fc3942f938a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #36 0x7fc3942a6cca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #37 0x7fc3942aed92 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #38 0x55dbb4cda050 in main () [Inferior 1 (process 45573) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 461024] New: Empty queue message not exact.
https://bugs.kde.org/show_bug.cgi?id=461024 Bug ID: 461024 Summary: Empty queue message not exact. Classification: Applications Product: kasts Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: jonr...@pacbell.net Target Milestone: --- STEPS TO REPRODUCE 1. Start Kasts 2. Clear the queue 3. Look at the message OBSERVED RESULT Message saying "Nothing added to the queue yet." EXPECTED RESULT Message saying "Nothing in the queue." SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.19.16-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 ADDITIONAL INFORMATION I suspect there is some confusion caused by the similarity between the English "yet" and the German "jetzt". "Yet" means any time up to the present. "Nothing added to the queue yet" means that nothing has ever been added to the queue. I have in fact added many things to the queue. This is a very small thing, but it bugs me whenever I see the message. -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 456291] New: Ruler not visible
https://bugs.kde.org/show_bug.cgi?id=456291 Bug ID: 456291 Summary: Ruler not visible Product: kruler Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: soe...@pprojekt.de Reporter: jonr...@pacbell.net Target Milestone: --- SUMMARY Kruler reports no problems when started, but nothing appears on the screen. STEPS TO REPRODUCE 1. Enter $kruler on a terminal or start from the Application Launcher OBSERVED RESULT An entry appears on the Task Manager; but no ruler appears on the screen. EXPECTED RESULT Ruler appears on the screen. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.18.7-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 ADDITIONAL INFORMATION kruler-22.04.1-1.fc36.x86_64 Also reported to Fedora Bugzilla -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446349] Android phone does not stop ringing after using 'Ring my phone' feature
https://bugs.kde.org/show_bug.cgi?id=446349 Jonathan Ryshpan changed: What|Removed |Added CC||jonr...@pacbell.net --- Comment #1 from Jonathan Ryshpan --- I see this too. I got the phone to stop ringing by unpairing it on my desktop machine. The bug report says "on your Android phone, tap on 'Found' button of KDE Connect app", but I see no such button in the app on my phone. Desktop KDE Connect version: kde-connect-22.04.1-2.fc36.x86_64 Desktop System info: Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Phone Info: Samsung Galaxy A52 : Model 5G SM-A526U1 Phone kde-connect version: 1.19.2 : Running on Android 12 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 448956] Position Missing Red 9-K
https://bugs.kde.org/show_bug.cgi?id=448956 --- Comment #4 from Jonathan Ryshpan --- (In reply to Albert Astals Cid from comment #3) > That is indeed strange. > > If you open the file and undo 5 times you will see it goes from > https://i.imgur.com/ZFpmIyc.png to https://i.imgur.com/Ijx9BFG.png > > That is, you moved the 9 under the 10 and suddenly 5 cards disappeared. > > Can you try undoing those 5 times and then doing the same movement and > seeing if those cards disappear again? If I undo 5 times and then "Redo" the 9-K disappear. If I actually move the 9 under the 10, the 9-K don't disappear. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 448956] Position Missing Red 9-K
https://bugs.kde.org/show_bug.cgi?id=448956 --- Comment #2 from Jonathan Ryshpan --- Created attachment 145811 --> https://bugs.kde.org/attachment.cgi?id=145811&action=edit Kpat Game Position Missing Red 9-K Attachment is attached. Please excuse. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 448956] Position Missing Red 9-K
https://bugs.kde.org/show_bug.cgi?id=448956 Jonathan Ryshpan changed: What|Removed |Added CC||jonr...@pacbell.net -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 448956] New: Position Missing Red 9-K
https://bugs.kde.org/show_bug.cgi?id=448956 Bug ID: 448956 Summary: Position Missing Red 9-K Product: kpat Version: 20.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: jonr...@pacbell.net CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Spider Position Missing Red 9-K STEPS TO REPRODUCE 1. Load the attached saved game. OBSERVED RESULT Position is missing the red cards 9-K EXPECTED RESULT Game is solved. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.15-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 KPatience: Version 21.4.3 (not available in drop down list) ADDITIONAL INFORMATION I don't know what to make of this but Kpat maintainers may be interested. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443707] New: Okular crashes while searching
https://bugs.kde.org/show_bug.cgi?id=443707 Bug ID: 443707 Summary: Okular crashes while searching Product: okular Version: 21.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jonr...@pacbell.net Target Milestone: --- Application: okular (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.11-200.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: Reading the manual for an LG VS985 cell phone; searching for the word "cable". Just before the crash it became impossible to resize index pane to make the section entries larger. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7ff32c630864 in QWidget::style() const () from /lib64/libQt5Widgets.so.5 #5 0x7ff32c60cf44 in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x7ff32c607443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #7 0x7ff32ba9e798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7ff32baeee63 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #9 0x7ff32baef76c in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #10 0x7ff32a2054cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #11 0x7ff32a2594f8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #12 0x7ff32a202c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #13 0x7ff32baefb78 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #14 0x7ff32ba9d1a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #15 0x7ff32baa56e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #16 0x55ff5e733cca in main () [Inferior 1 (process 39819) detached] Possible duplicates by query: bug 443586, bug 443435, bug 442599, bug 441614, bug 440647. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 439171] Text can't be selected in the kinfocenter
https://bugs.kde.org/show_bug.cgi?id=439171 Jonathan Ryshpan changed: What|Removed |Added CC||jonr...@pacbell.net --- Comment #2 from Jonathan Ryshpan --- Paul W. is correct (thanks Paul), but the action is not obvious. You have to notice "Copy to Clipboard", consider what it would do (copy *what* to clipboard), then try it out. If you want a selection, say only the kernel version, you have to "Copy to Clipboard", paste into an editor, then select what you want. There are other pages from which you might want to copy (say about the graphics system); none of has has a "Copy to Clipboard" button. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 439171] New: Text can't be selected in the kinfocenter
https://bugs.kde.org/show_bug.cgi?id=439171 Bug ID: 439171 Summary: Text can't be selected in the kinfocenter Product: kinfocenter Version: 5.22.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jonr...@pacbell.net CC: hubn...@gmail.com Target Milestone: --- SUMMARY: Text in the kinfocenter "System Information" tab (and other tabs for that matter) should be selectable. STEPS TO REPRODUCE 1. Open kinfocenter->System Information 2. Attempt to select text with the mouse OBSERVED RESULT Nothing happens. EXPECTED RESULT Text is selected (and can be copied). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Wouldn't it be much easier to just copy the KDE Plasma info from the "System Information" tab and paste it here? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407130] New: Discover crashes on startup
https://bugs.kde.org/show_bug.cgi?id=407130 Bug ID: 407130 Summary: Discover crashes on startup Product: Discover Version: 5.14.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: jonr...@pacbell.net CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.9-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: The Software Updates popup reported 26 new updates. I started Discover to get more info. The system is pretty busy; about 75% cpu usage from other apps. Discover crashed about 2 minutes after being started. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d52c4e940 (LWP 3556))] Thread 11 (Thread 0x7f2d16954700 (LWP 3582)): #0 0x7f2d5333c25f in () at /lib64/libglib-2.0.so.0 #1 0x7f2d5333ecd2 in g_main_context_check () at /lib64/libglib-2.0.so.0 #2 0x7f2d5333f350 in () at /lib64/libglib-2.0.so.0 #3 0x7f2d5333f4d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f2d5650b5ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f2d564b9e0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f2d56321e86 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f2d5632b2fb in () at /lib64/libQt5Core.so.5 #8 0x7f2d55a7b58e in start_thread () at /lib64/libpthread.so.0 #9 0x7f2d55e67683 in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f2d30e1e700 (LWP 3577)): [KCrash Handler] #6 0x7f2d5688d0e8 in () at /lib64/libQt5Network.so.5 #7 0x7f2d5688ba39 in () at /lib64/libQt5Network.so.5 #8 0x7f2d564e3da6 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #9 0x7f2d57412285 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #10 0x7f2d574199a0 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #11 0x7f2d564baec6 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7f2d564be09b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #13 0x7f2d5650b807 in () at /lib64/libQt5Core.so.5 #14 0x7f2d5333f06d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #15 0x7f2d5333f438 in () at /lib64/libglib-2.0.so.0 #16 0x7f2d5333f4d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #17 0x7f2d5650b593 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #18 0x7f2d564b9e0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #19 0x7f2d56321e86 in QThread::exec() () at /lib64/libQt5Core.so.5 #20 0x7f2d5632b2fb in () at /lib64/libQt5Core.so.5 #21 0x7f2d55a7b58e in start_thread () at /lib64/libpthread.so.0 #22 0x7f2d55e67683 in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f2d31818700 (LWP 3573)): #0 0x7f2d55e57f54 in read () at /lib64/libc.so.6 #1 0x7f2d53385e90 in () at /lib64/libglib-2.0.so.0 #2 0x7f2d5333ee9b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f2d5333f350 in () at /lib64/libglib-2.0.so.0 #4 0x7f2d5333f4d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f2d5650b5ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f2d564b9e0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f2d56321e86 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f2d5632b2fb in () at /lib64/libQt5Core.so.5 #9 0x7f2d55a7b58e in start_thread () at /lib64/libpthread.so.0 #10 0x7f2d55e67683 in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f2d32019700 (LWP 3571)): #0 0x7f2d55e57f6e in read () at /lib64/libc.so.6 #1 0x7f2d53385e90 in () at /lib64/libglib-2.0.so.0 #2 0x7f2d5333ee9b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f2d5333f350 in () at /lib64/libglib-2.0.so.0 #4 0x7f2d5333f762 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #5 0x7f2d32b4810a in () at /lib64/libgio-2.0.so.0 #6 0x7f2d533682aa in () at /lib64/libglib-2.0.so.0 #7 0x7f2d55a7b58e in start_thread () at /lib64/libpthread.so.0 #8 0x7f2d55e67683 in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2d3281a700 (LWP 3570)): #0 0x7f2d55e57f54 in read () at /lib64/libc.so.6 #1 0x7f2d53385e90 in () at /lib64/libglib-2.0.so.0 #2 0x7f2d5333ee9b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f2d5333f350
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #19 from Jonathan Ryshpan --- (In reply to Albert Astals Cid from comment #18) > KDE Applications 19.04 has not been release yet, we're in beta phase at this > point. Can you tell me how to check when KDE Applications 19.04 has become incorporated into Fedora? Or should I ask the Fedora people how to make the check? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #17 from Jonathan Ryshpan --- Pardon my ignorance, but how can I tell whether "KDE Applications 19.04" has been installed in Fedora Linux? Do you mean kpat-19.04? Or maybe something else. A search using $ rpm -qa '*kde*' doesn't produce any packages with promising looking names. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #12 from Jonathan Ryshpan --- (In reply to Jonathan Ryshpan from comment #10) > (In reply to Shlomi Fish from comment #9) > > Hi all! > > > > I was able to see the problem esp with deal 830910836. See > > https://phabricator.kde.org/D19671 for a tentative fix. > > (In reply to Shlomi Fish from comment #8) > > (In reply to Jonathan Ryshpan from comment #7) > > > (In reply to Shlomi Fish from comment #3) > > > > (In reply to Jonathan Ryshpan from comment #0) > > > > > SUMMARY > > > > > Solver for Freecell is very slow > > > > > > > > Seems to work fine here on fedora 30 on an old acer aspire 5738DZG X64 > > > > laptop with xfce and 3 GB of RAM. What are your system's hardware > > > > specs? Can > > > > you use a system monitor? > > > > > > Hardware > > > Processors: 4 Intel Core I5 CPU at 3.20 GHz > > > Memory: 15.5 GiB of RAM > > > > > > I could use a system monitor; which one do you recommend? > > > > I like https://en.wikipedia.org/wiki/Htop but there are many other decent > > ones. > I tried ksysguard, but didn't see anything worth reporting. I tried ksysguard again and saw something interesting. I started kpat. (Unfortunately the game number is lost. The solver was disabled. After playing for a little while, the system became unusably slow; judging from disk activity it sounded like a swapping fit. However, I was able to get a screen shot, which is attached as comment 11. The system continued to be very slow even after I terminated kpat, and also some other big programs that had been running, namely chrome, firefox, and evolution. I was able to save the screen shot, but had to reboot before it was convenient to file this report. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #11 from Jonathan Ryshpan --- Created attachment 118708 --> https://bugs.kde.org/attachment.cgi?id=118708&action=edit Screenshot of kpat locking up the system Shows CPU and memory activity while kpat is locking up my system -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #10 from Jonathan Ryshpan --- (In reply to Shlomi Fish from comment #9) > Hi all! > > I was able to see the problem esp with deal 830910836. See > https://phabricator.kde.org/D19671 for a tentative fix. (In reply to Shlomi Fish from comment #8) > (In reply to Jonathan Ryshpan from comment #7) > > (In reply to Shlomi Fish from comment #3) > > > (In reply to Jonathan Ryshpan from comment #0) > > > > SUMMARY > > > > Solver for Freecell is very slow > > > > > > Seems to work fine here on fedora 30 on an old acer aspire 5738DZG X64 > > > laptop with xfce and 3 GB of RAM. What are your system's hardware specs? > > > Can > > > you use a system monitor? > > > > Hardware > > Processors: 4 Intel Core I5 CPU at 3.20 GHz > > Memory: 15.5 GiB of RAM > > > > I could use a system monitor; which one do you recommend? > > I like https://en.wikipedia.org/wiki/Htop but there are many other decent > ones. I tried ksysguard, but didn't see anything worth reporting. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #7 from Jonathan Ryshpan --- (In reply to Shlomi Fish from comment #3) > (In reply to Jonathan Ryshpan from comment #0) > > SUMMARY > > Solver for Freecell is very slow > > Seems to work fine here on fedora 30 on an old acer aspire 5738DZG X64 > laptop with xfce and 3 GB of RAM. What are your system's hardware specs? Can > you use a system monitor? Hardware Processors: 4S Intel Core I5 CPU at 3.20 GHz Memory: 15.5 GiB of RAM I could use a system monitor; which one do you recommend? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #2 from Jonathan Ryshpan --- Even without the solver being active (Settings->Enable Solver unset) Freecell is extremely slow. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] New: Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 Bug ID: 405187 Summary: Solver for Freecell is very slow Product: kpat Version: 3.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: solver Assignee: co...@kde.org Reporter: jonr...@pacbell.net CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Solver for Freecell is very slow STEPS TO REPRODUCE 1. Start Freecell 2. Make sure that Settings->Enable Solver is on 3. Play a game OBSERVED RESULT Game freezes for several seconds (up to 30) after some moves. EXPECTED RESULT Game available after no more than 1 second. SOFTWARE/OS VERSIONS Running under Fedora-29 KDE Frameworks 5.55.0 Qt 5.11.3 (built against 5.11.3) The xcb windowing system ADDITIONAL INFORMATION Bug appears to be new in version 3.6 Problem observed on game number 1206106340 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 345883] 0.9.1 Apper overlapping messages while downloading
https://bugs.kde.org/show_bug.cgi?id=345883 --- Comment #20 from Jonathan Ryshpan --- (In reply to Germano Massullo from comment #14) > Apper is end of life What is apper's successor? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393894] New: Panel popups don't pop up if desktop changes while a popup is visible
https://bugs.kde.org/show_bug.cgi?id=393894 Bug ID: 393894 Summary: Panel popups don't pop up if desktop changes while a popup is visible Product: plasmashell Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jonr...@pacbell.net Target Milestone: 1.0 To see the bug: 1. Click on the Applications Launcher; A menu pops up above the App Launcher 2. Change desktops; the menu disappears 3. Click on the App Launcher; nothing happens The problem can be cured by running: killall plasmashell && kstart plasmashell >From then on the bug goes away and stays gone as long as the current session is running. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 388406] New: Podcast http://feeds.feedburner.com/RevisionistHistory shows no episodes
https://bugs.kde.org/show_bug.cgi?id=388406 Bug ID: 388406 Summary: Podcast http://feeds.feedburner.com/RevisionistHistory shows no episodes Product: amarok Version: 2.8.90 (2.9 beta) Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Podcast Assignee: amarok-bugs-d...@kde.org Reporter: jonr...@pacbell.net CC: bart.cerne...@kde.org Target Milestone: 2.9 When I subscribe to http://feeds.feedburner.com/RevisionistHistory the image shows up as it ought to, but no episodes appear. Rhythmbox installs the podcast correctly. System Fedora-27 Platform KDE-5 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 387902] New: apper crashes on startup
https://bugs.kde.org/show_bug.cgi?id=387902 Bug ID: 387902 Summary: apper crashes on startup Product: apper Version: 0.9.0 Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: jonr...@pacbell.net Target Milestone: --- Complete version is apper-0.9.3-0.8.20170226.fc26.x86_64 System is Fedora-26 with all updates installed 4-Processor True Intel Here is the log of an attempt to start apper from a console; this always happens: $ apper QCommandLineParser: option not defined: "install-mime-type" QCommandLineParser: option not defined: "install-package-name" QCommandLineParser: option not defined: "install-provide-file" QCommandLineParser: option not defined: "install-catalog" QCommandLineParser: option not defined: "remove-package-by-file" kf5.kwidgetsaddons: Invalid pixmap specified. kf5.kwidgetsaddons: Invalid pixmap specified. KCrash: Application 'apper' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Stopped apper $ QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... [1]+ Exit 253apper -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380377] FLAC files show length 0
https://bugs.kde.org/show_bug.cgi?id=380377 --- Comment #3 from Jonathan Ryshpan --- (In reply to Leslie Zhai from comment #2) > Hi Jonathan, > > K3b 2.0.3 is not be maintained any more, please try k3b 17.07.0 > https://github.com/KDE/k3b I am using Fedora 24 :) > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2017/008023.html Very perplexing, since this is the version of k3b in the Fedora-25 release. Maybe the version will be upgraded in Fedora-26. Or maybe the Fedora team is out of contact with the k3b team. Or maybe I should juse build from source. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380377] FLAC files show length 0
https://bugs.kde.org/show_bug.cgi?id=380377 --- Comment #1 from Jonathan Ryshpan --- I would like to submit an example file, but my examples are all much too long. They were all created in 2006, and I fear that I can't make another shorter one. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380377] New: FLAC files show length 0
https://bugs.kde.org/show_bug.cgi?id=380377 Bug ID: 380377 Summary: FLAC files show length 0 Product: k3b Version: 2.0.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: K3bSetup Assignee: k...@kde.org Reporter: jonr...@pacbell.net CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- I have a bunch of old FLAC files that show a length of 0. K3b refuses to burn a CD of such files, hanging and returning an error. The files can be expanded to WAV format using "flac --decode" and the resulting WAV file shows a length in K3B and burn properly to a CD. I have attached one such file, 11-Adio-kerida... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365854] New: Plasma Desktop crashed immediately after starting Oracle VirtualBox
https://bugs.kde.org/show_bug.cgi?id=365854 Bug ID: 365854 Summary: Plasma Desktop crashed immediately after starting Oracle VirtualBox Product: plasmashell Version: 5.6.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jonr...@pacbell.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.6.5) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: I had just started Oracle VirtualBox. The screen went dark and VirtualBox never started The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa8a17c4940 (LWP 1572))] Thread 17 (Thread 0x7fa7d26bd700 (LWP 3579)): #0 0x7fa8af52fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa8b0ddc01a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fa7f657b8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa7f657fa68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa7f657aa3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa7f657fac2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa7f657aa3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fa7f657d909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fa8b0ddb99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fa8af52a5ca in start_thread () at /lib64/libpthread.so.0 #10 0x7fa8b01ceead in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fa7d2ebe700 (LWP 3578)): #0 0x7fa8af52fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa8b0ddc01a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fa7f657b8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa7f657fa68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa7f657aa3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa7f657fac2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa7f657aa3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fa7f657d909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fa8b0ddb99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fa8af52a5ca in start_thread () at /lib64/libpthread.so.0 #10 0x7fa8b01ceead in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fa7d36bf700 (LWP 3577)): #0 0x7fa8af52fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa8b0ddc01a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7fa7f657b8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa7f657fa68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa7f657aa3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa7f657fac2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa7f657aa3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7fa7f657d909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7fa8b0ddb99a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fa8af52a5ca in start_thread () at /lib64/libpthread.so.0 #10 0x7fa8b01ceead in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fa7d3ec0700 (LWP 3576)): #0 0x7fa8af52fbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa8b0ddc01a in QWaitCond
[plasmashell] [Bug 361741] New: Plasma crash
https://bugs.kde.org/show_bug.cgi?id=361741 Bug ID: 361741 Summary: Plasma crash Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jonr...@pacbell.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.6-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I was typing in a program name to the "Start" button at the left of the panel. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0eb0fcd940 (LWP 12276))] Thread 16 (Thread 0x7f0e90564700 (LWP 12278)): #0 0x7f0ea89a0fdd in poll () at /lib64/libc.so.6 #1 0x7f0eaee65272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f0eaee66ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f0e92e8eda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f0ea95a93de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f0ea7ce060a in start_thread () at /lib64/libpthread.so.0 #6 0x7f0ea89aca4d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f0e8db12700 (LWP 12359)): #0 0x7f0ea3f04734 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f0ea3ebf790 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f0ea3ec009b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f0ea3ec027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f0ea97e0ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0ea9787eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f0ea95a4434 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f0ead8f39b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f0ea95a93de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f0ea7ce060a in start_thread () at /lib64/libpthread.so.0 #10 0x7f0ea89aca4d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f0e84c9e700 (LWP 12363)): #0 0x7f0ea89a0fdd in poll () at /lib64/libc.so.6 #1 0x7f0ea3ec016c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f0ea3ec027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f0ea97e0ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0ea9787eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0ea95a4434 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f0ead8f39b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f0ea95a93de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f0ea7ce060a in start_thread () at /lib64/libpthread.so.0 #9 0x7f0ea89aca4d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f0e7b1aa700 (LWP 12364)): #0 0x7f0ea3e9447b in g_ptr_array_set_size () at /lib64/libglib-2.0.so.0 #1 0x7f0ea3ebf661 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f0ea3ec009b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f0ea3ec027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f0ea97e0ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0ea9787eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f0ea95a4434 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f0ead8f39b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f0ea95a93de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f0ea7ce060a in start_thread () at /lib64/libpthread.so.0 #10 0x7f0ea89aca4d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f0e79883700 (LWP 12368)): #0 0x7f0ea7ce5b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0eb0755514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f0eb079 in () at /lib64/libQt5Script.so.5 #3 0x7f0ea7ce060a in start_thread () at /lib64/libpthread.so.0 #4 0x7f0ea89aca4d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f0df1d60700 (LWP 12438)): #0 0x7f0ea899cbcd in read () at /lib64/libc.so.6 #1 0x7f0ea3f03390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f0ea3ebfc64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f0ea3ec0110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f0ea3ec027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f0e
[kmines] [Bug 361642] Kmines generates very similar boards
https://bugs.kde.org/show_bug.cgi?id=361642 --- Comment #3 from Jonathan Ryshpan --- The best way to see difference is to display the two boards in windows one above the other and to alternate between one board and the other. -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 361642] New: Kmines generates very similar boards
https://bugs.kde.org/show_bug.cgi?id=361642 Bug ID: 361642 Summary: Kmines generates very similar boards Product: kmines Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: jonr...@pacbell.net CC: kde-games-b...@kde.org Playing Version 4.0 (29 Jan 2015) I get boards that are extremely similar. Reproducible: Always Steps to Reproduce: 1. Run kmines by clicking start->All Applications->Games->Tactics & Strategy->kmines 2. Run again same way Actual Results: Random boards Expected Results: Boards very much alike Snapshots of two such boards will be in a comment. -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 361642] Kmines generates very similar boards
https://bugs.kde.org/show_bug.cgi?id=361642 --- Comment #2 from Jonathan Ryshpan --- Created attachment 98347 --> https://bugs.kde.org/attachment.cgi?id=98347&action=edit Another snapshot -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 361642] Kmines generates very similar boards
https://bugs.kde.org/show_bug.cgi?id=361642 Jonathan Ryshpan changed: What|Removed |Added CC||jonr...@pacbell.net --- Comment #1 from Jonathan Ryshpan --- Created attachment 98346 --> https://bugs.kde.org/attachment.cgi?id=98346&action=edit Snapshot of kmines board -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 360804] New: Baloo crash on reboot
https://bugs.kde.org/show_bug.cgi?id=360804 Bug ID: 360804 Summary: Baloo crash on reboot Product: Baloo Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: jonr...@pacbell.net CC: pinak.ah...@gmail.com Application: baloo_file_extractor (5.19.0) Qt Version: 5.5.1 Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: System reboot. I am reporting this again, since this system just received a large number of KDE updates. This is probably a duplicate of Bug 356114. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff43088c8c0 (LWP 2384))] Thread 2 (Thread 0x7ff419690700 (LWP 2385)): #0 0x7ff42ce35fdd in poll () at /lib64/libc.so.6 #1 0x7ff4274ea272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7ff4274ebee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7ff41ca02da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7ff42da3e3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7ff42bf4760a in start_thread () at /lib64/libpthread.so.0 #6 0x7ff42ce41a4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ff43088c8c0 (LWP 2384)): [KCrash Handler] #5 0x7ff42ce87bd4 in __memcpy_avx_unaligned () at /lib64/libc.so.6 #6 0x7ff42fba8ca2 in Baloo::PostingCodec::decode(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #7 0x7ff42fb91224 in Baloo::PostingDB::get(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #8 0x7ff42fba507d in Baloo::WriteTransaction::commit() () at /lib64/libKF5BalooEngine.so.5 #9 0x7ff42fb9b4c2 in Baloo::Transaction::commit() () at /lib64/libKF5BalooEngine.so.5 #10 0x55acf60b80dc in Baloo::App::processNextFile() () #11 0x7ff42dc5a888 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #12 0x7ff42dc4f113 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #13 0x7ff42e90441c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7ff42e9098e6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7ff42dc1f73b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7ff42dc74ccd in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #17 0x7ff42dc75209 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x7ff42b7aee3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x7ff42b7af1d0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #20 0x7ff42b7af27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7ff42dc75eaf in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7ff42dc1ceca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7ff42dc24fac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x55acf60b69d5 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 356114] Baloo crash - Baloo::PositionCodec::decode
https://bugs.kde.org/show_bug.cgi?id=356114 Jonathan Ryshpan changed: What|Removed |Added CC||jonr...@pacbell.net --- Comment #3 from Jonathan Ryshpan --- I see exactly the same thing using Fedora-23. Balloo is identified as: $ rpm -qf /usr/bin/baloo_file_extractor kf5-baloo-file-5.19.0-1.fc23.x86_64 I am running Firefox with an unusually larger number of windows+tabs Windows: 14, Tabs: 58, which seems to affect system performance. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360738] New: Plasma crashes when I start xsane.
https://bugs.kde.org/show_bug.cgi?id=360738 Bug ID: 360738 Summary: Plasma crashes when I start xsane. Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jonr...@pacbell.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I was started xsane by entering "sane" into the KDE application launcher. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f29ee34f940 (LWP 1584))] Thread 16 (Thread 0x7f29cd8f6700 (LWP 1585)): #0 0x7f29e5d2dfdd in poll () at /lib64/libc.so.6 #1 0x7f29ec1e8272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f29ec1e9ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f29d0220da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f29e69363de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f29e507160a in start_thread () at /lib64/libpthread.so.0 #6 0x7f29e5d39a4d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f29c6db4700 (LWP 1711)): #0 0x7ffec29a6989 in () #1 0x7ffec29a6cb5 in clock_gettime () #2 0x7f29e5d47cc6 in clock_gettime () at /lib64/libc.so.6 #3 0x7f29e69e6956 in qt_gettime() () at /lib64/libQt5Core.so.5 #4 0x7f29e6b6b949 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #5 0x7f29e6b6beb5 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #6 0x7f29e6b6d2ae in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #7 0x7f29e125070d in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #8 0x7f29e125109b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #9 0x7f29e125127c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #10 0x7f29e6b6decb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7f29e6b14eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7f29e6931434 in QThread::exec() () at /lib64/libQt5Core.so.5 #13 0x7f29eac7f9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #14 0x7f29e69363de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #15 0x7f29e507160a in start_thread () at /lib64/libpthread.so.0 #16 0x7f29e5d39a4d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f29bdf4f700 (LWP 1729)): #0 0x7f29e5d29bcd in read () at /lib64/libc.so.6 #1 0x7f29e1294390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f29e1250c64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f29e1251110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f29e125127c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f29e6b6decb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f29e6b14eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f29e6931434 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f29eac7f9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7f29e69363de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f29e507160a in start_thread () at /lib64/libpthread.so.0 #11 0x7f29e5d39a4d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f29b7fff700 (LWP 1753)): #0 0x7f29e5d29bcd in read () at /lib64/libc.so.6 #1 0x7f29e1294390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f29e1250c64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f29e1251110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f29e125127c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f29e6b6decb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f29e6b14eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f29e6931434 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f29eac7f9b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7f29e69363de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f29e507160a in start_thread () at /lib64/libpthread.so.0 #11 0x7f29e5d39a4d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f29b6bd5700 (LWP 1761)): #0 0x7f29e5076b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f29edad8514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2
[Baloo] [Bug 360523] New: Baloo crashes on system boot
https://bugs.kde.org/show_bug.cgi?id=360523 Bug ID: 360523 Summary: Baloo crashes on system boot Product: Baloo Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: jonr...@pacbell.net CC: pinak.ah...@gmail.com Application: baloo_file_extractor (5.19.0) Qt Version: 5.5.1 Operating System: Linux 4.4.4-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I had just rebooted the computer. To repeat, this happens every time the system is booted. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7eff1184b8c0 (LWP 2405))] Thread 2 (Thread 0x7efefa64f700 (LWP 2406)): #0 0x7eff0ddf4fdd in poll () at /lib64/libc.so.6 #1 0x7eff084a9272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7eff084aaee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7efefd9c1da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7eff0e9fd3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7eff0cf0660a in start_thread () at /lib64/libpthread.so.0 #6 0x7eff0de00a4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7eff1184b8c0 (LWP 2405)): [KCrash Handler] #5 0x7eff0de46af7 in __memcpy_avx_unaligned () at /lib64/libc.so.6 #6 0x7eff10b67ca2 in Baloo::PostingCodec::decode(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #7 0x7eff10b50224 in Baloo::PostingDB::get(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #8 0x7eff10b6407d in Baloo::WriteTransaction::commit() () at /lib64/libKF5BalooEngine.so.5 #9 0x7eff10b5a4c2 in Baloo::Transaction::commit() () at /lib64/libKF5BalooEngine.so.5 #10 0x55b48b7360dc in Baloo::App::processNextFile() () #11 0x7eff0ec19888 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #12 0x7eff0ec0e113 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #13 0x7eff0f8c341c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7eff0f8c88e6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7eff0ebde73b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7eff0ec33ccd in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #17 0x7eff0ec34209 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x7eff0c76de3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x7eff0c76e1d0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #20 0x7eff0c76e27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7eff0ec34eaf in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7eff0ebdbeca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7eff0ebe3fac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x55b48b7349d5 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 360242] New: Baloo crashed after invoking "Print" on a web page
https://bugs.kde.org/show_bug.cgi?id=360242 Bug ID: 360242 Summary: Baloo crashed after invoking "Print" on a web page Product: Baloo Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: jonr...@pacbell.net CC: pinak.ah...@gmail.com Application: baloo_file_extractor (5.19.0) Qt Version: 5.5.1 Operating System: Linux 4.4.3-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I had just invoked "Print" on the page http://www.theatlantic.com/international/archive/2015/10/how-isis-started-syria-iraq/412042/ being displayed by Firefox -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f40ddfd78c0 (LWP 24933))] Thread 2 (Thread 0x7f40c6ddb700 (LWP 24936)): #0 0x7f40da580fdd in poll () at /lib64/libc.so.6 #1 0x7f40d4c35272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f40d4c36ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f40ca14dda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f40db1893de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f40d969260a in start_thread () at /lib64/libpthread.so.0 #6 0x7f40da58ca4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f40ddfd78c0 (LWP 24933)): [KCrash Handler] #5 0x7f40da5d2af7 in __memcpy_avx_unaligned () at /lib64/libc.so.6 #6 0x7f40dd2f3ca2 in Baloo::PostingCodec::decode(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #7 0x7f40dd2dc224 in Baloo::PostingDB::get(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #8 0x7f40dd2f007d in Baloo::WriteTransaction::commit() () at /lib64/libKF5BalooEngine.so.5 #9 0x7f40dd2e64c2 in Baloo::Transaction::commit() () at /lib64/libKF5BalooEngine.so.5 #10 0x5646a8adb0dc in Baloo::App::processNextFile() () #11 0x7f40db3a5888 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #12 0x7f40db39a113 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #13 0x7f40dc04f41c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7f40dc0548e6 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7f40db36a73b in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7f40db3bfccd in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #17 0x7f40db3c01d1 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x7f40d8ef9e3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x7f40d8efa1d0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #20 0x7f40d8efa27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7f40db3c0eaf in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7f40db367eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7f40db36ffac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x5646a8ad99d5 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
