** 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-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1954843
Title:
a
*** 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
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-X,
which is subscribed to xorg in Ubuntu.
https:
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1954843
Title:
amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
argument
To manage
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-
Also, restarting i2c_hid_acpi usually makes the touchpad work again,
although for some reason it disables natural scrolling. Additionally,
restarting that module sometimes only makes the touchpad detected as a
mouse so touchpad-specific functions dont work.
--
You received this bug notification b
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
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
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
An upload of xfwm4 to focal-proposed has been rejected from the upload
queue for the following reason: "This is a mircorelease update of xfwm4
that doesn't follow the policy.".
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-am
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
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
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
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1954762
Title:
When selecting or navigating text with CTRL + LEFT ARROW or RIGHT, or
even just mouse
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
Hi timo,
Do you know when these xorg packages are in updates channel? We need
this fix in our OEM project next week. Thanks!
--
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/1947820
Title:
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
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
27 matches
Mail list logo
