[Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
The user environment is not copied over to the sudo environment (by default except with -E is passed or an override is added). What is likely happening is apt itself (or another debian maintainer script) is setting the errors variable before the python3 postinst script runs. Causing the error and entirely out of control of the user. The issue I found should be fixed asap. It is the only way for the script to exit without actually detecting any errors (is: without any "error running python pre-rtupdate hook" output) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
I found the bug. It is with this line [ -z "$errors" ] || exit 3 debian package maintainer scripts do not have their environment sanitized. So if the (root) user has a variable "errors" set in their environment (for whatever reason, maybe even apt set it) the postinst will error. 100% reproduction usecase sudo errors=hi apt install --reinstall python3 Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 23.0 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 python3 amd64 3.12.3-0ubuntu2 [23.0 kB] Fetched 23.0 kB in 0s (56.4 kB/s) (Reading database ... 601985 files and directories currently installed.) Preparing to unpack .../python3_3.12.3-0ubuntu2_amd64.deb ... running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 Errors were encountered while processing: /var/cache/apt/archives/python3_3.12.3-0ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Changed in: python3-defaults (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078356] Re: python3 preinst failure to run pre-rtupdate hooks
Still seeing this issue reported on user error reports. If you look at the log you will see this is a first time python3.10 install (not an upgrade). So this can occur on new installs and upgrades. ** Attachment added: "install-fail-AndroidBuddy.txt" https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+attachment/5816248/+files/install-fail-AndroidBuddy.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 preinst failure to run pre-rtupdate hooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
No know workaround other than using another desktop environment that doesn't use mutter (such as KDE plasma). -- 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 notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078356] Re: python3 upgrade has unmet dependencies
Seems related to https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078489 Why were these bugs filed separately? Seeing the linked issue reported via multiple users on varying hardware. Please drop `3.12.3-0ubuntu2` python3 packages from the repo to prevent further breakage of users systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078356 Title: python3 upgrade has unmet dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078489] Re: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3
CRITICAL regression I am seeing these errors reported on Ubuntu 22.04 and Ubuntu 24.04 as of 8/27/2024 from different users on various hardware 22.04: running python pre-rtupdate hooks for python3.10... dpkg: error processing archive /tmp/apt-dpkg-install- sHFfYL/00-python3_3.10.6-1~22.04.1_arm64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 24.04: running python pre-rtupdate hooks for python3.12... dpkg: error processing archive /tmp/apt-dpkg-install- tNib4c/00-python3_3.12.3-0ubuntu2_arm64.deb (--unpack): new python3 package pre-installation script subprocess returned error exit status 3 ** Changed in: python3-defaults (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/2078489 Title: package python3 3.12.3-0ubuntu1 failed to install/upgrade: new python3 package pre-installation script subprocess returned error exit status 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2078489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057155] Re: amdgpu driver crashes running electron application after some time
Here is a new log incase it helps. ** Attachment added: "7-31-2024-journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+attachment/5801602/+files/7-31-2024-journalctl.log -- 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 running electron application after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057155] Re: amdgpu driver crashes running electron application after some time
Months later I still observe this issue. Maybe firmware related? -- 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 running electron application after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: sddm/simpledrm race conditions leads to frequent black display on bootup
Bug https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275 was filed two months later and went unknown to me until I read the recent sddm ubuntu 24.04 package release notes. As mentioned by Brian I have no clue why a new report was filed https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275/comments/4 This issue is potentially fixed by the recent package updates. Please test everyone that was having issues. -- 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: sddm/simpledrm race conditions leads to frequent black display on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066275] Re: [SRU] Fix black screen on second boot due to video drivers not being ready.
*** This bug is a duplicate of bug 2063143 *** https://bugs.launchpad.net/bugs/2063143 ** This bug has been marked a duplicate of bug 2063143 sddm/simpledrm race conditions leads to frequent black display on bootup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066275 Title: [SRU] Fix black screen on second boot due to video drivers not being ready. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069926] [NEW] OBS-Studio Entirely broken on Ubuntu Noble (wrong dynamic linked libraries)
Public bug reported: obs studio has entirely wrong dynamic linked libraries in the version for ubuntu noble here is a truncated snippit of ldd directly from the binary in the noble deb libavcodec.so.60 => /lib/x86_64-linux-gnu/libavcodec.so.60 (0x7c3a3180) libavutil.so.58 => /lib/x86_64-linux-gnu/libavutil.so.58 (0x7c3a3060) libavformat.so.60 => /lib/x86_64-linux-gnu/libavformat.so.60 (0x7c3a3020) ... libavcodec.so.58 => not found libavformat.so.58 => not found libavutil.so.56 => not found libswscale.so.5 => not found libswresample.so.3 => not found Description:Ubuntu 24.04 LTS Release:24.04 Package version: 30.0.2+dfsg-3build1 ** Affects: obs-studio (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/2069926 Title: OBS-Studio Entirely broken on Ubuntu Noble (wrong dynamic linked libraries) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2069926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049315] Re: cups-browsed running non-stop on two cores
I frequently get 100% cups-browsed should I open a separate report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049315 Title: cups-browsed running non-stop on two cores To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)
@Sandeep I gave a summary of the problems currently experienced in January and the things that need to be done to fix them (I am just a user). You can work on them instead of waiting on ubuntu developers. https://forums.developer.nvidia.com/t/chromium-electron-applications-hang-on-launch-on-gnome-wayland/276978/12?u=theofficialgman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2028864 Title: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067328] [NEW] plymouth not closing virtual terminal properly (regression)
Public bug reported: Login managers cannot take control from Plymouth on Ubuntu noble likely on systems where simpledrm is not enabled or available in the kernel. See the upstream bug report for more detail. https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/254 ** Affects: plymouth Importance: Unknown Status: Unknown ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #254 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/254 ** Also affects: plymouth via https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/254 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067328 Title: plymouth not closing virtual terminal properly (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2067328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows
I imagine the removal of this "feature" probably makes it harder to test as well https://gitlab.gnome.org/GNOME/mutter/-/commit/184055b2bb7119566cada1eb632a5ab9471fe558 previously (mutter <= 43.0) you could set the _NET_WM_BYPASS_COMPOSITOR = 1 hint in your application and that would tell mutter to unredirect always. -- 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: [Xorg] Large performance regression in fullscreen windows To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2052913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 https://gitlab.gnome.org/GNOME/mutter/-/issues/3484 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell ** No longer affects: gnome-shell (Ubuntu) -- 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 notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065512] Re: QT Applications don't respond to xf86-input-joystick virtual keyboard wheel events
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 keyboard wheel events ** Description changed: - 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 here to see if others are running into this issue in - their use cases. - - Affects all QT5 versions (and likely QT6 though I have not checked). - - Upstream bug report: https://bugreports.qt.io/browse/QTBUG-47727 + scroll wheel events generated from the xorg joystick input driver mouse + wheel are working in non qt5 application (eg: gtk), but not in qt5 (so + all kde plasma5) applications. ** Package changed: qtbase-opensource-src (Ubuntu) => xserver-xorg- input-joystick (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065512 Title: QT Applications don't respond to xf86-input-joystick virtual keyboard wheel events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-joystick/+bug/2065512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065512] [NEW] QT Applications don't respond to virtual keyboard and wacom mouse wheel events
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 here to see if others are running into this issue in their use cases. Affects all QT5 versions (and likely QT6 though I have not checked). Upstream bug report: https://bugreports.qt.io/browse/QTBUG-47727 ** Affects: qtbase-opensource-src (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/2065512 Title: QT Applications don't respond to virtual keyboard and wacom mouse wheel events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2065512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065504] [NEW] KDE System Settings Language Modification Fails
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 afterwards results in most language being unchanged. ** Affects: systemsettings (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/2065504 Title: KDE System Settings Language Modification Fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/2065504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065497] [NEW] local restore fails (non-fatal) when run on ubuntu-base noble arm64 image
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 --no-run-if-empty dpkg -S | sed 's|, |\n|g;s|: [^:]*$||' |
uniq | DEBIAN_FRONTEND=noninteractive xargs --no-run-if-empty apt-get install
--reinstall -y
terminal output
Restoring system translations...
dpkg-query: error: --search needs at least one file name pattern argument
Use --help for help about querying packages.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Documentation has been restored successfully.
I have run the command manually after and do not get the same error I am
not sure why it is happening within the script but it is repeatable.
** Affects: unminimize (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/2065497
Title:
local restore fails (non-fatal) when run on ubuntu-base noble arm64
image
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unminimize/+bug/2065497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999480] Re: ubuntu-unity-desktop metapackage requires pulseaudio
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. https://bugs.launchpad.net/bugs/1999480 Title: ubuntu-unity-desktop metapackage requires pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1999480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999480] Re: ubuntu-unity-desktop metapackage requires pulseaudio
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999480 Title: ubuntu-unity-desktop metapackage requires pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1999480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7626 Importance: Unknown Status: Unknown -- 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 notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051041] Re: Regression: Ark unable to extract or view 7z after p7zip to 7zip transition in noble
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: Regression: Ark unable to extract or view 7z after p7zip to 7zip transition in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/7zip/+bug/2051041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
** 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 go to: https://bugs.launchpad.net/plymouth/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
** 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 Status: Unknown -- 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
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 => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
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: gnome-shell-extension-appindicator via https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/515 Importance: Unknown Status: Unknown ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (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/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
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 https://forums.freebsd.org/threads/linuxulator-switching-to-non-root-user-in-the-chroot-to-run-davinci-resolve.92234/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
** 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
** 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 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060915] Re: Comments in source files flood "other software"
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 Ubuntu. https://bugs.launchpad.net/bugs/2060915 Title: Comments in source files flood "other software" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
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 # to manage package sources in the /etc/apt/sources.list.d/ directory. # See the sources.list(5) manual page for details. ``` `ubuntu.sources` ``` ``` # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. ## Ubuntu distribution repository ## ## The following settings can be adjusted to configure which packages to use from Ubuntu. ## Mirror your choices (except for URIs and Suites) in the security section below to ## ensure timely security updates. ## ## Types: Append deb-src to enable the fetching of source package. ## URIs: A URL to the repository (you may add multiple URLs) ## Suites: The following additional suites can be configured ## -updates - Major bug fix updates produced after the final release of the ## distribution. ## -backports - software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. ## Components: Aside from main, the following components can be added to the list ## restricted - Software that may not be under a free license, or protected by patents. ## universe- Community maintained packages. ## Software from this repository is only maintained and supported by Canonical ## for machines with Ubuntu Pro subscriptions. Without Ubuntu Pro, the Ubuntu ## community provides best-effort security maintenance. ## multiverse - Community maintained of restricted. Software from this repository is ## ENTIRELY UNSUPPORTED by the Ubuntu team, and may not be under a free ## licence. Please satisfy yourself as to your rights to use the software. ## Also, please note that software in multiverse WILL NOT receive any ## review or updates from the Ubuntu security team. ## ## See the sources.list(5) manual page for further settings. Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports/ Suites: noble noble-updates noble-backports Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg ## Ubuntu security updates. Aside from URIs and Suites, ## this should mirror your choices in the previous section. Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports/ Suites: noble-security Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg ``` ** Attachment added: "Screenshot from 2024-04-24 23-18-46.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+attachment/5770144/+files/Screenshot%20from%202024-04-24%2023-18-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 this: AMD Framework 13 HP Spectre X360 -- 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 addition to linux) because of this. To me it seems that at least a systemd service should be handling blocking starting GUI userspace services until the kernel drivers are actually loaded but that is just my thought. I guess the AMD developer sees this the same way you do Daniel. ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** No longer affects: plymouth (Ubuntu) ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #253 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/253 ** Also affects: plymouth via https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/253 Importance: Unknown Status: Unknown -- 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
** 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 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 to: https://bugs.launchpad.net/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 #1256 https://gitlab.freedesktop.org/drm/amd/-/issues/1256 -- 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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 black screen the bootlog NEVER shows from plymouth. Using your reasoning of the race condition I should see the bootlogo at least sometimes in the boot to black screen but this has never happened (I have booted dozens of times to black screen and have always never seen the bootlogo). I do not think this has anything to do with sddm. If KMS is not working then of course everything else that relies on it later in the bootstack will also fail. The Ubuntu default drivers are in use. ** Package changed: sddm (Ubuntu) => 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 go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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 successful boot I see the plymouth bootlogos and messages and then get dropped to sddm login screen. ** Attachment added: "cuttent_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063143/+attachment/5769695/+files/cuttent_boot.txt -- 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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] Re: Frequent boot to black display
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063143/+attachment/5769694/+files/preboot.txt -- 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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063143] [NEW] Frequent boot to black display
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 believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze kubuntu noble ubuntu wayland-session ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (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 go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2063143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063041] Re: crashes immediately on pressing a key with python3.12 (Ubuntu Noble 24.04)
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063041 Title: crashes immediately on pressing a key with python3.12 (Ubuntu Noble 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/2063041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063041] [NEW] crashes immediately on pressing a key with python3.12 (Ubuntu Noble 24.04)
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063041 Title: crashes immediately on pressing a key with python3.12 (Ubuntu Noble 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/2063041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] monitors.xml.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] ShellJournal.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] GsettingsChanges.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu DisplayManager: sddm DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2021-06-21 (1035 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xorg-server PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 46.0-1ubuntu7 Tags: noble Uname: Linux 6.8.0-28-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-21 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu2 + Architecture: arm64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 24.04 + Package: xorg-server + PackageArchitecture: arm64 + ProcEnviron: + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + RelatedPackageVersions: mutter-common 46.0-1ubuntu7 + Tags: noble third-party-packages + Uname: Linux 4.9.140-l4t aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip gdm lpadmin plugdev sambashare sudo users video weston-launch + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2063005/+attachment/5768763/+files/Dependencies.txt -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] monitors.xml.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] ShellJournal.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] ProcCpuinfoMinimal.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] GsettingsChanges.txt
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. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
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 the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). - Tested on a fresh image as well as an old image from February running - GNOME 45 upgraded to the latest packages with GNOME 46 + Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu + DisplayManager: sddm + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2021-06-21 (1035 days ago) + InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + Package: xorg-server + PackageArchitecture: amd64 + ProcEnviron: + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: mutter-common 46.0-1ubuntu7 + Tags: noble + Uname: Linux 6.8.0-28-generic x86_64 + UpgradeStatus: Upgraded to noble on 2024-04-21 (0 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev render sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2063005/+attachment/5768758/+files/Dependencies.txt -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
** 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 cursor) + but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 -- 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: touchscreen input critical regressions in GNOME 45 to 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
** 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 does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - - iterating with application overview (cannot press left and right buttons or search bar) + - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) - - All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). + All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and + Ubuntu Noble from March and earlier before it was "upgraded" to GNOME + 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 -- 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: touchscreen input critical regressions in GNOME 45 to 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063005] [NEW] touchscreen input critical regressions in GNOME 45 to 46
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 with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 ** 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/2063005 Title: touchscreen input critical regressions in GNOME 45 to 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split
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: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
** 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]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine &main::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): - installed dictionaries-common package post-installation script subprocess returned error exit status 2 + installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: - dictionaries-common + dictionaries-common + + this worked without issues when I last built images of ubuntu-noble in + late February 2024 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062979] [NEW] unable to create ubuntu-noble image due to dictionaries-common config failure
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 &main::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common ** Affects: aspell (Ubuntu) Importance: Undecided Status: New ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Also affects: aspell (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/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059818] [NEW] Regression: Jammy to Noble, set_label no longer functions
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 ** Affects: gnome-shell-extension-appindicator (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/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059819] [NEW] Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
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 of the screen without proper theming. See attached image. ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2024-03-29_21-09.png" https://bugs.launchpad.net/bugs/2059819/+attachment/5760703/+files/2024-03-29_21-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2059819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057155] Re: amdgpu driver crashes running electron application after some time
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 running electron application after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057155] Re: amdgpu driver crashes running electron application after some time
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057155 Title: amdgpu driver crashes running electron application after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057155] [NEW] amdgpu driver crashes running electron application after some time
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 thread armcord:cs0 pid 14883 Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: GPU reset begin! Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110) Mar 11 18:30:07 garrett-desktop kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Mar 11 18:30:07 garrett-desktop kernel: amdgpu: cp is busy, skip halt cp Mar 11 18:30:07 garrett-desktop kernel: amdgpu: rlc is busy, skip halt rlc Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: BACO reset In KDE Wayland session, the screen freezes for a few seconds and then graphical corruption appears on screen. This issue did not happen in previous versions of ubuntu (mantic/jammy) that I have run previously. This appears to be a regresssion in the amdgpu kernel driver or mesa. I have attached a journalctl from the previous boot (any other logs that were auto-uploaded as part of this report are likely not relevant). It is named: look_at_this_journalctl_from_previous_boot.log ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Mar 11 18:35:54 2024 InstallationDate: Installed on 2022-03-16 (727 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c53f Logitech, Inc. USB Receiver Bus 001 Device 003: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI) Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Micro-Star International Co., Ltd. MS-7B48 ProcFB: 0 amdgpudrmfb 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=1bad4da7-3fac-4981-9976-490388955115 ro quiet splash amdgpu.ppfeaturemask=0x vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-01-22 (50 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.D3 dmi.board.asset.tag: Default string dmi.board.name: Z370-A PRO (MS-7B48) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.D3:bd11/18/2021:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B48:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370-APRO(MS-7B48):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B48 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- 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 running electron application after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056803] [NEW] amdgpu: hotplugging display sometimes fails
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 Expected: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) after boot does not fail every time What happened: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) frequently fails with either: - no outout - a white screen with only the mouse cursor visible - attempt enable and disable over and over again with dmesg log spam and KDE display configuration showing that the display arrangement changes every couple of seconds this problem is not observed on Windows 11 with the same hardware. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 11 16:59:30 2024 InstallationDate: Installed on 2023-11-16 (117 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-02-25 (16 days ago) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056803 Title: amdgpu: hotplugging display sometimes fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052913] Re: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052913 Title: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052913] Re: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
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 they did disable and I could see the visible changed in UI). I tried rebooting afterwards with no improvement. I did this: You can test that theory by comparing the windowed performance between jammy and noble. noble performance is about equal with a maximized window and fullscreen (140fps) jammy performance is a bit lower maximized window than fullscreen (162fps vs 177fps) but I see gnome-shell cpu usage at ~50% when when maximized window (vs 0-1% in fullscreen) so yeah definitely appears to be an issue with fullscreen direct scanout not working and additionally just gnome performance regresssions with windowed mode . -- 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 Jammy to Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052913] Re: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
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 changed I will not be able to do this because of no wayland support in the driverstack: Or by checking the scanout method using MUTTER_DEBUG=kms and grepping the log for "Post" (Wayland only though). I will check this later as well: You can test that theory by comparing the windowed performance between jammy and noble. -- 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 Jammy to Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052913] Re: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
** 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 Jammy to Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047778] Re: Software Updater unable to cancel Ubuntu Pro upgrade
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047778 Title: Software Updater unable to cancel Ubuntu Pro upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2047778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973285] Re: libraspberrypi0 multi-arch install failing due to lintian override content difference
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 applications/binaries, the armhf libraspberrypi0 package is also necessary for hardware accelerated gpu (as with 1.) 3. software such as chromium only has widevine support on armhf (and x86_64 and x86), not arm64, so the armhf version of chromium needs to be installs, requiring the armhf gpu libraries to be installed for hardware accelerated web compositing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973285 Title: libraspberrypi0 multi-arch install failing due to lintian override content difference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/1973285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966617] Re: Request to backport Fix for Swig when used with python 3.8+ https://github.com/swig/swig/pull/1587/files
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 Swig when used with python 3.8+ https://github.com/swig/swig/pull/1587/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swig/+bug/1966617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973285] Re: broken package on 22.04 libraspberrypi0
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 `/usr/share/lintian/overrides/libraspberrypi0` file. This files contents do not match on the armhf and arm64 package, causing apt to error saying that there is a conflicting file (which there is). The fix is to add the lintian overrides from armhf to arm64 and vice versa so the files match and update in all ubuntu releases, since its a problem on every release since the raspberrypi-userland package package was added (focal and up). the official raspbian/raspberrypi foundation packages do not have this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973285 Title: broken package on 22.04 libraspberrypi0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/1973285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971596] [NEW] SDDM fails to start frequently
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
Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset:
enabled)
Active: active (running) since Wed 2022-05-04 10:15:07 EDT; 1min 28s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Process: 760 ExecStartPre=/bin/sh -c [ "$(cat
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ]
(code=exited, status=0/SUCCESS)
Main PID: 766 (sddm)
Tasks: 2 (limit: 19008)
Memory: 10.7M
CPU: 74ms
CGroup: /system.slice/sddm.service
└─766 /usr/bin/sddm
May 04 10:15:07 garrett-desktop sddm[766]: Initializing...
May 04 10:15:07 garrett-desktop sddm[766]: Starting...
May 04 10:15:07 garrett-desktop sddm[766]: Logind interface found
May 04 10:15:07 garrett-desktop sddm[766]: Adding new display on vt 1 ...
May 04 10:15:07 garrett-desktop sddm[766]: Loading theme configuration from ""
May 04 10:15:07 garrett-desktop sddm[766]: Display server starting...
May 04 10:15:07 garrett-desktop sddm[766]: Adding cookie to
"/var/run/sddm/{078496a5-c054-4286-a48d-f76fa1eaa271}"
May 04 10:15:07 garrett-desktop sddm[766]: Running: /usr/bin/X -nolisten tcp
-auth /var/run/sddm/{078496a5-c054-4286-a48d-f76fa1eaa271} -background none
-noreset -displayfd 17 -seat seat0 vt1
May 04 10:15:08 garrett-desktop sddm[766]: Failed to read display number from
pipe
May 04 10:15:08 garrett-desktop sddm[766]: Could not start Display server on vt
1
```
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: sddm 0.19.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed May 4 10:17:19 2022
InstallationDate: Installed on 2022-03-16 (49 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: sddm
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: sddm (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971596
Title:
SDDM fails to start frequently
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1971596/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969256] [NEW] Dual Monitors on Xorg with Scaling is Broken
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 27in monitor (on the right) and a 1080p 21.5in monitor (on the left). I would like to scale my 4K monitor to 150% and leave the 1080p monitor at 100%. Doing this works correctly in wayland. However, doing this is gnome (through the gnome settings display dialog) produces the wrong outcome. Setting the 4K monitor to 150% scales BOTH the 4K display (right) and the other 1080p display (left). the 1080p display scaling should not change as per the gui but it does and cuts of the viewable area. I have attached before scaling and after scaling images to this to help show what is happening. I realize this may not be a gdm3 bug, please assist in moving this bug to the correct location as necessary. xrandr output for before scaling is as follows: ``` Screen 0: minimum 320 x 200, current 5760 x 2160, maximum 16384 x 16384 DisplayPort-2 disconnected (normal left inverted right x axis y axis) DisplayPort-3 connected primary 3840x2160+1920+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00*+ 30.00 2560x1440 59.95 1920x1200 60.00 1920x1080 60.0059.94 1600x1200 60.00 1680x1050 60.00 1600x900 60.00 1280x1024 60.02 1440x900 60.00 1280x800 59.81 1152x864 59.97 1280x720 60.0059.94 1024x768 60.00 800x600 60.32 720x480 60.0059.94 640x480 60.0059.94 DisplayPort-4 disconnected (normal left inverted right x axis y axis) HDMI-A-3 disconnected (normal left inverted right x axis y axis) DVI-D-0 disconnected (normal left inverted right x axis y axis) DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 1920x1080+0+1080 (normal left inverted right x axis y axis) 477mm x 268mm 1920x1080 60.00*+ 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x5e) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1280x1024 (0x63) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1024x768 (0x69) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 800x600 (0x6a) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 640x480 (0x6e) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz ``` xrandr output for when scaling is applied is as follows: ``` Screen 0: minimum 320 x 200, current 8960 x 2880, maximum 16384 x 16384 DisplayPort-2 disconnected (normal left inverted right x axis y axis) DisplayPort-3 connected primary 5120x2880+3840+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00*+ 30.00 2560x1440 59.95 1920x1200 60.00 1920x1080 60.0059.94 1600x1200 60.00 1680x1050 60.00 1600x900 60.00 1280x1024 60.02 1440x900 60.00 1280x800 59.81 1152x864 59.97 1280x720 60.0059.94 1024x768 60.00 800x600 60.32 720x480 60.0059.94 640x480 60.0059.94 DisplayPort-4 disconnected (normal left inverted right x axis y axis) HDMI-A-3 disconnected (normal left inverted right x axis y axis) DVI-D-0 disconnected (normal left inverted right x axis y axis) DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 3840x2160+0+720 (normal left inverted right x axis y axis) 477mm x 268mm 1920x1080 60.00*+ 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal
[Bug 1969249] [NEW] all wayland options missing after apt update/upgrade
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 WaylandEnable=True in the config file (it was commented out previously and working fine) to no avail. My system is pretty standard, its a amd RX 570 and intel igpu (UHD 630) system with both gpus outputing to two separate monitors. This might not be a gdm3 issue but it is likely an issue that occurred in one of these packages since the 12th of April. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu4 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 17:51:17 2022 InstallationDate: Installed on 2022-03-16 (30 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-04-15T17:38:59.992621 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969249 Title: all wayland options missing after apt update/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916278] Re: Arduino fails to start: undefined symbol: sp_get_port_usb_vid_pid
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: undefined symbol: sp_get_port_usb_vid_pid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arduino/+bug/1916278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966617] [NEW] Request to backport Fix for Swig when used with python 3.8+ https://github.com/swig/swig/pull/1587/files
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 PyObject_GC_UnTrack macro got deprecated in 3.6 and finally removed in 3.8. Thus for all python versions >= 3.6 instead used PyObject_GC_UnTrack. https://github.com/swig/swig/commit/db9822788e183b79457d6bedab8b9a5cabb4cd5e.patch ** Affects: swig (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/1966617 Title: Request to backport Fix for Swig when used with python 3.8+ https://github.com/swig/swig/pull/1587/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swig/+bug/1966617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963846] [NEW] Patch included: video does not always play or may stutter
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 https://code.videolan.org/videolan/vlc/-/commit/0834d39352a299f1ada6b319fff43f3c34b9d52a A patch is attached here by me to show the changes necessary for bionic 3.0.8 but all LTS versions should have this patch applied as well. ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Attachment added: "0001-codec-avcodec-use-filtered-best-effort-pts.patch" https://bugs.launchpad.net/bugs/1963846/+attachment/5566381/+files/0001-codec-avcodec-use-filtered-best-effort-pts.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963846 Title: Patch included: video does not always play or may stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1963846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
