To be clear, I wish to send this video. It happens unpredictably. Even
after a reformat it still happens like this.
So, is it possible this is a bug or this is more likely a hardware issue
rather than a bug or is it possibly both?
(Because of necessity, I had to change the laptop keyboard for the
So is there any progress so far? Or is this more likely a hardware issue
rather than a driver issue?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1775016
Title:
[Dell Latitude E6420] Ub
Despite my efforts, I still do (as of this writing, I experienced two of
these sudden keyboard shut offs). And it is kind of unpredictable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/177
Sorry if I missed the point all this whole time.
But, this is just in. I saw a warning in the BIOS settings when
switching between AHCI and RAID. There was a warning that actually
threatens the installation that says:
"SATA Operation is being changed!
Attention! Changing this setting may preven
Well, I just applied a firmware upgrade from A08 (very first firmware
revision of the Dell Latitude E6420) to A25 (released just this year, 27
March 2018).
SOURCE:
https://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=JP0YK
I am yet to see the results of the firmware upgrade.
This just in, given that I currently use Linux 4.10.17-041017-generic
(x86_64), here is my situation as of now:
1. I was in Twitter.
2. I was trying to type my tweet
3. The up button temporarily does not work but other buttons do work
4. And when I press other keys and mouse, **the up button works
Well thanks, as of now I'm currently using this kernel:
-Version-
Kernel : Linux 4.10.17-041017-generic (x86_64)
Version : #201705201051 SMP Sat May 20 14:53:33 UTC 2017
C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
Distribution: Ubuntu 18
In the latest update that I just installed before I revert back, which
is 4.15.20.24 (if I'm not mistaken), there was a point that even a
corded USB mouse refuses to even click (or rather select any item in the
desktop).
--
You received this bug notification because you are a member of Ubuntu-X,
This just in, I'm not sure about this but the error is being mitigated
by downgrading the kernel from 4.15.20 to 4.10.14.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1775016
Title:
[De
I'm using a laptop keyboard alone. No USB Keyboard, only a Rapoo
wireless mouse.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1775016
Title:
Ubuntu/Xubuntu 18.04 bug: Keyboard stops wor
And yes, no usb wireless keyboard, and no usb mouse and keyboard combo.
Only a Rapoo wireless mouse (white) and a laptop keyboard in Dell
Latitude E6420.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpa
now i got to reset as in reboot then keyboard starts working again
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1775016
Title:
Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the mi
at this point im only using mouse [rapoo mouse, not keyboard nor
keyboard combo] as my keyboard. my keyboard, as of that screenshot and
as of this writing , is not working. i cannot get kb combinations 2
work.
** Attachment added: "Screenshot at 2018-06-29 17-32-35.png"
https://bugs.launchpad.
** Description changed:
Ubuntu/Xubuntu 18.04 LTS bug
What should have happened: Keyboard should have been working no matter
the processes
What happened instead: Keyboard stops working in the middle of typing
when running firefox and when running the terminal as (sudo su) and
- simi
Public bug reported:
Ubuntu/Xubuntu 18.04 LTS bug
What should have happened: Keyboard should have been working no matter
the processes
What happened instead: Keyboard stops working in the middle of typing
when running firefox and when running the terminal as (sudo su) and
similar programs
xserv
Public bug reported:
..
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:9.012-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPl
Public bug reported:
After upgrading from 13.0.4
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: nvidia-current 304.88-0ubuntu0.0.2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Err
Public bug reported:
?
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value
Same here: A dual screen setup, Ubuntu 11.10, nvidia geforce 9300, the exact
same message reported by James Stewart appears after each login (except it's
"with output at 1680x1050@50Hz").
The only un-commented line in my xorg.conf (created with the nvidia X server
settings tool) referring to som
For the moment I have installed a Windows Vista Premium 64bits which
works fine, and runs Opengl correctly. I will keep trying the latest
Long Term Ubuntu anyway, when available, in case...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-
I observe the same problem with Ubuntu 10.10 Desktop i386 Live. There is
no way to reach a clean screen!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/372556
Title:
Rec
Same here: Lucid, MS Ergonomic 4000. Zoom doesn't work.
--
MASTER: evdev driver ignores keycodes > 255
https://bugs.launchpad.net/bugs/313514
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
___
Sorry, no way to get 9.04 logs, as the system doesn't let reach a
command line...
But I think I have got something: I have compared the recovery start up
with telinit 2 (which fails) and telinit 5 (which works fine), looking
at the scripts started in each /etc/rc2.d and /etc/rc5.d. The only
diffe
Produced when screen gets fuzzy
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/26707466/Xorg.0.log.old
--
Recovery start+telinit 5 is the only way to start correctly
https://bugs.launchpad.net/bugs/372556
You received this bug notification because you are a member of Ubun
Produced when screen gets fuzzy
** Attachment added: "gdm:0.log.1"
http://launchpadlibrarian.net/26707503/gdm%3A0.log.1
--
Recovery start+telinit 5 is the only way to start correctly
https://bugs.launchpad.net/bugs/372556
You received this bug notification because you are a member of Ubuntu-X
** Attachment added: "Produced when screen gets fuzzy"
http://launchpadlibrarian.net/26707411/gdm%3A0.log.1
--
Recovery start+telinit 5 is the only way to start correctly
https://bugs.launchpad.net/bugs/372556
You received this bug notification because you are a member of Ubuntu-X,
which is s
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/26707365/Xorg.0.log
--
Recovery start+telinit 5 is the only way to start correctly
https://bugs.launchpad.net/bugs/372556
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubu
** Attachment added: "gdm:0.log"
http://launchpadlibrarian.net/26707351/gdm%3A0.log
--
Recovery start+telinit 5 is the only way to start correctly
https://bugs.launchpad.net/bugs/372556
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubu
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/26707337/xorg.conf
--
Recovery start+telinit 5 is the only way to start correctly
https://bugs.launchpad.net/bugs/372556
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubunt
I have gathered some data which can be helpfull.
First lspci.txt is the lspci output in this system.
Second xorg.conf is the configuration file for X that is in use.
Third two files output during the 'good' run (telinit 5):
by X, Xorg.0.log
by gdm, gdm:0.log
Forth two same files ou
30 matches
Mail list logo
