This bug was fixed in the package xorg-server - 2:21.1.7-1ubuntu2
---
xorg-server (2:21.1.7-1ubuntu2) lunar; urgency=medium
* patches: Force update LEDs after device state update. (LP: #1993621)
-- Timo Aaltonen Tue, 21 Feb 2023 17:08:20 +0200
** Changed in: xorg-server (Ubuntu
This issue is verified on 2:21.1.3-2ubuntu2.8 on jammy, that switching
from text terminal to X session the keyboard LED status would recover.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Deskto
Public bug reported:
[Impact]
* LibreOffice 7.4.6 is in its sixth bugfix release of the 7.4 line:
https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.6_release
* Version 7.4.4/7.4.5 is currently released in kinetic. For a list of fixed
bugs compared to 7.4.5 see the list of bugs fixe
Public bug reported:
Errors were encountered while processing:
/tmp/apt-dpkg-install-HAFmYr/20-libgl1-mesa-dri_22.3.6-1ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgl1-mesa-dri 22.2.5-0ubuntu1
ProcVersionSi
All autopkgtests for the newly accepted pulseaudio (1:16.1+dfsg1-1ubuntu3.1)
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
openjdk-8/8u362-ga-0ubuntu1~22.10 (amd64)
Please visit the excuses page listed below and investigate th
Changed the bug importance of oem-priority to Critical, since it impacts
the user experience on Wayland and failed on Ubuntu Desktop
certification requirement.
** Changed in: oem-priority
Importance: Wishlist => Critical
--
You received this bug notification because you are a member of Deskto
*** This bug is a duplicate of bug 2008613 ***
https://bugs.launchpad.net/bugs/2008613
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #2008613, so is being marked as such.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bu
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bu
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19
(5.19.0-1022.23~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excu
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19
(5.19.0-1021.22~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuse
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.19.0-1021.22) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page list
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.19.0-1022.23) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page li
This bug was fixed in the package mesa - 22.3.6-1ubuntu1
---
mesa (22.3.6-1ubuntu1) lunar; urgency=medium
* Merge from Debian.
* rules: Drop i386 from RUSTICL_ARCHS.
mesa (22.3.6-1) unstable; urgency=medium
* New upstream release. (Closes: #1029731)
mesa (22.3.5-1) unstable;
Public bug reported:
Currently — if fonts-noto-core and fonts-noto-ui-core are installed —
fontconfig picks Noto Sans Arabic UI as the default sans-serif font for
Arabic, but only under an Arabic locale. The latter is to avoid a change
of the default sans-serif font (from DejaVu to Noto) for most
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave fil
Hi!
I just found this bug report.
I use a clean installed 22.04 (not upgraded from 20.04) and a clean setup of
Evolution (no config was copied from an earlier release) and I do experience
this issue, it's pretty straightforward to reproduce, i.e. every time a
composed email is saved into an auto
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxau in Ubuntu.
https://bugs.launchpad.net/bugs/2009301
Title:
package libxau-dev:amd64 1:1.0.9-1build5 failed to install/upgrade:
package is in
miguelquiros, can we mark this as verified?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Release
Public bug reported:
this is the fifth time it happens after few days of installing linux
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libxau-dev:amd64 1:1.0.9-1build5
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
ApportVersio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evolution (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad
All autopkgtests for the newly accepted xorg-server (2:21.1.3-2ubuntu2.8) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
libaperture-0/0.1.0+git20200908-3 (ppc64el)
aptdaemon/1.1.1+bzr982-0ubuntu39 (amd64)
notify-osd/0.9.35+20.04.2
Yes, this affects me too. It was working before the upgrade. I was
involved with the addition to libwacom that made it work previously, and
I suspect problems with that, where it identifies something not quite
correctly, probably the stylus, which seems to work as the mouse instead
of the stylus
All autopkgtests for the newly accepted xorg-server (2:21.1.4-2ubuntu1.6) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
gnudatalanguage/1.0.1-3maysync1 (amd64)
libsoup3
Public bug reported:
Não consigo faze com que minha placa amd radeon seja reconhecida pelo
Ubuntu. Com isso o Davinci Resolve não funciona
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19
Snap info chromium package
** Attachment added: "Snap info chromium package"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2009285/+attachment/5651689/+files/snap_info_chromium.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is
syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2009285/+attachment/5651690/+files/syslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bu
Public bug reported:
Chromium does not start for other users. I have two admin user accounts
on my Ubuntu. Chromium works as expected for the "first" user, but does
not start in the second user account.
[Expected behavior]
Chromium to start/work for all users.
[What is happening]
Chromium does n
Up.
GEdit 3.38.1
Looks like some Gnome theme are incompatible with the cursor visibility.
Theme "Adwaita-dark"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1876883
Title:
The positio
30 matches
Mail list logo
