[Desktop-packages] [Bug 2052853] Re: Wired Jaba Evolve headsets lose sidetone sound after 3-5 seconds after connecting to usb ports
An update. It is clear that sidetone for both jabra headsets now works only during recording but gets muted after I stop recording and/or when I'm playing a audio at the moment. Something's definitely wrong with the drivers. -- 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/2052853 Title: Wired Jaba Evolve headsets lose sidetone sound after 3-5 seconds after connecting to usb ports Status in alsa-driver package in Ubuntu: New Bug description: Hi, I assume this is an alsa problem although I'm not sure. This problem didn't exist for me on Ubuntu 18.04. After upgrading to 22.04 my 2 usb jabra evolve headsets started to lose sidetones almost immediately after connecting to the same PC with ubuntu 22.04 installed. Here's the details about my hardware. These are USB wired devices named Jabra Evolve 40 MS and Jabra Evolve 80. These two devices worked perfectly on Ubuntu 18.04. Output speakers, Input microphones and sidetone worked Okay for both of them. On both headsets sidetone feature is enabled once you put the device into usb slot. However after upgrading to 22.04 I'm having problems with sidetones on both of them. Microphones and speakers still work fine but Sidetone features got switched off after 3-5 seconds after I connect them to the PC. At the same time alsamixer shows correct setting for sidetone for both of them. Sidetones are enabled and volume is high. (See a attached picture). But after attaching the device to USB the sidetone works for 3-5 seconds only and then I hear a tiny click sound and sidetone gets disabled. It's strange that although alsamixer still shows sidetone enables there's no sidetone sound in speakers. This is for both headsets I have. I've just checked headsets under audacity. Sidetone starts to work after I press 'record' button and continue to work up until 5 seconds after I stop recording. For these devices sidetone must work independently on what the user is doing with the software. It's just a hardware feature of these headsets but somehow it gets switched off by some alsa commands or something. Please help. Headsets are unusable anymore. I'm ready to provide any information related to this bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ys 8906 F pulseaudio /dev/snd/controlC0: ys 8906 F pulseaudio /dev/snd/controlC2: ys 8906 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Feb 10 12:20:41 2024 InstallationDate: Installed on 2024-02-06 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: P67A-D3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-D3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-D3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P67A-D3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2024-02-07T22:14:28.359964 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2052853/+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 2052853] Re: Wired Jaba Evolve headsets lose sidetone sound after 3-5 seconds after connecting to usb ports
** Description changed: Hi, - I assume this is alsa problem although I'm not sure. - This problem didn't exist for me on Ubuntu 18.04. After upgrading to 22.04 my 2 usb jabra evolve headsets started to lose sidetones almost immediately after connecting to the same PC with ubuntu 22.04 installed. Here's the details about my hardware. + I assume this is an alsa problem although I'm not sure. + + This problem didn't exist for me on Ubuntu 18.04. After upgrading to + 22.04 my 2 usb jabra evolve headsets started to lose sidetones almost + immediately after connecting to the same PC with ubuntu 22.04 installed. + Here's the details about my hardware. These are USB wired devices named Jabra Evolve 40 MS and Jabra Evolve 80. These two devices worked perfectly on Ubuntu 18.04. Output speakers, - Input microphones and sidetone worked Okay for both of them. Now after - upgrading to 22.04 I'm having problems with sidetones on both of them. - Microphones and speakers still work fine but Sidetone features got - switched off after 3-5 seconds when I connect them to PC. + Input microphones and sidetone worked Okay for both of them. On both + headsets sidetone feature is enabled once you put the device into usb + slot. However after upgrading to 22.04 I'm having problems with + sidetones on both of them. Microphones and speakers still work fine but + Sidetone features got switched off after 3-5 seconds after I connect + them to the PC. - alsamixer shows correct setting for sidetone for both of them. Sidetones - are enabled and volume is high. (attaching picture). However after - attaching device to USB the sidetone works for 3-5 seconds and then I - hear tiny click and sidetone gets disabled. Although alsamixer still - shows sidetone enables there's no sound. This is for both headsets I - have. + At the same time alsamixer shows correct setting for sidetone for both + of them. Sidetones are enabled and volume is high. (See a attached + picture). But after attaching the device to USB the sidetone works for + 3-5 seconds only and then I hear a tiny click sound and sidetone gets + disabled. It's strange that although alsamixer still shows sidetone + enables there's no sidetone sound in speakers. This is for both headsets + I have. I've just checked headsets under audacity. Sidetone starts to work after - I press 'record' button and works until 5 seconds after I stop - recording. + I press 'record' button and continue to work up until 5 seconds after I + stop recording. - For these devices sidetone must work independently on what I'm doing. - It's just a hardware feature of these headsets but it gets switched off - by some alsa commands or something. + For these devices sidetone must work independently on what the user is + doing with the software. It's just a hardware feature of these headsets + but somehow it gets switched off by some alsa commands or something. - Please help. Headsets are unusable anymore. + Please help. Headsets are unusable anymore. I'm ready to provide any information related to this bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: ys 8906 F pulseaudio - /dev/snd/controlC0: ys 8906 F pulseaudio - /dev/snd/controlC2: ys 8906 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: ys 8906 F pulseaudio + /dev/snd/controlC0: ys 8906 F pulseaudio + /dev/snd/controlC2: ys 8906 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Feb 10 12:20:41 2024 InstallationDate: Installed on 2024-02-06 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: P67A-D3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-D3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-D3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P67A-D3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2024-02-07T22:14:28.359964 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in
[Desktop-packages] [Bug 2052853] [NEW] Wired Jaba Evolve headsets lose sidetone sound after 3-5 seconds after connecting to usb ports
Public bug reported: Hi, I assume this is alsa problem although I'm not sure. This problem didn't exist for me on Ubuntu 18.04. After upgrading to 22.04 my 2 usb jabra evolve headsets started to lose sidetones almost immediately after connecting to the same PC with ubuntu 22.04 installed. Here's the details about my hardware. These are USB wired devices named Jabra Evolve 40 MS and Jabra Evolve 80. These two devices worked perfectly on Ubuntu 18.04. Output speakers, Input microphones and sidetone worked Okay for both of them. Now after upgrading to 22.04 I'm having problems with sidetones on both of them. Microphones and speakers still work fine but Sidetone features got switched off after 3-5 seconds when I connect them to PC. alsamixer shows correct setting for sidetone for both of them. Sidetones are enabled and volume is high. (attaching picture). However after attaching device to USB the sidetone works for 3-5 seconds and then I hear tiny click and sidetone gets disabled. Although alsamixer still shows sidetone enables there's no sound. This is for both headsets I have. I've just checked headsets under audacity. Sidetone starts to work after I press 'record' button and works until 5 seconds after I stop recording. For these devices sidetone must work independently on what I'm doing. It's just a hardware feature of these headsets but it gets switched off by some alsa commands or something. Please help. Headsets are unusable anymore. I'm ready to provide any information related to this bug. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ys 8906 F pulseaudio /dev/snd/controlC0: ys 8906 F pulseaudio /dev/snd/controlC2: ys 8906 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Feb 10 12:20:41 2024 InstallationDate: Installed on 2024-02-06 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F3 dmi.board.name: P67A-D3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-D3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-D3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P67A-D3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2024-02-07T22:14:28.359964 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "alsamixer shows correct sidetine setting but it doesn't work anymore" https://bugs.launchpad.net/bugs/2052853/+attachment/5745521/+files/Screenshot_2024-02-10_12-39-50.png -- 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/2052853 Title: Wired Jaba Evolve headsets lose sidetone sound after 3-5 seconds after connecting to usb ports Status in alsa-driver package in Ubuntu: New Bug description: Hi, I assume this is alsa problem although I'm not sure. This problem didn't exist for me on Ubuntu 18.04. After upgrading to 22.04 my 2 usb jabra evolve headsets started to lose sidetones almost immediately after connecting to the same PC with ubuntu 22.04 installed. Here's the details about my hardware. These are USB wired devices named Jabra Evolve 40 MS and Jabra Evolve 80. These two devices worked perfectly on Ubuntu 18.04. Output speakers, Input microphones and sidetone worked Okay for both of them. Now after upgrading to 22.04 I'm having problems with sidetones on both of them. Microphones and speakers still work fine but Sidetone features got switched off after 3-5 seconds when I connect them to PC. alsamixer shows correct setting for sidetone for both of them. Sidetones are enabled and volume is high. (attaching picture). However after attaching device to USB the sidetone works for 3-5 seconds and then I hear tiny click and sidetone gets disabled. Although alsamixer still shows sidetone enables there's no sound. This is for both headsets I have. I've just checked headsets under audacity. Sidetone starts to work after I press 'record' button and works until 5 seconds after I stop recording. For these devices sidetone
[Desktop-packages] [Bug 2047779] Re: package firefox 120.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2047779 Title: package firefox 120.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: https://bugs.launchpad.net/bugs/2003045 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 120.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sh 853 F pulseaudio BuildID: 20231129155202 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jan 2 00:39:18 2024 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2024-01-01 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.3 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 120.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2024-01-02 (0 days ago) dmi.bios.date: 04/07/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53E.208:bd04/07/2011:br4.6:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku: dmi.product.family: K dmi.product.name: K53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2047779/+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 2036735] Re: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2036735 Title: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: facing problem while upgrading ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 117.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 NonfreeKernelModules: aufs AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aniket 1332 F pulseaudio BuildID: 20230912013654 CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Sep 20 17:22:12 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-18 (610 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.57 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, unpackaged RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 117.0.1+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-09-20 (0 days ago) dmi.bios.date: 06/03/2021 dmi.bios.release: 2.33 dmi.bios.vendor: LENOVO dmi.bios.version: FKCN33WW(V2.01) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ITL05 dmi.ec.firmware.release: 2.33 dmi.modalias: dmi:bvnLENOVO:bvrFKCN33WW(V2.01):bd06/03/2021:br2.33:efr2.33:svnLENOVO:pn82FE:pvrIdeaPad514ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad514ITL05:skuLENOVO_MT_82FE_BU_idea_FM_IdeaPad514ITL05: dmi.product.family: IdeaPad 5 14ITL05 dmi.product.name: 82FE dmi.product.sku: LENOVO_MT_82FE_BU_idea_FM_IdeaPad 5 14ITL05 dmi.product.version: IdeaPad 5 14ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2036735/+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 2037340] Re: Four Screens
** Information type changed from Private Security to Public -- 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/2037340 Title: Four Screens Status in xorg package in Ubuntu: New Bug description: I apologize for any grammar issues, but I can barely see what I am typing. Essentially, when I installed Ubuntu, I had to do so in safe graphics mode, as the screen would otherwise split itself into four different displays that had small amounts of resolution and are rather pale. I managed to install it, but once that happend, and it restarted, it went back to being four screens. I am not sure what to do, as I cannot really read any lines of code. Thank you for your help. I am using an iMac a1311, with an HDD and installed from a flashed usb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 20:33:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2023-09-24 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac10,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268CC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268CC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2037340/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
I've been watching the situation around the outdated Thunderbird package for quite some years now, and I have to speak up as well. It's ridiculous to have a discussion about "regressions" through recolored buttons in an otherwise fully functional mail client version, while at the same time security vulnerabilities remain unpatched for months. You guys really need to rethink your priorities! I would understand if there was a long term option to stay with familiar Thunderbird 102. But since probably nobody wants and has the time to backport security fixes every 14 days, this option doesn't exist. Read the linked issue! Thunderbird developer writes, "[changed color behavior, people complaining on] is a conscious decision we made to simplify our UI" and after that closes the issue as resolved/invalid. Package maintainer calls it "quite a visible user regression and I think we will consider as a blocker to update stable series from 102 to 115". Come on! Since this color change is very noticeable in use, it must be assumed that it was introduced intentionally. There are other (functional!) changes from Thunderbird 102 to 115, that not everyone may like, but the color of buttons is a matter of taste, not a "regression"! Mail clients are software designed mainly to work with, not just to look at. I know that Ubuntu is strict about introducing regressions through updates, what is a good thing in general. But with browsers, the lesson was learned long time ago, that up-to-dateness takes precedence over individual taste and minor functional regressions. That's how mail clients have to be treated as well. So unless there are real regressions please stop this discussion and roll out version 115 soon! -- 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/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+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 2027552] Re: package chromium-browser failed to install
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2027552 Title: package chromium-browser failed to install Status in chromium-browser package in Ubuntu: New Bug description: the package failed to launch. Afterwards I tried removing chromium via cli I got the response that the package is not installed (yet I can see the launch icon in the application menu). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jul 12 09:55:47 2023 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-18 (23 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2027552/+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 2026729] Re: package evince-common 42.3-0ubuntu3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/2026729
Title:
package evince-common 42.3-0ubuntu3 failed to install/upgrade: O
pacote está num mau estado de inconsistência; deve reinstala-lo antes
de tentar configura-lo.
Status in evince package in Ubuntu:
New
Bug description:
mau liga
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: evince-common 42.3-0ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Jul 10 10:29:30 2023
Dependencies:
ErrorMessage: O pacote está num mau estado de inconsistência; deve
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2023-07-10 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic
root=UUID=ee64d929-7c14-4b2a-96f8-790bcec006c2 ro quiet splash
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal,
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: evince
Title: package evince-common 42.3-0ubuntu3 failed to install/upgrade: O
pacote está num mau estado de inconsistência; deve reinstala-lo antes de
tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2026729/+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 2020846] [NEW] High memory usage of gsd-color
Public bug reported: The Gnome shell consumes an extremely high amount of memory and not clearing up. While using the system it doesn't take much memory, however, when being put to sleep, it builds up memory usage. The next day system becomes too slow and takes a long time to respond. It returns to a normal state after I kill the "gsd-color" process from the system monitor. For instance, gsd-color took 1Gb of memory while working, but after putting it to sleep overnight, it shows usage of 28Gb memory the next day. My system is Dell OptiPlex 5050 desktop CPU : Intel® Core™ i7-7700 CPU @ 3.60GHz × 8 OS : Ubuntu 20.04.6 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:28:26 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-19 (1709 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-12-26 (880 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "List of gnome extensions" https://bugs.launchpad.net/bugs/2020846/+attachment/5675765/+files/gnome_extensions -- 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/2020846 Title: High memory usage of gsd-color Status in gnome-shell package in Ubuntu: New Bug description: The Gnome shell consumes an extremely high amount of memory and not clearing up. While using the system it doesn't take much memory, however, when being put to sleep, it builds up memory usage. The next day system becomes too slow and takes a long time to respond. It returns to a normal state after I kill the "gsd-color" process from the system monitor. For instance, gsd-color took 1Gb of memory while working, but after putting it to sleep overnight, it shows usage of 28Gb memory the next day. My system is Dell OptiPlex 5050 desktop CPU : Intel® Core™ i7-7700 CPU @ 3.60GHz × 8 OS : Ubuntu 20.04.6 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-148.165-generic 5.4.231 Uname: Linux 5.4.0-148-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 26 11:28:26 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-19 (1709 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-12-26 (880 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020846/+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] 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=
[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:
[Desktop-packages] [Bug 2004074] [NEW] package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 2
Public bug reported: E: Sub-process /usr/bin/dpkg returned an error code (1) Sat Jan 28 09:02:32 AM EST 2023 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tex-common 6.17 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jan 28 09:02:22 2023 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-06-07 (234 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tex-common Title: package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to jammy on 2022-08-16 (165 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/2004074 Title: package tex-common 6.17 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 2 Status in tex-common package in Ubuntu: New Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) Sat Jan 28 09:02:32 AM EST 2023 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tex-common 6.17 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jan 28 09:02:22 2023 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-06-07 (234 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tex-common Title: package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to jammy on 2022-08-16 (165 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/2004074/+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 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.
Thank you very much Christian for the confirmation (upstream as well) and your further analysis of the issue. Your comment #12 (qemu- system-x86_64 -display gtk) is also reflected in my observation in comment #7. I also appreciate your GDK_BACKEND=x11 ... workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2000739 Title: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. Status in qemu package in Ubuntu: Confirmed Status in wayland package in Ubuntu: New Bug description: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized. This can be seen by running an installed or even a trial Ubuntu from an ISO like: $ qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga The GTK UI of qemu has a feature called "fullscreen" which disables the screen decorations and sets the window to maximize. The decorations go away, but maximize doesn't work. The following details were found so far: - running with GDK_BACKEND=x11 works - using sdl instead of gtk backend works - using the old qemu of Focal, or the newest from upstream git in jammy all fails (no qemu change AFAICS) - host UI widgets (the square at the window top) do not work either - hotkeys (super-up) do not work either It seems that once the guest has enabled the desktop something changes and the maximize/minimize/... actions are no more processed. Not sure were to debug next in regard to the gnome/wayland UI handling of this - any idea? P.S. We can reproduce this in git builds of qemu, so we can debug of modify the code as needed. The code for this is mostly in [1] [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c --- original report --- Running QEMU version 4.2.1 on Ubuntu 20.04 via qemu-system-x86_64 \ -boot d \ -cdrom ubuntu-22.04.1-desktop-amd64.iso \ -m 4096M \ -machine type=q35,accel=kvm \ -cpu host \ -smp 2 \ -device qxl-vga and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and adjusting the display resolution to match the native resolution, works as expected, i.e., the VM screen is correctly displayed in fullscreen. However, after running the same command for QEMU version 6.2.0 on Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution adjustment, yields a fullscreen view where the space occupied by the GNOME top bar (top panel with date in center) of the host is not used. The top bar itself is not visible but instead the purple background is shown where the top bar resides. The problem also occurs when replacing '-device qxl-vga' by '-device VGA,vgamem_mb=64'. The problem however does not occur when using '-device virtio-vga'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Cool! Thanks for testing :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: Fix Released Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Ok, i did find the issue -Thanks Security folks - and I'm issuing a security regression update. Thanks. ** Changed in: poppler (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: In Progress Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Hi, Could you please provide with any steps in how to reproduce it? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: New Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1738774]
Just to remember this bug was happening also at 100% scale as you can see on the Ckmment below with an screenshot: https://bugs.documentfoundation.org/show_bug.cgi?id=117158#c4 I cannot test anymore, because I switched back to MS Office. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+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 1988754] [NEW] libreoffice writer crashes when edit the page break
Public bug reported: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Description changed: - LibreOffice Writes crashes when editing the page break. It happens in - Xubuntu 22.04.1 and also in LinuxMint 21. + LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. + I have tried also using LibreOffice from ppa and it still crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1988754 Title: libreoffice writer crashes when edit the page break Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988754/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
I had this issue but it was a different reason, if you use the yubioath- desktop snap, all certificate readers are grabbed by that snap and pcscd cant see any devices. It doesnt matter if its just an YubiKey or a different device like a NitroKey. After killing yubioath-desktop and reinsert the smartcard, pcscd is able to claim the device. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1100326]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #7) > How does this compare to the portal service that was recently added for > Flatpak and so on? Do we really need both? Portal service is a limited API for Flatpak containers that internally forwards to Geoclue. Without Flatpak runtime that API is not available. In contrast to the portal provider this is a complete, native Geoclue API implementation on a state machine (for handling corner cases, etc.) for use in a standalone Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Confirmed Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1100326]
By the way, WebKitGTK got Geoclue2 support already. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Confirmed Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1100326]
Created attachment 9275622 Bug 1063572 - Geoclue2 geolocation provider. r=emilio Add a Geoclue (version 2) geolocation provider. This way Firefox can make use of multiple location sources present in the system, from GNSS provided by a cellular modem or the current network to location based on visible WiFi networks and 3G tower data, all while sharing them with other applications. This is a pure D-Bus-based implementation using a proper state machine, it does not require any additional dependencies. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Confirmed Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1964851] [NEW] Ubuntu 22.04 (dev-branch) shutdown/reboot hangs
Public bug reported: I have a desktop with MSI-Z690 motherboard and installed Dual boot Windows 11 on SSD and Ubuntu 22.04 dev-branch on HDD (upgraded from 20.04 LTS and this issue exists on 20.04 also) I choose Ubuntu at the first priority boot and Windows 11 is in Ubuntu bootloader. The Windows works fine. But when I power-off Ubuntu, it hangs, and I have to hold the power button for about 5 seconds to shut it down. I set grub to `GRUB_CMDLINE_LINUX_DEFAULT=""` and the last line of log is `reached target system power off` and it will stuck seems forever(I have once waited for 120 mins) By the way, I have another laptop and have a dual-boot on same SSD, everything works fine. So I am not sure if it is a HDD-related issue. How to set my Ubuntu to the really normal behavior? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 Uname: Linux 5.16.0-051600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 09:54:55 2022 InstallationDate: Installed on 2022-02-14 (28 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-02-27 (15 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1964851 Title: Ubuntu 22.04 (dev-branch) shutdown/reboot hangs Status in evince package in Ubuntu: New Bug description: I have a desktop with MSI-Z690 motherboard and installed Dual boot Windows 11 on SSD and Ubuntu 22.04 dev-branch on HDD (upgraded from 20.04 LTS and this issue exists on 20.04 also) I choose Ubuntu at the first priority boot and Windows 11 is in Ubuntu bootloader. The Windows works fine. But when I power-off Ubuntu, it hangs, and I have to hold the power button for about 5 seconds to shut it down. I set grub to `GRUB_CMDLINE_LINUX_DEFAULT=""` and the last line of log is `reached target system power off` and it will stuck seems forever(I have once waited for 120 mins) By the way, I have another laptop and have a dual-boot on same SSD, everything works fine. So I am not sure if it is a HDD-related issue. How to set my Ubuntu to the really normal behavior? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 Uname: Linux 5.16.0-051600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 09:54:55 2022 InstallationDate: Installed on 2022-02-14 (28 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-02-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1964851/+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 1961327] [NEW] Audio drops when switiching applications
Public bug reported: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". ➜ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - - ``` + ` ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - ``` + ` - ``` + ` apt-cache policy pulseaudio pulseaudio: - Installed: 1:15.0+dfsg1-1ubuntu2.2 - Candidate: 1:15.0+dfsg1-1ubuntu2.2 - Version table: - *** 1:15.0+dfsg1-1ubuntu2.2 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:15.0+dfsg1-1ubuntu2 500 - 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages - ``` + Installed: 1:15.0+dfsg1-1ubuntu2.2 + Candidate: 1:15.0+dfsg1-1ubuntu2.2 + Version table: + *** 1:15.0+dfsg1-1ubuntu2.2 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:15.0+dfsg1-1ubuntu2 500 + 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages + ` ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - ` + ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 ` - ` - apt-cache policy pulseaudio + + ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages - ` ** Description changed: The audio on my laptop drops when I open a new application (or switch to a different one). Sometimes it happens when switching tabs. It does not matter which application is playing audio, the audio usually stops when the application is switched. The typical workaround is to kill pulseaudio and start it again but that requires me to restart the application which is playing the audio. I found a better workaround which is to open PulseAudio Volume Control (pavucontrol) and toggle the profile from "Play HiFi quality music" -> "Off" -> "Play HiFi quality music". - ➜ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 - ` - ➜ apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 500 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to
[Desktop-packages] [Bug 1958435] Re: Icons on Dock get stuck in Dragging Mode
Though hardly an ideal solution, I can confirm that this bug is no longer present on 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+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 1958435] Re: Icons on Dock get stuck in Dragging Mode
Additional info: $ gsettings list-recursively org.gnome.shell org.gnome.shell enabled-extensions ['sound-output-device-choo...@kgshank.net'] org.gnome.shell command-history ['r'] org.gnome.shell remember-mount-password false org.gnome.shell always-show-log-out true org.gnome.shell had-bluetooth-devices-setup false org.gnome.shell looking-glass-history @as [] org.gnome.shell disable-user-extensions false org.gnome.shell app-picker-view uint32 0 org.gnome.shell disable-extension-version-validation true org.gnome.shell development-tools true org.gnome.shell enable-hot-corners false org.gnome.shell favorite-apps ['org.gnome.Terminal.desktop', 'firefox.desktop', 'discord.desktop', 'steam.desktop', 'spotify_spotify.desktop', 'org.remmina.Remmina.desktop', 'net.lutris.Lutris.desktop', 'gnome-control-center.desktop', 'org.gnome.Nautilus.desktop', 'signal-desktop.desktop', 'org.gnome.Screenshot.desktop'] org.gnome.shell.keyboard keyboard-type 'touch' org.gnome.shell.keybindings toggle-message-tray ['v', 'm'] org.gnome.shell.keybindings open-application-menu ['F10'] org.gnome.shell.keybindings pause-resume-tweens @as [] org.gnome.shell.keybindings toggle-application-view ['a'] org.gnome.shell.keybindings focus-active-notification ['n'] org.gnome.shell.keybindings toggle-overview ['s'] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+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 1958435] [NEW] Icons on Dock get stuck in Dragging Mode
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 - $ apt-cache policy gnome-shell-extension-ubuntu-dock + $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: - Installed: 0.9.1ubuntu18.04.3 - Candidate: 0.9.1ubuntu18.04.3 - Version table: - *** 0.9.1ubuntu18.04.3 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages - 100 /var/lib/dpkg/status - 0.9.1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages + Installed: 0.9.1ubuntu18.04.3 + Candidate: 0.9.1ubuntu18.04.3 + Version table: + *** 0.9.1ubuntu18.04.3 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages + 100 /var/lib/dpkg/status + 0.9.1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: - The icon gets stuck in dragging mode. When my mouse moves over the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. + The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all 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 SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode Status in
[Desktop-packages] [Bug 1880764] Re: Dragging icons frozen in place without finishing
Hello, I am affected by the same bug. The output of your command is the following: gsettings list-recursively org.gnome.shell org.gnome.shell enabled-extensions ['sound-output-device-choo...@kgshank.net'] org.gnome.shell command-history ['r'] org.gnome.shell remember-mount-password false org.gnome.shell always-show-log-out true org.gnome.shell had-bluetooth-devices-setup false org.gnome.shell looking-glass-history @as [] org.gnome.shell disable-user-extensions false org.gnome.shell app-picker-view uint32 0 org.gnome.shell disable-extension-version-validation true org.gnome.shell development-tools true org.gnome.shell enable-hot-corners false org.gnome.shell favorite-apps ['org.gnome.Terminal.desktop', 'firefox.desktop', 'discord.desktop', 'steam.desktop', 'spotify_spotify.desktop', 'org.remmina.Remmina.desktop', 'net.lutris.Lutris.desktop', 'gnome-control-center.desktop', 'org.gnome.Nautilus.desktop', 'signal-desktop.desktop', 'org.gnome.Screenshot.desktop'] org.gnome.shell.keyboard keyboard-type 'touch' org.gnome.shell.keybindings toggle-message-tray ['v', 'm'] org.gnome.shell.keybindings open-application-menu ['F10'] org.gnome.shell.keybindings pause-resume-tweens @as [] org.gnome.shell.keybindings toggle-application-view ['a'] org.gnome.shell.keybindings focus-active-notification ['n'] org.gnome.shell.keybindings toggle-overview ['s'] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1880764 Title: Dragging icons frozen in place without finishing Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: When I was dragging around the discord icon around, Gnome froze and the icon remained in place. This was happening when I was compiling gettext and it was using memory. However, even after the compilation stopped and the memory went down, Gnome keeps the icons in place, refusing to finish what it started. In this state, the Grid button on the bottom has no effect, and clicking on the icons have no effect, though they will update when a new program launches or closes, and if a new window opens. I expect the Gnome Shell to become responsive once the memory has gone down. It has enough memory to finish the animations; it just won't finish them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 26 17:24:53 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-07 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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-extension-ubuntu-dock/+bug/1880764/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Sure thing, working on it, till Tuesday it will be done as I need to test it and so for all releases. Thanks ** Changed in: exiv2 (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => Leonidas S. Barbosa (leosilvab) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1951685] Re: Chromium flatpak reliably crashes xdg-desktop-portal
This is indeed fixed at least in version 1.8.1-1~flatpak1~20.04 as installed from the official PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1951685 Title: Chromium flatpak reliably crashes xdg-desktop-portal Status in xdg-desktop-portal package in Ubuntu: New Bug description: For a while now I am facing the issue that Chromium installed via Flatpak after a minute or so stops working with a puzzling error ERR_NO_SUPPORTED_PROXIES. I guess this is due to the Proxy feature of the desktop portal because now I noticed that the portal is actually crashing shortly after I started Chromium and/or started browsing. According to the stack trace this happens in get_one_app_state so I think this bug was fixed in version 1.7.0 with this patch: https://github.com/flatpak/xdg-desktop- portal/commit/a0b641f1230016e8ed9a291c70d4dd226429dda4 Could that fix please be backported to 1.6.0/focal? PID: 15467 (xdg-desktop-por) UID: 1000 (xxx) GID: 1000 (xxx) Signal: 11 (SEGV) Timestamp: Sat 2021-11-20 16:55:00 CET (4min 23s ago) Command Line: /usr/libexec/xdg-desktop-portal Executable: /usr/libexec/xdg-desktop-portal Control Group: /user.slice/user-1000.slice/user@1000.service/xdg-desktop-portal.service Unit: user@1000.service User Unit: xdg-desktop-portal.service Slice: user-1000.slice Owner UID: 1000 (xxx) Boot ID: 1841d625a5354885a778e18a20b48103 Machine ID: 30e0f491ec7847428bc900251dc271af Hostname: xxx Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.1841d625a5354885a778e18a20b48103.15467.1637423700.lz4 Message: Process 15467 (xdg-desktop-por) of user 1000 dumped core. Stack trace of thread 15505: #0 0x7f5990c485f4 g_str_hash (libglib-2.0.so.0 + 0x405f4) #1 0x7f5990c4773c g_hash_table_lookup (libglib-2.0.so.0 + 0x3f73c) #2 0x5646137cf282 get_one_app_state (xdg-desktop-portal + 0x30282) #3 0x5646137cf778 background_monitor (xdg-desktop-portal + 0x30778) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15470: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f5990c5a4f1 n/a (libglib-2.0.so.0 + 0x524f1) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15475: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f598e5f099d n/a (libdconfsettings.so + 0xa99d) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15467: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x5646137bb7e8 main (xdg-desktop-portal + 0x1c7e8) #4 0x7f5990a1a0b3 __libc_start_main (libc.so.6 + 0x270b3) #5 0x5646137bb94e _start (xdg-desktop-portal + 0x1c94e) Stack trace of thread 15471: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x7f5990eaff8a n/a (libgio-2.0.so.0 + 0x11ef8a) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) xdg-desktop-portal: Installed: 1.6.0-1 Candidate:
[Desktop-packages] [Bug 1951685] [NEW] Chromium flatpak reliably crashes xdg-desktop-portal
Public bug reported: For a while now I am facing the issue that Chromium installed via Flatpak after a minute or so stops working with a puzzling error ERR_NO_SUPPORTED_PROXIES. I guess this is due to the Proxy feature of the desktop portal because now I noticed that the portal is actually crashing shortly after I started Chromium and/or started browsing. According to the stack trace this happens in get_one_app_state so I think this bug was fixed in version 1.7.0 with this patch: https://github.com/flatpak/xdg-desktop- portal/commit/a0b641f1230016e8ed9a291c70d4dd226429dda4 Could that fix please be backported to 1.6.0/focal? PID: 15467 (xdg-desktop-por) UID: 1000 (xxx) GID: 1000 (xxx) Signal: 11 (SEGV) Timestamp: Sat 2021-11-20 16:55:00 CET (4min 23s ago) Command Line: /usr/libexec/xdg-desktop-portal Executable: /usr/libexec/xdg-desktop-portal Control Group: /user.slice/user-1000.slice/user@1000.service/xdg-desktop-portal.service Unit: user@1000.service User Unit: xdg-desktop-portal.service Slice: user-1000.slice Owner UID: 1000 (xxx) Boot ID: 1841d625a5354885a778e18a20b48103 Machine ID: 30e0f491ec7847428bc900251dc271af Hostname: xxx Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.1841d625a5354885a778e18a20b48103.15467.1637423700.lz4 Message: Process 15467 (xdg-desktop-por) of user 1000 dumped core. Stack trace of thread 15505: #0 0x7f5990c485f4 g_str_hash (libglib-2.0.so.0 + 0x405f4) #1 0x7f5990c4773c g_hash_table_lookup (libglib-2.0.so.0 + 0x3f73c) #2 0x5646137cf282 get_one_app_state (xdg-desktop-portal + 0x30282) #3 0x5646137cf778 background_monitor (xdg-desktop-portal + 0x30778) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15470: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f5990c5a4f1 n/a (libglib-2.0.so.0 + 0x524f1) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15475: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f598e5f099d n/a (libdconfsettings.so + 0xa99d) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15467: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x5646137bb7e8 main (xdg-desktop-portal + 0x1c7e8) #4 0x7f5990a1a0b3 __libc_start_main (libc.so.6 + 0x270b3) #5 0x5646137bb94e _start (xdg-desktop-portal + 0x1c94e) Stack trace of thread 15471: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x7f5990eaff8a n/a (libgio-2.0.so.0 + 0x11ef8a) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) xdg-desktop-portal: Installed: 1.6.0-1 Candidate: 1.6.0-1 Version table: *** 1.6.0-1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Distributor ID: Neon Description:KDE neon User - Plasma 25th Anniversary Edition Release:20.04 Codename: focal ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu.
[Desktop-packages] [Bug 1100326]
I do have a Geoclue2 geolocation provider for gecko-dev right now and have been using it in Firefox for a few weeks now. This provider is purely (G)D-Bus based, so it doesn't need any additional external library as a dependency. I envision it as a system-wide geolocation source, much like the ones that Firefox already uses on Windows, Mac OS or Android platforms. Unfortunately, it's unlikely that I will be able to find enough time to go through a formal review process with this patch before this year winter holiday break. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Unknown Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1945899] Re: package libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1945899 Title: package libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_74_83_generic_81 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 26 12:17:16 2021 DpkgHistoryLog: Start-Date: 2021-09-26 12:16:42 Commandline: /usr/bin/unattended-upgrade Upgrade: gcc-10-base:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libitm1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libquadmath0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgcc1:amd64 (1:10.2.0-5ubuntu1~20.04, 1:10.3.0-1ubuntu1~20.04), libtsan0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libubsan1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgfortran5:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), liblsan0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgomp1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libgcc-s1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libatomic1:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libcc1-0:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04), libstdc++6:amd64 (10.2.0-5ubuntu1~20.04, 10.3.0-1ubuntu1~20.04) DuplicateSignature: package:libreoffice-help-common:1:6.4.7-0ubuntu0.20.04.1 Setting up libgomp1:amd64 (10.3.0-1ubuntu1~20.04) ... dpkg: error processing package libreoffice-help-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-09-05 (392 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to focal on 2020-10-10 (357 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1945899/+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 1949233] Re: Baloo File Extractor Closed Unexpectedly
** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1949233/+attachment/5537070/+files/acpidump.txt ** Information type changed from Private Security to Public -- 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/1949233 Title: Baloo File Extractor Closed Unexpectedly Status in xorg package in Ubuntu: New Bug description: Ballo File Extractor Closed Unexpectedly please report this error to help improve this software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 29 15:26:00 2021 DistUpgraded: 2021-01-08 14:56:49,798 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6310] [17aa:397f] InstallationDate: Installed on 2020-12-18 (315 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 2181 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=c44a1ac5-9dee-4bf8-a246-6303f68e5c24 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-01-08 (294 days ago) dmi.bios.date: 10/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G585 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G585 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:svnLENOVO:pn2181:pvrLenovoG585:rvnLENOVO:rnLenovoG585:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG585: dmi.product.family: IDEAPAD dmi.product.name: 2181 dmi.product.sku: LENOVO_MT_2181 dmi.product.version: Lenovo G585 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Oct 17 09:09:38 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1949233/+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 1949187] Re: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949187 Title: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: sometime system freezes ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: systemd-timesyncd:amd64: Configure systemd:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 29 16:00:03 2021 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:i386:1.16.2-4ubuntu0.1 Setting up libgstreamer1.0-0:i386 (1.16.2-2) ... Setcap worked! gst-ptp-helper is not suid! dpkg: error processing package libgstreamer-plugins-base1.0-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-10-28 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1949187/+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 1949303] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1949303 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: i don't no ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-38-generic Date: Sat Oct 30 21:28:43 2021 InstallationDate: Installed on 2021-05-09 (175 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1949303/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
This is also problematic for me. Has anyone had actual success with a fix? please Thanks. pulseAudio x ALC1220 = Unusable Condenser Microphone Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.10.68-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics ASUS x370 Crosshair Hero VI wifiac -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1764965/+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 1919255] Re: tracker-store crashed with signal 5
Same here on a fresh Hirsute install. There's a couple of suspect things in my syslog. Here is what happens right before the crash (anonymized): tracker-extract[2439]: bad character 'M' tracker-extract[2439]: bad character 'O' tracker-extract[2439]: bad character 'D' tracker-extract[2439]: bad character 'E' tracker-extract[2439]: bad character 'x' tracker-extract[2439]: bad character '/' tracker-extract[2439]: 59975: syntax error tracker-extract[2439]: bad character 'x' tracker-extract[2439]: message repeated 2 times: [ bad character 'x'] tracker-extract[2439]: libpng warning: iCCP: known incorrect sRGB profile tracker-extract[2439]: libpng warning: iCCP: known incorrect sRGB profile tracker-extract[2439]: message repeated 2 times: [ libpng warning: iCCP: known incorrect sRGB profile] tracker-store[2522]: SQLite error: database disk image is malformed (errno: Success) kernel: [ 408.547231] traps: pool-tracker-st[2527] trap int3 ip:7fd050c8d3a7 sp:7fd046f9c190 error:0 in libglib-2.0.so.0.6800.0[7fd050c4e000+8d000] tracker-store[2522]: SQLite experienced an error with file:'/home/[user]/.cache/tracker/meta.db'. It is either NOT a SQLite database or it is corrupt or there was an IO error accessing the data. This file has now been removed and will be recreated on the next start. Shutting down now. systemd[2429]: Starting Notification regarding a crash report... update-notifier-crash[6325]: /usr/bin/whoopsie systemd[2429]: update-notifier-crash.service: Succeeded. systemd[2429]: Finished Notification regarding a crash report. systemd[2429]: tracker-store.service: Main process exited, code=killed, status=5/TRAP systemd[2429]: tracker-store.service: Failed with result 'signal'. So this points either to some sort of malformed input (see the bad characters messages), something with libpng and/or something with sqlite. Hope this helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29458 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29457 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
A security update will be issue in next days to fix it on Ubuntu releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
issued* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
There are no CVEs for this issues so far. ** Changed in: exiv2 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] [NEW] out of buffer access and Integer overflow in Exiv2
Public bug reported: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases ** Affects: exiv2 (Ubuntu) Importance: Undecided Assignee: Leonidas S. Barbosa (leosilvab) Status: In Progress ** Changed in: exiv2 (Ubuntu) Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
This bug affects me too. Linux laptop 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04.2 LTS I think this bug may (at least in some cases) be related to this here question: https://askubuntu.com/questions/1234807/no-sound-after-sleep-ubuntu-20-04 . The solution they found involves removing the sound device and requesting a rescan: echo 1 > /sys/bus/pci/devices//remove echo 1 > /sys/bus/pci/rescan They automated this through a script such as this one: https://github.com/GHopperMSK/configs/blob/master/bin/restart-sound -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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
Re: [Desktop-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
I tried this but didn't work for me. But it could be because I didn't use the right patch.diff file. My patch.diff starts at: "--- a/src/gallium/drivers/i915/i915_screen.c" and ends at "switch (param)" from the patch link provided. After that, I just tried building " libgl1-mesa-dri" with: sudo apt-build install libgl1-mesa-dri This took a long time to complete, but doesn't fix the issue. I guess I will wait for the patch to be pushed into Ubuntu updates eventually. Any idea when that would be? Note: I can do "startx" from command line. However, the graphics login doesn't appear at startup because of segfault in gnome-session-check-accelerated-gl-helper. Thanks,Santosh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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
Re: [Desktop-packages] [Bug 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Sure. Thanks a lot. Looks like this has worked for Mark. So I will give this a try as well... Regards,Santosh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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
Re: [Desktop-packages] [Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Hi Mark,Where do I find the "patch.diff"? Thanks,Santosh- Sent from a web-browser based mail client! On Wednesday, February 24, 2021, 02:30:55 AM GMT+5:30, Mark Muth <1915...@bugs.launchpad.net> wrote: Now I can confirm, applying the patch mentioned above brings my PC back to normal. Short summary for everyone else who might read this bug report: Download and save patch as patch.diff and run: sudo apt-build install --patch patch.diff libgl1-mesa-dri -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1914147] Re: [upstream] Firefox 85 hangs at startup
FYI: this fix seems to work for me. Also, re "when": like the other reporter, this only started for me with the previous update (I think 85.0). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: [upstream] Firefox 85 hangs at startup Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+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 1914147] Re: [upstream] Firefox 85 hangs at startup
I have the same problem: after a security update last night on 20.04 LTS, firefox is now completely broken (displays a window frame with no content inside, ie it just copies the background image that was underneath on startup in the framebuffer?). firefox does work if I pass it a URL at startup. $ firefox --full-version Mozilla Firefox 85.0 20210118153634 20210118153634 cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" This is a critical bug for my main browser on the Ubuntu LTS channel!! Please fix ASAP!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: [upstream] Firefox 85 hangs at startup Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: In Progress Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+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 1912098] Re: Report a bug
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1912098 Title: Report a bug Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Bug description: Report a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1912098/+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
Re: [Desktop-packages] [Bug 1908500] Re: libxslt.a missing from libxslt1-dev
Mattia Rizzolo writes: > Could you please describe: > > * Which release you are basing this bug on? Buster > * Describe why you'd want the static library? My mistake, I had gotten confused while trying to fix a broken build with a libxslt dependency and thought I needed it. You can close this issue, apologies for wasting your time. ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1908500 Title: libxslt.a missing from libxslt1-dev Status in libxslt package in Ubuntu: Incomplete Bug description: The libxslt.a file is missing from 1.1.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1908500/+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 1909941] Re: xdg-email changes break simple-scan email functionality
I did tried in my focal VM with both xdg-utils and claws-mail and it worked here (see attached image). In claws it opened a gtk stuff, with settings steps and a window with the message to be composed and the attached file. Maybe someone else in this bug/thread has any idea what is happening. As the security update was already reverted I don't see any ways it can be security related with the sec update. ** Attachment added: "image.png" https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+attachment/5452350/+files/image.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+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 1909941] Re: xdg-email changes break simple-scan email functionality
hi @Dik, could you please provide the package, the release and version. Also, any steps in how to reproduce. In regarding xdg-utils the whole patch was reverted/delete, so I don't see how it can be related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+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 1909941] Re: xdg-email changes break simple-scan email functionality
https://ubuntu.com/security/notices/USN-4649-2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+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 1909941] Re: xdg-email changes break simple-scan email functionality
Hi, There are new version of this package in security-proposed [1] with the patch/update reverted, feel free to test it/check if the functionality is back. thanks [1]https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages?field.name_filter=xdg- utils_filter=published_filter= -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+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 1909941] Re: xdg-email changes break simple-scan email functionality
I'll revert that patch/update and issue a new one asap. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+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 1908500] [NEW] libxslt.a missing from libxslt1-dev
Public bug reported: The libxslt.a file is missing from 1.1.34 ** Affects: libxslt (Ubuntu) Importance: Undecided Status: New ** Summary changed: - libxslt.a missing from libxslt2-dev + libxslt.a missing from libxslt1-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxslt in Ubuntu. https://bugs.launchpad.net/bugs/1908500 Title: libxslt.a missing from libxslt1-dev Status in libxslt package in Ubuntu: New Bug description: The libxslt.a file is missing from 1.1.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1908500/+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 1904241] [NEW] Unable to recover forgotten archive folder password
Public bug reported: Hi Team Using Archive Manager i have compressed and password protected some folders in my system. Now, i have forgot the password. I am unable to find a way to recover the password and extract/open the folders. System Info: Description:Ubuntu 16.04.7 LTS Release:16.04 Archive Manager : 3.16.5 Please help me with the issue. Those folders contain the most important information in my life. I am literally dying to get those information. Please please help me with a solution. Thanking you in advance Thank and Regards, Nikhil ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1904241 Title: Unable to recover forgotten archive folder password Status in file-roller package in Ubuntu: New Bug description: Hi Team Using Archive Manager i have compressed and password protected some folders in my system. Now, i have forgot the password. I am unable to find a way to recover the password and extract/open the folders. System Info: Description: Ubuntu 16.04.7 LTS Release: 16.04 Archive Manager : 3.16.5 Please help me with the issue. Those folders contain the most important information in my life. I am literally dying to get those information. Please please help me with a solution. Thanking you in advance Thank and Regards, Nikhil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1904241/+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 1901533] [NEW] The computer is shutting down automatically.
Public bug reported: Sometimes the system does not boot. At other times the computer is shutting down automatically. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 26 17:17:50 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-122-generic, x86_64: installed v4l2loopback, 0.9.1, 4.10.0-28-generic, x86_64: installed v4l2loopback, 0.9.1, 4.15.0-122-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] InstallationDate: Installed on 2019-12-31 (300 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=8884ad19-c0c1-499c-99a6-9238419f6155 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd01/21/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Oct 26 17:11:56 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB Optical MouseMOUSE, id 8 inputCHICONY USB Keyboard KEYBOARD, id 9 inputCHICONY USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1176 vendor ACR xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1901533 Title: The computer is shutting down automatically. Status in xorg package in Ubuntu: New Bug description: Sometimes the system does not boot. At other times the computer is shutting down automatically. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 26 17:17:50 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-122-generic, x86_64: installed v4l2loopback, 0.9.1, 4.10.0-28-generic, x86_64: installed v4l2loopback, 0.9.1, 4.15.0-122-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical
[Desktop-packages] [Bug 1882402] Re: Ubuntu-drivers allows installation of (nvidia-340) drivers, which are broken/break things (Kubuntu 20.04)
Error on nvidia 340 install. Computer freezes while using Google Chrome. Chromium did not work at all. Kubuntu 20.10 Beta release with all updates. When trying to install 340 is below. Unpacking nvidia-opencl-icd-340 (340.108-0ubuntu5) ... Selecting previously unselected package screen-resolution-extra. Preparing to unpack .../7-screen-resolution-extra_0.18build1_all.deb ... Unpacking screen-resolution-extra (0.18build1) ... Selecting previously unselected package nvidia-settings. Preparing to unpack .../8-nvidia-settings_440.82-0ubuntu1_amd64.deb ... Unpacking nvidia-settings (440.82-0ubuntu1) ... Setting up nvidia-opencl-icd-340 (340.108-0ubuntu5) ... Setting up libxnvctrl0:amd64 (440.82-0ubuntu1) ... Setting up screen-resolution-extra (0.18build1) ... Setting up libc6-i386 (2.32-0ubuntu3) ... Setting up nvidia-settings (440.82-0ubuntu1) ... Setting up libcuda1-340 (340.108-0ubuntu5) ... Setting up lib32gcc-s1 (10.2.0-13ubuntu1) ... Setting up nvidia-340 (340.108-0ubuntu5) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Adding system user `nvidia-persistenced' (UID 126) ... Adding new group `nvidia-persistenced' (GID 136) ... Adding new user `nvidia-persistenced' (UID 126) with group `nvidia-persistenced' ... Not creating home directory `/'. Loading new nvidia-340-340.108 DKMS files... Building for 5.8.0-21-generic Building for architecture x86_64 Building initial module for 5.8.0-21-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-340.0.crash' Error! Bad return status for module build on kernel: 5.8.0-21-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of nvidia-340-dev: nvidia-340-dev depends on nvidia-340 (>= 340.108); however: Package nvidia-340 is not configured yet. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package nvi dia-340-dev (--configure): dependency problems - leaving unconfigured Processing triggers for desktop-file-utils (0.24-1ubuntu4) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-21-generic I: The initramfs will attempt to resume from /dev/sdc5 I: (UUID=1bd3ae7c-0d87-4e62-b5be-bcbdace82179) I: Set the RESUME variable to override this. Errors were encountered while processing:
[Desktop-packages] [Bug 1898456] [NEW] hp-plugin downloads plugins via insecure HTTP
Public bug reported: While looking what hp-plugin was doing when it was semmingly hung I noticed that it calls wget to download an executable via plain HTTP even though www.openprinting.org supports HTTPS: Relevant part from ps axf: 10353 pts/4Ss 0:00 | \_ /bin/bash 10492 pts/4Sl+0:07 | | \_ /usr/bin/python3 /usr/bin/hp-plugin 10507 pts/5Ss+0:00 | | \_ /usr/bin/wget --cache=off -P $HOME/.hplip http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.20.3-plugin.run Looks like there are two issues here: 1. Unless a local file exists, a plugin descriptor is downloaded from http://hplip.sf.net/plugin.conf 2. That one then contains the actual download URLs at www.openprinting.org which are plain HTTP as well The first one has checksums so theoretically it might be ok to download the latter via HTTP (though there is no reason to do so) but the checksums are downloaded via plain HTTP as well. ** Affects: hplip Importance: Undecided Status: New ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Summary changed: - hp-plugin downloads from openprinting.org via insecure HTTP from + hp-plugin downloads plugins via insecure HTTP ** Also affects: hplip Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1898456 Title: hp-plugin downloads plugins via insecure HTTP Status in HPLIP: New Status in hplip package in Ubuntu: New Bug description: While looking what hp-plugin was doing when it was semmingly hung I noticed that it calls wget to download an executable via plain HTTP even though www.openprinting.org supports HTTPS: Relevant part from ps axf: 10353 pts/4Ss 0:00 | \_ /bin/bash 10492 pts/4Sl+0:07 | | \_ /usr/bin/python3 /usr/bin/hp-plugin 10507 pts/5Ss+0:00 | | \_ /usr/bin/wget --cache=off -P $HOME/.hplip http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.20.3-plugin.run Looks like there are two issues here: 1. Unless a local file exists, a plugin descriptor is downloaded from http://hplip.sf.net/plugin.conf 2. That one then contains the actual download URLs at www.openprinting.org which are plain HTTP as well The first one has checksums so theoretically it might be ok to download the latter via HTTP (though there is no reason to do so) but the checksums are downloaded via plain HTTP as well. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1898456/+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 1866999] Re: gnome-calendar does not sync with Google Calendar
I've just updated from 18.04.5 to 20.04.1 and the calendar stopped working - none of my calendars are showing up. This seems to be another snap-related issue, as the apt installation (version 3.36.2) works fine. I tried removing and reinstalling the snap (version 3.30.0) but it didn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 1893813] Re: the super key is not working to show the overview of all running applications like before
** Information type changed from Private Security to Public -- 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/1893813 Title: the super key is not working to show the overview of all running applications like before Status in gnome-shell package in Ubuntu: New Bug description: my super key used to work before perfectly well on ubuntu but suddenly stopped showing me the recents .Althought if i press alt+ f1 i am getting it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 22:47:58 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-10 (327 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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/1893813/+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 1893569] Re: The mouse freezes
** Information type changed from Private Security to Public -- 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/1893569 Title: The mouse freezes Status in xorg package in Ubuntu: New Bug description: The mouse freezes in the middle of work. I connected others and the same thing happens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:44:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation HD Graphics 5500 [1179:f920] Subsystem: Toshiba Corporation Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1179:f923] InstallationDate: Installed on 2020-06-15 (76 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: TOSHIBA SATELLITE L50-B ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sr_RS SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8f2dae7e-98af-440c-adfc-c31f5c18bb4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTQE-00500DY4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.sku: INVALID dmi.product.version: PSKTQE-00500DY4 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893569/+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 1888086] Re: Fehler : Ubuntu 18.04.4 LTS
** Information type changed from Private Security to Public -- 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/1888086 Title: Fehler : Ubuntu 18.04.4 LTS Status in xorg package in Ubuntu: New Bug description: Fehler : Ubuntu 18.04.4 LTS Details Do you want to start the upgrade? 1 package is going to be removed To prevent data loss close all open applications and documents Details: Remove (1) systemd-shim-shim for systemd Could not install 'systemd-shim' The upgrade will continue but the 'systemd-shim' package may not be in a working state. Please consider submitting a bug report about it. installed systemd-shim package post-removal script subprocess returned error exit status 2 Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Upgrade complete The upgrade has completed but there were errors during the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jul 18 23:24:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-07-17 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2017 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-78LMT-USB3 R2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: sex dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 R2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jul 18 01:11:31 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888086/+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 1890011] Re: Could not install 'systemd-shim'
** Information type changed from Private Security to Public -- 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/1890011 Title: Could not install 'systemd-shim' Status in xorg package in Ubuntu: New Bug description: The upgrade will continue but the 'systemd-shim' package may not be in a working state. Please consider submitting a bug report about it. installed systemd-shim package post-removal script subprocess returned error exit status 2 Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Upgrade complete The upgrade has completed but there were errors during the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Aug 2 00:58:13 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-07-17 (15 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2017 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-78LMT-USB3 R2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: sex dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 R2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jul 18 01:11:31 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890011/+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 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 Nvidia 1080 with two 4K screens. After updating to 440 i only have lost fraction scaling, gnome settings only shows 100,200,300,400. The old experimental flag does not work (xorg). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Working on fully updated focal fossy Procedure to make bug happen: 1. open gnome control center and select screen (skærme in danish) 2. click the "fractional scaling" switch 3. select 150% scaling and click the green button at top right 4. Result is a blank screen and the monitor going into a power save state A reboot doesn't help. The login screen appears, when I log in the screen goes blank again and the monitor power save kicks in. If I select the "unity" environment, the display does work. If I do this on the command line "gsettings set org.gnome.mutter experimental-features ['']", I can log in as usual and fractional scaling has been turned off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 12:11:39 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+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 1886412] Re: $ ubuntu-bug xorg
** Information type changed from Private Security to Public -- 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/1886412 Title: $ ubuntu-bug xorg Status in xorg package in Ubuntu: New Bug description: I cannot open system settings so I can set up a sleep mode after leaving offfor a spell. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jul 6 11:57:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2837 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 3 12:16:20 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1886412/+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 1825963] Re: Abysmal memory leak on tracker-extract
I get the same error as Alex, but for TGA files: ``` tracker-extract[13828]: Call to gst_discoverer_discover_uri(file://[...]/Ale_col.tga) failed: Internal data stream error. ``` The error only occurs with certain TGAs, I shall attaching one below. My current workaround is to add '*.tga' to "/org/freedesktop/tracker/miner/files/ignored-files" in `dconf-editor`. SYSTEM: ``` #lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 #apt-cache policy tracker* tracker-extract: Installed: 2.3.3-2 Candidate: 2.3.3-2 tracker-miner-fs: Installed: 2.3.3-2 Candidate: 2.3.3-2 tracker: Installed: 2.3.4-1 Candidate: 2.3.4-1 ``` ** Attachment added: "Ale_col.tga" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+attachment/5389438/+files/Ale_col.tga -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1885337] [NEW] LibreOffice Writer selects inappropriate font when Traditional Chinese text is pasted on system that also has TexLive installed
Public bug reported: LibreOffice 6.0.7 on Ubuntu 18.04, with English (UK) locales selected and running LXDE, reacts to paragraphs of Traditional Chinese text being pasted into LibreOffice Writer by searching the system for a Chinese font and selecting it for the pasted Chinese text. Unfortunately, if the package "texlive-full" is installed on the system (which includes texlive-lang-chinese), then the first Chinese font LibreOffice encounters will be "AR PL SungtiL GB" from the fonts-arphic-gbsn00lp package. This font includes only a subset of Chinese characters (it is a "Simplified Chinese only" font), and if the text being pasted is Traditional Chinese then it will almost certainly contain other characters not present in the "AR PL SungtiL GB" font. In this case a font-fallback system selects a different font for just some of the characters. If the font it falls back on happens to be "AR PL MingtiL" then all is well, since those two fonts are designed to complement each other stylistically. But our system had the "fonts-wqy-microhei" package installed too (which was needed for WINE to run a Chinese CD-ROM that couldn't use the Arphic fonts), and unfortunately the text pasted into LibreOffice ended up using this "WenQuanYi Micro Hei" font as a fallback for any character not present in the Simplified Chinese set, whereas those characters that are present in the Simplified Chinese set get the Arphic font. The end result is a paragraph of Chinese text that keeps changing font every other word, and although the user was putting up with it, her printouts were looking decidedly sloppy and were apparently causing others to think Linux is an inferior system because its Chinese printouts are so bad. Since this particular user is unlikely to write old-style CJK-LaTeX, I worked around the problem by removing the Arphic font packages from her laptop (she can still use the rest of LaTeX, which is enough for her most likely use-case of typesetting English scientific papers), so her LibreOffice now finds the WenQuanYi font first, and that one supports all Chinese characters (both Simplified and Traditional) so her Chinese printouts now look much better (regardless of which type of Chinese is being printed today). Another workaround would be to ensure the user knows how to override LibreOffice's choice of font after any Chinese text is pasted into a LibreOffice document, but this is a chore that would have to be remembered every time. I did try to find a configuration option in LibreOffice to set it by default, but I was unable to find one that worked (it does not work to override "Tools / Options / LibreOffice Writer / Basic fonts", since these are not what gets applied when Chinese text is pasted; it does not work to edit the default style via Styles / Edit; there is nothing in Options about default Chinese font). So I think we either need to make a feature request to LibreOffice to implement a "default Chinese font" option (or "default font by language"), or put some kind of special-case code into LibreOffice that causes it to treat the Arphic fonts as lowest priority even though they are listed under "A", or else address the font fallback system (if LibreOffice is selecting Arphic Simplified because it's listed under "A" then I'm not sure why the fallback system is not selecting Arphic Traditional which is also listed under "A" but instead goes to a font listed under "W"; either they're being arranged in some non-alphabetical order or two different font-selection systems with different logic are at play). I don't know if there's some way for the package maintainers to kludge things so that Arphic is given lower priority by LibreOffice. Or perhaps there is some other solution? ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1885337 Title: LibreOffice Writer selects inappropriate font when Traditional Chinese text is pasted on system that also has TexLive installed Status in libreoffice package in Ubuntu: New Bug description: LibreOffice 6.0.7 on Ubuntu 18.04, with English (UK) locales selected and running LXDE, reacts to paragraphs of Traditional Chinese text being pasted into LibreOffice Writer by searching the system for a Chinese font and selecting it for the pasted Chinese text. Unfortunately, if the package "texlive-full" is installed on the system (which includes texlive-lang-chinese), then the first Chinese font LibreOffice encounters will be "AR PL SungtiL GB" from the fonts- arphic-gbsn00lp package. This font includes only a subset of Chinese characters (it is a "Simplified Chinese only" font), and if the text being pasted is Traditional Chinese then it will almost certainly contain other characters not present in the "AR PL SungtiL GB" font. In this case a
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
This affects me too, external monitors only work when using the Nvidia card exclusively on my laptop, so fractional scaling is a must, but it just flickers and selects 200% instead. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1876704] Re: 20.04 usb printing problem HP Envy 5640
*** This bug is a duplicate of bug 1875796 *** https://bugs.launchpad.net/bugs/1875796 ** This bug has been marked a duplicate of bug 1875796 HP Envy 5530 printer/scanner does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1876704 Title: 20.04 usb printing problem HP Envy 5640 Status in cups package in Ubuntu: Confirmed Bug description: USB printing worked fine with 18.04. After upgrade to 20.04 printer appears multiple times. Some data in this thread: NOT solved for USB: https://ubuntuforums.org/showthread.php?t=2442142 https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_printer Just noticed this in syslog while following debugging thread: May 4 12:23:46 gja-desktop root: loading HP Device 002 012 May 4 12:23:47 gja-desktop python3: io/hpmud/musb.c 2189: [7538] hpmud_make_usb_uri() bus=002 dev=012 May 4 12:23:47 gja-desktop python3: io/hpmud/musb.c 2287: hpmud_make_usb_uri() uri=hp:/usb/ENVY_5640_series?serial=TH66P9W21D05ZC bytes_read=46 May 4 12:23:47 gja-desktop systemd[1]: Starting Daemon to make IPP-over-USB printers available as network printers (002:012)... May 4 12:23:47 gja-desktop systemd[1]: Started Daemon to make IPP-over-USB printers available as network printers (002:012). May 4 12:23:53 gja-desktop colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied There seems to be a permission error. Thanks for looking into this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [04/May/2020:12:15:32 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'ENVY-5640-Gray..\' already exists W [04/May/2020:12:15:32 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'ENVY-5640-RGB..\' already exists E [04/May/2020:12:18:00 +0200] [Job 51] Job held by \"gja\". E [04/May/2020:12:18:01 +0200] [Job 52] Job held by \"gja\". E [04/May/2020:12:23:07 +0200] [Job 51] Stopping unresponsive job. CurrentDesktop: ubuntu:GNOME Date: Mon May 4 12:26:02 2020 InstallationDate: Installed on 2020-02-22 (72 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lpstat: device for ENVY-5640: hp:/usb/ENVY_5640_series?serial=TH66P9W21D05ZC MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ENVY-5640.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ENVY-5640.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=7d1dd584-c6b2-4d9c-b32c-8e58889d3049 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-04-25 (8 days ago) dmi.bios.date: 10/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: FM2A85X Extreme4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/19/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A85XExtreme4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1876704/+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 1875796] Re: HP Envy 5530 printer/scanner does not work
Try workaround: sudo apt purge ippusbxd Source: Kellerkind_2009, https://forum.ubuntuusers.de/post/9151988/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1875796 Title: HP Envy 5530 printer/scanner does not work Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 20.04 LTS see troubleshoot.txt please ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 08:15:00 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for ENVY_5530_series_CN4A5310HJ067B_: implicitclass://ENVY_5530_series_CN4A5310HJ067B_/ device for HP-ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-ENVY-5530-series.ppd', '/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+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 1880961] [NEW] Deja dup allow multiple backup locations, destination and schedules.
Public bug reported: If someone wants to save their external hard drive to AWS and their main SSD to google drive, currently (to my knowlage) this is impossible. With the ability to choose multiple Backups a lot of extra utility would be possible. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: wishlist ** Description changed: If someone wants to save their external hard drive to AWS and their main SSD to google drive, currently (to my knowlage) this is impossible. With - the ability to choose multiple Backups. + the ability to choose multiple Backups a lot of extra utility would be + possible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1880961 Title: Deja dup allow multiple backup locations, destination and schedules. Status in deja-dup package in Ubuntu: New Bug description: If someone wants to save their external hard drive to AWS and their main SSD to google drive, currently (to my knowlage) this is impossible. With the ability to choose multiple Backups a lot of extra utility would be possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1880961/+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 1879010] [NEW] Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink
Public bug reported: This seems identical to this bug: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was suggested to open a new bug as the other one was closed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 16:13:24 2020 InstallationDate: Installed on 2020-05-06 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9300 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.4.0-29-generic root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 54:8D:5A:D8:BA:43 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1126282 acl:178 sco:0 events:156624 errors:0 TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1879010 Title: Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink Status in bluez package in Ubuntu: New Bug description: This seems identical to this bug: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was suggested to open a new bug as the other one was closed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 16:13:24 2020 InstallationDate: Installed on 2020-05-06 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9300 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.4.0-29-generic root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 54:8D:5A:D8:BA:43 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1126282 acl:178 sco:0 events:156624 errors:0 TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879010/+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 1876905] Re: package chromium-browser (not installed) failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1876905 Title: package chromium-browser (not installed) failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status de saída 1 Status in chromium-browser package in Ubuntu: New Bug description: Não installação ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 5 08:16:21 2020 ErrorMessage: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1876905/+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 1876642] Re: Firefox Dark
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1876642 Title: Firefox Dark Status in firefox package in Ubuntu: New Bug description: When I lock the screen, Firefox goes dark like a modal window appears and everything else goes dark. This does not block the functionality of the application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yerzinperez 2626 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 3 19:39:05 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-03-31 (33 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.9 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profiles: Profile3 - LastVersion=76.0/20200407205853 (Out of date) Profile1 (Default) - LastVersion=75.0/20200403170909 Profile0 - LastVersion=75.0/20200403170909 (In use) Profile2 - LastVersion=75.0/20200403064004 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-04-24 (9 days ago) dmi.bios.date: 05/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X507UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X507UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX507UF.304:bd05/22/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX507UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX507UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook
[Desktop-packages] [Bug 1875800] [NEW] Cannot choose which display dock shows on
Public bug reported: I have two monitors both connected to one graphics card. Dock is showing on both of them. I would like it to show only on the right side of the left monitor. I go to "Settings > Appearance > Dock > Show on". I select the left monitor from the menu. I expect the dock to disappear from the right monitor and show on the left. Instead the dock stays on both monitors. To be spesific what seems to happen is that selecting other option, eg. AOC 27", from the menu makes the dock flash but the selection goes to "All displays". Then if I select AOC 27" again the selection goes to that but now the dock doesn't flash and it stays on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 09:31:59 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1875800 Title: Cannot choose which display dock shows on Status in gnome-control-center package in Ubuntu: New Bug description: I have two monitors both connected to one graphics card. Dock is showing on both of them. I would like it to show only on the right side of the left monitor. I go to "Settings > Appearance > Dock > Show on". I select the left monitor from the menu. I expect the dock to disappear from the right monitor and show on the left. Instead the dock stays on both monitors. To be spesific what seems to happen is that selecting other option, eg. AOC 27", from the menu makes the dock flash but the selection goes to "All displays". Then if I select AOC 27" again the selection goes to that but now the dock doesn't flash and it stays on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 09:31:59 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1875800/+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 1870726] Re: Ubuntu Login Screen Loop
** Description changed: * Ubuntu Focal Fossa 20.04 (dev) * xorg: - Installed: 1:7.7+19ubuntu14 - Candidate: 1:7.7+19ubuntu1 + Installed: 1:7.7+19ubuntu14 + Candidate: 1:7.7+19ubuntu1 + * VirtualBox version : 5.2.34_Ubuntu r133883 (installed via apt) Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. - Steps to reproduce : + Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=d609fc71-9cba-4875-8bc1-795cb584a629 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1870726 Title: Ubuntu Login Screen Loop Status in xorg package in Ubuntu: New Bug description: * Ubuntu Focal Fossa 20.04 (dev) * xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu1 * VirtualBox version : 5.2.34_Ubuntu r133883 (installed via apt) Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
[Desktop-packages] [Bug 1870726] [NEW] Ubuntu Login Screen Loop
Public bug reported: * Ubuntu Focal Fossa 20.04 (dev) * xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu1 Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=d609fc71-9cba-4875-8bc1-795cb584a629 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session ** Attachment added: "The video showing what actually happens." https://bugs.launchpad.net/bugs/1870726/+attachment/5345984/+files/AayrBV8M.mp4 -- 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/1870726 Title: Ubuntu Login Screen Loop Status in xorg package in Ubuntu: New Bug description: * Ubuntu Focal Fossa 20.04 (dev) * xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu1 Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic
[Desktop-packages] [Bug 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
A viable work around seems to be increasing shared memory via the sysctl.conf file and opening a small (?KB) image before opening a larger (?MB) image. This does cause a noticable system lag when the mouse cursor passes over the rendered image window. add the following line: kernel.shmmax = 1073741824 then execute: sudo sysctl -p ... This solution does NOT always work if a small image has not first been opened. Looking through the source code, it appears the cairo routines find exhausted shared memory pool and return a NULL ptr. Why opening a small image first seems to help? I have no idea. Version 3.18.1 on 16.04 LTS does not have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. Status in eog package in Ubuntu: Confirmed Bug description: I opened an image. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 16:22:00 2019 ExecutablePath: /usr/bin/eog ExecutableTimestamp: 1523677004 InstallationDate: Installed on 2017-03-13 (874 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: eog /home/mircea/Downloads/IMG_20190410_143513.jpg ProcCwd: /home/mircea Signal: 6 SourcePackage: eog StacktraceTop: __assert_fail_base (fmt=0x7fac8c9d47d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fac8c0ce9a9 "*ptr != NULL", file=file@entry=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=line@entry=619, function=function@entry=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:92 __GI___assert_fail (assertion=0x7fac8c0ce9a9 "*ptr != NULL", file=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=619, function=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. UpgradeStatus: Upgraded to bionic on 2018-08-24 (345 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+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 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
This bug is not duplicate, or the 'duplicate' is private. Please address. ** This bug is no longer a duplicate of private bug 1671487 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. Status in eog package in Ubuntu: Confirmed Bug description: I opened an image. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 16:22:00 2019 ExecutablePath: /usr/bin/eog ExecutableTimestamp: 1523677004 InstallationDate: Installed on 2017-03-13 (874 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: eog /home/mircea/Downloads/IMG_20190410_143513.jpg ProcCwd: /home/mircea Signal: 6 SourcePackage: eog StacktraceTop: __assert_fail_base (fmt=0x7fac8c9d47d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fac8c0ce9a9 "*ptr != NULL", file=file@entry=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=line@entry=619, function=function@entry=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:92 __GI___assert_fail (assertion=0x7fac8c0ce9a9 "*ptr != NULL", file=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=619, function=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. UpgradeStatus: Upgraded to bionic on 2018-08-24 (345 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+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 1590661] Re: Unable to unlock: "Time has expired"
Same thing here ubuntu budgie 19.10 gnome 3.34.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1590661 Title: Unable to unlock: "Time has expired" Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Sometimes when coming back after locking the screen I am unable to unlock. The login box on the screen has a disabled password input field with the buttons also disabled. Except for the mouse, the entire screen is frozen. Even the time in the top of the screen stops going. The only way to continue is to move to a tty (Ctrl-Alt-F1), log in and kill gnome-screensaver. Since the time also stops going I have deduced that this seems to happen on days and times that correspond to when the cleaners are here. Because of this I speculate that they accidentally press some keys, including the enter key. This of course fails to unlock and after a certain timeout it then proceeds to freeze. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 9 08:59:15 2016 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2016-05-27 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1590661/+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 1860946] [NEW] Error or every boot
Public bug reported: Delay in response infrequent interrution ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Mon Jan 27 07:28:37 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-72-generic, x86_64: installed anbox, 1, 4.15.0-74-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fa31] InstallationDate: Installed on 2018-08-27 (517 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: TOSHIBA Satellite C50-A ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=02250975-d476-48ef-9a7d-22dbbe5e4c15 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PT10F dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd11/08/2013:svnTOSHIBA:pnSatelliteC50-A:pvrPSCG8G-05500G:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite C50-A dmi.product.version: PSCG8G-05500G dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Aug 28 09:45:06 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1860946 Title: Error or every boot Status in xorg package in Ubuntu: New Bug description: Delay in response infrequent interrution ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Mon Jan 27 07:28:37 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-72-generic, x86_64: installed anbox, 1, 4.15.0-74-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fa31] InstallationDate: Installed on 2018-08-27 (517 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: TOSHIBA Satellite C50-A ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=02250975-d476-48ef-9a7d-22dbbe5e4c15 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PT10F dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd11/08/2013:svnTOSHIBA:pnSatelliteC50-A:pvrPSCG8G-05500G:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
After enabling proposed, did sudo apt install pulseaudio pulseaudio-module-bluetooth pulseaudio-utils to update only present packages related to pulseaudio Can confirm the issue is now fixed for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1647285] Re: SSL trust not system-wide
Like others, I'm manually symlinking .so files on all of my interactive hosts and hoping updates don't break it. IMO this is not a valid workaround. @ahasenack - I understand this is a roadmap item that would ideally resolve for multiple packages, but it seems that the Mozilla products are the worst offenders at the moment. I don't see anyone requesting anything else in this bug. Would it be possible to at least resolve it for Firefox and Thunderbird? What would it take to get this looked at for the next LTS? For now, Thunderbird needs this too (and works for me on 18.0.3 LTS): sudo mv /usr/lib/firefox/libnssckbi.so /usr/lib/firefox/libnssckbi.so.bak sudo ln -s /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/firefox/libnssckbi.so sudo mv /usr/lib/thunderbird/libnssckbi.so /usr/lib/thunderbird/libnssckbi.so.bak sudo ln -s /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/thunderbird/libnssckbi.so -- 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/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1857749] Re: HDMI output always selected on reboot
** Attachment added: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857749/+attachment/5315999/+files/default.pa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1857749 Title: HDMI output always selected on reboot Status in pulseaudio package in Ubuntu: New Bug description: Setting default output via "pactl set-default-sink 2" or editing "/etc/pulse/default.pa" does not help. The only work around that helps is to not load "module-switch-on-connect" (as in uploaded "/etc/pulse/default.pa") It seems that HDMI output is seen by the system as connected later than Line Out, so it switches to it on every reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svobonas 1693 F pulseaudio /dev/snd/controlC1: svobonas 1693 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 11:14:19 2019 InstallationDate: Installed on 2019-10-12 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-28T10:52:04.652956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857749/+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 1857749] [NEW] HDMI output always selected on reboot
Public bug reported: Setting default output via "pactl set-default-sink 2" or editing "/etc/pulse/default.pa" does not help. The only work around that helps is to not load "module-switch-on-connect" (as in uploaded "/etc/pulse/default.pa") It seems that HDMI output is seen by the system as connected later than Line Out, so it switches to it on every reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svobonas 1693 F pulseaudio /dev/snd/controlC1: svobonas 1693 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 11:14:19 2019 InstallationDate: Installed on 2019-10-12 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-28T10:52:04.652956 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1857749 Title: HDMI output always selected on reboot Status in pulseaudio package in Ubuntu: New Bug description: Setting default output via "pactl set-default-sink 2" or editing "/etc/pulse/default.pa" does not help. The only work around that helps is to not load "module-switch-on-connect" (as in uploaded "/etc/pulse/default.pa") It seems that HDMI output is seen by the system as connected later than Line Out, so it switches to it on every reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: svobonas 1693 F pulseaudio /dev/snd/controlC1: svobonas 1693 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 28 11:14:19 2019 InstallationDate: Installed on 2019-10-12 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/14/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-28T10:52:04.652956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857749/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
dmesg output attached from #21, step 2) ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305171/+files/dmesg.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Hi, 1) Steps: - Removed the option model= - Rebooted - turned off Secure Boot and booted with your test kernel. Result: No sound from speakers. Very very quiet headphones. 2) Steps: sudo set-coeff.sh sudo su echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef Result: No sound from speakers. Very very quiet headphones. alsa-info is attached. Thanks, Martin ** Attachment added: "alsa-info-with-coefficients-after-set-coeff.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305170/+files/alsa-info-with-coefficients-after-set-coeff.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Install the testing kernel and reboot, <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Couldn't boot after installing all 3 .deb's: error: /boot/vmlinuz-5.3.0.23.25+samsung-test-generic has invalid signature error: you need to load the kernel first Press any key to continue... -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F p
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Attachment to #17 was incorrect (forgot to turn on coefficients) Attached is alsa-info with coefficients. ** Attachment added: "alsa-info-dell-headset3-with-coefficients.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304921/+files/alsa-info-dell-headset3-with-coefficients.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ub
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> nd If you have time, please redo the test of #10, after finishing all commands, please generate an alsa-info.txt-with-coeff, let us check if all those commands successfully executed. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Option: dell-headset3 Headphone works, and does not seem to change when any of the below settings are applied. alsa-info output attached; it was generated after the last command in the sequence. martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e nid = 0x20, verb = 0x500, param = 0x8e value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20 nid = 0x20, verb = 0x400, param = 0x20 value = 0x0 >>>>>>>> NO change martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19 nid = 0x20, verb = 0x500, param = 0x19 value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317 nid = 0x20, verb = 0x400, param = 0x317 value = 0x0 >>>>>>>> NO change martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67 nid = 0x20, verb = 0x500, param = 0x67 value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110 nid = 0x20, verb = 0x400, param = 0x1110 value = 0x0 >>>>>>>> NO change martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f nid = 0x20, verb = 0x500, param = 0x4f value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429 nid = 0x20, verb = 0x400, param = 0xc429 value = 0x0 >>>>>>>> NO change Thanks, Martin ** Attachment added: "alsa-info-dell-headset3-with-coefficients.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304920/+files/alsa-info-dell-headset3-with-coefficients.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, dat
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
>>>>>>>>>>>>>>>>>>>>> please verify that both speaker and headphone work well under windows, then using this tool to collect a log under windows, the log is a useful reference for linux. <<<<<<<<<<<<<<<<<<<<< Output attached; looks like this might be helpful to get the speakers to work. Thank you, Martin ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304916/+files/RtHDDump.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
<<<<<<<<<<<<<<<<<<< Ah, please test model=dell-headset3, it should work. And please also add options snd-hda-codec-realtek dyndbg, then boot the system without the headphone plugged. after boot up, plug headphone, and test if it works well. If it works well, please upload the dmesg. >>>>>>>>>>>>>>>>>>>> Yes, headphones work well. dmesg output is attached. Thank you. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304905/+files/dmesg.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
FYI: I just re-tested with model=mono-speakers, and there the headhpone output likewise does not change for any of the above settings: it works great the entire time. Thanks, Martin -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_R
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Hi, I was surprised, but none of these settings helped. Mode was set originally to options snd-hda-intel model=headset-mode-no-hp-mic sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20 //check if headphone can output sound normally? Running speaker-test: very very quiet sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317 //check if headphone can output sound normally? same result sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110 //check if headphone can output sound normally? same result sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429 //check if headphone can output sound normally? same result -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, chann
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Using options snd-hda-intel model=headset-mode-no-hp-mic Result: Headphones: very very quiet Internal speakers: Nothing Alsa-info is attached. Thank you. ** Attachment added: "alsa-info-with-coefficients-headset-mode-no-hp-mic.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304381/+files/alsa-info-with-coefficients-headset-mode-no-hp-mic.txt -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Instal
