PrtScrn button does not produce screenshot in kubuntu saucy

Bug #1243733 reported by Sergio Callegari
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
KDE Base Workspace
Fix Released
Medium
kde-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Pressing the button nothing happens. Before the upgrade to saucy, this used to work in raring.

Tags: bot-comment
Revision history for this message
In , Alexander Mezin (mezin-alexander) wrote :

When I press "Print Screen", nothing happens.
If I set any shortcut without "Print Screen", KSnapshot starts.

Ctrl+Print Screen, Alt+Print Screen and so on don't work. Ctrl+Shift+P does.

Reproducible: Always

Steps to Reproduce:
1. Press "Print Screen"
Actual Results:
Nothing happens

Expected Results:
KSnapshot should be started

Xorg server 1.14.3

Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

Please check "System Settings > Shortcuts > Global Shortcuts > component khotkeys", if the "Print" hotkey is indeed assigned to KSnaphot. If not, you have to set it in kmenuedit.

Revision history for this message
In , Alexander Mezin (mezin-alexander) wrote :

Yes, "Print" is assigned.
And if I assign another shortcut without "Print" in it, it starts working.

Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

Odd, cannot reproduce. Setting just "Print" shortcut for KSnapshot in kmenuedit makes it appear correctly in System Settings, and simply pressing "Prt Sc" key launches KSnapshot from then on.

You could check bug 166608, it contains additional tips or hints.

Revision history for this message
Sergio Callegari (callegar) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1243733/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → kubuntu-meta (Ubuntu)
Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing in favor of upstream report, please follow up with the KDE developers to get this resolved.

affects: kubuntu-meta (Ubuntu) → kde-workspace (Ubuntu)
Changed in kde-workspace (Ubuntu):
status: New → Invalid
Changed in kdebase-workspace:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Sergio Callegari (callegar) wrote :

Does this mean that the bug actually remains visible in launchpad and associated to saucy, so that there is memory that saucy shows the bug and that the upstream activity can be tracked?
E.g., if fix gets committed upstream for next release, to see if it is worth backporting to current ubuntu, etc?

Revision history for this message
In , Iwasanewt (iwasanewt) wrote :

I have the same problem ever since I upgraded to 13.10
However, if I set the shortcut to the "pause" button, everything works as expected. If I set it back to "prt sc", the shortcut stops working.

Revision history for this message
In , Alexander Mezin (mezin-alexander) wrote :

Interestingly, everything works on Debian Sid.
Maybe it's systemd problem (logind? udev?). I had systemd 208 on Gentoo, and on Debian only have 204.

Revision history for this message
Bas Roufs (basroufs) wrote :

At present, I have 2 laptops with Kubuntu 13.10 as primary system - in both cases freshly installed via exactly the same manual insttall procedure. At one of them, an Asus Eee PC 1001 HA, K Snapshot works perfectly well when hitting the printscreen button. However, on my HP Pavilion dm1, nothing happens when hitting the prt sc button from the Kubuntu 13.10 partition: so, at that machine, the problem effects me like in the case of Sergio Callegeri.

Have a good weekend.
Respectfully yours,
Bas G. Roufs.

Revision history for this message
In , Anidev-aelico (anidev-aelico) wrote :

I am currently running KDE 4.11.3 on opensuse 13.1, and have the exact same issue. Under khotkeys, the PrintScreen command is bound to the "Print" button, which is the print screen button, but pressing that button does nothing. Assigning any other shortcut does work. The print screen button itself is recognized by other programs such as xev, but it just doesn't launch the ksnapshot program. Setting any other command in khotkeys to the print screen button doesn't work either.

Is there a good way to debug this issue and find out what is swallowing the button press? All I know is that it used to work with kde 4.10, but now it doesn't.

Revision history for this message
Camilo Gonzalez (yhwh-aggro) wrote :

I have the same problem when i upgraded from ubuntu 12.04 to ubuntu 14.04
any other shorcut works but not print

Revision history for this message
In , Camilo Gonzalez (yhwh-aggro) wrote :

Actually i think i have found a fix, i have a pavilion hp laptop

using xev, i found in laptop print screen button is key 218

"KeyRelease event, serial 40, synthetic NO, window 0x5600001,
    root 0xb1, subw 0x0, time 3380983, (57,-5), root:(57,542),
    state 0x0, keycode 218 (keysym 0xff61, Print), same_screen YES,
    XKeysymToKeycode returns keycode: 107
    XLookupString gives 0 bytes:
    XFilterEvent returns: False"

Using my desktop computer, and another laptop (not hp) i found that key normally is key 107 not 218

"KeyRelease event, serial 40, synthetic NO, window 0x3200001,
    root 0xaa, subw 0x0, time 4327134, (67,-10), root:(67,797),
    state 0x0, keycode 107 (keysym 0xff61, Print), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False"

I think is some rare hp keyboard implementation

command "xmodmap -e "keycode 107 = Sys_Req" returns:

keycode 107 = Print Sys_Req Print Sys_Req
keycode 218 = Print NoSymbol Print

i tried removing key 107 as print using " xmodmap -e "keycode 107 = Sys_Req "

command "xmodmap -e "keycode 107 = Sys_Req" now returns:

keycode 218 = Print NoSymbol Print

after that the key started working for me

( later i have restored the original, key 107 config, and print screen still works... ?¿?)

Revision history for this message
In , David Chambers (cdpuff) wrote :

Thank you, Camilio! I had the same problem, and tried the above xev/xmodmap fix and eventually got it to work. But my keymap was different --

Fedora 20, KDE. Machine is an HP laptop, Pavilion dv6 (dv61-7000).

1. PrtSc does nothing.

2. xmodmap -pk | grep Print returns
        191 0xff61 (Print) 0xff15 (Sys_Req) 0xff61 (Print) 0xff15 (Sys_Req)
        218 0xff61 (Print) 0x0000 (NoSymbol) 0xff61 (Print)

3. xmodmap -e "keycode 191 = Sys_Req"

4. PrtSc now correctly lauches ksnapshot.

5. xmodmap -pk | grep Print now returns
        218 0xff61 (Print) 0x0000 (NoSymbol) 0xff61 (Print)

Revision history for this message
In , Alexander Mezin (mezin-alexander) wrote :

Now it works with KDE 4.13 (workspaces 4.11)

Changed in kdebase-workspace:
status: New → Fix Released
Revision history for this message
In , Néstor Acevedo (sainthyoga2003) wrote :

I am sorry if this bug is in "fixed" but I am using openSUSE 13.2, KDE 4.14.9 and I have the same issue: Print key assigned to kshorcuts, recognized key but doesn't launch Ksnapshot. If I assign for instance Meta+P ksnapshot is launched.

Print Screen was working until around 1 year but now is not working. If I launch Yast (I guess is Qt) the print key works (doesn't launch ksnapshot, but else shows save dialog).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.