[Desktop-packages] [Bug 1993557] Re: Nautilus "Files" hangs when trying to type search string
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1993557 Title: Nautilus "Files" hangs when trying to type search string Status in nautilus package in Ubuntu: Expired Bug description: Hi, I recently installed Ubuntu 22.04.1 LTS (dual boot installation on a new Dell XPS15 laptop shipped with Windows 11 Pro). For the last couple of days, when I try typing more than one letter in the files search menu, I get a ' "Files" is not responding ' message and have to force quit. My /var/log/syslog (and a syslog.1) had grown to a large number of GB (so I won't attempt to attach it). I purged them a while ago but syslog has grown again to >23GB. It seems filled by lines all similar to these two: Oct 19 16:58:57 [...] tracker-miner-f[2233]: g_file_equal: assertion 'G_IS_FILE (file1)' failed Oct 19 16:58:57 [...] tracker-miner-f[2233]: g_file_has_prefix: assertion 'G_IS_FILE (file)' failed nautilus: Installed: 1:42.2-0ubuntu1 Candidate: 1:42.2-0ubuntu1 Version table: *** 1:42.2-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Your help resolving this would be much appreciated. Philippe ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 17:20:24 2022 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.window-state' b'initial-size' b'(1198, 1042)' InstallationDate: Installed on 2022-10-11 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993557/+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 1993870] Re: WiFi setting has no visible networks (Intel Wireless-AC 9560)
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1993870 Title: WiFi setting has no visible networks (Intel Wireless-AC 9560) Status in network-manager package in Ubuntu: Expired Bug description: With ubuntu 22.10, I can not see any AP in WiFi setting. It's ok on previous versions. The driver is okay since I can scan with iwlist tool. Below are more details. $ sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.10 Release: 22.10 Codename: kinetic $ ifconfig enx5e80011fa4e9: flags=4163 mtu 1500 inet 192.168.42.116 netmask 255.255.255.0 broadcast 192.168.42.255 inet6 fe80::cd60:eccc:f8d7:21e6 prefixlen 64 scopeid 0x20 ether 5e:80:01:1f:a4:e9 txqueuelen 1000 (Ethernet) RX packets 432320 bytes 621981996 (621.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 186680 bytes 22769110 (22.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 11354 bytes 24889535 (24.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11354 bytes 24889535 (24.8 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp0s20f3: flags=4099 mtu 1500 ether 18:1d:ea:ed:34:16 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 $ sudo iwlist wlp0s20f3 scan wlp0s20f3 Scan completed : Cell 01 - Address: D0:79:80:DA:4F:F3 Channel:1 Frequency:2.412 GHz (Channel 1) Quality=29/70 Signal level=-81 dBm Encryption key:on ESSID:"CMCC-7S6H" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s Mode:Master Extra:tsf=00e793b8a899 Extra: Last beacon: 2164ms ago IE: Unknown: 0009434D43432D37533648 IE: Unknown: 010882848B962430486C IE: Unknown: 030101 IE: Unknown: 23021100 IE: Unknown: 2A0104 IE: Unknown: 32040C121860 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: 0B0539 IE: Unknown: 7F0804000840 IE: Unknown: DD7E0050F204104A0001101044000102103B000103104700105D2DBCBB9D644948047E083B1A419A72102100094669626572686F6D65102300094669626572686F6D651024000631323334353610420004313233341054000800060050F20400011011000B4669626572686F6D6541501008000220081049000600372A000120 IE: Unknown: DD0A001018020C01 IE: WPA Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK IE: Unknown: DD180050F20201018C0003A227A442435E0062322F00 Cell 02 - Address: FC:DD:65:2B:6B:52 $ sudo dmesg | grep iwl [2.816274] iwlwifi :00:14.3: WRT: Overriding region id 0 [2.816285] iwlwifi :00:14.3: WRT: Overriding region id 1 [2.816289] iwlwifi :00:14.3: WRT: Overriding region id 2 [2.816293] iwlwifi :00:14.3: WRT: Overriding region id 3 [2.816297] iwlwifi :00:14.3: WRT: Overriding region id 4 [2.816300] iwlwifi :00:14.3: WRT: Overriding region id 6 [2.816304] iwlwifi :00:14.3: WRT: Overriding region id 8 [2.816307] iwlwifi :00:14.3: WRT: Overriding region id 9 [2.816311] iwlwifi :00:14.3: WRT: Overriding region id 10 [2.816314] iwlwifi :00:14.3: WRT: Overriding region id 11 [2.816318] iwlwifi :00:14.3: WRT: Overriding region id 15 [2.816322] iwlwifi :00:14.3: WRT: Overriding region id 16 [2.816326] iwlwifi :00:14.3: WRT: Overriding region id 18 [2.816330] iwlwifi :00:14.3: WRT: Overriding region id 19 [2.816333]
[Desktop-packages] [Bug 1995810] Re: occasionally fails to open a directory with images
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1995810 Title: occasionally fails to open a directory with images Status in nautilus package in Ubuntu: Expired Bug description: I open a local dir containing about 100 jpg photos and a subdir. Nautilus shows a "loading..." indicator in the lower right corner, but it never shows the contents of the directory. It should show thumbnails of the files in the directory. This happens occasionally. It is very simple to work around - just go to e.g. the parent dir and come back to the offending dir - but it's still mildly problematic and nautilus is used by effectively every gnome user. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58~20.04.1-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 20:07:45 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 551)' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-11-03 (3 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995810/+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 1756484] Re: [radeon] Screen flickers and small moving artifacts
The Grinch’s suit and speaking style. Since the story was first published in 1957, families eagerly have been repeating the Grinch's tale every Christmas season. https://grinchcostume.shop/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1756484 Title: [radeon] Screen flickers and small moving artifacts Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: This is likely a wayland issue. I can't bear the tearing if I don't use wayland. I get screen flickering (approximately every 5 seconds) and some windows seem to bring up some mis-colored moving artifacts that clear when the window is closed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 20:07:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112] InstallationDate: Installed on 2018-03-17 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1756484/+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 1492753] Re: Screen rotation broken in Wily
There is a showoff competition between squishmallow enthusiasts where they are always looking to get an upper hand over other kids by buying some fancy squishmallows. Your kid might also be looking at the mushroom squishmallow collection thinking to grab one for his collection. https://mushroomsquishmallow.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1492753 Title: Screen rotation broken in Wily Status in xserver-xorg-driver-ati: Fix Released Status in xserver-xorg-video-ati package in Ubuntu: Triaged Bug description: Using a Radeon 280x (tahiti). Rotation previously working in Vivid but not in Wily. Arch is on xserver-xorg 1.17.2 and rotation is working so maybe a debian bug. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Sun Sep 6 13:02:16 2015 InstallationDate: Installed on 2015-09-03 (3 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:229a] InstallationDate: Installed on 2015-09-03 (17 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1) MachineType: Gigabyte Technology Co., Ltd. EX58-UD3R Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic root=UUID=433d9dbe-1395-4885-b668-19b707c0cd93 ro radeon.audio=0 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Tags: wily kubuntu single-occurrence has-fix UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/04/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: EX58-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd05/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX58-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX58-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX58-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sun Sep 20 08:29:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1492753/+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 1091058] Re: 1002:95c4 [Satellite Pro P300-16V] GPU locks up and the screen turns white
Pretty nice post. I just stumbled upon your weblog and wanted to say that I have really enjoyed browsing your blog posts. After all I’ll be subscribing to your feed and I hope you write again soon! Learn More:https://vikingaxe.shop/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1091058 Title: 1002:95c4 [Satellite Pro P300-16V] GPU locks up and the screen turns white Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: At random, if I'm using ANY 3D program or game (except, strangely, window managers, including compiz, gala, mutter, etc)... the GPU will lockup, the screen redraws with a bunch of lines at the bottom, and then it begins to turn white. I wish I could give more information but each time it happens the system locks up completely and I have to force it to restart (which is NOT good). This problem was happening on Ubuntu 12.10 and persists into 13.04. --- .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.2, 3.12.0-7-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-1-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2012-10-24 (447 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA Satellite Pro P300 Package: xserver-xorg-video-ati 1:7.2.0+git1311151746.d571d6~gd~s [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-2-generic root=UUID=11f0f4e0-65cd-4d72-b5a0-5fab21660b89 ro quiet splash radeon.dpm=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 Tags: third-party-packages trusty ubuntu regression reproducible compiz-0.9 Uname: Linux 3.13.0-2-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo dmi.bios.date: 04/14/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.70 dmi.board.name: Satellite Pro P300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.70:bd04/14/2008:svnTOSHIBA:pnSatelliteProP300:pvrPSPC5E-01400CEN:rvnTOSHIBA:rnSatelliteProP300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A: dmi.product.name: Satellite Pro P300 dmi.product.version: PSPC5E-01400CEN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1~git1311211600.2d5f21~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1~git1311211600.2d5f21~gd~s version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0+git1311151746.d571d6~gd~s version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1311070905.480f09~gd~s xserver.bootTime: Mon Jan 13 02:01:34 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1091058/+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 990632] Re: Add IDs for new AMD Evergreen/Fusion SKUs
These calm and quite cute little toys are the perfect alternatives as they are the fluffiest, the cutest, and simply do not make any noises. cow squishmallows:https://cowsquishmallow.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/990632 Title: Add IDs for new AMD Evergreen/Fusion SKUs Status in libdrm package in Ubuntu: Fix Released Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: This graphics driver has no compiz or Unity 3d support. I understand that this is a new laptop, but please, do include support for this graphics card soon.This graphics driver has no compiz or Unity 3d support. I understand that this is a new laptop, but please, do include support for this graphics card soon, that is, if you can cherry-pick a patch to make 3d work on this thing. If not now, please try for the next Ubuntu release. Running Precise Pangolin with the latest patches. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-radeon 1:6.14.99~git20111219.aacbd629-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CasperVersion: 1.315 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Sat Apr 28 17:09:12 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI Device [1002:9649] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3566] LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3568 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.39 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd02/22/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn3568:rvr21.39:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g7 Notebook PC dmi.product.version: 06901320461620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/990632/+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 1199409] Re: Xrandr twitches when using DVI-VGA adapter via triple AMD card setup
In this case, you need to pack a pair of frog squishmallow toys for your kids so that they can play with them in the car and the hotel room as well. The compact size of the this squishmallow makes things easier as the squishmallows frog can fit even in a small backpack which allows you to pack other stuff in the backpack too. Squishmallow frogs:https://frogsquishmallow.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1199409 Title: Xrandr twitches when using DVI-VGA adapter via triple AMD card setup Status in xserver-xorg-video-ati package in Ubuntu: Triaged Bug description: What I expected to happen is a normal picture on all four of my monitors. What happened instead xrandr will twitch when using a DVI-VGA adapter via ubuntu 12.04-14.04: lspci | grep VGA 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV610 [Radeon HD 2400 PRO] 06:06.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV250/M9 GL [Mobility FireGL 9000/Radeon 9000] (rev 02) fglrx-* in Precise did not recognize all my cards so I was unable to test it. The IGP is connected via DVI to a 24" monitor and via VGA to a 17" monitor, all good so far. Then I have three monitors left, two 15" VGA and one 17" vga, so to use all monitors, I have to use one DVI-VGA adapter. No matter in what order/combination I connect the monitors to the video cards, the monitor that is connected via the adapter always flickers along with the other monitor on that same card (does not matter which card). It seems like the two monitors have two sperate framebuffers, but by default they both show the framebuffer for the monitor with adapter, but when I move the mouse they switch rapidly from that framebuffer to the other and back. Here are three video's showing the problem: http://www.youtube.com/watch?v=tQiJADHGuZg (Top-Right monitor connected via adapter, in the same card as Bottom-Right) http://www.youtube.com/watch?v=lk9muK8f06c (Top-Left monitor connected via adapter, in the same card as Bottom-Right) http://www.youtube.com/watch?v=6Ses1jUcu2k (Top-Left monitor connected via adapter, in the same card as Top-Right) I think it's a xrandr problem because using the same setup with zaphodhead mode and xinerama, it works but its EXTREMELY slow. I have already tried another DVI-VGA adapter, but with the same results. Another strange thing is that xrandr seems to think that two monitors are clones, but one of which is not connected. xrandr --verbose log: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1199409/+attachment/3944844/+files/xrandr%20--verbose I have cut out the various supported modes, the full xrandr --verbose output is attached. As you see, VGA-2 and DVI-1 apparently are clones, but in this case only VGA-2 is connected, I don't know if that is normal. I now have connected two monitors (both 15") to VGA-2 and DVI-1, and the xrandr output has not changed, it still shows VGA-2 and DVI-1 as cloned, but the two displays still twitch as in the video's... --- .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.336ubuntu1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: No LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140105) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: xorg 1:7.7+1ubuntu7 PackageArchitecture: amd64 ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Tags: third-party-packages trusty ubuntu reproducible compiz-0.9 Uname: Linux 3.12.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 880GMH/USB3. dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn880GMH/USB3.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M.
[Desktop-packages] [Bug 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
The attachment "nemo_5.4.3-2ubuntu0.1.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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
I have made a Pull Request for upstream. https://github.com/intel/media-driver/pull/1588 Once this is merged and released, we should pick this up in our snap build. By setting GFX_FEATURE_FILE and GFX_FEATURE_FILE_NEXT we can then prevent access to /etc/ dir. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Confirmed -- 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/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: Confirmed Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Applied the patches, not getting any nasty messages in /var/log/syslog ** Patch added: "nemo_5.4.3-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1998060/+attachment/5639800/+files/nemo_5.4.3-2ubuntu0.1.debdiff ** Changed in: nemo (Ubuntu Kinetic) Status: New => In Progress -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2002182] [NEW] wireplumber initiates not implemented dbus message on bluez
Public bug reported: auth.log:649:Jan 6 21:32:17 ice-home dbus-daemon[802]: message repeated 20 times: [ [system] Rejected send message, 0 matched rules; type="error", sender=":1.33" (uid=1000 pid=1182 comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.5" (uid=0 pid=796 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")] root@ice-home:/var/log# systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Fri 2023-01-06 18:31:17 EET; 4h 12min ago Docs: man:bluetoothd(8) Main PID: 796 (bluetoothd) Status: "Running" Tasks: 1 (limit: 27957) Memory: 2.2M CPU: 66ms CGroup: /system.slice/bluetooth.service └─796 /usr/lib/bluetooth/bluetoothd Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_51 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_71 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_duplex Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_pro ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: wireplumber 0.4.12-1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 22:55:22 2023 SourcePackage: wireplumber UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wireplumber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wireplumber in Ubuntu. https://bugs.launchpad.net/bugs/2002182 Title: wireplumber initiates not implemented dbus message on bluez Status in wireplumber package in Ubuntu: New Bug description: auth.log:649:Jan 6 21:32:17 ice-home dbus-daemon[802]: message repeated 20 times: [ [system] Rejected send message, 0 matched rules; type="error", sender=":1.33" (uid=1000 pid=1182 comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.5" (uid=0 pid=796 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")] root@ice-home:/var/log# systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Fri 2023-01-06 18:31:17 EET; 4h 12min ago Docs: man:bluetoothd(8) Main PID: 796 (bluetoothd) Status: "Running" Tasks: 1 (limit: 27957) Memory: 2.2M CPU: 66ms CGroup: /system.slice/bluetooth.service └─796 /usr/lib/bluetooth/bluetoothd Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_51 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/opus_05_71 Jan 06 21:32:18 ice-home bluetoothd[796]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jan 06 21:32:18 ice-home bluetoothd[796]:
[Desktop-packages] [Bug 1998893] Re: NV reverse prime HDMI has no output
I ran update-maintainer on the mesa source and uploaded again. Give the removal of PCI IDs, and the vague statement in the "Where things could go wrong" section of the bug description, I'd like to see a more clear statement saying that these IDs are already not available in the jammy kernel, and as such there is an even lesser risk of regression due to that. -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Re: NV reverse prime HDMI has no output
Hello Kai-Chuan, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-jammy ** Tags added: verification-needed verification-needed-jammy -- 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/1998893 Title: NV reverse prime HDMI has no output Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The X failed to load glamoregl module on Dell's new platforms, the module is needed by NV dGPU. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: vendor="X.Org Foundation" 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 1.21.1.3, module version = 1.0.1 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org ANSI C Emulation, version 0.4 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does not support the 0xa78b PCI ID. 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to try glamor on llvmpipe 十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor initialization failed [Fix] The upstream PR added missing ID for the platforms. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/ After creating the test build to include the PR above, ODM verified passed on those platform. [Test case] Install fixed package on the systems, check that display works. [Where things could go wrong] Although one commit drops a couple of pci-id's, they were synced from the kernel and such id's should not be in the wild. Other than that these just add id's and modify some vendor branding. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end
I accepted 22.0.5-0ubuntu0.3 which does NOT fix this bug, so I'm reopening it. ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Confirmed -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Confirmed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end
Hello errors.ubuntu.com, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-jammy ** Tags added: verification-needed-jammy -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Confirmed Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+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 1846398] Re: [modeset] xrandr transformations cause significant visible tearing in Xorg sessions
The proposed fix has been merged to the xserver master branch. The author of the fix also has a patch set against a recent xserver stable release here: https://github.com/kerneltoast/xserver/tree/new-tearfree-21.1.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846398 Title: [modeset] xrandr transformations cause significant visible tearing in Xorg sessions Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: On my laptop, fractional scaling seems fine, including watching a YouTube video. It has a quad HD display. Enabling fractional scaling on my desktop which is attached to a single 4k display, fractional scaling isn't usable. The video appears to be constantly refreshing and not using the same acceleration as if I just run at 100% or 200%. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:23:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (435 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+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 1998950] Re: GPU hang on Alder Lake laptop
Since there appears to be upstream patches in kernel 6.0 and Mesa 22.3.1 which fix this, perhaps it would be possible to backport those to the versions in Ubuntu 22.10? If not, would it at least be possible to upload such packages to Lunar so that there's an option which doesn't involve reinstalling the machine to go back to 22.04? Right now my machine is freezing multiple times per day and it would be really valuable to get those backports applied. I'm pretty sure this affects all Alder Lake-P GPUs on Kinetic, since the upstream bug report mentions multiple different hardware variants. -- 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/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.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-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/linux/+bug/1998950/+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 1946215] Re: transmission: Fail to build against OpenSSL 3.0
I can confirm that there is a memory leak at the indicated point in the code, though I'm surprised it is noticeable as it only happens when tr_rc4_new() fails. Would you mind opening a bug report in Debian for this? (Since this was upstreamed and Ubuntu is now in sync with Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1946215 Title: transmission: Fail to build against OpenSSL 3.0 Status in transmission package in Ubuntu: Fix Released Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099409/+files/buildlog_ubuntu- impish-amd64.transmission_3.00-1ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 This has been fixed upstream, currently on master: https://github.com/transmission/transmission/pull/1788 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1946215/+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 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
Intel provided guidance on how to address this. I will make a merge request. ** Changed in: chromium-browser (Ubuntu) Assignee: Nathan Teodosio (nteodosio) => Bram Stolk (b-stolk) -- 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: Confirmed Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
ubuntu-bug is a command from Apport. This bug is fixed in Ubuntu >= 22.10 (kinetic) but not in 22.04 (jammy) – yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: New Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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 1425000] Re: Cannot set right monitor as primary in dual monitor configuration
BTW, I found few app can show on the correct monitor. e.g: google-chrome, firefox, when start these applications in Terminal on monitor B, they can show on the monitor B. but most other app can not. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1425000 Title: Cannot set right monitor as primary in dual monitor configuration Status in unity-control-center package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Won't Fix Status in xfwm4 package in Ubuntu: Invalid Bug description: Unity always considers the left monitor as the default/primary one when in a dual-monitor configuration. By this I mean that: - Desktop icons appear only on the left monitor - An opened app (eg libreoffice writer) is opened on the left screen, even if I launch it via the launcher on the right monitor The current configuration can be seen at http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png The .config/monitors.xml file is shown below. Notice that the HDMI display (green in the photo) is set asyes. Nevertheless, this seems to be ignored - the behaviour is the one mentioned above (desktop icons on the left and writer opening on the left) . no GSM 0x4b7a 0xb13b 1440 900 60 0 0 normal no no no GSM 0x5a26 0x0008976f 1920 1080 60 1440 0 normal no no yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+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 2002153] Re: Guitarix not starting, fontconfig errors
Cannot reproduce on Lunar. I'm suspecting this is an issue with fontconfig as there were some changes between Jammy and Lunar. ** Also affects: guitarix (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Also affects: guitarix (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: guitarix (Ubuntu Lunar) Status: Incomplete => Invalid ** Also affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Changed in: fontconfig (Ubuntu Lunar) Status: New => Invalid ** Changed in: guitarix (Ubuntu Jammy) Status: New => Invalid ** No longer affects: guitarix (Ubuntu) ** No longer affects: guitarix (Ubuntu Jammy) ** No longer affects: guitarix (Ubuntu Lunar) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2002153 Title: Guitarix not starting, fontconfig errors Status in fontconfig package in Ubuntu: Invalid Status in fontconfig source package in Jammy: New Status in fontconfig source package in Lunar: Invalid Bug description: There is a problem with starting guitarix cause fontconfig errors for ex: Fontconfig error: "/etc/fonts/conf.d/66-lohit-tamil-classical.conf", line 22: out of memory Fontconfig warning: "/etc/fonts/conf.d/66-lohit-tamil-classical.conf", line 23: No nor elements in --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-05 (214 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: guitarix 0.42.1+dfsg1-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Tags: third-party-packages jammy Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2002153/+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 1425000] Re: Cannot set right monitor as primary in dual monitor configuration
Yes, I encountered same issue on Ubuntu 20.04 with Unity desktop. e.g: a laptop (monitor A) connected with an external monitor B over HDMI. Monitor A is on the left of monitor B. In the "System Settings" >> Displays, I selected "Launcher Placement" as "All displays" In the Terminal on monitor B, when start a new process, e.g: libreoffice or gnome-calculator, the created app is shown on monitor A. Whether it can be changed like this: if a child process is created by process on monitor X, then show the child process also on monitor X. in some situation, if the process is partly on monitor A, partly on monitor B, etc, show the child process on the monitor[0]. (assume that the monitors are an array in the system ). It's like the child process inherited the monitor setting of parent process. At last, whether this is an issue on Unity Desktop or X Window System, or some else ? Please advice! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1425000 Title: Cannot set right monitor as primary in dual monitor configuration Status in unity-control-center package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Won't Fix Status in xfwm4 package in Ubuntu: Invalid Bug description: Unity always considers the left monitor as the default/primary one when in a dual-monitor configuration. By this I mean that: - Desktop icons appear only on the left monitor - An opened app (eg libreoffice writer) is opened on the left screen, even if I launch it via the launcher on the right monitor The current configuration can be seen at http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png The .config/monitors.xml file is shown below. Notice that the HDMI display (green in the photo) is set asyes. Nevertheless, this seems to be ignored - the behaviour is the one mentioned above (desktop icons on the left and writer opening on the left) . no GSM 0x4b7a 0xb13b 1440 900 60 0 0 normal no no no GSM 0x5a26 0x0008976f 1920 1080 60 1440 0 normal no no yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+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 1946215] Re: transmission: Fail to build against OpenSSL 3.0
It seems that the patch that fixed this might have been faulty and introduced a memory leak. See https://github.com/NixOS/nixpkgs/issues/207047#issuecomment-1360393405 for some details. Should I open a new issue for this? ** Bug watch added: github.com/NixOS/nixpkgs/issues #207047 https://github.com/NixOS/nixpkgs/issues/207047 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1946215 Title: transmission: Fail to build against OpenSSL 3.0 Status in transmission package in Ubuntu: Fix Released Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099409/+files/buildlog_ubuntu- impish-amd64.transmission_3.00-1ubuntu2.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 This has been fixed upstream, currently on master: https://github.com/transmission/transmission/pull/1788 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1946215/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
@guiverc i just tried latest iso lubuntu-22.04.1-desktop-amd64.iso and reported Bug 2002120 that now is a duplicate of this. So its not fixed. My bug is about Apport. Is this about ubuntu-bug? So then mine is not duplicate, or why its the same package? Ubuntu-bug doesnt work for me at all because of Bug #2002119 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: New Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
** Tags added: jammy ** Also affects: apport (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: xdg-utils (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Status in apport source package in Jammy: New Status in xdg-utils source package in Jammy: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
Happened again today. Again, was anything pushed last night that might have triggered this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: New Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially galling that it removes the real version at the same time. I have lost data (passwords and history) because of this bug, because one of the many faults of the snap version is that it ignores the user's real ~/.mozilla profile and creates a shadow profile instead inside of the snap system. Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated user preferences, and it causes the loss of data. I am unclear on what package is causing the behavior so for now marking it against Firefox, but it could be against some other piece of infrastructure related to snap: affects ubuntu/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+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 2002146] [NEW] Second Display not detected after software update
Public bug reported: Update required restart, before restart the display was working as expected. After restart the system does not even detect the display, even after unplugging and plugging back the HDMI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 19:39:38 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-56-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-57-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] [1043:109f] Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2022-06-12 (208 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=0efa9695-6ef2-4b6e-b3c8-b0702c8a9b8a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 16.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.316:bd01/28/2021:br5.14:efr16.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2002146 Title: Second Display not detected after software update Status in xorg package in Ubuntu: New Bug description: Update required restart, before restart the display was working as expected. After restart the system does not even detect the display, even after unplugging and plugging back the HDMI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 19:39:38 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-56-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-57-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] [1043:109f] Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2022-06-12 (208 days ago) InstallationMedia: Ubuntu 22.04 LTS
[Desktop-packages] [Bug 1999487] Re: Webcam does not work with v107.0.5304.121-hwacc
With the flag changes[1] that went in the hwacc/edge my webcam works again. [1]: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=4c051e7082153f898e46e27d56466ae497cbfdfe -- 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/1999487 Title: Webcam does not work with v107.0.5304.121-hwacc Status in chromium-browser package in Ubuntu: Confirmed Bug description: With the latest version of Chromium in the stable channel (108.0.5359.94), I can access the webcam and the microphone in Google Meet and Jitsi (using a framatalk.org instance). However, with version 107.0.5304.121-hwacc (from latest/candidate/hwacc branch), the same test does not work. The only difference between the two in `snap connections chromium` is content chromium:va-driver-non-free - - Test: 1. Install Chromium from the given channel 2. Go to https://framatalk.org/ and click on "Create a room" 3. Accept the permissions to access Microphone and Camera Expected result: Image from camera is displayed on screen Actual result: The webcam is turned on (the LED turns on), but no image is captured, and after a few seconds, an error message is displayed ("We are unable to access your camera"). In the settings, I can see the camera name ("UVC Camera (046d:0802)"). Attached are two logs: - One retrieved by launching Chromium with `chromium --enable-logging=stderr`, accessing framatalk.org and clicking on "Create a room". - One retrieved by launching Chromium with `chromium --enable-logging=stderr` and accessing a Google Meet event. Configuration information = - Desktop with AMD GPU RX580 - Ubuntu 20.04 (kernel 5.15.0-56-generic) - Webcam: 046d:0802 Logitech, Inc. Webcam C200 - Headset: 046d:0a38 Logitech, Inc. Headset H340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1999487/+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 2000175] Re: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/435222 ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Bram Stolk (b-stolk) -- 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/2000175 Title: [snap] latest/candidate/hwacc channel cause lots of Apparmor noise Status in chromium-browser package in Ubuntu: In Progress Bug description: # Issue description After installing chromium with hwacc (snap refresh chromium --channel latest/candidate/hwacc) I notice a lot of those new messages in dmesg: Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 Those 2 files do not exist in the host's filesystem: $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory # Additional information $ uname -a Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ snap list chromium core20 snapd Name Version RevTrackingPublisher Notes chromium 107.0.5304.121-hwacc 2224 latest/candidate/… canonical✓ - core2020221123 1738 latest/stable canonical✓ base snapd 2.57.617883 latest/stable canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 Ah my apologies, I didn't realise I had already reported this a few months back when updating to jammy here https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750 -- 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/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound
*** This bug is a duplicate of bug 1783689 *** https://bugs.launchpad.net/bugs/1783689 That does sound like it could be an issue for sure. -- 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/2000917 Title: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Every now and then, after boot, I get no sounds at all coming from the speakers. Everything seems normal - the control center reports the output as active, and if I play anything with sound I can see the VU meter going back and forth. I've attached a screenshot showing as much. The internal microphone does not pick up any sounds either when this happens. If I connect my Bose NC700 bluetooth headset, I get sound out of it just fine, and the mike on it also works. Sometimes the internal sound will start working after a few times of switching back and forth internal audio / bluetooth headset. Restarting the systemd pipewire and pipewire-pulse user services doesn't help. Nor does killing & respawning wireplumber. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.58-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Tue Jan 3 11:25:23 2023 InstallationDate: Installed on 2023-01-03 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pipewire UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2000917/+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 2002102] [NEW] gnome-shell has continouus high cpu utilization of nearly 20 %
Public bug reported: excerpt from top: 4625 michael 20 0 5077584 256364 114324 S 18,3 3,2 10:32.37 gnome-shell 1500 root 20 0 1139948 121488 72424 S 10,6 1,5 7:22.24 Xorg 4858 michael 20 0 405756 44672 32928 S 3,3 0,6 2:14.81 plank 6861 michael 20 0 898372 61712 44712 S 3,0 0,8 0:10.26 gnome-terminal- 5207 michael 31 11 12,5g 565140 204924 S 2,3 7,0 15:48.61 firefox 14261 michael 31 11 2471436 134648 92944 S 2,0 1,7 0:06.48 Isolated Web Co 10389 root 20 0 0 0 0 I 1,3 0,0 0:28.22 kworker/1:3-events 14 root 20 0 0 0 0 I 0,3 0,0 0:05.85 rcu_sched 22 root 20 0 0 0 0 S 0,3 0,0 0:14.96 ksoftirqd/1 131 root 0 -20 0 0 0 D 0,3 0,0 0:03.14 kworker/u9:0+i915_flip 177 root 0 -20 0 0 0 I 0,3 0,0 0:01.17 kworker/2:1H-events_highpri 250 root 20 0 0 0 0 I 0,3 0,0 0:10.68 kworker/0:2-events 4902 michael 31 11 1827896 50784 17048 S 0,3 0,6 0:19.78 syncthing 5504 michael 31 11 2486188 141052 91908 S 0,3 1,8 0:31.26 Isolated Web Co 6788 michael 20 0 1471320 76164 57676 S 0,3 0,9 0:26.51 wfica 7142 michael 20 0 15768 3296 R 0,3 0,1 0:14.54 top 7150 michael 20 0 3948680 384776 194316 S 0,3 4,8 0:26.26 thunderbird ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 Uname: Linux 5.15.0-57-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 11:32:40 2023 DisplayManager: lightdm EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-19 (2696 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150729) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-26 (132 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2002102 Title: gnome-shell has continouus high cpu utilization of nearly 20 % Status in gnome-shell package in Ubuntu: New Bug description: excerpt from top: 4625 michael 20 0 5077584 256364 114324 S 18,3 3,2 10:32.37 gnome-shell 1500 root 20 0 1139948 121488 72424 S 10,6 1,5 7:22.24 Xorg 4858 michael 20 0 405756 44672 32928 S 3,3 0,6 2:14.81 plank 6861 michael 20 0 898372 61712 44712 S 3,0 0,8 0:10.26 gnome-terminal- 5207 michael 31 11 12,5g 565140 204924 S 2,3 7,0 15:48.61 firefox 14261 michael 31 11 2471436 134648 92944 S 2,0 1,7 0:06.48 Isolated Web Co 10389 root 20 0 0 0 0 I 1,3 0,0 0:28.22 kworker/1:3-events 14 root 20 0 0 0 0 I 0,3 0,0 0:05.85 rcu_sched 22 root 20 0 0 0 0 S 0,3 0,0 0:14.96 ksoftirqd/1 131 root 0 -20 0 0 0 D 0,3
[Desktop-packages] [Bug 2002098] Re: Intel PCI ID 8086:9a78 missing in pci.ids
It is supported, just the name of the GPU is unknown in 22.04. This has been fixed already in later Ubuntu versions and should not affect performance at all. ** Summary changed: - Seems like my GPU isn't supported + Intel PCI ID 8086:9a78 missing in pci.ids ** Package changed: xorg (Ubuntu) => pci.ids (Ubuntu) ** Changed in: pci.ids (Ubuntu) Importance: Undecided => Low ** Changed in: pci.ids (Ubuntu) Status: New => Fix Released -- 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/2002098 Title: Intel PCI ID 8086:9a78 missing in pci.ids Status in pci.ids package in Ubuntu: Fix Released Bug description: (base) walid@len:~$ lspci | grep VGA :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01) (base) walid@len:~$ sudo lshw -C video [sudo] password for walid: *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:400-3ff irq:158 memory:600200-6002ff memory:40-400fff ioport:3000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 (base) walid@len:~$ lspci -nn |egrep "VGA|Display" :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a78] (rev 01) (base) walid@len:~$ sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree... Done Reading state information... Done xserver-xorg-video-intel is already the newest version (2:2.99.917+git20210115-1). xserver-xorg-video-intel set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 11:30:53 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f89] MachineType: LENOVO 82FG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f5b7aa1d-e67f-4b72-8621-88ab6b130991 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2021 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: FHCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ITL05 dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrFHCN59WW:bd08/26/2021:br1.59:efr1.59:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05:skuLENOVO_MT_82FG_BU_idea_FM_IdeaPad515ITL05: dmi.product.family: IdeaPad 5 15ITL05 dmi.product.name: 82FG dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05 dmi.product.version: IdeaPad 5 15ITL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/2002098/+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 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
Can't I just update xorg package somehow (because it is not in the official builds repository for jammy)? Or you think that this problem might be fixed not in xorg, but somewhere else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+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 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
If we don't know exactly what fixed it then the only supported solutions are: (a) Don't use Xorg. Select a desktop environment that supports Wayland instead (like regular Ubuntu using GNOME); or (b) Upgrade to Lubuntu 22.10 where Xorg appears to be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2002098] [NEW] Seems like my GPU isn't supported
Public bug reported: (base) walid@len:~$ lspci | grep VGA :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01) (base) walid@len:~$ sudo lshw -C video [sudo] password for walid: *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:400-3ff irq:158 memory:600200-6002ff memory:40-400fff ioport:3000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 (base) walid@len:~$ lspci -nn |egrep "VGA|Display" :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a78] (rev 01) (base) walid@len:~$ sudo apt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree... Done Reading state information... Done xserver-xorg-video-intel is already the newest version (2:2.99.917+git20210115-1). xserver-xorg-video-intel set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 6 11:30:53 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f89] MachineType: LENOVO 82FG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f5b7aa1d-e67f-4b72-8621-88ab6b130991 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2021 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: FHCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ITL05 dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrFHCN59WW:bd08/26/2021:br1.59:efr1.59:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05:skuLENOVO_MT_82FG_BU_idea_FM_IdeaPad515ITL05: dmi.product.family: IdeaPad 5 15ITL05 dmi.product.name: 82FG dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05 dmi.product.version: IdeaPad 5 15ITL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2002098 Title: Seems like my GPU isn't supported Status in xorg package in Ubuntu: New Bug description: (base) walid@len:~$ lspci | grep VGA :00:02.0 VGA compatible controller: Intel Corporation Device 9a78 (rev 01) (base) walid@len:~$ sudo lshw -C video [sudo] password for walid: *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:400-3ff irq:158 memory:600200-6002ff memory:40-400fff ioport:3000(size=64) memory:c-d
[Desktop-packages] [Bug 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
But how do I update to that without building xorg from source myself? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+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 2001922] Re: Xorg crash
That's fine, it just means Xorg crashed hard. So please report new crashes whenever they occur again and eventually we'll have more luck. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN
[Desktop-packages] [Bug 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
Looks like it might have been fixed when bug 1999213 got fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+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 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
Thanks. This seems to be the 5th most common Xorg crash in Ubuntu 22.04 but it doesn't happen at all in 22.10. So I am thinking it got fixed in Xorg 21.1.4 ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+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 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()
** Summary changed: - Xorg crashes or freezes + Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions() Status in xorg-server package in Ubuntu: Fix Released Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2001922] Re: Xorg crash
I don't see anything useful in the log: Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=4uc+8Lpm5dEaUqICltU/1RtAGdPAJRNDnjN+h4KK4+V198oPek0B866EgtZjQLXjDS9IA4iI+46VWpzNpyNd9hyBDrch5nR> Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gnome-keyring-daemon[1489]: asked to register item /org/freedesktop/secrets/collection/login/4, but it's already registered Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: closing the prompt Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p3@:1.30 Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the PromptDone method on /org/gnome/keyring/Prompt/p3@:1.30, and ignoring reply Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: 10 second inactivity timeout, quitting Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: unregistering prompter Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: disposing prompter Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: finalizing prompter Jan 05 14:02:01 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-66 noise= txrate=144400 Jan 05 14:02:04 xlap wpa_supplicant[1006]: wlp1s0: PMKSA-CACHE-ADDED 00:23:5d:8e:bd:3e 0 Jan 05 14:02:04 xlap wpa_supplicant[1006]: wlp1s0: PMKSA-CACHE-ADDED 1c:e6:c7:3f:8a:c1 0 Jan 05 14:02:04 xlap wpa_supplicant[1006]: wlp1s0: PMKSA-CACHE-ADDED 00:23:5d:8e:bd:31 0 Jan 05 14:02:49 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:02:49 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:02:53 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:02:53 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:03:02 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:03:02 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:03:24 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise= txrate=27 Jan 05 14:03:28 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise= txrate=27 Jan 05 14:03:51 xlap pkexec[4145]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000) Jan 05 14:03:51 xlap pkexec[4145]: petr: Executing command [USER=root] [TTY=unknown] [CWD=/home/petr] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness 15] Jan 05 14:03:56 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-64 noise= txrate=27 Jan 05 14:04:09 xlap systemd[1]: Starting Download data for packages that failed at package install time... Jan 05 14:04:09 xlap systemd[1]: update-notifier-download.service: Deactivated successfully. Jan 05 14:04:09 xlap systemd[1]: Finished Download data for packages that failed at package install time. Jan 05 14:04:38 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:04:38 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users. Jan 05 14:05:12 xlap dbus-daemon[1224]: [session uid=1000 pid=1224] Activating service name='org.mate.atril.Daemon' requested by ':1.107' (uid=1000 pid=4400 comm="atril rna-seq.pdf " label=> Jan 05 14:05:12 xlap dbus-daemon[1224]: [session uid=1000 pid=1224] Successfully activated service 'org.mate.atril.Daemon' Jan 05 14:05:13 xlap dbus-daemon[1224]: [session uid=1000 pid=1224] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.107' (uid=1000 > Jan 05 14:05:13 xlap systemd[1198]: Starting Virtual filesystem metadata service... Jan 05 14:05:13 xlap dbus-daemon[1224]: [session uid=1000 pid=1224] Successfully activated service 'org.gtk.vfs.Metadata' Jan 05 14:05:13 xlap systemd[1198]: Started Virtual filesystem metadata service. Jan 05 14:06:29 xlap systemd[1]:
[Desktop-packages] [Bug 2000649] Re: Xorg crashes or freezes
I tried standard Ubuntu version of xorg and it immediately crashed. I used the `ubuntu-bug` on it and this is the id (in .uploaded file): 949ad2ac-8d9f-11ed-9cde-fa163e993415. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2000649 Title: Xorg crashes or freezes Status in xorg-server package in Ubuntu: Incomplete Bug description: Occasionally, (I wasn't able to reproduce it) xorg just hangs or crashes to the log screen. It happens about every two weeks, especially if I don't reboot often (However doesn't matter much, I think, because it also happens on "fresh" boot). I use bspwm (version from the jammy repository), on Lubuntu 22.04.1 (fresh install, not upgrade from 22.04, nor 20.04). Freezes occur when I switch between desktops, just hangs and that's it, no response to the keyboard, however mouse is usually usable and screen keeps updating. Crashes occur when I switch between windows or desktops (I use shortcuts for this), xorg just goes black and prints my shortcut to the screen; waits for a few secs and opens login screen. I don't know why it is happening, before 22.04 I was using 16.04 never had any problems. I tried google it, use some intel video card in /etc/X11/xorg.conf.d directory, but it makes system unusable at all, just type is super slow and I gave up experimenting with different flags ... I really hope you can tell me something, because this bug is really annoying, especially when I have a lot of windows open and I have to open them all again and again. Thank you in advance and have a nice day! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Wed Dec 28 23:59:36 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2022-12-24 (3 days ago) InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+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 2001922] Re: Xorg crash
No we can't process .crash files manually. Can you check to see if Xorg logged messages about the crash in the seconds prior to Thu Jan 5 14:09:26 2023?... Xorg likes to handle its own crashes which sometimes causes us problems. We don't get clean crash reports from Xorg, or that we don't get useful symbols in its bespoke crash logger. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias:
[Desktop-packages] [Bug 2001922] Re: Xorg crash
The journal says contains these entries: Jan 05 14:09:26 xlap systemd[1]: Starting Process error reports when automatic reporting is enabled... Jan 05 14:09:26 xlap systemd[1]: Started crash report submission. Jan 05 14:09:26 xlap whoopsie[5359]: [14:09:26] Using lock path: /var/lock/whoopsie/lock Jan 05 14:09:26 xlap systemd[1]: whoopsie.service: Deactivated successfully. Jan 05 14:09:26 xlap whoopsie-upload-all[5358]: INFO:root:/var/crash/_usr_libexec_valgrind_memcheck-amd64-linux.1000.crash already marked for upload, skipping Jan 05 14:09:26 xlap whoopsie-upload-all[5358]: INFO:root:Collecting info for /var/crash/_usr_lib_xorg_Xorg.0.crash... Jan 05 14:09:26 xlap systemd[1]: Started crash report submission. Jan 05 14:09:26 xlap whoopsie[5364]: [14:09:26] Using lock path: /var/lock/whoopsie/lock Jan 05 14:09:26 xlap systemd[1]: whoopsie.service: Deactivated successfully. Do you want me to attach the file /var/crash/_usr_lib_xorg_Xorg.0.crash here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro
[Desktop-packages] [Bug 2001922] Re: Xorg crash
Thanks. Unfortunately that's not showing the crash location, I don't know why: https://errors.ubuntu.com/oops/311e7093-8cfa-11ed-aae6-fa163e55efd0 Can you find the system log entries (using journalctl) from the time of the crash? (Thu Jan 5 14:09:26 2023) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias:
[Desktop-packages] [Bug 2001922] Re: Xorg crash
The file contains this ID: 311e7093-8cfa-11ed-aae6-fa163e55efd0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Thu Jan 5 14:17:42 2023 DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3f96] InstallationDate: Installed on 2021-11-07 (424 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago) dmi.bios.date: 09/23/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook