** Changed in: gentoo
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/255008
Title:
Up arrow key mapped to Print [screen]
--
desktop-bugs mailing list
desktop-bugs
** Changed in: gentoo
Status: Fix Released => Won't Fix
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@l
** Changed in: gnome-settings-daemon
Importance: Unknown => Medium
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
I realized I had made a mistake, Intrepid Ibex 8.10 "will reach" EOL on
30 "APRIL" 2010.
Sorry for this.
Anyway, I think that one month doesn't make any difference now.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: xorg-server (Ubuntu
I think it is a good idea to make a decision how to handle this for
lucid release.
Every LTS upgrader with a customized keyboardmapping will run in big
trouble - every!
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you
I've marked Bug #512622, filed myself, as duplcate of this bug. It is
describing the "wiredness" mentioned in Bug #254939 which I also marked
as duplcate. I'm aware it does so in a confusing manner.
Lucid Lynx is also affected.
In the essence my search which also led me here, ends up to following
** Branch linked: lp:ubuntu/gnome-settings-daemon
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.c
** Tags added: iso-testing
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu
As a work around I could fix remaining issues by "deleting" any xmodmap-
related file of the affected users and changing keyboard layout again. I
still consider it a bug when an dist-upgrade breaks prior keyboard
configuration. It may be of minor importance though ...
--
Up arrow key mapped to Pr
I made and upgrade from ubuntu 8.04 to ubuntu 8.10 and experienced this very
same problem. What ever has been done to fix the issue does only work for new
installations and new users. The issue even persists when upgrading further to
9.04.
Proposed work arounds do not entirely fix the issue in a
Problem still present when upgrading from 8.04 to 8.10 and even persists when
upgrading further to 9.04.
It only affects existing users. When I create a new user, the keyboard is
working as expected. However none of the above workarounds does fix all the
issues for my existing user.
Best I can a
** Changed in: gentoo
Status: Invalid => Fix Released
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lis
To fix this bug, on the server type:
apt-get install xkb-data
then type:
setxkbmap
(or restart nx)
The file /usr/share/X11/xkb/rules/xorg is the file that was needed.
This could be fixed with a dependency in one of the nx packages.
As of now, the problem still occurs with the latest nx p
sorry I didn't realise this bug report was not specifically about nx.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
** Changed in: gentoo
Status: Confirmed => Invalid
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.
I have the same problem with the arrow keys, but I'm trying to connect
through an Ubuntu 8.10 server with freenx
0.7.3+svn612-0freenxteam11~intrepid1 to windows machines (vm's and real
machines). I use the NX Java applet, but also when I try to connect from
my Ubuntu 8.10 machine it won't work.
I
I no long have this problem. I did try to do anything to fix it, and I
did not notice any updates that would have fixed this bug for me.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop B
Up (by itself) is still maps to PrintScreen fr me, but I realized today
that both Ctrl-Up and Shift-Up work correctly (if that matters).
I have never consciously used Ctrl-Up before (normally Ctrl-Left and
-Right jump the cursor over text), but it appears to be a workaround, at
least in the contex
I am not in any remote session. I would be surprised if it were a
different bug, but I do not know enough to make a stronger claim.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@Bender2k14
Is this with an nx session? If so then this may help, if not I think its a
different bug from what I have been seeing.
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/289918/comments/26
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You recei
@mabawsa
I have the "us" layout and those two commands do not fix the problem for
me. Also, there was no "metacity" running before executing the second
command.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a m
Did you try
killall metacity
?
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.
Yes, I have it, too, I still have to run "setxkbmap -model evdev -layout
de" after login.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
This bug says that a fix is released (several times), but I still have
this problem and have all updates installed.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug as
These commands fix the keyboard mapping for me. Please swap the -layout
for your keyboard.
setxkbmap -model evdev -layout us
killall metacity
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desk
I also found that it helps to move up to most recent nx, if using the
nomachine version. It seems that some keyboard mapping issues were
fixed in recent updates.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a m
Not fixed for me! If I connect from an intrepid client to a dapper
nxserver, I get this problem. The printscreen key sends delete, arrow up
sends print screen... How can I fix this?
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification
Weeks ago I ran into the same problem after starting to use Ubuntu Intrepid on
my desktop.
I was using a FreeNX-server on CentOS 5.x, but by coincidence I was also
testing a FreeNX-server with Ubuntu Intrepid.
In the Ubuntu FreeNX-server desktop I could change the keyboard to evdev, and
on my ow
There's a report on this issue over on NoMachine's site:
http://www.nomachine.com/tr/view.php?id=TR11F02131
For me, this workaround is acceptable (it also disables evdev):
Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection
However, that report also incorrectly states that this
I have a japanese keyboard, panasonic Y5 laptop. The PgDown key doesn't
work. Up-to-date intrepid packages.
* setting the keyboard model to evdev in the gnome configuration tool doesn't
fix it.
* `sudo setxkbmap -model evdev -layout jp -variant 106` fixes the issue, but I
guess I will have to do
Hi. I tried everything listed in the comments before but I'm still unable to
use some keys. Arrow down and Page UP
won't work. Thou arrow up and page down do.
I tried different things in xorg.conf: no keyboard entry, keyboad evdev and
keyboard as it was with hardy. I didn't see a
different behav
I'm curious about something before I start playing with my xorg.conf...
my keyboard driver was "keyboard". What is the difference between it and
"evdev" and "kbd"? What is the default in intrepid?
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bu
Forget what i mention before , doesn't work instead of that just put :
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "CoreKeyboard"
EndSection
it will do the trick , anyway intrepid seems to be affected by a serious bug
related to default keyboard driver...
--
U
modifying my xorg.conf with my old informations from hardy solve the
problem :
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
I solved the problem changing my keyboard to Edev, but still reproducing
this bug after some reboot. I really don't know why.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
Actually I found the responsible key, at least in my case. It's the
Compiz plugin ezoom (Enhanced Desktop Zoom) which I actually don't use
anymore. I removed the key with gconftool-2 and almost everything works
fine. (Well would be nice to have the menu key as compose, but I guess
that's just some
Well, thanks Muelli, mv'ing .gconf helps me as well, but having to
reconfigure everything is quite annoying. It would be great to find the
responsible key...
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member
Since I removed the keyboard config from my xorg.conf (to let X.Org
decide automatically with HAL), I have to do "setxkbmap -model evdev
-layout de -variant nodeadkeys" after every login :(
@PeteJ: For NX-Related problems, I found Bug #289918 (which affects me,
too)
--
Up arrow key mapped to Pri
I had a gutsy thinkpad t21 laptop nx client connecting to a gutsy plain
wrap freenx server working fine. Upgraded to Intrepid this morning and
got the broken nav key problem in the nx session (up arrow opened Take
screenshot and the other nav keys were borken too).
After reading tons, having no c
** Changed in: gentoo
Status: Unknown => Confirmed
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.
** Bug watch added: Gentoo Bugzilla #239092
http://bugs.gentoo.org/show_bug.cgi?id=239092
** Also affects: gentoo via
http://bugs.gentoo.org/show_bug.cgi?id=239092
Importance: Unknown
Status: Unknown
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
Judging by the remapping this appears to be the same issue that affects
NX-sessions.
https://bugs.launchpad.net/ubuntu/+bug/289918
The difference here is that the keyboard works as expected with no ill
effects *locally*, but broken when in an NX-session. I cannot find any
.Xmodmap-files anywhere
This bug also affected my keyboard, but the only key that didn't work was LEFT
ARROW (mapped to no action).
Changing the keyboard model to Evdev fixed this.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member
Got a solution.
First manually delete your old .Xmodmap Files in your Home-Directory.
then do a
sudo dpkg-reconfigure console-setup
to reconfigure your Keyboard.
After this perform
gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard
and reboot.
So I hope you have no problems f
Hi!
This solution doesn't work for me.
After using the command and logging in.
The System is asking me for a Xmodmap.
Also the evdev solution is not working for me.
Is there a fix or something else to do?
thx
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
Yo
Thanks Muelli,
That fixed the problem for me. Though the correct command is
gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard
cheers
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ub
Hey,
On 23.10.2008 13:24, midnightflash wrote:
> For me the solution was:
>
> $ rm .gconf/desktop/gnome/peripherals/keyboard/
>
Congrats :)
But please consider using
gcontool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/
instead of removing the directory because gconf is a cachi
For me the solution was:
$ rm .gconf/desktop/gnome/peripherals/keyboard/
and relogin.
After this it's running as expected.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
Same problem here, since the today update.
Italian keyboard on Dell XPS M1330
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Starting with a new user did the trick, no problem with the up arrow
anymore...
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing li
Have exactly the same problem on my laptop. Upgraded yesterday from
Hardy to Intrepid.
[EMAIL PROTECTED]:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
None of these fixes worked for me on Intrepid beta. I tried both Dell
wired USB and Kensington MAC KBD.
Here are relevant inputs: setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ incl
I am on a thinkpad t61 with swiss keyboard layout.
Until yesterday i still had this bug, all the mentioned workarounds
and/or updates didn't solved my problem (Actually i had this bug at the
beginning, then it was solved (by changing xorg.conf if I remember
correctly) and came up again a few weeks
On 24.09.2008 20:31, Bryce Harrington wrote:
> Re-closing. Muelli, you seem to have a different problem than everyone
> else, please file a new bug.
The issue still persists. But if I start with a newly created user, it
works. When copying the .gconf/ folder over to the old account, the
up-key wor
in kde, "Evdev-managed Keyboard" has to be selected as keyboard type if
the keyboard-layout-manager is activated, which overwrites the xorg/xkb-
settings. This works fine in my case (Cherry G230). I chose "de-
nodeadkeys" as layout.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.
should have read the all the comments!
fixed by running 'setxkbmap -model evdev -layout us' on the machine
running hardy.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
>I use the free version of NoMachine NX (www.nomachine.com) to connect from my
>home PC (current Intrepid, the one
>that had this bug a few weeks ago) to a PC at my university (current hardy).
>Inside the NX window, the keyboard exhibits
>the same behaviour as described here.
I'm having the ex
Which package is the fix supposed to be released with?
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
Re-closing. Muelli, you seem to have a different problem than everyone
else, please file a new bug. You can try doing so via running `ubuntu-
bug xserver-xorg-input-evdev`, which should attach the necessary files
for troubleshooting.
--
Up arrow key mapped to Print [screen]
https://bugs.launchp
Closing again. Muelli, check your configuration. if you can reproduce
this with a new user, open a new bug. Thanks.
** Changed in: xorg-server (Ubuntu Intrepid)
Status: New => Fix Released
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bu
With blacklist evdev sinaptic touchpad doesn't work. So still need a
fix.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
des
Another workaround that just worked for me: add
blacklist evdev
to /etc/modprobe.d/blacklist then run /sbin/update-modules as root, and
reboot. The behavior of the keyboard and mouse is thereafter reverted
to what it was under Hardy Heron, no xorg.conf changes or setxkbmap
voodoo needed.
--
Up
I just discovered: while "setxkbmap -model evdev" does not help,
"setxkbmap -model evdev -layout de" does!
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Hmm, I thought I got rid of this bug, but now it came back, in a more
complex scenario:
I use the free version of NoMachine NX (www.nomachine.com) to connect
from my home PC (current Intrepid, the one that had this bug a few weeks
ago) to a PC at my university (current hardy). Inside the NX window
I just got this bug ... arrow keys fail along with the cluster of keys
around insert, pagedown. PgUp gives me a "/", but / works as normal. I
use a GB keyboard map.
I've just run some updates from Hardy to Intrepid but I can't narrow
down what is at fault. Also I'm getting wrong keymapping in some
On 17.09.2008 21:07 Jan Rathmann wrote:
> Can't reproduce this anymore on my system with current daily live, so
> I'm setting it to fix released.
>
You better revert that since am still affected.
[EMAIL PROTECTED]:~$ apt-cache policy xserver-xorg xserver-xorg-input-evdev
xserver-xorg:
Installe
Reverting the "fix released" status to something more accurate
** Changed in: xorg-server (Ubuntu Intrepid)
Status: Fix Released => New
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Des
Can't reproduce this anymore on my system with current daily live, so
I'm setting it to fix released.
Kind regards,
Jan
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Incomplete => Fix Released
** Changed in: xorg-server (Ubuntu Intrepid)
Status: Incomplete => Fix R
** Changed in: xorg-server (Ubuntu Intrepid)
Status: Fix Released => Incomplete
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Fix Released => Incomplete
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notificati
@Matt
It was on real hardware, so there still seems to be an issue.
Kind regards,
Jan
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mai
In fact, this only happens to me when I forget the -k switch to kvm.
Sorry about the noise, I think the original issue remains fixed, and kvm
is just broken.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Triaged => Fix Released
--
Up arrow key mapped to Print [screen]
htt
My test was in KVM. Jan, were you testing on real hardware or in a VM?
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskt
Scratch that, I've just confirmed the bug in a fresh installation using
intrepid-desktop-i386 20080903. This seems to have regressed.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Fix Released => Triaged
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Target
It's working fine here, and this bug report is already very long and
confused, so I think it would be better to take your issue to bug
257855. I've unmarked it as a duplicate as your issue may be slightly
different.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Status: Confirmed =
I am setting the status to Confirmed again, since I still experienced
the bug in daily-live image 20080903 (amd64) (The behaviour is still the
same like in description of my first report:
https://bugs.launchpad.net/ubuntu/+bug/257855 ).
Kind regards,
Jan
** Changed in: gnome-settings-daemon (Ubun
actually, the evdev change broke ABNT2 and jp106 cases partially, and
the most sane way to fix it was to force the rules (not model) to be
evdev when evdev driver is used. This has been changed in xkeyboard-
config upstream, and it also means that there is no need for gnome-
settings-daemon (or KDE
** Changed in: gnome-settings-daemon
Status: Confirmed => Won't Fix
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
de
On Sat, Aug 16, 2008 at 06:45:25PM -, Luka Renko wrote:
> Still a problem here: Kubuntu Intrepid, up-to-date as of today.
> Workaround with "setxkbmap -model evdev -layout us" helps.
Not surprising, since the fix was in a GNOME component. Probably KDE needs
to do the same, but I don't know wh
Still a problem here: Kubuntu Intrepid, up-to-date as of today.
Workaround with "setxkbmap -model evdev -layout us" helps.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
On Sat, Aug 16, 2008 at 08:20:14AM -, Paul Weiss wrote:
> This bug doesn't exist for me in Alpha 4 anymore...
Working fine for me as well now, on both affected systems. Thanks, all.
--
- mdz
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this
This bug doesn't exist for me in Alpha 4 anymore...
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
Thanks for the reply.
I think it is the same basic issue as in bug #255372 (both japanese and
brazilian keyboards are special cases that used to work before whatever
caused bug #255008), I added the same information there.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/
Iñaki: that's a problem in the layout, please file a bug against
xkeyboard-config.
TomasR: those settings have no meaning when using evdev, so it was
likely the updates that fixed it for you.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug no
I have a japanese keyboard (pc106) and some keys still do not work after
upgrading to gnome-settings-daemon (2.23.6-0ubuntu2), although the Up ->
PrtScr problem is indeed fixed (I am using evdev managed keyboard, as
recommended).
The symbols that do not work and used to work before are ']' and '}'
I've found a solution!
I commented out all xkb-options in xorg.conf.
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
** Changed in: gnome-settings-daemon
Status: Unknown => Confirmed
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desk
This bug was fixed in the package gnome-settings-daemon -
2.23.6-0ubuntu2
---
gnome-settings-daemon (2.23.6-0ubuntu2) intrepid; urgency=low
* debian/patches/80_evdev_no_model.patch:
- don't set a keyboard model when evdev is being used (lp: #255008)
-- Sebastien Bacher <[EMAIL
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
** Bug watch added: GNOME Bug Tracker #547684
http://bugzilla.gnome.org/show_bug.cgi?id=547684
** Also affects: gnome-settings-daemon via
http://bugzilla.gnome.org/show_b
Seb found a patch in Fedora against gnome-settings-daemon, that'll
ignore the model if we are using evdev. This is much easier than the
suggested libxklavier change, so it'll get in alpha4.
** Changed in: gnome-settings-daemon (Ubuntu Intrepid)
Sourcepackagename: libxklavier => gnome-settings-daem
Marking again as fixed for xorg-server, since it already has the
necessary patches for the layout stuff.
** Changed in: xorg-server (Ubuntu Intrepid)
Status: Triaged => Fix Released
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notif
91 matches
Mail list logo
