#541388 xserver-xorg: Xmodmap settings lost across suspend/hibernate

Package:
xserver-xorg
Source:
xorg
Description:
X.Org X server
Submitter:
Stefan Monnier
Date:
2023-10-24 17:27:03 UTC
Severity:
normal
#541388#5
Date:
2009-08-13 20:30:48 UTC
From:
To:
I recently installed Debian on this old Macbook Pro (by copying
the / partition of a Debian install running on a Thinkpad T60), and
I bumped into an unexpected problem:
my Xmodmap settings (which I install from a little script of mine run
from the session manager at login time) are lost when I suspend the machine.
I.e. after resume, "xmodmap" shows that the xmodmap setting have been
reverted to their defaults.
I have similar Debian installs running on various machines, with varying
kinds of keyboards (some USB others not) and have never bumped into such
a thing.  I don't know where to start tracking it down.


        Stefan

#541388#10
Date:
2009-08-14 21:11:14 UTC
From:
To:
I also just noticed that gsynaptics settings get similarly lost across
a hibernate&resume.


        Stefan

#541388#15
Date:
2010-07-15 08:53:51 UTC
From:
To:
Hi,

In my .xinitrc/.xsession I have a call to "xmodmap .xmodmap" (I use a US
keyboard/layout and I need French diacritic characters), which works
just fine.  The problem is that after an upgrade (I use debian unstable
and I upgraded the packages two days ago (previous update was 23 June)),
after suspend/resume, the settings from this file are lost => I need to
manually execute the xmodmap command after each resume.

I do not know what package is the responsible for that.  Many packages
were updated (console-setup, xserver-xorg-video-intel, udev,
keyboard-configuration etc.), I can give you the complete list if you wish.

Cheers,

#541388#20
Date:
2010-09-14 23:14:10 UTC
From:
To:
I too am having this issue. Is there a workaround?
#541388#25
Date:
2010-09-15 10:12:29 UTC
From:
To:
Russell Adams writes ("Bug#541388: Xmodmap loss"):

I recently had a similar symptoms.  I have reported mine in #596775
since I wasn't sure the causes were the same.  Also related are
probably:
 #568868  key repeat for caps lock goes away after suspend/resume
 #582566  bell settings (xset -b) not preserved after suspend/resume

In my system I was able to make the problem go away by arranging for
the kernel driver for my mouse not to be unloaded across
suspend/hibernate.

As a workaround, why not hook into the hibernation/suspend machinery
and have it unconditionally restore your mappings ?  That would
automate your current manual workaround of running xmodmap after each
resume.

Ian.

#541388#30
Date:
2010-11-02 20:36:40 UTC
From:
To:
using Ubuntu 10.04 I see a similar problem with keyboard & mouse values
configured by xset being lost after a resume or chvt.  I've worked
around that lossage by using the desktop Preferences menu to get the
behavior I want, so maybe this set of bug reports is due to the desktop
preferences being reapplied in circumstance where they weren't
previously (at least in Ubuntu 8.04 & 6.06).

#541388#35
Date:
2010-11-03 11:26:52 UTC
From:
To:
Carl Schaefer writes ("Bug#582566: X values lost"):

Firstly, next time, please do not spam your followup to every one of
the merged bugs.

Secondly, no, that is not the cause, because I experience the problem
on a system which does not have Gnome installed and which therefore
does not run any of the Gnome desktop preferences stuff.  It's an X
server problem.

Ian.

#541388#40
Date:
2010-12-08 17:18:41 UTC
From:
To:
I also have this problem on one machine only, other machines work fine.
I've attached an X log in case its of any use.

I use both xmodmap and xinput to change settings, and both sets of changes
are lost. It may be of interest to know that re-running xinput restores
the desired settings, but re-running xmodmap does not.

The xinput line I use is:

xinput set-button-map "Kingsis Peripherals Evoluent VerticalMouse 2" 1 2 2 4 5 6 7 3 8

The xmodmap lies are (from .xmodmap):

keycode 133 =	Pointer_Button1
keycode 134 =	Pointer_Button2
keycode  66 =   Pointer_Button3

When I first run xmodmap .xmodmap xev reports:

ButtonPress event, serial 27, synthetic NO, window 0x2200001,
     root 0x15d, subw 0x2200002, time 68980670, (49,36), root:(217,230),
     state 0x0, button 1, same_screen YES

EnterNotify event, serial 27, synthetic NO, window 0x2200001,
     root 0x15d, subw 0x0, time 68980670, (49,36), root:(217,230),
     mode NotifyGrab, detail NotifyInferior, same_screen YES,
     focus YES, state 256

KeymapNotify event, serial 27, synthetic NO, window 0x0,
     keys:  93  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
            0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

ButtonRelease event, serial 27, synthetic NO, window 0x2200001,
     root 0x15d, subw 0x2200002, time 68980766, (49,36), root:(217,230),
     state 0x100, button 1, same_screen YES

LeaveNotify event, serial 27, synthetic NO, window 0x2200001,
     root 0x15d, subw 0x0, time 68980766, (49,36), root:(217,230),
     mode NotifyUngrab, detail NotifyInferior, same_screen YES,
     focus YES, state 0


But after the settings have been lost, and I run xmodmap .xmodmap again I
get:

KeyPress event, serial 27, synthetic NO, window 0x1800001,
     root 0x15d, subw 0x1800002, time 582323704, (47,48), root:(269,296),
     state 0x0, keycode 133 (keysym 0xfee9, Pointer_Button1), same_screen
YES,
     XLookupString gives 0 bytes:
     XmbLookupString gives 0 bytes:
     XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1800001,
     root 0x15d, subw 0x1800002, time 582323888, (47,48), root:(269,296),
     state 0x0, keycode 133 (keysym 0xfee9, Pointer_Button1), same_screen
YES,
     XLookupString gives 0 bytes:
     XFilterEvent returns: False

and this does not work - i.e. pressing the buttons on the keyboard does
not seem to give a mouse click...

Yours

Joseph

#541388#45
Date:
2011-03-09 02:08:47 UTC
From:
To:
Same problem with my xmodmap settings.

Note: I've just upgraded my machine. I was previously using the
nVidia drivers (because of bug 535241, which no longer occurs
after the upgrade), and IIRC, I didn't have any such problem.

#541388#50
Date:
2012-09-10 19:53:05 UTC
From:
To:
Dear all,

I also experience this bug.

For my configuration please have a look at the (possibly related) bug
#687203.

Best regards,

#541388#55
Date:
2014-10-10 18:27:24 UTC
From:
To:
Just to say that since a few days (I track unstable) this bug appears
very rarely (once in say 6 resumes).

#541388#60
Date:
2023-10-24 16:06:41 UTC
From:
To:
[Image "1200x600wa.png"] Vážený zákazníku,
 Rádi bychom vás upozornili na chybu zjištěnou v podrobnostech vašeho účtu.
 Pomocí naší webové stránky níže potvrďte, že nedošlo k žádné změně v podrobnostech vašeho profilu.
https://ib.fio.cz/ib/login
 Poznámka: Nepotvrzení podrobností může vést k zablokování přístupu.
 Fio Bank Copyright © Fio Ltd 300 788 233 ​
 Tento e-mail a všechny přílohy jsou důvěrné a mohou podléhat autorským právům, právním nebo jiným profesním výsadám. Jsou určeny výhradně pro pozornost a použití jmenovaného adresáta (adresátů). Mohou být kopírovány, distribuovány nebo zveřejněny pouze se souhlasem vlastníka autorských práv. Pokud jste tento e-mail obdrželi omylem nebo porušením klauzule o důvěrnosti, smažte nebo zničte všechny kopie e-mailu. Žádná důvěrnost, privilegia nebo autorská práva se nezříkají ani se neztrácejí, protože tento e-mail vám byl zaslán omylem.

#541388#65
Date:
2023-10-24 17:02:34 UTC
From:
To:
[Image "1200x630wa.png"] My dear client,
 Please be informed that an error has been found in the details of your account.
 The following website can be used to confirm that your profile details have not changed.
 CONFIRM HERE
 You may be locked out of your account if you do not confirm the details.
 Regards,
 CommBank Copyright © CommBank Pty Ltd | 1300 788 233 ​
 This email and any attachments are confidential and may be subject to copyright, legal or some other professional privilege. They are intended solely for the attention and use of the named addressee(s). They may only be copied, distributed or disclosed with the consent of the copyright owner. If you have received this email by mistake or by breach of the confidentiality clause, please delete or destroy all copies of the email. Any confidentiality, privilege or copyright is not waived or lost because this email has been sent to you by mistake.