Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13562 - [yakuake] 2.9.4-2 Section Sign global hotkey not working

Attached to Project: Arch Linux
Opened by Zeal (Zeal) - Thursday, 26 February 2009, 21:02 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 19 January 2010, 19:32 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Yakuake 2.9.4-2 Section sign § doesn't work as a global hotkey to Open/Retract Yakuake.
This was noticed after installing the latest version of Yakuake.
I've heard that i'm not the only one with this problem after the latest version.

Additional info:
Yakuake 2.9.4-2 under KDE 4.2

Steps to reproduce:
Download Yakuake 2.9.4-2 and try inserting § as a global hotkey to Open/Retract Yakuake
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 19 January 2010, 19:32 GMT
Reason for closing:  Deferred
Additional comments about closing:  No response in 7 months
Comment by hadrien marquet (plopito) - Thursday, 28 May 2009, 17:39 GMT
This is a very annoying bug :/
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 31 May 2009, 07:04 GMT
what is the status with the latest packages KDE 4.2.4 and Yakuake-2.9.6-1?
Comment by Zeal (Zeal) - Monday, 01 June 2009, 07:40 GMT
Im using KDE 4.2.3 and Yakuake-2.9.6-1 and the bug remains but slightly changes.
Now § works when you bind it, but after reboot you have to bind something else for the global key and then change it back to §.
Comment by hadrien marquet (plopito) - Friday, 05 June 2009, 10:54 GMT
It happens even with the lastest package (2.9.6-1) so i don't understand why you have closed it...
Comment by Andrea Scarpino (BaSh) - Friday, 23 October 2009, 05:32 GMT
Isn't this an upstream bug?
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 02 December 2009, 04:32 GMT
  • Field changed: Status (Assigned → Waiting on Response)

Loading...