[Desktop-packages] [Bug 2043053] Re: Xorg/Wayland crash - maybe gnome-shell
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2043053
Title:
Xorg/Wayland crash - maybe gnome-shell
Status in xorg package in Ubuntu:
New
Bug description:
I recently upgraded a Dell OptiPlex 7000 from 23.04 to 23.10 and a new
install of Ubuntu 23.10 on a fresh Dell Latitude 7440. Both are now
unstable, regularly crashing out of gnome with a full plain white
screen with a sad terminal and "Oh no! Something has gone wrong." and
the only option being to Log Out.
It is regularly triggered when starting up totem/video or rhythmbox
and youtube in a browser, so perhaps audio or video related on both X
and Wayland. Also can be triggered on X with `Alt-F2 r`.
Has been happening for 2 weeks, regularly updating the system with
`wajig update; wajig distupgrade`. The issue remains.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 9 08:20:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
Subsystem: Dell Raptor Lake-P [Iris Xe Graphics] [1028:0c0b]
InstallationDate: Installed on 2023-10-19 (20 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2023
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.1
dmi.board.name: 0982JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.asset.tag: 080753
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.6
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.1:bd09/12/2023:br1.8:efr1.6:svnDellInc.:pnLatitude7440:pvr:rvnDellInc.:rn0982JK:rvrA03:cvnDellInc.:ct10:cvr:sku0C0B:
dmi.product.family: Latitude
dmi.product.name: Latitude 7440
dmi.product.sku: 0C0B
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2043053/+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 2043053] [NEW] Xorg/Wayland crash - maybe gnome-shell
You have been subscribed to a public bug:
I recently upgraded a Dell OptiPlex 7000 from 23.04 to 23.10 and a new
install of Ubuntu 23.10 on a fresh Dell Latitude 7440. Both are now
unstable, regularly crashing out of gnome with a full plain white screen
with a sad terminal and "Oh no! Something has gone wrong." and the only
option being to Log Out.
It is regularly triggered when starting up totem/video or rhythmbox and
youtube in a browser, so perhaps audio or video related on both X and
Wayland. Also can be triggered on X with `Alt-F2 r`.
Has been happening for 2 weeks, regularly updating the system with
`wajig update; wajig distupgrade`. The issue remains.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 9 08:20:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
(prog-if 00 [VGA controller])
Subsystem: Dell Raptor Lake-P [Iris Xe Graphics] [1028:0c0b]
InstallationDate: Installed on 2023-10-19 (20 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2023
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.1
dmi.board.name: 0982JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.asset.tag: 080753
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.6
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.1:bd09/12/2023:br1.8:efr1.6:svnDellInc.:pnLatitude7440:pvr:rvnDellInc.:rn0982JK:rvrA03:cvnDellInc.:ct10:cvr:sku0C0B:
dmi.product.family: Latitude
dmi.product.name: Latitude 7440
dmi.product.sku: 0C0B
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug crash mantic ubuntu
--
Xorg/Wayland crash - maybe gnome-shell
https://bugs.launchpad.net/bugs/2043053
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043057] [NEW] Graphical issues on WSL
Public bug reported: Any GUI application regardless of graphics framework (X, Wayland, GNOME, etc.) experiences heavy graphical issues and bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Nov 8 17:57:27 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy wayland-session ** Attachment added: "Picture of Firefox running on WSL" https://bugs.launchpad.net/bugs/2043057/+attachment/5717383/+files/Screenshot%202023-11-08%20175701.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2043057 Title: Graphical issues on WSL Status in xorg package in Ubuntu: New Bug description: Any GUI application regardless of graphics framework (X, Wayland, GNOME, etc.) experiences heavy graphical issues and bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Nov 8 17:57:27 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2043057/+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 2043055] [NEW] Screensaver stopped working
Public bug reported:
Just yesterday my screensaver preferences seem to have been overruled by
some always on feature (meaning that my screens aren't going blank after
5 minutes of inactivity, per my current screensaver preferences).
I have had this problem happen to me once or twice this year already but
now I felt like letting you guys know about it!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Wed Nov 8 17:48:41 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (208 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
LightdmDisplayLog: (EE) event3 - USB Optical Mouse Mouse: client bug: event
processing lagging behind by 33ms, your system is too slow
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (26 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2043055
Title:
Screensaver stopped working
Status in xorg package in Ubuntu:
New
Bug description:
Just yesterday my screensaver preferences seem to have been overruled
by some always on feature (meaning that my screens aren't going blank
after 5 minutes of inactivity, per my current screensaver
preferences).
I have had this problem happen to me once or twice this year already
but now I felt like letting you guys know about it!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Wed Nov 8 17:48:41 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc.
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Tim Woelfle (teadoub) which kernel version do you have? And for you make a file /etc/modprobe.d/snd conf and paste "options snd-sof-intel- hda-common hda_model=alc287-yoga9-bass-spk-pin" was enaugh? Thx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 2041155] Re: Nautiulus not open a NTFS drive from usb
I had the same issue, and I got the following when inserting a usb drive or external HD formatted with NTFS "Error mounting /dev/some-device at /media/username/some-drive-name: wrong fs type, bad option, bad superblock on /dev/some, missing codepage or helper program, or other error" It makes it sound like it was detecting an EXT2/3/4 type partition instead of NTFS. It was all working fine literally the hour before upgrading to Ubuntu 23.10 and now have the issue with drives that have never been touched by Windows but have NTFS on them needing to be rescued. Running ntfsfix or running Disks to check the file system option on the partition says that there are no errors. I did find an item from syslog about the kernel finding a dirty flag for one device when i went looking there but it happened AFTER upgrading to 23.10 2023-11-08T15:03:42.163421-05:00 NA kernel: [38161.331242] ntfs3: dm-3: volume is dirty and "force" flag is not set! Clearing the flag with ntfsfix -d /dev/devices-to-fix seems to handle it but the error message from the Nautilus dialog is severely misleading. But clearly something has changed and the error messaging is wrong, it also seems like something after the upgrade is setting the flag to dirty causing it all to fail. >From what i've seen the issue is starting to pop up on various forums. -- 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/2041155 Title: Nautiulus not open a NTFS drive from usb Status in nautilus package in Ubuntu: New Bug description: The problem: When i try to open a NTFS USB drive in nautilus i get the error "Error mounting /dev/sda1 at /media//: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error". What i expect: Mound the drive and show the drive directory in nautilus. Extra the drive that i use is a 2.5 inch external hardrive that connect with usb3. Ubuntu version that i use is Ubuntu 23.10 that is upgrade from Ubuntu 23.04. Early Ubuntu versions include ubuntu 23.04 work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2041155/+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 2043049] [NEW] logging out when screen goes blank
Public bug reported:
when the screen of my laptop goes blank, it will log me out. this
happens when I lock my laptop or put it to sleep. This only happens on
wayland.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 15:02:48 2023
DistUpgraded: 2023-11-02 23:55:54,921 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
openrazer-driver/3.4.0, 6.2.0-36-generic, x86_64: installed
openrazer-driver/3.4.0, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681]
(rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Rembrandt [Radeon 680M] [17aa:50b6]
InstallationDate: Installed on 2022-12-03 (341 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=32b06683-a98d-4585-81c7-edb51198f58c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to mantic on 2023-11-03 (6 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.40
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET70W (1.40 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CH000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.30
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET70W(1.40):bd08/08/2023:br1.40:efr1.30:svnLENOVO:pn21CH000GUS:pvrThinkPadT16Gen1:rvnLENOVO:rn21CH000GUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CH_BU_Think_FM_ThinkPadT16Gen1:
dmi.product.family: ThinkPad T16 Gen 1
dmi.product.name: 21CH000GUS
dmi.product.sku: LENOVO_MT_21CH_BU_Think_FM_ThinkPad T16 Gen 1
dmi.product.version: ThinkPad T16 Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug crash mantic ubuntu wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2043049
Title:
logging out when screen goes blank
Status in xorg package in Ubuntu:
New
Bug description:
when the screen of my laptop goes blank, it will log me out. this
happens when I lock my laptop or put it to sleep. This only happens on
wayland.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 15:02:48 2023
DistUpgraded: 2023-11-02 23:55:54,921 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
openrazer-driver/3.4.0, 6.2.0-36-generic, x86_64: installed
openrazer-driver/3.4.0, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] [1002:1681]
(rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Rembrandt [Radeon 680M] [17aa:50b6]
InstallationDate: Installed on 2022-12-03 (341 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=32b06683-a98d-4585-81c7-edb51198f58c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to mantic
[Desktop-packages] [Bug 2017463] Re: chromium 111 and 112 have the wrong architecture in the user agent
working as intended according to google
https://bugs.chromium.org/p/chromium/issues/detail?id=1500114
this can be closed I guess
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
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/2017463
Title:
chromium 111 and 112 have the wrong architecture in the user agent
Status in chromium-browser package in Ubuntu:
Invalid
Status in chromium-browser source package in Bionic:
Won't Fix
Bug description:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent is expected to contain the string aarch64
however it contains the string x86_64. I am not aware if i386 and
armhf builds are also affected by this or not. This was not an issue
in chromium 110 builds, they had the correct user agent. I am assuming
this is likely an issue with chromium source and not packaging in
particular.
On the other hand, using x86_64 fixes a bug that youtube has on
aarch64 user agent, where it thinks it's a Hisense TV and limits max
resolution to 480p since chromium 110+. playback debug info from
youtube to show that:
```
{
"ns": "yt",
"el": "detailpage",
"cpn": "HFfQQ5-Ud1Xq31GM",
"ver": 2,
"cmt": "0",
"fmt": "247",
"fs": "0",
"rt": "3.724",
"euri": "",
"lact": 3,
"cl": "525275539",
"mos": 0,
"state": "49",
"volume": 100,
"cbrand": "hisense",
"cbr": "Chrome",
"cbrver": "110.0.0.0",
"c": "WEB",
"cver": "2.20230421.01.00",
"cplayer": "UNIPLAYER",
"cmodel": "65a67gevs",
"cos": "X11",
"cplatform": "TV",
"hl": "en_US",
"cr": "US",
"len": "41920.021",
"fexp":
"23776346,23983296,23986022,24004644,24007246,24080738,24135310,24169501,24219381,24255163,24406084,24415864,24416291,24433679,24437577,24439361,24449113,24462372,24468691,24499792,24516157,24532854,24539776,24550457,24556606,39323074",
"feature": "g-high-rec",
"afmt": "251",
"muted": "0",
"docid": "HA7emw-FIjs",
"ei": "welFZNqxGPik0_wPjtWe6A4",
"plid": "AAX6C8oUWaU74VL5",
"referrer": "https://www.youtube.com/;,
"sdetail": "p:/",
"sourceid": "y",
"of": "xjLV454MDgULLBhO4MUTig",
"vm":
"CAQQARgBOjJBTE03ZXZMUmtPVHNLMHhveDl3MHZNWDhrcW9jY0tuYVVCMnB5LUxwdzNfNW9pSUEtd2JTQVBta0tESV85bzU2Nlg2VmdHV2VRY09NOWxsZ284RUdLelRtTVdVZGxmZXJLanZOOGlWX1g0eGFiSUJOMUlGc0JjM1RwMzJGeHpGdElTdmhaVmNoAQ",
"vct": "0.000",
"vd": "41920.021",
"vpl": "",
"vbu": "0.000-7.000",
"vpa": "0",
"vsk": "0",
"ven": "0",
"vpr": "1",
"vrs": "1",
"vns": "2",
"vec": "null",
"vemsg": "",
"vvol": "1",
"vdom": "1",
"vsrc": "1",
"vw": "693",
"vh": "390",
"lct": "0.000",
"lsk": false,
"lmf": false,
"lbw": "152435.812",
"lhd": "1.635",
"lst": "0.000",
"laa":
"itag_251_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_0_range_78167-212166_time_0.0-8.2_off_0_len_134000",
"lva":
"itag_247_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_0_range_130036-287966_time_0.0-7.0_off_0_len_157931_end_1",
"lar":
"itag_251_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_1_range_241354-432255_time_10.0-19.9_off_0_len_190902",
"lvr":
"itag_247_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_2_range_412688-502401_time_14.0-18.3_off_0_len_89714",
"laq": "220089",
"lvq": "214435",
"lab": "0.000-8.461",
"lvb": "0.000-7.000",
"ismb": 1329,
"leader": 1,
"relative_loudness": "-2.590",
"optimal_format": "720p",
"user_qual": 720,
"release_version": "youtube.player.web_20230418_00_RC00",
"debug_videoId": "HA7emw-FIjs",
"0sz": "false",
"op": "",
"yof": "false",
"dis": "",
"gpu":
"ANGLE_(NVIDIA_Corporation,_NVIDIA_Tegra_X1_(nvgpu)/integrated,_OpenGL_4.5.0)",
"debug_playbackQuality": "hd720",
"debug_date": "Sun Apr 23 2023 22:30:34 GMT-0400 (Eastern Daylight Time)"
}
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017463/+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 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
bug still present in jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: Fix Released Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken
I can confirm same for released fedora 39. env vars helped to continue normal typing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2040450 Title: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using keyboard layout Latvian (apostrophe), when writing accented characters like "š", second character is outputed accented, too. When writing, for example, 'so, šō is outputted (should be šo) When testing keyboard during Ubuntu 23.10 installation and choosing Latvian (apostrophe) layout, the behaviour was correct. affects ubuntu/mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043043] [NEW] closed laptop not shutting down
Public bug reported: Maybe this also a feature request, but the current behavior is definitely not useful: Current behavior: * use a laptop (with lid switch) * click Power Off in the Power Off/Log Out menu. * the 60 second counter starts * close the lid immediately * wait a few minutes * open the list * be greeted with the shutting down countdown (!) Expected behavior: * after clicking shutdown, the laptop either shuts down after 60 seconds or I cancel. A shutdown should not be interruptible by anything short of a dead battery. Maybe shutdown instantly when closing the lid (or do that in general? It's not like you get a "These apps would like to prevent the shutdown" dialog.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 19:36:52 2023 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to jammy on 2022-08-16 (449 days ago) ** Affects: gnome-power-manager (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-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/2043043 Title: closed laptop not shutting down Status in gnome-power-manager package in Ubuntu: New Bug description: Maybe this also a feature request, but the current behavior is definitely not useful: Current behavior: * use a laptop (with lid switch) * click Power Off in the Power Off/Log Out menu. * the 60 second counter starts * close the lid immediately * wait a few minutes * open the list * be greeted with the shutting down countdown (!) Expected behavior: * after clicking shutdown, the laptop either shuts down after 60 seconds or I cancel. A shutdown should not be interruptible by anything short of a dead battery. Maybe shutdown instantly when closing the lid (or do that in general? It's not like you get a "These apps would like to prevent the shutdown" dialog.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 19:36:52 2023 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to jammy on 2022-08-16 (449 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/2043043/+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 2042367] Re: eglinfo device platform eglInitialize failed
I have upgraded from 22.04 to 23.10 and this issue is fixed: Device platform: Device #0: EGL device extensions string: EGL_EXT_device_drm, EGL_EXT_device_drm_render_node Platform Device platform: EGL API version: 1.5 EGL vendor string: Mesa Project EGL version string: 1.5 EGL client APIs: OpenGL OpenGL_ES -- 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/2042367 Title: eglinfo device platform eglInitialize failed Status in mesa package in Ubuntu: New Bug description: On an Intel NUC13RNGi9 system with 13900K processor with integrated Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the Device platform: $ eglinfo ... Device platform: eglinfo: eglInitialize failed The other platforms (X11, Wayland, GBM) initialize. The reason I am reporting is I'm trying to fix an issue in my system where: EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY) is returning EGL_NO_DISPLAY on my system, and I think it's due to the Device platform failing to initialize. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 09:42:40 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3033] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC13RNGi9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-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: 02/04/2023 dmi.bios.release: 5.27 dmi.bios.vendor: Intel Corp. dmi.bios.version: SBRPL579.0056.2023.0204.0233 dmi.board.name: NUC13SBBi9 dmi.board.vendor: Intel Corporation dmi.board.version: M58736-304 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 44.0 dmi.modalias: dmi:bvnIntelCorp.:bvrSBRPL579.0056.2023.0204.0233:bd02/04/2023:br5.27:efr44.0:svnIntel(R)ClientSystems:pnNUC13RNGi9:pvrM89920-304:rvnIntelCorporation:rnNUC13SBBi9:rvrM58736-304:cvnIntelCorporation:ct35:cvr2.0:skuRNUC13RNGi9: dmi.product.family: RN dmi.product.name: NUC13RNGi9 dmi.product.sku: RNUC13RNGi9 dmi.product.version: M89920-304 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2042367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
If I lock the system while it is frozen (by closing the laptop's lid), the lock screen will be usable, but once I log back in, the system will still be frozen (until I kill the foreground process). However, the cursor will be a normal cursor instead of the "dragging" cursor. Also, something I discovered: if I use two-fingers at once (multitouch), I can interact with the focused window. However, it is very limited and glitchy. As with before, the only way to return the system to a usable state is to kill the foreground process. All other events (including Alt-F2) except for TTY switching (Ctrl-Alt-F3) are still completely ignored by GNOME, rendering the system frozen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: New Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040037] Re: Xorg crash
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
I try it again, this error has nothing to do with bug #1861609. In 2020
I was running Xubuntu 20.04 and Virtualbox 6.1. This error only occurs
in Xubuntu 23.10 and it does not occur in the development edition of
Xubuntu 24.04.
I will add journalctl -b as attachment and indeed it is related to
vboxguest.
nov 08 13:15:51 VM-Xubuntu-2310 kernel: vboxguest: loading out-of-tree module
taints kernel.
nov 08 13:15:51 VM-Xubuntu-2310 kernel: vboxguest: module verification failed:
signature and/or required key missing - tainting kernel?field.comment=
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2040037/+attachment/5717296/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2040037
Title:
Xorg crash
Status in xorg package in Ubuntu:
New
Bug description:
The first login of my Xubuntu 23.10 VBox VM fails. The second login seems OK,
but all programs I start at login are started twice, like e.g conky. It results
in 100% cpu load on one core.
The system displays an error message for ~2 seconds and it says something
like: "VBoxclient can't connect to X server".
The error also occurs on a fresh install.
Some additional info:
- The login loop also happens on Ubuntu 23.10 VM when started with Xorg, but
here it keeps looping.
- A comparable error occurs on Ubuntu Unity 23.10 VM, on the first screen no
login box will be presented. On the second boot the login screen is presented
and the login seems normal.
Note that the same Vbox release 7.0.12 has no issues with flavors of
22.04 LTS nor with 20.04 LTS.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Oct 20 20:55:33 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2023-05-10 (163 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230510)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=68afebf4-295a-4f3d-b521-36f13d8e060d ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2040037/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Hello, tried the workarounds and the proposed packages The issue persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 23.10 Release: 23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 19:47:42 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043015] Re: Update gnome-shell to 45.1
** Also affects: gnome-shell (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Mantic) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Mantic) Assignee: (unassigned) => Jeremy Bícha (jbicha) ** Changed in: gnome-shell (Ubuntu Mantic) Status: New => 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/2043015 Title: Update gnome-shell to 45.1 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Mantic: In Progress Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043027] [NEW] Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Public bug reported:
Tablet seems to work until I open Krita (as I could read on Internet, it
may be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when it
comes to click action it doesn't work and any further action with mouse
is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff between
built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff between
built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if
00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd06/15/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic possible-manual-nvidia-install ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in xorg package in Ubuntu:
New
[Desktop-packages] [Bug 2043025] [NEW] Top Bar app icons cause a part of screen to be unclickable
Public bug reported:
I faced the issue on 2 different application installations. On Anydesk
and Xlite sip phone client. When the apps are installed and they produce
the small top-bar icon, then a small section of the screen right below
that icon is becoming like an active area of that icon and if you click
on that area you get like a right click menu of the above app. This
makes the browwer like firefox windows for example that are open under
that to become unclickable. When you quit the app it still remains as a
dead zone not being able to click on it, but also not printing the ui of
that app because you closed it.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:27:41 2023
DistUpgraded: 2023-11-03 18:35:10,946 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated Graphics
Controller [106b:]
Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M
XT] [1002:6740] (prog-if 00 [VGA controller])
Subsystem: Apple Inc. Whistler [Radeon HD 6730M/6770M/7690M XT] [106b:6740]
InstallationDate: Installed on 2023-10-23 (16 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=d34e53b2-3855-4542-9f57-a6b4713bda61 ro quiet splash pcie_aspm=force
acpi_backlight=native vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (5 days ago)
dmi.bios.date: 06/14/2019
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 87.0.0.0.0
dmi.board.name: Mac-942B59F58194171B
dmi.board.vendor: Apple Inc.
dmi.board.version: iMac12,2
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-942B59F58194171B
dmi.modalias:
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B:sku:
dmi.product.family: iMac
dmi.product.name: iMac12,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug corruption mantic ubuntu
** Attachment added: "video showing blocked area"
https://bugs.launchpad.net/bugs/2043025/+attachment/5717210/+files/Screencast%20from%202023-11-08%2017-42-01.webm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2043025
Title:
Top Bar app icons cause a part of screen to be unclickable
Status in xorg package in Ubuntu:
New
Bug description:
I faced the issue on 2 different application installations. On Anydesk
and Xlite sip phone client. When the apps are installed and they
produce the small top-bar icon, then a small section of the screen
right below that icon is becoming like an active area of that icon and
if you click on that area you get like a right click menu of the above
app. This makes the browwer like firefox windows for example that are
open under that to become unclickable. When you quit the app it still
remains as a dead zone not being able to click on it, but also not
printing the ui of that app because you closed it.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:27:41 2023
DistUpgraded: 2023-11-03
[Desktop-packages] [Bug 2043024] [NEW] When resizing Google Chrome, my syslog are full of error
Public bug reported: Here some example of such logs: ``` 2023-11-08T17:34:28.189783+02:00 me-Latitude-5511 gnome-shell[36475]: Can't update stage views actor [:0x5583e4887fc0] is on because it needs an allocation. 2023-11-08T17:34:28.190086+02:00 me-Latitude-5511 gnome-shell[36475]: Can't update stage views actor [:0x5583e51cb660] is on because it needs an allocation. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 17:28:54 2023 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages -- 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/2043024 Title: When resizing Google Chrome, my syslog are full of error Status in gnome-shell package in Ubuntu: New Bug description: Here some example of such logs: ``` 2023-11-08T17:34:28.189783+02:00 me-Latitude-5511 gnome-shell[36475]: Can't update stage views actor [:0x5583e4887fc0] is on because it needs an allocation. 2023-11-08T17:34:28.190086+02:00 me-Latitude-5511 gnome-shell[36475]: Can't update stage views actor [:0x5583e51cb660] is on because it needs an allocation. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 17:28:54 2023 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 RelatedPackageVersions: mutter-common 45.0-3ubuntu3 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/2043024/+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 1978757] Re: Cheese can't playback the preview on Intel IPU6 camera platform
After a bit of a fight, I've managed to get the MIPI camera working on my Lenovo ThinkPad X1 Carbon Gen 10. Here's what I've got: - I'm using Ubuntu 22.04.3 LTS. - I'm using Kernel 6.2.0-34-generic (with 6.2.0-35-generic for example it doesn't work for me) With the above, I followed these steps: https://wiki.ubuntu.com/Lenovo And I have added these configurations (replacing what is there, if any): - In the file /etc/modprobe.d/v4l2loopback.conf: options v4l2loopback card_label="Intel MIPI Camera" exclusive_caps=1 video_nr=0 - In the /etc/modprobe.d/v4l2-relayd.conf file: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" - In the /etc/default/v4l2-relayd file: # GStreamer source element name: VIDEOSRC="icamerasrc" #SPLASHSRC="filesrc location=/.../splash.png ! pngdec ! imagefreeze num-buffers=4 ! videoscale ! videoconvert" # Output format, width, height, and frame rate: FORMAT=NV12 WIDTH=1280 HEIGHT=720 FRAMERATE=30/1 # Virtual video device name: CARD_LABEL="Intel MIPI Camera" # Extra options to pass to v4l2-relayd: #EXTRA_OPTS=-d With this, after rebooting the system, the camera usually works in both chrome and firefox (meet, zoom, webcam test, etc...). - In Cheese, I can also get it to work by launching it this way: sudo cheese -d "Intel MIPI Camera". - Sometimes when a black screen appears, just restart the v4l2-relayd service: sudo systemctl restart v4l2-relayd.service I hope this helps someone -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Cheese can't playback the preview on Intel IPU6 camera platform Status in OEM Priority Project: Confirmed Status in cheese package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in v4l2loopback package in Ubuntu: Confirmed Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-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 plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 2016217] Re: gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer() from GjsAutoPointer()
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Jeremy Bícha (jbicha)
--
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/2016217
Title:
gnome-shell crashed with SIGSEGV in clutter_actor_remove_effect() from
st_scroll_view_dispose() from g_object_unref() from GjsAutoPointer()
from GjsAutoPointer()
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Won't Fix
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
44.0-2ubuntu3, the problem page at
https://errors.ubuntu.com/problem/677a794c2788cd0244c8fc6d7d34780a85127bc9
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
#0 0x7f3aa429dd82 in clutter_actor_remove_effect
(self=self@entry=0x55d60fa59e90, effect=0x55d6101c48a0) at
../clutter/clutter/clutter-actor.c:14830
__inst = 0x55d6101c48a0
__t = 94377826055744
__r =
_g_boolean_var_274 =
__func__ = "clutter_actor_remove_effect"
#1 0x7f3aa3f9d27f in st_scroll_view_dispose (object=0x55d60fa59e90) at
../src/st/st-scroll-view.c:246
priv = 0x55d60fa59a00
#2 0x7f3aa4aeada0 in g_object_unref (_object=0x55d60fa59e90) at
../../../gobject/gobject.c:3891
_pp =
gaig_temp =
gaig_temp =
weak_locations =
nqueue = 0x55d60fa6da60
_ptr =
object = 0x55d60fa59e90
old_ref =
retry_atomic_decrement1 =
__func__ = "g_object_unref"
#3 0x7f3aa43b4b2c in GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::reset (ptr=0x0, this=) at ../gjs/jsapi-util.h:229
old_ptr =
#4 GjsAutoPointer<_GObject, void, _object_unref,
_object_ref>::~GjsAutoPointer (this=, this=) at
../gjs/jsapi-util.h:172
No locals.
#5 GjsSmartPointer<_GObject>::~GjsSmartPointer (this=,
this=) at ../gjs/jsapi-util.h:349
No locals.
#6 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1524
No locals.
#7 ObjectInstance::release_native_object (this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1500
No locals.
#8 0x7f3aa43c9ec0 in ObjectInstance::~ObjectInstance (this=, this=) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1945
was_using_toggle_refs = false
had_toggle_up = false
had_toggle_down =
had_toggle_up =
had_toggle_down =
was_using_toggle_refs =
#9 GIWrapperInstance::finalize_impl (this=0x55d60fa0ce80) at ../gi/wrapperutils.h:1113
No locals.
#10 ObjectInstance::finalize_impl (gcx=, obj=0x35b1abd24820,
this=0x55d60fa0ce80) at
/usr/src/gjs-1.76.0-1/obj-x86_64-linux-gnu/../gi/object.cpp:1912
query = {type = 94377830362416, type_name = 0x7f3aa3fdcda6
"StScrollView", class_size = 664, instance_size = 48}
query =
_g_boolean_var_74 =
#11 GIWrapperBase::finalize
(gcx=, obj=0x35b1abd24820) at ../gi/wrapperutils.h:411
priv = 0x55d60fa0ce80
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2016217/+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 2043015] [NEW] Update gnome-shell to 45.1
Public bug reported: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) ** Affects: gnome-shell (Ubuntu) Importance: High Assignee: Jeremy Bícha (jbicha) Status: Fix Committed ** Tags: mantic upgrade-software-version -- 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/2043015 Title: Update gnome-shell to 45.1 Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- gnome-shell provides the GNOME version number for the Settings app About page, as of Ubuntu 22.10 (in earlier Ubuntu releases, this was provided by gnome-desktop/gnome-desktop3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043015/+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 2043007] Re: package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2043007 Title: package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: Invalid Bug description: Failed to upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 8 14:17:50 2023 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2023-11-07 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2043007/+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 2043007] [NEW] package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: Failed to upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 8 14:17:50 2023 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2023-11-07 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2043007 Title: package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: New Bug description: Failed to upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 8 14:17:50 2023 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2023-11-07 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-gnome 1:6.4.7-0ubuntu0.20.04.6 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2043007/+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 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
> the same error. Which one? If the one in DpkgHistoryLog.txt, it really looks like a store/snapd bug, maybe follow up in the forum. Found this: https://forum.snapcraft.io/t/cannot-performe-any-task-using-snap. -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in Snap Store Server: New Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapstore-server/+bug/2038609/+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 2041219] Re: GUI Freezes Randomly
Will do! The .crash file is empty as well and the error ubuntu error says nothing is on the tracker. -- 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/2041219 Title: GUI Freezes Randomly Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: Hi, So everything would be working normally and then all of a sudden the laptop would freeze and nothing works. There's nothing in /var/crash. This has been run: cd ~/.local/share/gnome-shell/ rm -rf extensions output of journalctl -b-1 > prevboot.txt is attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darian 2556 F pulseaudio /dev/snd/pcmC0D0p: darian 2556 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-21 (66 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: PC Specialist Limited W94_95_97JU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-35-generic N/A linux-backports-modules-6.2.0-35-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.21 Tags: jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2015 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W94_95_97JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: W94_95_97JU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
> the same error. Which one? If the one in DpkgHistoryLog.txt, it really looks like a store/snapd bug, maybe follow up in the forum. Found this: https://forum.snapcraft.io/t/cannot-performe-any-task-using-snap. -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in Snap Store Server: New Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapstore-server/+bug/2038609/+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 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Same here, also ubuntu 23.10, snapd version 2.60.4+23.10.1. Trying the candidate channel produces the same error. I've successfully installed other snaps. -- 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/2038609 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in Snap Store Server: New Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: failed to install ProblemType: Package DistroRelease: Ubuntu 23.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu4 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Oct 5 23:37:38 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapstore-server/+bug/2038609/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
+1 on -proposed mutter. I'm using Ubuntu 23.10 w/ Linux 6.5.0-10-generic kernel, ThinkPad T14 Gen 3 (AMD), it helped resolving the problem. Many thanks! -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu
The attachment "1-23.2.1-1ubuntu4.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Mantic: New Status in mesa source package in Noble: Confirmed Bug description: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2042909] Re: Gnome shell freezing and/or taking a long time to load
Try breaking into the gnome-shell process in gdb and calling 'gjs_dumpstack'. That's assuming it doesn't already reveal where it's hung when you attach. -- 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/2042909 Title: Gnome shell freezing and/or taking a long time to load Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 23.10 Gnome Shell 45.0 I expect gdm and the shell to be responsive but they freeze forcing me to reboot. Sometimes I'm able to use them but it takes some time to load. After taking a look at the journal, I see lots of messages like this: #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was AsyncReadyCallback(). == Stack trace for context 0x564c4deaab90 == #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. The offending signal was g-properties-changed on GDBusProxy 0x564c4fec8670. == Stack trace for context 0x564c4deaab90 == On successful boots this seems to auto resolve, being followed by this message: nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome' nov 07 09:21:56 perseus systemd[1722]: Started xdg-desktop-portal-gnome.service - Portal service (GNOME implementation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042909/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu
This integrates the patch for this bug from upstream. ** Patch added: "1-23.2.1-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038834/+attachment/5717150/+files/1-23.2.1-1ubuntu4.debdiff -- 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/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Mantic: New Status in mesa source package in Noble: Confirmed Bug description: This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2043000] [NEW] Update mutter to 45.1
Public bug reported: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.1/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- ** Affects: mutter (Ubuntu) Importance: High Assignee: Jeremy Bícha (jbicha) Status: In Progress ** Tags: mantic upgrade-software-version -- 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/2043000 Title: Update mutter to 45.1 Status in mutter package in Ubuntu: In Progress Bug description: Impact -- There is a new bugfix release in the stable 45 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/45.1/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043000/+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 2042987] Re: The settings of different Wi-Fi adapters do NOT work separately.
** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2042987 Title: The settings of different Wi-Fi adapters do NOT work separately. Status in gnome-control-center package in Ubuntu: New Bug description: The settings of different Wi-Fi adapters do NOT work separately. The Wi-Fi switch triggers all Wi-Fi adapters, and the Saved Networks lists do NOT be saved separately. Hope this bug can be fixed soon. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-settings 23.10.5 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 08:54:37 2023 InstallationDate: Installed on 2023-07-29 (101 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to mantic on 2023-08-16 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042987/+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 2042909] Re: Gnome shell freezing and/or taking a long time to load
Disabling extensions seems to avoid permanent freezing but it still takes some time for the shell to respond. -- 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/2042909 Title: Gnome shell freezing and/or taking a long time to load Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 23.10 Gnome Shell 45.0 I expect gdm and the shell to be responsive but they freeze forcing me to reboot. Sometimes I'm able to use them but it takes some time to load. After taking a look at the journal, I see lots of messages like this: #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was AsyncReadyCallback(). == Stack trace for context 0x564c4deaab90 == #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. The offending signal was g-properties-changed on GDBusProxy 0x564c4fec8670. == Stack trace for context 0x564c4deaab90 == On successful boots this seems to auto resolve, being followed by this message: nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome' nov 07 09:21:56 perseus systemd[1722]: Started xdg-desktop-portal-gnome.service - Portal service (GNOME implementation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042909/+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
