[Ubuntu-x-swat] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....

2014-02-11 Thread Barry Drake
I've put that in and am trying it. Thanks. For the record, gdm is not istalled in Trusty, so you need to do sudo apt-get install gdm In my case, I was given the option to make gdm the default during installation. If not, you need to edit /etc/X11/default-display-manager after installing gdm

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....

2014-01-26 Thread Barry Drake
Another workaround seems to be: Open a terminal from the login screen using ctrl+alt+F2 followed by username and password. Then do: sudo stop lightdm sudo lightdm -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....

2014-01-15 Thread Barry Drake
Next time, try going into suspend if you can. This always works for me. Failing that, try ctrl+alt+F2 to bring up a terminal. Log in (your user name and password) and do 'sudo shutdown -h to shut down properly. -- You received this bug notification because you are a member of Ubuntu-X, which

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty boots spasmodically with inactive keyboard .....

2014-01-08 Thread Barry Drake
Problem came back after a large update that included a number of xorg packages ... So the bug is still there as far as I can see at the current build. I'm happy to carry out further tests. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty boots spasmodically with inactive keyboard .....

2014-01-07 Thread Barry Drake
I had a problem earlier today and wiped the drive with Trusty installed. I have re-installed and fully updated but no longer see this fault. Pleas hold until I can see any further problems. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty boots spasmodically with inactive keyboard .....

2014-01-06 Thread Barry Drake
Thanks for that. I have reflashed the bios to version 1.6 release date 07/11/2013 and will wait to see if the problem is fixed. As the problem is spasmodic, I will wait a week or so before saying that it is no longer there. -- You received this bug notification because you are a member of

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty boots spasmodically with inactive keyboard .....

2014-01-06 Thread Barry Drake
Sorry I didn't read the instruction to update the bios before reporting a hardware bug of this kind. I can confirm that nothing has changed. The information requested is: barry@trusty:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date [sudo] password for barry: P1.60

[Ubuntu-x-swat] [Bug 1264543] [NEW] Trusty boots spasmodically with inactive keyboard .....

2013-12-27 Thread Barry Drake
Public bug reported: Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing CTRL+ALT+F2 and withing the terminal. Logout and login from the terminal followed by CTRL+ALT+F7 to reaccess X does not bring back the keyboard. My current workaround is

[Ubuntu-x-swat] [Bug 1264543] Re: Trusty boots spasmodically with inactive keyboard .....

2013-12-27 Thread Barry Drake
I get no problem when booting into Saucy which I have as a dual-boot installation. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1264543 Title: Trusty boots spasmodically with inactive

[Ubuntu-x-swat] [Bug 999563] [NEW] fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build

2012-05-15 Thread Barry Drake
Public bug reported: This driver is working OK in my installation of 12.04. Both FGLRX drivers offered in 12.10 fail to install. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.4.0-1.3-generic-pae 3.4.0-rc5 Uname: Linux

[Ubuntu-x-swat] [Bug 999563] Re: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build

2012-05-15 Thread Barry Drake
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/999563 Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 999341] [NEW] fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build

2012-05-14 Thread Barry Drake
Public bug reported: First bot into 12.10 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.4.0-1.3-generic-pae 3.4.0-rc5 Uname: Linux 3.4.0-1-generic-pae i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion:

[Ubuntu-x-swat] [Bug 999341] Re: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build

2012-05-14 Thread Barry Drake
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/999341 Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

2012-03-26 Thread Barry Drake
Started using Unity 2d as ther is a current problem with 3d. Crash occurred after opening Thunderbird. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/905686 Title: nautilus assert failure:

[Ubuntu-x-swat] [Bug 933059] Re: Num Lock stucks on makes keyboard unusable

2012-02-16 Thread Barry Drake
Exactly the behaviour I get. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/933059 Title: Num Lock stucks on makes keyboard unusable To manage notifications about this bug go to: