reply #5
Can you try $ fwupdmgr get-updates to see if you can see the latest
firmware in LVFS? or attach your output here.
Also, you can always get latest BIOS here
https://www.dell.com/support/home/en-in/product-
support/product/latitude-15-7520-laptop/drivers, sometimes it is newer
than BIOS in
Hi there,
I used this[0] script to test the different series. The most relevant
parts of it are those parameters for qemu:
-smbios type=0,vendor='Hyper-V test',version=1.2.3 \
-smbios
type=1,manufacturer=t1manufacturer,product=t1product,version=t1version,serial=t1serial,uuid=---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 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 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
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
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Reporter's account suspended by Launchpad admins.
Closing as no further information can be asked of reporter.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug not
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Reporter's account suspended by Launchpad admins.
Closing as no further information can be asked of reporter.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug not
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
** Tags added: fr-1927
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1954649
Title:
autopkgtest regressions with python3.10 as supported
Status in ipywidgets pa
#7 output was already attached there, just grepped for brevity. The
first lines where confusing me though, I've now upgraded the system BIOS
from 1.6.1 to 1.12.2. 1.13 seems available on the official site, I'll
report back ASAP on the results of the upgrade.
--
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.
dash is POSIX-compliant shell similar to bash. Looking at your bug
report you probably intended to report your problem against the 'Unity'
package.
Ubuntu 16.04 (xenial) reached end-of-life on Apr
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
dash is POSIX-compliant shell similar to bash. Looking at your bug
report you probably intended to report your problem against the 'Unity'
package.
Ubuntu 15.04 (vivid) reached end-of-life on Febr
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
dash is POSIX-compliant shell similar to bash. Looking at your bug
report you probably intended to report your problem against the 'Unity'
package.
Ubuntu 14.04 (trusty) reached end-of-life on Apr
After first reboot with BIOS 1.12.2 all seems fine, the update seems
even to have made the process of hooking up the docking station and
activating the external monitors faster.
After first sleep and wakeup, no battery pinging that I can see with
udevadm monitor, not even at a slow pace (but the b
Thank you for your bug report, could you perhaps report it directly
upstream as well on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues ?
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touc
The git change is https://gitlab.gnome.org/GNOME/gtk/-/commit/e23b4dd2
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => High
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboo
** Changed in: gtk+3.0 (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1913775
Title:
Copy from Firefox Wa
The issue is first found on other platform during enablement, and the
fix is landed in BIOS. Latitude 7520 has no problem with the BIOS
version we certified, however, the regression should be caused by BIOS
upgrade. Therefore, I assume the latest BIOS should contain fix for it.
As I know, the issue
the armhf tests worked after a retry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
Status in evolution-data-s
Some further research on this [1] suggests gzip may be a preferable
choice on the smaller platforms (lower memory usage, and better
compression anyway), plus this would alleviate the need for including
lz4 in the images.
I need to do some further analysis of the decompression to see if it is
still
Just to clarify, while gzip may be preferable this shouldn't prevent the
lz4 fix from landing. It's a "good enough" workaround for a bug that
prevents people from running apt-upgrade (which is far more important
than "choice of compression algorithm").
--
You received this bug notification becaus
You have been subscribed to a public bug:
This started happening recently. Perhaps after a kernel update. I'm now
on Ubuntu 21.10, running kernel Linux 5.13.0-22-generic, on a Huawei
Matebook Pro X (2020).
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-co
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1954762
Title:
When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, o
Have been testing at 100% and 200% scaling - so far the problem hasn't
appeared at these scalings, which makes me suspect it is a problem with
fractional scaling. It's a new problem, as, about a month ago, there was
no such problem with the same fractional scaling - I have always
preferred 150% on
With fractional scaling at 150%, it occurs only after some time. On a
fresh reboot it isn't apparent, but it gradually gets worse when
manipulating text. It's as if some error accumulates with time. After a
while it becomes really annoying when working with text. The cursor
position is correct, but
Public bug reported:
When connected simultaneously to two different networks with overlapping domains
$ resolvectl domain
Global:
Link 3 (wlp0s20f3): ~. mit.edu
Link 2 (enp0s31f6): ~. psfc.mit.edu
$ resolvectl dns
Global:
Link 3 (wlp0s20f3): 18.0.70.160 18.0.72.3 18.0.71.151
Link 2 (enp0s31f6): 19
On 100% scaling it is certainly less noticeable, though the cursor
sometimes appears slightly moved to the right of where it actually is.
The screen resolution I am using is (and always has been) 3000x2000.
Maybe it has something to do with this less common screen ratio.
--
You received this bug
Does this also need fixing in impish? I'm not very concerned about
hirsute given it will be EoL in January.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/19501
Test result on Focal (245.4-4ubuntu3.14):
- Normal environment: Tested on my desktop. timedatectl output is correct.
Setting the timezone works, and doesn't put the link inside /etc/writable/.
- System-image environment (UBports image): timedatectl output is correct.
Setting timezone works; readl
This bug was fixed in the package xorg-server -
2:1.20.13-1ubuntu1~20.04.2
---
xorg-server (2:1.20.13-1ubuntu1~20.04.2) focal-security; urgency=medium
* SECURITY UPDATE: SProcRenderCompositeGlyphs out-of-bounds access
- debian/patches/CVE-2021-4008.patch: check lengths in render
** Also affects: qtbase-opensource-src (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1950193
Title
Hello Robert, or anyone else affected,
Accepted qtbase-opensource-src into impish-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/qtbase-opensource-
src/5.15.2+dfsg-12ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by test
Hello Robert, or anyone else affected,
Accepted qtbase-opensource-src into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/qtbase-opensource-
src/5.12.8+dfsg-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testin
Public bug reported:
Hi,
my secondary display support 2560*1440 but 'Display' in Ubuntu is
presenting a max resolution of 2048*1080.
The max resolution was working yesterday, I think I performed a update
today and it has stopped working after that.
Thanks,
Jerry,
ProblemType: Bug
DistroRelease
** Tags added: champagne rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
Bluetooth headset not autoconnecting on power-on on 21.10
Status in b
I uploaded this after modifying the debian/changelog to reference the
bug number and running update-maintainer.
$ dput sed_4.8-1ubuntu1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/jammy/sed_4.8-1ubuntu1_source.changes: Valid signature from
1E9
Hello Matthias, or anyone else affected,
Accepted gdb into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gdb/9.2-0ubuntu1~20.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
The gdb upload looks fine; I presume it wants to be marked block-
proposed, though?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1927192
Title:
gdb ftbfs on armhf, testsuite
Thank you (especially for the direct link)!
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305
(btw: Would be nice, if ubuntu-bug or launchpad could propose upstream
reporting when trying to create an issue.)
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issu
You have been subscribed to a public bug:
Ubuntu 21.10 does not succeed at setting the display brightness after
booting (either to the GNOME login screen or to a logged-in user's
desktop). The brightness is at its highest level until I adjust it with
keyboard shortcuts or a GUI tool.
The systemd-
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1954843
Title:
amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
ALinuxUser, Xiaofan Chen's example was unbinding the usbhid driver via
the /sys/bus/usb/drivers/usbhid/unbind control file -- yours is using
/sys/bus/usb/drivers/usb/unbind instead. You probably have to use the
control file that corresponds to the driver your device is using. (Check
lsusb -t output
Thanks for the bug report. Which apps are affected?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xo
*** This bug is a duplicate of bug 1901470 ***
https://bugs.launchpad.net/bugs/1901470
The EDID data reported by the monitor (decoded from XorgLog.txt)
mentions the correct resolution:
EDID version: 1.3
Manufacturer: DEL Model 16619 Serial Number 842152019
Made in week 32 of 2017
Digital disp
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1954843
Title:
amdgpu_bl0: Fai
For Latitude 7520, BIOS 1.7.1 should fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1944409
Title:
Systemd uses CPU after wakeup due to power_supply BAT0 (
53 matches
Mail list logo
