I just had this hit me with kubuntu 12.10 and firefox aurora, I updated
to the latest (20.0~a2~hg20130131r123843-0ubuntu1~umd1~quantal at the
moment) and it made no difference.
I can left click on links and tabs, but I cannot open menu items and
cannot right-click on anything
as far as
apport information
** Tags added: apport-collected jammy ubuntu wayland-session
** Description changed:
after updating to jammy beta, xorg does not work for any desktop, in
every case the desktop comes up, but there is no response to keyboard or
mouse (not even numlock). I tried
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576393/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576394/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576397/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576396/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576392/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576398/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Public bug reported:
after updating to jammy beta, xorg does not work for any desktop, in
every case the desktop comes up, but there is no response to keyboard or
mouse (not even numlock). I tried unplugging and replugging the devices
with no luck.
All desktops do 'work' in the wayland version,
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576405/+files/acpidump.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576402/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576406/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576399/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576401/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576403/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576400/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576395/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1967651/+attachment/5576404/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
separate bug filed for wayland
note that for this bug I am not sure that it's only an input problem for
this bug. The system is unresponsive (inc numlock) so I can't tell if
it's only the input or if the entire system is locked.
--
You received this bug notification because you are a member of
Public bug reported:
failed to install
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu4
On Fri, 6 Oct 2023, David Lang wrote:
> On Fri, 6 Oct 2023, Nathan Teodosio wrote:
>
>>> - Fetch and check assertions for snap "chromium" (2642) (cannot verify
>> snap "chromium", no matching signatures found)
>>
>> Looks like a transient fail
ice after a reboot, same error each time.
David Lang
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2038609
Title:
package chromium-browser (not installed) failed to inst
adding the package xserver-xorg-input-libinput appears to have solved
the problem. According to the folks at freedesktop, it should have
defaulted to use the libinput driver, even without the 40-libinput.conf
file, but in my case it didn't
** Changed in: xserver-xorg-input-libinput (Ubuntu)
I was hoping that updates to the full release would fix this, but it
hasn't. Any suggestions on what I should try to track this down?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
24 matches
Mail list logo
