Public bug reported:
Hi,
I have a got a touchscreen plugged in .
Altough I have no gesture enabled , sliding cursor from top screen to bottom it
applies an unattended gesture reducing window size.
here is a video :
https://drive.google.com/file/d/1vLRCZrHLXDZgBQXIjcqqeha4ouNmfL6q/view?usp=sharin
Public bug reported:
It doesn't appear in /proc/bus/input/devices:
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B: SW=1
I: Bus
Also, it correctly works with a live Pop!_OS installation USB; `uname
-a` there yields:
Linux pop-os 5.13.0-7614-generic #14~1631647151~21.04~930e87c-Ubuntu SMP
Fri Sep 17 00:24:58 UTC x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package thunderbird -
1:91.5.0+build1-0ubuntu0.20.04.1
---
thunderbird (1:91.5.0+build1-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream stable release (91.5.0build1)
thunderbird (1:91.4.0+build2-0ubuntu0.20.04.1) focal; urgency=medium
* New upstr
Thanks for the bug report. It looks like the touchscreen thinks either a
button is held down or a finger is touching the screen during the
downward cursor movement.
Please try running 'sudo evtest' in a separate window to log all the
touchscreen events, and see if you can find evidence of the kern
Thanks Timo for taking a look!
** Changed in: linux-hwe-5.13 (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
@arighi
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
To manage notifications about this bug go to:
https:
Public bug reported:
?
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubuntu-release-upgrader-core 1:21.04.17
ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22
Uname: Linux 5.11.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
CasperMD5CheckResult: unknown
Public bug reported:
Upon running e.g. Puppet's r10k, which makes use of ruby-faraday
(version 0.15.4-3), a few lines of deprecation warnings are thrown on
every invocation:
# /usr/bin/r10k deploy environment -p
/usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given
blo
Great work! I second for the new version in Focal, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955413
Title:
Update to containerd 1.5.9
To manage notifications about this bug go to:
http
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ruby-faraday (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958629
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942713
Title:
bcmw
here is evtest output
esting ... (interrupt to exit)
Event: time 1642755262.678951, type 3 (EV_ABS), code 0 (ABS_X), value 431
Event: time 1642755262.678951, type 3 (EV_ABS), code 1 (ABS_Y), value 960
Event: time 1642755262.678951, -- SYN_REPORT
Event: time 1642755262.6799
Public bug reported:
Hello everybody,
Recently my internal monitor on my laptop (HP Pavilion Gaming 15) starts
flickering after boot. On my laptop I have Geforce 1660 Ti beside AMD
Renoir. Formerly I had the problem of not detecting the external monitor
but solved it. Now this problem has arisen.
Thank you for updating the MIR content. Foundations agreed to take
ownership of this package in our weekly #ubuntu-meeting and signed up as
a team subscriber. The outstanding issues are still to be done.
** Tags added: fr-1990
** Tags removed: rls-jj-incoming
--
You received this bug notificati
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Je
** Changed in: asterisk (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams console output to syslog due to systemd
mi
I can't replicate your error message as everything seems to be working
normally here bearing in mind that Ubuntu 22.04 is still in its
development period. I can enable Liverpatch in "Software & Updates" but
it later turns off automatically.
Please be aware that Livepatch is not yet available for U
Thank you for the review Christian! Due to lack of possible testing
hardware, no critical use cases and lack of resources, we have decided
to postpone this MIR until needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Public bug reported:
32bit Kubuntu 18.04.5 Chromium-browser crash notification didnt came up
after 2nd time crashing. This is 7th time
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.27
ProcVersionSignature: Ubuntu 5.4.0-96.109~18.04.1-generic 5.4.157
Uname: Linux 5.4
Public bug reported:
Reproduced this issue several times, but it doesn't happen all the time.
After trying to take a screenshot of an area, the screenshotting may fail and
the ubuntu dock and all window menus become unresponsive. Mouseover on the dock
will change the cursor to the plus-sign used
Why is the size problematic? And how do you define less common HW? Where
do you draw the line? Some HW might not be common for you but is for
others. I'm sympathetic to the request but it's not trivial to find the
right balance without upsetting/breaking existing users.
** Also affects: linux-firm
*** This bug is a duplicate of bug 1958412 ***
https://bugs.launchpad.net/bugs/1958412
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Also affects: linux-azure-5.11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-5.11 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-azure-5.11 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-azure-5.11 (Ubuntu Focal)
Im
Thank you for the reply and for setting up the branch, I'll do the MR on
this branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943849
Title:
[FFe] improve the appearance-page in gnome-control-
Thank you for your suggestions. However, the changes you are requesting
aren't really a bug and require more discussion, which should be done on
an appropriate mailing list or forum.
http://www.ubuntu.com/support/community/mailinglists might be a good
start for determining which mailing list to us
*** This bug is a duplicate of bug 1958412 ***
https://bugs.launchpad.net/bugs/1958412
This sounds like bug 1958412.
** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)
** Changed in: linux-hwe-5.13 (Ubuntu)
Status: Confirmed => New
** Summary changed:
- Flickering internal
Thanks. It looks to me that there is a phantom touch event at the start
of the gesture. So gnome-shell is behaving correctly:
Event: time 1642755262.679902, type 1 (EV_KEY), code 330 (BTN_TOUCH),
value 1
This means it is either a kernel bug or a hardware fault relating to the
touchscreen.
** Pac
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958412
Title:
[amdgpu] at startup and shutdown screen gets white noise
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
** Package changed: ubuntu => ubuntu-unity-meta (Ubuntu)
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890725
Title:
wacom tablet disturbs unity background, color scheme and k
Please consider a backport for Focal. This LTS distro will become EOL in 2025
only.
Thus there are still 3 years of use ahead of us...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869405
Title:
C
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866999
Title:
gnome-calendar does not sync with Google Calendar
To manage notifications about this bug go to:
https://bugs.launc
Possibly fixed after 20.04? I might try upgrading some day I have plenty
of time then. If I then stop getting the crashes, I could mention that
here. And if I still get them, I guess I could mention that. It's pretty
random when it happens, but I guess it should happen at least once per
month, espe
This bug is awaiting verification that the linux-raspi/5.13.0-1016.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists
This bug is awaiting verification that the linux-raspi/5.11.0-1028.31
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the
problem still exis
This bug is awaiting verification that the linux-raspi/5.13.0-1016.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists
This bug is awaiting verification that the linux-raspi/5.13.0-1016.18
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists
This bug is awaiting verification that the linux-raspi/5.11.0-1028.31
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the
problem still exis
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Public bug reported:
I am running Ubuntu 20.04.3:
$ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
I am running Ubuntu on a Lenovo ThinkPad P14s with Intel Wi-Fi 6 AX210 Wi-Fi
interface. This used to work up to kernel 5.11.0-46 (which loaded iwlwifi
"firmware version
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
** Attachment added: "Verification report"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+attachment/5556131/+files/SRU%20for%20network-manager%28verify%20report%29%20.pdf
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You receiv
Test passed with Lenovo ThinkEdge SE30(11ND) on Focal:
* The version of the packages tested:
network-manager: 1.22.10-1ubuntu2. 3
The detail testing procedure and result is provided as the attached file
: "SRU for network-manager(verify report).pdf"
--
You received this bug notification
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Do you still see a problem related to th
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Do you still see a problem related to th
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Do you still see a problem related to th
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Do you still see a problem related to th
** Changed in: netsurf (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958082
Title:
netsurf crashes when trying to visit "duckduckgo.com"
To manage notif
This is a build time comparison between linux 5.13.0-28.31 and
5.13.0-27.29
* amd64
- before: 3 hours, 22 minutes
- after: 2 hours, 19 minutes
* arm64
- before: 15 hours, 49 minutes,
- after: 15 hours, 12 minutes
* armhf
- before: 10 hours, 59 minutes
- after: 9 hours, 41 minutes
* ppc
I'm using a Lenovo Ideapad with a Ryzen 7 4700U on Ubuntu 20.04 focal,
and with the focal kernel 5.13.0-27 I still can't suspend the device.
Last working is 5.13.0-22
The mentioned released fix for impish, is it also included in the focal
version of 5.13.0-27 or do we have to wait longer for an fo
it's part of ubuntu again... https://launchpad.net/ubuntu/+source/crawl
** Changed in: crawl (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631677
Title:
i have continued to have performance issues which are charecterised by
chrome making preload go nuts , its particularly bad when video is
involved. I discovered this by watching top when i got load spikes and
noticing that when i rebooted preload was bring the problem back.
i removed preload and n
Public bug reported:
Tried re-installing mysql server after uninstalling
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.27-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules:
** Also affects: cloud-initramfs-tools
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958260
Title:
cloud-initramfs-copymods hides the full list of module
Thank you for your bug report which I've come across whilst reviewing
bug reports filed against "end-of-life" Ubuntu releases.
You reported this bug some time ago and there have been many changes in
Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
I'm closing
Thank you for your bug report which I've come across whilst reviewing
bug reports filed against "end-of-life" Ubuntu releases. You reported
this bug some time ago and there have been many changes in Ubuntu since
that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
I'm closing t
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958628
Title:
Fehlermedlung
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
Building libxcrypt with the new binutils upload
2.37.50.20220119-0ubuntu1 in proposed produces binaries with one RWE
LOAD header instead of two LOAD headers (one RE, one RW); causing it to
fail to load in services that use MemoryDenyWriteExecute=yes, thus
breaking a ton of sys
** Changed in: ledmon (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
https://bugs.l
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Do you still see a problem related to th
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
The attached patch resolved the issue on my test VM, could you please
give it a try?
** Patch added:
"0001-s390-module-fix-loading-modules-with-a-lot-of-reloca.patch"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5556146/+files/0001-s390-module-fix-loading-modul
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Binutils has been removed from jammy-proposed while this is
investigated:
$ remove-package -m 'Missbuilding libraries (libcrypt2 as example)' -s
jammy-proposed binutils
Removing packages from jammy-proposed:
binutils 2.37.50.20220119-0ubuntu1 in jammy
binutils 2.37.50.2022
Knowing that libxcrypt is miss-built this has also been removed from
jammy-proposed:
$ remove-package -m 'Causing package test failures' -s jammy-proposed libxcrypt
Removing packages from jammy-proposed:
libxcrypt 1:
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Hi Jeremy,
It's not your fault. This is something your sponsor is supposed to have
checked.
@Alberto
Please could you properly review this, make sure it meets SRU policy,
try to anticipate and answer any questions the SRU team might have in
advance, and then work with Jeremy to resubmit to the q
The backport to LTS releases is in my todo list. I added tasks for those
series so you can track it in this bug.
** Also affects: containerd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: containerd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
*** Bug 374472 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317449
Title:
sqlite3 version 3.8.2 breaks digikam
To manage notifications about this b
Technically this was critical while it was in proposed, I set it to high
as we removed it; but it's a blocker to fix this for a future binutils
upload.
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Thanks Paride! I confirm that updating to your PPA fixes the issue,
which confirms that it's sssd.
I'll do a no-change rebuild of impish's sssd now and try with that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Do you still see a problem related to t
Thank you Dag! Let me try looking at the provided logs and see if I can
pinpoint it better.
In the meantime, the visibility toggle has been committed for GTK + I
prepared a MP for the KDE counterpart.
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquit
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Do you still see a problem related to th
> I'll do a no-change rebuild of impish's sssd now and try with that.
Done, but the bug is still the same. So not some weird build-time issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958392
Ti
Further data points:
- The first build with new binutils was
s390x build of soci 4.0.1-5ubuntu1 in ubuntu jammy PROPOSED
- Investigation on Debian shows that it was not affected, and that the
bug is caused by LTO - if you enable LTO on Debian, it starts building
the broken library as well.
--
My bad, it's just "Japanese" (I didn't run the installation again just
to check the exact hardcoded text for the bug report).
My point was that the physical actual keyboard is a japanese one with 109 keys
(the usual in japanese keyboards).
The japanese layout has some keys that just plainly don'
From the bug description:
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
It's possible you had a bad write to your media or for some other reason
its contents could not be read correctly. If you're still having
problems you should try re-writing the image to your media
All autopkgtests for the newly accepted linux-meta-raspi (5.13.0.1016.21) for
impish have finished running.
The following regressions have been reported in tests triggered by the package:
west-chamber/unknown (arm64)
dm-writeboost/unknown (arm64)
gost-crypto/unknown (arm64)
nat-rtsp/unknown (arm6
Public bug reported:
Hello,
The two above packages are sync'd in from Debian and it's causing
dependency problems in our ongoing PHP transition. Requesting you to
please drop these two packages from jammy-proposed temporarily and I'll
sync them back again once the doctrine, symfony migrates to Ja
Oh, and also please check the image I attached.
The keyboard layout program showing "?" instead of the layout name is a
clear hint that something is not right.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
From the bug description:
CasperMD5CheckMismatches:
./pool/main/l/linux-signed-hwe-5.8/linux-image-5.8.0-43-generic_5.8.0-43.49~20.04.1_amd64.deb
CasperMD5CheckResult: skip
It's possible you had a bad write to your media or for some other reason
its contents could not be read correctly. Please
From the bug description:
CasperMD5CheckMismatches:
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.141-0ubuntu0.20.04.1_i386.deb
CasperMD5CheckResult: skip
It's possible you had a bad write to your media or for some other reason
its contents could not be read correctly. Ple
From the bug description:
CasperMD5CheckMismatches:
./pool/main/l/linux-signed-oem-5.6/linux-image-5.6.0-1027-oem_5.6.0-1027.27_amd64.deb
CasperMD5CheckResult: skip
It's possible you had a bad write to your media or for some other reason
its contents could not be read correctly. Please always al
1 - 100 of 276 matches
Mail list logo
