[Desktop-packages] [Bug 62949] Re: No way to configure mouse button number
** Changed in: kdelibs Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+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 62949]
Additionally, do note -- what is the scope here? Are there global, and window specific settings? For example, does "bind button 11 to 'move forward to next workspace', mean that this is taken no matter if the mouse is hovering over the desktop, or a window? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+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 62949]
Most of those actions are exposed globally, and either have a keyboard shortcut bound to them by default, or you can bind one yourself. And you can also assign arbitrary shell scripts to global keyboard shortcuts. Then you can bind a mouse button to the keyboard shortcut used to trigger any of those actions. So the ability is there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+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 62949]
(In reply to Nate Graham from comment #53) > Most of those actions are exposed globally, and either have a keyboard > shortcut bound to them by default, or you can bind one yourself. And you can > also assign arbitrary shell scripts to global keyboard shortcuts. Then you > can bind a mouse button to the keyboard shortcut used to trigger any of > those actions. So the ability is there. Wouldn't binding a keyboard button to a mouse button, followed by an action to a keyboard button, be considered a workaround? The original bug report seems fairly clear. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+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 62949]
This bug is about being able to bind any action *at all* to the mouse buttons, in X11/xorg, not binding mouse buttons to a key. The prior to responses to this bug, prior to closing, expressed that there was no resolution at all to this bug. So, were you able to; - change workspaces by binding a mouse button, without any additional software (no imwheel!)? - perform any action you can bind a key to? That is, if I can bind a key combo to "minimize window", can I bind a mouse button to that? - change all other buttons already mosue mapped? eg, change from wheel movements to side buttons, or button 11, or whatever, workspace up/down? I don't believe you've read and understood this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+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 62949]
As this has been mentioned you can now bind arbitrary key combinations to extra mouse buttons. I just tested it and it works fine for (bound printscreen to a side button for testing). So I am closing this as resolved. If it doesnt work for people (as it seems to not do for Bernd) please file a new bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/62949 Title: No way to configure mouse button number Status in kdelibs: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-system-tools package in Ubuntu: Invalid Status in kde4libs package in Ubuntu: Won't Fix Bug description: Using kde-systemsettings, I can't configure my 6 button mouse. It would be interesting to just have a way to say "this mouse has X buttons". To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/62949/+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 2039577] Re: gnome-control-center incorrectly claims remote login is off
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2039577 Title: gnome-control-center incorrectly claims remote login is off Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME control center offers a way to disable or enable remote shell (ssh) connections. This functionality is outsourced to /usr/libexec/cc-remote-login-helper which starts and stops the systemd service ssh.service using the code: if (!cc_disable_service (SSHD_SERVICE, G_BUS_TYPE_SYSTEM, &error)) ... if (!cc_enable_service (SSHD_SERVICE, G_BUS_TYPE_SYSTEM, &error)) The irony is that ssh.service is socket activated: zyga@x240:~$ systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: active (running) since Tue 2023-10-17 16:40:04 CEST; 21s ago TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 7055 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 7056 (sshd) Tasks: 1 (limit: 9305) Memory: 1.4M CPU: 21ms CGroup: /system.slice/ssh.service └─7056 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups" paź 17 16:40:04 x240 systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... paź 17 16:40:04 x240 sshd[7056]: Server listening on :: port 22. paź 17 16:40:04 x240 systemd[1]: Started ssh.service - OpenBSD Secure Shell server. In effect, it will always activate again whenever someone attempts to connect. This bug is a security vulnerability, as users may be prone to attacks while thinking remote shell is disabled. I would suggest to *mask* the service, so that it cannot be socket activated. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu2 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: ubuntu:GNOME Date: Tue Oct 17 16:36:23 2023 InstallationDate: Installed on 2023-10-17 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2039577/+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 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
Nitin and I have an agreement to not backport this patch on jammy after a discussion on an email thread, since the current AT command solution could work and switching to libmbim way would take a lot of effort. ** Changed in: oem-priority Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Won't Fix Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Fibocom WWAN cards (Intel XMM 7560), and Lenovo are struggling to give a decent way to run the FCC unlock service without this. Until the device is unlocked, the end users are not able to use the SIM cards, and some of the affected devices have already been shipped. The end users now have to go to the Lenovo support website and download a few scripts and binaries to unlock the device to make their SIM cards work. The Lenovo wants this patch to be included in jammy, then they can provide the FCC unlock service and manage it in OEM-archive, so the end users can use SIM cards as soon as they receive the laptop. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
** Changed in: linux
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
No, this was an issue happening in monitors connected via HDMI.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2046166] Re: mesa 23.3 zink errors
** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released ** Changed in: gtk4 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2046166 Title: mesa 23.3 zink errors Status in gtk4 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2046166/+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 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
It seems like you are experiencing issues with HPLIP on Ubuntu 20.04 LTS. Here are some steps you can take to address the problems: libcups2 and cups Service: Ensure that the libcups2 package is installed. You've already checked this, but you can run the command again to be sure: sudo apt-get install libcups2 libcups2-dev Check if the CUPS service is running: sudo service cups status If it's not running, start it: sudo service cups start python3-pyqt4 Package: The python3-pyqt4 package is not available in the default repositories for Ubuntu 20.04. You might need to find an alternative solution or use a compatible version. As of Ubuntu 20.04, Python 3 and Qt 5 are the default. gtk2-engines-pixbuf Package: Ensure that the gtk2-engines-pixbuf package is installed: sudo apt-get install gtk2-engines-pixbuf python3-dbus.mainloop.qt Package: Similar to python3-pyqt4, the python3-dbus.mainloop.qt package may not be available. You can try installing python3-pyqt5 instead: sudo apt-get install python3-pyqt5 After making these changes, run hp-doctor and hp-check again to see if the issues are resolved i resolved it for https://compassionify.com/somatic-therapy-nyc/ blog. Keep in mind that the compatibility of certain packages with newer Ubuntu releases may require adjustments or alternative solutions. If you encounter any specific errors or warnings during these steps, they might provide additional clues for further troubleshooting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus
[Desktop-packages] [Bug 2012831] Re: CVE-2022-38745
** Information type changed from Private Security to Public -- 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/2012831 Title: CVE-2022-38745 Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice source package in Focal: Fix Released Bug description: https://www.libreoffice.org/about- us/security/advisories/cve-2022-38745/ https://cgit.freedesktop.org/libreoffice/core/commit/?id=5e8f64e50f97d39e83a3358697be14db03566878 https://ubuntu.com/security/CVE-2022-38745 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2012831/+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 2020817] Re: CVE-2023-0950 and CVE-2023-2255
** Information type changed from Private Security to Public -- 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/2020817 Title: CVE-2023-0950 and CVE-2023-2255 Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Won't Fix Status in libreoffice source package in Focal: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: https://www.libreoffice.org/about- us/security/advisories/cve-2023-0950/ https://cgit.freedesktop.org/libreoffice/core/commit/?h=distro/mimo/mimo-7-3&id=29a32f6e405e6c8dfb9729a3d72e23dccdfa53a9 https://www.libreoffice.org/about- us/security/advisories/cve-2023-2255/ https://cgit.freedesktop.org/libreoffice/core/commit/?h=distro/mimo/mimo-7-3&id=7324709c452a7dc69716e67230625703795ada7e https://cgit.freedesktop.org/libreoffice/core/commit/?h=distro/mimo/mimo-7-3&id=b41ef0dfc9e061589fa35c73ec942c0b598be3d4 https://cgit.freedesktop.org/libreoffice/core/commit/?h=distro/mimo/mimo-7-3&id=c7d2580885673fa73253ee8878c8730f0263d3fa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2020817/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Bug fixed with kernel 6.6.x, more info, please see here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
** No longer affects: linux (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
This bug was fixed in the package ubuntu-meta - 1.524.1 --- ubuntu-meta (1.524.1) mantic; urgency=medium * Refreshed dependencies LP: #2039328 * Added flash-kernel to desktop-minimal-recommends [arm64], desktop- recommends [arm64] * Added protection-domain-mapper to desktop-minimal-recommends [arm64], desktop-recommends [arm64] * Added qrtr-tools to desktop-minimal-recommends [arm64], desktop- recommends [arm64] -- Dimitri John Ledkov Fri, 13 Oct 2023 23:28:04 +0100 ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-meta source package in Noble: Fix Released Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2039328] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-meta source package in Noble: Fix Released Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** Tags added: foundations-todo
--
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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+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 2046221] Re: Get help with matrix does not lead to ubuntu support
This bug was fixed in the package gnome-user-docs - 45.1-2ubuntu2 --- gnome-user-docs (45.1-2ubuntu2) noble; urgency=medium * debian/rules: Don't install help-matrix.page (LP: #2046221) -- Gunnar Hjalmarsson Tue, 12 Dec 2023 16:12:27 +0100 ** Changed in: gnome-user-docs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in gnome-user-docs package in Ubuntu: Fix Released Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2046221/+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 2046221] Re: Get help with matrix does not lead to ubuntu support
Marking as wishlist per request from OP in IRC ** Changed in: ubuntu-docs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in gnome-user-docs package in Ubuntu: Fix Committed Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2046221/+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 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+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 2046221] Re: Get help with matrix does not lead to ubuntu support
Thanks for your report. The "Get help with Matrix" page is indeed GNOME specific, and was installed by mistake. It's too early, I think, to replace it with an Ubuntu equivalent, since matrix for Ubuntu is in a test phase. So I keep the ubuntu-docs task open for now. Let's revisit this topic later. ** Also affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-user-docs (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-user-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in gnome-user-docs package in Ubuntu: Fix Committed Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2046221/+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 2040474] Re: GPU reset fails and system freezes
*** This bug is a duplicate of bug 2038998 *** https://bugs.launchpad.net/bugs/2038998 ** This bug has been marked a duplicate of bug 2038998 [amdgpu] Screen corruption, distorted geometry and misplaced triangles -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2040474 Title: GPU reset fails and system freezes Status in mesa package in Ubuntu: New Bug description: There is no specific scenario when the system crashes. In most cases the system crashes completely, but occasionally the system recovers. The system was freshly installed and updated with latest packages. Description: Ubuntu 23.10 Release: 23.10 Kernel: 6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 7 01:35:40 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2040474/+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 2046221] Re: Get help with matrix does not lead to ubuntu support
** Package changed: yelp (Ubuntu) => ubuntu-docs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in ubuntu-docs package in Ubuntu: New Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2046221/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
I've looked further into this and dumped the CORB buffer from booting a windows VM with working sound, using vfio passthrough based on https://github.com/Conmanx360/QemuHDADump Unfortunately converting these to hda-verb commands and applying on linux didn't fix the internal speaker output. Perhaps I need a particular subset of verbs, but I don't know how to determine which ones. There are also some pin settings in the CORB frames though, which makes me wonder if patching the pins (e.g. via hdajackretask) is really the problem we have here. Needs further investigation. ** Attachment added: "CORB frames" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+attachment/5728590/+files/corb-frames.log -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 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:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2046224] [NEW] Resolutions lower than max results in corrupted screen
Public bug reported:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when switching
to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2) (prog-if
00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
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 corruption mantic ubuntu
** Attachment added: "corrupt-screen.jpg"
https://bugs.launchpad.net/bugs/2046224/+attachment/5728569/+files/corrupt-screen.jpg
--
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/2046224
Title:
Resolutions lower than max results in corrupted screen
Status in xorg package in Ubuntu:
New
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:
[Desktop-packages] [Bug 2046221] [NEW] Get help with matrix does not lead to ubuntu support
Public bug reported: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] - Yelp/get more help/Get help with matrix leads only the the Gnome + Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel - [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: - LANG=nl_NL.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=nl_NL.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in yelp package in Ubuntu: New Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2046221/+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
