When will this be fixed in 20.04 LTS? If not, why not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868517
Title:
Stray /usr/.crates2.json file
To manage notifications about this bug go to:
Shouldn't there be a proposed fix for the hwe kernel of focal as well so
we can test?
As I understood it (and please correct me if I'm wrong), the HWE kernel
is simply the kernel from a newer Ubuntu release (currently groovy)
rebuilt with the older toolchain of an LTS release (currently focal).
If there is an easy way to install the newer kernel on Focal I'll
happily try it (I don't particularly want to build a kernel by hand
again, I left Gentoo many years ago for a reason). I presume I could
download a couple of deb from somewhere and install them by hand, then
run some dkms commands
Since the hardware device in question is attached via USB I'm adding
lsusb output here.
The device in question is "Bus 001 Device 007: ID 056a:51e9 Wacom Co.,
Ltd Pen and multitouch sensor"
** Attachment added: "lsusb.txt"
Public bug reported:
When using the Wacom pen that was included for the touch screen on my
Lenovo Thinkpad P15 Gen1 laptop, the kernel hangs. This worked a few
weeks ago. Looking at journalctl after rebooting shows the following two
lines:
mar 22 13:26:33 minerva kernel: wacom
I'm changing this to public security bug, as the CVE is already
published.
** Information type changed from Private Security to Public Security
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-26910
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Even though it says fix released, Ubuntu 18.04 is still affected by
this. Presumably this needs LTS backporting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863080
Title:
Unable to use dead keys
I have these messages too. Lenovo Thinkpad R500 running lucid with
2.6.31 kernel. Unable to test 2.6.32 kernels due to other bugs (reported
elsewhere). Strangest thing is that this system have DisplayPort rather
than HDMI. I don't have any external monitor connected, nor any to test
with. But the
So when can we expect a fix for this in the stock lucid kernel (amd64)?
This reduces battery life with more than half compared to jaunty on my
Thinkpad R500 (Core 2 Duo P8400). Didn't stay on karmic for long enough
to check this (only for about 2 days).
--
Tens of wakes per second in [kernel
How does one fix a system affected by this issue? I have here a
presumably broken upgrade due to hitting this bug. A partial upgrade
was mentioned in one comment, but how does one perform that?
--
etckeeper hook breaks upgrade with Argument list too long
https://bugs.launchpad.net/bugs/574244
Does that mean that there will be no issues with the package manager
that needs to be resolved after the crash? Like cleaning up phase (if I
understood the upgrade screen correctly it crashed at the end of the
stage before clean up [note this is backtranslated from Swedish l10n,
might be called
Seems like using the acpi_pm timer doesn't help either:
[ 1444.543809] CE: hpet increasing min_delta_ns to 15000 nsec
[18676.192193] CE: hpet increasing min_delta_ns to 22500 nsec
[29242.780200] CE: hpet increasing min_delta_ns to 33750 nsec
These three above all happened within 10 minutes after
Same issue on 2.6.28-15-generic (x64_64).
System is a Lenovo Thinkpad R500.
$ uname -a
Linux dragon 2.6.28-15-generic #48-Ubuntu SMP Wed Jul 29 08:53:35 UTC 2009
x86_64 GNU/Linux
$ grep 'model name' /proc/cpuinfo
model name : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
model name
Ok tested the workarounds:
* clocksource=jiffies caused X to refuse to start
* noapic booted and X worked, but didn't fix the issue. Rather it make it
happen a lot quicker after boot. Often less than a minute. Going to test with
other clock sources, like acpi pm timer.
--
lockups with default
The acpi pm timer (clocksource=acpi_pm) does seem to work better than
the jiffies one so far (X works), and so far it seems to work. Not sure
what sort of side effects it could have though. Or if it will work in
the long run.
--
lockups with default (hpet) clocksource on 2.6.27-2-generic 64-bit
*** This bug is a duplicate of bug 400664 ***
https://bugs.launchpad.net/bugs/400664
At comment #3:
I can do that. (Sorry for the slow reply, has been away from home for quite a
while, unable to check email.)
--
Having vino-preferences open causes vino-server to crash every few seconds.
*** This bug is a duplicate of bug 400664 ***
https://bugs.launchpad.net/bugs/400664
As requested in comment #4, continuing discussion in the other bug,
backtrace requested in comment #3 is attached there.
--
Having vino-preferences open causes vino-server to crash every few seconds.
As requested in
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/405339/comments/4
continuing discussion here.
As requested in
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/405339/comments/3 here is a
new log from debugging:
** Attachment added: Vino backtrace as requested.
I have the same issue as the original reporter (with warzone 2100 at
least) on my Lenovo Thinkpad R500. Same details reported by lspci for
VGA compatible controller and Display controller. Using Ubuntu 9.04
(x86_64).
--
[g45] Warzone 2100 3D is rendered black with GMA4500MHD
Public bug reported:
Binary package hint: vino
Ubuntu version: 9.04 (Jaunty) for amd64.
Vino version: 2.26.1-0ubuntu1
Kernel: 2.6.28-13-generic.
Graphics driver: xserver-xorg-video-intel version 2:2.6.3-0ubuntu9.3
Issue:
When vino-preferences is opened, any connected clients are disconnected
Issue exists with a Thinkpad R500 with Ubuntu 9.04 as well. It has such
an ALPS Dual Pointing device.
Using kernel 2.6.28-13-generic x86_64. Any more useful info I can
provide?
--
tap-to-select option is missing for trackpoint on Thinkpad R61 in Hardy beta
https://bugs.launchpad.net/bugs/210085
I installed debugging symbols for vino and attached gdb to the running
vino-server process then ran vino-preferences. Attached is the result.
** Attachment added: gdb-vino-server.txt
http://launchpadlibrarian.net/29589265/gdb-vino-server.txt
--
Having vino-preferences open causes vino-server
As a crossfire developer (not an Ubuntu user) I can say this is not a
upstream bug, I run 64-bit Gentoo Linux and the client works perfectly
there. Nor has it been reproduced on any other distro. So I'm
considering closing the upstream bug with works for me.
--
Double text display issue with
For your information: Upstream bug has been set to pending (will auto
close in 30 days if there are no updates) with resolution works for
me.
--
Double text display issue with crossfire-client-gtk2
https://bugs.launchpad.net/bugs/87194
You received this bug notification because you are a member
24 matches
Mail list logo
