Description of problem: Fresh install of Mageia 5 Beta 3 x86_64 with Mate desktop. After long running cauldron (since Mageia 4 Beta 1) i decided to freshen my root partition. After installing and starting guake i can see notification popup that says guake is started and i can press F12 to see it. When pressing F12 key nothing happens. Running from commandline reveals that i hit the known upstream bug https://github.com/Guake/guake/issues/260 Which is fixed by this commit:https://github.com/Guake/guake/commit/76679c889ac7bfe69dc7081db826f38b10ea5448 From Commandline: (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. (guake:12159): libglade-WARNING **: unknown attribute `swapped' for <signal>. Floating point exception This bug is fixed in guake-0.5.1 and above versions. Version-Release number of selected component (if applicable): guake-0.5.0-0.rc1.3.mga5 How reproducible: 1. Install guake on Mageia 5 Beta3 2. Run at commandline and see the exception Jani, i have guake-0.5.2 on my local machine which fixes this issue. Would you like me to commit to svn and ask for freeze push? Reproducible: Steps to Reproduce:
See Also: (none) => https://github.com/Guake/guake/issues/260
(In reply to Atilla ÃNTAÅ from comment #0) > Jani, i have guake-0.5.2 on my local machine which fixes this issue. Would > you like me to commit to svn and ask for freeze push? Sure, go ahead.
Thanks. Will do tonight. :-)
CC: (none) => jani.valimaaAssignee: jani.valimaa => tarakbumba
It is submitted to repos and seems worked flawlessly. Jani, why did you removed extra % on commented lines with http://svnweb.mageia.org/packages/cauldron/guake/current/SPECS/guake.spec?r1=815416&r2=815526&pathrev=815526? I have put them for fix rpmlint warnings.
(In reply to Atilla ÃNTAÅ from comment #3) > It is submitted to repos and seems worked flawlessly. Jani, why did you > removed extra % on commented lines with > http://svnweb.mageia.org/packages/cauldron/guake/current/SPECS/guake. > spec?r1=815416&r2=815526&pathrev=815526? I have put them for fix rpmlint > warnings. This is mostly off topic and you shouldn't be offended at all about my comments: You shouldn't have touched the release tag at all. Only thing needed some love was directory paths in source tag. Plus of course the patch and source additions. It was intentional to have such release and source tags they were before your changes. There seems to be prereleases over now and then and when upstream makes such release only thing I need to do is uncomment/comment prerel and edit rel macro. 'mgarepo sync -d' handles downloading correct tarball and release tag is also set automatically to the correct form. IMHO you can skip rpmlint's warning about macros in commented lines. Also, you shouldn't have changed tabs to spaces either. IMHO you can also ignore such warning from rpmlint output. However if you want to do something to tabs/spaces warning, please check if tabs were used previously in most of the lines (like it was the case) and then find lines with spaces and fix them. Same applies if most of the lines uses spaces, find lines with tabs and fix them. If you do such changes, please also mention them in commit msg. I see almost every day .specs which doesn't meet rpmlint's sometimes odd requirements. That's why I hardly never run .specs through rpmlint.
BTW, I'm closing this as FIXED.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Thank you. Non offended and learned a lot from you. Greetings.