I have filed an upstream bug since this seems to be going nowhere
currently https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7626
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7626
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7626
** Also affects: gnome-shell via
** No longer affects: linux
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
Status in Plymouth:
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #32509
https://github.com/systemd/systemd/issues/32509
** Also affects: systemd via
https://github.com/systemd/systemd/issues/32509
Importance: Unknown
Upstream QT bugtracker url (can't add to launchpad because it doesn't
recognize the format) https://bugreports.qt.io/browse/QTBUG-94871
** Also affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New =>
Upstream MR in gnome-shell to partially fix this
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3283
** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues
#515
https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/515
** Also affects:
Seems like a racecondition of some sort. I tried a few days ago with no
issue.
This seems to be a long running bug, not something new since its been reported
in other places.
https://ubuntuforums.org/archive/index.php/t-2391820.html
** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues
#514
https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/514
** Also affects: gnome-shell-extension-appindicator via
https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/514
** Bug watch added: github.com/sddm/sddm/issues #1917
https://github.com/sddm/sddm/issues/1917
** Also affects: sddm via
https://github.com/sddm/sddm/issues/1917
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
AMD kernel developer wants to classify this is as both SDDM bug and
plymouth bug https://gitlab.freedesktop.org/drm/amd/-/issues/3341.
amdgpu kernel driver is not ready by the time that sddm and plymouth are
started in some cases (race condition). Marking this as a sddm and
plymouth bug (in
Adding Julian Andres Klode as a subscriber as seemingly this could only
be due to the recent package update from aspell
https://changelogs.ubuntu.com/changelogs/pool/main/a/aspell/aspell_0.60.8.1-1build1/changelog
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Hardware: AMD Framework 13
OS: Ubuntu Noble 24.04
DE: Plasma Wayland
BIOS: version 3.03 and 3.05 (latest new release)
Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux
This issue started about 2-3 weeks ago I
the attached info above are from the ARM64 tablet
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2063005
Title:
Some shell elements don't respond to touchscreen in Xorg sessions
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768767/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768766/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768765/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768764/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Tags added: third-party-packages
** Description changed:
Starting in GNOME 46 touchscreen input on the X11 session has become
unusable
the touchscreen is responsive on the desktop itself (moving the cursor)
but does not interact with most things
on GNOME 46
I've confirmed the issue on multiple devices with touchscreen now
(x86_64 laptop with touchscreen and an ARM64 tablet with touchscreen)
The attached info above is from the x86_64 laptop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768762/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768761/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768760/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/2063005/+attachment/5768759/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Starting in GNOME 46 touchscreen input on the X11 session has become
unusable
the touchscreen is responsive on the desktop itself (moving the cursor)
but does not interact with most things
on GNOME 46 on
** Description changed:
Starting in GNOME 46 touchscreen input on the X11 session has become
unusable
- the touchscreen is responsive and on the desktop itself (moving the
- cursor) but does not interact with most things
+ the touchscreen is responsive on the desktop itself (moving the
** Description changed:
Starting in GNOME 46 touchscreen input on the X11 session has become
unusable
the touchscreen is responsive and on the desktop itself (moving the
cursor) but does not interact with most things
on GNOME 46 on the current version of Ubuntu Noble, touch input
Public bug reported:
Starting in GNOME 46 touchscreen input on the X11 session has become
unusable
the touchscreen is responsive and on the desktop itself (moving the
cursor) but does not interact with most things
on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work
Hopefully this can also be reverted or added in a separate package
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1992498
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
** Description changed:
+ this is running with LC_ALL=C
+
+ the following are output in terminal when configuring dictionaries-
+ common
+
Setting up dictionaries-common (1.29.7) ...
Processing triggers for dictionaries-common (1.29.7) ...
aspell-autobuildhash: processing: en [en-common].
Public bug reported:
Setting up dictionaries-common (1.29.7) ...
Processing triggers for dictionaries-common (1.29.7) ...
aspell-autobuildhash: processing: en [en-common].
Error: /dev/null:1: The key "/usr/bin/aspell" is unknown.
Undefined subroutine ::subst called at
Public bug reported:
In ubuntu jammy and previous releases, right clicking on appindicator
icons brings up the menu below the appindicator with appropriate gnome
theming. In ubuntu noble, right clicking on some appindicator icons
(example: barrier) results in the menu appearing on the left side
Public bug reported:
In ubuntu jammy and previous releases, set_label can be used to set the text to
display instead of an appindicator icon. In ubuntu noble set_label no longer
functions at all.
https://gjs-docs.gnome.org/appindicator301~0.1/appindicator3.indicator#method-set_label
**
this might be the same as the reported upstream issue in mutter
https://gitlab.gnome.org/GNOME/mutter/-/issues/3134
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3134
https://gitlab.gnome.org/GNOME/mutter/-/issues/3134
--
You received this bug notification because you are a
I tested all of these:
* gnome-extensions disable tiling-assist...@ubuntu.com
* gnome-extensions disable ubuntu-appindicat...@ubuntu.com
* gnome-extensions disable d...@rastersoft.com
* gnome-extensions disable ubuntu-d...@ubuntu.com
and then had no effect on the performance on noble (yes
Sorry I missed the replies in my email
I will test disabling the extensions later
I can confirm that these are the same (because I use the same custom
kernel and GL/Vulkan/EGL/GLES driverstack):
* lspci -k # to see if the kernel driver changed
* es2_info | grep ^GL_ # to see if the GL driver
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2052913
Title:
Large Performance Regression in
** Description changed:
- Test system: ARM64 Ubuntu Jammy and Ubuntu Noble
+ Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble
(gnome-shell 45.3-1ubuntu1)
Default Ubuntu GNOME desktop environment used with no user added extensions.
GPU driverstack identical
Public bug reported:
Test system: ARM64 Ubuntu Jammy and Ubuntu Noble
Default Ubuntu GNOME desktop environment used with no user added extensions.
GPU driverstack identical between the two distros (eliminated as a variable).
Linux kernel identical between distros (eliminated as a variable)
CPU,
** Also affects: gtk4 (Fedora)
Importance: Undecided
Status: New
** Also affects: gtk4 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
Public bug reported:
https://gitlab.gnome.org/GNOME/gtk/-/issues/5610
cross posting this here since it affects the majority of Ubuntu's UI
applications in Ubuntu Noble (eg: settings) and is perceived as a
regression by users from Ubuntu Jammy where the majority of applications
are GTK3 based.
Found a rouge service (not from the ubuntu distro but instead my custom
nvidia tegra BSP) that had the `/usr/lib/bluetooth/bluetoothd` path in
it.
Closing as removing or altering that service fixes it.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug
Public bug reported:
Release: Ubuntu Noble Dev Branch
the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd
this causes bluetooth to fail to start since something is still looking
for the old location
Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service -
Public bug reported:
Firefox armhf and arm64 have been failing to build on 18.04 and 20.04 on
mozillateam/ppa for the past couple of weeks.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
"This is ok for Ubuntu"
This is no OK for Ubuntu and is perceived as a regression for users
(like myself and many others) that use gnome-software as a one stop shop
for managing installation and updates of debs, snaps, and flatpaks. With
this patch added now we have to use a separate software to
working as intended according to google
https://bugs.chromium.org/p/chromium/issues/detail?id=1500114
this can be closed I guess
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
Certain websites use the user agent architecture string to determine
what download link to show/serve to users on their websites. Having it
as x86_64 will cause these websites to give the wrong link.
When it comes to the YouTube playback issue, I think fixing this
behavior is a bit of a catch-22
** Description changed:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent is expected to contain the string aarch64 however
it contains the string x86_64. I am not aware if i386
** Description changed:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent should contain the string aarch64 however it
contains the string x86_64. Many websites use the user
Public bug reported:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent should contain the string aarch64 however it
contains the string x86_64. Many websites use the user agent to
I can confirm the be build from the ppa works on arm64. Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2008433
Title:
Request to enable WidevineCDM checking on
ae you able to put it in the ubuntu bionic beta chromium ppa? I can't
really test the snap due to kernel incompatibility.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2008433
just to note, this patch replaces the cdm_registration.cc changes from
widevine-enable-version-string.patch but you still need the changes to
widevine_cdm_version.h from that patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
widevine isn't supplied with the chromium deb on linux amd64. you are
misinterpreting what the flag does. if bundled is not set, then you hit this
case always and widevine is never checked
Public bug reported:
If possible, could you please include a patch to enable widevinecdm
checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get set
for arm64 linux (but does on amd64 linux) so chromium does not even
check for widevine even if we have it available and placed in the
Public bug reported:
Firstly I want to note that this is not a Jammy specific bug. I have
used ubuntu focal, and impish and note it there as well (it may exist on
older releases, I have not tested).
When using multiple monitors with the Xorg backend, scaling does not
work properly. I have a 4K
Public bug reported:
I perform apt update/upgrades almost daily on my system and today I
update/upgraded (mesa, gdm3, and gnome shell among other packages were
upgrade since my last upgrade on the 12th).
All wayland options have disappeared from my gdm3 login menu. I have
tried manually setting
55 matches
Mail list logo
