Thanks for the bug report.
This sounds like a hardware problem, most likely just new batteries are
required.
Wired mice or wireless with a dongle use the same code paths so clearly
that's working for some mice. I don't think there's any software bug
here.
** Package changed: xorg (Ubuntu) =>
Public bug reported:
What happens:
Wireless mouse shows up under `lsusb` list but doesn't control the
cursor.
Expected behavior:
The mouse controls the cursor.
Background:
I purchased a "Mini 2.4 GHz Wireless Optical Mini Finger Mouse Mice For
Laptop PC Computers"
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291
** Summary changed:
- NVIDIA: Laggy mouse movement on external monitor
+ Wayland/Hybrid/NVIDIA: Laggy mouse
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Public bug reported:
I use the same monitor 1440p, keyboard and mouse connected via HDMI to
older MacBook Pro and dual boot Laptop (Ubuntu + Win10) with Hybrid
graphics Intel 630HD and GeForce 1050Ti.
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.1-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Just checking in again :) The description of this report talks about
Focal, but I only see Jammy in the affected list?
--
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/1958673
Title:
SRU
Thanks. It kind of looks like the Nvidia driver is directly aware of the
USB-C/Thunderbolt port. So maybe it's not surprising then that the order
of connection matters.
For now that suggests the bug is somewhere between the Nvidia driver and
the kernel.
** Package changed: xorg-server (Ubuntu)
Before reboot I had:
* Laptop internal monitor on
* Samsung 34" external monitor on, with USB-C
* Aces 24" external monitor on, with HDML
Rebooted without changing anything.
* The Samsung 34" / USB-C connected external monitor did _not_ come to life.
* The Acer 24" / HDMI second external
I've got it working one more time.
* Disconnected the HDMI.
* Rebooted - with USB-C to the monitor connected.
* The external monitor did not register.
In addition to the monitor a Lenovo network adapter (8P8C for
CAT5/CAT6/..) is connected.
I tailed /var/log/syslog and /var/log/kern.log
I kept
If you are using a USB-C dock then please see bug 1970495.
Otherwise if you think the USB-C port might be wired directly to the
Nvidia GPU then please see bug 1960865.
When the bug occurs next please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the
Also which monitor is displaying the wrong resolution?
** Summary changed:
- monitor resolution issue
+ Wayland session limited to 1024x768
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux
Please try selecting 'Ubuntu on Xorg' on the login screen.
** Tags added: hybrid i915 radeon
--
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/1973143
Title:
[impish] Wayland session limited to
Public bug reported:
The external Samsung 34" monitor connects fine with HDMI, but not on USB-C.
It worked for a short amount of time at one point early after installing Ubuntu
22.04, but not since.
No difference with disconnect / reconnect, reboot, etc.
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
Even though my monitor support maximum resolution, I can only set it to
1068X768.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
ApportVersion:
14 matches
Mail list logo
