[Desktop-packages] [Bug 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
I think the final address ending in a7c is probably raise() so that may not be useful information. This is starting to smell like stack corruption. -- 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/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Desktop has some issues but it was not showable ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu1 Uname: Linux 5.16.12-051612-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 12:12:08 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-04 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f0d7aec5a7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+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 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address]
All the duplicates seem to get stuck at addresses in [stack] according to ProcMaps.txt. The crash reports all say "Backtrace stopped: Cannot access memory at address", but ProcMaps.txt seems to indicate it's a valid stack address (read-write memory, but not executable). ** Summary changed: - gnome-shell crashed with SIGSEGV at ?+a7c called from [heap address] + gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address] ** Summary changed: - gnome-shell crashed with SIGSEGV at ?+a7c called from [Cannot access memory at address] + gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) -- 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/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Desktop has some issues but it was not showable ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu1 Uname: Linux 5.16.12-051612-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 12:12:08 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-04 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f0d7aec5a7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+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 1967274] Re: Screen can't turn on after screen off [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Looks like the same error as
https://gitlab.gnome.org/GNOME/mutter/-/issues/2197
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2197
https://gitlab.gnome.org/GNOME/mutter/-/issues/2197
--
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/1967274
Title:
Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967274/+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 1967274] Re: Screen can't turn on after screen off [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Please try these in /etc/environment:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1
and then reboot.
If that works then please figure out which one is actually fixing the
problem.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967274/+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 1967274] Re: Screen can't turn on after screen off [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Summary changed:
- screen can't turn on after screen off
+ Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
--
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/1967274
Title:
Screen can't turn on after screen off [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in gnome-shell package in Ubuntu:
Incomplete
Status in mutter package in Ubuntu:
Incomplete
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967274/+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 1967329] Re: Full screen in Firefox and Ubuntu panel options can't be displayed
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1967329 Title: Full screen in Firefox and Ubuntu panel options can't be displayed Status in gnome-shell package in Ubuntu: Fix Released Bug description: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967329/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: resume suspend-resume -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1967452] Re: When resume from suspend, monitor keep blinking and don't show the whole desktop.
Looks like this might be an extreme case of bug 1876632. ** Package changed: xwayland (Ubuntu) => mutter (Ubuntu) ** Summary changed: - When resume from suspend, monitor keep blinking and don't show the whole desktop. + [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop. ** Tags added: nvidia resume suspend-resume -- 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/1967452 Title: [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop. Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Reproduce steps] 1. Install jammy beta. 2. Install nvidia-driver by ubuntu-driver install 3. Suspend the system by clicking the button at the upper right corner. [Expected result] Should re-enter to desktop. [Actual result] Screen keep blinking and don't show the desktop screen. According to reaction of the system, it seems to login already, I can press ctrl+alt+del to pop out a logout menu. [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:27:12 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967452/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%
A fix for GTK3 is also in progress:
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4381
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu)
Status: New => In Progress
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => High
--
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/1967448
Title:
All the windows and the desktop icons disappear constantly after
setting Scaling to 300%
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Invalid
Status in gtk+3.0 package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Summary
===
Device with nvidia GPU, using proprietary drivers, wayland activated
by default.
By default, the scaling is set to 200% (the screen is UHD). If
selecting 300%, all the windows close down, as well as the desktop
icons (Home) as long as the mouse cursor is in the way.
To fix the issue, one has to open the Display Settings (while making
sure the mouse cursor is never above any of the Settings windows!),
then set Scaling back to 200% using the keyboard.
This problem does not happen in X11, and does not happen in Wayland if
I select 100%, 200% or even 400% scaling!
Steps to reproduce
==
- Install 22.04 beta, selecting "install third party software" to make sure
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
- After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE
should return `wayland`)
- Go to Settings > Display, select 300% scaling, then press Apply
Expected result
===
The scaling is set to 300% and user can keep using the device.
Actual result
=
The scaling is set to 300% and all the windows are shut down. If user
tries to reopen a window (e.g. Terminal), it is shut down immediately
if the mouse cursor is hovering it. The desktop icons keep
disappearing and reappearing for as long as the mouse cursor is
hovering the background.
The only way to stop this is to go back to Settings > Display, and,
using the keyboard, set the scaling back to 200%.
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.045.15.0.23.25
amd64Complete Generic Linux kernel and headers
ii linux-headers-5.15.0-235.15.0-23.23
all Header files related to Linux kernel version 5.15.0
ii linux-headers-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.045.15.0.23.25
amd64Generic Linux kernel headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23
amd64Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25
amd64Generic Linux kernel image
ii linux-modules-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit
x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit
x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1
amd64Extra drivers for nvidia-510 for the generic-hwe-20.04
flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
(objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel signatures for nvidia modules for version
5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:24:25 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.g
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
See also bug 1855757. -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+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 1967329] Re: Full screen in Firefox and Ubuntu panel options can't be displayed
Today I have updated Ubuntu and plenty of fixes arrived and I can confirm this problem is fixed. Thanks -- 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/1967329 Title: Full screen in Firefox and Ubuntu panel options can't be displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967329/+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 1832958] Re: Quirky preview behavior when autohide is on
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- 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/1832958 Title: Quirky preview behavior when autohide is on Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: See details in my upstream report: https://github.com/micheleg/dash- to-dock/issues/963 Also reporting here because it affects configurations supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1832958/+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 1967452] Re: When resume from suspend, monitor keep blinking and don't show the whole desktop.
** Also affects: gnome-shell Importance: Undecided Status: New ** No longer affects: gnome-shell ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1967452 Title: When resume from suspend, monitor keep blinking and don't show the whole desktop. Status in gnome-shell package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: [Reproduce steps] 1. Install jammy beta. 2. Install nvidia-driver by ubuntu-driver install 3. Suspend the system by clicking the button at the upper right corner. [Expected result] Should re-enter to desktop. [Actual result] Screen keep blinking and don't show the desktop screen. According to reaction of the system, it seems to login already, I can press ctrl+alt+del to pop out a logout menu. [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:27:12 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967452/+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 1967452] Re: When resume from suspend, monitor keep blinking and don't show the whole desktop.
This video shows that what I observed. ** Attachment added: "IMG_6015.mp4" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1967452/+attachment/5575459/+files/IMG_6015.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1967452 Title: When resume from suspend, monitor keep blinking and don't show the whole desktop. Status in xwayland package in Ubuntu: New Bug description: [Reproduce steps] 1. Install jammy beta. 2. Install nvidia-driver by ubuntu-driver install 3. Suspend the system by clicking the button at the upper right corner. [Expected result] Should re-enter to desktop. [Actual result] Screen keep blinking and don't show the desktop screen. According to reaction of the system, it seems to login already, I can press ctrl+alt+del to pop out a logout menu. [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:27:12 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1967452/+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 1967452] [NEW] When resume from suspend, monitor keep blinking and don't show the whole desktop.
Public bug reported: [Reproduce steps] 1. Install jammy beta. 2. Install nvidia-driver by ubuntu-driver install 3. Suspend the system by clicking the button at the upper right corner. [Expected result] Should re-enter to desktop. [Actual result] Screen keep blinking and don't show the desktop screen. According to reaction of the system, it seems to login already, I can press ctrl+alt+del to pop out a logout menu. [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:27:12 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy jiayi oem-priority wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1967452 Title: When resume from suspend, monitor keep blinking and don't show the whole desktop. Status in xwayland package in Ubuntu: New Bug description: [Reproduce steps] 1. Install jammy beta. 2. Install nvidia-driver by ubuntu-driver install 3. Suspend the system by clicking the button at the upper right corner. [Expected result] Should re-enter to desktop. [Actual result] Screen keep blinking and don't show the desktop screen. According to reaction of the system, it seems to login already, I can press ctrl+alt+del to pop out a logout menu. [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:27:12 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1967452/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
** Tags added: wayland-fractional-scaling
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+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 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
Just for the record, I see the same issue with a Dell Precision 7760 (CID 202103-28858) when running 22.04 beta on Wayland. I was told the HDMI connector was wired directly to the Nvidia GPU, so gnome-shell crashes when I connect an external monitor there, but even after logging back in, the monitor cannot be used. Plugging the same monitor to the USB-C connector (which is wired to Intel GPU apparently) works like a charm... -- 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/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: This is on my weird desktop setup, with one monitor plugged into an AMD card and one into an NVIDIA card. When using the Wayland session, by default Shell will come up on the monitor connected to the AMD card, and the second (NVIDIA) monitor will be blank. Attempting to enable the second monitor in Display Settings will immediately and reproducibly crash gnome-shell. This is trivial for me to reproduce, so if you need patches tested I can easily do so. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2 Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 09:37:51 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-11-02 (125 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
The Xorg implementation of fractional scaling isn't really related to
the Wayland one so we shouldn't link the bugs together.
Xorg fractional scaling is an Ubuntu patch.
Wayland fractional scaling is an upstream feature.
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
** Tags added: jiayi oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
The related issue reported when using Xorg:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966050
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in OEM Priority Project:
New
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
Good point. I haven't done a duplicate check yet but I expect other
people have reported this somewhere
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
But who would keep that resolution when it sure *looks* broken? I can
understand the "it's not new and we don't know how to fix it" :) but
probably users won't know that they'll be fine after a reboot.
Thanks
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1967176] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964120 *** https://bugs.launchpad.net/bugs/1964120 I forgot we also have bug 1964120 for this. ** This bug has been marked a duplicate of bug 1964120 gnome-shell crashed with SIGSEGV at ?+a7c called from [heap address] -- 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/1967176 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42~beta-1ubuntu3 Candidate: 42~beta-1ubuntu3 Version table: *** 42~beta-1ubuntu3 500 500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status nvidia 1030. nvidia-driver-510 3) What you expected to happen just logout and login again 4) What happened instead after logout and login again, apport reported this crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 22:40:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967176/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
--
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/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
I've been seeing this issue (on rare occasions) for years. So it's not
new but also not common enough to be a big concern. Once a user has
settled on a choice of resolution and rebooted, they will never see it
again.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Confirmed
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1967450] Re: When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
The video shows what happens when user is using 175% fractional scaling
and then deactivate Fractional Scaling:
- only the upper left part of the screen is used
- a popup asks if user wants to keep or revert the changes
- if user clicks Revert, it doesn't actually revert back to Fractional Scaling,
but it remains in integer scaling, and the whole screen is being used.
** Attachment added: "lp1967450_fractional_scaling.mp4"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+attachment/5575453/+files/lp1967450_fractional_scaling.mp4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
New
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image
generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel
extra modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux
kernel signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967450/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%
Fixed by wayland-surface-Disable-WL_SURFACE_ERROR_INVALID_SIZE-che.patch
which is in:
https://launchpad.net/ubuntu/+source/mutter/42.0-1ubuntu1
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1967448
Title:
All the windows and the desktop icons disappear constantly after
setting Scaling to 300%
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Summary
===
Device with nvidia GPU, using proprietary drivers, wayland activated
by default.
By default, the scaling is set to 200% (the screen is UHD). If
selecting 300%, all the windows close down, as well as the desktop
icons (Home) as long as the mouse cursor is in the way.
To fix the issue, one has to open the Display Settings (while making
sure the mouse cursor is never above any of the Settings windows!),
then set Scaling back to 200% using the keyboard.
This problem does not happen in X11, and does not happen in Wayland if
I select 100%, 200% or even 400% scaling!
Steps to reproduce
==
- Install 22.04 beta, selecting "install third party software" to make sure
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
- After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE
should return `wayland`)
- Go to Settings > Display, select 300% scaling, then press Apply
Expected result
===
The scaling is set to 300% and user can keep using the device.
Actual result
=
The scaling is set to 300% and all the windows are shut down. If user
tries to reopen a window (e.g. Terminal), it is shut down immediately
if the mouse cursor is hovering it. The desktop icons keep
disappearing and reappearing for as long as the mouse cursor is
hovering the background.
The only way to stop this is to go back to Settings > Display, and,
using the keyboard, set the scaling back to 200%.
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.045.15.0.23.25
amd64Complete Generic Linux kernel and headers
ii linux-headers-5.15.0-235.15.0-23.23
all Header files related to Linux kernel version 5.15.0
ii linux-headers-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.045.15.0.23.25
amd64Generic Linux kernel headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23
amd64Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25
amd64Generic Linux kernel image
ii linux-modules-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit
x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit
x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1
amd64Extra drivers for nvidia-510 for the generic-hwe-20.04
flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
(objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel signatures for nvidia modules for version
5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:24:25 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems'
[Desktop-packages] [Bug 1967450] [NEW] When switching from 175% fractional scaling back to integer scaling, only a quarter of the screen is used
Public bug reported:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or revert
them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel and
headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers for
version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64 Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel image
ii linux-modules-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel extra
modules for version 5.15.0 on 64 bit x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel
nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64 Extra
drivers for nvidia-510 for the generic-hwe-20.04 flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel
nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64 Linux kernel
signatures for nvidia modules for version 5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:51:09 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']"
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967450
Title:
When switching from 175% fractional scaling back to integer scaling,
only a quarter of the screen is used
Status in gnome-shell package in Ubuntu:
New
Bug description:
Steps
=
- In Settings > Display, activate Fractional Scaling, and set it to 175%.
- Deactivate fractional scaling and press Apply
Expected results
The screen goes back to 200% integer scaling
Actual results
==
Only the upper left quarter of the screen is being used.
Workaround
==
After pressing Apply, a popup asks if we want to keep changes or
revert them.
Pressing "Revert" does not revert anything, but actually updates the
screen to use the full screen instead of just the upper left section,
while remaining in 200% integer scaling!
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.04 5.15.0.23.25 amd64 Complete Generic Linux kernel
and headers
ii linux-headers-5.15.0-23 5.15.0-23.23 all Header files related to Linux
kernel version 5.15.0
ii linux-headers-5.15.0-23-generic 5.15.0-23.23 amd64 Linux kernel headers
for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.04 5.15.0.23.25 amd64 Generic Linux kernel
headers
ii linux-image-5.15.0-23-generic 5.15.
[Desktop-packages] [Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)
Maybe related to https://gitlab.gnome.org/GNOME/mutter/-/issues/2083 (bug 1967448) ? ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2083 https://gitlab.gnome.org/GNOME/mutter/-/issues/2083 -- 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/1965563 Title: gnome-extensions-app fails to start (Protocol error) Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%
Tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/2083 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2083 https://gitlab.gnome.org/GNOME/mutter/-/issues/2083 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2083 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Fix Committed ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Tags added: fixed-in-42.1 fixed-upstream -- 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/1967448 Title: All the windows and the desktop icons disappear constantly after setting Scaling to 300% Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: Summary === Device with nvidia GPU, using proprietary drivers, wayland activated by default. By default, the scaling is set to 200% (the screen is UHD). If selecting 300%, all the windows close down, as well as the desktop icons (Home) as long as the mouse cursor is in the way. To fix the issue, one has to open the Display Settings (while making sure the mouse cursor is never above any of the Settings windows!), then set Scaling back to 200% using the keyboard. This problem does not happen in X11, and does not happen in Wayland if I select 100%, 200% or even 400% scaling! Steps to reproduce == - Install 22.04 beta, selecting "install third party software" to make sure ubuntu-drivers installs the appropriate proprietary nvidia drivers. - After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE should return `wayland`) - Go to Settings > Display, select 300% scaling, then press Apply Expected result === The scaling is set to 300% and user can keep using the device. Actual result = The scaling is set to 300% and all the windows are shut down. If user tries to reopen a window (e.g. Terminal), it is shut down immediately if the mouse cursor is hovering it. The desktop icons keep disappearing and reappearing for as long as the mouse cursor is hovering the background. The only way to stop this is to go back to Settings > Display, and, using the keyboard, set the scaling back to 200%. Information === Version: Ubuntu Jammy Jellyfish (development branch) [Beta image] Release: 22.04 Device: Dell Precision 7760 with Nvidia GPU CID: 202103-28858 Third party software installed during installation Wayland in use. ii linux-generic-hwe-20.045.15.0.23.25 amd64Complete Generic Linux kernel and headers ii linux-headers-5.15.0-235.15.0-23.23 all Header files related to Linux kernel version 5.15.0 ii linux-headers-5.15.0-23-generic5.15.0-23.23 amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP ii linux-headers-generic-hwe-20.045.15.0.23.25 amd64Generic Linux kernel headers ii linux-image-5.15.0-23-generic 5.15.0-23.23 amd64Signed kernel image generic ii linux-image-generic-hwe-20.04 5.15.0.23.25 amd64Generic Linux kernel image ii linux-modules-5.15.0-23-generic5.15.0-23.23 amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23 amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86 SMP ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64Linux kernel nvidia modules for version 5.15.0-23 ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1 amd64Extra drivers for nvidia-510 for the generic-hwe-20.04 flavour ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1 amd64Linux kernel nvidia modules for version 5.15.0-23 (objects) ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1 amd64Linux kernel signatures for nvidia modules for version 5.15.0-23-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd6
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Updating debdiff for focal to correct the bug number and use the
upstream fix.
** Patch added: "iio-sensor-proxy_2.8-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5575435/+files/iio-sensor-proxy_2.8-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in OEM Priority Project:
New
Status in iio-sensor-proxy package in Ubuntu:
Fix Released
Status in iio-sensor-proxy source package in Focal:
New
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+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 1967448] Re: All the windows and the desktop icons disappear constantly after setting Scaling to 300%
You can clearly see what's going on in the attached video.
** Attachment added: "lp1967448_scaling300.mp4"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967448/+attachment/5575424/+files/lp1967448_scaling300.mp4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967448
Title:
All the windows and the desktop icons disappear constantly after
setting Scaling to 300%
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Summary
===
Device with nvidia GPU, using proprietary drivers, wayland activated
by default.
By default, the scaling is set to 200% (the screen is UHD). If
selecting 300%, all the windows close down, as well as the desktop
icons (Home) as long as the mouse cursor is in the way.
To fix the issue, one has to open the Display Settings (while making
sure the mouse cursor is never above any of the Settings windows!),
then set Scaling back to 200% using the keyboard.
This problem does not happen in X11, and does not happen in Wayland if
I select 100%, 200% or even 400% scaling!
Steps to reproduce
==
- Install 22.04 beta, selecting "install third party software" to make sure
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
- After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE
should return `wayland`)
- Go to Settings > Display, select 300% scaling, then press Apply
Expected result
===
The scaling is set to 300% and user can keep using the device.
Actual result
=
The scaling is set to 300% and all the windows are shut down. If user
tries to reopen a window (e.g. Terminal), it is shut down immediately
if the mouse cursor is hovering it. The desktop icons keep
disappearing and reappearing for as long as the mouse cursor is
hovering the background.
The only way to stop this is to go back to Settings > Display, and,
using the keyboard, set the scaling back to 200%.
Information
===
Version: Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release: 22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.045.15.0.23.25
amd64Complete Generic Linux kernel and headers
ii linux-headers-5.15.0-235.15.0-23.23
all Header files related to Linux kernel version 5.15.0
ii linux-headers-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.045.15.0.23.25
amd64Generic Linux kernel headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23
amd64Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25
amd64Generic Linux kernel image
ii linux-modules-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit
x86 SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit
x86 SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1
amd64Extra drivers for nvidia-510 for the generic-hwe-20.04
flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
(objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel signatures for nvidia modules for version
5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:24:25 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-
[Desktop-packages] [Bug 1967448] [NEW] All the windows and the desktop icons disappear constantly after setting Scaling to 300%
Public bug reported:
Summary
===
Device with nvidia GPU, using proprietary drivers, wayland activated by
default.
By default, the scaling is set to 200% (the screen is UHD). If selecting
300%, all the windows close down, as well as the desktop icons (Home) as
long as the mouse cursor is in the way.
To fix the issue, one has to open the Display Settings (while making
sure the mouse cursor is never above any of the Settings windows!), then
set Scaling back to 200% using the keyboard.
This problem does not happen in X11, and does not happen in Wayland if I
select 100%, 200% or even 400% scaling!
Steps to reproduce
==
- Install 22.04 beta, selecting "install third party software" to make sure
ubuntu-drivers installs the appropriate proprietary nvidia drivers.
- After installation, make sure Wayland is in use (echo $XDG_SESSION_TYPE
should return `wayland`)
- Go to Settings > Display, select 300% scaling, then press Apply
Expected result
===
The scaling is set to 300% and user can keep using the device.
Actual result
=
The scaling is set to 300% and all the windows are shut down. If user
tries to reopen a window (e.g. Terminal), it is shut down immediately if
the mouse cursor is hovering it. The desktop icons keep disappearing and
reappearing for as long as the mouse cursor is hovering the background.
The only way to stop this is to go back to Settings > Display, and,
using the keyboard, set the scaling back to 200%.
Information
===
Version:Ubuntu Jammy Jellyfish (development branch) [Beta image]
Release:22.04
Device: Dell Precision 7760 with Nvidia GPU
CID: 202103-28858
Third party software installed during installation
Wayland in use.
ii linux-generic-hwe-20.045.15.0.23.25
amd64Complete Generic Linux kernel and headers
ii linux-headers-5.15.0-235.15.0-23.23
all Header files related to Linux kernel version 5.15.0
ii linux-headers-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel headers for version 5.15.0 on 64 bit x86 SMP
ii linux-headers-generic-hwe-20.045.15.0.23.25
amd64Generic Linux kernel headers
ii linux-image-5.15.0-23-generic 5.15.0-23.23
amd64Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.15.0.23.25
amd64Generic Linux kernel image
ii linux-modules-5.15.0-23-generic5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86
SMP
ii linux-modules-extra-5.15.0-23-generic 5.15.0-23.23
amd64Linux kernel extra modules for version 5.15.0 on 64 bit x86
SMP
ii linux-modules-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23
ii linux-modules-nvidia-510-generic-hwe-20.04 5.15.0-23.23+1
amd64Extra drivers for nvidia-510 for the generic-hwe-20.04
flavour
ii linux-objects-nvidia-510-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel nvidia modules for version 5.15.0-23 (objects)
ii linux-signatures-nvidia-5.15.0-23-generic 5.15.0-23.23+1
amd64Linux kernel signatures for nvidia modules for version
5.15.0-23-generic
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 1 10:24:25 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: mutter
Importance: Unknown
Status: Unknown
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: mutter (Ubuntu)
Importance: High
Status: Fix Committed
** Tags: amd64 apport-bug fixed-in-42.1 fixed-upstream jammy wayland-session
** Description changed:
Summary
===
Device with nvidia GPU, using proprietary drivers, wayland activated by
default.
By defa
[Desktop-packages] [Bug 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
> Would be possible to get the JS trace here? There is no JS trace. There is no JS running. -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl Status in gjs: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: Core was generated by `gnome-shell --sm-disable --mode=ubiquity'. Program terminated with signal SIGSEGV, Segmentation fault. In mozjs91: #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7f5a5002b200, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7f5a5002b218, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:482 #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at ../gjs/context.cpp:495 #13 0x7f5a6c0d2dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x557e2950bece in main (argc=, argv=) at ../src/main.c:659 In mozjs78: See bug 1947130 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
I haven't got to that yet. It will require a different kind of bug report to the Nvidia forums detailing which GBM function is failing, without mentioning these mutter symptoms. -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1967329] Re: Full screen in Firefox and Ubuntu panel options can't be displayed
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967329 Title: Full screen in Firefox and Ubuntu panel options can't be displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967329/+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 1967329] Re: Full screen in Firefox and Ubuntu panel options can't be displayed
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/1967329 Title: Full screen in Firefox and Ubuntu panel options can't be displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967329/+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 1967329] Re: Full screen in Firefox and Ubuntu panel options can't be displayed
I can't find the upstream reference but I think this was fixed in today's updates. Please try them: mutter: 42.0-1ubuntu1 gnome-shell: 42.0-1ubuntu1 -- 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/1967329 Title: Full screen in Firefox and Ubuntu panel options can't be displayed Status in gnome-shell package in Ubuntu: Incomplete Bug description: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967329/+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 1724732] Re: Wayland login options are missing when a radeon card is installed
This bug is closed. Please open a new bug if you have any problems, by running: ubuntu-bug gdm3 -- 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/1724732 Title: Wayland login options are missing when a radeon card is installed Status in gdm3 package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Wayland login options are missing when a radeon card is installed. GDM only offers Xorg sessions... 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] Subsystem: Hewlett-Packard Company Cedar GL [FirePro 2270] Kernel driver in use: radeon Kernel modules: radeon And I'm not in hybrid mode either. The integrated graphics device is not listed by lspci. Strangely I can start weston on another VT successfully. Only mutter/gdm3 is refusing to show Wayland as an option. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 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 Date: Thu Oct 19 11:18:11 2017 InstallationDate: Installed on 2017-05-03 (168 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724732/+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 1966115] Re: wrong icon used with the new branding
Fix committed, waiting for 42.0.1-1ubuntu2 ** Changed in: gnome-initial-setup (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1966115 Title: wrong icon used with the new branding Status in gnome-initial-setup package in Ubuntu: Fix Committed Bug description: Since the updated ubuntu branding has landed, the icon isn't just the logo. See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1966115/+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 1967198] Re: gnome-initial-setup icon in dock is badly sized
*** This bug is a duplicate of bug 1966115 *** https://bugs.launchpad.net/bugs/1966115 To avoid confusion, I think the correct state is 'Fix Committed' and 42.0.1-1ubuntu2 really fixes bug 1967198, not bug 1966115. ** This bug is no longer a duplicate of bug 1966115 wrong icon used with the new branding ** Changed in: gnome-initial-setup (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1967198 Title: gnome-initial-setup icon in dock is badly sized Status in gnome-initial-setup package in Ubuntu: Fix Committed Bug description: I noticed this while testing the beta jammy image (20220329) on arm64, but I checked and I see the same issue on amd64 as well. The best way I can describe it, is that it looks squished, as if it was sized incorrectly. I'll attach a screenshot showing the problem also. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-initial-setup 42.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19 Uname: Linux 5.15.0-1003-raspi aarch64 ApportVersion: 2.20.11-0ubuntu79 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 21:12:45 2022 ImageMediaBuild: 20220329 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1967198/+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 1967198] Re: gnome-initial-setup icon in dock is badly sized
*** This bug is a duplicate of bug 1966115 *** https://bugs.launchpad.net/bugs/1966115 Better yet, let's use bug 1966115 again but keep it open till the final fix lands. ** This bug has been marked a duplicate of bug 1966115 wrong icon used with the new branding -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1967198 Title: gnome-initial-setup icon in dock is badly sized Status in gnome-initial-setup package in Ubuntu: Fix Committed Bug description: I noticed this while testing the beta jammy image (20220329) on arm64, but I checked and I see the same issue on amd64 as well. The best way I can describe it, is that it looks squished, as if it was sized incorrectly. I'll attach a screenshot showing the problem also. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-initial-setup 42.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19 Uname: Linux 5.15.0-1003-raspi aarch64 ApportVersion: 2.20.11-0ubuntu79 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 21:12:45 2022 ImageMediaBuild: 20220329 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1967198/+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 1965727] Re: [jammy] Purple background is visible briefly during the login animation
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965727 Title: [jammy] Purple background is visible briefly during the login animation Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Purple background is visible briefly during the login animation. The hard-coded system background colour needs to be updated to match the new grey login screen in jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965727/+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 1878998] Re: Value in Yaru-dark/gnome-shell/gnome-shell.css not used
** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress -- 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/1878998 Title: Value in Yaru-dark/gnome-shell/gnome-shell.css not used Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Won't Fix Bug description: The value for selected-color at line 153 in the gnome-shell.css files for Yaru and Yaru-dark is ignored by the shell. (Selected text should change color from dark grey to white.) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-17 (214 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: yaru-theme PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxsf _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1878998/+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 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
> The most suspicious part of that stack I can find so far is in > gjs_context_finalize: > >GjsContextPrivate* gjs = GjsContextPrivate::from_object(object); >gjs->~GjsContextPrivate(); No, that's all fine... It's just calling the dtor manually because such object is manually allocated. -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl Status in gjs: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: Core was generated by `gnome-shell --sm-disable --mode=ubiquity'. Program terminated with signal SIGSEGV, Segmentation fault. In mozjs91: #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7f5a5002b200, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7f5a5002b218, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:482 #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at ../gjs/context.cpp:495 #13 0x7f5a6c0d2dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x557e2950bece in main (argc=, argv=) at ../src/main.c:659 In mozjs78: See bug 1947130 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+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 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
Would be possible to get the JS trace here? -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl Status in gjs: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: Core was generated by `gnome-shell --sm-disable --mode=ubiquity'. Program terminated with signal SIGSEGV, Segmentation fault. In mozjs91: #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7f5a5002b200, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7f5a5002b218, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:482 #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at ../gjs/context.cpp:495 #13 0x7f5a6c0d2dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x557e2950bece in main (argc=, argv=) at ../src/main.c:659 In mozjs78: See bug 1947130 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+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 1964964] Re: libayatana-appindicator 0.5.90-7 breaks libappindicator3-1
This bug was fixed in the package libayatana-appindicator - 0.5.90-7ubuntu2 --- libayatana-appindicator (0.5.90-7ubuntu2) jammy; urgency=medium * debian/control: - version the provides to match depends constrains -- Sebastien Bacher Mon, 28 Mar 2022 15:09:30 +0200 ** Changed in: libayatana-appindicator (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libayatana-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1964964 Title: libayatana-appindicator 0.5.90-7 breaks libappindicator3-1 Status in libayatana-appindicator package in Ubuntu: Fix Released Bug description: On Ubuntu 22.04 (Jammy) the latest libayatana-appindicator3-1 and gir1.2-ayatanaappindicator3-0.1 0.5.90-7 broke libappindicator3-1, gir1.2-appindicator3-0.1and related apps like indicator-application. GitHub libayatana-appindicator issue #53 https://github.com/AyatanaIndicators/libayatana-appindicator/issues/53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1964964/+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 1965072] Re: In Xorg sessions, desktop icons flicker when entering the overview
This bug was fixed in the package gnome-shell - 42.0-1ubuntu1 --- gnome-shell (42.0-1ubuntu1) jammy; urgency=medium [ Jeremy Bicha ] * Merge with Debian. * Add patches to revert switch to new gnome-bluetooth * Revert "debian/control.in: Switch to gnome-bluetooth3" [ Marco Trevisan (Treviño) ] * debian/patches: Refresh * debian/patches: Fix monitor switching configuration (LP: #1964496) * debian/patches: Overview, remove desktop fade logic (LP: #1965072) * debian/patches: Cherry-pick various upstream fixes targeting 42.1 * js: Support legacy GNOME Control Center (now Settings) dbus name * shellDBus: Actually make ScreenTransitionAsync async [ Jeremy Bicha ] * Remaining changes with debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming + gnome-remote-desktop to provide remote desktop support by default - Moved some Recommends to Suggests: + chrome-gnome-shell - Update debian/gbp.conf with Ubuntu settings - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - optional-hot-corner.patch + enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - ubuntu/layout-Make-starting-in-the-overview-optional.patch: + Makes dock replace overview easier - ubuntu/layout-Try-to-allocate-before-getting-size-of-tracke.patch: + Ensure windows don't get maximized under the panels / dock - ubuntu/sessionMode-Add-support-for-configuring-an-icons-resource.patch: + Support loading iconsResourceName from session file - ubuntu/main-Support-loading-multiple-Yaru-theme-variants.patch: + Support loading Yaru theme variants (for accent color) - debian/patches: Support configuring icons resource to use for mode - debian/ubuntu-session-mods/ubuntu.json: Use Yaru's gnome-shell icons - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814) gnome-shell (42.0-1) experimental; urgency=medium * New upstream release * debian/control.in: Bump minimum mutter to 42.0 * Add patch to restore Settings item in system menu (LP: #1964136) gnome-shell (42~rc-1) experimental; urgency=medium * New upstream release * debian/control.in: Bump minimum mutter to 42~rc * debian/control.in: Switch to gnome-bluetooth3 * Drop patches reverting use of gnome-bluetooth3 * Drop patches applied in new release -- Marco Trevisan (Treviño) Mon, 28 Mar 2022 16:31:13 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1965072 Title: In Xorg sessions, desktop icons flicker when entering the overview Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Invalid Bug description: In Xorg sessions, desktop icons flicker when entering the overview. I think this is a combination of a new feature in DING: https://gitlab.com/rastersoft/desktop-icons- ng/-/commit/
[Desktop-packages] [Bug 1964496] Re: [GS 42] display switching key does not work
This bug was fixed in the package gnome-shell - 42.0-1ubuntu1 --- gnome-shell (42.0-1ubuntu1) jammy; urgency=medium [ Jeremy Bicha ] * Merge with Debian. * Add patches to revert switch to new gnome-bluetooth * Revert "debian/control.in: Switch to gnome-bluetooth3" [ Marco Trevisan (Treviño) ] * debian/patches: Refresh * debian/patches: Fix monitor switching configuration (LP: #1964496) * debian/patches: Overview, remove desktop fade logic (LP: #1965072) * debian/patches: Cherry-pick various upstream fixes targeting 42.1 * js: Support legacy GNOME Control Center (now Settings) dbus name * shellDBus: Actually make ScreenTransitionAsync async [ Jeremy Bicha ] * Remaining changes with debian: - Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds - Add some Recommends: + ubuntu-session (| gnome-session) to have the ubuntu session available + xserver-xorg-legacy + yaru-theme-gnome-shell for the default ubuntu theming + gnome-remote-desktop to provide remote desktop support by default - Moved some Recommends to Suggests: + chrome-gnome-shell - Update debian/gbp.conf with Ubuntu settings - gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative - ubuntu/desktop_detect.patch: + add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. - ubuntu/smarter_alt_tab.patch: + quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. - ubuntu/lightdm-user-switching.patch: + Allow user switching when using LightDM. - ubuntu/lock_on_suspend.patch + Respect Ubuntu's lock-on-suspend setting. - ubuntu/background_login.patch + Change default background color as we modified the default GDM color for our ubuntu session. - ubuntu/gdm_alternatives.patch + Add support for GDM3 theme alternatives - optional-hot-corner.patch + enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. - main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: + Improve debug JS tracing for crash reports - ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: + stop searches when requested from UI - magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch: + Show monitor scaled cursor when magnifier is enabled - ubuntu/layout-Make-starting-in-the-overview-optional.patch: + Makes dock replace overview easier - ubuntu/layout-Try-to-allocate-before-getting-size-of-tracke.patch: + Ensure windows don't get maximized under the panels / dock - ubuntu/sessionMode-Add-support-for-configuring-an-icons-resource.patch: + Support loading iconsResourceName from session file - ubuntu/main-Support-loading-multiple-Yaru-theme-variants.patch: + Support loading Yaru theme variants (for accent color) - debian/patches: Support configuring icons resource to use for mode - debian/ubuntu-session-mods/ubuntu.json: Use Yaru's gnome-shell icons - Break gnome-shell-extension-desktop-icons (<< 19.01.3+git20190814) gnome-shell (42.0-1) experimental; urgency=medium * New upstream release * debian/control.in: Bump minimum mutter to 42.0 * Add patch to restore Settings item in system menu (LP: #1964136) gnome-shell (42~rc-1) experimental; urgency=medium * New upstream release * debian/control.in: Bump minimum mutter to 42~rc * debian/control.in: Switch to gnome-bluetooth3 * Drop patches reverting use of gnome-bluetooth3 * Drop patches applied in new release -- Marco Trevisan (Treviño) Mon, 28 Mar 2022 16:31:13 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1964496 Title: [GS 42] display switching key does not work Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: Hi, Using GS 42 in Jammy, when I press the display switch key of my laptop keyboard, I get the usual pop-up but the selected item is not applied. I have to use gnome-control-center to configure my displays. (gcc is slow to start these days?) To manage
[Desktop-packages] [Bug 1965993] Re: [UIFe] Remove Ubuntu Pro settings
This bug was fixed in the package software-properties - 0.99.21 --- software-properties (0.99.21) jammy; urgency=medium * Remove Ubuntu Pro settings (LP: #1965993) -- Robert Ancell Wed, 23 Mar 2022 12:11:31 +1300 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965993 Title: [UIFe] Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: Fix Released Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
This bug was fixed in the package intel-media-driver - 22.2.1+dfsg1-1build1 --- intel-media-driver (22.2.1+dfsg1-1build1) jammy; urgency=medium * Rebuild with the current libva version (lp: #1966571) -- Sebastien Bacher Tue, 29 Mar 2022 16:47:39 +0200 ** Changed in: intel-media-driver (Ubuntu) Status: Fix Committed => Fix Released -- 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/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE 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.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE: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.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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://
[Desktop-packages] [Bug 1724732] Re: Wayland login options are missing when a radeon card is installed
I am having a similar issue on Ubuntu 22.04 with Asus Tuf A15 FA605IH -- 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/1724732 Title: Wayland login options are missing when a radeon card is installed Status in gdm3 package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Wayland login options are missing when a radeon card is installed. GDM only offers Xorg sessions... 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] Subsystem: Hewlett-Packard Company Cedar GL [FirePro 2270] Kernel driver in use: radeon Kernel modules: radeon And I'm not in hybrid mode either. The integrated graphics device is not listed by lspci. Strangely I can start weston on another VT successfully. Only mutter/gdm3 is refusing to show Wayland as an option. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 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 Date: Thu Oct 19 11:18:11 2017 InstallationDate: Installed on 2017-05-03 (168 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724732/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I've also got an Avantree DG80 as a workaround and I can confirm it works with my Trekz OpenComm headset. It supports sounds up to 8 kHz (corresponding to mSBC with a 16 kHz sampling frequency) with the mic enabled, while anything connected directly to Linux bluetooth only goes up to 4 kHz in HSP/HFP mode (CVSD). The sound with mSBC is still noticeably worse than in A2DP mode when listening to music, but a lot better than CVSD. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1923052] Re: screen reader does not read ubiquity window
** Changed in: ubiquity (Ubuntu Jammy) Milestone: None => ubuntu-22.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Incomplete Status in orca package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Confirmed Status in at-spi2-core source package in Jammy: Incomplete Status in orca source package in Jammy: Incomplete Status in ubiquity source package in Jammy: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
I followed the same test, s/focal/jammy/ in /etc/apt/sources.list and apt-get update. I then first installed the new snapd from jammy: ... Preparing to unpack .../6-snapd_2.55.2+22.04_amd64.deb ... Unpacking snapd (2.55.2+22.04) over (2.54.3+20.04.1ubuntu0.2) ... ... Setting up snapd (2.55.2+22.04) ... Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ... snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it. ... I then ran "sudo apt-get dist-upgrade" but I still encountered the same error: Errors were encountered while processing: /tmp/apt-dpkg-install-DY0azb/17-firefox_1%3a1snap1-0ubuntu1_amd64.deb Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku0
[Desktop-packages] [Bug 1966572] Re: Chromium Zero Day
B[], aha, you've received no Chromium updates since November 2021 because the author of that PPA hasn't provided any. apt-file will report what files are in the Ubuntu package whether or not you have it installed. It's very handy to see what files are in an Ubuntu package without installing it. dpkg -l will report what files are in the package that you've got installed. It's the better tool if you have installed third-party packages. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1966572 Title: Chromium Zero Day Status in chromium-browser package in Ubuntu: Fix Released Bug description: Please see: https://chromereleases.googleblog.com/2022/03/stable- channel-update-for-desktop_25.html Apparently this also affects the Chromium package and is being actively exploited in the wild: > [$TBD][1309225] High CVE-2022-1096: Type Confusion in V8. Reported by anonymous on 2022-03-23 Please update from Version 97.0.4692.20 (last updated 2021-11-26) to latest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1966572/+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 1967161] Re: gnome-initial-setup crashed with SIGSEGV
*** This bug is a duplicate of bug 1966524 *** https://bugs.launchpad.net/bugs/1966524 ** This bug is no longer a duplicate of private bug 1967075 ** This bug has been marked a duplicate of bug 1966524 yelp crashed with SIGSEGV in WebKit::WaylandCompositor::Buffer::createImage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1967161 Title: gnome-initial-setup crashed with SIGSEGV Status in gnome-initial-setup package in Ubuntu: New Bug description: crash when try to add google account Ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-initial-setup 42.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 18:21:54 2022 ExecutablePath: /usr/libexec/gnome-initial-setup InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcCmdline: /usr/libexec/gnome-initial-setup --existing-user ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4485d8430b:mov0x8,%rax PC (0x7f4485d8430b) ok source "0x8" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-initial-setup StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 Title: gnome-initial-setup crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1967161/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
I am not installing all updates my docker file is as follows RUN echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted' >> /etc/apt/sources.list && \ apt-get update -q -y && \ apt-get install -y --fix-missing --no-install-recommends \ libx11-6 \ //more packages apt-get purge -y pm-utils xscreensaver* && \ apt-get autoremove -y && \ apt-get clean -y && \ rm -rf /var/lib/apt/lists/* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1
[Desktop-packages] [Bug 1967176] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libjpeg-turbo8 no debug symbol package found for libcrypt1 no debug symbol package found for libnvidia-gl-510 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967176/+attachment/5574891/+files/CoreDump.gz -- 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/1967176 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42~beta-1ubuntu3 Candidate: 42~beta-1ubuntu3 Version table: *** 42~beta-1ubuntu3 500 500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status nvidia 1030. nvidia-driver-510 3) What you expected to happen just logout and login again 4) What happened instead after logout and login again, apport reported this crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 22:40:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967176/+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 1967176] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967176/+attachment/5575359/+files/ThreadStacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967176 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42~beta-1ubuntu3 Candidate: 42~beta-1ubuntu3 Version table: *** 42~beta-1ubuntu3 500 500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status nvidia 1030. nvidia-driver-510 3) What you expected to happen just logout and login again 4) What happened instead after logout and login again, apport reported this crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 22:40:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967176/+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 1967176] gnome-shell crashed with SIGSEGV
Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceSource: #0 0x7ffbc79eda7c in ?? () StacktraceTop: ?? () -- 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/1967176 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42~beta-1ubuntu3 Candidate: 42~beta-1ubuntu3 Version table: *** 42~beta-1ubuntu3 500 500 http://mirror.docker.ru/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status nvidia 1030. nvidia-driver-510 3) What you expected to happen just logout and login again 4) What happened instead after logout and login again, apport reported this crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 22:40:45 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7ffbc79eda7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffc1a2ffa60 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967176/+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 1966589] Re: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1`
the error is similar to the one on bug #1965805 which was said to be fixed by the new snapd, it would be worth checking if upgrading snapd on the system before upgrading fixes the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 07/08/2021 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.2 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.2:bd07/08/2021:br1.20:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:sku06B9: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966589/+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 1967150] ThreadStacktrace.txt
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1967150/+attachment/5575357/+files/ThreadStacktrace.txt
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
--
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/1967150
Title:
gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
This was running a live session of the jammy beta candidate image
20220329.1 in qemu. I let it sit for a bit after booting, came back to
the session and came out of the screen blank and saw it reporting this
crash had occurred. The session has been up 41 minutes but the files
in /var/crash are timestamped from just a few minutes ago so I think
it may have happened coming out of the screen blank.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 14:31:13 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SegvAnalysis:
Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
PC (0x7f8255af2f44) ok
source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f8255af2f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967150/+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 1967150] Crash report cannot be processed
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:
no debug symbol package found for libjpeg-turbo8
no debug symbol package found for libcrypt1
Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.
Thank you for your understanding, and sorry for the inconvenience!
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1967150/+attachment/5574783/+files/CoreDump.gz
--
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/1967150
Title:
gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
This was running a live session of the jammy beta candidate image
20220329.1 in qemu. I let it sit for a bit after booting, came back to
the session and came out of the screen blank and saw it reporting this
crash had occurred. The session has been up 41 minutes but the files
in /var/crash are timestamped from just a few minutes ago so I think
it may have happened coming out of the screen blank.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 14:31:13 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SegvAnalysis:
Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
PC (0x7f8255af2f44) ok
source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f8255af2f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967150/+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 1967150] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
Stacktrace:
#0 0x7f8255af2f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceSource: #0 0x7f8255af2f44 in ?? ()
StacktraceTop: ?? ()
--
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/1967150
Title:
gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
This was running a live session of the jammy beta candidate image
20220329.1 in qemu. I let it sit for a bit after booting, came back to
the session and came out of the screen blank and saw it reporting this
crash had occurred. The session has been up 41 minutes but the files
in /var/crash are timestamped from just a few minutes ago so I think
it may have happened coming out of the screen blank.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 14:31:13 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SegvAnalysis:
Segfault happened at: 0x7f8255af2f44:mov(%rsi),%rax
PC (0x7f8255af2f44) ok
source "(%rsi)" (0x35d82c10) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f8255af2f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd8bbdf190
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967150/+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 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
** Changed in: gvfs (Ubuntu) Milestone: None => ubuntu-22.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() Status in gvfs package in Ubuntu: Confirmed Bug description: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+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 1965558] Re: Cannot change wallpaper by right-clicking image in dark theme
Thanks for fixing this, I also noticed same.Maybe i need to update the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1965558 Title: Cannot change wallpaper by right-clicking image in dark theme Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: Fix Released Bug description: With the light theme enabled, you can set the desktop wallpaper by right-clicking on an image file's icon in the file manager and selecting "Set As Wallpaper". When you do this the Desktop wallpaper changes straight away. Now change to dark theme and repeat the above steps. The wallpaper never changes. You can however change the wallpaper fine using Gnome settings -> Appearance. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu6 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 16:14:38 2022 InstallationDate: Installed on 2022-02-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1965558/+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 1966589] Re: Upgrader unable to contact snap store
I was able to recreate this on an Ubuntu 20.04 LTS system by editing /etc/apt/sources.list so that focal was replaced with jammy and then running `sudo apt-get update` and `sudo apt-get dist-upgrade`. I then found the following in the terminal: Errors were encountered while processing: /tmp/apt-dpkg-install-pYF5m8/17-firefox_1%3a1snap1-0ubuntu1_amd64.deb Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) And the same error as posted earlier in /var/log/apt/term.log: ==> Installing the firefox snap^M error: cannot perform the following tasks:^M - Run configure hook of "firefox" snap if present (run hook "configure": error: cannot create transient scope: DBus error "org.freedesktop.DBus.Error.TimedOut": [Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)])^M dpkg: error processing archive /tmp/apt-dpkg-install-pYF5m8/17-firefox_1%3a1snap1-0ubuntu1_amd64.deb (--unpack):^M new firefox package pre-installation script subprocess returned error exit status 1^M ** Changed in: firefox (Ubuntu) Milestone: None => ubuntu-22.04 ** Summary changed: - Upgrader unable to contact snap store + release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966589 Title: release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` Status in firefox package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upgrading from Lubuntu Focal 20.04.4 to Lubuntu Jammy 22.04 (date 27.03.2022) The upgrader was unable to connect to the snap store in order to install the firefox snap The upgrade was performed with GUI - do-release-upgrade -d -m desktop -f DistUpgradeViewKDE The error "could not install the upgrades" was received. I closed the error and then received th dialog box message "upgrade complete but there were errors during the upgrade process" After rebooting I received an upgrade notification and the Firefox snap was installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: LXQt Date: Sun Mar 27 13:08:26 2022 InstallationDate: Installed on 2022-03-27 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2022-03-27 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kf 950 F pulseaudio BuildID: 20220322144853 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 22.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev enp0s31f6 proto dhcp metric 100 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.250 metric 100 Package: ubuntu-release-upgrader PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:364 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=98.0.2/20220322144853 (In use) RunningIncompatibleAddons: False Tags: jammy Uname: Linux 5.13.0-39-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window
I also tested this with an Ubuntu 21.10 image and observed the same behavior as with Jammy. ** Also affects: orca (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: ubiquity (Ubuntu Jammy) Importance: High Status: Confirmed ** Also affects: at-spi2-core (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Tags removed: rls-jj-incoming ** Tags added: fr-2159 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Incomplete Status in orca package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Confirmed Status in at-spi2-core source package in Jammy: Incomplete Status in orca source package in Jammy: Incomplete Status in ubiquity source package in Jammy: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1923052] Re: screen reader does not read ubiquity window
I tested this following the instructions in test case 1309 and did not hear the screen reader read the ubiquity window after choosing Try Ubuntu. The screen reader was working though and happily read other windows. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Incomplete Status in orca package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1967290] Re: USB Kyb and Mouse hangs "Suspend" ?
Just to confirm: I can open a putty xterm from a remote computer even though mouse & Kyb non responsive on jammy box. ** Package changed: ubuntu => gnome-session (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1967290 Title: USB Kyb and Mouse hangs "Suspend" ? Status in gnome-session package in Ubuntu: New Bug description: Hi, My email is: zolt...@geograph.co.za My system is: root@gs00:/home/geograph# uname -a Linux gs00 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux I update this beta sometime twice per day, and this problem persists. I have 1 monitor with 2 inputs. One input is dedicated to my laptop and the other to this jammy system. I have separate USB Kyb/Mouse HW connected directly to each of these computers (so they are never disconnected). I have my power settings set to never logout/lockscreen etc. and I can leave the system for long periods with no typing or mouse movements as long as I do not switch the monitor input away from jammy. If I switch the monitor over to get signal from the laptop and then some time later switch it back to the jammy desktop, I find that the Kyb/Mouse connected to jammy is non-active even though the Kyb & Mouse lights are on. I have tried replugging the Kyb/Mouse. I have to reboot the system to get control of its Kyb & Mouse. I do get lots of these messages in syslog (so suspect a GDK problem). Thanks and regards, Zoltan. Mar 31 14:46:06 gs00 gnome-shell[3873]: message repeated 3 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.187: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.194: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: GNOME nautilus 42.0 Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.208: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.215: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 8 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.215: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.216: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 30 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.216: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.217: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 39 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.217: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.218: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 2 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.218: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: Not enough space to add icons Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.223: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 48 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.223: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: Detected async api for thumbnails Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.480: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 4 times: [ DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.480: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.481: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1967290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1967290] [NEW] USB Kyb and Mouse hangs "Suspend" ?
You have been subscribed to a public bug: Hi, My email is: zolt...@geograph.co.za My system is: root@gs00:/home/geograph# uname -a Linux gs00 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux I update this beta sometime twice per day, and this problem persists. I have 1 monitor with 2 inputs. One input is dedicated to my laptop and the other to this jammy system. I have separate USB Kyb/Mouse HW connected directly to each of these computers (so they are never disconnected). I have my power settings set to never logout/lockscreen etc. and I can leave the system for long periods with no typing or mouse movements as long as I do not switch the monitor input away from jammy. If I switch the monitor over to get signal from the laptop and then some time later switch it back to the jammy desktop, I find that the Kyb/Mouse connected to jammy is non-active even though the Kyb & Mouse lights are on. I have tried replugging the Kyb/Mouse. I have to reboot the system to get control of its Kyb & Mouse. I do get lots of these messages in syslog (so suspect a GDK problem). Thanks and regards, Zoltan. Mar 31 14:46:06 gs00 gnome-shell[3873]: message repeated 3 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.187: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.194: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: GNOME nautilus 42.0 Mar 31 14:46:06 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:06.208: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.215: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 8 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.215: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.216: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 30 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.216: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.217: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 39 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.217: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.218: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 2 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.218: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: Not enough space to add icons Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.223: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 48 times: [ DING: (gjs:578106): Gdk-CRITICAL **: 14:46:07.223: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: Detected async api for thumbnails Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.480: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed Mar 31 14:46:07 gs00 gnome-shell[3873]: message repeated 4 times: [ DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.480: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed] Mar 31 14:46:07 gs00 gnome-shell[3873]: DING: (gjs:578138): Gdk-CRITICAL **: 14:46:07.481: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment hangs hid suspend-resume -- USB Kyb and Mouse hangs "Suspend" ? https://bugs.launchpad.net/bugs/1967290 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967329] [NEW] Full screen in Firefox and Ubuntu panel options can't be displayed
Public bug reported: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967329 Title: Full screen in Firefox and Ubuntu panel options can't be displayed Status in gnome-shell package in Ubuntu: New Bug description: In Ubuntu 22.04 and all programs just normally displayed e.g. Firefox in normal view. I can hover to the clock widget or top-right corner network-sound-battery widget and panel widget color gets changed from black to gray color. When clicked on widget pop-up menu appears as expected and any option can be selected. Now when in Firefox playing some video e.g. youtube.com in full screen then when pressing Super key panel is displayed. Moving mouse over to clock or top-right network widget and clock or network panel widget color changes from black to gray as in previous example. But when clicking on clock or network widget and nothing happens. Maybe pop-up is opened bellow Firefox's full screen window, but this is not what I expect. Obviously I would like to have panel widget pop-up menu displayed on top of anything else. For example when in Firefox playing some video in full-screen and I decide to lower the voice in Ubuntu, now I am force to quit Firefox video full screen and lower the Ubuntu panel located voice. I somehow expect this to be simpler, just to never quit full screen and allow me to lower the voice by pressing Super key and then from top-right voice widget allow me to lower the voice. I don't know if this can be classified as bug, but to me it is for sure an usability bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 18:10:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967329/+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 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() Status in gvfs package in Ubuntu: Confirmed Bug description: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+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 1964547] Re: [apt] Firefox 98 installed from apt cannot Play YouTube
And this is the content of amdgpu.ids It's just a plain text file # List of AMDGPU IDs # # Syntax: # device_id,revision_id,product_name<-- single tab after comma 1.0.0 15DD, C3, AMD Radeon(TM) Vega 3 Graphics 15DD, CB, AMD Radeon(TM) Vega 3 Graphics 15DD, CE, AMD Radeon(TM) Vega 3 Graphics 15DD, D8, AMD Radeon(TM) Vega 3 Graphics 15DD, CC, AMD Radeon(TM) Vega 6 Graphics 15DD, D9, AMD Radeon(TM) Vega 6 Graphics 15DD, C2, AMD Radeon(TM) Vega 8 Graphics 15DD, C4, AMD Radeon(TM) Vega 8 Graphics 15DD, C8, AMD Radeon(TM) Vega 8 Graphics 15DD, CA, AMD Radeon(TM) Vega 8 Graphics 15DD, D1, AMD Radeon(TM) Vega 8 Graphics 15DD, D5, AMD Radeon(TM) Vega 8 Graphics 15DD, D7, AMD Radeon(TM) Vega 8 Graphics 15DD, C3, AMD Radeon(TM) Vega 10 Graphics 15DD, D0, AMD Radeon(TM) Vega 10 Graphics 15DD, C1, AMD Radeon(TM) Vega 11 Graphics 15DD, C6, AMD Radeon(TM) Vega 11 Graphics 15DD, C9, AMD Radeon(TM) Vega 11 Graphics 15DD, D3, AMD Radeon(TM) Vega 11 Graphics 15DD, D6, AMD Radeon(TM) Vega 11 Graphics 15DD, 81, AMD Ryzen Embedded V1807B with Radeon Vega Gfx 15DD, 82, AMD Ryzen Embedded V1756B with Radeon Vega Gfx 15DD, 83, AMD Ryzen Embedded V1605B with Radeon Vega Gfx 15DD, 85, AMD Ryzen Embedded V1202B with Radeon Vega Gfx 15D8, 93, AMD Radeon(TM) Vega 1 Graphics 15D8, C4, AMD Radeon(TM) Vega 3 Graphics 15D8, C5, AMD Radeon(TM) Vega 3 Graphics 15D8, CC, AMD Radeon(TM) Vega 3 Graphics 15D8, CE, AMD Radeon(TM) Vega 3 Graphics 15D8, CF, AMD Radeon(TM) Vega 3 Graphics 15D8, D4, AMD Radeon(TM) Vega 3 Graphics 15D8, DC, AMD Radeon(TM) Vega 3 Graphics 15D8, DD, AMD Radeon(TM) Vega 3 Graphics 15D8, DE, AMD Radeon(TM) Vega 3 Graphics 15D8, DF, AMD Radeon(TM) Vega 3 Graphics 15D8, E3, AMD Radeon(TM) Vega 3 Graphics 15D8, E4, AMD Radeon(TM) Vega 3 Graphics 15D8, A3, AMD Radeon(TM) Vega 6 Graphics 15D8, B3, AMD Radeon(TM) Vega 6 Graphics 15D8, C3, AMD Radeon(TM) Vega 6 Graphics 15D8, D3, AMD Radeon(TM) Vega 6 Graphics 15D8, A2, AMD Radeon(TM) Vega 8 Graphics 15D8, B2, AMD Radeon(TM) Vega 8 Graphics 15D8, C2, AMD Radeon(TM) Vega 8 Graphics 15D8, C9, AMD Radeon(TM) Vega 8 Graphics 15D8, CB, AMD Radeon(TM) Vega 8 Graphics 15D8, D2, AMD Radeon(TM) Vega 8 Graphics 15D8, D9, AMD Radeon(TM) Vega 8 Graphics 15D8, DB, AMD Radeon(TM) Vega 8 Graphics 15D8, A1, AMD Radeon(TM) Vega 10 Graphics 15D8, B1, AMD Radeon(TM) Vega 10 Graphics 15D8, C1, AMD Radeon(TM) Vega 10 Graphics 15D8, D1, AMD Radeon(TM) Vega 10 Graphics 15D8, C8, AMD Radeon(TM) Vega 11 Graphics 15D8, CA, AMD Radeon(TM) Vega 11 Graphics 15D8, D8, AMD Radeon(TM) Vega 11 Graphics 15D8, DA, AMD Radeon(TM) Vega 11 Graphics 15D8, 91, AMD Ryzen Embedded R1606G with Radeon Vega Gfx 15D8, 92, AMD Ryzen Embedded R1505G with Radeon Vega Gfx 15D8, CF, AMD Ryzen Embedded R1305G with Radeon Vega Gfx 15D8, E4, AMD Ryzen Embedded R1102G with Radeon Vega Gfx 6600, 0, AMD Radeon HD 8600/8700M 6600, 81, AMD Radeon (TM) R7 M370 6601, 0, AMD Radeon (TM) HD 8500M/8700M 6604, 0, AMD Radeon R7 M265 Series 6604, 81, AMD Radeon (TM) R7 M350 6605, 0, AMD Radeon R7 M260 Series 6605, 81, AMD Radeon (TM) R7 M340 6606, 0, AMD Radeon HD 8790M 6607, 0, AMD Radeon (TM) HD8530M 6608, 0, AMD FirePro W2100 6610, 0, AMD Radeon HD 8600 Series 6610, 81, AMD Radeon (TM) R7 350 6610, 83, AMD Radeon (TM) R5 340 6611, 0, AMD Radeon HD 8500 Series 6613, 0, AMD Radeon HD 8500 series 6617, C7, AMD Radeon R7 240 Series 6640, 0, AMD Radeon HD 8950 6640, 80, AMD Radeon (TM) R9 M380 6646, 0, AMD Radeon R9 M280X 6646, 80, AMD Radeon (TM) R9 M470X 6647, 0, AMD Radeon R9 M270X 6647, 80, AMD Radeon (TM) R9 M380 6649, 0, AMD FirePro W5100 6658, 0, AMD Radeon R7 200 Series 665C, 0, AMD Radeon HD 7700 Series 665D, 0, AMD Radeon R7 200 Series 665F, 81, AMD Radeon (TM) R7 300 Series 6660, 0, AMD Radeon HD 8600M Series 6660, 81, AMD Radeon (TM) R5 M335 6660, 83, AMD Radeon (TM) R5 M330 6663, 0, AMD Radeon HD 8500M Series 6663, 83, AMD Radeon (TM) R5 M320 6664, 0, AMD Radeon R5 M200 Series 6665, 0, AMD Radeon R5 M200 Series 6665, 83, AMD Radeon (TM) R5 M320 6667, 0, AMD Radeon R5 M200 Series 666F, 0, AMD Radeon HD 8500M 66A1, 06, AMD Radeon (TM) Pro VII 66AF, C1, AMD Radeon VII 6780, 0, ATI FirePro V (FireGL V) Graphics Adapter 678A, 0, ATI FirePro V (FireGL V) Graphics Adapter 6798, 0, AMD Radeon HD 7900 Series 679A, 0, AMD Radeon HD 7900 Series 679B, 0, AMD Radeon HD 7900 Series 679
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1964541 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
Hi Daniel, In this case, do we have any ticket for nvidia to fix the GBM issue? We would like to highlight this to 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Committed Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+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 1966945] Re: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966945 Title: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head() Status in xdg-desktop-portal package in Ubuntu: New Bug description: Crash happened a short time after starting a screen cast / remote desktop session using the Freedesktop portal API in a Wayland session with mouse and keyboard input. Screen cast continues to run (i.e., PipeWire stream), but input stops. Unfortunately, at the moment I cannot provide much more details on the application used to trigger the issue and it could also be a problem on the application side, but even then this should probably not result in a crash of xdg-desktop-portal (which is the reason why I opened the bug report). lsb_release -rd: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 14:04:48 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x7fcf54779d7b:mov0x8(%rax),%rcx PC (0x7fcf54779d7b) ok source "0x8(%rax)" (0x7fcf0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __GI___nptl_deallocate_tsd () at ./nptl/nptl_deallocate_tsd.c:73 __GI___nptl_deallocate_tsd () at ./nptl/nptl_deallocate_tsd.c:22 start_thread (arg=) at ./nptl/pthread_create.c:453 Title: xdg-desktop-portal crashed with SIGSEGV in __GI___nptl_deallocate_tsd() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966945/+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 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"
** Changed in: mesa (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966221 Title: gnome-extensions-app crashes with "Segmentation fault (core dumped)" Status in Mesa: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Bug description: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1966221/+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 1967198] Re: gnome-initial-setup icon in dock is badly sized
*** This bug is a duplicate of bug 1966115 *** https://bugs.launchpad.net/bugs/1966115 the fix has been blocked in the review queue since tuesday https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=gnome- initial-setup ** Changed in: gnome-initial-setup (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1966115 wrong icon used with the new branding -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1967198 Title: gnome-initial-setup icon in dock is badly sized Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: I noticed this while testing the beta jammy image (20220329) on arm64, but I checked and I see the same issue on amd64 as well. The best way I can describe it, is that it looks squished, as if it was sized incorrectly. I'll attach a screenshot showing the problem also. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-initial-setup 42.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19 Uname: Linux 5.15.0-1003-raspi aarch64 ApportVersion: 2.20.11-0ubuntu79 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 21:12:45 2022 ImageMediaBuild: 20220329 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1967198/+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 1967174] Re: Installing with zfs results in bpool, rpool drives locked on the dock
Did the behaviour changed compared to previous cycles? If so that might be worth tagging as a regression and bumping a bit the importance since zfs is an option directly available in the installer -- 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/1967174 Title: Installing with zfs results in bpool, rpool drives locked on the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I installed the ubuntu 20220329 jammy beta with zfs root selected. After installation, there are drives on the dock for the zfs bpool and rpool (and in my case also a "1.6GB Encrypted" device since I also selected disk encryption at install time). These don't do anything useful when you click on them, and the only option when right-clicking is to mount them, which also doesn't result in anything observable from the UI (indeed, they should already be in use). Nor are they removable or 'un-pinnable' from the dock. You're just stuck with them taking up space. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 13:25:07 2022 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967174/+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 1967311] [NEW] Cloud account login page cannot be displayed
Public bug reported: When you click to log in to any of the cloud accounts, the pop-up window will be blank. This issue only occurs on Wayland, normal on Xorg ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 22:01:14 2022 InstallationDate: Installed on 2022-02-09 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed wayland-session ** Attachment added: "0.png" https://bugs.launchpad.net/bugs/1967311/+attachment/5575242/+files/0.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1967311 Title: Cloud account login page cannot be displayed Status in gnome-settings-daemon package in Ubuntu: New Bug description: When you click to log in to any of the cloud accounts, the pop-up window will be blank. This issue only occurs on Wayland, normal on Xorg ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 22:01:14 2022 InstallationDate: Installed on 2022-02-09 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1967311/+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 1964458] Re: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
** Changed in: gnome-shell (Ubuntu) Milestone: ubuntu-22.04-beta => ubuntu-22.04 -- 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/1964458 Title: [jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl Status in gjs: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: Core was generated by `gnome-shell --sm-disable --mode=ubiquity'. Program terminated with signal SIGSEGV, Segmentation fault. In mozjs91: #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7f5a5002b200, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7f5a5002b218, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:482 #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at ../gjs/context.cpp:495 #13 0x7f5a6c0d2dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x557e2950bece in main (argc=, argv=) at ../src/main.c:659 In mozjs78: See bug 1947130 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+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 1954980] Re: [snap] Chromium showing Japanese fonts incorrectly
Today it was experimental.refresh-app-awareness expiry time. It claimed it had waited long enough and did the refresh anyway without consulting me. Immediately my fonts broke. And, as usual, the red dot in the Ubuntu Dock (the "running applications indicator") next to the Chromium icon disappeared: a click on that icon will now open a _new_ Chromium instead of revealing the running one. (Another poor side effect from this snap auto-refresh thing.) Olivier: do you happen to know where I can find this expiry-awareness timer and raise it to a million days? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1954980 Title: [snap] Chromium showing Japanese fonts incorrectly Status in chromium-browser package in Ubuntu: Confirmed Bug description: It simply shows square rectangles for all Japanese characters this occurred after a recent update (earlier this week), a restart fixed it the first time but now it has reverted, probably after another update. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 11:54:12 2021 InstallationDate: Installed on 2019-02-08 (1041 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Snap: chromium 96.0.4664.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2021-12-01 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1954980/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Changed in: mesa (Ubuntu) Milestone: None => ubuntu-22.04 -- 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/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1886414] Re: the chromium snap takes a long time to install without visible user feedback, seems stuck
The most easyest thin in linux is installing, except chromium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1886414 Title: the chromium snap takes a long time to install without visible user feedback, seems stuck Status in chromium-browser package in Ubuntu: Confirmed Bug description: after an initial attemp to install where the progress got stuck at 20%, i rebooted as there were a bunch of other system updates that had been applied after a fresh isntall. Now chromium wont install dantheperson@danski:~$ sudo apt install chromium-browser Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: chromium-browser 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 48.4 kB of archives. After this operation, 164 kB of additional disk space will be used. Get:1 http://nz.archive.ubuntu.com/ubuntu focal-updates/universe amd64 chromium-browser amd64 81.0.4044.129-0ubuntu0.20.04.1 [48.4 kB] Fetched 48.4 kB in 0s (1,527 kB/s) Preconfiguring packages ... (Reading database ... 185728 files and directories currently installed.) Preparing to unpack .../chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap error: snap "chromium" has "install-snap" change in progress dpkg: error processing archive /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 10 Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 6 23:39:11 2020 Dependencies: ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-07-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1886414/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Changed in: devhelp Status: New => Invalid -- 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/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "AD_installed_packages.txt" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575198/+files/AD_installed_packages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "smb.conf" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575197/+files/smb.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "sssd.conf" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575196/+files/sssd.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "1641_environ_slow-machine_with-workaround.txt" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575194/+files/1641_environ_slow-machine_with-workaround.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "1274_environ_slow-machine_no-workaround.txt" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575192/+files/1274_environ_slow-machine_no-workaround.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "psauxf_slow-machine-with-workaroud.txt" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575193/+files/psauxf_slow-machine-with-workaroud.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "psauxf_fast-machine-no-workaroud.txt" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575195/+files/psauxf_fast-machine-no-workaroud.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
Hi Matthew,
I report the complete configuration of the machine in which I see the problem.
The machine is an Optiplex 745, with an Intel Core2 6320 CPU, 4 GB RAM and a
rotational HD, which I use as a test box for Ubuntu 22.04.
It was joined to an AD domain with the "net ads join -U aduser" command and
uses sssd for authentication and samba and winbind for sharing folders.
The minimun number of iterations needed for the
ExecStartPre=bash -c "for i in echo {1..20} ; do if [ $(env | grep KRB5CCNAME)
== "" ]; then sleep 0.2 ; fi ; done"
command to work is 15, so it's a delay of about 3 s.
I normally do not see the bug in my personal workstation, which runs
Ubuntu 20.04 and is a much faster machine (Ryzen 5 with nvme SSD).
>From the logs I can see that gvfsd is correctly started by systemd
--user also in all my cases; so I suspect that the problem is that, with
the slow machine, the kerberos ticket needed by gvfsd is actually
written to the hard disk with too much delay.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1779890
Title:
Nautilus does not use a valid Kerberos ticket when accessing Samba
share
Status in gvfs:
Unknown
Status in gvfs package in Ubuntu:
Triaged
Bug description:
Nautilus prompts for username and password when accessing a Samba
share on a network drive, despite having a perfectly valid unexpired
Kerberos ticket. The Kerberos ticket is obtained automatically at
logon by authentication against a Samba Active Directory server (Samba
AD-DC).
Accessing the same Samba share with the same Kerberos ticket via
"smbclient //host/sharename -k" works fine.
One known workaround is: "nautilus -q", and then "killall gvfsd".
After that, accessing the Samba share with Nautilus works normally as
it should.
I did not experience this issue in Ubuntu 16.04. It appears that a
regression was introduced somewhere between 16.04 and 18.04.
The issue is quite annoying and confusing for the users who are used
to accessing Samba shares on the network drive without being prompted
for their username and password.
The issue appears to manifest itself usually not on the first access
to a Samba share, but on subsequent accesses after a system reboot or
upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry
file before user login appears to fix the issue for the current user
session, but then the problem reappears upon subsequent user logins or
after a system reboot.
Nemo appears to have the same problem as Nautilus.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs-daemons 1.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 3 11:12:06 2018
ExecutablePath: /usr/lib/gvfs/gvfsd
InstallationDate: Installed on 2018-04-27 (66 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
LANG=en_CA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Attachment added: "psauxf_slow-machine-no-workaroud.txt" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1779890/+attachment/5575188/+files/psauxf_slow-machine-no-workaroud.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+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
