Xfce Forum

GS

Member

From: place once called Transylvania

Registered: 2010-06-23

Posts: 41

Logitech Keyboards and 3.2 kernel

Hi,

I'm using a Logitech K360 wireless keyboard. Since upgrade to kernel 3.2 in Debian Wheezy this keyboard has started behaving in a very peculiar manner. In all respects it seems to function normally -- with the exception that the arrow keys can't be used on the Xfce desktop for moving windows around.

If I hit the <Alt><Space> key combination then hit the <M> key to prepare to move a window, using the left and right arrow keys makes the window jump up and down as well as move left and right. Sometimes a window will jump upward so high that half of it is off-screen. When this happens, the arrow keys often cease to have any control over the window. At that point, only the mouse can be used to re-establish control of the window position.

If I maximize a window vertically (but leave it NOT maximized horizontally) the left and right arrow keys always work normally for moving the window back-and-forth.

It seems that other users of Logitech keyboards may be seeing odd behaviors with the new kernel. For example:

https://bbs.archlinux.org/viewtopic.php … #p10554427

I have been using this keyboard with Debian since the 2.6 kernel, with nary a problem in this regard.  It moves windows normally when attached to a Windows system, so the hardware hasn't failed.

I have tried assigning several different keyboard layouts through Xfce's keyboard settings applet, but most of the alternatives work worse than just setting the default.

Suggestions? File a bug report? If so, against what?

Thanks,
Gilbert

secipolla

Member

Registered: 2012-01-15

Posts: 393

Re: Logitech Keyboards and 3.2 kernel

I suppose the bug report should be against the kernel itself as it may be an issue with some driver.

GS

Member

From: place once called Transylvania

Registered: 2010-06-23

Posts: 41

Re: Logitech Keyboards and 3.2 kernel

If no one has other suggestions I guess I'll run reportbug tomorrow and file a bug. It certainly is a weird one, though. I hate making weird bug reports. I like bugs that just make things crash and burn.

;-)

GS

Member

From: place once called Transylvania

Registered: 2010-06-23

Posts: 41

Re: Logitech Keyboards and 3.2 kernel

Okay, this just got a little more interesting. It's not just this keyboard. I tried a couple of other keyboards on this system, and they're all goofy -- including the built-in one.

I fooled myself into thinking the laptop's own keyboard (Lenovo T520i) was working properly, but further testing revealed that it was wonky, also. (Moving windows with the arrow keys sometimes seems to work fine, and then sometimes not.)

I plugged a couple of other keyboards into the AMD64 system, and they're also affected the same way.

In all other respects that I can determine, the arrow keys behave normally. They work perfectly for moving the cursor through text files and spreadsheets and menus. They only behave abnormally when I'm trying to move windows within the DE.

This is beginning to look to me as though its a problem between Xfce and the 3.2 version 64 bit kernel. Or it may be a problem between the kernel and motherboard / chipset of this laptop. But it certainly seems specific to this single feature of the DE.

I'm not quite certain how to go about finding out what to file agains.

secipolla

Member

Registered: 2012-01-15

Posts: 393

Re: Logitech Keyboards and 3.2 kernel

What you could maybe try is when the issue happens, run dmesg and see if there's any related error at the end.

GS

Member

From: place once called Transylvania

Registered: 2010-06-23

Posts: 41

Re: Logitech Keyboards and 3.2 kernel

Only one line concerning keyboard in dmesg:

[    1.112086] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0

All other dmesg output concerns network traffic, USB drives (with occasional errors regarding the mounting thereof), detection of the pointing devices and the following segfaults:

[   23.564714] colord[1687]: segfault at 10 ip 00007f3a0a280230 sp 00007fff02a77c18 error 4
[   23.564721] colord[1690]: segfault at 7ff9 ip 00007f3a0a28a195 sp 00007f39fb568b90 error 4 in libdbus-1.so.3.5.8[7f3a0a261000
...
[   25.679526] colord[1699]: segfault at 71 ip 00007f13a5225e5e sp 00007f1396420bf0 error 4 in libdbus-1.so.3.5.8[7f13a520d000+43000]
[   27.861211] colord[1708]: segfault at be ip 00007f00503b8195 sp 00007f00415b8b90 error 4
[   27.861219] colord[1705]: segfault at 7f0000000001 ip 00007f00503b6f2c sp 00007fff1d5210f8 error 4 in libdbus-1.so.3.5.8[7f005038f000+43000]

The only errors listed in .xsession-errors are:

WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-pTDUdD/pkcs11: No such file or directory

(xfce4-mixer-plugin:3350): libxfce4mixer-CRITICAL **: xfce_mixer_get_track: assertion `GST_IS_MIXER (card)' failed

(xfce4-mixer-plugin:3350): xfce4-mixer-plugin-CRITICAL **: xfce_mixer_plugin_set_card: assertion `GST_IS_MIXER (card)' failed

(xfce4-mixer-plugin:3350): xfce4-mixer-plugin-CRITICAL **: xfce_mixer_plugin_set_track: assertion `GST_IS_MIXER_TRACK (track)' failed
(xfce4-settings-manager:14525): xfce4-settings-manager-DEBUG: geometry = (200,200)
(xfce4-settings-manager:14943): xfce4-settings-manager-DEBUG: geometry = (200,200)
(xfce4-settings-manager:14954): xfce4-settings-manager-DEBUG: geometry = (200,200)
(xfce4-settings-manager:14974): xfce4-settings-manager-DEBUG: geometry = (200,200)

I guess the segfault in libdbus could be an indicator of the culprit. Not sure where to go from here.