[kmines] [Bug 92097] add randomness avoidance logic
https://bugs.kde.org/show_bug.cgi?id=92097 JStrebel changed: What|Removed |Added CC||joerg.stre...@gmail.com --- Comment #13 from JStrebel --- I support this feature request and would offer a possible solution - please https://github.com/JoergStrebel/minesweeper I am a fan of KMines and I think this would improve the player experience. Could you please give me some feedback if you would be interested into incorporating such a functionality into KMines? I could contribute a patch if enough people find it interesting. Extending KMines should not be so hard. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 472669] New: CPU usage goes to 100% after closing the KDevelop window
https://bugs.kde.org/show_bug.cgi?id=472669 Bug ID: 472669 Summary: CPU usage goes to 100% after closing the KDevelop window Classification: Applications Product: kdevelop Version: 5.7.211203 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: joerg.stre...@gmail.com Target Milestone: --- SUMMARY After working in KDevelep on some C++ code, I save my files and close the KDevelop window successfully. Then the kdevelop process goes to 100% CPU usage (visible in "top" CLI tool). Killing kdevelop using kill SIGTERM does not work, only using SIGKILL. STEPS TO REPRODUCE 1. Run Kdevelop 2. Close Kdevelop window (end session) 3. inspect kdevelop process in "top" OBSERVED RESULT kdevelop process is using 100% CPU capacity EXPECTED RESULT kdevelop process is no longer visible in "top" SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.69-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 540 @ 2.53GHz Memory: 3.7 GiB of RAM Graphics Processor: NVA8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 472669] CPU usage goes to 100% after closing the KDevelop window
https://bugs.kde.org/show_bug.cgi?id=472669 --- Comment #2 from JStrebel --- I exited KDevelop and after waiting 10 minutes, the kdevelop process is still using 100% CPU. So I don't think the kdevelop process is doing anything meaningful. Clearing the cache using jstrebel@phoenix:~> CLEAR_DUCHAIN_DIR=1 kdevelop OR deleting the directories ~/.cache/kdevelop and kdevduchain did not change the faulty behaviour. Here is the contents of the file kdevelop-freeze-on-exit.bt: [New LWP 1970] [New LWP 1971] [New LWP 1972] [New LWP 1977] [New LWP 1979] [New LWP 1985] [New LWP 1986] [New LWP 2007] [New LWP 2092] [New LWP 2123] [New LWP 2126] [New LWP 2127] [New LWP 2128] [New LWP 2129] [New LWP 2130] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f46146f98ca in ?? () from /usr/lib64/libKDevPlatformLanguage.so.57 Thread 16 (Thread 0x7f457e7fc700 (LWP 2130) "Queue(0x55dfa86"): #0 0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4615f0f19b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7f460cde7feb in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f460cde6650 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f460cde6f1b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f4615f088bc in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f460e93c6ea in start_thread () from /lib64/libpthread.so.0 #12 0x7f461592749f in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f457effd700 (LWP 2129) "Queue(0x55dfa86"): #0 0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4615f0f19b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7f460cde7feb in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f460cde6650 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f460cde6f1b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f4615f088bc in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f460e93c6ea in start_thread () from /lib64/libpthread.so.0 #12 0x7f461592749f in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f457f7fe700 (LWP 2128) "Queue(0x55dfa86"): #0 0x7f460e94370c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4615f0f19b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7f460cde7feb in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f460cde6650 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f460cdea1d2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f460cde7f0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f460cde6f1b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f4615f088bc in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f460e93c6ea in start_thread () from /lib64/libpthread.so.0 #12 0x7f461592749f in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f457700 (LWP 2127) "Queue(0x55dfa86"): #0 0x7f460e94370c in pthrea
[kdesrc-build] [Bug 447121] New: Setup of kdesrc-build on openSUSE Leap 15.3 does not work
https://bugs.kde.org/show_bug.cgi?id=447121 Bug ID: 447121 Summary: Setup of kdesrc-build on openSUSE Leap 15.3 does not work Product: kdesrc-build Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: joerg.stre...@gmail.com Target Milestone: --- SUMMARY *** I tried to execute the commands on the tutorial https://community.kde.org/Get_Involved/development#One-time_setup:_your_development_environment to set up my KDE development environment on my openSUSE Leap 15.3 Linux box. When running ./kdesrc-build --initial-setup, I receive the error message: pkgconfig(libattr)' wurde in den Paketnamen nicht gefunden. Fähigkeiten werden durchsucht. Keine Anbieter von pkgconfig(libattr)' gefunden. * Ran into an error with the installer! * You already have a configuration file: ~/.kdesrc-buildrc * Update your ~/.bashrc? (y/N) N So it cannot resolve the dependency on libattr. And the tool skips the rest of the package checks, so I think I am missing some dependencies. It does not build anything. I tried to find libattr myself, but no chance. *** STEPS TO REPRODUCE 1. open Konsole and create a root shell 2. execute the steps in the tutorial: mkdir -p ~/kde/src cd ~/kde/src/ git clone https://invent.kde.org/sdk/kdesrc-build.git && cd kdesrc-build ./kdesrc-build --initial-setup OBSERVED RESULT See error message above in the summary EXPECTED RESULT kdesrc-build --initial-setup retrieves / installs all dependencies. My Linux configuration is standard and all update processes usually work. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE LEAP 15.3, fully updated. (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 447121] Setup of kdesrc-build on openSUSE Leap 15.3 does not work
https://bugs.kde.org/show_bug.cgi?id=447121 JStrebel changed: What|Removed |Added Resolution|MOVED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 447121] Setup of kdesrc-build on openSUSE Leap 15.3 does not work
https://bugs.kde.org/show_bug.cgi?id=447121 --- Comment #2 from JStrebel --- I closed the defect https://invent.kde.org/sdk/kdesrc-build/-/issues/88 on the issue tracker, so this bug will only live here. I gave a wrong summary - I don't open a root shell in step #1, I am just using a regular shell, but I get asked for my sudo password. Maybe that's why I wrote about that root shell. Here are my steps: 1. open regular Konsole window 2. cd ~/kde/src/kdesrc-build 3. ./kdesrc-build --initial-setup Error message is the same as in the summary. In parallel, I started the rest of the tutorial and I can build the helloworld program just fine, so I don't have general issue with KDE libraries. -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 92097] add randomness avoidance logic
https://bugs.kde.org/show_bug.cgi?id=92097 --- Comment #15 from JStrebel --- > I was also thinking of implementing this option. So, to me at least, this is > wanted. However, I was simply going to port over the algorithm given in > https://www.chiark.greenend.org.uk/~sgtatham/puzzles/js/mines.html, which I > see you've already considered (and rejected?). The thing with this algorithm is that it claims to always produce solvable minefields, but I am not so sure. This algorithm is also used in the Android app "Antimine" (https://play.google.com/store/apps/details?id=com.logical.minato&hl=en_US&gl=US). I have been playing ca. 30 games there on medium difficulty and I ran into numerous situation, where I had the impression that only guessing would help me (and I have screenshots for others to check my assumption). So I am not so sure that this algorithm is really effective. I said above that KMines should be easy to extend with the Gecode library, but I am not so sure anymore. KDE games use a pretty intricate build system. I tried to build the current version of KMines on openSUSE Leap 15.3, but I failed because of outdated dependencies. Maybe I need to build a fork first and then investigate how to incorporate my changes into the official KMines repo. -- You are receiving this mail because: You are watching all bug changes.
