After update to karmic ALT-F[1-8] switches to text console

Bug #463762 reported by Dominik Stadler
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Reporting to X-Server as I don't know where else this could be caused.

After upgrading to Karmic I now have the strange behavior that not only ALT-CTRL-F[1-8] switches to the text console from X-Server, but also ALT-F[1-8] does this switching. I don't know where this comes from, but it breaks lots of stuff, i.e. ALT-F4 to close an app, ALT-F2 to open the quick-start-applet, ...

Strange thing is that if I switch back to the X-Server from the text console with ALT-F7, the actual keyboard action is executed in the X-Server, i.e. if I press ALT-F4, the text console is shown, when I switch back, the current application is closed!

Every time I switch (either with ALT-CTRL-F[1-8] or with ALT-F[1-8]), the following is printed to the system log:

Oct 29 21:59:51 dstathink acpid: client 1258[0:0] has disconnected
Oct 29 21:59:51 dstathink acpid: client connected from 1258[0:0]
Oct 29 21:59:51 dstathink anacron[2150]: Anacron 2.3 started on 2009-10-29
Oct 29 21:59:51 dstathink anacron[2150]: Normal exit (0 jobs run)
Oct 29 21:59:51 dstathink kernel: [10749.984755] CPU0 attaching NULL sched-domain.
Oct 29 21:59:51 dstathink kernel: [10749.984760] CPU1 attaching NULL sched-domain.
Oct 29 21:59:51 dstathink kernel: [10750.010232] CPU0 attaching sched-domain:
Oct 29 21:59:51 dstathink kernel: [10750.010240] domain 0: span 0-1 level MC
Oct 29 21:59:51 dstathink kernel: [10750.010246] groups: 0 1
Oct 29 21:59:51 dstathink kernel: [10750.010258] CPU1 attaching sched-domain:
Oct 29 21:59:51 dstathink kernel: [10750.010263] domain 0: span 0-1 level MC
Oct 29 21:59:51 dstathink kernel: [10750.010268] groups: 1 0

$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

ProblemType: Bug
Architecture: amd64
Date: Thu Oct 29 21:56:28 2009
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 205545G
Package: xserver-xorg 1:7.4+3ubuntu7
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=00c3d061-bae6-42a6-a329-deefb7d0d350 ro resume=/dev/sda2 usbcore.autosuspend=1 quiet splash crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
 LANGUAGE=de_AT:de
 PATH=(custom, user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.49+tuxonice1-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati N/A
SourcePackage: xorg
Uname: Linux 2.6.31-15-generic x86_64
dmi.bios.date: 05/15/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET71WW (3.01 )
dmi.board.name: 205545G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6FET71WW(3.01):bd05/15/2009:svnLENOVO:pn205545G:pvrThinkPadT500:rvnLENOVO:rn205545G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 205545G
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-15-generic

Revision history for this message
Dominik Stadler (dominik-stadler) wrote :
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Dominik Stadler (dominik-stadler) wrote :

I saw that restarting fixes this for some time, but it reappears and it "survives" a hibernate/resume.

Logging in/out does not help.

Restarting kdm does help for a while until it reappears.

Cannot yet say for sure if hibernate/resume is related, but might be.

Revision history for this message
Dominik Stadler (dominik-stadler) wrote :

I think it only happens after I hibernate/resume using the default swsusp functionality.

I have a kernel that has both, TuxOnIce and the standard swsusp functionality from the TuxOnIce PPA. If I hibernate/resume using TuxOnIce via the "hibernate" script, it works fine, if I use the standard hibernate-option in the KDE Menu, I have the problem described above after I resume.

Revision history for this message
Dominik Stadler (dominik-stadler) wrote :

I have it reproducible here, anything that I can provide to aid in debugging this? Where would I start?

Revision history for this message
Dominik Stadler (dominik-stadler) wrote :

I did some more investigation, this is what I came up with:

It seems to be depending on the kernel and the type of hibernate/resume that is used.

- For stock kernels from Karmic with swsusp it does NOT happen
- For TuxOnIce-enalbed kernels from the TuxOnIce PPA it HAPPENS
- If I download pre-kernel 2.6.31-16.51~pre2 from the PPA at https://launchpad.net/~stefan-bader-canonical/+archive/karmic, it does NOT happen
- If I patch pre-kernel 2.6.31-16.51~pre2 from the PPA at https://launchpad.net/~stefan-bader-canonical/+archive/karmic with TuxOnIce patches from 20091009, it does NOT happen

so it seems to be introduced in the TuxOnIce sources between the patch-release 20091009 and the version of TuxOnIce used for building the kernel on the TuxOnIce-PPA.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

closing the bug, not caused by stock ubuntu.

Changed in xorg-server (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
st_ (saint-d-a) wrote :

I don't use TuxOnIce, but I observe the same problem. I've attached my bug report by apport-cli. We should reopen the bug.

Revision history for this message
Nigel Cunningham (nigelc) wrote :

st_'s report makes perfect sense to me. TuxOnIce doesn't touch drivers so the issue would have to be caused by differences in the underlying kernel.

Reopening on st_'s behalf.

Changed in xorg-server (Ubuntu):
status: Invalid → Confirmed
Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi Dominik,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 463762

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 463762 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/463762

Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
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 xorg-server (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Dominik Stadler (dominik-stadler) wrote :

For the record, on the tuxonice mailing list, the following possible solution was given, see http://lists.tuxonice.net/pipermail/tuxonice-users/2010-August/000511.html:
" If you are on intel graphic chipset(KMS) and you use pm-utils, I think I
have some clues about the issue.

 If you dig deep into pm-hibernate code, you'll see that the no-chvt quirk is
used in this case. According to my experience this is bad, I think this
switches keyboard into xlate mode (same as you would doing alt-sysrq-R, but
can't be really switched back into normal mode). The only way I discovered to
prevent this is disabling the no-chvt quirk. My ugly hack consists of
commenting a line like this (comment already included):
# add_parameters --quirk-no-chvt
 in the file /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler: 360 (on my
Debian sid). I have pm-utils 1.3.0

 This code is part of the suspend|hibernate case when using_kms."

Revision history for this message
aoandr (t-launchpad-nbs-eng-ru) wrote :

The same bug affected me after upgrade to 10.04 LTS on a Toshiba with Nvidia video card, and also on a fresh install of 10.10 on ThinkPad X200T with Intel Mobile 4 Series Chipset Integrated Graphics Controller. Looks like a long standing and persistent problem in Ubuntu.

Revision history for this message
aoandr (t-launchpad-nbs-eng-ru) wrote :

Related bug: bug 730307
Related bug: bug 520546

This same bug is reported a couple more times. Seems that console-cyrillic is triggering the problem.
Uninstalling the package or disabling Bootsetup in /etc/console-cyrillic fixes the problem, but leaves text console without Cyrillic support. The Cyrillic support can be enabled manually by running /usr/bin/cyr from the console.

Revision history for this message
aoandr (t-launchpad-nbs-eng-ru) wrote :

I've uploaded the patch that fixes the usage of kbd_mode -u in console-cyrillic, see bug 520546
Hopefully the patch fixes the bug.

However, there seems not much sense in installing console-cyrillic in the first place. Most of its functionality is available from console-setup package, which is installed as part of even minimal Ubuntu system. Just run dpkg-reconfigure console-setup and select your keyboard, language, encoding, etc.

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.