[Bug 1225393] Re: Phone does not reliably switch to cellular data
I have a similar bug to this although does not involve WiFi. If i am driving/travelling through an area that does not have reception from my mobile network. 3G/data does not come back when the phone has reception again. I can text and make calls but cannot use data. I have to power my N4 off and back on again to resolve this. Toggling the Data switch in the cellular settings does nothing. I would love to file a bug for this but wouldn't have a clue where to do so... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1225393 Title: Phone does not reliably switch to cellular data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1225393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899986] [NEW] Ubuntu 12.04 Installer Crashes
Public bug reported: Install 3rd Party Option Selected Install updated packages selected ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.9.5 ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3 Uname: Linux 3.2.0-2-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CasperVersion: 1.292 Date: Sun Dec 4 17:38:30 2011 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2029.1) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) LANG=en_GB.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ubiquity-2.9.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899986 Title: Ubuntu 12.04 Installer Crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/899986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899986] Re: Ubuntu 12.04 Installer Crashes
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899986 Title: Ubuntu 12.04 Installer Crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/899986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664645] Re: package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for the superb effort and turn around time. This is definately fixed and is working 100% for me. Thank you again!! -- package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/664645 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664654] [NEW] package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Binary package hint: alsa-utils ldconfig deferred processing now taking place Errors were encountered while processing: alsa-utils E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up alsa-utils (1.0.23-2ubuntu3.3) ... dpkg: error processing alsa-utils (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: alsa-utils ProblemType: Package DistroRelease: Ubuntu 10.10 Package: alsa-utils 1.0.23-2ubuntu3.3 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Oct 21 19:21:24 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: alsa-utils Title: package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package maverick -- package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/664654 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664654] Re: package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- package alsa-utils 1.0.23-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/664654 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 647742] [NEW] WARNING: at /build/buildd/linux-2.6.35/net/mac80211/scan.c:265 ieee80211_scan_completed 0x1c7/0x1e0 [mac80211]()
Public bug reported: Description:Ubuntu maverick (development branch) Release:10.10 ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-22-generic 2.6.35-22.33 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kalle 1613 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd250 irq 47' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,10250090,0012 HDA:14f12bfa,1025007f,0009' Controls : 24 Simple ctrls : 14 Date: Thu Sep 23 21:50:11 2010 Failure: oops Frequency: This has only happened once. HibernationDevice: RESUME=UUID=acc56a6f-6367-4c84-b913-7cbcca0e6fb8 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MachineType: Acer Aspire 5680 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=2b83eedd-3fb3-4cbe-87ab-003526a09ed3 ro quiet splash RelatedPackageVersions: linux-firmware 1.38 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: WARNING: at /build/buildd/linux-2.6.35/net/mac80211/scan.c:265 ieee80211_scan_completed+0x1c7/0x1e0 [mac80211]() dmi.bios.date: 11/15/2006 dmi.bios.vendor: Acer dmi.bios.version: V3.10 dmi.board.name: Grapevine dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.10:bd11/15/2006:svnAcer:pnAspire5680:pvrV3.10:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5680 dmi.product.version: V3.10 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops maverick needs-upstream-testing regression-potential -- WARNING: at /build/buildd/linux-2.6.35/net/mac80211/scan.c:265 ieee80211_scan_completed 0x1c7/0x1e0 [mac80211]() https://bugs.launchpad.net/bugs/647742 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 647742] Re: WARNING: at /build/buildd/linux-2.6.35/net/mac80211/scan.c:265 ieee80211_scan_completed 0x1c7/0x1e0 [mac80211]()
** Attachment added: logs.tar.gz https://bugs.launchpad.net/bugs/647742/+attachment/1636351/+files/logs.tar.gz ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636352/+files/AcpiTables.txt ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636353/+files/AlsaDevices.txt ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636354/+files/AplayDevices.txt ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636355/+files/ArecordDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636356/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636357/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636358/+files/Card0.Codecs.codec.0.txt ** Attachment added: Card0.Codecs.codec.1.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636359/+files/Card0.Codecs.codec.1.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636360/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636361/+files/Dependencies.txt ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636362/+files/IwConfig.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636363/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636364/+files/Lsusb.txt ** Attachment added: OopsText.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636365/+files/OopsText.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636366/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636367/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636368/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636369/+files/ProcModules.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636370/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636371/+files/UdevLog.txt ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/647742/+attachment/1636372/+files/WifiSyslog.txt -- WARNING: at /build/buildd/linux-2.6.35/net/mac80211/scan.c:265 ieee80211_scan_completed 0x1c7/0x1e0 [mac80211]() https://bugs.launchpad.net/bugs/647742 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563018] Re: main.py crashed with SIGSEGV
*** This bug is a duplicate of bug 560562 *** https://bugs.launchpad.net/bugs/560562 Can't even confirm if this is a duplicated or not as we do not have permission to view #560562 which is probably why it was reported again. #560562 doesn't show up anywhere. -- main.py crashed with SIGSEGV https://bugs.launchpad.net/bugs/563018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken due to invalid SKIP keyboard model
Hi Joshua, Thanks for getting back to us. I just wanted to respond and clarify i don't think this affects Karmic. The only mention of Karmic was myself, having installed an instance of the guest running under Karmic for testing to eliminate whether it was an OS specific issue with respect to the host. This problem only seems to exist with Lucid running as a guest within any given OS host, be it OS X, Windows or Linux. I hope this helps clarify any ambiguity regarding where the problem lies. -- keyboard input broken due to invalid SKIP keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken due to invalid SKIP keyboard model
I think the simplest way to do the sanity check, would be to do it as part of the clean-up process when a console-setup reconfigure is triggered. -- keyboard input broken due to invalid SKIP keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
After a little more research and VM building, this is what i find. I can reproduce this problem with Ubuntu as guest on the following operating systems. Ubuntu Karmic 64-bit Mac OSX Snow Leopard Windows XP Windows 7 VMWare ESXi 4.0 For the most part, the problem is identical. Everything works with Lucid Beta 1 as the guest, up until applying updates after that i can no longer log in with the same symptoms as previously reported on all of them, with the exception of Karmic. Karmic does not work from the get go, if i do a basic install of Lucid running on a Karmic host, the keyboard works but is mapped to the wrong keys and i have to use the onscreen keyboard to login. No matter what option i choose in under keyboard preferences after loggin in i cannot get the keyboard to map properly. After applying the updates to Lucid on the Karmic host it then mirrors the problems experienced with all the other hosts. The keyboard flat out does not work anymore. Now the one thing i have noticed is that Lucid does not seem to pickup its keyboard mappings correctly for any of my hosts, when i say that, i mean it defaults to USA/USA as language and keyboard layout even though i have set it to use UK/UK as the language and keyboard layout. I am assuming the reason some of us can work and some can't is because those that can are using a USA/USA layout. Again, i am happy to test anything on any of the VM's i have should anyone wish to get to the bottom of this problem. I am not sure the onscreen keyboard problem is necessarily exactly the bug listed above, as that was submitted in Feb and even though nothing has been resolved with it, Beta 1 shipped after that and the onscreen keyboard works in that release. Subsequent updates seem to have broken that again so i am sure its just a variation of it. I have experience exactly that bug but on a physical machine running Lucid and not in a VM. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
This is definitely a problem with the guest not detecting the keyboard mappings or saving them. For some reason it insists on using American layout settings even if i log in an apply them system wide. The only way i can use my machine at this point in time is to set it to AutoLogin and then i am fine but everytime i log in the first thing i have to do is change the keyboard layout. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, macbook79, gb,us, mac,, grep ^X /etc/default/console-setup XKBMODEL=macbook79 XKBLAYOUT=gb XKBVARIANT=mac XKBOPTIONS= udevadm info --export-db|grep LAYOUT|sort -u E: XKBLAYOUT=gb -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
The previous post was for a working machine with no updates installed. With updates installed and no longer working, the above becomes: xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, SKIP, gb,us, mac,, grep ^X /etc/default/console-setup XKBMODEL=SKIP XKBLAYOUT=us XKBVARIANT=U.S. English XKBOPTIONS= udevadm info --export-db|grep LAYOUT|sort -u E: XKBLAYOUT=us -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken due to invalid SKIP keyboard model
Martin, that is exactly the command i was looking for. I have just run it and everything seems to be working as expected. grep ^X /etc/default/console-setup XKBMODEL=macbook79 XKBLAYOUT=gb XKBVARIANT=mac XKBOPTIONS= Interestingly it has allowed me to drop the USA keyboard layout in GDM now too, which i could not previously do. It would just come back after the next reboot. xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, macbook79, gb, mac,, Thank you to both Martin and Matt for resolving this issue! If there is any further feedback you require would be more than happy to assist. -- keyboard input broken due to invalid SKIP keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken due to invalid SKIP keyboard model
oh, almost forgot to paste this. ;-) output of udevadm info --export-db|grep MODEL|sort -u http://pastebin.ubuntu.com/409642/ -- keyboard input broken due to invalid SKIP keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken due to invalid SKIP keyboard model
Hi Martin, I think you are right in that the problem with the SKIP option appearing is as a result of something that is happening in the install process. I think it is most likely something to do with the way that VMWare answers, or doesn't, the questions presented to it in the automated easy install option. I think this is the case because i have installed Lucid Beta 1 on physical machines from the same install ISO and not had the problem with the keyboard being set to SKIP. This may just be a case of VM needing to update their unattended install script, or possibly the Ubuntu post install checking to make sure the keyboard is not set to SKIP and if it is, prompting the user to specify a keyboard. I have checked again and its definitely set to SKIP after a default install of Lucid without updates installed. sudo DISPLAY=:0 xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, SKIP, gb,us, mac,, -- keyboard input broken due to invalid SKIP keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken due to invalid SKIP keyboard model
The problem definitely exists from the beginning. I have checked a number of times with basic installs of Lucid Beta 1 without installing updates and they all come out with exactly the same output: DISPLAY=:0 xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, SKIP, gb,us, mac,, So its seems the problem is dormant until such time as the latest console-setup update is applied and re-applies the settings and then breaks things. -- keyboard input broken due to invalid SKIP keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
Ok, i rebuilt the VM as it only takes about 10mins to recreate. I ran the following before the update: sudo DISPLAY=:0 xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, SKIP, gb,us, mac,, and then again after the update: sudo DISPLAY=:0 xprop -root |grep NAMES.S _XKB_RULES_NAMES(STRING) = evdev, SKIP, us, U.S. English, The only way i can do anything is by using an ssh session to the VM at the moment. I cannot login into GDM. I have tried logging in remotely and doing a service gdm shutdown and then a start but makes no difference. I am happy to setup a new VM without the updates and go through a troubleshooting process if anyone has any ideas as to what they would like me to supply them to compare what is different between the working and broken setups. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
Additionally when i run: setxkbmap gb Cannot open display default display or setxkbmap of any form i get this error message. I am running this from a ssh session. Attached is my dmesg output just incase. ** Attachment added: Dmesg output from VM http://launchpadlibrarian.net/42888764/dmesg_vm_nw.pdf -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
Thanks for that, i did read the thread beforehand, which was how i found this bug report. However i am not one of the lucky few that seems to have option of a onscreen keyboard to get me by. The best i can do is ssh. I may try something like nomachine to get me by for now. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
My none-working setup is as follows: VMWare Fusion 3.0.2 build-232780 Host OS: Mac OSX 10.6.3 (32/64bit) Guest OS: Ubuntu 10.04 Beta (64-bit), Kernel Ubuntu 2.6.32-19.28-generic I have setup a second VM should anyone wish to check the differences, with a standard install of 10.04 beta1, no updates installed whatsoever. Which works. The setup for that is as follows: VMWare Fusion 3.0.2 build-232780 Host OS: Mac OSX 10.6.3 (32/64bit) Guest OS: Ubuntu 10.04 Beta (64-bit), Kernel Ubuntu 2.6.32-16.25-generic -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
I have attached the Xorg logs from both the working and non-working VM's. There seems to be some issue with xkb creating xkm files at the end of the machine that is not working. ** Attachment added: Xorg.log.tar.gz http://launchpadlibrarian.net/42928275/Xorg.log.tar.gz -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
Just to add to your woes and to add a bit of diversity. I would like to point out that this does not only apply to Ubuntu as VM on a Windows host. I have exactly the same problem with Lucid, running under VM Fusion on Mac OSX. Interestingly, i only built this machine today and only had this problem once i updated the machine. I built the initial VM using a beta1 ISO and everything was wonderful. Unfortunately i have not been one of the lucky ones and been able to use the onscreen keyboard to login. I have no way to log in whatsoever, the keyboard does not come up if i try using the onscreen keyboard. No matter what i do the minute i tick the box, it disappears. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
