Using text console disables AltGr under X

Bug #337069 reported by Torsten Bronger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

If I use a text console and log out there, and then I switch back to X with Alt-Ctrl-F7, the AltGr button has no effect anymore. I have to log out and re-login in order to revert this effect.

I have disabled my ~/.Xmodmap but the problem persists.

I run Ubuntu 8.10, with German keybord layout and "eliminated dead keys".

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation C51 Host Bridge [10de:02f1] (rev a2)
     Subsystem: Giga-byte Technology Device [1458:5000]
00:05.0 VGA compatible controller [0300]: nVidia Corporation C51G [GeForce 6100] [10de:0242] (rev a2)
     Subsystem: Giga-byte Technology Device [1458:d000]

Revision history for this message
Bryce Harrington (bryce) wrote :

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Torsten Bronger (bronger) wrote :

I didn't touch </etc/X11/xorg.conf>.

bronger@wilson:~$ tail -f /var/log/Xorg.0.log
(II) Logitech USB Receiver: Found x and y relative axes
(II) Logitech USB Receiver: Found 16 mouse buttons
(II) Logitech USB Receiver: Configuring as mouse
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE)
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
AUDIT: Tue Mar 3 05:11:18 2009: 9874 X: client 4 rejected from local host ( uid=0 gid=0 pid=9893 )
AUDIT: Tue Mar 3 05:11:23 2009: 9874 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=9897 )
AUDIT: Tue Mar 3 05:11:23 2009: 9874 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=9898 )
AUDIT: Tue Mar 3 05:11:23 2009: 9874 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=9899 )
(II) Open ACPI successful (/var/run/acpid.socket)
(II) NVIDIA(0): Setting mode "1280x1024"
(II) Configured Mouse: ps2EnableDataReporting: succeeded
(II) Macintosh mouse button emulation: Device reopened after 10 attempts.
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) AT Translated Set 2 keyboard: Device reopened after 10 attempts.
(II) Logitech USB Receiver: Device reopened after 10 attempts.
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) Logitech USB Receiver: Device reopened after 10 attempts.
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200

Revision history for this message
Bryce Harrington (bryce) wrote :

You didn't attach the Xorg.0.log.

Anyway, without more data I'm afraid we have to just assume this is yet another proprietary driver bug. Refiling.

Revision history for this message
Torsten Bronger (bronger) wrote :

You mean you need the complete Xorg.0.log? Well, I attach it, but this time without having replayed the bug. So this and the snippet above should be the full story.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

In Jaunty (9.04), we have just updated to the latest
nvidia-graphics-drivers-180 package from nVidia, version 180.44.

This package provides fixes for a large number of bugs, and we need your
assistance in testing if it fixes the issue you reported.

To do this, please do the following:

 a. Update to the 180.44 version of -nvidia using your favorite update
     method

 b. Attempt to reproduce your bug

 c. If your bug still remains, please simply reply to this email
     indicating so.

 d. If your bug is now solved, you can help us by setting your bug
     report to Fix Released:
     * In launchpad, go to your bug report
     * Click on the downward pointing arrow under Status
     * Set the Status field to 'Fix Released'
     * Comment on the change, such as, 'Verified fixed in 180.44'
     * Click 'Save Changes'

 e. If the original problem is solved but there are now other problems,
     please close the original bug and open new ones for those issues.

Thank you!

For details on the changes in this version of -nvidia, please see:

   http://www.nvidia.com/object/linux_display_ia32_180.44.html

Bryce Harrington (bryce)
Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Confirmed
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Confirmed → New
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Invalid
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.