Daniel, a user has bisected and confirmed the bug in mutter (see linked
bug report). I have removed the affects from gnome-shell because of
this.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3484
https://gitlab.gnome.org/GNOME/mutter/-/issues/3484
** Also affects: mutter via
fixed the bug and opened a merge request upstream
https://gitlab.freedesktop.org/xorg/driver/xf86-input-
joystick/-/merge_requests/5
** Summary changed:
- QT Applications don't respond to virtual keyboard and wacom mouse wheel events
+ QT Applications don't respond to xf86-input-joystick virtual
Public bug reported:
scroll wheel events generated from the xorg joystick input driver and
wacom mouse wheel are working in non qt5 application (eg: gtk), but not
in qt5 (so all kde plasma5) applications.
This is a long reported upstream QT5 regression (it worked in QT4) and I
am reporting it
Public bug reported:
Attempting to change the language in system settings to anything other
than the default configured language on a fresh install results in the
banner "Failed to install package Failed to obtain authentication.".
There is no popup asking for authentication and rebooting
Public bug reported:
When run on a ubuntu-base image (currently testing ubuntu noble arm64
base images), the following query results in an error
dpkg --verify --verify-format rpm | awk '$2 ~ /\/usr\/share\/locale/ {print
$2}' | sed 's|/[^/]*$||' | sort | uniq \
| xargs
I have added the last 3 maintainers of this package to the thread as
they do not seem to have been previously notified (Steve Langasek,
Jeremy Bícha, and Brian Murray).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It would be great if this issue would be fixed in the current LTS
(Ubuntu Noble).
This arbitrary and needless conflict prevents installation of pipewire
even though all dependencies of the meta package are compatible with
pipewire.
--
You received this bug notification because you are a member
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
Can we get the upstream commmit that fixes unencrypted 7z support
backported please? https://bugs.kde.org/show_bug.cgi?id=468240#c13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051041
Title:
** No longer affects: linux
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
To manage notifications about this bug
** 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
** Changed in: sddm (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/2063143
Title:
Frequent boot to black display
To manage notifications about this bug go
** 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
Does not seem fully fixed as I am still seeing the comments. Unless this
is expected functionality. See
https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/2061214/comments/17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I do not think the GTK version is fixed.
I am seeing the issue as seen in the screenshot.
Tell me to open a new bug if needed.
`sources.list`
```
# Ubuntu sources have moved to the /etc/apt/sources.list.d/ubuntu.sources
# file, which uses the deb822 format. Use deb822-formatted .sources files
#
here is i915 with a successfull boot. the i915 driver finishes starting
before sddm starts.
** Attachment added: "i915-successfull-boot.txt"
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770119/+files/i915-successfull-boot.txt
--
You received this bug notification because you
here is i915 failed to boot in the same way. you can see the i915 kernel
driver does not finish until much after sddm starts
** Attachment added: "i915-fail-boot.txt"
https://bugs.launchpad.net/sddm/+bug/2063143/+attachment/5770118/+files/i915-fail-boot.txt
--
You received this bug
I am hitting this on i915 as well with the same 50-75% frequency.
I think this need to be upgraded to critical status (at least for non
GDM login managers where no mitigation exists) and potentially release
blocker depending on how widespread this issue is.
Devices I have confirmed affected by
** 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 Ubuntu
Bugs,
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
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3341
https://gitlab.freedesktop.org/drm/amd/-/issues/3341
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/3341
Importance: Unknown
Status: Unknown
--
You received this bug notification
this issue has appeared before on other AMD hardware but was closed due
to lack of activity and driver changes. my issue shows that it has re-
appeared on new hardware and drivers
https://gitlab.freedesktop.org/drm/amd/-/issues/1256
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues
Going to change this back to linux as the plymouth failing to display
indicates an issues with KMS (plymouth uses KMS to display graphics on
earlyboot which is what is happening here). The bootlogo from plymouth
always shows (even for a very brief time) when SDDM starts and when it
boots to a
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 Ubuntu
Bugs,
Here is my current boot journalctl (where booting to a desktop
succeeded) for comparison incase it helps.
I will also note that on the boot to black screen I never see any
plymouth bootlogos or messages. The screen remains black after grub
(with only backlight level changing). When I get a
Attached is the journalctl as instructed. I tried to power it off by
short pressing the power button a few times (as you can see in the log
at the end) while black screened but wasn't able to do that so hard to
force power off.
There are no logs in /var/crash/
** Attachment added: "preboot.txt"
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
to fix this, I first pulled the latest debian changes, then applied this
additional patch https://github.com/Azkali/onboard-
keyman/commit/ac8633670a5467e7b7364651e77be2c94f7e3104.patch and also
set LC_ALL=en_US.UTF-8 in the debian rules for the tests so that the
tests would pass.
--
You
Public bug reported:
A number of functions were removed after their deprecation period ended in
python3.12 from python3.11.
These removals cause onboard to crash immediately when pressing a key.
** Affects: onboard (Ubuntu)
Importance: Undecided
Status: New
--
You received this
the attached info above are from the ARM64 tablet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063005
Title:
Some shell elements don't respond to touchscreen in Xorg sessions
To manage
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056767
Title:
** 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, 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
**
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
Anyone looking into this? I get this a few times a week especially with
multiple chromium based applications open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057155
Title:
amdgpu driver crashes
** Attachment added: "look_at_this_journalctl_from_previous_boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+attachment/5754997/+files/look_at_this_journalctl_from_previous_boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* Process information: process armcord pid 14844
Public bug reported:
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic
#11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64
x86_64 x86_64 GNU/Linux
Hardware: AMD Framework 13
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052913
Title:
Large Performance Regression in gnome-shell from Ubuntu
Hi there needs to be a way to disable this by default out of the box.
enabling ESM has the tendency to break systems that use multiarch where one
architecture is not supported via ESM (eg: ARM64 with ARMhf multiarch where ESM
only supports ARM64)
--
You received this bug notification because
there are a few usecases where pi users wish to install the armhf
variants in addition to the arm64 variants:
1. use armhf only binary software with hardware accelerated gles (and
other gpu libraries). The arm64 libraries do not help in this case.
2. for x86 (32bit) to armhf emulation of linux
can we get this backported to swig for bionic? should be as simple as
adding the patchfile I linked above
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966617
Title:
Request to backport Fix for
I can give some extra insight. the problem is with attempting to install
the libraspberrypi0:armhf dependency in addition which users might want
to do in a multiarch arm64 and armhf scenario.
The problem is that both the armhf and arm64 package contain the
Public bug reported:
Using KDE plasma on 22.04, sddm fails to start very frequently (maybe
once our of every 5 times it fails). the output from the sddm service
when it fails is seen below. I can restart the service and then it
works.
```
● sddm.service - Simple Desktop Display Manager
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
over a year and this bug is still unfixed. @c.schoen...@t-online.de
please take a look at fixing your package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916278
Title:
Arduino fails to start:
Public bug reported:
https://github.com/swig/swig/pull/1587/files
this is a simple change to the swig source that fixed autogenerated files when
used with python3.8.
Ubuntu bionic has python 3.8 (in addition to 3.6 and 3.8) and causes errors
when swig with it installed.
The
Public bug reported:
Some videos may not play on all versions of vlc in ubuntu repos (all
3.0.X versions which is currently used in all currently supported ubuntu
releases)
Upstream VLC 4.0.X has fixed this with
70 matches
Mail list logo
