<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>257900</bug_id>
          
          <creation_ts>2010-11-25 18:31:05 +0000</creation_ts>
          <short_desc>XF86Calculator key doesn&apos;t work as trigger</short_desc>
          <delta_ts>2024-01-30 18:10:55 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>10</classification_id>
          <classification>Unmaintained</classification>
          <product>khotkeys</product>
          <component>general</component>
          <version>4.10.0</version>
          <rep_platform>Arch Linux</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          <see_also>https://bugs.kde.org/show_bug.cgi?id=478936</see_also>
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Stephen Baker">cycoone</reporter>
          <assigned_to name="Michael Jansen">kde</assigned_to>
          <cc>adaptee</cc>
    
    <cc>agostinelli</cc>
    
    <cc>ali240</cc>
    
    <cc>faure</cc>
    
    <cc>Foxandxss</cc>
    
    <cc>jmeidal</cc>
    
    <cc>johu</cc>
    
    <cc>kde</cc>
    
    <cc>kde</cc>
    
    <cc>kde</cc>
    
    <cc>leonardopl</cc>
    
    <cc>maarizwan</cc>
    
    <cc>mattsch</cc>
    
    <cc>motosauro</cc>
    
    <cc>philipp.woelfel</cc>
    
    <cc>quantumphazor</cc>
    
    <cc>sendel2000</cc>
    
    <cc>stupor_scurvy343</cc>
    
    <cc>vectro</cc>
          
          <cf_commitlink>http://commits.kde.org/kdelibs/1c7ae18ef5d1b7adbb271c1164d0d899eb6d4ed8</cf_commitlink>
          <cf_versionfixedin>4.9.1</cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>160</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1049355</commentid>
    <comment_count>0</comment_count>
    <who name="Stephen Baker">cycoone</who>
    <bug_when>2010-11-25 18:31:05 +0000</bug_when>
    <thetext>Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

I have been trying to use the calculator key on my Microsoft Multimedia Pro keyboard to launch kcalc.  I tried setting it up as a global shortcut under custom actions, and through the edit menu dialog.

When I press the Calculator button it is registered in the trigger as Launch(1) but after clicking apply it doesn&apos;t have any effect.  Using another shortcut like Meta+c works as expected.

xev for that key shows the following:

KeyPress event, serial 34, synthetic NO, window 0x5000001,
    root 0x107, subw 0x0, time 13592514, (763,758), root:(766,781),
    state 0x0, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False



Reproducible: Always

Steps to Reproduce:
Right click K-menu and choose Menu Editor
Click on the KCalc entry
Click Advanced
Click the button beside Current Shortcut Key
Press the Calculator key (Launch(1) will show up on the button)
Click save settings
Press the calculator key

Actual Results:  
Nothing

Expected Results:  
KCalc should open</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1066333</commentid>
    <comment_count>1</comment_count>
    <who name="Philipp Woelfel">philipp.woelfel</who>
    <bug_when>2011-01-01 09:31:28 +0000</bug_when>
    <thetext>I can confirm this on KDE 4.5.4., OpenSuSE 11.3 packages, with a Microsoft Natural Ergonomic Keyboard 4000.

A workaround as posted at http://forum.kde.org/viewtopic.php?f=17&amp;t=89602 works for me: In khotkeysrc and kglobalshortcutsrc I replaced the occurrences of &quot;Launch (1)&quot; with &quot;Calculator&quot; (while not logged into KDE). After that the calculator key starts the program assigned to it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1066334</commentid>
    <comment_count>2</comment_count>
    <who name="Philipp Woelfel">philipp.woelfel</who>
    <bug_when>2011-01-01 09:34:47 +0000</bug_when>
    <thetext>Bug 255329 is a duplicate of this one...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1123233</commentid>
    <comment_count>3</comment_count>
    <who name="Andrew M">quantumphazor</who>
    <bug_when>2011-05-26 09:45:16 +0000</bug_when>
    <thetext>I would like to confirm this problem in both KDE 4.5.5 on Ubuntu and 4.6.3 on Arch.

If you do the config file hack to force it manually, the menu editor correctly displays &quot;Calculator&quot; as the hot key. If you then try to set it by pressing the calculator key it sets it to Launch(1). Launch(1) is actually a generic hot key sometimes found as Fn+F2/F3 on laptops.

I have tried this on Microsoft Digital Media keyboard 1.0a and Wireless desktop 1000. Until someone says otherwise I think it&apos;s safe to assume that it effects all MS keyboards with the calculator key.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1167024</commentid>
    <comment_count>4</comment_count>
    <who name="Andrew M">quantumphazor</who>
    <bug_when>2011-09-26 09:42:47 +0000</bug_when>
    <thetext>Still effects KDE 4.7.1

Can this please be marked as confirmed? It should effect any user with a Microsoft keyboard.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1169579</commentid>
    <comment_count>5</comment_count>
    <who name="Matteo Agostinelli">agostinelli</who>
    <bug_when>2011-10-03 14:56:28 +0000</bug_when>
    <thetext>*** Bug 283249 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1199928</commentid>
    <comment_count>6</comment_count>
    <who name="sendel">sendel2000</who>
    <bug_when>2011-12-15 06:07:30 +0000</bug_when>
    <thetext>in KDE 4.7.1 still, with Logitech Internet Keyboard</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1226471</commentid>
    <comment_count>7</comment_count>
    <who name="">motosauro</who>
    <bug_when>2012-02-13 16:00:25 +0000</bug_when>
    <thetext>Absolutely confirmed
I&apos;m on Gentoo, KDE 4.7.4
and the problem is still there:
khotkeys stubbornly thinks that the calculator key on all of my keyboards is the &quot;Launch (1)&quot; key
I used a Microsoft ComfortCurve2000, a Logitech k750 and a Logitech k710 all with the same result, so I&apos;m pretty sure it&apos;s not hardware related
All other multimedia Keys work as expected

xev reports this:
KeyPress event, serial 35, synthetic NO, window 0x6e00001,
    root 0x15d, subw 0x6e00002, time 133413435, (63,62), root:(1801,93),
    state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x6e00001,
    root 0x15d, subw 0x6e00002, time 133413535, (63,62), root:(1801,93),
    state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1226477</commentid>
    <comment_count>8</comment_count>
    <who name="">motosauro</who>
    <bug_when>2012-02-13 16:11:30 +0000</bug_when>
    <thetext>(In reply to comment #7)
&gt; Absolutely confirmed
&gt; I&apos;m on Gentoo, KDE 4.7.4
&gt; and the problem is still there:
&gt; khotkeys stubbornly thinks that the calculator key on all of my keyboards is
&gt; the &quot;Launch (1)&quot; key
cut ...

Forgot to mention that for me too manually changing &quot;Launch (1)&quot; with &quot;Calculator&quot; in both .kde4/share/config/khotkeysrc and .kde4/share/config/kglobalshortcutsrc fixes the problem</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1228169</commentid>
    <comment_count>9</comment_count>
    <who name="Christoph Feck">cfeck</who>
    <bug_when>2012-02-18 14:05:12 +0000</bug_when>
    <thetext>*** Bug 263109 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1230454</commentid>
    <comment_count>10</comment_count>
      <attachid>69094</attachid>
    <who name="Leonardo">leonardopl</who>
    <bug_when>2012-02-25 21:12:00 +0000</bug_when>
    <thetext>Created attachment 69094
This patch fix the bug

This patch fix the bug</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1230535</commentid>
    <comment_count>11</comment_count>
      <attachid>69094</attachid>
    <who name="Leonardo">leonardopl</who>
    <bug_when>2012-02-26 10:13:39 +0000</bug_when>
    <thetext>Comment on attachment 69094
This patch fix the bug

&gt;--- kdelibs-4.8.0/kdeui/util/kkeyserver_x11.cpp	2012-02-25 18:53:49.480771132 -0200
&gt;+++ kkeyserver_x11.cpp	2012-02-25 18:20:38.912403430 -0200
&gt;@@ -355,7 +355,7 @@
&gt;     { Qt::Key_MediaRecord, XF86XK_AudioRecord },
&gt;     { Qt::Key_LaunchMail, XF86XK_Mail },
&gt;     { Qt::Key_Launch0,    XF86XK_MyComputer },
&gt;-    { Qt::Key_Calculator,    XF86XK_Calculator },
&gt;+    { Qt::Key_Launch1,    XF86XK_Calculator },
&gt;     { Qt::Key_Memo,    XF86XK_Memo },
&gt;     { Qt::Key_ToDoList,    XF86XK_ToDoList },
&gt;     { Qt::Key_Calendar,    XF86XK_Calendar },</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1282513</commentid>
    <comment_count>12</comment_count>
    <who name="Jesus">Foxandxss</who>
    <bug_when>2012-08-07 10:32:27 +0000</bug_when>
    <thetext>KDE 4.9, the bug is still there. It&apos;s boring to patch every new version to get the calc key working.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283209</commentid>
    <comment_count>13</comment_count>
    <who name="David Faure">faure</who>
    <bug_when>2012-08-09 11:12:33 +0000</bug_when>
    <thetext>This looks like a workaround to me. Does this mean Qt handles Qt::Key_Calculator badly?

I grepped qt4 src/gui and I see no difference between Key_Calculator and Key_Launch1, on X11. They are both in qkeymapper_x11.cpp and in qkeysequence.cpp

Ah, but qkeymapper_x11.cpp maps XF86XK_Calculator to both!

Isn&apos;t the right fix to remove the line 1066, which says
  XF86XK_Calculator,          Qt::Key_Launch1,
?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283238</commentid>
    <comment_count>14</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-09 13:17:55 +0000</bug_when>
    <thetext>(In reply to comment #13)
&gt; This looks like a workaround to me. Does this mean Qt handles
&gt; Qt::Key_Calculator badly?
&gt; 
&gt; I grepped qt4 src/gui and I see no difference between Key_Calculator and
&gt; Key_Launch1, on X11. They are both in qkeymapper_x11.cpp and in
&gt; qkeysequence.cpp
&gt; 
&gt; Ah, but qkeymapper_x11.cpp maps XF86XK_Calculator to both!
&gt; 
&gt; Isn&apos;t the right fix to remove the line 1066, which says
&gt;   XF86XK_Calculator,          Qt::Key_Launch1,
&gt; ?

I looked at the source as well for qt-gui.  I saw the two mappings but did you also notice that the second one has calculator misspelled as calculater?  It might be better to shift a few lines around instead of deleting the properly spelled one so the properly spelled one is maintained and the misspelled one is deleted -- XF86XK_Calculator being the proper spelling and not XF86XK_Calculater.  I&apos;ll try testing it to see if that would work.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283259</commentid>
    <comment_count>15</comment_count>
      <attachid>73062</attachid>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-09 14:31:43 +0000</bug_when>
    <thetext>Created attachment 73062
qt-gui-4.8.2-calculator-key.patch

I just confirmed that patching qt-gui works without needing to patch kdelibs.  It seems like the qt guys even know that some of the key shortcuts are screwed up as well? (// ### Qt 5: remap properly)  I wonder if this calculator key bug has also been fixed in qt 5.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283269</commentid>
    <comment_count>16</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-09 15:35:19 +0000</bug_when>
    <thetext>Although this qt patch fixes the problem, I wonder what the purpose of the misspelled calculator constant is for.  These constants in qt were pulled from XF86keysym.h from the x11proto package.  The misspelled &quot;XF86XK_Calculater&quot; constant which has a different hex value from &quot;XF86XK_Calculator&quot; originated in xfree86 XF86keysym.h revision 1.13 on 11/22/2002:  

522. Added support for special keys found on many ACPI control, Easy Access
      Keyboards, Internet keyboards, laptops, notebooks and PDA (via
      xkb/symbols/inet). Added new key symbols for these keyboards
      (Stanislav Brabec).

Before that commit, XF86XK_Calculator was the only one that existed.  

In revision 1.12, the keysym for XF86XK_Calculator was 0x1008FF1D.  This is the same symbol that my keyword uses (Microsoft Natural Keyboard 4000).  In revision 1.13 that keysym did not change while XF86XK_Calculater was added with a keysym of 0x1008FF54.  Strangely enough, the comments for XF86XK_Calculator note that the developer thinks they only apply to PDAs like Pocket PC and Palm while the other keysym 0x1008FF54 applies to &quot;internet keyboards&quot; which is what I guess my keyboard is.  I wonder if there are keyboards out there that register the calculator key as 0x1008FF54 instead of 0x1008FF1D as my keyboard does (you can test this with the xev program and looking at the keysym your calculator key emits).   In that case, my patch for qt-gui would not work for everyone.  I&apos;m thinking that maybe Qt::Key_Calculator should be applied to both the misspelled constant and the correctly spelled one instead.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283277</commentid>
    <comment_count>17</comment_count>
      <attachid>73065</attachid>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-09 15:58:48 +0000</bug_when>
    <thetext>Created attachment 73065
qt-gui-4.8.2-calculator-key.patch

I just tested my theory and that appears to work.  This patch would work for both types of keyboards that register the calculator key as 0x1008FF1D or 0x1008FF54.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283294</commentid>
    <comment_count>18</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-09 17:27:11 +0000</bug_when>
    <thetext>I just examined qt 5 alpha and unfortunately, it appears as though nothing as changed in qt 5 alpha in regards to this bug or any changes to the mapping of keys (file changed to qxcbkeyboard.cpp in qt 5) as indicated in that qt comment.  Perhaps this patch can be pushed to the qt developers so they can patch qt 4 and 5.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283302</commentid>
    <comment_count>19</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-09 17:45:30 +0000</bug_when>
    <thetext>I created a ticket on the qt tracker as well if anyone is interested: https://bugreports.qt-project.org/browse/QTBUG-26812</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283546</commentid>
    <comment_count>20</comment_count>
    <who name="David Faure">faure</who>
    <bug_when>2012-08-10 10:34:41 +0000</bug_when>
    <thetext>Thanks for your work on this. Unfortunately, for legal reasons, *you* have to be the one to push the patch to Qt5, and then to Qt4, via gerrit (http://codereview.qt-project.org).
Well, ok it&apos;s a one-liner, I guess it could be considered trivial enough for anyone to apply it.
But since I can&apos;t even test it, I&apos;d rather not do that myself :-)
In any case, the first step is to make a Qt5 patch (Qt contribution rules require a Qt5 fix before a Qt4 fix, so that no fix for 4 is forgotten in 5)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283583</commentid>
    <comment_count>21</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-10 13:52:41 +0000</bug_when>
    <thetext>(In reply to comment #20)
&gt; Thanks for your work on this. Unfortunately, for legal reasons, *you* have
&gt; to be the one to push the patch to Qt5, and then to Qt4, via gerrit
&gt; (http://codereview.qt-project.org).
&gt; Well, ok it&apos;s a one-liner, I guess it could be considered trivial enough for
&gt; anyone to apply it.
&gt; But since I can&apos;t even test it, I&apos;d rather not do that myself :-)
&gt; In any case, the first step is to make a Qt5 patch (Qt contribution rules
&gt; require a Qt5 fix before a Qt4 fix, so that no fix for 4 is forgotten in 5)

I don&apos;t mind submitting the patch myself but I&apos;m not sure how to sign up for an account and post to https://codereview.qt-project.org</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1283589</commentid>
    <comment_count>22</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-10 14:07:26 +0000</bug_when>
    <thetext>(In reply to comment #21)
&gt; (In reply to comment #20)
&gt; &gt; Thanks for your work on this. Unfortunately, for legal reasons, *you* have
&gt; &gt; to be the one to push the patch to Qt5, and then to Qt4, via gerrit
&gt; &gt; (http://codereview.qt-project.org).
&gt; &gt; Well, ok it&apos;s a one-liner, I guess it could be considered trivial enough for
&gt; &gt; anyone to apply it.
&gt; &gt; But since I can&apos;t even test it, I&apos;d rather not do that myself :-)
&gt; &gt; In any case, the first step is to make a Qt5 patch (Qt contribution rules
&gt; &gt; require a Qt5 fix before a Qt4 fix, so that no fix for 4 is forgotten in 5)
&gt; 
&gt; I don&apos;t mind submitting the patch myself but I&apos;m not sure how to sign up for
&gt; an account and post to https://codereview.qt-project.org

nm, I found the wiki on how to do it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1284028</commentid>
    <comment_count>23</comment_count>
    <who name="Leonardo">leonardopl</who>
    <bug_when>2012-08-12 11:51:41 +0000</bug_when>
    <thetext>Well, I think that patching the kdelibs is the most correct approach, because, according to http://qt-project.org/doc/qt-4.8/qt.html, Qt::Key_Calculator is not mapped on X11 and Qt::Key_Launch1 must be used instead. Anyway, even if the problem is with Qt, your path probably will not be accept, because, as stated in https://bugreports.qt-project.org/browse/QTBUG-25118 Qt5 is meant to have minimum source incompatibility. Therefore, I think this patch must be accept in kdelibs as soon as possible, because, as said before, is indeed annoying have to patch every new version to have the calculator key working.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1284331</commentid>
    <comment_count>24</comment_count>
    <who name="Matthew Schultz">mattsch</who>
    <bug_when>2012-08-13 12:40:16 +0000</bug_when>
    <thetext>Leonardo is right.  It would likely take a while for Qt to apply this patch, it&apos;s better to patch kdelibs now than to wait for the change to come through Qt assuming they agree to change it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1285770</commentid>
    <comment_count>25</comment_count>
    <who name="David Faure">faure</who>
    <bug_when>2012-08-17 17:38:28 +0000</bug_when>
    <thetext>What a mess, between the typo in the X headers and the full documentation of these quirks in the Qt API docs -- I had no idea the use of Launch1 was fully documented in Qt :-)

OK then, I&apos;ll apply the kdelibs fix.

Thanks for all the investigations.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1285771</commentid>
    <comment_count>26</comment_count>
    <who name="David Faure">faure</who>
    <bug_when>2012-08-17 17:41:47 +0000</bug_when>
    <thetext>Git commit 1c7ae18ef5d1b7adbb271c1164d0d899eb6d4ed8 by David Faure.
Committed on 17/08/2012 at 19:41.
Pushed by dfaure into branch &apos;KDE/4.9&apos;.

Fix handling of XF86Calculator, patch by &quot;Leonardo&quot;.

Full investigation details in the bug report.
FIXED-IN: 4.9.1

M  +3    -1    kdeui/util/kkeyserver_x11.cpp

http://commits.kde.org/kdelibs/1c7ae18ef5d1b7adbb271c1164d0d899eb6d4ed8</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1304065</commentid>
    <comment_count>27</comment_count>
    <who name="Ian Turner">vectro</who>
    <bug_when>2012-10-07 23:49:49 +0000</bug_when>
    <thetext>I&apos;m actually still seeing this issue in 4.9.2.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1304070</commentid>
    <comment_count>28</comment_count>
    <who name="Jesus">Foxandxss</who>
    <bug_when>2012-10-08 00:48:02 +0000</bug_when>
    <thetext>It&apos;s working for me since 4.9.1 Ian.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1304072</commentid>
    <comment_count>29</comment_count>
    <who name="Ian Turner">vectro</who>
    <bug_when>2012-10-08 01:04:26 +0000</bug_when>
    <thetext>Looks like I did not have the shortcut key set. Following Stephen&apos;s steps in the bug description, I see that the calculator key now works.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1322122</commentid>
    <comment_count>30</comment_count>
    <who name="Janek Bevendorff">kde</who>
    <bug_when>2012-12-08 12:54:51 +0000</bug_when>
    <thetext>Bug still present in 4.9.90. Is this a regression?
I did not re-check in 4.9.1 since I already applied the workaround from the forums several versions ago.
From my perspective I would say this was never fixed, but if it actually was in 4.9.1, then it seems to be back in 4.10.

xev correctly outputs:

KeyRelease event, serial 36, synthetic NO, window 0x4000001,
    root 0x135, subw 0x0, time 10647210, (561,-616), root:(563,226),
    state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

but when setting a shortcut I still get &quot;Launch (1)&quot; instead of &quot;Calculator&quot;.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1322140</commentid>
    <comment_count>31</comment_count>
    <who name="Ian Turner">vectro</who>
    <bug_when>2012-12-08 13:38:14 +0000</bug_when>
    <thetext>This WORKSFORME using KDE 4.9.2 on Ubuntu 12.04.1, however it requests root privileges for kcalc (I guess that&apos;s a different issue...)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1339408</commentid>
    <comment_count>32</comment_count>
    <who name="Stephen Baker">cycoone</who>
    <bug_when>2013-02-09 04:28:11 +0000</bug_when>
    <thetext>Still works for me in 4.9.5 and 4.10 on ArchLinux.  The shortcut trigger still says Launch(1), however the fix made pressing the calculator key work to trigger the event anyway.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1339451</commentid>
    <comment_count>33</comment_count>
    <who name="Janek Bevendorff">kde</who>
    <bug_when>2013-02-09 09:40:28 +0000</bug_when>
    <thetext>That&apos;s right, but it&apos;s still confusing that it says &quot;Launch (1)&quot;. It should really display &quot;Calculator&quot;. I wouldn&apos;t consider this issue fully fixed until then.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1339524</commentid>
    <comment_count>34</comment_count>
    <who name="Leonardo">leonardopl</who>
    <bug_when>2013-02-09 13:27:43 +0000</bug_when>
    <thetext>No, &quot;Launch (1)&quot; is how Qt handle this key. If you check the link that I posted before you&apos;ll see that       Qt::Key_Calculator is not mapped in X11 and you must use Qt::Key_Launch1 instead. If you still want it to display &quot;Calculator&quot; please open a ticket on Qt tracker since I don&apos;t think that this is a job to KDE do.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1477829</commentid>
    <comment_count>35</comment_count>
    <who name="David Edmundson">kde</who>
    <bug_when>2014-10-24 11:08:12 +0000</bug_when>
    <thetext>Tested on Qt5. Things seem to work for me.</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>69094</attachid>
            <date>2012-02-25 21:12:00 +0000</date>
            <delta_ts>2012-02-26 10:13:39 +0000</delta_ts>
            <desc>This patch fix the bug</desc>
            <filename>calculator-key.patch</filename>
            <type>text/plain</type>
            <size>521</size>
            <attacher name="Leonardo">leonardopl</attacher>
            
              <data encoding="base64">LS0tIGtkZXVpL3V0aWwva2tleXNlcnZlcl94MTEuY3BwCTIwMTItMDItMjUgMTg6NTM6NDkuNDgw
NzcxMTMyIC0wMjAwCisrKyBra2V5c2VydmVyX3gxMS5jcHAJMjAxMi0wMi0yNSAxODoyMDozOC45
MTI0MDM0MzAgLTAyMDAKQEAgLTM1NSw3ICszNTUsNyBAQAogICAgIHsgUXQ6OktleV9NZWRpYVJl
Y29yZCwgWEY4NlhLX0F1ZGlvUmVjb3JkIH0sCiAgICAgeyBRdDo6S2V5X0xhdW5jaE1haWwsIFhG
ODZYS19NYWlsIH0sCiAgICAgeyBRdDo6S2V5X0xhdW5jaDAsICAgIFhGODZYS19NeUNvbXB1dGVy
IH0sCi0gICAgeyBRdDo6S2V5X0NhbGN1bGF0b3IsICAgIFhGODZYS19DYWxjdWxhdG9yIH0sCisg
ICAgeyBRdDo6S2V5X0xhdW5jaDEsICAgIFhGODZYS19DYWxjdWxhdG9yIH0sCiAgICAgeyBRdDo6
S2V5X01lbW8sICAgIFhGODZYS19NZW1vIH0sCiAgICAgeyBRdDo6S2V5X1RvRG9MaXN0LCAgICBY
Rjg2WEtfVG9Eb0xpc3QgfSwKICAgICB7IFF0OjpLZXlfQ2FsZW5kYXIsICAgIFhGODZYS19DYWxl
bmRhciB9LAo=
</data>

          </attachment>
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>73062</attachid>
            <date>2012-08-09 14:31:43 +0000</date>
            <delta_ts>2012-08-09 15:58:48 +0000</delta_ts>
            <desc>qt-gui-4.8.2-calculator-key.patch</desc>
            <filename>qt-gui-4.8.2-calculator-key.patch</filename>
            <type>text/plain</type>
            <size>1562</size>
            <attacher name="Matthew Schultz">mattsch</attacher>
            
              <data encoding="base64">ZGlmZiAtdSAtciBxdC1ldmVyeXdoZXJlLW9wZW5zb3VyY2Utc3JjLTQuOC4yLW9yaWcvL3NyYy9n
dWkva2VybmVsL3FrZXltYXBwZXJfeDExLmNwcCBxdC1ldmVyeXdoZXJlLW9wZW5zb3VyY2Utc3Jj
LTQuOC4yL3NyYy9ndWkva2VybmVsL3FrZXltYXBwZXJfeDExLmNwcAotLS0gcXQtZXZlcnl3aGVy
ZS1vcGVuc291cmNlLXNyYy00LjguMi1vcmlnLy9zcmMvZ3VpL2tlcm5lbC9xa2V5bWFwcGVyX3gx
MS5jcHAJMjAxMi0wNC0yNiAxNDo0NjoxMC4wMDAwMDAwMDAgLTA1MDAKKysrIHF0LWV2ZXJ5d2hl
cmUtb3BlbnNvdXJjZS1zcmMtNC44LjIvc3JjL2d1aS9rZXJuZWwvcWtleW1hcHBlcl94MTEuY3Bw
CTIwMTItMDgtMDkgMDg6MzM6MjAuMzMyNTExNTIzIC0wNTAwCkBAIC03ODgsNyArNzg4LDYgQEAK
ICNkZWZpbmUgWEY4NlhLX0FwcGxpY2F0aW9uUmlnaHQgICAgMHgxMDA4RkY1MQogI2RlZmluZSBY
Rjg2WEtfQm9vayAgICAgICAgICAgICAgICAweDEwMDhGRjUyCiAjZGVmaW5lIFhGODZYS19DRCAg
ICAgICAgICAgICAgICAgIDB4MTAwOEZGNTMKLSNkZWZpbmUgWEY4NlhLX0NhbGN1bGF0ZXIgICAg
ICAgICAgMHgxMDA4RkY1NAogI2RlZmluZSBYRjg2WEtfQ2xlYXIgICAgICAgICAgICAgICAweDEw
MDhGRjU1CiAjZGVmaW5lIFhGODZYS19DbGVhckdyYWIgICAgICAgICAgIDB4MTAwOEZFMjEKICNk
ZWZpbmUgWEY4NlhLX0Nsb3NlICAgICAgICAgICAgICAgMHgxMDA4RkY1NgpAQCAtMTA2Myw3ICsx
MDYyLDcgQEAKICAgICBYRjg2WEtfQXVkaW9SZWNvcmQsICAgICAgICAgUXQ6OktleV9NZWRpYVJl
Y29yZCwKICAgICBYRjg2WEtfTWFpbCwgICAgICAgICAgICAgICAgUXQ6OktleV9MYXVuY2hNYWls
LAogICAgIFhGODZYS19NeUNvbXB1dGVyLCAgICAgICAgICBRdDo6S2V5X0xhdW5jaDAsICAvLyAj
IyMgUXQgNTogcmVtYXAgcHJvcGVybHkKLSAgICBYRjg2WEtfQ2FsY3VsYXRvciwgICAgICAgICAg
UXQ6OktleV9MYXVuY2gxLAorICAgIFhGODZYS19DYWxjdWxhdG9yLCAgICAgICAgICBRdDo6S2V5
X0NhbGN1bGF0b3IsCiAgICAgWEY4NlhLX01lbW8sICAgICAgICAgICAgICAgIFF0OjpLZXlfTWVt
bywKICAgICBYRjg2WEtfVG9Eb0xpc3QsICAgICAgICAgICAgUXQ6OktleV9Ub0RvTGlzdCwKICAg
ICBYRjg2WEtfQ2FsZW5kYXIsICAgICAgICAgICAgUXQ6OktleV9DYWxlbmRhciwKQEAgLTEwOTUs
NyArMTA5NCw2IEBACiAgICAgWEY4NlhLX0FwcGxpY2F0aW9uUmlnaHQsICAgIFF0OjpLZXlfQXBw
bGljYXRpb25SaWdodCwKICAgICBYRjg2WEtfQm9vaywgICAgICAgICAgICAgICAgUXQ6OktleV9C
b29rLAogICAgIFhGODZYS19DRCwgICAgICAgICAgICAgICAgICBRdDo6S2V5X0NELAotICAgIFhG
ODZYS19DYWxjdWxhdGVyLCAgICAgICAgICBRdDo6S2V5X0NhbGN1bGF0b3IsCiAgICAgWEY4NlhL
X0NsZWFyLCAgICAgICAgICAgICAgIFF0OjpLZXlfQ2xlYXIsCiAgICAgWEY4NlhLX0NsZWFyR3Jh
YiwgICAgICAgICAgIFF0OjpLZXlfQ2xlYXJHcmFiLAogICAgIFhGODZYS19DbG9zZSwgICAgICAg
ICAgICAgICBRdDo6S2V5X0Nsb3NlLAo=
</data>

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>73065</attachid>
            <date>2012-08-09 15:58:48 +0000</date>
            <delta_ts>2012-08-09 15:58:48 +0000</delta_ts>
            <desc>qt-gui-4.8.2-calculator-key.patch</desc>
            <filename>qt-gui-4.8.2-calculator-key.patch</filename>
            <type>text/plain</type>
            <size>839</size>
            <attacher name="Matthew Schultz">mattsch</attacher>
            
              <data encoding="base64">ZGlmZiAtdSAtciBxdC1ldmVyeXdoZXJlLW9wZW5zb3VyY2Utc3JjLTQuOC4yLW9yaWcvL3NyYy9n
dWkva2VybmVsL3FrZXltYXBwZXJfeDExLmNwcCBxdC1ldmVyeXdoZXJlLW9wZW5zb3VyY2Utc3Jj
LTQuOC4yL3NyYy9ndWkva2VybmVsL3FrZXltYXBwZXJfeDExLmNwcAotLS0gcXQtZXZlcnl3aGVy
ZS1vcGVuc291cmNlLXNyYy00LjguMi1vcmlnLy9zcmMvZ3VpL2tlcm5lbC9xa2V5bWFwcGVyX3gx
MS5jcHAJMjAxMi0wNC0yNiAxNDo0NjoxMC4wMDAwMDAwMDAgLTA1MDAKKysrIHF0LWV2ZXJ5d2hl
cmUtb3BlbnNvdXJjZS1zcmMtNC44LjIvc3JjL2d1aS9rZXJuZWwvcWtleW1hcHBlcl94MTEuY3Bw
CTIwMTItMDgtMDkgMTA6Mzg6MDQuMzc3ODE2NTAyIC0wNTAwCkBAIC0xMDYzLDcgKzEwNjMsNyBA
QAogICAgIFhGODZYS19BdWRpb1JlY29yZCwgICAgICAgICBRdDo6S2V5X01lZGlhUmVjb3JkLAog
ICAgIFhGODZYS19NYWlsLCAgICAgICAgICAgICAgICBRdDo6S2V5X0xhdW5jaE1haWwsCiAgICAg
WEY4NlhLX015Q29tcHV0ZXIsICAgICAgICAgIFF0OjpLZXlfTGF1bmNoMCwgIC8vICMjIyBRdCA1
OiByZW1hcCBwcm9wZXJseQotICAgIFhGODZYS19DYWxjdWxhdG9yLCAgICAgICAgICBRdDo6S2V5
X0xhdW5jaDEsCisgICAgWEY4NlhLX0NhbGN1bGF0b3IsICAgICAgICAgIFF0OjpLZXlfQ2FsY3Vs
YXRvciwKICAgICBYRjg2WEtfTWVtbywgICAgICAgICAgICAgICAgUXQ6OktleV9NZW1vLAogICAg
IFhGODZYS19Ub0RvTGlzdCwgICAgICAgICAgICBRdDo6S2V5X1RvRG9MaXN0LAogICAgIFhGODZY
S19DYWxlbmRhciwgICAgICAgICAgICBRdDo6S2V5X0NhbGVuZGFyLAo=
</data>

          </attachment>
      

    </bug>

</bugzilla>