[Touch-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 Ubuntu Touch seeded 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)
[Touch-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 Ubuntu Touch seeded 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.
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2015696] Re: add-apt-repository crashed with --- in _request()
*** This bug is a duplicate of bug 2015695 *** https://bugs.launchpad.net/bugs/2015695 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2015695, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2015696/+attachment/5662500/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2015696/+attachment/5662501/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2015695 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2015696 Title: add-apt-repository crashed with --- in _request() Status in software-properties package in Ubuntu: New Bug description: bug during use ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: software-properties-common 0.99.35 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 9 14:50:11 2023 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2023-04-09 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230406) InterpreterPath: /usr/bin/python3.11 JournalErrors: abr 09 14:50:14 hostname systemd[11707]: update-notifier-crash.service: Failed with result 'exit-code'. abr 09 14:50:14 hostname systemd[11707]: Failed to start update-notifier-crash.service - Notification regarding a crash report. PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:touchegg/stable ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:touchegg/stable'] PythonDetails: N/A SourcePackage: software-properties Title: add-apt-repository crashed with --- in _request() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2015696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash
-- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
