[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
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7189 Importance: Unknown Status: Unknown -- 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 GNOME Shell: Unknown 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/gnome-shell/+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 2044061] Re: Vertical and horizontal lines appearing since update
** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Summary changed: - Vertical and horizontal lines appearing since update + [amdgpu] Green vertical and horizontal lines appearing since update ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags added: amdgpu -- 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/2044061 Title: [amdgpu] Green vertical and horizontal lines appearing since update Status in linux-hwe-6.2 package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Did sudo apt update && upgrade, now getting vertical and horizontal visual artifacts -Tried installing amd drivers -Tried using an older kernel Still no luck; definitely 100% not a hardware issue, machine is dual boot and they do not appear on the windows side. It's related to the update. It occurs particularly frequently if I'm writing code or moving windows around. Attaching a picture to try and show it (it's hard to catch on pictures and I don't think it shows up in a screen shot). It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 21:30:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (21 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.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: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd 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 N/A 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/linux-hwe-6.2/+bug/2044061/+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 2044027] Re: keyboard , mouse and black screen after rebooting on ubuntu os only
Please ignore "ACPI Error: ..." because it's really just a warning about
a BIOS bug, which is very common and not really a problem to Ubuntu.
Please also describe in more detail what the remaining problem is, and
run:
apport-collect 2044027
to automatically provide system information.
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2044027
Title:
keyboard , mouse and black screen after rebooting on ubuntu os only
Status in linux package in Ubuntu:
Incomplete
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard
are working fine on ubuntu systems with all versions and all other os
including windows os
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044027/+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 2043951] Re: very slow when charger isn't connect
Try changing the power mode in the quick settings menu, or in Settings > Power, to 'Performance'. Or just to 'Balanced', just not 'Power Saver'. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2043951 Title: very slow when charger isn't connect Status in Ubuntu: Incomplete Bug description: very slow error my ryzen 7 5700U laptop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 09:56:18 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-19 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2043951/+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 2043966] Re: Second display is not showing up
There is no working Nvidia driver installed. Please use the 'Additional Drivers' app to install one. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2043966 Title: Second display is not showing up Status in Ubuntu: Invalid Bug description: This is issues with NVIDIA drivers ~$ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126 Uname: Linux 5.15.0-1050-realtime x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 09:39:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: librealsense2-dkms/1.3.24, 5.15.0-1050-realtime, x86_64: installed librealsense2-dkms/1.3.24, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Ti Mobile] [17aa:3a3e] InstallationDate: Installed on 2023-08-19 (92 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 82B5 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1050-realtime root=UUID=6579ad60-9e6c-4896-b43a-3edc631af107 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnINVALID:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_IDEAPAD dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO 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/+bug/2043966/+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 2043755] Re: Screen show garbage when shrinking window from maximized window in Xorg
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Tags added: jammy -- 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/2043755 Title: Screen show garbage when shrinking window from maximized window in Xorg Status in OEM Priority Project: New Status in mutter package in Ubuntu: New Bug description: The Windows is flickering when shrinking from maximized window in Xorg session. The issue won't happen if I disable animation in g-c-c > Accesibility > Enable Animations. Description:Ubuntu 22.04.3 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2043755/+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 2043942] Re: Primary screen does not resume (post power management)
** Package changed: xorg (Ubuntu) => marco (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/2043942
Title:
Primary screen does not resume (post power management)
Status in marco package in Ubuntu:
New
Bug description:
On a laptop with a HDMI screen plugged (using same image on all monitors):
It seems that after power management feature kicks in (in my case a blank
screen) and actions are resumed that the original (laptop) screen remains with
a full light grey and is unusable.
Recreation steps:
1. plug in a hdmi monitor into the hdmi plug of your laptop;
2. while the laptop remains charged+plugged in the wall watch something with
celluloid then resume in 2+ hours;
3. on external screen: full working desktop with mouse cursor and colors;
on laptop screen: full light grey screen, no life
nb: by totally unplugging (power and hdmi cable) the laptop it screen remains
unusable but TTY1-6 will work.
By replugging both cables the desktop will again show on the external screen
but laptop screen will remain unusable.
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
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Nov 19 15:45:00 2023
DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [103c:87b7]
InstallationDate: Installed on 2023-02-23 (270 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=3e40054f-c010-4c20-834b-badb6d17cf88 ro splash splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (38 days ago)
dmi.bios.date: 12/29/2022
dmi.bios.release: 15.67
dmi.bios.vendor: AMI
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.21
dmi.modalias:
dmi:bvnAMI:bvrF.67:bd12/29/2022:br15.67:efr28.21:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.21:cvnHP:ct10:cvrChassisVersion:sku10M11UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 10M11UA#ABL
dmi.sys.vendor: HP
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/marco/+bug/2043942/+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 2043944] Re: WISHLIST-Make MOD+LEFT|RIGHT great
** Package changed: xorg (Ubuntu) => marco (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/2043944
Title:
WISHLIST-Make MOD+LEFT|RIGHT great
Status in marco package in Ubuntu:
New
Bug description:
Dear Santa,
This year I have been augmenting my TTY7 keyboard skillz and in that
respect the MOD+arrow key resizing capabilities.
As we know pressing MOD+right arrow shall flawlessly redraw the
currently selected window into half of the right side of the screen.
Based on my user expertise each and every time I invoke it I always
always always end up having to ALT+TAB to another window that I will
then MOD+left arrow to complement it. And so that I can see both
windows simultaneously.
My wish for this year is to automate the ALT+TAB part yet I have to
ask if this a X feature or if it's a MATE feature or ...? In that
respect this as a xorg bug.
But back to the problem: Redmond has got this feature implemented
already on their end. From our end it just currently looks like it's
halfway implemented. If not made a default behavior then for sure
there should be a way to allow the automated resizing of a 2nd screen
once any combination of the MOD+arrow keys will have been typed.
Cheers,
'lil Dan
PS: by "MOD" I mean the "windoze key" AKA MOD4?
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
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Nov 19 15:55:14 2023
DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [103c:87b7]
InstallationDate: Installed on 2023-02-23 (270 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=3e40054f-c010-4c20-834b-badb6d17cf88 ro splash splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (38 days ago)
dmi.bios.date: 12/29/2022
dmi.bios.release: 15.67
dmi.bios.vendor: AMI
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.21
dmi.modalias:
dmi:bvnAMI:bvrF.67:bd12/29/2022:br15.67:efr28.21:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.21:cvnHP:ct10:cvrChassisVersion:sku10M11UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 10M11UA#ABL
dmi.sys.vendor: HP
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/marco/+bug/2043944/+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 2044061] Re: Vertical and horizontal lines appearing since update
Note: changing to xorg from wayland fixed the issue; the issue is something with wayland. -- 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/2044061 Title: Vertical and horizontal lines appearing since update Status in xorg package in Ubuntu: New Bug description: Did sudo apt update && upgrade, now getting vertical and horizontal visual artifacts -Tried installing amd drivers -Tried using an older kernel Still no luck; definitely 100% not a hardware issue, machine is dual boot and they do not appear on the windows side. It's related to the update. It occurs particularly frequently if I'm writing code or moving windows around. Attaching a picture to try and show it (it's hard to catch on pictures and I don't think it shows up in a screen shot). It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 21:30:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (21 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.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: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd 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 N/A 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/2044061/+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 2043716] Re: Desktop freezing and slowing down when multiple apps running
Thanks for the bug report. When the system is slow please run: free -h > free.txt ps aux --sort -rss > ps.txt and attach the resulting text files here. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2043716 Title: Desktop freezing and slowing down when multiple apps running Status in Ubuntu: Incomplete Bug description: This machine is being used a lot to cast to Chromecast using Chromium. Some days Chromium is regularly freezing every 10 minutes or so. It is necessary to restart the computer to get casting again. Regularly, the freeze causes the "force close" or "wait" pop up to appear. If I am quick to react, I can quit Chromium and a reboot gets things going again. But if I am too slow, sometimes the whole desktop freezes including the mouse and I need to Alt-SysRq+B. If I am casting and during a boring bit I want to check my emails, then running Thunderbird causes the whole system to slow down, and the casting to reduce resolution and only update the screen every 10 seconds or so. Please let me know if there is anything I can do to help diagnose the problem. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10.1-lowlatency 6.5.3 Uname: Linux 6.5.0-10-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 17:52:42 2023 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-11-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2043716/+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 2044061] [NEW] Vertical and horizontal lines appearing since update
Public bug reported: Did sudo apt update && upgrade, now getting vertical and horizontal visual artifacts -Tried installing amd drivers -Tried using an older kernel Still no luck; definitely 100% not a hardware issue, machine is dual boot and they do not appear on the windows side. It's related to the update. It occurs particularly frequently if I'm writing code or moving windows around. Attaching a picture to try and show it (it's hard to catch on pictures and I don't think it shows up in a screen shot). It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 21:30:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (21 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.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: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd 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 N/A 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 corruption jammy ubuntu wayland-session ** Attachment added: "PXL_20231121_053102394.TS_exported_4862_1700544704921.jpg" https://bugs.launchpad.net/bugs/2044061/+attachment/5721492/+files/PXL_20231121_053102394.TS_exported_4862_1700544704921.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/2044061 Title: Vertical and horizontal lines appearing since update Status in xorg package in Ubuntu: New Bug description: Did sudo apt update && upgrade, now getting vertical and horizontal visual artifacts -Tried installing amd drivers -Tried using an older kernel Still no luck; definitely 100% not a hardware issue, machine is dual boot and they do not appear on the windows side. It's related to the update. It occurs particularly frequently if I'm writing code or moving windows around. Attaching a picture to try and show it (it's hard to catch on pictures and I don't think it shows up in a screen shot). It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop:
[Desktop-packages] [Bug 2043598] Re: A vertical strip on the screen is unresponsive or does not allow iteration
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 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 2012388, 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 2012388 X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks -- 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/2043598 Title: A vertical strip on the screen is unresponsive or does not allow iteration Status in xorg package in Ubuntu: New Bug description: A fraction of the screen, located on the right side of the entire vertical, that is, from the minimize, restore and maximize buttons to the bottom of the screen, the click action (single or double) does not work. Today I am forced to make the window smaller to be able to close it, for example. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 12:50:44 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0792] InstallationDate: Installed on 2023-11-03 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=b18f1fb8-30b8-49f3-81fe-227de68fb188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2019 dmi.bios.release: 3.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.3.0 dmi.board.name: 02HKXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.3.0:bd01/17/2019:br3.3:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn02HKXD:rvrA00:cvnDellInc.:ct9:cvr:sku0792: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.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/2043598/+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 2043529] Re: HDMI port issues after ubuntu 23 upgrade
It appears the Nvidia Xorg driver can't find any devices. But also the Nvidia driver 545 you have is not officially supported by Ubuntu. Please use the 'Additional Drivers' app to install a supported driver, then reboot and open new bugs for any problems you find. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2043529 Title: HDMI port issues after ubuntu 23 upgrade Status in Ubuntu: Invalid Bug description: Hdmi port will not recognize external display after lunar lobster install. This issue was verified by upgrading my desktop to lunar lobster that had 22.10 previously installed. The desktop has 3 monitors working before the upgrade. After the upgrade only one monitor will work. I have attempted to trouble shoot the issue but am leaning towards a bug at this point. The thunderbolt works for displaying however I am unable to get the hdmi to recognize any connection. The port is working and was verified by windows that is dual booted on this laptop. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.02 Thu Oct 26 21:21:38 UTC 2023 GCC version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04) ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 18:29:03 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-27-generic, x86_64: installed nvidia/545.29.02, 6.2.0-27-generic, x86_64: installed rtl8812AU/#MODULE_VERSION#: added virtualbox/7.0.6, 6.2.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2023-02-21 (266 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=47692d38-dda2-45e4-b8f9-eb478775c1fe ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0CDJF9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0CDJF9:rvrA01:cvnDellInc.:ct10:cvr:sku087D: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.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/+bug/2043529/+subscriptions
[Desktop-packages] [Bug 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)
Thanks for the bug report. Please also report the issue upstream at
https://gitlab.gnome.org/GNOME/mutter/-/issues
** Tags added: jammy
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
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/2043517
Title:
gnome-shell on non-active VT busy-loops through libwayland-server.so
(sometimes)
Status in mutter package in Ubuntu:
New
Bug description:
I run several gnome sessions at once - different users on different
Virtual Terminals.
Sometimes, gnome-shell for a non-active VT starts using 100% CPU. Or,
actually 99% CPU because it's doing IPC as well. And the
corresponding XWayland uses 40% CPU.
FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
other one from busy-looping as well.
If I switch back to the affected VT, it appears to function fine, but
it is still using 100% + 40% CPU.
Version numbers:
Ubuntu 22.04.3 LTS
gnome-shell 42.9-0ubuntu2
xwayland 2:22.1.1-1ubuntu0.7
$ ps -aux | grep 'alan .*gnome-shell$'
alan9248 26.1 3.4 5492888 269136 ? Rsl 19:54 30:26
/usr/bin/gnome-shell
$ sudo strace -p 9248 2>&1|head
strace: Process 9248 attached
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
recvmsg(21, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\1\0\0\0\0\0\f\0\3\0\0\0", iov_len=752}, {iov_base="",
iov_len=3344}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC},
MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
sendmsg(21, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\3\0\0\0\0\0\f\0[\2\0\0\1\0\0\0\1\0\f\0\3\0\0\0",
iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0},
MSG_DONTWAIT|MSG_NOSIGNAL) = 24
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN},
{fd=19, events=POLLIN}, {fd=20, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24,
events=POLLIN}, {fd=25, events=POLLIN}, {fd=34, events=POLLIN}, {fd=36,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=54, events=POLLIN}, {fd=63,
events=POLLIN}, {fd=66, events=POLLIN}], 14, 79809702) = 2 ([{fd=4,
revents=POLLIN}, {fd=37, revents=POLLIN}])
read(4, "\2\0\0\0\0\0\0\0", 16) = 8
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
The recvmsg() call is here:
#0 __libc_recvmsg (fd=21, msg=0x7fff1de64a50, flags=1073741888) at
../sysdeps/unix/sysv/linux/recvmsg.c:35
#1 0x7f2531ea5ad6 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#2 0x7f2531ea4eea in wl_event_loop_dispatch () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#3 0x7f2531d2b45b in wayland_event_source_dispatch (base=, callback=, data=)
at ../src/wayland/meta-wayland.c:110
#4 0x7f2532b42d3b in g_main_dispatch (context=0x55c0046cc8f0) at
../../../glib/gmain.c:3419
#5 g_main_context_dispatch (context=0x55c0046cc8f0) at
../../../glib/gmain.c:4137
#6 0x7f2532b98258 in g_main_context_iterate.constprop.0
(context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../../../glib/gmain.c:4213
#7 0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at
../../../glib/gmain.c:4413
#8 0x7f2531cd0b79 in meta_context_run_main_loop
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
at ../src/core/meta-context.c:437
#9 0x55c003cf4f12 in main (argc=, argv=)
at ../src/main.c:650
The sendmsg() call is here:
Thread 1 "gnome-shell" hit Breakpoint 1, __libc_sendmsg (fd=21,
msg=0x7fff1de64c50, flags=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:26
26../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
(gdb) where
#0 __libc_sendmsg (fd=21, msg=0x7fff1de64c50, flags=16448) at
../sysdeps/unix/sysv/linux/sendmsg.c:26
#1 0x7f2531ea1c9d in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#2 0x7f2531ea565e in wl_display_flush_clients () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#3 0x7f2531d2b437 in wayland_event_source_prepare
(base=base@entry=0x55c004a374d0, timeout=timeout@entry=0x7fff1de64dc4)
at ../src/wayland/meta-wayland.c:97
#4 0x7f2532b428e7 in g_main_context_prepare (context=0x55c0046cc8f0,
priority=0x7fff1de64e50) at ../../../glib/gmain.c:3739
#5 0x7f2532b98123 in g_main_context_iterate.constprop.0
(context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../../../glib/gmain.c:4193
#6 0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at
../../../glib/gmain.c:4413
#7 0x7f2531cd0b79 in meta_context_run_main_loop
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
at ../src/core/meta-context.c:437
#8 0x55c003cf4f12 in main (argc=,
[Desktop-packages] [Bug 2043462] Re: after the sleeping mod, the login process takes a loooong time. Also, pages get freezed.
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 This sounds most like bug 1876632. Generally I'd recommend not putting an Nvidia desktop to sleep because of that. ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/2043462 Title: after the sleeping mod, the login process takes a lng time. Also, pages get freezed. Status in gnome-shell package in Ubuntu: Incomplete Bug description: after login one of the monitors is not turning on, in case the monitor turns on, it looks like fizzed. it take a looong time to get PC work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 14:55:52 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-03 (255 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2043462/+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
Hello Atlas, Thank you for your comment. Yes, i can understand that Ubuntu 24.04 will have this changes but i think Ubuntu 22.04 LTS end of life is till 2027. May I know, if there is any concern backporting this changes in Ubuntu 22.04 LTS ? Regarding this feature - We are currently using AT mechanism and its working fine. If this patch is backported then we can use MBIM mechanism and since mbim mechanism is safer . So , Intel has suggested us earlier to use it. As of now , i haven't receive any issue like AT port occupied issue etc with AT mechanism but just to be cautious, we had requested it long back. Thank you !! -- 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: Confirmed 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 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
The "desktop-icons" extension is deprecated and was replaced by "desktop-icons-ng", so this isn't really relevant to the former. For newer releases it seems to be marked as fixed already so I suggest opening a new bug. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: In Progress => Won't Fix ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu) -- 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/1723117 Title: Desktop icons goes under the Dock, if the Dock is set to auto-hide. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: This bug is found in Artful. Desktop icons goes under the Dock, if the Dock is set to auto-hide. Either the Dock should auto-hide on the Desktop as well, or the Desktop Icons should leave a margin with the same size of the Dock. This happen both horizontal and vertical Dock positions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1723117/+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 1717878] Re: gdm3/gdm-session-worker crashed with SIGTRAP logging "GdmSession: no session desktop files installed, aborting..." from get_fallback_session_name from get_default_
** Bug watch added: Debian Bug tracker #918984 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918984 ** Also affects: fuse (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918984 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1717878 Title: gdm3/gdm-session-worker crashed with SIGTRAP logging "GdmSession: no session desktop files installed, aborting..." from get_fallback_session_name from get_default_session_name from get_session_name from get_session_filename from gdm_session_is_wayland_session Status in fuse package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Triaged Status in fuse package in Debian: Unknown Bug description: https://errors.ubuntu.com/problem/b8e7721d0034b2c4a5ddafcac2e1cc55703f9dbd https://errors.ubuntu.com/problem/55afdb022e0f09e32692656f5ec80985acf385cc https://errors.ubuntu.com/problem/f4fce39ac75fb4f87b243f14cb5f8e72f90c2c0f --- This crash occurs when you uninstall all session files (by accident) from the system. One common way this can happen is by trying to install 'fuse'. To fix it just run: sudo apt install --reinstall ubuntu-session or whatever-session for your preferred Ubuntu flavor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1717878/+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 2044043] [NEW] package cups-ppdc 2.3.1-9ubuntu1.2 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2
Public bug reported: While upgrading procedure abort ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-ppdc 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: libx11-6:amd64: Install cups-filters:amd64: Install cups-ppdc:amd64: Install libavahi-glib1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 20 22:33:42 2023 ErrorMessage: el subproceso dpkg-deb --control devolvió el código de salida de error 2 InstallationDate: Installed on 2023-11-21 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: EXO Ready C2 - Style C2 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: cups Title: package cups-ppdc 2.3.1-9ubuntu1.2 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: H310CH5-M2 dmi.board.vendor: EXO dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EXO dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629: dmi.product.family: Ready - Style dmi.product.name: Ready C2 - Style C2 dmi.product.sku: 3629 dmi.product.version: 1.0 dmi.sys.vendor: EXO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2044043 Title: package cups-ppdc 2.3.1-9ubuntu1.2 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2 Status in cups package in Ubuntu: New Bug description: While upgrading procedure abort ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-ppdc 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: libx11-6:amd64: Install cups-filters:amd64: Install cups-ppdc:amd64: Install libavahi-glib1:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 20 22:33:42 2023 ErrorMessage: el subproceso dpkg-deb --control devolvió el código de salida de error 2 InstallationDate: Installed on 2023-11-21 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: EXO Ready C2 - Style C2 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: cups Title: package cups-ppdc 2.3.1-9ubuntu1.2 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
** Changed in: gnome-control-center Status: New => 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact the settings segfault when trying to set up a livepatch account * Test case $ gnome-control-center info-overview $ gnome-control-center online-accounts add google -> shouldn't segfault check also for error reports on https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 * Regression potential the change could introduce a small leak, that's better than a segfault though --- problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+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 2044038] [NEW] package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: While updating ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Nov 20 22:14:16 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libx11-6:2:1.6.9-2ubuntu1.2 Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems UHD Graphics 630 (Desktop 9 Series) [1019:a55d] InstallationDate: Installed on 2023-11-21 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: EXO Ready C2 - Style C2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libx11 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: H310CH5-M2 dmi.board.vendor: EXO dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EXO dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629: dmi.product.family: Ready - Style dmi.product.name: Ready C2 - Style C2 dmi.product.sku: 3629 dmi.product.version: 1.0 dmi.sys.vendor: EXO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/2044038 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 Status in libx11 package in Ubuntu: New Bug description: While updating ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Nov 20 22:14:16 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libx11-6:2:1.6.9-2ubuntu1.2 Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer
[Desktop-packages] [Bug 2044040] [NEW] package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: bugs while updating ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1.6 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Nov 20 22:14:16 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libx11-6:2:1.6.9-2ubuntu1.2 Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems UHD Graphics 630 (Desktop 9 Series) [1019:a55d] InstallationDate: Installed on 2023-11-21 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: EXO Ready C2 - Style C2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libx11 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: H310CH5-M2 dmi.board.vendor: EXO dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EXO dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629: dmi.product.family: Ready - Style dmi.product.name: Ready C2 - Style C2 dmi.product.sku: 3629 dmi.product.version: 1.0 dmi.sys.vendor: EXO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/2044040 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 Status in libx11 package in Ubuntu: New Bug description: bugs while updating ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1.6 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Nov 20 22:14:16 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libx11-6:2:1.6.9-2ubuntu1.2 Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Elitegroup
[Desktop-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
I tested it again, and at the moment I reproduce this issue with a
xwayland window (in this case, Discord app), but all gnome was stable,
which is strange (but good). See screenshot attached.
** Attachment added: "Captura desde 2023-11-21 00-42-42.png"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038998/+attachment/5721350/+files/Captura%20desde%202023-11-21%2000-42-42.png
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
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 denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
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
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/gnome-shell/+bug/2038998/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
** Changed in: linux
Status: Unknown => 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:
Confirmed
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 2044027] Re: keyboard , mouse and black screen after rebooting on ubuntu os only
** Description changed:
For input devices : gnome-shell
For rebooting process : init system
- the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times and
both keyboard and mouse internal doesnot work on start screen , at the end
when performing a reboot after rebooting my device it appears on my screen a
black screen resulting to turning off from the btn on my laptop always this
incident happens with me and only on ubuntu 16.04 and later systems the
problem occurs while on windows os the problem does not occur any more
(rebooting keyboard and mouse "internal")
- note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
+ the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
+ At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
+
+ note : secondary storage ,optical disks external devices like keyboard
+ are working fine on ubuntu systems with all versions and all other os
+ including windows os
--
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/2044027
Title:
keyboard , mouse and black screen after rebooting on ubuntu os only
Status in gnome-shell package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard
are working fine on ubuntu systems with all versions and all other os
including windows os
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044027/+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 2044027] [NEW] keyboard , mouse and black screen after rebooting on ubuntu os only
Public bug reported:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell desktop
environment (ubuntu-desktop) the below message appears twice times and both
keyboard and mouse internal doesnot work on start screen , at the end when
performing a reboot after rebooting my device it appears on my screen a black
screen resulting to turning off from the btn on my laptop always this incident
happens with me and only on ubuntu 16.04 and later systems the problem occurs
while on windows os the problem does not occur any more (rebooting keyboard
and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond end
of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- TFor input devices : gnome-shell
- For rebooting process : init system
+ For input devices : gnome-shell
+ For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times and
both keyboard and mouse internal doesnot work on start screen , at the end
when performing a reboot after rebooting my device it appears on my screen a
black screen resulting to turning off from the btn on my laptop always this
incident happens with me and only on ubuntu 16.04 and later systems the
problem occurs while on windows os the problem does not occur any more
(rebooting keyboard and mouse "internal")
- note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
+ note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
--
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/2044027
Title:
keyboard , mouse and black screen after rebooting on ubuntu os only
Status in gnome-shell package in Ubuntu:
New
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times and
both keyboard and mouse internal doesnot work on start screen , at the end
when performing a reboot after rebooting my device it appears on my screen a
black screen resulting to turning off from the btn on my laptop always this
incident happens with me and only on ubuntu 16.04 and later systems the
problem occurs while on windows os the problem does not occur any more
(rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard are
working fine on ubuntu systems with all versions and all other os including
windows os
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044027/+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 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Hi,
if it is of any help, this problem occurs primarily in GNOME for me.
With XFCE and i3 I tried it as well and there the tablet works fine.
The stylus press freezes the cursor and when I then move the mouse it
appears as if it was still pressing down.
Happy to produce any logfiles to debug this, but I do not know how.
Advise appreciated.
Best,
Rüdiger
--
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/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Tablet seems to work until I open Krita (as I could read on Internet,
it may be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
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.nvidia-graphics-drivers:
[Desktop-packages] [Bug 2041716] Re: [SRU] libreoffice 7.5.8 for lunar
** Description changed: [Impact] * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release - * Version 7.5.5 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of 21 bugs): + * Version 7.5.7 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of 21 bugs): https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs 7.5.8 RC2 is identical to the 7.5.8 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1762/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15348703/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231029_113409_73daf@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231029_195903_c198a@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/armhf/libr/libreoffice/20231029_204848_b6986@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231029_113020_49f1b@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231029_131951_9ac3d@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 21 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/2041716 Title: [SRU] libreoffice 7.5.8 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Committed Bug description: [Impact] * LibreOffice 7.5.8 is in its eighth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.8_release * Version 7.5.7 is currently released in lunar. For a list of fixed bugs compared to 7.5.7 see the list of bugs fixed in the release candidates of 7.5.8 (that's a total of 21 bugs): https://wiki.documentfoundation.org/Releases/7.5.8/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.8/RC2#List_of_fixed_bugs 7.5.8 RC2 is identical to the 7.5.8 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1762/ * More information about the upstream QA testing can be found here: * Automated tests
[Desktop-packages] [Bug 2044019] [NEW] [SRU] libreoffice 7.6.3 for mantic
Public bug reported: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 115+ bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1459/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15389862/+listing-archive-extra * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [riscv64] not available * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 115+ bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu Mantic) Importance: Medium Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu Mantic) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Mantic) Status: New => In Progress -- 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/2044019 Title: [SRU] libreoffice 7.6.3 for mantic Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Mantic: In Progress Bug description: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 115+ bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1459/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice
[Desktop-packages] [Bug 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.
It's still happening on 23.10 -- 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/1723117 Title: Desktop icons goes under the Dock, if the Dock is set to auto-hide. Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: This bug is found in Artful. Desktop icons goes under the Dock, if the Dock is set to auto-hide. Either the Dock should auto-hide on the Desktop as well, or the Desktop Icons should leave a margin with the same size of the Dock. This happen both horizontal and vertical Dock positions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1723117/+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 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
(had to remove a lot of auto-uploaded files due to privacy) relevant loglines from syslog attached. ** Attachment added: "syslog.log.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721253/+files/syslog.log.txt -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: New Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+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 2044014] [NEW] networkmanager crashes on configuring wireguard connection via nm-connection-editor
Public bug reported: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages ** Description changed: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: - default via 10.10.13.254 dev enp0s31f6 proto dhcp src 10.10.13.150 metric 100 - 10.10.13.0/24 dev enp0s31f6 proto kernel scope link src 10.10.13.150 metric 100 - 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 + default via dev enp0s31f6 proto dhcp src metric 100 + /24 dev enp0s31f6 proto kernel scope link src metric 100 + 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=false - WWANEnabled=false + [main] + NetworkingEnabled=true + WirelessEnabled=false + WWANEnabled=false ProcEnviron: - LANG=de_DE.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color + LANG=de_DE.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) - http_proxy: http://10.10.0.254:3128 + http_proxy: http://:3128 nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.44.2 connected started full enabled enabled disabled missing disabled - no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,*.home.bastolino.de,*.net.b9r.it + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.44.2 connected started full enabled enabled disabled missing disabled + no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, ** Attachment removed: "IpAddr.txt"
[Desktop-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Here, there's an issue opened in Gitlab Gnome about mutter that could be
related to this issue (thanks again to Michel Dänzer):
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3036
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:
Unknown
Status in linux package in Ubuntu:
Confirmed
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 1973084] Please test proposed package
Hello aramaicus, or anyone else affected, Accepted transmission into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/transmission/3.00-2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 1973084] Re: transmission-daemon high RAM usage
Hello aramaicus, or anyone else affected, Accepted transmission into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/transmission/3.00-2.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: transmission (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-lunar ** Changed in: transmission (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2038557] Re: Update gtk4 to 4.12.3
This bug was fixed in the package gtk4 - 4.12.3+ds-1ubuntu0.1 --- gtk4 (4.12.3+ds-1ubuntu0.1) mantic; urgency=medium * Merge with Debian (LP: #2038557). Remaining changes: - debian/tests: + include the memorytexture test in the flaky set, it has been unreliable - debian/control: + Build-Depend on dh-sequence-translations - Switch from the CUPS print backend to CPDB -- Amin Bandali Thu, 05 Oct 2023 11:27:16 -0400 ** Changed in: gtk4 (Ubuntu Mantic) Status: Fix Committed => 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/2038557 Title: Update gtk4 to 4.12.3 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Mantic: Fix Released Bug description: There is a new point release in the stable GTK 4.12 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.12.3/NEWS The version currently in Ubuntu 23.10 is 4.12.2 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2038557/+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 2038557] Update Released
The verification of the Stable Release Update for gtk4 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 gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2038557 Title: Update gtk4 to 4.12.3 Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Mantic: Fix Released Bug description: There is a new point release in the stable GTK 4.12 series. https://gitlab.gnome.org/GNOME/gtk/-/blob/4.12.3/NEWS The version currently in Ubuntu 23.10 is 4.12.2 Test Case 0 --- gtk4 has an extensive build test suite, and failures will fail the build. gtk4 also has thorough autopkgtests. Ensure that the build succeeds and that the autopgktests pass. Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok Test Case 3 --- Install and test gtk4-demo (from the gtk-4-examples package) as well as a few other GTK/GNOME applications like nautilus and gnome-text-editor, and verify that they continue to launch and work as expected. What Could Go Wrong --- Many of the default Ubuntu 23.10 desktop apps use GTK4. A serious enough regression could severely break the Ubuntu Desktop. Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg-desktop-portal-gtk which uses GTK3, so are not affected by this SRU. gtk4 is included in the GNOME micro release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2038557/+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 1958019]
What about Lenovo Legion Slim 7 Gen 8 2023 ? does sound works ? i've seen that work will be mainlined as said in the comment 774 but when ? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2043236] Re: [Latitude 7440, Realtek ALC289, top speakers and headphones play at same time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/2043236 Title: [Latitude 7440, Realtek ALC289, top speakers and headphones play at same time Status in alsa-driver package in Ubuntu: Confirmed Bug description: The laptop has 2 speakers on the bottom and 2 speakers on the top. When plugging headphones into the 3.5mm jack, the bottom speakers are auto-muted as they are supposed to be (confirmed this in alsamixer); the top speakers however continue to output sound- the headphones work fine, but the top speakers play at the same time. If you go into alsamixer to play with levels, you will note that changing "headphones" volume also changes the volume of the speakers on the top. In fact, even with the headphones unplugged, alsamixer shows a "headphones" section (which will control top speaker volume). The bottom speakers which are muted properly are called "Speakers" in alsamixer. It seems this is a pin issue- it seems that the headphones and the top speakers are linked in some way. The headphone plug action properly mutes all speakers on Windows 11, so this seems to be a software issue. In case it helps: I have reproduced this behavior on Ubuntu 23.10's live installer, and also on Fedora 39 Workstation's live installer. My Ubuntu 22.04 install is completely up-to-date. 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 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: poeticrpm 1781 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 10 14:17:20 2023 InstallationDate: Installed on 2023-10-06 (35 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_Type: None of the above Title: [Latitude 7440, Realtek ALC289, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0NDV55 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd09/12/2023:br1.8:efr1.6:svnDellInc.:pnLatitude7440:pvr:rvnDellInc.:rn0NDV55:rvrA00:cvnDellInc.:ct10:cvr:sku0C0B: dmi.product.family: Latitude dmi.product.name: Latitude 7440 dmi.product.sku: 0C0B dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-11-10T13:48:00.967491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2043236/+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 2043462] Re: after the sleeping mod, the login process takes a loooong time. Also, pages get freezed.
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043462/+attachment/5721203/+files/journal.txt -- 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/2043462 Title: after the sleeping mod, the login process takes a lng time. Also, pages get freezed. Status in gnome-shell package in Ubuntu: Incomplete Bug description: after login one of the monitors is not turning on, in case the monitor turns on, it looks like fizzed. it take a looong time to get PC work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 14:55:52 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-03 (255 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2043462/+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 2036422] Re: XWayland cannot click fullscreen window beyond 1024x768
need update to Ubuntu 23.10 ** Changed in: xwayland (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2036422 Title: XWayland cannot click fullscreen window beyond 1024x768 Status in xwayland package in Ubuntu: Fix Released Bug description: When I click in any xwayland window beyond the top-left 1024x768 rectangle, the window below is clicked. Expected result: The xwayland window registers the click Actual result: The xwayland window registers the click correctly only in the top left 1024x768 pixels rectangle. lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 apt-cache policy xwayland xwayland: Installed: 2:22.1.8-1ubuntu1 Candidate: 2:22.1.8-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 14:13:07 2023 InstallationDate: Installed on 2023-08-01 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2036422/+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 2036422] Re: XWayland cannot click fullscreen window beyond 1024x768
This bug is fully resolved by update to Ubuntu 23.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2036422 Title: XWayland cannot click fullscreen window beyond 1024x768 Status in xwayland package in Ubuntu: Fix Released Bug description: When I click in any xwayland window beyond the top-left 1024x768 rectangle, the window below is clicked. Expected result: The xwayland window registers the click Actual result: The xwayland window registers the click correctly only in the top left 1024x768 pixels rectangle. lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 apt-cache policy xwayland xwayland: Installed: 2:22.1.8-1ubuntu1 Candidate: 2:22.1.8-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 14:13:07 2023 InstallationDate: Installed on 2023-08-01 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2036422/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
Tested with COGL_DEBUG parameter added and at the moment, I can't
reproduce these artifacts. I will keep trying it today.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
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 denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
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
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/gnome-shell/+bug/2038998/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
Had the same problem, trying to sign documents with libreoffice, and used the same method to set the certificates store path in libreoffice (tools / options / security / certificate button, and set the path (manual) to: ~/.pki/nssdb Now I can manage my certificates with google chrome (no snap version); firefox and thunderbird and chromium snap have their own certificate databases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+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 1875717] Re: Opening file from Samba share results in Document in Use
Hi! I'm having this problem in Lubuntu 23.10, but the solution ain't working for me! Maybe i'm doing something wrong... can anyone advise? Thanks! -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 2043462] Re: after the sleeping mod, the login process takes a loooong time. Also, pages get freezed.
Please log in, reproduce the bug and then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2043462 Title: after the sleeping mod, the login process takes a lng time. Also, pages get freezed. Status in gnome-shell package in Ubuntu: Incomplete Bug description: after login one of the monitors is not turning on, in case the monitor turns on, it looks like fizzed. it take a looong time to get PC work correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 14:55:52 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-03 (255 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2043462/+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 2043331] Re: Mouse pointer bug on Intel N2600 (Cedarview)
** Summary changed:
- Mouse pointer bug on Intel Corporation Atom Processor D2xxx/N2xxx Integrated
Graphics Controller
+ Mouse pointer bug on Intel N2600 (Cedarview)
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Mouse pointer bug on Intel N2600 (Cedarview)
+ [gma500] Mouse pointer bug on Intel N2600 (Cedarview)
--
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/2043331
Title:
[gma500] Mouse pointer bug on Intel N2600 (Cedarview)
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
If you press a button in a window that doesn't close the window and
doesn't change the area under the button, you get half an fake mouse
pointer on the area of the mouse pointer that was clicked. If you move
the correct mouse pointer over the fake mouse pointer, it disappears.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
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
NonfreeKernelModules: wl
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 20:31:10 2023
DistUpgraded: 2023-11-12 20:22:28,705 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus:
broadcom-sta/6.30.223.271, 6.5.0-10-generic, x86_64: installed
broadcom-sta/6.30.223.271, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
[8086:0be1] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Atom Processor D2xxx/N2xxx Integrated
Graphics Controller [1025:0624]
InstallationDate: Installed on 2023-11-12 (0 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.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=b67dae3e-d7cf-4a05-a809-18bc61b127ea ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2023-11-12 (0 days ago)
dmi.bios.date: 07/23/2013
dmi.bios.release: 10.240
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJE01_CT
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.10:bd07/23/2013:br10.240:svnPackardBell:pndots:pvrV1.10:rvnPackardBell:rnSJE01_CT:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:skuType1Sku0:
dmi.product.family: Type1Family
dmi.product.name: dot s
dmi.product.sku: Type1Sku0
dmi.product.version: V1.10
dmi.sys.vendor: Packard Bell
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.116-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:22.0.0-1
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/linux/+bug/2043331/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken
Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libmutter-12-0:amd64 < 44.3-0ubuntu1.1 @ii mK Ib > Broken libmutter-12-0:amd64 Depends on mutter-common-bin:amd64 < 44.3-0ubuntu1.1 -> 45.0-3ubuntu3.1 @ii umU > (= 44.3-0ubuntu1.1) Considering mutter-common-bin:amd64 3 as a solution to libmutter-12-0:amd64 -1 Removing libmutter-12-0:amd64 rather than change mutter-common-bin:amd64 MarkDelete libmutter-12-0:amd64 < 44.3-0ubuntu1.1 @ii mK Ib > FU=0 Investigating (0) gir1.2-mutter-12:amd64 < 44.3-0ubuntu1.1 @ii mK Ib > Broken gir1.2-mutter-12:amd64 Depends on libmutter-12-0:amd64 < 44.3-0ubuntu1.1 @ii mR > (= 44.3-0ubuntu1.1) Considering libmutter-12-0:amd64 -1 as a solution to gir1.2-mutter-12:amd64 -2 Removing gir1.2-mutter-12:amd64 rather than change libmutter-12-0:amd64 MarkDelete gir1.2-mutter-12:amd64 < 44.3-0ubuntu1.1 @ii mK Ib > FU=0 Investigating (0) libavcodec59:amd64 < 7:5.1.2-3ubuntu1 @ii mK Ib > Broken libavcodec59:amd64 Depends on libswresample4:amd64 < 7:5.1.2-3ubuntu1 -> 7:6.0-6ubuntu1 @ii umU > (= 7:5.1.2-3ubuntu1) Considering libswresample4:amd64 4 as a solution to libavcodec59:amd64 -2 Removing libavcodec59:amd64 rather than change libswresample4:amd64 MarkDelete libavcodec59:amd64 < 7:5.1.2-3ubuntu1 @ii mK Ib > FU=0 ** Tags added: lunar mantic ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2043395 Title: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken Status in gnome-shell package in Ubuntu: New Bug description: Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal based** install: 2023-11-10 07:03:16,578 DEBUG nvidiaUpdate() 2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new 2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache 2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache 2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with 2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35 2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36 2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after upgrade: gnome-remote-desktop, gnome-shell' 2023-11-10 07:03:20,564 DEBUG abort called To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043321] Re: intel ekran kartı çalışmıyor (Intel graphics card not working)
Thanks for the bug report. I don't see any evidence of the driver not working but I'm reminded of bug 2037497. Do you have any files in /var/crash ? What makes you think the drivers are not working? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2043321 Title: intel ekran kartı çalışmıyor (Intel graphics card not working) Status in Ubuntu: Incomplete Bug description: intel ekran kartı çalışmıyor hatalı sürücüler var Google translates as: Intel graphics card is not working, there are faulty drivers ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 12 18:43:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:09e8] InstallationDate: Installed on 2023-11-12 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. Inspiron 14 5401 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2023 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.0 dmi.board.name: 06DNFY dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.0:bd09/19/2023:br1.25:svnDellInc.:pnInspiron145401:pvr:rvnDellInc.:rn06DNFY:rvrA02:cvnDellInc.:ct10:cvr:sku09E8: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5401 dmi.product.sku: 09E8 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 N/A 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/+bug/2043321/+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 2043255] Re: Wayland user session terminates when screen is disabled on inactivity
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
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 2034619, 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 2034619
[amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in
Wayland
--
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/2043255
Title:
Wayland user session terminates when screen is disabled on inactivity
Status in mutter package in Ubuntu:
New
Bug description:
Reproducibly, the user is logged out the moment the screen gets
disabled due to inactivity. Can be worked around by disabling the
"screen disabling on inactivity" feature in the system settings.
Issue started after upgrade from 23.04 to 23.10. Wayland is used.
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: Sat Nov 11 09:21:02 2023
DistUpgraded: 2023-11-03 18:23:57,803 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Lucienne [17aa:5097]
InstallationDate: Installed on 2021-08-27 (806 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=/boot/vmlinuz-6.5.0-10-generic
root=UUID=86fa7801-2441-4de0-bdff-28c460a157ee ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to mantic on 2023-11-03 (8 days ago)
dmi.bios.date: 05/17/2021
dmi.bios.release: 1.6
dmi.bios.vendor: LENOVO
dmi.bios.version: R1OET27W (1.06 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20YHS00A00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.6
dmi.modalias:
dmi:bvnLENOVO:bvrR1OET27W(1.06):bd05/17/2021:br1.6:efr1.6:svnLENOVO:pn20YHS00A00:pvrThinkPadE15Gen3:rvnLENOVO:rn20YHS00A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YH_BU_Think_FM_ThinkPadE15Gen3:
dmi.product.family: ThinkPad E15 Gen 3
dmi.product.name: 20YHS00A00
dmi.product.sku: LENOVO_MT_20YH_BU_Think_FM_ThinkPad E15 Gen 3
dmi.product.version: ThinkPad E15 Gen 3
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
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/mutter/+bug/2043255/+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 2043264] Re: External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) + [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2043264 Title: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: --- en Always, almost every time I turn on my notebook, my LG external monitor keeps blinking and it takes a while to actually connect to the notebook and the external monitor screen to turn on. For the external monitor to work I change the video settings using Ctrl + P and turn the monitor off/on several times. In Kubuntu it is recognized but when it blinks the system thinks the monitor is off. I'm using Kubuntu 23.04, I've used other distributions on the same hardware and this problem hasn't happened. I believe it's something with KDE. --- pt-br Sempre, quase toda vez que ligo meu notebook, meu monitor externo LG fica piscando e demora para realmente conectar ao notebook e a tela do monitor externo ligar. Para o monitor externo funcionar eu mudo as configurações de vídeo usando Ctrl + P e desligo/ligo o monitor várias vezes. No Kubuntu ele é reconhecido mas quando fica piscando o sistema acha que o monitor está desligado. Estou usando o Kubuntu 23.04, já usei outras distribuições no mesmo hardware e esse problema não aconteceu. Eu acredito que seja algo com o KDE. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 11 07:52:24 2023 DistUpgraded: 2023-11-02 07:28:00,578 DEBUG /openCache(), new cache size 78921 DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3804] InstallationDate: Installed on 2022-10-23 (383 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 81V7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=d72b8a6b-953f-4b38-8b0a-d1e9b6899ad2 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-11-02 (9 days ago) dmi.bios.date: 05/19/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: BUCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15API dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrBUCN25WW:bd05/19/2020:br1.25:efr1.25:svnLENOVO:pn81V7:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81V7_BU_idea_FM_IdeaPadS145-15API: dmi.product.family: IdeaPad S145-15API dmi.product.name: 81V7 dmi.product.sku: LENOVO_MT_81V7_BU_idea_FM_IdeaPad S145-15API dmi.product.version: Lenovo IdeaPad S145-15API dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.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/linux/+bug/2043264/+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 2043215] Re: Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.
** Tags added: wacom
** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput
(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/2043215
Title:
Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
Xorg.
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Bug description:
There is more information on this issue:
https://github.com/xournalpp/xournalpp/issues/5303
and the other bug report that is linked there.
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] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 10 07:17:22 2023
DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
InstallationDate: Installed on 2021-05-25 (899 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
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=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux
quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
dmi.bios.date: 12/21/2015
dmi.bios.release: 1.15
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.15
dmi.board.name: FJNB288
dmi.board.vendor: FUJITSU
dmi.board.version: D2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
dmi.product.name: LIFEBOOK T935
dmi.sys.vendor: FUJITSU
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/xserver-xorg-input-libinput/+bug/2043215/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
Please try adding COGL_DEBUG=disable-batching to /etc/environment and
then reboot.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
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 denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
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
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/gnome-shell/+bug/2038998/+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 2043976] [NEW] Default theme has white highlight and line number background
Public bug reported: Classic and Tango color scheme use white background color for the current line highlight box and the line number background. The problem is that the text stays white, making them hard to read. All of the other themes work perfectly and are easy to read. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gedit 46.1-3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 13:00:50 2023 InstallationDate: Installed on 2022-05-12 (557 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gedit UpgradeStatus: Upgraded to noble on 2023-08-14 (98 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble package-from-proposed wayland-session ** Attachment added: "Bug in action" https://bugs.launchpad.net/bugs/2043976/+attachment/5721148/+files/Screenshot%20from%202023-11-20%2013-05-33.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2043976 Title: Default theme has white highlight and line number background Status in gedit package in Ubuntu: New Bug description: Classic and Tango color scheme use white background color for the current line highlight box and the line number background. The problem is that the text stays white, making them hard to read. All of the other themes work perfectly and are easy to read. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gedit 46.1-3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 13:00:50 2023 InstallationDate: Installed on 2022-05-12 (557 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gedit UpgradeStatus: Upgraded to noble on 2023-08-14 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2043976/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
Thanks for the clarification, Daniel.
Could makes sense if it's related to Mesa. I have the feeling that these
strange artifacts, appear especially when I launch windows and apps from
the integrated graphics, instead of the dedicated.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
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 denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
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
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/gnome-shell/+bug/2038998/+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 2043538] Re: gnome-shell takes too much ram
This doesn't sound right. gnome-shell only uses a couple hundred megabytes of RAM by default. How are you measuring it? While the problem is happening, please run: ps auxw | grep gnome-shell > ps-gs.txt and attach the resulting text file here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: gnome-shell-leak -- 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/2043538 Title: gnome-shell takes too much ram Status in gnome-shell package in Ubuntu: Incomplete Bug description: I had no memory problems with Ubuntu 20.04. After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory. I upgraded to 48GB (!), and the memory still continues to fill. After a few days, with no program started, 12GB is taken. Gnome-shell alone is taking 17.4% of my 48GB. I guess it is suffering from a memory leak. Description:Ubuntu 22.04.3 LTS gnome-shell: Installé : 42.9-0ubuntu2 Candidat : 42.9-0ubuntu2 Table de version : *** 42.9-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 07:04:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-31 (75 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2043538/+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 2040108] Re: error "contains an invalid sample specification."
this works too pactl load-module module-tunnel-sink-new server=remote_ip:4713 sink=0 sink_name=MySoundServer so definetly issue only zeroconf-publish or in avahi integration. -- 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/2040108 Title: error "contains an invalid sample specification." Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrade network audio stop working. On the client side in log i see: "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2040108/+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 2043966] [NEW] Second display is not showing up
Public bug reported: This is issues with NVIDIA drivers ~$ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126 Uname: Linux 5.15.0-1050-realtime x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 09:39:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: librealsense2-dkms/1.3.24, 5.15.0-1050-realtime, x86_64: installed librealsense2-dkms/1.3.24, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Ti Mobile] [17aa:3a3e] InstallationDate: Installed on 2023-08-19 (92 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 82B5 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1050-realtime root=UUID=6579ad60-9e6c-4896-b43a-3edc631af107 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnINVALID:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_IDEAPAD: dmi.product.family: IDEAPAD dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_IDEAPAD dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO 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 jammy 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/2043966 Title: Second display is not showing up Status in xorg package in Ubuntu: New Bug description: This is issues with NVIDIA drivers ~$ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1050.56-realtime 5.15.126 Uname: Linux 5.15.0-1050-realtime x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 09:39:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: librealsense2-dkms/1.3.24, 5.15.0-1050-realtime, x86_64: installed librealsense2-dkms/1.3.24, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Ti Mobile] [17aa:3a3e] InstallationDate: Installed on 2023-08-19 (92 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 82B5 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1050-realtime root=UUID=6579ad60-9e6c-4896-b43a-3edc631af107 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31
[Desktop-packages] [Bug 2042972] Re: Apps take minutes to launch
Thanks. This looks like the problem:
Nov 11 18:26:16 Jarvis systemd[3035]: xdg-desktop-portal.service: start
operation timed out. Terminating.
Nov 11 18:26:16 Jarvis systemd[3035]: xdg-desktop-portal.service: Failed with
result 'timeout'.
Nov 11 18:26:16 Jarvis systemd[3035]: Failed to start
xdg-desktop-portal.service - Portal service.
...
Nov 11 18:26:46 Jarvis dbus-daemon[3078]: [session uid=1000 pid=3078] Failed to
activate service 'org.freedesktop.portal.Desktop': timed out
(service_start_timeout=12ms)
Nov 11 18:26:46 Jarvis dbus-daemon[3078]: [session uid=1000 pid=3078] Failed to
activate service 'org.freedesktop.impl.portal.desktop.gnome': timed out
(service_start_timeout=12ms)
Nov 11 18:26:46 Jarvis dbus-daemon[3078]: [session uid=1000 pid=3078]
Successfully activated service 'org.gnome.Terminal'
Do you find any evidence of crashes in /var/crash/ ?
** Package changed: ubuntu => xdg-desktop-portal (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
https://bugs.launchpad.net/bugs/2042972
Title:
Apps take minutes to launch
Status in xdg-desktop-portal package in Ubuntu:
Incomplete
Bug description:
After booting, sometimes I am not able to quickly open apps, it takes
more than 5 mins to launch and in most of them dark mode is not shown.
It used to come back to normal but now it stays the same.
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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 00:11:58 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc]
NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile]
[1043:13fc]
InstallationDate: Installed on 2023-10-29 (9 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX506HCB.313
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX506HCB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.11
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS TUF Gaming F15
dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
[Desktop-packages] [Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Please try deleting locally installed extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 23.10 Release: 23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 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: Tue Nov 7 19:47:42 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+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 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Changed in: bluez (Ubuntu) Status: In Progress => Won't Fix ** No longer affects: bluez (Ubuntu Xenial) ** No longer affects: bluez (Ubuntu Zesty) ** No longer affects: bluez (Ubuntu Artful) ** No longer affects: bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth=150824844606937=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731467/+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 2042874] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
*** This bug is a duplicate of bug 2042973 *** https://bugs.launchpad.net/bugs/2042973 ** This bug has been marked a duplicate of bug 2042973 Desktop becomes unusable after changing window from fullscreen games on Wayland Only -- 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/2042874 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only Status in gnome-shell package in Ubuntu: Invalid Bug description: Description: Ubuntu 23.10 Release: 23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 Uname: Linux 6.5.10-x64v4-xanmod1 x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 21:43:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042874/+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 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 23.10 Release: 23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 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: Tue Nov 7 19:47:42 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+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 2042972] [NEW] Apps take minutes to launch
You have been subscribed to a public bug:
After booting, sometimes I am not able to quickly open apps, it takes
more than 5 mins to launch and in most of them dark mode is not shown.
It used to come back to normal but now it stays the same.
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
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 00:11:58 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if
00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc]
NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile] [1043:13fc]
InstallationDate: Installed on 2023-10-29 (9 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX506HCB.313
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX506HCB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.11
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS TUF Gaming F15
dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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: xdg-desktop-portal (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: amd64 apport-bug mantic performance ubuntu
--
Apps take minutes to launch
https://bugs.launchpad.net/bugs/2042972
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal 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 2040999] Re: backport a commit to fix workspace matrix extension
Well it's almost in updates so let's make the status correct... ** Changed in: gnome-shell (Ubuntu Mantic) Status: Won't Fix => Fix Committed -- 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: Fix Released Status in gnome-shell source package in Mantic: Fix Committed 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 2041496] Re: btmgmt --index broken in Mantic
** Bug watch added: github.com/bluez/bluez/issues #639 https://github.com/bluez/bluez/issues/639 ** Also affects: bluez via https://github.com/bluez/bluez/issues/639 Importance: Unknown Status: Unknown ** Tags added: fixed-in-bluez-5.71 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2041496 Title: btmgmt --index broken in Mantic Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: In Progress Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/2041496/+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 2039354] Re: GDM does not prevent users with login shell /sbin/nologin from logging on
** Tags added: jammy ** Bug watch added: Red Hat Bugzilla #1745147 https://bugzilla.redhat.com/show_bug.cgi?id=1745147 ** Also affects: gdm3 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1745147 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2039354 Title: GDM does not prevent users with login shell /sbin/nologin from logging on Status in gdm3 package in Ubuntu: New Status in gdm3 package in Fedora: Unknown Bug description: Version: 42.0-1ubuntu7.22.04.3 Release: Ubuntu 22.04.3 LTS A user with login-shell set to /sbin/nologin is still able to login using GDM. See also https://bugzilla.redhat.com/show_bug.cgi?id=1745147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039354/+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)
** Tags added: amdgpu
** Tags added: multimonitor
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2993
Importance: Unknown
Status: Unknown
--
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:
Unknown
Status in linux package in Ubuntu:
Confirmed
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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
Importance is set to Medium because it seems pretty rare that someone will be using Xorg and a touchscreen at the same time. Hence there are no other reports of the issue yet. -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: Triaged Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
Confirmed, but I had to have a window maximized before it occurred for me. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: Triaged Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
There was no fix released in gnome-shell. That's just a quirk of
Launchpad that any upstream bug that is closed is set to 'Fix Released'.
The upstream gnome-shell bug was closed because we don't believe it is
gnome-shell or mutter's fault. That's why this bug is now assigned to
the kernel and Mesa.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
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 denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
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
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/gnome-shell/+bug/2038998/+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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: Triaged Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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
