[Desktop-packages] [Bug 2042796] Re: Ubuntu 20.04 The four corners of the touchscreen are not sensitive
Upload video when encountering the issue ** Attachment added: "Touch screen are not sensitive after BIOS recovery.mp4" https://bugs.launchpad.net/bugs/2042796/+attachment/5716317/+files/Touch%20screen%20are%20not%20sensitive%20after%20BIOS%20recovery.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042796 Title: Ubuntu 20.04 The four corners of the touchscreen are not sensitive Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042796] [NEW] Ubuntu 20.04 The four corners of the touchscreen are not sensitive
Public bug reported: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2039160 somerville ** Tags added: oem-priority originate-from-2039160 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042796 Title: Ubuntu 20.04 The four corners of the touchscreen are not sensitive Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981837] Re: Using DiNG triggers ubuntu-dock opacity
« Just added a reminder to fix this in jammy, some time. » Is it ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1981837 Title: Using DiNG triggers ubuntu-dock opacity Status in Gnome Shell Extension Desktop Icons Ng: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: New Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: Hi, Ubuntu 22.04 LTS jammy Linux 5.15.0-40-generic x86_64 x86_64 ubuntu-xorg / x11 I prefer panel and dock to become fully opaque only when windows are maximized. So I use this extension for panel : Transparent Top Bar (Adjustable transparency) which JustWorks™ in both Xorg and Wayland. In ubuntu-dock, dynamic-transparency is set through dconf-editor ( transparency-mode, min-alpha, max-alpha. ) When using DiNG under Wayland, opacity is triggered as if « desktop » was considered as a maximized window. Under Xorg, DiNG does not trigger dock opacity, as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1981837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042763] Re: Keyboard navigation in the Show Applications menu
** Description changed:
Hello.
My bug, if it is one, is in Wayland, or more likely in new desktop icon
management thingy, which was introduced with one of the last Ubuntu versions.
- I can't navigate the "Show Applications" menu with the keyboard when I go
into a subfolder. This means that I can navigate in "Show Applications" with
the keyboard as long as I stay at the top level. But when I go to a folder that
contains several programs, such as the "Utilities" folder, the keyboard
navigation no longer works. The cursor will stuck no matter which arrow key I
press. Even the Tab key is of no use. I've already searched for this problem on
the Internet, but couldn't find it. Either I'm the only one who has this
problem, or most others simply prefer to use the mouse to navigate. I only use
the keyboard when possible. I am a heavy keyboard/hotkey user.
+ Maybe around ubuntu 22.04. I'm not sure if the problem came when Wayland was
set as the window manager or if it came when the new "Desktop Icon Manager"
thing came along. I think the two weren't too far apart in time. I'm only
reporting my problem now because I always assumed it would be fixed in future
updates. But my problem never changed with all the updates.
+ Here is my problem:
+ I can't navigate in the "Show Applications" menu with the keyboard when I go
into a subfolder. This means that I can navigate in "Show Applications" with
the keyboard as long as I stay at the top level. But when I go to a folder that
contains several programs, such as the "Utilities" folder, the keyboard
navigation no longer works. The cursor will stuck no matter which arrow key I
press. Even the Tab key is of no use. I've already searched for this problem on
the Internet, but couldn't find it. Either I'm the only one who has this
problem, or most others simply prefer to use the mouse to navigate. I only use
the keyboard when possible. I am a heavy keyboard/hotkey user.
The problem has existed for me for a long time. It either came with the
switch to Wayland or with the switch to the new desktop icon management thingy.
It's just a small problem, but for a massive keyboard user, it's really
annoying. And definitely also for people who can't use a mouse.
Kind regards
Chris
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 11:22:55 2023
DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500
XT/6500M] [1002:743f] (rev c1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M]
[1043:05db]
InstallationDate: Installed on 2021-09-16 (779 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: P35C-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P35C-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042763
Title:
Keyboard navigation in the Show Applications menu
Status in xorg package in Ubuntu:
New
Bug description:
Hello.
My bug, if it is one, is in Wayland, or
[Desktop-packages] [Bug 2042780] [NEW] CUPS always fails to print and crashes; started on 23.10
Public bug reported:
Release: 23.10
Package: 2.0.0-0ubuntu2
When trying to print from any application to a network printer Brother
DCP-8112DN, which was detected and configured automatically by the OS,
the printing operation fails and a crash is reported.
It worked fine in Ubuntu 22.04 and 23.04. Also works fine on other
distros. The only OS where this happens is on Ubuntu 23.10. Can
reproduce 100% of the time, including on fresh installs.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: cups-browsed 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 18:47:27 2023
InstallationDate: Installed on 2023-11-05 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lpstat: device for Brother_DCP_8112DN: implicitclass://Brother_DCP_8112DN/
Lsusb:
Bus 001 Device 003: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/Brother_DCP_8112DN.ppd'] failed with exit code 2: grep:
/etc/cups/ppd/Brother_DCP_8112DN.ppd: Permission denied
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=c25eb9d1-c8a4-43df-8eee-be01ff705965 ro quiet splash
SourcePackage: cups-browsed
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
** Affects: cups-browsed (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-browsed in Ubuntu.
https://bugs.launchpad.net/bugs/2042780
Title:
CUPS always fails to print and crashes; started on 23.10
Status in cups-browsed package in Ubuntu:
New
Bug description:
Release: 23.10
Package: 2.0.0-0ubuntu2
When trying to print from any application to a network printer Brother
DCP-8112DN, which was detected and configured automatically by the OS,
the printing operation fails and a crash is reported.
It worked fine in Ubuntu 22.04 and 23.04. Also works fine on other
distros. The only OS where this happens is on Ubuntu 23.10. Can
reproduce 100% of the time, including on fresh installs.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: cups-browsed 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 18:47:27 2023
InstallationDate: Installed on 2023-11-05 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
Lpstat: device for Brother_DCP_8112DN: implicitclass://Brother_DCP_8112DN/
Lsusb:
Bus 001 Device 003: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/Brother_DCP_8112DN.ppd'] failed with exit code 2: grep:
/etc/cups/ppd/Brother_DCP_8112DN.ppd: Permission denied
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=c25eb9d1-c8a4-43df-8eee-be01ff705965 ro quiet splash
SourcePackage: cups-browsed
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
I thought the whole point of Snap cores is that its supposed to be more resistant to issues like this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name
[Desktop-packages] [Bug 2030947] Re: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature en
Kir, this is the Ubuntu bug tracker, not the Fedora one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2030947 Title: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature enabled Status in gjs package in Ubuntu: New Bug description: gnome-shell logs gnome-shell[4537]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed multiple times per second for weeks now. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:38:23 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 44.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2030947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Ok. This bug is focused on the UI for the upgrader itself. I would recommend you to ask a question at Ask Ubuntu. That way you'll hopefully get help to determine if it is a problem with your configuration or some kind of bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
My upgrade for Ubuntu to 23.10 was a bunch of days ago. In that time I have rebooted multiple times and no change observed for fonts (better or worse). Still bad heh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042776] [NEW] [81VV, Realtek ALC257, Speaker, Internal] No sound at all
Public bug reported: No sound whatsoever not even on external speakers. I suspected a hardware problem at first and by the way drivers have been updated but same issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph-vunanga 4569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 20:04:21 2023 InstallationDate: Installed on 2023-03-30 (220 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [81VV, Realtek ALC257, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN27WW(V1.16) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76446 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IIL dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrCUCN27WW(V1.16):bd06/15/2021:br1.27:efr1.27:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0T76446WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL:skuLENOVO_MT_81VV_BU_idea_FM_IdeaPadS340-14IIL: dmi.product.family: IdeaPad S340-14IIL dmi.product.name: 81VV dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL dmi.product.version: Lenovo IdeaPad S340-14IIL dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2042776 Title: [81VV, Realtek ALC257, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound whatsoever not even on external speakers. I suspected a hardware problem at first and by the way drivers have been updated but same issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph-vunanga 4569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 20:04:21 2023 InstallationDate: Installed on 2023-03-30 (220 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [81VV, Realtek ALC257, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN27WW(V1.16) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76446 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IIL dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrCUCN27WW(V1.16):bd06/15/2021:br1.27:efr1.27:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0T76446WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL:skuLENOVO_MT_81VV_BU_idea_FM_IdeaPadS340-14IIL: dmi.product.family: IdeaPad S340-14IIL dmi.product.name: 81VV dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL dmi.product.version: Lenovo IdeaPad S340-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2042776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2042543] Re: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration
xdg-desktop-portal-gtk was indeed installed with gnome: ~$ grep " install " /var/log/dpkg.log | grep xdg 2023-11-04 13:01:03 install xdg-desktop-portal:amd64 1.14.4-1ubuntu2~22.04.1 1.14.4-1ubuntu2~22.04.1 2023-11-04 13:01:08 install xdg-desktop-portal-gtk:amd64 1.14.0-1build1 2023-11-04 13:01:08 install xdg-desktop-portal-gnome:amd64 42.1-0ubuntu1 And after removing the xdg-desktop-portal-gtk package the file access in firefox stopped working again. There was no warning that firefox depencies will be broken upon removal of the xdg package, so xdg seems to be missing from the firefox depencies, wich is confirmed by the package manager: ~$ apt-cache depends firefox | grep xdg ~$ So either just the xdg missing in the depency list of firefox, or, worse, if snap manages dependencies independently, it fails to keep dependencies consistent whenever there is an attempt to update or remove them via the package manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2042543 Title: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration Status in firefox package in Ubuntu: Incomplete Bug description: Since a recent update, firefox cannot any more save pages, images or download files. It also cannot launch other processes like zoom via meeting links. This seems to be caused by a faulty apparmor configuration and a common problem since the introduction of the snap package, e.g. c.f. https://arstechnica.com/civis/threads/snap-based- firefox-is-a-terrible-experience.1487499 or https://ubuntuforums.org/showthread.php?t=2476758 . However, none of the proposed workarounds works for me, neither editing apparmor configuration files, reinstalling firefox, or refreshing it via Help -> More troubleshoot information -> Refresh firefox. Finally, I found that snap installs two binaries, one in /usr/bin/firefox and one in /snap/firefox/3252/usr/lib/firefox/firefox. If I start firefox from cli with typing firefox, the first one is invoked, which is broken. If I explicitly invoke /snap/firefox/3252/usr/lib/firefox/firefox, saving works fine. So I just aliased the second binary to firefox in the .bashrc. This binary also strangely seems to use its own configuration, i.e. own apps, password storage, etc. I hope this information helps other users with the same problem and the package maintainers with fixing the configuration. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Nov 2 10:03:30 2023 InstallationDate: Installed on 2015-11-05 (2918 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-10-30 (367 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986444] Re: network-manager fails to detect usb internet adapter
>From what I discovered, the USB device itself is not listed by lsusb anymore although the driver ax88179_178a is available in /lib/modules/... Note : I've checked the device on another laptop where it works just fine with the very same cable. On that secondary laptopt, the device is listed by lsusb properly as follows : ASIX Electronics Corp. AX88179 Gigabit Ethernet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1986444 Title: network-manager fails to detect usb internet adapter Status in network-manager package in Ubuntu: Confirmed Bug description: Since I upgraded to Ubuntu 22.04 from 20.04 several days ago, my ugreen network adapter is not detected even though the lights between the ethernet cable and the adapter are on. I am using a Dell G3 3500 that came with windows 10. The adapter works ok on my Dell XPS and worked fine with Ubuntu 20.04 on the Dell G3. Other devices are detected when plugged into the usb. The wifi is working. Any help with this would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 13 19:16:38 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-12-04 (617 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.4 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1986444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986444] Re: network-manager fails to detect usb internet adapter
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1986444 Title: network-manager fails to detect usb internet adapter Status in network-manager package in Ubuntu: Confirmed Bug description: Since I upgraded to Ubuntu 22.04 from 20.04 several days ago, my ugreen network adapter is not detected even though the lights between the ethernet cable and the adapter are on. I am using a Dell G3 3500 that came with windows 10. The adapter works ok on my Dell XPS and worked fine with Ubuntu 20.04 on the Dell G3. Other devices are detected when plugged into the usb. The wifi is working. Any help with this would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 13 19:16:38 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-12-04 (617 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.4 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1986444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042772] Re: Display corrupted/freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042772 Title: Display corrupted/freeze Status in xorg package in Ubuntu: New Bug description: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042772] [NEW] Display corrupted/freeze
You have been subscribed to a public bug: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu -- Display corrupted/freeze https://bugs.launchpad.net/bugs/2042772 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
@Bloodyiron: Does it help to reboot? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Not sure if I'm in the right thread, but after upgrading to Mantic (23.10) a lot of fonts, namely in browsers, look like trash. There's lots of overlapping and other font weirdness. I haven't really seen boxes yet, but it was not present before doing do-release-upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015479] Re: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array()
** No longer affects: wayland (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2015479 Title: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 --- after clicking the screenshot icon in the top panel right corner control centre, my google chrome window crashed and the screenshots were not taken. The system then automatically logged me out closing all my other windows. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 19:35:53 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ochego Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
** Tags added: mantic ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041008] Re: wayland : no uppercase accented characters with capslock
*** This bug is a duplicate of bug 2035076 ***
https://bugs.launchpad.net/bugs/2035076
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2035076, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 2035076
Wayland - Capital accented letters not recognized
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2041008
Title:
wayland : no uppercase accented characters with capslock
Status in wayland package in Ubuntu:
Confirmed
Bug description:
Until Ubuntu 23.04, with the "french alternative" [français (variante)]
keyboard, capslock gave you directly uppercase accented characters (like É È À)
from the keys 2, 7 and 0 of the fifth row of the keyboard.
With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it
works like before if you connect with Xorg.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 13:36:26 2023
DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850]
[1002:6739] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD
6850] [174b:174b]
InstallationDate: Installed on 2020-04-10 (1294 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
dmi.bios.date: 08/05/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: 970 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2041008/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
Could be similar to bug #2035076 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in wayland package in Ubuntu: Confirmed Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2040450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040999] Re: backport a commit to fix workspace matrix extension
** Tags added: mantic noble ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu Mantic) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Mantic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2040999 Title: backport a commit to fix workspace matrix extension Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Mantic: Triaged Bug description: [Impact] GNOME Workspace Matrix extension is broken on mantic and up, even with the latest git version because some previously exported variables and classes are not exported anymore with the current gnome-shell version. [Fix] Backport a merged commit from upstream https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2978 [Test case] Test current wsmatrix extension from git once the gnome-shell update has landed. [Regression potential] I don't know how exporting some variables again could break anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036426] Re: gnome calculator crash on IMF server error
** Changed in: gnome-calculator Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2036426 Title: gnome calculator crash on IMF server error Status in GNOME Calculator: Fix Released Status in gnome-calculator package in Ubuntu: Confirmed Bug description: Description: Ubuntu 23.04 Release: 23.04 gnome-calculator: Installed: 1:44.0-1ubuntu1 Candidate: 1:44.0-1ubuntu1 Version table: *** 1:44.0-1ubuntu1 500 500 http://mirror.sg.gs/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status when i tried to open the app, it crashed immediately with this in the log: ** (gnome-calculator:75655): WARNING **: 19:43:34.821: currency- provider.vala:161: Couldn't download IMF currency rate file: HTTP/2 Error: INTERNAL_ERROR (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0) (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL) Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/2036426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042767] [NEW] Crackling sound at random intervals while Virtualbox is running
Public bug reported: Recently I'm having an issue where the audio playback from my HDMI output starts crackling at random intervals in Ubuntu 22.04. It is not sure if Virtualbox is causing this issue, but it's a possible cause. I dug up a forum post from 2 years ago on AskUbuntu where someone implies Virtualbox causes their issue. Since Virtualbox runs in the background all the time for me, I cannot be certain about this. I run my Home Asisstant server inside Virtualbox. If any audio playback starts crackling, executing pulseaudio -k always fixes it. Then the applications producing sound need to be restarted in order to get any sound out of them. After that the crackling will take hours to show up again. In that AskUbuntu forum post that I referred to earlier, the user fixed this by setting resample-method = speex-float-10 in /etc/pulse/daemon.conf. So I did the same thing just before filling this bug report to see if that would fix it. I do not have enough data yet to draw any conclusions. I can be sure that the crackling is from the HDMI sound output and not from malfunctioning speakers, since no other devices connected to the same speakers/TV have this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rick 90340 F pulseaudio /dev/snd/controlC0: rick 90340 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 14:01:41 2023 InstallationDate: Installed on 2023-10-28 (8 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG B550M MORTAR WIFI (MS-7C94) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H0:bd10/13/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C94:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550MMORTARWIFI(MS-7C94):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C94 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2023-11-05T11:50:19.891182 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2042767 Title: Crackling sound at random intervals while Virtualbox is running Status in pulseaudio package in Ubuntu: New Bug description: Recently I'm having an issue where the audio playback from my HDMI output starts crackling at random intervals in Ubuntu 22.04. It is not sure if Virtualbox is causing this issue, but it's a possible cause. I dug up a forum post from 2 years ago on AskUbuntu where someone implies Virtualbox causes their issue. Since Virtualbox runs in the background all the time for me, I cannot be certain about this. I run my Home Asisstant server inside Virtualbox. If any audio playback starts crackling, executing pulseaudio -k always fixes it. Then the applications producing sound need to be restarted in order to get any sound out of them. After that the crackling will take hours to show up again. In that AskUbuntu forum post that I referred to earlier, the user fixed this by setting resample-method = speex-float-10 in /etc/pulse/daemon.conf. So I did the same thing just before filling this bug report to see if that would fix it. I do not have enough data yet to draw any conclusions. I can be sure that the crackling is from the HDMI sound output and not from malfunctioning speakers, since no other devices connected to the same speakers/TV have this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rick 90340 F pulseaudio /dev/snd/controlC0: rick 90340
[Desktop-packages] [Bug 2042768] [NEW] package libreoffice-common 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: le sous-processus paquet libreoffice-common script post-installation installé a re
Public bug reported: Installation failed during upgrade from 20.04LTS to 22.04LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.7-0ubuntu0.22.04.3 ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252 Uname: Linux 5.4.0-166-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 5 14:03:57 2023 ErrorMessage: le sous-processus paquet libreoffice-common script post-installation installé a renvoyé un état de sortie d'erreur 1 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: le sous-processus paquet libreoffice-common script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to jammy on 2023-11-05 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2042768 Title: package libreoffice-common 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: le sous-processus paquet libreoffice-common script post-installation installé a renvoyé un état de sortie d'erreur 1 Status in libreoffice package in Ubuntu: New Bug description: Installation failed during upgrade from 20.04LTS to 22.04LTS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.7-0ubuntu0.22.04.3 ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252 Uname: Linux 5.4.0-166-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 5 14:03:57 2023 ErrorMessage: le sous-processus paquet libreoffice-common script post-installation installé a renvoyé un état de sortie d'erreur 1 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.7-0ubuntu0.22.04.3 failed to install/upgrade: le sous-processus paquet libreoffice-common script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to jammy on 2023-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2042768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036426] Re: gnome calculator crash on IMF server error
Upstream bug: https://gitlab.gnome.org/GNOME/gnome- calculator/-/issues/359 Upstream says the actual bug is in libsoup: https://gitlab.gnome.org/GNOME/libsoup/-/issues/361. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/-/issues #359 https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359 ** Also affects: gnome-calculator via https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/libsoup/-/issues #361 https://gitlab.gnome.org/GNOME/libsoup/-/issues/361 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/2036426 Title: gnome calculator crash on IMF server error Status in GNOME Calculator: Unknown Status in gnome-calculator package in Ubuntu: Confirmed Bug description: Description: Ubuntu 23.04 Release: 23.04 gnome-calculator: Installed: 1:44.0-1ubuntu1 Candidate: 1:44.0-1ubuntu1 Version table: *** 1:44.0-1ubuntu1 500 500 http://mirror.sg.gs/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status when i tried to open the app, it crashed immediately with this in the log: ** (gnome-calculator:75655): WARNING **: 19:43:34.821: currency- provider.vala:161: Couldn't download IMF currency rate file: HTTP/2 Error: INTERNAL_ERROR (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0) (gnome-calculator:75655): libsoup-WARNING **: 19:43:34.821: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL) Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/2036426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041008] Re: wayland : no uppercase accented characters with capslock
Additional information:
This issue depends on the application used ! You get it with Gnome-text-
editor or LO Writer but not in Firefox Web browser (snap). Because the
good libraries are embedded with the snap ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2041008
Title:
wayland : no uppercase accented characters with capslock
Status in wayland package in Ubuntu:
Confirmed
Bug description:
Until Ubuntu 23.04, with the "french alternative" [français (variante)]
keyboard, capslock gave you directly uppercase accented characters (like É È À)
from the keys 2, 7 and 0 of the fifth row of the keyboard.
With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it
works like before if you connect with Xorg.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 13:36:26 2023
DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850]
[1002:6739] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD
6850] [174b:174b]
InstallationDate: Installed on 2020-04-10 (1294 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
dmi.bios.date: 08/05/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: 970 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2041008/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042764] [NEW] ICC profile has no effect in Wayland session
Public bug reported: The color profile set either via the Gnome Control Center or colord has no effect in the Wayland session. I tested it with Firefox and can see no difference no matter what color profile is set in GNOME. I also changed the color profile in Firefox via the about:config and tried to set the color management flag to 1 (to always enable color management to no effect). I then tested eog vs. shotwell. In the Gnome Wayland session the images I compared looked identical but both not in the ICC profile I selected. In the Gnome Xorg session there was a visible difference between eog which displayed the image with the selected ICC profile and shotwell which ignored the ICC profile. This bug might very well be an upstream issue. I am reporting it because (without diving very deep into the system) I do not see anything else to try to remedy this issue. Ubuntu version: Ubuntu 23.10 colord version: 1.4.6-3 (Maybe this is not the correct package to file this against) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: colord 1.4.6-3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 13:09:08 2023 InstallationDate: Installed on 2023-11-03 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/2042764 Title: ICC profile has no effect in Wayland session Status in colord package in Ubuntu: New Bug description: The color profile set either via the Gnome Control Center or colord has no effect in the Wayland session. I tested it with Firefox and can see no difference no matter what color profile is set in GNOME. I also changed the color profile in Firefox via the about:config and tried to set the color management flag to 1 (to always enable color management to no effect). I then tested eog vs. shotwell. In the Gnome Wayland session the images I compared looked identical but both not in the ICC profile I selected. In the Gnome Xorg session there was a visible difference between eog which displayed the image with the selected ICC profile and shotwell which ignored the ICC profile. This bug might very well be an upstream issue. I am reporting it because (without diving very deep into the system) I do not see anything else to try to remedy this issue. Ubuntu version: Ubuntu 23.10 colord version: 1.4.6-3 (Maybe this is not the correct package to file this against) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: colord 1.4.6-3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 13:09:08 2023 InstallationDate: Installed on 2023-11-03 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2042764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042763] Re: Keyboard navigation in the Show Applications menu
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042763
Title:
Keyboard navigation in the Show Applications menu
Status in xorg package in Ubuntu:
New
Bug description:
Hello.
My bug, if it is one, is in Wayland, or more likely in new desktop icon
management thingy, which was introduced with one of the last Ubuntu versions.
I can't navigate the "Show Applications" menu with the keyboard when I go
into a subfolder. This means that I can navigate in "Show Applications" with
the keyboard as long as I stay at the top level. But when I go to a folder that
contains several programs, such as the "Utilities" folder, the keyboard
navigation no longer works. The cursor will stuck no matter which arrow key I
press. Even the Tab key is of no use. I've already searched for this problem on
the Internet, but couldn't find it. Either I'm the only one who has this
problem, or most others simply prefer to use the mouse to navigate. I only use
the keyboard when possible. I am a heavy keyboard/hotkey user.
The problem has existed for me for a long time. It either came with the
switch to Wayland or with the switch to the new desktop icon management thingy.
It's just a small problem, but for a massive keyboard user, it's really
annoying. And definitely also for people who can't use a mouse.
Kind regards
Chris
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 11:22:55 2023
DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500
XT/6500M] [1002:743f] (rev c1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M]
[1043:05db]
InstallationDate: Installed on 2021-09-16 (779 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: P35C-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P35C-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042763/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042763] [NEW] Keyboard navigation in the Show Applications menu
You have been subscribed to a public bug:
Hello.
My bug, if it is one, is in Wayland, or more likely in new desktop icon
management thingy, which was introduced with one of the last Ubuntu versions.
I can't navigate the "Show Applications" menu with the keyboard when I go into
a subfolder. This means that I can navigate in "Show Applications" with the
keyboard as long as I stay at the top level. But when I go to a folder that
contains several programs, such as the "Utilities" folder, the keyboard
navigation no longer works. The cursor will stuck no matter which arrow key I
press. Even the Tab key is of no use. I've already searched for this problem on
the Internet, but couldn't find it. Either I'm the only one who has this
problem, or most others simply prefer to use the mouse to navigate. I only use
the keyboard when possible. I am a heavy keyboard/hotkey user.
The problem has existed for me for a long time. It either came with the switch
to Wayland or with the switch to the new desktop icon management thingy. It's
just a small problem, but for a massive keyboard user, it's really annoying.
And definitely also for people who can't use a mouse.
Kind regards
Chris
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 11:22:55 2023
DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M]
[1002:743f] (rev c1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M]
[1043:05db]
InstallationDate: Installed on 2021-09-16 (779 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: P35C-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P35C-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu wayland-session
--
Keyboard navigation in the Show Applications menu
https://bugs.launchpad.net/bugs/2042763
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Is you want to make this permanent on Firefox you can go to about:config and change: browser.preferences.defaultPerformanceSettings.enabled -> false layers.acceleration.disabled -> true And Firefox will start without gpu acceleration (until MATE supports Wayland, I hope). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
To all MATE-Desktop users: there is not Wayland support. The only way to execute Firefox and Chromium snaps is by disabling gpu support: $ firefox --safe-mode $ chromium --disable-gpu Or install the packages outside snap. Firefox appimage works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Possible, proposed solutions Option 1: Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox Option 2: chromium --ozone-platform=wayland MOZ_ENABLE_WAYLAND=1 firefox If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on
[Desktop-packages] [Bug 2042762] [NEW] GNOME under Wayland does not start after updating to Ubuntu 23.10
Public bug reported: Hello Ubuntu community, I recently upgraded my system from Ubuntu 23.04 to 23.10 and since then (1 Week) I've had problems starting GNOME under Wayland. Here are the details of my system and the steps already taken: System information: Device: MS Surface Pro 5 (Intel Iris Plus Graphics 640) Ubuntu version: 10/23 Kernel: Linux 6.5.6-surface Description of the problem: After updating to Ubuntu 23.10, the GNOME window manager no longer starts under Wayland. X.org, however, works fine. However, in my opinion the quality of the display is lower (screen tearing, flickering mouse, low fps) Screen resolution and scaling: I use an external monitor with 1920x1080px and 100% scaling. The built- in screen has a resolution of 2736x1824px and a scaling of 200%. Fractional scaling is enabled. Steps already taken: * All available updates have been installed. * Fractional scaling has been disabled. * I tried to "force" Wayland by adding "WaylandEnable=True" in the "gdm3 custom.conf". * Automatic login (without entering a password) has been deactivated. * I tried reinstalling "libglib2.0-0". * Various Linux kernels tested: Linux 6.5.6-surface, Linux 6.3.2-surface, Linux 6.5.0-9-generic ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log_coredump.zip" https://bugs.launchpad.net/bugs/2042762/+attachment/5716160/+files/log_coredump.zip ** Description changed: Hello Ubuntu community, I recently upgraded my system from Ubuntu 23.04 to 23.10 and since then (1 Week) I've had problems starting GNOME under Wayland. Here are the details of my system and the steps already taken: System information: Device: MS Surface Pro 5 (Intel Iris Plus Graphics 640) Ubuntu version: 10/23 Kernel: Linux 6.5.6-surface Description of the problem: After updating to Ubuntu 23.10, the GNOME window manager no longer starts under Wayland. X.org, however, works fine. However, in my opinion the quality of the display is lower (screen tearing, flickering mouse, low fps) Screen resolution and scaling: I use an external monitor with 1920x1080px and 100% scaling. The built- in screen has a resolution of 2736x1824px and a scaling of 200%. Fractional scaling is enabled. Steps already taken: * All available updates have been installed. * Fractional scaling has been disabled. * I tried to "force" Wayland by adding "WaylandEnable=True" in the "gdm3 custom.conf". * Automatic login (without entering a password) has been deactivated. * I tried reinstalling "libglib2.0-0". * Various Linux kernels tested: Linux 6.5.6-surface, Linux 6.3.2-surface, Linux 6.5.0-9-generic - * Log (journalctl) from login screen (gdm Debug) - - Log (journalctl) from login screen (gdm Debug) - - https://drive.google.com/file/d/1Hm8QjmRknCMAhKwOhjHc2mgvbYsBWzKO/view?usp=sharing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042762 Title: GNOME under Wayland does not start after updating to Ubuntu 23.10 Status in gnome-shell package in Ubuntu: New Bug description: Hello Ubuntu community, I recently upgraded my system from Ubuntu 23.04 to 23.10 and since then (1 Week) I've had problems starting GNOME under Wayland. Here are the details of my system and the steps already taken: System information: Device: MS Surface Pro 5 (Intel Iris Plus Graphics 640) Ubuntu version: 10/23 Kernel: Linux 6.5.6-surface Description of the problem: After updating to Ubuntu 23.10, the GNOME window manager no longer starts under Wayland. X.org, however, works fine. However, in my opinion the quality of the display is lower (screen tearing, flickering mouse, low fps) Screen resolution and scaling: I use an external monitor with 1920x1080px and 100% scaling. The built-in screen has a resolution of 2736x1824px and a scaling of 200%. Fractional scaling is enabled. Steps already taken: * All available updates have been installed. * Fractional scaling has been disabled. * I tried to "force" Wayland by adding "WaylandEnable=True" in the "gdm3 custom.conf". * Automatic login (without entering a password) has been deactivated. * I tried reinstalling "libglib2.0-0". * Various Linux kernels tested: Linux 6.5.6-surface, Linux 6.3.2-surface, Linux 6.5.0-9-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly
Just hit a similar issue with "fonts-wine 8.0.1~repack-3ubuntu2" in Ubuntu 23.10. Text on the web page https://www.virtualdub.org/altirra.html is rendered by the font Tahoma and it looks ugly, see https://i.imgur.com/KXC5DYq.png I uninstalled the package "fonts-wine". Now the font Verdana is used on that page and it looks well, see https://i.imgur.com/P7xO53r.png I tested it in Chrome and Firefox, with the same result. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/412195 Title: ttf-tahoma-replacement makes some web-sites look ugly Status in fontconfig package in Ubuntu: Invalid Status in wine1.2 package in Ubuntu: Fix Released Bug description: Binary package hint: wine1.2 This font package is good for wine 1.2; however, it also makes sites look ugly in Firefox and other browsers. I had to manually remove the fonts from /usr/share/fonts/ to rectfiy this, because removing the package through apt would have made me remove wine 1.2 and I didn't want that. ProblemType: Bug Architecture: i386 Date: Wed Aug 12 00:23:40 2009 DistroRelease: Ubuntu 9.10 Package: ttf-tahoma-replacement 1.1.27-0ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: wine1.2 Uname: Linux 2.6.31-5-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/412195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031096] Re: udisks2 daemon fails to start
Great, let's close it then, thanks ** Changed in: udisks2 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2031096 Title: udisks2 daemon fails to start Status in udisks: New Status in udisks2 package in Ubuntu: Fix Released Bug description: udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10) Error status is: Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager... Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'. Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager. This bug seems to refer: https://github.com/storaged- project/udisks/issues/1139 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2031096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039369] Re: gnome-mahjongg locks up with high cpu usage on the second game played after one or two moves
This is met with many linux OS and seems related to cairo: https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/issues/37 https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/merge_requests/35 Hope 3.42 will be out soon ** Bug watch added: gitlab.gnome.org/GNOME/gnome-mahjongg/-/issues #37 https://gitlab.gnome.org/GNOME/gnome-mahjongg/-/issues/37 ** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/2039369 Title: gnome-mahjongg locks up with high cpu usage on the second game played after one or two moves Status in gnome-mahjongg package in Ubuntu: Confirmed Bug description: I encountered this behaviour earlier during development of mantic and opened a bug which I closed when the behaviour stopped .. later during development .. unfortunately I have to file this bug again as the problem has returned.. it has also been reported for an earlier version of gnome-mahjongg as well ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-mahjongg 1:3.40.0-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 14 17:57:49 2023 InstallationDate: Installed on 2023-10-04 (10 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-mahjongg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/2039369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042728] Re: No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336).
Note: after launching 'ubuntu-bug' from command line, pulseaudio did crash and launched a automatic bug report, then I completed my manual bug report. ** Summary changed: - No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). + No sound from speakers. Audio chip: Everest ESSX 8336 (ESSX8336, ES8336). ** Description changed: - Similar to bug #1977685. + The laptop does not output sound from its speaker, just a loud 'click' + when launching a sound player (ie: audio file from Rhythm'box). + + Issue similar to bug #1977685. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: joel905 F wireplumber - /dev/snd/seq:joel902 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: joel905 F wireplumber + /dev/snd/seq:joel902 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 15:27:44 2023 InstallationDate: Installed on 2023-11-03 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: - LANG=fr_FR.UTF-8 - LANGUAGE=fr_FR - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color + LANG=fr_FR.UTF-8 + LANGUAGE=fr_FR + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 0.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE dmi.board.asset.tag: Default string dmi.board.name: G8316 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: N14C4WH64 dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor: THOMSON -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2042728 Title: No sound from speakers. Audio chip: Everest ESSX 8336 (ESSX8336, ES8336). Status in pulseaudio package in Ubuntu: New Bug description: The laptop does not output sound from its speaker, just a loud 'click' when launching a sound player (ie: audio file from Rhythm'box). Issue similar to bug #1977685. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel905 F wireplumber /dev/snd/seq:joel902 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 15:27:44 2023 InstallationDate: Installed on 2023-11-03 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr_FR PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 0.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE dmi.board.asset.tag: Default string dmi.board.name: G8316 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: N14C4WH64 dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor:
[Desktop-packages] [Bug 1983181] Re: Cheese Internal data stream error
Still happens on my system (22.04.3 LTS). ** Changed in: cheese (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1983181 Title: Cheese Internal data stream error Status in cheese package in Ubuntu: Confirmed Bug description: corrado@corrado-n4-kk-0718:~$ cheese (cheese:12091): Gdk-WARNING **: 16:18:17.659: Native Windows taller than 65535 pixels are not supported (cheese:12091): cheese-WARNING **: 16:18:48.168: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: cheese 41.1-2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 30 16:21:11 2022 InstallationDate: Installed on 2022-07-19 (11 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese41.1-2 cheese-common 41.1-2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: corrado1757 F wireplumber /dev/snd/controlC0: corrado1757 F wireplumber /dev/snd/seq:corrado1754 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-07-19 (11 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2f8a8007-7685-4a68-85d3-46088d66849c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220711.gitdfa29317-0ubuntu1 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: wayland-session kinetic Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
