Created attachment 111288 [details] Count is incorrect near bottom Count is incorrect (see attached screenshot): x212121 33x3x_x 1xxx___ Should be (assuming only 3s are wrong): x212121 34x4_?_ 1xxx___ or (assuming multiple #s are wrong): x211_11 34x31_x 1xxx1__
What's the output of kmines -v ? I don't understand your ASCII art, can you explain what it means?
$ kmines -v kmines 4.0 (29 Jan 2015) Explanation of ascii art: number is a number x is a mine _ is a blank (unknown) space These refer to the problem area on the bottom of the screen shot attached to the original report.
Sorry I don't have a later version. The version of kmines is the latest one in the Fedora 27 repo (sudo dnf upgrade says "Nothing to do."). I'll try recompiling from https://github.com/KDE/kmines
I cannot figure out how to compile--there is no autogen or other script, and ./configure, make, and qmake do nothing. There is no .pro file for qtcreator. I cannot find any guides online. The sourceforge project has tarballs, but they are 3 years old, though the GitHub "mirror" says modified one month ago. Do you have any clues?
Created attachment 111451 [details] Issue remains in git 2018-03-30 The 2 NE (up, right) from the yellow mine clicked should be a 3
OK, I got it to compile but still the same issue occurs (I added an additional screenshot, where the "2" NE (up, right) from the yellow mine clicked should be a "3") #howto compile (discovered myself by trial and error): sudo apt remove kmines sudo apt install cmake extra-cmake-modules libkf5-plasma-dev libkf5iconthemes-dev libkf5plasma-dev libkf5windowsystem-dev libkf5declarative-dev libkf5xmlgui-dev libkf5activities-dev libkf5wayland-dev libkf5crash-dev libkf5newstuff-dev kdoctools-dev kde-games-core-declarative libkdegames-dev libkf5kdegames-dev mkdir build cd build cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local make sudo make install
Ignore previous comment and image "Issue remains in git 2018-03-30". I noticed the mines I was counting were ones with x's which means they weren't mines, but rather places I flagged mines incorrectly. The case is also the same with the first screenshot, so I'll say this bug in general is unconfirmed. If I get a screenshot that demonstrates there is a bug I'll post it.
I'm actually going to close it as invalid. Unconfirmed means something like "a user found a bug but noone else has been able to reproduce it yet", as far as i understand, in this case you didn't really find a bug, you just made a mistake playing.