[Desktop-packages] [Bug 2052859] Re: Windows go to behind others when clicking with mouse
> org.gnome.desktop.wm.preferences action-middle-click-titlebar 'lower'
I wonder if the system thinks you are middle clicking somehow. Try:
gsettings set org.gnome.desktop.wm.preferences action-middle-click-
titlebar 'toggle-maximize-vertically'
> org.gnome.desktop.wm.keybindings lower ['disabled']
This doesn't look like a valid setting. In case this is causing
confusion try clearing it with:
gsettings set org.gnome.desktop.wm.keybindings lower "[]"
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
Incomplete
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.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: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 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-3ubuntu2.7
[Desktop-packages] [Bug 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386
Note linked merge proposal for the option when we do not publish atk- wrapper in security update ** Description changed: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: - java-atk-wrapper is present in noble on i386 + java-atk-wrapper is present in noble on i386 + + This is a regression introduced in 8u402-ga-2: + + * Restore M-A installability of focal/i386 package (LP#1916327) + by adding xenial, bionic, focal, jammy to the list of releases + built with the ATK bridge, but not enabling it by default; + keep jessie on, stretch and sid and mantic/noble off the list: + please report bugs for issues with the bridge, so sthibault + can find, debug, fix them ** Also affects: java-atk-wrapper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/2053110 Title: openjdk-8 402 fails to install in focal, jammy, mantic on i386 Status in java-atk-wrapper package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Bug description: openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to dependency on java-atk-bridge. This dependency was introduced by dropping condition present in 392: -- ifeq ($(derivative),Ubuntu) ifeq ($(DEB_HOST_ARCH),i386) ifeq (,$(filter $(distrel),precise trusty xenial bionic)) with_bridge = endif endif endif -- Note: java-atk-wrapper is present in noble on i386 This is a regression introduced in 8u402-ga-2: * Restore M-A installability of focal/i386 package (LP#1916327) by adding xenial, bionic, focal, jammy to the list of releases built with the ATK bridge, but not enabling it by default; keep jessie on, stretch and sid and mantic/noble off the list: please report bugs for issues with the bridge, so sthibault can find, debug, fix them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
FYI, multiple parties and people promised me more input, but so far none has arrived over the last weeks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2052859] Re: Windows go to behind others when clicking with mouse
gsettings list-recursively | grep lower
org.cinnamon.desktop.keybindings.wm lower @as []
org.cinnamon.desktop.keybindings.wm raise-or-lower @as []
org.cinnamon.desktop.wm.preferences action-middle-click-titlebar 'lower'
org.gnome.desktop.wm.keybindings lower ['disabled']
org.gnome.desktop.wm.keybindings raise-or-lower @as []
org.gnome.desktop.wm.preferences action-middle-click-titlebar 'lower'
(process:458291): GLib-GIO-WARNING **: 08:25:47.271: Failed to parse
translated string
'['attachment','attaching','attached','enclosed,'liite','liitteenä','liitän']'
for key 'attachment-reminder-clues' in schema
'org.gnome.evolution.plugin.attachment-reminder': 48:expected ',' or ']'
to follow array element
(process:458291): GLib-GIO-WARNING **: 08:25:47.271: Using untranslated default
instead.
org.gnome.shotwell.preferences.files use-lowercase-filenames false
org.yorba.shotwell.preferences.files use-lowercase-filenames false
--
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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
New
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.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: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co.,
[Desktop-packages] [Bug 2052859] Re: Windows go to behind others when clicking with mouse
What output do you get when you run this?
gsettings list-recursively | grep lower
--
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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
New
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.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: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 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-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
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
xserver.bootTime: Fri Feb 9 20:05:59 2024
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version:
[Desktop-packages] [Bug 2053019] Re: Second (external) monitor not active after screen lock
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Second (external) monitor not active after screen lock
+ [nvidia] Second (external) monitor not active after screen lock in Xorg
** Tags added: multimonitor nvidia
--
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/2053019
Title:
[nvidia] Second (external) monitor not active after screen lock in
Xorg
Status in mutter package in Ubuntu:
New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Bug description:
After switching back to Xorg, I have encountered the issue with the
second (external) monitor - after the screen is locked and I unlock
it, the second monitor either shows a blank black screen or is not
even active in Display settings. It's like the configuration is lost
during lock/unclock process.
I am using USB-C to HDMI cable with the second screen and Xorg as
display manager.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-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.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 13 12:53:24 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (32 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2023
dmi.bios.release: 1.64
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN64WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 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.64
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
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/2053019/+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 2052859] Re: Windows go to behind others when clicking with mouse
I suspect the bug first appeared with the introduction of the Nvidia
driver because that switched you over from Wayland to Xorg. So this
might be a Xorg-only bug.
** Changed in: mutter (Ubuntu)
Status: Incomplete => 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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
New
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.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: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 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-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
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
xserver.bootTime: Fri
[Desktop-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
This bug was fixed in the package gsettings-desktop-schemas - 46~beta-1ubuntu1 --- gsettings-desktop-schemas (46~beta-1ubuntu1) noble; urgency=medium * Merge with Debian. Remaining changes: - Add ubuntu_lock-on-suspend.patch - Add dark-theme migration script using dh-migrations - Drop Breaks: ukwm because ukwm still runs but fails to build from source for unrelated reasons gsettings-desktop-schemas (46~beta-1) unstable; urgency=medium * New upstream release - Enable tap-to-click by default - Add new show-status-shapes schema to show shapes in Adwaita on/off switches, disabled by default - Add xkb-model schema, used by GNOME Shell 46 - Allow localization of clock format (in coordination with glib 2.78) (LP: #1956102) * Add patch to keep using the 45 default wallpaper. See #1060278 -- Jeremy Bícha Tue, 13 Feb 2024 08:30:42 -0500 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2048797] Re: Screen Sharing no longer works with nouveau driver
** Package changed: xserver-xorg-video-nouveau (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/2048797 Title: Screen Sharing no longer works with nouveau driver Status in mutter package in Ubuntu: New Bug description: Hi Since the end of last november, screen sharing no longer works, i get a black screen. here is the log i get nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 1 [02ffd8c000 gnome-shell[1369]] subc 0 class c797 mthd 17e0 data 0030 if i install NVIDIA proprietary driver (nvidia-driver-535) the screen sharing work again, back to nouveau it fails. i'm on Ubuntu 22.04.3 LTS with latest update Linux touco-System-Product-Name 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux my graphics card is [GeForce RTX 3060 Lite Hash Rate] (rev a1) i have a laptop with exact Ubuntu version and updates, screen sharing works with nouveau driver but the graphic card is NVIDIA® GeForce RTX™ 3070 Laptop GPU I made the test with chrome on this site https://www.webrtc- experiment.com/Pluginfree-Screen-Sharing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 19:23:06 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA106 [GeForce RTX 3060 Lite Hash Rate] [1458:4096] InstallationDate: Installed on 2022-07-12 (546 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=c179fd07-f21e-43e9-856b-eeaeb54b2ebb ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2023 dmi.bios.release: 30.10 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3010 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3010:bd12/11/2023:br30.10:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690M-PLUSD4:rvrRev1.xx: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.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.5 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/mutter/+bug/2048797/+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 1961508] Re: Dock displaying over window after resuming from blank screen
We know: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939/comments/21 -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
This bug was fixed in the package ubuntu-release-upgrader - 1:22.04.18 --- ubuntu-release-upgrader (1:22.04.18) jammy; urgency=medium * do-release-upgrade: pass XDG_CURRENT_DESKTOP env var (LP: #2034986) * Run pre-build.sh: updating po files, mirrors, and demotions. -- Nick Rosbrook Thu, 12 Oct 2023 11:56:03 -0400 ** Changed in: ubuntu-release-upgrader (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Released Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep
I've had at least 2 instances where the dash-to-dock workaround fails since installing it this morning, so I don't see that as a viable fix. -- 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/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Status in mutter package in Ubuntu: Fix Released Status in gnome-shell package in Fedora: Won't Fix Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+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 2020110] Re: Migrate netplan settings to this package
Per discussions in the appropriate PR for Calamares[1], this should be done in network-manager itself. The appeal is more custom approaches. Downstreams and vendors of Ubuntu. [1] https://github.com/calamares/calamares/pull/2284 ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in network-manager package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
I have verified the XDG_CURRENT_DESKTOP fix using ubuntu-release- upgrader-core 1:22.04.18 from jammy-proposed: nr@clean-jammy-amd64:~$ apt policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.18 Candidate: 1:22.04.18 Version table: *** 1:22.04.18 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:22.04.17 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 1:22.04.10 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages nr@clean-jammy-amd64:~$ do-release-upgrade -f DistUpgradeViewGtk3 Checking for a new Ubuntu release localuser:root being added to access control list Checking for a new Ubuntu release libEGL warning: pci id for fd 48: 1b36:0100, driver (null) libEGL warning: pci id for fd 13: 1b36:0100, driver (null) authenticate 'mantic.tar.gz' against 'mantic.tar.gz.gpg' extracting 'mantic.tar.gz' [ ... left running in another window ... ] nr@clean-jammy-amd64:~$ ps aux | grep mantic root 12099 13.4 22.2 662444 216644 pts/0 Rl+ 12:06 0:10 /usr/bin/python3 -s /tmp/ubuntu-release-upgrader-kb757df9/mantic --mode=server --frontend=DistUpgradeViewGtk3 nr 14227 0.0 0.2 9080 2560 pts/2S+ 12:07 0:00 grep --color=auto mantic nr@clean-jammy-amd64:~$ sudo xargs -0 -L1 -a /proc/12099/environ | grep XDG_CURRENT_DESKTOP XDG_CURRENT_DESKTOP=ubuntu:GNOME ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Committed Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname:
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Sorry if I missed it the comments. What is the solution for appimages? Thanks, Scarlett -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
Timo, can you verify this? -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2052794] Re: 2.79.1 test issue on s390x
** Changed in: glib Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2052794 Title: 2.79.1 test issue on s390x Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: In Progress Bug description: One of the newly added tests in the 2.79 serie is failing on s390x. The issue is being discussed upstream on https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new and is currently buggy. Upstream/Debian/Ubuntu already disabled similar tests in 2.79.1 but that one as not noticed to fail because it's skipped during build so is only showing now in the installed- tests result and in autopkgtest. (And the package is in Debian/experimental where it didn't get tested by the Debian CI) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2052794/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: plasma-welcome (Ubuntu) Importance: Undecided Status: New ** Changed in: plasma-welcome (Ubuntu) Importance: Undecided => High ** Changed in: plasma-welcome (Ubuntu) Status: New => In Progress ** Changed in: plasma-welcome (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 1724037] Re: Allow GNOME fractional scaling below 100%
@darkdragon-001 by way of an update, I re-tried this on 24.04 (development) as of this date, using Gnome 45.3, on Wayland and it worked. It's quite uncanny to see 2400x1600 rendered on a 2160x1440 screen, but it worked with the exception of a couple of apps that were blew up spectacularly, including OBS, and Slack... otherwise... everything else worked fine, and at the scaling factor above (90%), things seemed quite usable... it looked a little like an old CRT that was being pushed a little hard, but for certain applications this could be awesome. I wish the UI in gnome would offer the ability to be more granular than just 25% increments, and also go below 100%, perhaps with a warning, or from within Gnome Tweaks. -- 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/1724037 Title: Allow GNOME fractional scaling below 100% Status in Mutter: New Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Bug description: It should be possible to scale down the whole shell to less than 100% e.g. 90% 85% etc. thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 20:14:43 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724037/+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 1917939] Re: Windows maximise underneath dock after monitor sleep
Agreed. Also still affected -- 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/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Status in mutter package in Ubuntu: Fix Released Status in gnome-shell package in Fedora: Won't Fix Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+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 2052495] Re: [MIR] wsl-pro-service
** Also affects: wsl-pro-service (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: wsl-pro-service (Ubuntu Noble) Importance: Undecided Assignee: Lukas Märdian (slyon) Status: New ** Also affects: wsl-pro-service (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wsl-pro-service in Ubuntu. https://bugs.launchpad.net/bugs/2052495 Title: [MIR] wsl-pro-service Status in wsl-pro-service package in Ubuntu: New Status in wsl-pro-service source package in Focal: New Status in wsl-pro-service source package in Jammy: New Status in wsl-pro-service source package in Noble: New Bug description: [Availability] The package wsl-pro-service is already available in Ubuntu universe. The package wsl-pro-service build for the architectures it is designed to work on. It currently builds and works for architectures: amd64, arm64, armhf, ppc64el, riscv64, s390x Link to package https://launchpad.net/ubuntu/+source/wsl-pro-service [Rationale] Ubuntu Pro for WSL is a set of applications to manage Ubuntu WSL instances, grant them Pro status, orchestrate instances from Landscape and manage their lifecycle. Wsl-pro-service serves as a bridge between the agent running on Windows and Ubuntu instances. It controls the Pro and Landscape status. The package wsl-pro-service is required to be in main to seed it by default on WSL images. The package wsl-pro-service will generally be useful for corporate users. No package in main or universe currently offers these capabilities. The target release is all the LTS releases from 20.04 onwards. [Security] This is a new software developed and maintained by Canonical. It has no security history. It is a new software and no CVEs/security issues in this software in the past. - no `suid` or `sgid` binaries - The package installs a systemd service called wsl-pro-service - It installs a service in /usr/libexec/wsl-pro-service, running as root. The service has some systemd confinement. - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software - Communication between wsl-pro-service and the agent running on Windows is done over gRPC. - Security has been kept in mind and common isolation/risk-mitigation patterns are in place utilizing systemd isolation features. *This requires a security review.* [Quality assurance - function/usage] The package works well right after installation. [Quality assurance - maintenance] The Ubuntu Desktop team (~desktop-packages) maintains this package. It doesn’t have any long-term and critical, open bugs: - https://github.com/canonical/ubuntu-pro-for-windows/issues - https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service [Quality assurance - testing] There is a comprehensive, non-trivial, testsuite. The testsuite includes integration and functional tests. The testsuite runs at build time. The branch coverage is over 88%: - https://github.com/canonical/ubuntu-pro-for-windows/actions/workflows/qa.yaml?query=branch%3Amain - https://app.codecov.io/gh/canonical/ubuntu-pro-for-wsl The same test suite runs as autopkgtest. It is passing on all supported architectures. Links to test logs: - https://autopkgtest.ubuntu.com/packages/wsl-pro-service Upstream CI also includes code sanity checks (golangci-lint, including gosec) and vulnerability scanning (govulneck). [Quality assurance - packaging] - There is no debian/watch because wsl-pro-service is a native package. - debian/control defines a correct Maintainer field: - Maintainer: Ubuntu Developers This package does not yield massive lintian Warnings, Errors ``` W: wsl-pro-service: no-manual-page [usr/libexec/wsl-pro-service] ``` Full output from `lintian --pedantic`: ``` W: wsl-pro-service: no-manual-page [usr/libexec/wsl-pro-service] ``` - Lintian overrides are not present. - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default but does not ask debconf questions. Packaging and build is easy: - https://github.com/canonical/ubuntu-pro-for-windows/blob/main/wsl-pro-service/debian/rules [UI standards] Application is not end-user facing. However some strings are translatable and used for error messages via standard intltool/gettext or similar build and runtime internationalization system: The system for internationalization is in place of the project and the mo and po files are generated. It’s a question of taking the time to mark the appropriate strings for translations. It is a background service. Strings are used for logging and are not immediately visible to the user. [Dependencies] No further
[Desktop-packages] [Bug 2052859] Re: Windows go to behind others when clicking with mouse
No change. After boot and login, I started firefox, then opened Mines
on top of it, and clicking on Mines put it background. This time it
seems that the game got the click, but it still disappeared behind the
browser window.
journal.txt attached.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2052859/+attachment/5746051/+files/journal.txt
--
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/2052859
Title:
Windows go to behind others when clicking with mouse
Status in mutter package in Ubuntu:
Incomplete
Bug description:
After installing ubuntu graphics-drivers ppa nvidia-550 driver, the
bug appears.
When there are several windows on top of each other, clicking within
the topmost window, the window seems to disappear. Actually, the
window is still there, but just goes behind another window, that comes
in front of the clicked window. The program in the window that is
clicked will not notice the click.
This does not happen with all programs. Mines is a good example
program. If the window fills full screen, this happens, but if it is
smaller, only partially covering the screen, it does not happen.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.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..2d.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 550.40.07 Thu Jan 18
07:30:58 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,gnomecompat,resize,regex,imgpng,grid,mousepoll,move,unitymtgrabhandles,animation,vpswitch,place,session,workarounds,expo,wall,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 10 17:56:32 2024
DistUpgraded: 2023-11-03 20:23:14,648 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:e130]
InstallationDate: Installed on 2012-12-22 (4067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (99 days ago)
dmi.bios.date: 02/28/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.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: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.J0:bd02/28/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C37
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx 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-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
[Desktop-packages] [Bug 1861609] Re: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRI
I'd like to note that, on Xubuntu at least, these crashes are eliminated by removing libva-wayland2. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/comments/9 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. and call stack comes from DRIMoveBuffersHelper WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1861609/+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 1961508] Re: Dock displaying over window after resuming from blank screen
Similar bug report: https://bugs.launchpad.net/dash-to-dock/+bug/1917939 -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 1917939] Re: Windows maximise underneath dock after monitor sleep
Still happening in Ubuntu 24.04.3 with the latest updates. I have a dual-monitor setup with Wayland. Bug occurs when I lock the screen and unlock it again. Everything gets left behind the dock. I think it is related to dash-to-dock implementation of Ubuntu. There is a workaround which fixes the issue, but it just hides and unhides the panel when unlocked: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-ubuntu-dock/+bug/1917939 Why is the screen state not saved when the screen is locked? It feels like it tries to draw it again and misses the dock as if the screen starts from the edges. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Invalid => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Opinion -- 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/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Status in mutter package in Ubuntu: Fix Released Status in gnome-shell package in Fedora: Won't Fix Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+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 2053019] [NEW] Second (external) monitor not active after screen lock
Public bug reported:
After switching back to Xorg, I have encountered the issue with the
second (external) monitor - after the screen is locked and I unlock it,
the second monitor either shows a blank black screen or is not even
active in Display settings. It's like the configuration is lost during
lock/unclock process.
I am using USB-C to HDMI cable with the second screen and Xorg as
display manager.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-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.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 13 12:53:24 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (32 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2023
dmi.bios.release: 1.64
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN64WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 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.64
dmi.modalias:
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
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/2053019
Title:
Second (external) monitor not active after screen lock
Status in xorg package in Ubuntu:
New
Bug description:
After switching back to Xorg, I have encountered the issue with the
second (external) monitor - after the screen is locked and I unlock
it, the second monitor either shows a blank black screen or is not
even active in Display settings. It's like the configuration is lost
during lock/unclock process.
I am using USB-C to HDMI cable with the second screen and Xorg as
display manager.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-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.154.05 Thu
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: kontact (Ubuntu) Status: In Progress => Fix Released ** Changed in: konqueror (Ubuntu) Status: In Progress => Fix Released ** Changed in: marble (Ubuntu) Status: In Progress => Fix Released ** Changed in: kgeotag (Ubuntu) Status: Confirmed => In Progress ** Changed in: kgeotag (Ubuntu) Assignee: (unassigned) => Scarlett Gately Moore (scarlettmoore) ** Changed in: tellico (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
i have the same issue with Ubuntu 22.04.3 LTS woth the same graphics cards (NVIDIA GeForce RTX 3060 Ti) and nouveau driver. it seems related to this issue https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/2048797 -- 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/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in Mutter: New Status in PipeWire: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012556/+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 2053013] [NEW] can not mount phone path when shotwell is up
Public bug reported: i plug my android phone with /e/. i select file transfer on the phone. the phone file system is mount and i can access to files if i start shotwell the phone path is unmount in th other way shotwell is up and i plug my phone shotwell detect the phone before i set file transfert on it. after set transfer file mount then unmount and can not acces to file. /var/log/syslog on event 2024-02-13T12:15:58.893342+01:00 computerName kernel: [11428.152735] usb 1-2: USB disconnect, device number 31 2024-02-13T12:15:58.916619+01:00 computerName (udev-worker)[19319]: 1-2: Process '/usr/lib/snapd/snap-device-helper unbind snap_cups_cupsd /devices/pci:00/:00:14.0/usb1/1-2 189:30' failed with exit code 1. 2024-02-13T12:15:58.917559+01:00 computerName (udev-worker)[19319]: 1-2: Process '/usr/lib/snapd/snap-device-helper unbind snap_cups_ippeveprinter /devices/pci:00/:00:14.0/usb1/1-2 189:30' failed with exit code 1. 2024-02-13T12:15:59.245320+01:00 computerName kernel: [11428.501774] usb 1-2: new high-speed USB device number 32 using xhci_hcd 2024-02-13T12:15:59.393283+01:00 computerName kernel: [11428.653368] usb 1-2: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.04 2024-02-13T12:15:59.393292+01:00 computerName kernel: [11428.653373] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2024-02-13T12:15:59.393293+01:00 computerName kernel: [11428.653375] usb 1-2: Product: ONEPLUS A5000 2024-02-13T12:15:59.393293+01:00 computerName kernel: [11428.653377] usb 1-2: Manufacturer: OnePlus 2024-02-13T12:15:59.393294+01:00 computerName kernel: [11428.653378] usb 1-2: SerialNumber: a33cc375 2024-02-13T12:15:59.414319+01:00 computerName (udev-worker)[19319]: 1-2: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_cupsd /devices/pci:00/:00:14.0/usb1/1-2 189:31' failed with exit code 1. 2024-02-13T12:15:59.415703+01:00 computerName (udev-worker)[19319]: 1-2: Process '/usr/lib/snapd/snap-device-helper bind snap_cups_ippeveprinter /devices/pci:00/:00:14.0/usb1/1-2 189:31' failed with exit code 1. 2024-02-13T12:15:59.611023+01:00 computerName gnome-system-monitor.desktop[15700]: glibtop(c=15700): [WARNING] statvfs '/run/user/1000/doc' failed: Opération non permise 2024-02-13T12:16:00.837415+01:00 computerName kernel: [11430.094165] usb 1-2: reset high-speed USB device number 32 using xhci_hcd 2024-02-13T12:16:00.997616+01:00 computerName gnome-system-monitor.desktop[15700]: message repeated 4 times: [ glibtop(c=15700): [WARNING] statvfs '/run/user/1000/doc' failed: Opération non permise] 2024-02-13T12:16:00.998882+01:00 computerName tracker-miner-f[3281]: g_str_has_suffix: assertion 'str != NULL' failed 2024-02-13T12:16:00.999490+01:00 computerName tracker-miner-f[3281]: g_str_has_prefix: assertion 'str != NULL' failed 2024-02-13T12:16:01.003132+01:00 computerName tracker-miner-f[3281]: g_str_has_suffix: assertion 'str != NULL' failed 2024-02-13T12:16:01.003535+01:00 computerName tracker-miner-f[3281]: g_str_has_prefix: assertion 'str != NULL' failed 2024-02-13T12:16:01.004067+01:00 computerName gnome-system-monitor.desktop[15700]: glibtop(c=15700): [WARNING] statvfs '/run/user/1000/doc' failed: Opération non permise 2024-02-13T12:16:01.009879+01:00 computerName gnome-system-monitor.desktop[15700]: glibtop(c=15700): [WARNING] statvfs '/run/user/1000/doc' failed: Opération non permise 2024-02-13T12:16:02.383973+01:00 computerName gvfsd[19338]: Device 0 (VID=2717 and PID=ff40) is a Xiaomi Mi-2s (id2) (MTP). 2024-02-13T12:16:02.384374+01:00 computerName gvfsd[19338]: Android device detected, assigning default bug flags ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: shotwell 0.32.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 12:06:41 2024 InstallationDate: Installed on 2023-12-28 (47 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/2053013 Title: can not mount phone path when shotwell is up Status in shotwell package in Ubuntu: New Bug description: i plug my android phone with /e/. i select file transfer on the phone. the phone file system is mount and i can access to files if i start shotwell the phone path is unmount in th other way shotwell is up and i plug my phone shotwell detect
[Desktop-packages] [Bug 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pipewire (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/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in Mutter: New Status in PipeWire: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012556/+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 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in Mutter: New Status in PipeWire: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012556/+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 2012556] Re: GNOME Magnifier: Performance issues with Pipewire and OBS
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/2012556 Title: GNOME Magnifier: Performance issues with Pipewire and OBS Status in Mutter: New Status in PipeWire: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: Timeline: 1. (March 11, 2023) I have uploaded a video regarding the problems with GNOME Magnifier. https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 2. (March 11, 2023) I filed a bug report on Pipewire. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3087 3. (March 14, 2023) I uploaded another short video with pw-top (Pipewire) running on the terminal. https://odysee.com/@GraysonPeddie:6/gnomemag-pwtop-obs-pipewire:d 4. (March 14, 2023) I filed a bug report on GNOME Mutter's issue tracker and referenced the two videos and a bug report from Pipewire, but I get no response from the Mutter team. https://gitlab.gnome.org/GNOME/mutter/-/issues/2698 Affected GNOME versions and why I am filing the bug here: This affects GNOME 42, GNOME 43, and GNOME 44. For GNOME 42 and 43, I used Nobara 36 and 37. Nobara is based on Fedora but includes patches for gaming and content creation. I wanted to try out GNOME 44 in Ubuntu 23.04 and I managed to run OBS with Pipewire Screen Sharing, but then the performance with GNOME Magnifier is very sluggish and it froze my entire computer. I've had to restart my computer, but for some reason, GNOME 44 won't load and I've had to go back to Nobara as that is my distro of choice for gaming. This issue with GNOME not loading is beyond the scope of the bug report. So in short, all the recent versions of GNOME (up to 44) are affected regardless of which Linux distribution I use. The reason why I need to file a bug here is because I do not get a response from the Mutter team and I'm at a standstill with Pipewire as they cannot diagnose the problem that I am having. I could test the issue in Ubuntu 22.04 and 22.10, but unfortunately, I do not have another computer to test. On top of that, even if I could install OBS in a live USB image of Ubuntu 22.04 and 22.10, I have an NVIDIA GPU and the GNOME Magnifier is sluggish with Nouveau driver, but again, that is beyond the scope of this issue that I am having. Specs: AMD Ryzen 9 5900X CPU 32GB of RAM NVIDIA GeForce RTX 3060 Ti Resolution: 3840x2160 at 60Hz What I'm Expecting to Happen: The performance with GNOME Magnifier and Pipewire screen capturing with OBS should be smooth. Actual Behavior: Please refer to the two videos in the Timeline section. Steps to Reproduce: In order to reproduce an issue, OBS needs to be installed. However, I am not sure if this is only related to OBS, but that is the only software I use for screen capturing and with support for JACK. 1. Open OBS. 2. Under Sources, press the Add (+) button. 3. Select "Screen Capture (Pipewire)." 4. Select the monitor and press "Share." The screen capture should show up on the preview area of OBS. 5. Open the Settings from either the Overview or the Quick Settings Menu. 6. Scroll down to Accessibility and turn on Zoom. Move your mouse around and you should see performance issues with GNOME Magnifier when doing screen capturing using Pipewire. This affects both Xorg and Wayland. Questions: Is there anything else that I am missing? Should I only test this in Ubuntu even though it's not Ubuntu-specific? Besides, the supported Ubuntu versions should all be affected by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2012556/+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 2052959] Re: FTBFS when rebuilding 1.44 with glib2-2.79.1
Upstream fix landed in: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7f2a32fa11d580ee65a0458f438018de12b6ae84 ** Summary changed: - FTBFS when rebuilding 1.44 with GCC-14 + FTBFS when rebuilding 1.44 with glib2-2.79.1 -- 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/2052959 Title: FTBFS when rebuilding 1.44 with glib2-2.79.1 Status in network-manager package in Ubuntu: Fix Committed Bug description: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2052959/+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 2052959] Re: FTBFS when rebuilding 1.44 with GCC-14
Fixed in https://launchpad.net/ubuntu/+source/network- manager/1.45.90-1ubuntu1 ** Changed in: network-manager (Ubuntu) Status: New => Fix Committed -- 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/2052959 Title: FTBFS when rebuilding 1.44 with glib2-2.79.1 Status in network-manager package in Ubuntu: Fix Committed Bug description: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2052959/+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 594377] Re: transmission-daemon starting by default confuses some less technical users.
transmission-daemon is a separate package since 1.40-1 . ** Changed in: transmission (Ubuntu) Status: Triaged => Fix Released -- 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/594377 Title: transmission-daemon starting by default confuses some less technical users. Status in transmission package in Ubuntu: Fix Released Bug description: Binary package hint: transmission By default transmission-daemon is launched as a system daemon, it confuses less experienced users who assume that it should have an access to their files (often the same files they download using GTK+ client). As more advanced users are more likely to check changelogs and dig into settings lets disable transmission-daemon launching by default by changing ENABLE_DAEMON to 0 in /etc/default/transmission-daemon for now and see if we get any feedback. Should be discussed with Debian Maintainer at some point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/594377/+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 475302] Re: file does not download by torrent
** Changed in: transmissionrpc (Ubuntu) Status: New => Invalid -- 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/475302 Title: file does not download by torrent Status in transmission package in Ubuntu: Invalid Status in transmissionrpc package in Ubuntu: Invalid Bug description: Binary package hint: transmission Download the torrent does not start when it is placed to begin with, it is only on idle! ProblemType: Bug Architecture: i386 Date: Thu Nov 5 08:50:26 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/transmission Package: transmission-gtk 1.75-0ubuntu2 ProcEnviron: LANGUAGE=pt_BR.UTF-8 LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: transmission Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:1661): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:1661): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:1766): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1750): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (gnome-panel:1746): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -10 and height 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/475302/+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 2052959] Re: FTBFS when rebuilding 1.44 with GCC-14
** Summary changed: - FTBFS when rebuilding 1.44 + FTBFS when rebuilding 1.44 with GCC-14 -- 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/2052959 Title: FTBFS when rebuilding 1.44 with GCC-14 Status in network-manager package in Ubuntu: New Bug description: FTBFS due to test failure after an unrelated autopkgtest change was uploaded (https://launchpad.net/ubuntu/+source/network- manager/1.44.2-7ubuntu2). ok 7 /config/warnings PASS: src/core/tests/config/test-config 7 /config/warnings # (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ") exec "./src/core/tests/config/test-config" failed with exit code 133 ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7) ERROR: src/core/tests/config/test-config - exited with status 5 See upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2052959/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Erich, yes the archive version is based on the ppa, with a couple small fixes in the packaging. The ppa is going to get updated based the new archive version + a few more patches. Do you have some higher priority electron apps that you can point us at. We will look into the Visual Studo and Element Desktop debs. Please keep adding applications to the list. We want to cover as many out of tree applications as we can. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Confirmed Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: In Progress Status in kontact package in Ubuntu: In Progress Status in marble package in Ubuntu: In Progress Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: In Progress Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
** Tags removed: lunar ** Tags added: mantic noble ** Tags removed: rls-ll-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2012388/+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
