There's a better workaround (method 3) now suggested on the arch wiki page:
https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Yoga_(Gen_3)
It works with Ubuntu as well; you can test it when the touch screen
isn't responding with:
sudo apt install acpi-call-dkms; sudo modprobe acpi_call;
usbcore.quirks=056a:5146:m also failed for me (with 19.10 and focal); I
read on the Arch wiki that disabling Thunderbolt in the bios (under
Security -> IO ports) might work and tried it, and it worked!
I imagine this breaks Thunderbolt, but have no way to test.
--
You received this bug
Speaking of, I ran into this bug moving from 18.04 to 20.04.
It left apt in a broken state, but I was able to uninstall the lxd and
lxd-client packages and complete the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This happened on my machine, and diepes's fix worked for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
To manage notifications about this
I ran into this on 18.04 -- also with Screen Reader set to off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496542
Title:
Running processes left after disabling screen reader
To manage
Is there any workaround for this besides using another window manager? I
am rather liking Unity but this makes the launcher nearly useless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755842
Title:
I ran into this with 12.10 (with wine installed), and did #16 to fix it
-- though it looks like #32 has a much better solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937200
Title:
Fat fonts
*** This bug is a duplicate of bug 829086 ***
https://bugs.launchpad.net/bugs/829086
This bug effected/effects me as well (i5-2520M), but this is a duplicate
of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/882349 and you can work around it with the instructions
I am no longer able to reproduce it in Karmic or Lucid. :)
--
Sounds are taken over by java programs
https://bugs.launchpad.net/bugs/82099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I found that, to summarize... if I have a 9 button on the mouse on the
server, but the client only has a 3 button mouse, synergy will crash
when I use one of those extra buttons. As some others have noticed,
it's whatever the last mouse used had.
As a work around for me -- and this is nowhere
I can see that it was removed deliberately, and reading the reasons it
seems understandable.
I would like to point out that the battstat applet is a very different
thing from the g-p-m. It was an applet that could be moved and
rearranged, the current charge could be displayed on the panel, the
Turning off tiling made it respond *much* more quickly for me as well. I
read there were many disadvantages to doing without tiling, but the
massive performance boost while rotated is worth it.
--
It does not refresh well when dragging a window in the rotated screen (Santa
Rosa)
Ok, does this seem familiar to anyone else? Mozilla is waiting until a
distro is just about to ship then slapping them with demands they either
have to give into quick or do a lot of work to get around. First they
did it with Debian, and now with Ubuntu. Why are the distros putting up
with this
This happens in Ubuntu 7.10 (AMD64) as well, and is not limited only to
Synergy on Windows machines -- all connected clients do not work if the
machine running the synergy server is also running Glipper.
There are no issues if you run Glipper and then run Synergy in client
mode as long as the
I had/have a similar problem as well, although in my case, like Thomas
Detoux's, killing java gave me sound back. I was able to fix it by
using the ALSA wrapper for OSS applications (package alsa-oss, command
is aoss) before launching java. I was losing sound even when the java
program I was
15 matches
Mail list logo
