Description of problem:if you play with gnome-mines under kde environment (I didn't try under gnome), and you lose and the mines explode, it may happens that everything freeze: mouse no longer works, no return from classical key-combinations (Ctrl+Alt+delete, for example) and the only way to quit this situation is to press the reset button of your PC case, which is not an optimal way to reboot. Version-Release number of selected component (if applicable): see source RPM above How reproducible:play gnome-mines under kde and lose Steps to Reproduce: 1.open the application mines 2.choose 30x16 99 mines (personnal set up doesn't work anyway) 3.make the mines to explode Reproducible: Steps to Reproduce:
Can you please try KMines, which is designed for use with KDE? kmines-1:4.14.3-1.mga5 I doubt anyone will be motivated to get Gnome mines to work well for everyone in KDE (here it gnome mines works well in KDE, btw, but only tried on a 32bit system)
CC: (none) => marja11
(In reply to Marja van Waes from comment #1) > Can you please try KMines, which is designed for use with KDE? > > kmines-1:4.14.3-1.mga5 > > I doubt anyone will be motivated to get Gnome mines to work well for > everyone in KDE (here it gnome mines works well in KDE, btw, but only tried > on a 32bit system) mines (mines, not kmines) works very well under KDE environment with mageia4 x86_64 with mageia5 x86_64, kmines works well under KDE
Assignee: bugsquad => kde
I guess this might be a feature from the GNOME project to undermine the KDE project ;) Joke aside, gnome-mines should not freeze KDE, using kmines instead is but a workaround.
Hi Igor, Thank you for having taken the needed time to report this issue! We regret if this issue didn't get fixed in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed. I assume this bug doesn't exist in Mageia 6 or later, because KDE (now Plasma5) is entirely different there. Closing as OLD. Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6.
Status: NEW => RESOLVEDResolution: (none) => OLD
(In reply to Marja Van Waes from comment #4) > Hi Igor, > > Thank you for having taken the needed time to report this issue! > > We regret if this issue didn't get fixed in Mageia 5. > > Mageia 5 has officially reached its End of Life on December 31st, 2017 > https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ > It only continued to get important security updates since then, but > non-security bugs have no chance of still getting fixed. > > I assume this bug doesn't exist in Mageia 6 or later, because KDE (now > Plasma5) is entirely different there. > > Closing as OLD. > > Please reopen this report and change its "Version:" at the top left to "6", > if the same bug still exists in Mageia 6. this bug is fixed in mageia6