[Desktop-packages] [Bug 2015540] Re: Loop PCIe Bus Error
this bug is wrong, the problem is a kernel loop, no problem with gnome-shell. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015670 -- 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/2015540 Title: Loop PCIe Bus Error Status in gnome-shell package in Ubuntu: New Bug description: at login hi have this loop: Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0:[ 0] RxErr (First) Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0:[ 0] RxErr (First) Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 7 11:50:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-31 (6 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540/+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 2015671] [NEW] no spinning Ubuntu logo on startup
Public bug reported: no spinning Ubuntu logo on startup on the latest kernel (6.2.0-19-generic) update ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth-theme-spinner 22.02.122-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 9 16:27:11 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-06-25 (1017 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2022-09-30 (190 days ago) dmi.bios.date: 02/10/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd02/10/2023:br1.22:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2015671 Title: no spinning Ubuntu logo on startup Status in plymouth package in Ubuntu: New Bug description: no spinning Ubuntu logo on startup on the latest kernel (6.2.0-19-generic) update ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth-theme-spinner 22.02.122-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 9 16:27:11 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-06-25 (1017 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2022-09-30 (190 days ago) dmi.bios.date: 02/10/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd02/10/2023:br1.22:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2015671/+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 2015540] Re: Loop PCIe Bus Error
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015540 Title: Loop PCIe Bus Error Status in gnome-shell package in Ubuntu: Invalid Bug description: at login hi have this loop: Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0:[ 0] RxErr (First) Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0:[ 0] RxErr (First) Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 7 11:50:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-31 (6 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540/+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 2015674] [NEW] Unread mail notification does not update
Public bug reported:
The Thunderbird icon on the dock shows the count of new mails correctly,
but the icon does not update itself once the emails have been read. Even
restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once the
mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Finnish Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric 600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-af991e4b-f99c-455f-8b24-2a1ee2160904
bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
dmi.bios.date: 06/27/2022
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET72W(1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001AMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001AMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lunar wayland-session
** Description changed:
- Thunderbird shows the count of new mails correctly, but the icon does
- not update itself once the mail is read. Event restarting the app will
- not update the icon.
+ The Thunderbird icon on the doct shows the count of new mails correctly,
+ but the icon does not update itself once the mail has been read. Event
+ restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once the
mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
- English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
- Finnish Language Pack - langpack...@thunderbird.mozilla.org
- Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
+ English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
+ Finnish Language Pack - langpack...@thunderbird.mozilla.org
+ Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
- default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
- 169.254.0.0/16 dev wlp3s0 scope link metric 1000
- 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
+ default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
+ 169.254.0.0/16 dev wlp3s0 scope link metric 1000
+ 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage
[Desktop-packages] [Bug 2015674] Re: Unread mail notifications do not update
** Summary changed:
- Unread mail notification does not update
+ Unread mail notifications do not update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2015674
Title:
Unread mail notifications do not update
Status in thunderbird package in Ubuntu:
New
Bug description:
The Thunderbird icon on the dock shows the count of new mails
correctly, but the icon does not update itself once the emails have
been read. Even restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once
the mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Finnish Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-af991e4b-f99c-455f-8b24-2a1ee2160904
bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
dmi.bios.date: 06/27/2022
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET72W(1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001AMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001AMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2015674/+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 2015660] Re: Unable to set Super+P as custom shortcut
lucio@biscoito:~$ gsettings get org.gnome.mutter.keybindings switch-monitor ['p', 'XF86Display'] Add 'Super+P' as a custom shortcut maybe should disable and warn about Mutter switch-monitor keybind. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2015660 Title: Unable to set Super+P as custom shortcut Status in gnome-control-center package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu lucio@biscoito:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-control-center: Installed: 1:44.0-1ubuntu4 Candidate: 1:44.0-1ubuntu4 Version table: *** 1:44.0-1ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I'm trying to run "playerctl play-pause" using the custom gnome shortcut 'Super+P'. 4) What happened instead 1. Nothing happens. 2. If using another shortcut like 'Super+W' it works, but not Super+P. 3. playerctl play-pause works on cli. lucio@biscoito:~$ dconf dump / | grep Super close=['q'] lower=['j'] maximize=['f'] move-to-workspace-1=['1'] move-to-workspace-2=['2'] move-to-workspace-3=['3'] move-to-workspace-4=['4'] raise=['k'] switch-to-workspace-1=['1'] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] toggle-tiled-left=['h'] toggle-tiled-right=['l'] email=['m'] mic-mute=['BackSpace'] screensaver=['x'] terminal=['Return'] volume-down=['minus'] volume-mute=['BackSpace'] volume-up=['equal'] www=['b'] binding='p' << the infamous one. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 8 20:18:56 2023 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015660/+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 1901609] Re: signond causes qprocess crash
April 9, 2023 Operating System: Ubuntu 22.04 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-10005-tuxedo (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: Latitude E7470 - Bug still exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
April 9, 2023 Operating System: Ubuntu 22.04 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-10005-tuxedo (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: Latitude E7470 - Bug still exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes
I'm dropping the Kinetic tasks since we don't support glib 2.76.1 on Kinetic. ** No longer affects: gjs (Ubuntu Kinetic) ** No longer affects: gnome-characters (Ubuntu Kinetic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2012287 Title: GNOME Characters search provider for GNOME Shell 44 crashes Status in GNOME Characters: Fix Released Status in gjs package in Ubuntu: Confirmed Status in gnome-characters package in Ubuntu: Triaged Status in gjs source package in Lunar: Confirmed Status in gnome-characters source package in Lunar: Triaged Bug description: Test Case - 1. From Ubuntu 22.10, install Lunar's glib 2.76.1 2. Log out 3. Log back in 4. Open the GNOME Shell Activities Overview and type the word smile 5. Close the Activities Overview What Happens In my case, if I repeat 4 and 5 several times, I will eventually get an apport crash popup dialog reporting that the GNOME Shell search provider for GNOME Characters has crashed. Other Info -- This isn't a gjs bug, but I'm leaving the gjs task open since I think apport looks for it. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gjs 1.75.90-1 Uname: Linux 6.1.0-16-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 23:04:59 2023 ExecutablePath: /usr/bin/gjs-console ExecutableTimestamp: 1678210639 ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters --gapplication-service ProcCwd: /home/solomax Signal: 6 SourcePackage: gjs UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-characters/+bug/2012287/+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 1993668] Re: mSBC codec not available only CVSD one
** Changed in: pipewire Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993668 Title: mSBC codec not available only CVSD one Status in Linux: Confirmed Status in PipeWire: Fix Released Status in linux package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Bug description: I am using Ubuntu 22.10 and my headset Pixel Buds Pro works correctly but only the low-quality CVSD codec is available and not the mSBC one for the Handsfree profile. I know the Pixel Buds Pro headset are compatible with mSBC because on another machine also running Ubuntu 22.10, this headset correctly works with the mSBC codec (and the audio quality is much better for both input and output audio). My motherboard is an Aorus x670 with AMD Zen 4 CPU. The bluetooth controller seems to be: ``` Bus 005 Device 003: ID 0e8d:0616 MediaTek Inc. Wireless_Device ``` Let me know if you need more informations. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-27 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) NonfreeKernelModules: nvidia_modeset nvidia Package: pipewire 0.3.58-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-21-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/linux/+bug/1993668/+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 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04
Version - Ubuntu 22.04 Kernel - 5.19.0-38-generic Processor - AMD Ryzen 7 6800U with Radeon Graphics x8 Graphics Card (onboard) - Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt (Laptop is a GPD Win Max 2) The TV being used is an older Samsung model. This issue is still present for me. Sound works perfectly well with windows, so I am 99.9% certain the issue is something in ubuntu itself. Ran MOC with a looping sound file and then opened Pulseaudio Volume Control. Under output devices, with the default device selected, it plays perfectly well. The HDMI shows up correctly under audio devices [HDMI/DisplayPort 2 (plugged in)], but when selected no sound emerges. The output bar is showing that sound is being routed through that port, but nothing emerges. Option selected under advanced is just PCM (not sure what these do but it's best to report everything). -- 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/1970050 Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: After upgrading today from 20.04 LTS to 22.04 HDMI Audio does not work at all. Audio from speakers from a headphone jack works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 21:13:23 2022 InstallationDate: Installed on 2020-04-24 (729 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97M-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Hi, I also have the same issue. In my case, I use DP to connect my monitor to my computer and I was able to use the monitor's built in audio without problems. I have even reinstalled Ubuntu just to check if it was my fault that the audio stopped working. Note, the audio works on Windows. I am currently on kernel 5.19.0-38-generic. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
can confirm. what is causing this? -- 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/1991901 Title: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available Status in gnome-shell package in Ubuntu: Confirmed Bug description: This error is too noisy and also not an error. Many systems and most desktops won't have fingerprint devices. JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991901/+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 2015691] [NEW] gnome-shell crashes while interacting with firefox
Public bug reported:
Output of gdb backtrace full:
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {0}}
ret =
#1 __pthread_kill_internal (signo=11, threadid=) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at
./nptl/pthread_kill.c:89
#3 0x7fd23e83c406 in __GI_raise (sig=sig@entry=11) at
../sysdeps/posix/raise.c:26
ret =
#4 0x564413f87aea in dump_gjs_stack_on_signal_handler (signo=11) at
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x564413f87730
, sa_sigaction = 0x564413f87730
}, sa_mask = {__val = {0 }},
sa_flags = 0, sa_restorer = 0x0}
i =
#5 0x7fd23e83c4b0 in () at
/lib/x86_64-linux-gnu/libc.so.6
#6 0x7fd23ed2ce04 in meta_wayland_compositor_get_context () at
/lib/x86_64-linux-gnu/libmutter-12.so.0
#7 0x7fd23ed3046f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#8 0x7fd23bf0dfaf in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#9 0x7fd23bf0fe0e in wl_resource_destroy () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#10 0x7fd23e3758b6 in () at /lib/x86_64-linux-gnu/libffi.so.8
#11 0x7fd23e37234d in () at /lib/x86_64-linux-gnu/libffi.so.8
#12 0x7fd23e374f33 in ffi_call () at /lib/x86_64-linux-gnu/libffi.so.8
#13 0x7fd23bf0b2a0 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#14 0x7fd23bf0f694 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#15 0x7fd23bf0e0fa in wl_event_loop_dispatch () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#16 0x7fd23ed2a73b in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#17 0x7fd23f2b349d in g_main_dispatch (context=0x56441550e3b0) at
../../../glib/gmain.c:3460
dispatch = 0x7fd23ed2a720
prev_source = 0x0
begin_time_nsec = 0
was_in_call = 0
user_data = 0x0
callback = 0x0
cb_funcs =
cb_data =
need_destroy =
source = 0x5644155c50e0
current = 0x5644154ec5b0
i = 0
#18 g_main_context_dispatch (context=0x56441550e3b0) at
../../../glib/gmain.c:4200
#19 0x7fd23f30e178 in g_main_context_iterate.constprop.0
(context=0x56441550e3b0, block=, dispatch=1, self=) at ../../../glib/gmain.c:4276
max_priority = 2147483647
timeout = 134
some_ready = 1
nfds =
allocated_nfds = 28
fds = 0x5644226315d0
#20 0x7fd23f2b2bdf in g_main_loop_run (loop=0x5644186fe790) at
../../../glib/gmain.c:4479
__func__ = "g_main_loop_run"
#21 0x7fd23ecbddf9 in meta_context_run_main_loop () at
/lib/x86_64-linux-gnu/libmutter-12.so.0
#22 0x564413f86fa1 in main (argc=, argv=) at
../src/main.c:765
context = 0x56441550c780
debug_flags_string = 0x5644157fa640
"backtrace-aborts:backtrace-math-errors:backtrace-crashes-all:backtrace-all"
error = 0x0
shell_debug =
ecode = 0
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 10:49:04 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-15 (83 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lunar wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2015691
Title:
gnome-shell crashes while interacting with firefox
Status in gnome-shell package in Ubuntu:
New
Bug description:
Output of gdb backtrace full:
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {0}}
ret =
#1 __pthread_kill_internal (signo=11, threadid=) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at
./nptl/pthread_kill.c:89
#3 0x7fd23e83c406 in __GI_raise (sig=sig@entry=11) at
../sysdeps/posix/raise.c:26
ret =
#4 0x564413f87aea in dump_gjs_stack_on_signal_handler (signo=11) at
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x564413f87730
, sa_sigaction = 0x564413f87730
}, sa_mask = {__val = {0 }},
sa_flags = 0, sa_restorer = 0x0}
i =
#5 0x7fd23e83c4b0 in () at
/lib/x86_64-linux-gnu/libc.so.
[Desktop-packages] [Bug 2015691] Re: gnome-shell crashes while interacting with firefox
Attaching gdb backtrace full output since paste looks line-wrapped.
** Attachment added: "gdb_usr-bin-gnome-shell_backtrace-full.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015691/+attachment/5662484/+files/gdb_usr-bin-gnome-shell_backtrace-full.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2015691
Title:
gnome-shell crashes while interacting with firefox
Status in gnome-shell package in Ubuntu:
New
Bug description:
Output of gdb backtrace full:
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {0}}
ret =
#1 __pthread_kill_internal (signo=11, threadid=) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at
./nptl/pthread_kill.c:89
#3 0x7fd23e83c406 in __GI_raise (sig=sig@entry=11) at
../sysdeps/posix/raise.c:26
ret =
#4 0x564413f87aea in dump_gjs_stack_on_signal_handler (signo=11) at
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x564413f87730
, sa_sigaction = 0x564413f87730
}, sa_mask = {__val = {0 }},
sa_flags = 0, sa_restorer = 0x0}
i =
#5 0x7fd23e83c4b0 in () at
/lib/x86_64-linux-gnu/libc.so.6
#6 0x7fd23ed2ce04 in meta_wayland_compositor_get_context () at
/lib/x86_64-linux-gnu/libmutter-12.so.0
#7 0x7fd23ed3046f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#8 0x7fd23bf0dfaf in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#9 0x7fd23bf0fe0e in wl_resource_destroy () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#10 0x7fd23e3758b6 in () at /lib/x86_64-linux-gnu/libffi.so.8
#11 0x7fd23e37234d in () at /lib/x86_64-linux-gnu/libffi.so.8
#12 0x7fd23e374f33 in ffi_call () at /lib/x86_64-linux-gnu/libffi.so.8
#13 0x7fd23bf0b2a0 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#14 0x7fd23bf0f694 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#15 0x7fd23bf0e0fa in wl_event_loop_dispatch () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#16 0x7fd23ed2a73b in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#17 0x7fd23f2b349d in g_main_dispatch (context=0x56441550e3b0) at
../../../glib/gmain.c:3460
dispatch = 0x7fd23ed2a720
prev_source = 0x0
begin_time_nsec = 0
was_in_call = 0
user_data = 0x0
callback = 0x0
cb_funcs =
cb_data =
need_destroy =
source = 0x5644155c50e0
current = 0x5644154ec5b0
i = 0
#18 g_main_context_dispatch (context=0x56441550e3b0) at
../../../glib/gmain.c:4200
#19 0x7fd23f30e178 in g_main_context_iterate.constprop.0
(context=0x56441550e3b0, block=, dispatch=1, self=) at ../../../glib/gmain.c:4276
max_priority = 2147483647
timeout = 134
some_ready = 1
nfds =
allocated_nfds = 28
fds = 0x5644226315d0
#20 0x7fd23f2b2bdf in g_main_loop_run (loop=0x5644186fe790) at
../../../glib/gmain.c:4479
__func__ = "g_main_loop_run"
#21 0x7fd23ecbddf9 in meta_context_run_main_loop () at
/lib/x86_64-linux-gnu/libmutter-12.so.0
#22 0x564413f86fa1 in main (argc=, argv=)
at ../src/main.c:765
context = 0x56441550c780
debug_flags_string = 0x5644157fa640
"backtrace-aborts:backtrace-math-errors:backtrace-crashes-all:backtrace-all"
error = 0x0
shell_debug =
ecode = 0
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 10:49:04 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-01-15 (83 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015691/+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 2015691] Re: gnome-shell crashes while interacting with firefox
This has been happening every few days to week for the last couple
months. I've installed lunar from scratch on January 15. I upgraded from
kernel 5.19.0-19 to 6.1.0-14 late January. I have been regularly
updating.
I have text copies of journald logs going back to March 1, so I think this
covers the dates:
root@neil:~
# grep -i gnome-shell j.Wed\ 22\ Mar\ 2023\ 10\:39\:15\ AM\ MDT | grep -i
crashed
Mar 17 17:22:59 neil gnome-shell[9530]: GNOME Shell crashed with signal 11
Mar 20 13:53:41 neil gnome-shell[16559]: GNOME Shell crashed with signal 11
Mar 20 13:55:27 neil gnome-shell[242217]: GNOME Shell crashed with signal 11
Mar 21 13:40:42 neil gnome-shell[9042]: GNOME Shell crashed with signal 11
Mar 22 10:11:09 neil gnome-shell[6556]: GNOME Shell crashed with signal 11
root@neil:~
# grep -i gnome-shell j.Sun\ 09\ Apr\ 2023\ 10\:29\:27\ AM\ MDT | grep -i
crashed
Mar 28 11:21:54 neil gnome-shell[14173]: GNOME Shell crashed with signal 11
Mar 29 12:38:02 neil gnome-shell[6334]: GNOME Shell crashed with signal 11
Mar 29 16:01:21 neil gnome-shell[6575]: GNOME Shell crashed with signal 11
Apr 03 15:54:18 neil gnome-shell[246110]: GNOME Shell crashed with signal 11
Apr 06 09:33:04 neil gnome-shell[6814]: GNOME Shell crashed with signal 11
Apr 09 10:25:49 neil gnome-shell[13108]: GNOME Shell crashed with signal 11
Here is the latest apt upgrade prior to the first crash:
Start-Date: 2023-03-17 15:52:16
Commandline: apt upgrade
Requested-By: bme (1000)
Upgrade: libcanberra-gtk3-0:amd64 (0.30-10ubuntu2, 0.30-10ubuntu4),
yaru-theme-icon:amd64 (22.10.3-1, 23.04.1-0ubuntu1), libext2fs2:amd64
(1.46.6~rc1-1ubuntu1, 1.47.0-1ubuntu1), aspnetcore-runtime-6.0:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), sosreport:amd64 (4.4-1ubuntu2,
4.5-1ubuntu0), gnome-control-center-faces:amd64 (1:44~rc-1ubuntu1,
1:44~rc-1ubuntu2), libcanberra-gtk3-module:amd64 (0.30-10ubuntu2,
0.30-10ubuntu4), ibus-gtk3:amd64 (1.5.28-1, 1.5.28-2), ibus-gtk4:amd64
(1.5.28-1, 1.5.28-2), liblzma5:amd64 (5.4.1-0.0, 5.4.1-0.2), liblzma5:i386
(5.4.1-0.0, 5.4.1-0.2), dotnet-hostfxr-6.0:amd64 (6.0.114-0ubuntu1,
6.0.115-0ubuntu1), python3-ibus-1.0:amd64 (1.5.28-1, 1.5.28-2),
libostree-1-1:amd64 (2022.7-2, 2022.7-2ubuntu1), dotnet-sdk-6.0:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), dotnet-targeting-pack-6.0:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), poppler-data:amd64 (0.4.11-1, 0.4.12-1),
xz-utils:amd64 (5.4.1-0.0, 5.4.1-0.2), libcom-err2:amd64 (1.46.6~rc1-1ubuntu1,
1.47.0-1ubunt
u1), libcom-err2:i386 (1.46.6~rc1-1ubuntu1, 1.47.0-1ubuntu1),
liblzma-dev:amd64 (5.4.1-0.0, 5.4.1-0.2), gir1.2-ibus-1.0:amd64 (1.5.28-1,
1.5.28-2), ibus-data:amd64 (1.5.28-1, 1.5.28-2), yaru-theme-sound:amd64
(22.10.3-1, 23.04.1-0ubuntu1), yaru-theme-gtk:amd64 (22.10.3-1,
23.04.1-0ubuntu1), dotnet-templates-6.0:amd64 (6.0.114-0ubuntu1,
6.0.115-0ubuntu1), librest-1.0-0:amd64 (0.9.1-4, 0.9.1-5), python3-doc:amd64
(3.11.1-3, 3.11.2-1), dotnet-host:amd64 (6.0.114-0ubuntu1, 6.0.115-0ubuntu1),
gnome-control-center-data:amd64 (1:44~rc-1ubuntu1, 1:44~rc-1ubuntu2),
ibus-gtk:amd64 (1.5.28-1, 1.5.28-2), netstandard-targeting-pack-2.1:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), gnome-control-center:amd64
(1:44~rc-1ubuntu1, 1:44~rc-1ubuntu2), gnome-session-canberra:amd64
(0.30-10ubuntu2, 0.30-10ubuntu4), libcanberra-pulse:amd64 (0.30-10ubuntu2,
0.30-10ubuntu4), ibus:amd64 (1.5.28-1, 1.5.28-2), dotnet-apphost-pack-6.0:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), aspnetcore-targeting-pack-6.0:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), logsave:amd64 (1.46.6~rc1-1ubuntu1,
1.47.0-1ubuntu1), flatpak:amd64 (1.14.3-1, 1.14.4-1),
yaru-theme-gnome-shell:amd64 (22.10.3-1, 23.04.1-0ubuntu1), libibus-1.0-5:amd64
(1.5.28-1, 1.5.28-2), libss2:amd64 (1.46.6~rc1-1ubuntu1, 1.47.0-1ubuntu1),
libcanberra0:amd64 (0.30-10ubuntu2, 0.30-10ubuntu4), dotnet-runtime-6.0:amd64
(6.0.114-0ubuntu1, 6.0.115-0ubuntu1), e2fsprogs:amd64 (1.46.6~rc1-1ubuntu1,
1.47.0-1ubuntu1)
End-Date: 2023-03-17 15:53:45
--
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/2015691
Title:
gnome-shell crashes while interacting with firefox
Status in gnome-shell package in Ubuntu:
New
Bug description:
Output of gdb backtrace full:
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {0}}
ret =
#1 __pthread_kill_internal (signo=11, threadid=) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at
./nptl/pthread_kill.c:89
#3 0x7fd23e83c406 in __GI_raise (sig=sig@entry=11) at
../sysdeps/posix/raise.c:26
ret =
#4 0x564413f87aea in dump_gjs_stack_on_signal_handler (signo=11) at
../src/main.c:495
sa = {__sigaction_handler = {sa_handler = 0x564413f87730
, sa_sigaction = 0x564413f87730
}, sa
[Desktop-packages] [Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
same with ubuntu 22.10. is something planned to be done about this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language Status in gdm: New Status in GNOME Screensaver: New Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Lock screen (gnome-screensaver) uses last active window's language (keyboard layout) instead of default keyboard language. Steps to reproduce this bug: 1. In the system Text Entry settings: 1a. add two or more languages to the input sources list, e.g. English (as first and default) and Russian (as second); 1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock). 1c. Select "Allow different sources for each window" radio button. 1d. Select "New windows use the default source" radio button. 2. Run any application (e.g. gedit) and switch keyboard to second input language (Russian). 3. Lock the screen (Ctrl+Alt+L) or just wait idle time. 4. See what language set by default for password input in the lock screen. Expected: lock screen uses first input language (English) by default. What happened instead: lock screen uses last active window's language (Russian). Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds) gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1286910/+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 2015706] [NEW] Automatic time-zone detection does not work
Public bug reported: Whenever gsd-datetime attempts to query the location, the following lines appear in journalctl: Apr 09 17:38:11 prescott gsd-datetime[13578]: g_bytes_unref_to_data: assertion 'size != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_file_set_contents_full: assertion 'contents != NULL || length == 0' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_task_return_error: assertion 'error != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: GTask 0x562ac7384890 (source object: 0x562ac6d73480, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. After doing some debugging, I have found that the issue is fixed by applying this commit from upstream: https://gitlab.gnome.org/GNOME/geocode- glib/-/commit/72285d203963c118a05f810016b584210663ae80 ** Affects: geocode-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/2015706 Title: Automatic time-zone detection does not work Status in geocode-glib package in Ubuntu: New Bug description: Whenever gsd-datetime attempts to query the location, the following lines appear in journalctl: Apr 09 17:38:11 prescott gsd-datetime[13578]: g_bytes_unref_to_data: assertion 'size != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_file_set_contents_full: assertion 'contents != NULL || length == 0' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_task_return_error: assertion 'error != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: GTask 0x562ac7384890 (source object: 0x562ac6d73480, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. After doing some debugging, I have found that the issue is fixed by applying this commit from upstream: https://gitlab.gnome.org/GNOME/geocode- glib/-/commit/72285d203963c118a05f810016b584210663ae80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/2015706/+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 2015706] Re: Automatic time-zone detection does not work
** Changed in: geocode-glib (Ubuntu) Importance: Undecided => High ** Changed in: geocode-glib (Ubuntu) Status: New => Triaged ** Tags added: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/2015706 Title: Automatic time-zone detection does not work Status in geocode-glib package in Ubuntu: Triaged Bug description: Whenever gsd-datetime attempts to query the location, the following lines appear in journalctl: Apr 09 17:38:11 prescott gsd-datetime[13578]: g_bytes_unref_to_data: assertion 'size != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_file_set_contents_full: assertion 'contents != NULL || length == 0' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_task_return_error: assertion 'error != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: GTask 0x562ac7384890 (source object: 0x562ac6d73480, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. After doing some debugging, I have found that the issue is fixed by applying this commit from upstream: https://gitlab.gnome.org/GNOME/geocode- glib/-/commit/72285d203963c118a05f810016b584210663ae80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/2015706/+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 2015714] [NEW] Xorg freeze
Public bug reported: Hangs occurs either I during Opera browser launches or when I surf the net in Opera. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 06:04:43 2023 DistUpgraded: 2022-10-09 11:13:16,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: 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: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2020-08-19 (963 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire A515-43 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=71ead6cb-c8fa-4dc4-aac5-d0b56b6a8640 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-10-09 (182 days ago) dmi.bios.date: 12/04/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd12/04/2019:br1.7:efr1.6:svnAcer:pnAspireA515-43:pvrV1.07:rvnPK:rnGrumpy_PK:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 freeze 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/2015714 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hangs occurs either I during Opera browser launches or when I surf the net in Opera. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 06:04:43 2023 DistUpgraded: 2022-10-09 11:13:16,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: 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: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2020-08-19 (963 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire A515-43 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=71ead6cb-c8fa-4dc4-aac5-d0b56b6a8640 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-10-09 (182 days ago) dmi.bios.date: 12/04/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V
[Desktop-packages] [Bug 2015714] Re: Xorg freeze
** Description changed: - Hangs occurs either I during Opera browser launches or when I surf the - net in Opera. + Hangs occurs either when Opera browser launches or when I surf the net + in Opera. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 06:04:43 2023 DistUpgraded: 2022-10-09 11:13:16,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: - 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: Acer Incorporated [ALI] Picasso [1025:134f] + 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: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2020-08-19 (963 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire A515-43 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=71ead6cb-c8fa-4dc4-aac5-d0b56b6a8640 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-10-09 (182 days ago) dmi.bios.date: 12/04/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd12/04/2019:br1.7:efr1.6:svnAcer:pnAspireA515-43:pvrV1.07:rvnPK:rnGrumpy_PK:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 -- 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/2015714 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hangs occurs either when Opera browser launches or when I surf the net in Opera. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 06:04:43 2023 DistUpgraded: 2022-10-09 11:13:16,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: 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: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2020-08-19 (963 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire A515-43 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LA
