[Desktop-packages] [Bug 1834264] Re: PCI/internal sound card not detected
I need to go to sleep now. I hope this sheds some light on the problem. I'm going to test the bluetooth audio tomorrow and see if that works. That may prove to be an adequate alternative if it does. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
[0.00] microcode: microcode updated early to revision 0xb4, date = 2019-04-01 [0.00] Linux version 5.2.0-050200rc6-generic (kernel@gloin) (gcc version 8.3.0 (Ubuntu 8.3.0-14ubuntu1)) #201906222033 SMP Sun Jun 23 00:36:46 UTC 2019 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200rc6-generic root=UUID=65e93403-63ae-4cca-81cd-2c9ce6230a12 ro quiet splash vt.handoff=1 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x00057fff] usable [0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved [0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x722aefff] usable [0.00] BIOS-e820: [mem 0x722af000-0x722a] ACPI NVS [0.00] BIOS-e820: [mem 0x722b-0x722b0fff] reserved [0.00] BIOS-e820: [mem 0x722b1000-0x89d9dfff] usable [0.00] BIOS-e820: [mem 0x89d9e000-0x89f9dfff] type 20 [0.00] BIOS-e820: [mem 0x89f9e000-0x8a78dfff] reserved [0.00] BIOS-e820: [mem 0x8a78e000-0x8ae7dfff] ACPI NVS [0.00] BIOS-e820: [mem 0x8ae7e000-0x8aefdfff] ACPI data [0.00] BIOS-e820: [mem 0x8aefe000-0x8aefefff] usable [0.00] BIOS-e820: [mem 0x8aeff000-0x8fff] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfd00-0xfe7f] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xffa0-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00036eff] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.50 by INSYDE Corp. [0.00] efi: ACPI 2.0=0x8aefd014 SMBIOS=0x89fd9000 SMBIOS 3.0=0x89fd7000 ESRT=0x89fd4158 PROP=0x722ab858 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: HP HP Pavilion Laptop 15-cc0xx/8364, BIOS F.14 02/23/2018 [0.00] tsc: Detected 2900.000 MHz processor [0.001044] tsc: Detected 2904.000 MHz TSC [0.001044] e820: update [mem 0x-0x0fff] usable ==> reserved [0.001046] e820: remove [mem 0x000a-0x000f] usable [0.001050] last_pfn = 0x36f000 max_arch_pfn = 0x4 [0.001055] MTRR default type: write-back [0.001056] MTRR fixed ranges enabled: [0.001056] 0-9 write-back [0.001057] A-B uncachable [0.001058] C-F write-protect [0.001058] MTRR variable ranges enabled: [0.001059] 0 base 00C000 mask 7FC000 uncachable [0.001060] 1 base 00A000 mask 7FE000 uncachable [0.001060] 2 base 009000 mask 7FF000 uncachable [0.001061] 3 base 008C00 mask 7FFC00 uncachable [0.001061] 4 base 008B80 mask 7FFF80 uncachable [0.001061] 5 disabled [0.001062] 6 disabled [0.001062] 7 disabled [0.001062] 8 disabled [0.001063] 9 disabled [0.001965] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.002147] last_pfn = 0x8aeff max_arch_pfn = 0x4 [0.008216] esrt: Reserving ESRT space from 0x89fd4158 to 0x89fd4190. [0.008221] check: Scanning 1 areas for low memory corruption [0.008225] Using GB pages for direct mapping [0.008226] BRK [0x14d801000, 0x14d801fff] PGTABLE [0.008227] BRK [0x14d802000, 0x14d802fff] PGTABLE [0.008228] BRK [0x14d803000, 0x14d803fff] PGTABLE [0.008250] BRK
[Desktop-packages] [Bug 1834264] Re: PCI/internal sound card not detected
please upload the dmesg dmesg > /tmp/dmesg.txt upload the 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
Installed them, but still get Dummy Output. uname -a Linux adam-HP-Pavilion-Laptop-15-cc0xx 5.2.0-050200rc6-generic #201906222033 SMP Sun Jun 23 00:36:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
Whoops, I needed to install the second one first. Getting ready to reboot. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
sudo dpkg -i linux-image-unsigned-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb [sudo] password for adam: Selecting previously unselected package linux-image-unsigned-5.2.0-050200rc6-generic. (Reading database ... 239411 files and directories currently installed.) Preparing to unpack linux-image-unsigned-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb ... Unpacking linux-image-unsigned-5.2.0-050200rc6-generic (5.2.0-050200rc6.201906222033) ... dpkg: dependency problems prevent configuration of linux-image-unsigned-5.2.0-050200rc6-generic: linux-image-unsigned-5.2.0-050200rc6-generic depends on linux-modules-5.2.0-050200rc6-generic; however: Package linux-modules-5.2.0-050200rc6-generic is not installed. dpkg: error processing package linux-image-unsigned-5.2.0-050200rc6-generic (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-unsigned-5.2.0-050200rc6-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
Yes, the driver is loaded correctly, but it fails during initialization. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
download linux-image- unsigned-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb and linux- modules-5.2.0-050200rc6-generic_5.2.0-050200rc6.201906222033_amd64.deb Then install them by: sudo dpkg -i $files_name.deb after that, reboot and run uname -a to check if the kernel is 5.2.0 and check if sound works or not -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
Is the correct driver installed? lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) Subsystem: Hewlett-Packard Company Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [103c:8364] 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8364] Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 02) Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [103c:8364] Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP USB 3.0 xHCI Controller [103c:8364] Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP Thermal subsystem [103c:8364] Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP CSME HECI [103c:8364] Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP SATA Controller [AHCI mode] [103c:8364] Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1) Kernel driver in use: pcieport 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1) Kernel driver in use: pcieport 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) Kernel driver in use: pcieport 00:1d.3 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1) Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E [8086:9d4e] (rev 21) Subsystem: Hewlett-Packard Company Device [103c:8364] 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP PMC [103c:8364] 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP HD Audio [103c:8364] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP SMBus [103c:8364] Kernel modules: i2c_i801 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01) Subsystem: Hewlett-Packard Company RTS522A PCI Express Card Reader [103c:8364] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [103c:8364] Kernel driver in use: r8169 Kernel modules: r8169 05:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug
[Desktop-packages] [Bug 1834264] Re: PCI/internal sound card not detected
I tried the install disc in live user mode. I did not want to overwrite all my files, so I didn't do a fresh install. I don't know if the live user mode not working with sound tells you anything. HDMI doesn't work either. I saw it earlier, but it has disappeared. Also, when I uninstalled and purged alsa according to one of the online suggestions, and reinstalled it, alsamixer no longer loads, saying "no such file or directory", and if I load it with -c 1, it says invalid card. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
I tried renaming the pulse folder to pulse_old under .config like someone else suggested online, and that didn't fix anything. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
The install disc didn't work. Which file on the page you suggested should I try? -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834262] Re: Secondary screen shows a bluish color shift. White turns into a turquoise.
This sounds like likely to be a hardware fault. If not a faulty screen then a faulty connection or faulty cable. Please try replacing the cable. It seems there was no secondary screen connected when you opened this bug. Can you tell us what type of connector you are using? ** Summary changed: - connecting a new monitor + Secondary screen shows a bluish color shift. White turns into a turquoise. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Secondary screen shows a bluish color shift. White turns into a turquoise. + i915: Secondary screen shows a bluish color shift. White turns into a turquoise. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1834262 Title: i915: Secondary screen shows a bluish color shift. White turns into a turquoise. Status in linux package in Ubuntu: Incomplete Bug description: The process with this pc and my tv monitor (an old Sonoko) always takes alot with Ubuntu. It takes even a little bit with Windows on the same device, but with this distro (the only one I've ever tried, 19.04) it can even takes minutes and even a counter intuitive setup. I tried alot of days ago and I hope it can show up in the logs. Furthermore the screen no 2, when finally start working, has a color shift. A blue-ish shift. From the color the mouse cursor it seems white turns into a turquoise. I decided to report it now because I thought it was the old tv fault, but today I decide to plug a new laptop on that and, even if Windows colors are a little bit off, it's not at the same level as this issue lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 apt-cache policy pkgname N: Impossibile trovare il pacchetto pkgname ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 00:24:28 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-16-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0277] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0277] InstallationDate: Installed on 2019-06-11 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude E4200 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=3530e372-e9e5-454c-915e-8fa98dfff972 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/18/2008:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E4200 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/linux/+bug/1834262/+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 1834249] Re: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds
Sorry, Google Chrome is not part of Ubuntu so we can't handle bug reports for it here. However, if you install 'chromium-browser' and find the same bug in that then we can handle it here. Do you find the same problems with Firefox? ** Package changed: totem (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1834249 Title: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds Status in Ubuntu: Incomplete Bug description: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 01:28:52 2019 InstallationDate: Installed on 2019-06-19 (6 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1834249/+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 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809407, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1809407 [nvidia] Corrupted wallpaper after resuming from suspend -- 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/1834110 Title: Broken lock-screen wallpaper, stutter after resuming from hibernation Status in mutter package in Ubuntu: Incomplete Bug description: Very similar to Bug #1809407 (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407). I set up my swap partition and tested hibernation on 19.04 /w Nvidia drivers. Basically I observed 2 things: - Lock screen wallpaper gone (black screen with clock), same as with #1809407 - Desktop wallpaper seems okay - Big frame rate drops (despite performance governor), everything seems quite laggy I'm new to Linux/Ubuntu, if you need any logs please tell me the commands and I will attach them. Thanks --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-20 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia wl Package: mutter 3.32.1-2ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-19.20-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834110/+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 1834264] Re: PCI/internal sound card not detected
I found my install disc for Ubuntu 18.04. I can select to try Ubuntu and see if the sound works. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
** Description changed: - Many scanners can no more be used since sane has changed something: The - 3rd-party plug-in the vendor provides as .deb package will still - install. But the scanner is no more recognized. + [Impact] - Scanners that are affected are(besides others): - - Epson Perfection V10 - - Epson Perfection V1000 - - Epson WorkForce GT-1500 - - Brother MFC-8510DN - - Epson Perfection V33 + * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane + dll looks for third party drivers. This configuration effectively broke + backward compatibility for all existing third-party drivers. - It is to note that the probability that the scanner manufacturers fix - things others broke is below 100%. + * A large swath of these third party drivers (most of them) are no + longer supported by the OEM, so maintaining compatibility is important. - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: libsane1 1.0.27-1~experimental2ubuntu2 - Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 - ApportVersion: 2.20.7-0ubuntu3.1 - Architecture: amd64 - Date: Fri Oct 27 12:35:52 2017 - EcryptfsInUse: Yes - SourcePackage: sane-backends - UpgradeStatus: No upgrade log present (probably fresh install) + * No open source replacement drivers are currently available, nor does + the community have the resources to easily replace them. + + * This bug represents a substantial portion of the scanners in use. + + Scanners known to be affected include, but are not limited to: + + - Brother Scanners (all Brother scanners before brscan4) + - DCP-145C + - DCP-163C + - DCP-165C + - DCP-167C + - DCP-185C + - DCP-195C + - DCP-197C + - DCP-365CN + - DCP-373CW + - DCP-375CW + - DCP-377CW + - DCP-383C + - DCP-385C + - DCP-387C + - DCP-395CN + - DCP-585CW + - DCP-6690CW + - DCP-7030 + - DCP-7040 + - DCP-7045N + - DCP-8070D + - DCP-8080DN + - DCP-8085DN + - DCP-9010CN + - DCP-9040CN + - DCP-9042CDN + - DCP-9045CDN + - DCP-J125 + - DCP-J315W + - DCP-J515W + - DCP-J715W + - MFC-250C + - MFC-255CW + - MFC-257CW + - MFC-290C + - MFC-295CN + - MFC-297C + - MFC-490CW + - MFC-495CW + - MFC-5490CN + - MFC-5890CN + - MFC-5895CW + - MFC-6490CW + - MFC-6890CDW + - MFC-7320 + - MFC-7340 + - MFC-7345N + - MFC-7440N + - MFC-7450 + - MFC-7840N + - MFC-7840W + - MFC-790CW + - MFC-795CW + - MFC-8370DN + - MFC-8380DN + - MFC-8480DN + - MFC-8510DN + - MFC-8680DN + - MFC-8880DN + - MFC-8890DW + - MFC-9010CN + - MFC-9120CN + - MFC-9320CW + - MFC-9440CN + - MFC-9450CDN + - MFC-9840CDW + - MFC-990CW + - MFC-J220 + - MFC-J265W + - MFC-J270W + - MFC-J410 + - MFC-J410W + - MFC-J415W + - MFC-J615W + - MFC-J630W + + - Dell MFP Laser Printer 1135n + + - Epson Scanners + - All scanners supported by the libsane-epk driver + - All scanners supported by the iscan driver + - Epson Perfection V10 + - Epson Perfection V1000 + - Epson WorkForce GT-1500 + - Epson Perfection V33 + + - Samsung M2070 + + - Xerox Workcentre 3225 + + * This was working in the 17.04 release. 18.10 is an LTS release, so + backporting is warranted for the 18.10 release. + + [Test Case] + + * Following the standard installation procedures for any of the + affected scanner drivers results in the driver files being installed to + /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux- + gnu/sane. When xsane is run, the scanner is not found. + + [Regression Potential] + + * Regression to previous working sane package often results in the + automatic removal of core system components (documented in the comments + to this bug report), making regression an unusable option for addressing + this bug. + + * The available patch is functional and stable in the 19.10 branch. + + [Other Info] + * Third party sane drivers in previous version of sane were located under /usr/lib/sane/, however, the current version of sane on Ubuntu only looks for 64 bit drivers under the /usr/lib/x86_64-linux-gnu/sane directory. /usr/lib64 and /usr/lib64/sane are other directories old drivers are known to install files to. + + * The addition of symlinks alone does not appear to fix this issue, + though it may make the scanner detectable. Changes to udev rules are + also needed to allow proper communications to the scanners. A selection + of workarounds, including working (though not ideal) udev rules for a + number of scanners has been posted to the sane troubleshooting guide: + help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Bionic:
[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend
The Ubuntu release process requires that we always get the fix into the _next_ release first. That means 19.10. After that we are free to propose it for 19.04 and earlier. I have nominated 19.10, 19.04 and 18.04 at the top of this bug. -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1833508] Re: the system woke up and has not proper desktop image
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809407, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: nvidia ** This bug has been marked a duplicate of bug 1809407 [nvidia] Corrupted wallpaper after resuming from suspend -- 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/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-26 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1834264] Re: PCI/internal sound card not detected
or else, could you install the latest mainline kernel to test if the sound work? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/ -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1834264] Re: PCI/internal sound card not detected
I just launched VirtualBox and it did not work in Windows 7. But I'm not sure if that's what you wanted. I don't have Windows installed. On Tue, Jun 25, 2019 at 7:30 PM Hui Wang wrote: > [ 47.123101] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0 > [ 47.124615] snd_hda_intel :00:1f.3: no codecs found! > > Does your sound work under other OS like windows? we need to confirm it > is not a HW issue first. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1834264 > > Title: > PCI/internal sound card not detected > > Status in alsa-driver package in Ubuntu: > New > > Bug description: > I don't have any sound. I have followed some online instructions that > have not worked. Please help me. My laptop was working just fine > until today. I opened it up and there was no sound. If you need > further information from me, please provide instructions on how to > obtain it. Thank you. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-22-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: ubuntu:GNOME > Date: Tue Jun 25 18:29:31 2019 > InstallationDate: Installed on 2019-02-18 (127 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Title: PCI/internal sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/23/2018 > dmi.bios.vendor: Insyde > dmi.bios.version: F.14 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 8364 > dmi.board.vendor: HP > dmi.board.version: 46.23 > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Pavilion > dmi.product.name: HP Pavilion Laptop 15-cc0xx > dmi.product.sku: 1KU13UA#ABA > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+subscriptions > -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf:
[Desktop-packages] [Bug 1834264] Re: PCI/internal sound card not detected
I just launched VirtualBox and it did not work in Windows 7. But I'm not sure if that's what you wanted. I don't have Windows installed. How can I test the hardware on my laptop with a different operating system? -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
** Changed in: sane-backends (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Bionic: In Progress Status in sane-backends package in Debian: Fix Released Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1834248] Re: HDMI audio and AC3 audio output does not work in Intel NUC
Did you notice a significant delay for booting process when the HDMI and ac3 can't work? there are 30s delay between #1 and #2. Please check the dmesg to find why there is a 30s delay when plugging a usb sound card. [ 37.065157] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC233: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [ 37.065160] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 37.065161] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.677078] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC233: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line [4.677081] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.677082] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1834248 Title: HDMI audio and AC3 audio output does not work in Intel NUC Status in linux package in Ubuntu: Incomplete Bug description: I have a Intel NUC7PJYH with HDMI video and audio to a monitor. Also I use SPDIF ac3 output (having libasound2-plugins-extra). This always worked fine. Since a few weeks, HDMI and ac3 is gone. I.e. 'aplay -l' does not show HDMI any more. Now I found out that if I boot without any usb devices connected (without webcam,mouse,keyboard), it works and I have the HDMI audio output. Does this point into a IRQ problem? Attached find the apport and the alsa-info when HDMI was present and when it was not present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834248/+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 1825940] Re: [graphics] Enable ICL
** Attachment added: "icl_commit_20190626.list_kernv_drm-tip" https://bugs.launchpad.net/intel/+bug/1825940/+attachment/5273300/+files/icl_commit_20190626.list_kernv_drm-tip -- 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/1825940 Title: [graphics] Enable ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+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 1825940] Re: [graphics] Enable ICL
update for icl latest commmits compared with 2019/06/17 --- icl_commit_20190617.list_kernv_drm-tip 2019-06-17 17:10:09.330369948 +0800 +++ icl_commit_20190626.list_kernv_drm-tip 2019-06-26 08:10:11.102281024 +0800 @@ -1,6 +1,23 @@ -f4071997f1d,drm/i915/ehl: Update MOCS table for EHL,2019-05-30 16:40:14,not in drm-intel-next/linux-upstream -cc49abc2460,drm/i915: Add Wa_1409120013:icl,ehl,2019-06-12 11:36:31,not in drm-intel-next/linux-upstream -326fb6dd148,drm/i915/dmc: protect against reading random memory,2019-06-05 16:55:35,next-20190613 +fc25441c7b9,drm/i915/ehl: Add one additional PCH ID to MCC,2019-06-21 08:18:47,not in drm-intel-next/linux-upstream +8dcfdfb4501,drm/i915/perf: fix ICL perf register offsets,2019-06-10 11:19:14,not in drm-intel-next/linux-upstream +f9a393875d3,drm/i915: Disable SAMPLER_STATE prefetching on all Gen11 steppings.,2019-06-25 10:06:55,not in drm-intel-next/linux-upstream +683d672c425,drm/i915/ehl/dsi: Enable AFE over PPI strap,2019-06-19 16:31:34,next-20190621 +6a7bafe8fdb,drm/i915/ehl/dsi: Set lane latency optimization for DW1,2019-06-19 16:31:33,next-20190621 +bdeb18dbcf8,drm/i915/ehl: Allow combo PHY A to drive a third external display,2019-06-18 10:51:31,next-20190620 +patches series of Update whitelist support for new hardware,,, +1/4 5380d0b781c ADDED!,drm/i915: Support flags in whitlist WAs,2019-06-17 18:01:05,next-20190619 +2/4 ebd2de47a19 ADDED!,drm/i915: Support whitelist workarounds on all engines,2019-06-17 18:01:06,next-20190619 +3/4 7b3d4063109,drm/i915: Add whitelist workarounds for ICL,2019-06-17 18:01:07,next-20190619 +4/4 767662bc62a ADDED!,drm/i915: Update workarounds selftest for read only regs,2019-06-17 18:01:08,next-20190619 +c6f7acb80ab,drm/i915/ehl: Introduce Mule Creek Canyon PCH,2019-06-14 17:42:10,next-20190619 +patches series of Enable Multi-segmented-gamma for ICL,,, +1/4 89a72304f2f,drm/i915: Change gamma/degamma_lut_size data type to u32,2019-06-12 12:14:57,next-20190619 +2/4 377c70edd48,drm/i915/icl: Add register definitions for Multi Segmented gamma,2019-06-12 12:14:58,next-20190619 +3/4 eec0778ec42 ADDED!,drm/i915: Rename ivb_load_lut_10_max,2019-06-12 12:14:59,next-20190619 +4/4 02ae8ba9664,drm/i915/icl: Add Multi-segmented gamma support,2019-06-12 12:15:00,next-20190619 +f4071997f1d,drm/i915/ehl: Update MOCS table for EHL,2019-05-30 16:40:14,next-20190617 +cc49abc2460,drm/i915: Add Wa_1409120013:icl,ehl,2019-06-12 11:36:31,next-20190617 +326fb6dd148,drm/i915/dmc: protect against reading random memory,2019-06-05 16:55:35,v5.2-rc5 -- 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/1825940 Title: [graphics] Enable ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+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 1834264] Re: PCI/internal sound card not detected
[ 47.123101] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0 [ 47.124615] snd_hda_intel :00:1f.3: no codecs found! Does your sound work under other OS like windows? we need to confirm it is not a HW issue first. -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
To the extent this bug is similar to the linked Debian bug, it was fixed in Ubuntu 19.04, so I marked it as "Fix Released". OTOH, in that case there is a need to backport the fix to Ubuntu 18.04, and therefore I added a bionic bug task. ** Also affects: sane-backends (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: sane-backends (Ubuntu) Status: Confirmed => Fix Released ** Changed in: sane-backends (Ubuntu Bionic) Importance: Undecided => High ** Changed in: sane-backends (Ubuntu Bionic) Status: New => In Progress ** Changed in: sane-backends (Ubuntu Bionic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Bionic: In Progress Status in sane-backends package in Debian: Unknown Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1834225] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1820794 *** https://bugs.launchpad.net/bugs/1820794 ** This bug has been marked a duplicate of bug 1820794 [Dell Inspiron 3558] PCI/internal sound card not detected -- 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/1834225 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The sound doesnt work, even earphones aren't detected, please help im using ubuntu 14.04 LTS processor - Intel celeron(R) CPU N3060 @1.60Hz x 2 OS type 64 bit ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jun 25 22:26:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-06-13 (742 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834225/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
** Bug watch added: Debian Bug tracker #910103 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910103 ** Also affects: sane-backends (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910103 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Status in sane-backends package in Debian: Unknown Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+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 1834264] [NEW] PCI/internal sound card not detected
Public bug reported: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+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 1833431] Autopkgtest regression report (gnome-settings-daemon/3.32.1-0ubuntu1)
All autopkgtests for the newly accepted gnome-settings-daemon (3.32.1-0ubuntu1) for disco have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1833431 Title: Update gnome-settings-daemon to 3.32.1 Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Disco: Fix Committed Bug description: * Impact There is a new bugfix GNOME update available with some bugs fixed, details on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS * Test case Log into a Ubuntu/GNOME session and make sure that the session has the correct theme, that the screen resolution is correct, that the keybinding work as they should. * Regression potential The main changes are in the plugins to handle the monitor, night mode and multimedia keys, make sure those keep working The update is covered by the GNOME standing exception. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+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 1832374] Autopkgtest regression report (gnome-settings-daemon/3.32.1-0ubuntu1)
All autopkgtests for the newly accepted gnome-settings-daemon (3.32.1-0ubuntu1) for disco have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Disco: Fix Committed Bug description: * Impact Sometime multimedia keys stop working * Test case - start playing an audio file in VLC/totem/smplayer - pause - open a video in another player - exit the other player - try to resume the music play from the first one using the play key -> it should work * Regression potential Make sure that multimedia play/pause keys keep working -- Over the last two releases I've noticed that if you have an audio player such as Clementine running, pause the audio playback and watch a video via VLC or SMPlayer and then close the video player and try to use the media keys again, the following is logged to journald: gsd-media-keys[2607]: Error calling method GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.smplayer was not provided by any .service files. From what I can see is that a service file is created for the media keys for SMPlayer, when SMPlayer is closed that service file is removed and then media keys are still bound to that service. I get the above output for previous track, stop, play, pause and next track media keys. I do get the following output if neither is SMPlayer or Clementine is running or if Clementine is running and playing audio and SMPlayer is open, but no video is loaded: org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed the range into a comma separated list If you re-open SMPlayer and load a video, the media keys work and the GDBus error doesn't occur but the above "Overwriting ..." messages still get logged. Closing SMPlayer again does not restore media keys so that Clementine can handle them. I had SMPlayer running ~17 hours ago. Doing a shell reload doesn't seem to fix this either. I can't really tell if this is an SMPlay/VLC/Video Player issue or actually an issue in GSD, so filing here until someone can reassign to the relevant project. I hit this a while ago, while trying to get some debugging information for a Clementine bug: https://github.com/clementine- player/Clementine/issues/6320 If you need any other information let me know. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 11 17:36:07 2019 InstallationDate: Installed on 2019-02-01 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+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 1834262] [NEW] connecting a new monitor
Public bug reported: The process with this pc and my tv monitor (an old Sonoko) always takes alot with Ubuntu. It takes even a little bit with Windows on the same device, but with this distro (the only one I've ever tried, 19.04) it can even takes minutes and even a counter intuitive setup. I tried alot of days ago and I hope it can show up in the logs. Furthermore the screen no 2, when finally start working, has a color shift. A blue-ish shift. From the color the mouse cursor it seems white turns into a turquoise. I decided to report it now because I thought it was the old tv fault, but today I decide to plug a new laptop on that and, even if Windows colors are a little bit off, it's not at the same level as this issue lsb_release -rd Description:Ubuntu 19.04 Release:19.04 apt-cache policy pkgname N: Impossibile trovare il pacchetto pkgname ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 00:24:28 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-16-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0277] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0277] InstallationDate: Installed on 2019-06-11 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude E4200 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=3530e372-e9e5-454c-915e-8fa98dfff972 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/18/2008:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E4200 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco 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/1834262 Title: connecting a new monitor Status in xorg package in Ubuntu: New Bug description: The process with this pc and my tv monitor (an old Sonoko) always takes alot with Ubuntu. It takes even a little bit with Windows on the same device, but with this distro (the only one I've ever tried, 19.04) it can even takes minutes and even a counter intuitive setup. I tried alot of days ago and I hope it can show up in the logs. Furthermore the screen no 2, when finally start working, has a color shift. A blue-ish shift. From the color the mouse cursor it seems white turns into a turquoise. I decided to report it now because I thought it was the old tv fault, but today I decide to plug a new laptop on that and, even if Windows colors are a little bit off, it's not at the same level as this issue lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 apt-cache policy pkgname N: Impossibile trovare il pacchetto pkgname ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 00:24:28 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom,
[Desktop-packages] [Bug 510889] Re: Alsa No firmware for EMU card
** No longer affects: ubuntustudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/510889 Title: Alsa No firmware for EMU card Status in alsa-plugins: New Status in alsa-plugins package in Ubuntu: New Bug description: A Fresh Install Ubuntu Studio 9.10 Karmic Koala i386 DAW : AMD Athlon, MB ASUS A7N8E, Soundcard EMU 1820M (PCI + Audiodock) My sound card doesn't start, audiodock is blank, no Alsa device for alsamixer. dmesg log : [ 23.071778] EMU10K1_Audigy :01:0a.0: PCI INT A -> Link[APC1] -> GSI 16 (level, high) -> IRQ 16 [ 23.071872] emu1010: Special config. [ 23.073377] emu1010: EMU_HANA_ID = 0x7f [ 23.073382] emu1010: filename emu/hana.fw testing [ 23.073388] EMU10K1_Audigy :01:0a.0: firmware: requesting emu/hana.fw [ 23.434662] firmware: emu/hana.fw not found. Err = -2 [ 23.434668] emu1010: Loading Firmware file emu/hana.fw failed [ 23.441452] EMU10K1_Audigy :01:0a.0: PCI INT A disabled [ 23.441478] EMU10K1_Audigy: probe of :01:0a.0 failed with error -2 I just upload "alsa-firmware-1.0.20" sources from ALSA project website ./configure; make; sudo make install After the reboot my sound card works. I access to alsamixe, play sounds, run Jack in RT 48KHz. (I'm not sure it's fully fonctionnal, because in previous realease I was on Ubuntu-studio 8.04LTS with beta ALSA drivers for my card, so I can't compare). dmesg log : [ 23.220586] EMU10K1_Audigy :01:0a.0: PCI INT A -> Link[APC1] -> GSI 16 (level, high) -> IRQ 16 [ 23.220683] emu1010: Special config. [ 23.220773] emu1010: EMU_HANA_ID = 0x7f [ 23.220775] emu1010: filename emu/hana.fw testing [ 23.220780] EMU10K1_Audigy :01:0a.0: firmware: requesting emu/hana.fw [ 23.406459] firmware size = 0x133a4 I think several component from ALSA are missing in install process. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-plugins/+bug/510889/+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 1833431] Re: Update gnome-settings-daemon to 3.32.1
Hello Sebastien, or anyone else affected, Accepted gnome-settings-daemon into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-settings-daemon/3.32.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1833431 Title: Update gnome-settings-daemon to 3.32.1 Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Disco: Fix Committed Bug description: * Impact There is a new bugfix GNOME update available with some bugs fixed, details on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/gnome-3-32/NEWS * Test case Log into a Ubuntu/GNOME session and make sure that the session has the correct theme, that the screen resolution is correct, that the keybinding work as they should. * Regression potential The main changes are in the plugins to handle the monitor, night mode and multimedia keys, make sure those keep working The update is covered by the GNOME standing exception. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1833431/+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 1832374] Re: Media keys stop working due to missing service file
Hello Bruce, or anyone else affected, Accepted gnome-settings-daemon into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-settings-daemon/3.32.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Disco: Fix Committed Bug description: * Impact Sometime multimedia keys stop working * Test case - start playing an audio file in VLC/totem/smplayer - pause - open a video in another player - exit the other player - try to resume the music play from the first one using the play key -> it should work * Regression potential Make sure that multimedia play/pause keys keep working -- Over the last two releases I've noticed that if you have an audio player such as Clementine running, pause the audio playback and watch a video via VLC or SMPlayer and then close the video player and try to use the media keys again, the following is logged to journald: gsd-media-keys[2607]: Error calling method GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.smplayer was not provided by any .service files. From what I can see is that a service file is created for the media keys for SMPlayer, when SMPlayer is closed that service file is removed and then media keys are still bound to that service. I get the above output for previous track, stop, play, pause and next track media keys. I do get the following output if neither is SMPlayer or Clementine is running or if Clementine is running and playing audio and SMPlayer is open, but no video is loaded: org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed the range into a comma separated list If you re-open SMPlayer and load a video, the media keys work and the GDBus error doesn't occur but the above "Overwriting ..." messages still get logged. Closing SMPlayer again does not restore media keys so that Clementine can handle them. I had SMPlayer running ~17 hours ago. Doing a shell reload doesn't seem to fix this either. I can't really tell if this is an SMPlay/VLC/Video Player issue or actually an issue in GSD, so filing here until someone can reassign to the relevant project. I hit this a while ago, while trying to get some debugging information for a Clementine bug: https://github.com/clementine- player/Clementine/issues/6320 If you need any other information let me know. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 11 17:36:07 2019 InstallationDate: Installed on 2019-02-01 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Same here for: Ubuntu 19.04 gnome 3.32.1 GPU: GeForce MX130/PCIe/SSE2 CPU: Intel® Core™ i5-8250U -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+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 1833508] Re: the system woke up and has not proper desktop image
this is from journalctl after resuming ** Attachment added: "r.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+attachment/5273272/+files/r.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-26 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1833508] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1833508/+attachment/5273271/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-26 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1833508] Re: the system woke up and has not proper desktop image
apport information ** Tags added: apport-collected disco ** Description changed: i have ubuntu 19.04 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.04 + GsettingsChanges: + b'org.gnome.shell' b'app-picker-view' b'uint32 1' + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + InstallationDate: Installed on 2019-01-26 (150 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 + Tags: disco + Uname: Linux 5.0.0-17-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1833508/+attachment/5273269/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-26 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1833508] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1833508/+attachment/5273270/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-26 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1833508] Re: the system woke up and has not proper desktop image
i have gtx 1060 it seems like dublicate -- 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/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-26 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-17-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-12 (44 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1834249] [NEW] Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds
Public bug reported: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 01:28:52 2019 InstallationDate: Installed on 2019-06-19 (6 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1834249 Title: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds Status in totem package in Ubuntu: New Bug description: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 01:28:52 2019 InstallationDate: Installed on 2019-06-19 (6 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1834249/+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 1834248] Re: HDMI audio and AC3 audio output does not work in Intel NUC
** Attachment added: "no HDMI" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834248/+attachment/5273248/+files/hdmi-no.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/1834248 Title: HDMI audio and AC3 audio output does not work in Intel NUC Status in alsa-driver package in Ubuntu: New Bug description: I have a Intel NUC7PJYH with HDMI video and audio to a monitor. Also I use SPDIF ac3 output (having libasound2-plugins-extra). This always worked fine. Since a few weeks, HDMI and ac3 is gone. I.e. 'aplay -l' does not show HDMI any more. Now I found out that if I boot without any usb devices connected (without webcam,mouse,keyboard), it works and I have the HDMI audio output. Does this point into a IRQ problem? Attached find the apport and the alsa-info when HDMI was present and when it was not present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834248/+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 1834248] Re: HDMI audio and AC3 audio output does not work in Intel NUC
** Attachment added: "HDMI works" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834248/+attachment/5273249/+files/hdmi-works.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/1834248 Title: HDMI audio and AC3 audio output does not work in Intel NUC Status in alsa-driver package in Ubuntu: New Bug description: I have a Intel NUC7PJYH with HDMI video and audio to a monitor. Also I use SPDIF ac3 output (having libasound2-plugins-extra). This always worked fine. Since a few weeks, HDMI and ac3 is gone. I.e. 'aplay -l' does not show HDMI any more. Now I found out that if I boot without any usb devices connected (without webcam,mouse,keyboard), it works and I have the HDMI audio output. Does this point into a IRQ problem? Attached find the apport and the alsa-info when HDMI was present and when it was not present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834248/+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 1834248] [NEW] HDMI audio and AC3 audio output does not work in Intel NUC
Public bug reported: I have a Intel NUC7PJYH with HDMI video and audio to a monitor. Also I use SPDIF ac3 output (having libasound2-plugins-extra). This always worked fine. Since a few weeks, HDMI and ac3 is gone. I.e. 'aplay -l' does not show HDMI any more. Now I found out that if I boot without any usb devices connected (without webcam,mouse,keyboard), it works and I have the HDMI audio output. Does this point into a IRQ problem? Attached find the apport and the alsa-info when HDMI was present and when it was not present. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa hdmi nuc -- 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/1834248 Title: HDMI audio and AC3 audio output does not work in Intel NUC Status in alsa-driver package in Ubuntu: New Bug description: I have a Intel NUC7PJYH with HDMI video and audio to a monitor. Also I use SPDIF ac3 output (having libasound2-plugins-extra). This always worked fine. Since a few weeks, HDMI and ac3 is gone. I.e. 'aplay -l' does not show HDMI any more. Now I found out that if I boot without any usb devices connected (without webcam,mouse,keyboard), it works and I have the HDMI audio output. Does this point into a IRQ problem? Attached find the apport and the alsa-info when HDMI was present and when it was not present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834248/+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 1821765] Re: [snap] Missing icon in indicator
Olivier, My best guess is: https://chromium.googlesource.com/chromium/src.git/+/master/chrome/browser/ui/libgtkui/app_indicator_icon.cc#298 --- Logs from running chromium in snap that indicate this is likely a problem: (chrome:29051): libappindicator-WARNING **: 14:11:04.701: Using '/tmp' paths in SNAP environment will lead to unreadable resources --- The (missing) icons in question are located for me at: /tmp/snap.chromium/tmp/.org.chromium.Chromium.yzUwdr/chrome_app_indicator_1_1.png /tmp/snap.chromium/tmp/.org.chromium.Chromium.d1gVzr/chrome_app_indicator_2_7.png -- 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/1821765 Title: [snap] Missing icon in indicator Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium is adding an appindicator, which has a missing icon when running from the snap. I've confirmed with the deb that it shows the chromium icon there. I'm not sure what setting makes it display the appindicator, I've had it there for years so must be some setting I have that is being synced. The only extensions I have installer are: * The Great Suspender * Google Drive * Google Calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1821765/+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 1794997] Re: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available
Govinda, Is this still an issue? If yes, can you reopen the bug .. If not, advise next steps ... thanks, Anish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1794997 Title: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available Status in libnl3 package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Bug description: We are observing the following error while creating VMs Sep 27 14:25:47 xpl-dvt-41 libvirtd[4927]: 2018-09-27 21:25:47.387+: 4927: error : virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available This message is observed with latest Bionic libvirt packages. lab@xpl-dvt-35:~$ dpkg -l | grep libvirt ii gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 amd64GObject introspection files for the libvirt-glib library ii libsys-virt-perl 4.0.0-1 amd64Perl module providing an extension for the libvirt library ii libvirt-bin 4.0.0-1ubuntu8.5 amd64programs for the libvirt library ii libvirt-clients 4.0.0-1ubuntu8.5 amd64Programs for the libvirt library ii libvirt-daemon4.0.0-1ubuntu8.5 amd64Virtualization daemon ii libvirt-daemon-system 4.0.0-1ubuntu8.5 amd64Libvirt daemon configuration files ii libvirt-glib-1.0-0:amd64 1.0.0-1 amd64libvirt GLib and GObject mapping library ii libvirt0:amd644.0.0-1ubuntu8.5 amd64library for interfacing with different virtualization systems ii python-libvirt4.0.0-1 amd64libvirt Python bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1794997/+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 1251059] Re: Preferences dialog window too small
I'm in Bionic now and I can't even get this version of Thunderbird to
ask me.
WM = window manager
--
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/1251059
Title:
Preferences dialog window too small
Status in Mozilla Thunderbird:
Unknown
Status in thunderbird package in Ubuntu:
Incomplete
Bug description:
When replying to an e-mail a dialog sometimes pops up asking if you
want to send the mail Plain Text or HTML. This dialog doesn't fit its
own window. See the attached screenshot.
Using Gnome 2.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 1:24.1.0+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
NonfreeKernelModules: wl
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-32-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ken8740 F pulseaudio
/dev/snd/controlC0: ken8740 F pulseaudio
BuildID: 20131028131509
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xd230 irq 16'
Mixer name : 'Realtek ALC272X'
Components : 'HDA:10ec0272,1025036e,0011'
Controls : 24
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd221 irq 19'
Mixer name : 'ATI RS690/780 HDMI'
Components : 'HDA:1002791a,00791a00,0010'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Channel: Unavailable
Date: Wed Nov 13 23:08:17 2013
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
IpRoute:
default via 192.168.0.254 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.4 metric 2
MarkForUpload: True
Plugins: iTunes Application Detector -
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
(rhythmbox-mozilla)
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=24.1.0/20131028131509 (In use)
RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.3
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2011
dmi.bios.vendor: Acer
dmi.bios.version: V2.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE50_DN
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.14
dmi.modalias:
dmi:bvnAcer:bvrV2.14:bd07/27/2011:svnAcer:pnAspire5551:pvrV2.14:rvnAcer:rnJE50_DN:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.14:
dmi.product.name: Aspire 5551
dmi.product.version: V2.14
dmi.sys.vendor: Acer
---
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: ken3331 F...m pulseaudio
/dev/snd/controlC0: ken3331 F pulseaudio
BuildID: 20180522092743
Channel: Unavailable
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev eth2 proto dhcp src 192.168.0.13 metric 1024
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
192.168.0.0/24 dev eth2 proto kernel scope link src 192.168.0.13
192.168.0.1 dev eth2 proto dhcp scope link src 192.168.0.13 metric 1024
IwConfig:
lxcbr0no wireless extensions.
eth2 no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-dc69d4dc-9e6c-4f63-9c3b-9ed2a0180624
Package: thunderbird 1:52.8.0+build1-0ubuntu0.16.04.1
PackageArchitecture: i386
PrefSources:
prefs.js
[Profile]/extensions/mintr...@tn123.ath.cx/defaults/preferences/mintrayr.js
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Re: [Desktop-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Although mine is the "esc" key, I read somewhere that "shift" key also used to get to the recovery mode to which I also tried to no avail. thanksLevi On Monday, June 24, 2019, 7:00:56 PM PDT, Daniel van Vugt wrote: Recovery mode should work, but that does sound like a different bug. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1834225] [NEW] PCI/internal sound card not detected
Public bug reported: The sound doesnt work, even earphones aren't detected, please help im using ubuntu 14.04 LTS processor - Intel celeron(R) CPU N3060 @1.60Hz x 2 OS type 64 bit ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jun 25 22:26:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-06-13 (742 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1834225 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The sound doesnt work, even earphones aren't detected, please help im using ubuntu 14.04 LTS processor - Intel celeron(R) CPU N3060 @1.60Hz x 2 OS type 64 bit ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jun 25 22:26:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-06-13 (742 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834225/+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 1798074] Re: LIbreoffice crashes on startup
** Changed in: libreoffice-l10n (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- 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/1798074 Title: LIbreoffice crashes on startup Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: [Impact] * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*' packages installed. * The fix is currently in LibreOffice 6.2.0+ on disco and eoan. [Test Case] 1. apt install cpdb-backend-gcp 2. run LibreOffice [Regression Potential] * We're backporting a patch that has already been applied to 6.2.0+ with no regression, so potential for regression here is low. * A combination of autopkgtests and manual testing should provide reasonable confidence that no regressions sneaked in. [Original Description] On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5] /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97] /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca] I have tried entirely removing my profile, ~/.config/libreoffice , but the same problem still exhibits. ProblemType: Bug
[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
** Changed in: libreoffice-l10n (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu Bionic) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- 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/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in openjdk-lts source package in Disco: New Status in libreoffice package in Debian: Won't Fix Bug description: [Impact] * A recent OpenJDK update changes the value of the "java.vendor" property from "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Launch the LibreOffice Start Center 2. Open Tools > Options 3. Navigate to LibreOffice > Advanced 4. A JRE should be listed with Location: /usr/lib/jvm/... [Regression Potential] * This fix is small and concentrated so potential for regression should be relatively low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+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 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)
** Changed in: libreoffice-l10n (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu Bionic) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- 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/1820062 Title: LibreOffice Impress embed video problem (libreoffice-gtk3) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: LibreOffice Impress has problematic embedded video playback. In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress slide, when played video stretches in fullscreen. (LO versions affected at least 6.0.x, 6.1.y and 6.2.1.1) The video of miss-behavior: https://youtu.be/77E6IzVJ5jA The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3). Solution #1 install gstreamer1.0-gtk3 (probably missing dependency) Solution #2 Remove libreoffice-gtk3 and install libreoffice-gtk2 reference to Document Funtation bugzilla: https://bugs.documentfoundation.org/show_bug.cgi?id=124068 [Impact] * This effects all libreoffice-gtk3 users wishing to embed videos into an Impress slide. * The fix is currently in LibreOffice 6.2.2+ on disco and eoan. [Test Case] 1. Insert a video into an Impress slide 2. Play the video 3. The video should play within the slide (not fullscreen like this: https://youtu.be/77E6IzVJ5jA) [Regression Potential] * The fix is one line in the control file so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1820062/+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 1827451] Re: Japanese new era "Reiwa(令和)" support
** Changed in: libreoffice-l10n (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice-l10n (Ubuntu Bionic) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- 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/1827451 Title: Japanese new era "Reiwa(令和)" support Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: Japanese new era "Reiwa(令和)" has began at 2019-05-01. These patches add Reiwa support for Libreoffice Bionic/Xenial. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 10:44:42 2019 InstallationDate: Installed on 2018-07-21 (285 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64(20180506.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) [Impact] * This effects all users who use the Japanese era date format in LibreOffice. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Start Calc 2. Put "01/05/2019" into a cell 3. Right-click on the cell and select "Format Cells" 4. Set “Language" to "Japanese" 5. Set “Format" to "H11.12.31" 6. Cell should show "R1.05.01" (not "N1.05.01”) 7. Set “Format" to "平成11年12月31日" 8. Cell should show "令和1年5月1日" (not "平成31年5月1日") [Regression Potential] * The fix is minor so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827451/+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 1827451] Re: Japanese new era "Reiwa(令和)" support
Hello Ikuya, or anyone else affected, Accepted libreoffice-l10n into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libreoffice-l10n/1:6.0.7-0ubuntu0.18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice-l10n (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1827451 Title: Japanese new era "Reiwa(令和)" support Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: Japanese new era "Reiwa(令和)" has began at 2019-05-01. These patches add Reiwa support for Libreoffice Bionic/Xenial. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 10:44:42 2019 InstallationDate: Installed on 2018-07-21 (285 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64(20180506.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) [Impact] * This effects all users who use the Japanese era date format in LibreOffice. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Start Calc 2. Put "01/05/2019" into a cell 3. Right-click on the cell and select "Format Cells" 4. Set “Language" to "Japanese" 5. Set “Format" to "H11.12.31" 6. Cell should show "R1.05.01" (not "N1.05.01”) 7. Set “Format" to "平成11年12月31日" 8. Cell should show "令和1年5月1日" (not "平成31年5月1日") [Regression Potential] * The fix is minor so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827451/+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 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
Hello Olivier, or anyone else affected, Accepted libreoffice-l10n into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libreoffice-l10n/1:6.0.7-0ubuntu0.18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice-l10n (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in openjdk-lts source package in Disco: New Status in libreoffice package in Debian: Won't Fix Bug description: [Impact] * A recent OpenJDK update changes the value of the "java.vendor" property from "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Launch the LibreOffice Start Center 2. Open Tools > Options 3. Navigate to LibreOffice > Advanced 4. A JRE should be listed with Location: /usr/lib/jvm/... [Regression Potential] * This fix is small and concentrated so potential for regression should be relatively low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+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 1798074] Re: LIbreoffice crashes on startup
Hello Stuart, or anyone else affected, Accepted libreoffice-l10n into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libreoffice-l10n/1:6.0.7-0ubuntu0.18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice-l10n (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1798074 Title: LIbreoffice crashes on startup Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: [Impact] * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*' packages installed. * The fix is currently in LibreOffice 6.2.0+ on disco and eoan. [Test Case] 1. apt install cpdb-backend-gcp 2. run LibreOffice [Regression Potential] * We're backporting a patch that has already been applied to 6.2.0+ with no regression, so potential for regression here is low. * A combination of autopkgtests and manual testing should provide reasonable confidence that no regressions sneaked in. [Original Description] On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)
Hello Gašper, or anyone else affected, Accepted libreoffice-l10n into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libreoffice-l10n/1:6.0.7-0ubuntu0.18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice-l10n (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1820062 Title: LibreOffice Impress embed video problem (libreoffice-gtk3) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Committed Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: LibreOffice Impress has problematic embedded video playback. In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress slide, when played video stretches in fullscreen. (LO versions affected at least 6.0.x, 6.1.y and 6.2.1.1) The video of miss-behavior: https://youtu.be/77E6IzVJ5jA The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3). Solution #1 install gstreamer1.0-gtk3 (probably missing dependency) Solution #2 Remove libreoffice-gtk3 and install libreoffice-gtk2 reference to Document Funtation bugzilla: https://bugs.documentfoundation.org/show_bug.cgi?id=124068 [Impact] * This effects all libreoffice-gtk3 users wishing to embed videos into an Impress slide. * The fix is currently in LibreOffice 6.2.2+ on disco and eoan. [Test Case] 1. Insert a video into an Impress slide 2. Play the video 3. The video should play within the slide (not fullscreen like this: https://youtu.be/77E6IzVJ5jA) [Regression Potential] * The fix is one line in the control file so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1820062/+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 1834211] Re: [SRU] gconf FTBFS in Bionic
The attachment "Debdiff with the fix for Bionic" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+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 1831624]
(In reply to Regina Henschel from comment #2) > I think it is a deficit in the UI, that spaces in the margin are not shown. > Word shows all spaces, SoftMaker shows one space in the margin. So which is wrong, that there is no string wrap to the following line with a text run of spaces reaching the margin--allowing spaces to enter the margin, or that spaces extend beyond the margin and are not show-- where all other mixed text spans will wrap. Wonder what happens with a text run of ? -- 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/1831624 Title: ibus-cangjie in libreoffice cannot type Chinese character at end of line Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Incomplete Bug description: I am using LibreOffice Version: 6.0.7.3, in particular I am using LibreOffice Writer. I am using ibus-cangjie to input Chinese. I cannot input any Chinese characters when I reach the end of a line on the screen. The expected behavior is that the typed Chinese character simply spills over to the next line and I can continue to type without a problem. If I reach the end of the line with half a space (of full-sized Chinese character) available, then I could insert a punctuation mark like 。 or 、 even if I use cangjie codes to input them (and then I can continue normally). if I reach the end of the line with no space available, then I cannot insert 。 or 、 when I use cangjie codes to input them (in the ibus- cangjie standard input table, 、 = XI) In neither case I can type a Chinese character like 日, all the typed characters simply disappears from the input queue and is not typed at all. Note that as I type I can see that the candidate Chinese characters according to the cangjie codes I input, they just don't get sent to the application. when I am at the end of the line, I can type as many spaces as I want and the problem of being unable to type a Chinese character persists. Finally, the bug only triggers when I am at the end of text; if I am inserting in the middle of text, even if I am at the linebreak, I can type normally and naturally. the attached screenshot shows where I am getting my cursor stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1831624/+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 1831624]
I think it is a deficit in the UI, that spaces in the margin are not shown. Word shows all spaces, SoftMaker shows one space in the margin. -- 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/1831624 Title: ibus-cangjie in libreoffice cannot type Chinese character at end of line Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Incomplete Bug description: I am using LibreOffice Version: 6.0.7.3, in particular I am using LibreOffice Writer. I am using ibus-cangjie to input Chinese. I cannot input any Chinese characters when I reach the end of a line on the screen. The expected behavior is that the typed Chinese character simply spills over to the next line and I can continue to type without a problem. If I reach the end of the line with half a space (of full-sized Chinese character) available, then I could insert a punctuation mark like 。 or 、 even if I use cangjie codes to input them (and then I can continue normally). if I reach the end of the line with no space available, then I cannot insert 。 or 、 when I use cangjie codes to input them (in the ibus- cangjie standard input table, 、 = XI) In neither case I can type a Chinese character like 日, all the typed characters simply disappears from the input queue and is not typed at all. Note that as I type I can see that the candidate Chinese characters according to the cangjie codes I input, they just don't get sent to the application. when I am at the end of the line, I can type as many spaces as I want and the problem of being unable to type a Chinese character persists. Finally, the bug only triggers when I am at the end of text; if I am inserting in the middle of text, even if I am at the linebreak, I can type normally and naturally. the attached screenshot shows where I am getting my cursor stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1831624/+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 1831624]
(In reply to V Stuart Foote from comment #3) > Wonder what happens with a text run of ? So checked, and a run of are entered one at a time and will be wrapped onto vcl canvas. So just the with attribute for a text run of spaces is not wrapped--but also it is not visualized to canvas, and we can not advance text cursor into the margin. Checked and LO wrap behavior matches the MS Word 2016 wrap behavior-- that is the wrap will not occur until some non-space text is added, and that text then becomes the start of the next line. Spaces show into the margins, and then after the text causing the wrap. So our behavior is the same as MS Word, but we don't visualize the additional spaces outside the margins and we can not manipulate the text cursor which holds stuck against the right margin. -- 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/1831624 Title: ibus-cangjie in libreoffice cannot type Chinese character at end of line Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Incomplete Bug description: I am using LibreOffice Version: 6.0.7.3, in particular I am using LibreOffice Writer. I am using ibus-cangjie to input Chinese. I cannot input any Chinese characters when I reach the end of a line on the screen. The expected behavior is that the typed Chinese character simply spills over to the next line and I can continue to type without a problem. If I reach the end of the line with half a space (of full-sized Chinese character) available, then I could insert a punctuation mark like 。 or 、 even if I use cangjie codes to input them (and then I can continue normally). if I reach the end of the line with no space available, then I cannot insert 。 or 、 when I use cangjie codes to input them (in the ibus- cangjie standard input table, 、 = XI) In neither case I can type a Chinese character like 日, all the typed characters simply disappears from the input queue and is not typed at all. Note that as I type I can see that the candidate Chinese characters according to the cangjie codes I input, they just don't get sent to the application. when I am at the end of the line, I can type as many spaces as I want and the problem of being unable to type a Chinese character persists. Finally, the bug only triggers when I am at the end of text; if I am inserting in the middle of text, even if I am at the linebreak, I can type normally and naturally. the attached screenshot shows where I am getting my cursor stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1831624/+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 1831624]
I'm not sure about wrapping of spaces. Of cause an editor, which wraps at the window edge, will put the spaces to the new line. But Word and OpenOffice.org had always wrapped so, that the first non-space content is at the starting of the next line. I haven't got Wordperfect and have not used Latex. Perhaps someone knows, how they handle such spaces. But as long as the line break works as it is now, the spaces should be displayed to make it clear to the user why the cursor and delete key behave like this. -- 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/1831624 Title: ibus-cangjie in libreoffice cannot type Chinese character at end of line Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Incomplete Bug description: I am using LibreOffice Version: 6.0.7.3, in particular I am using LibreOffice Writer. I am using ibus-cangjie to input Chinese. I cannot input any Chinese characters when I reach the end of a line on the screen. The expected behavior is that the typed Chinese character simply spills over to the next line and I can continue to type without a problem. If I reach the end of the line with half a space (of full-sized Chinese character) available, then I could insert a punctuation mark like 。 or 、 even if I use cangjie codes to input them (and then I can continue normally). if I reach the end of the line with no space available, then I cannot insert 。 or 、 when I use cangjie codes to input them (in the ibus- cangjie standard input table, 、 = XI) In neither case I can type a Chinese character like 日, all the typed characters simply disappears from the input queue and is not typed at all. Note that as I type I can see that the candidate Chinese characters according to the cangjie codes I input, they just don't get sent to the application. when I am at the end of the line, I can type as many spaces as I want and the problem of being unable to type a Chinese character persists. Finally, the bug only triggers when I am at the end of text; if I am inserting in the middle of text, even if I am at the linebreak, I can type normally and naturally. the attached screenshot shows where I am getting my cursor stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1831624/+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 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
Although reported to gitlab.freedesktop.org (see above), there is no sign whatsoever of activity in that quarter. In the meantime, I have just downloaded the latest batch of 18.04 updates, and the situation has got immeasurably worse. The relevant part of the xmodmap -pk output has now changed to: 136 0xffc8 (F11)0xffc8 (F11)0xffc8 (F11)0xffc8 (F11) 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xffc9 (F12)0xffc9 (F12)0xffc9 (F12)0xffc9 (F12) 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0xffca (F13)0xffca (F13)0xffca (F13)0xffca (F13) 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xffcb (F14)0xffcb (F14)0xffcb (F14)0xffcb (F14) 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0xffcc (F15)0xffcc (F15)0xffcc (F15)0xffcc (F15) 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0xffcd (F16)0xffcd (F16)0xffcd (F16)0xffcd (F16) 0x1005ff72 (SunCopy)0x (NoSymbol) 0x1005ff72 (SunCopy) 142 0xffce (F17)0xffce (F17)0xffce (F17)0xffce (F17) 0x1005ff73 (SunOpen)0x (NoSymbol) 0x1005ff73 (SunOpen) 143 0xffcf (F18)0xffcf (F18)0xffcf (F18)0xffcf (F18) 0x1005ff74 (SunPaste) 0x (NoSymbol) 0x1005ff74 (SunPaste) 144 0xffd0 (F19)0xffd0 (F19)0xffd0 (F19)0xffd0 (F19) 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0xffd1 (F20)0xffd1 (F20)0xffd1 (F20)0xffd1 (F20) 0x1005ff75 (SunCut) 0x (NoSymbol) 0x1005ff75 (SunCut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) i.e. the keysyms mapped to keycodes 141, 142, 143, and 145 have all changed, and unpteen things which were working fine this morning are suddenly broken (in addition to gedit, which I can fix, my Opera Browser is affected' libreoffice and firefox seem to have survived, but every application whatsoever, when you press keycode 145, produces an ugly popup concerning my "rear microphone" - which does not even exist). What is going on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config: New Status in xkeyboard-config package in Ubuntu: Triaged Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the
[Desktop-packages] [Bug 1834217] [NEW] Firefox restarts ocacianlly
Public bug reported: Description:Ubuntu 18.04.2 LTS Release:18.04 firefox: Installed: 67.0.4+build1-0ubuntu0.18.04.1 Candidate: 67.0.4+build1-0ubuntu0.18.04.1 Version table: *** 67.0.4+build1-0ubuntu0.18.04.1 500 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 59.0.2+build1-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I got somewhat frustrated the other day when it happened - again, Firefox restarted without me updating it or anything like that. So I lashed out on Twitter (https://twitter.com/tmhanssonit/status/1142370265042685952) and ended up here. I don't know what the casue is, but some background information: I have multiple tabs open, some of them are standard tabs like email, Github, my webshop and so on. At any given time I have maximum 10-15 tabs open, but usually only around 5. Sometimes when opening a new tab Firefox greets me with this little thing: https://i.imgur.com/zLD8o9x.png and I need to restart Firefox (which never opens automatically again btw) and all my login cache are cleaned (that's how my settings are) which means I have to enter my 2FA in all the tabs again. I would be totally fine with this if I was the one deciding when to restart and when not to, but when Firefox makes the decisions over my head, sometimes several times per day, I get frustrated. When using Windows I noticed that Firefox asks the user something like "do you want to do this now" with an option to do it later. Why isn't that implemented in Ubuntu as well? Thanks for all your hard work btw. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 67.0.4+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 3119 F pulseaudio /dev/snd/controlC0: daniel 3119 F pulseaudio BuildID: 20190620092152 Channel: Unavailable Date: Tue Jun 25 17:51:16 2019 ForcedLayersAccel: False InstallationDate: Installed on 2018-11-17 (220 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) IpRoute: default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.10 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1834217 Title: Firefox restarts ocacianlly Status in firefox package in Ubuntu: New Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 firefox: Installed: 67.0.4+build1-0ubuntu0.18.04.1 Candidate: 67.0.4+build1-0ubuntu0.18.04.1 Version table: *** 67.0.4+build1-0ubuntu0.18.04.1 500 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 59.0.2+build1-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I got somewhat frustrated the other day when it happened - again, Firefox restarted without me updating it or anything like that. So I lashed out on Twitter (https://twitter.com/tmhanssonit/status/1142370265042685952) and ended up here. I don't know what the casue is, but some background information: I have multiple tabs open, some of them are standard tabs like email, Github, my webshop and so on. At any given time I have maximum 10-15 tabs open, but usually only around 5. Sometimes when opening a new tab Firefox greets me with this little thing: https://i.imgur.com/zLD8o9x.png and I need to restart Firefox (which never opens automatically again btw) and all my login cache are cleaned (that's how my settings are) which means I have to enter my 2FA in all the
[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup
Hello Stuart, or anyone else affected, Accepted libreoffice into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:6.0.7-0ubuntu0.18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1798074 Title: LIbreoffice crashes on startup Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Status in libreoffice-l10n source package in Bionic: In Progress Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: [Impact] * This effects all bionic and cosmic users who have 'libcpd*' 'cpdb*' packages installed. * The fix is currently in LibreOffice 6.2.0+ on disco and eoan. [Test Case] 1. apt install cpdb-backend-gcp 2. run LibreOffice [Regression Potential] * We're backporting a patch that has already been applied to 6.2.0+ with no regression, so potential for regression here is low. * A combination of autopkgtests and manual testing should provide reasonable confidence that no regressions sneaked in. [Original Description] On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179]
[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2
the solution works for all cherry trail based systems -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1561278] Re: internal sound card not detected HP X2
" Logan Rathbone 2019-01-27 19:57:00 UTC In case anyone is searching the web to seek solutions, I'll put on the record that 4.20.4, with the patch as generated above, along with the UCM files that have been posted on git at https://github.com/heikomat/linux/tree/cx2072x/cx2072x_fixes_and_manual/chtcx2072x - sound is now functioning on my Asus Transformer Mini T103HA. Shouldn't really matter as I am using an updated but otherwise vanilla kernel from ftp.kernel.org, but again, for the record, this is under Slackware Current (live ISO from alienBob 1.3.0.2, 20190117). Thanks all. I hope these efforts can be merged into mainline Linux and ALSA, but I'm sure there are reasons above my head as to why they have not." Big thanks to Heiko Mathes, Pierre Louis, Takashi Iwai and Pierre Bossart. -- 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/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1834206] Re: fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Thank you for your bug report, it might be worth reporting upstream on
https://gitlab.freedesktop.org/fontconfig/fontconfig/issues
** Changed in: fontconfig (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1834206
Title:
fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Status in fontconfig package in Ubuntu:
New
Bug description:
I have a BGR display so I really would like to have BGR subpixel
rendering. I'm having major trouble getting fc-match to emit correct
info.
$ fc-match -v | grep -E 'rgba|lcdfilter|antialias|hintstyle|dpi'
antialias: True(w)
hintstyle: 2(i)(w)
dpi: 75(f)(s)
rgba: 1(i)(w)
lcdfilter: 1(i)(w)
$ ls -l /etc/fonts/conf.d/10*
lrwxrwxrwx 1 root root 31 2016-08-16 22:18
/etc/fonts/conf.d/10-antialias.conf -> ../conf.avail/10-antialias.conf
lrwxrwxrwx 1 root root 30 2019-06-14 12:27 /etc/fonts/conf.d/10-autohint.conf
-> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 29 2016-08-16 22:18 /etc/fonts/conf.d/10-hinting.conf
-> ../conf.avail/10-hinting.conf
lrwxrwxrwx 1 root root 36 2016-08-16 22:18
/etc/fonts/conf.d/10-hinting-slight.conf -> ../conf.avail/10-hinting-slight.conf
lrwxrwxrwx 1 root root 40 2016-08-16 22:18
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf ->
../conf.avail/10-scale-bitmap-fonts.conf
lrwxrwxrwx 1 root root 35 2019-06-13 12:16
/etc/fonts/conf.d/10-sub-pixel-bgr.conf -> ../conf.avail/10-sub-pixel-bgr.conf
$ strace -e trace=file fc-match -v 2>&1 | grep "open.*bgr"
open("/etc/fonts/conf.d/10-sub-pixel-bgr.conf", O_RDONLY|O_CLOEXEC) = 5
$ gsettings list-recursively | grep bgr
com.canonical.unity-greeter xft-rgba 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.mate.font-rendering rgba-order 'bgr'
Is there some documented reason that fc-match fails to report correct
subpixel order given this config? Is there some another configuration
file that I must modify or create to get fc-match to correctly declare
BGR subpixel structure?
Also, the dpi above is incorrect too, the correct value would be near
96.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18
Uname: Linux 4.15.0-51-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jun 25 16:50:15 2019
InstallationDate: Installed on 2015-02-23 (1583 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: fontconfig
UpgradeStatus: Upgraded to xenial on 2016-06-10 (1110 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1834206/+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 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted
** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1573720 Title: Unencrypted private keys are insecure error reported even when key is encrypted Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ed50d4f9-c810-4be0-b06c-8acd58015c50 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1573720/+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 1834211] Re: [SRU] gconf FTBFS in Bionic
** Attachment added: "Debdiff with the fix for Bionic" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+attachment/5273159/+files/gconf-debdiff-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+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 1834211] [NEW] [SRU] gconf FTBFS in Bionic
Public bug reported: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk-doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+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 1825720] Re: No option to 'star' file in 19.04
Thank you for your bug report, on what file are you trying? There is one known limitation that it only applies to content indexed https://gitlab.gnome.org/GNOME/nautilus/issues/243 There is a bug in 3.32 that the option is not available in subdirs https://gitlab.gnome.org/GNOME/nautilus/issues/947 The UI is available in the context menu as a "mark as favorite" item and as column in the list view (though it might not be automatically enabled for users upgrading and an existing columns config, https://gitlab.gnome.org/GNOME/nautilus/issues/341) ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #243 https://gitlab.gnome.org/GNOME/nautilus/issues/243 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #947 https://gitlab.gnome.org/GNOME/nautilus/issues/947 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #341 https://gitlab.gnome.org/GNOME/nautilus/issues/341 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1825720 Title: No option to 'star' file in 19.04 Status in nautilus package in Ubuntu: Incomplete Bug description: New feature in 19.04 is not working on my system. As I understand, I should be able to right-click a file/folder and select star. That option is not available though 'Starred' is now a location in places. This option is missing under both Wayland and X. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825720/+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 1833555] Re: Add OEM->Family
** Changed in: ubuntu-report (Ubuntu Bionic)
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1833555
Title:
Add OEM->Family
Status in ubuntu-report package in Ubuntu:
Fix Released
Status in ubuntu-report source package in Bionic:
New
Bug description:
[Impact]
Some OEM store the commercial name of the product into the Family field of
the system information record of smbios.
This update retrieves this information from
/sys/class/dmi/id/product_family and adds it to the OEM->Family field
[Test Case]
From a terminal run the command:
$ ubuntu-report show
Verify that it contains a field OEM/Family and it matches the content
of /sys/class/dmi/id/product_family
The output should look like:
"OEM": {
"Vendor": "Dell Inc.",
"Product": "Inspiron 7472",
"Family": "Inspiron"
},
It is possible that the field is empty.
[Regression Potential]
Very low. This field didn't exist before and it is covered by a full
regression test suite.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-report 1.5.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 14:49:35 2019
Dependencies:
gcc-9-base 9.1.0-4ubuntu1
libc6 2.29-0ubuntu2
libgcc1 1:9.1.0-4ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2014-07-15 (1801 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubuntu-report
UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1833555/+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 1834206] [NEW] fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Public bug reported:
I have a BGR display so I really would like to have BGR subpixel
rendering. I'm having major trouble getting fc-match to emit correct
info.
$ fc-match -v | grep -E 'rgba|lcdfilter|antialias|hintstyle|dpi'
antialias: True(w)
hintstyle: 2(i)(w)
dpi: 75(f)(s)
rgba: 1(i)(w)
lcdfilter: 1(i)(w)
$ ls -l /etc/fonts/conf.d/10*
lrwxrwxrwx 1 root root 31 2016-08-16 22:18 /etc/fonts/conf.d/10-antialias.conf
-> ../conf.avail/10-antialias.conf
lrwxrwxrwx 1 root root 30 2019-06-14 12:27 /etc/fonts/conf.d/10-autohint.conf
-> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 29 2016-08-16 22:18 /etc/fonts/conf.d/10-hinting.conf ->
../conf.avail/10-hinting.conf
lrwxrwxrwx 1 root root 36 2016-08-16 22:18
/etc/fonts/conf.d/10-hinting-slight.conf -> ../conf.avail/10-hinting-slight.conf
lrwxrwxrwx 1 root root 40 2016-08-16 22:18
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf ->
../conf.avail/10-scale-bitmap-fonts.conf
lrwxrwxrwx 1 root root 35 2019-06-13 12:16
/etc/fonts/conf.d/10-sub-pixel-bgr.conf -> ../conf.avail/10-sub-pixel-bgr.conf
$ strace -e trace=file fc-match -v 2>&1 | grep "open.*bgr"
open("/etc/fonts/conf.d/10-sub-pixel-bgr.conf", O_RDONLY|O_CLOEXEC) = 5
$ gsettings list-recursively | grep bgr
com.canonical.unity-greeter xft-rgba 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.mate.font-rendering rgba-order 'bgr'
Is there some documented reason that fc-match fails to report correct
subpixel order given this config? Is there some another configuration
file that I must modify or create to get fc-match to correctly declare
BGR subpixel structure?
Also, the dpi above is incorrect too, the correct value would be near
96.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-lowlatency 4.15.18
Uname: Linux 4.15.0-51-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jun 25 16:50:15 2019
InstallationDate: Installed on 2015-02-23 (1583 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: fontconfig
UpgradeStatus: Upgraded to xenial on 2016-06-10 (1110 days ago)
** Affects: fontconfig (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1834206
Title:
fc-match -v reports rgba:1 instead of rgba:2 with BGR display
Status in fontconfig package in Ubuntu:
New
Bug description:
I have a BGR display so I really would like to have BGR subpixel
rendering. I'm having major trouble getting fc-match to emit correct
info.
$ fc-match -v | grep -E 'rgba|lcdfilter|antialias|hintstyle|dpi'
antialias: True(w)
hintstyle: 2(i)(w)
dpi: 75(f)(s)
rgba: 1(i)(w)
lcdfilter: 1(i)(w)
$ ls -l /etc/fonts/conf.d/10*
lrwxrwxrwx 1 root root 31 2016-08-16 22:18
/etc/fonts/conf.d/10-antialias.conf -> ../conf.avail/10-antialias.conf
lrwxrwxrwx 1 root root 30 2019-06-14 12:27 /etc/fonts/conf.d/10-autohint.conf
-> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 29 2016-08-16 22:18 /etc/fonts/conf.d/10-hinting.conf
-> ../conf.avail/10-hinting.conf
lrwxrwxrwx 1 root root 36 2016-08-16 22:18
/etc/fonts/conf.d/10-hinting-slight.conf -> ../conf.avail/10-hinting-slight.conf
lrwxrwxrwx 1 root root 40 2016-08-16 22:18
/etc/fonts/conf.d/10-scale-bitmap-fonts.conf ->
../conf.avail/10-scale-bitmap-fonts.conf
lrwxrwxrwx 1 root root 35 2019-06-13 12:16
/etc/fonts/conf.d/10-sub-pixel-bgr.conf -> ../conf.avail/10-sub-pixel-bgr.conf
$ strace -e trace=file fc-match -v 2>&1 | grep "open.*bgr"
open("/etc/fonts/conf.d/10-sub-pixel-bgr.conf", O_RDONLY|O_CLOEXEC) = 5
$ gsettings list-recursively | grep bgr
com.canonical.unity-greeter xft-rgba 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.cinnamon.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.gnome.settings-daemon.plugins.xsettings rgba-order 'bgr'
org.mate.font-rendering rgba-order 'bgr'
Is there some documented reason that fc-match fails to report correct
subpixel order given this config? Is there some another configuration
file that I must modify or create to get fc-match to correctly declare
BGR subpixel structure?
Also, the dpi above is incorrect too, the correct value would be near
96.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
[Desktop-packages] [Bug 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop
** Tags added: fixed-in-3.32.2 -- 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/1827953 Title: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: In Progress Bug description: Configure some “world clocks” in Gnome Clocks (or maybe using some other tool). Expected behaviour (how it worked in cosmic & before): Gnome Shell shows the time for the cities you configured when you click on the date at the top centre. What happens: Gnome Shell crashes just after login, creating a “login loop” where the user is locked out of their computer. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827953/+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 1833231] Re: cups ftbfs in eoan (amd64 only)
** Tags removed: rls-ee-incoming -- 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/1833231 Title: cups ftbfs in eoan (amd64 only) Status in cups package in Ubuntu: New Bug description: cups ftbfs in eoan (amd64 only) in a test rebuild: https://launchpadlibrarian.net/428250411/buildlog_ubuntu-eoan- amd64.cups_2.2.10-6ubuntu1_BUILDING.txt.gz E [14/Jun/2019:14:46:57.037970 +] Unknown default SystemGroup "lpadmin". PASS: 8 warning messages. PASS: 0 notice messages. PASS: 760 info messages. PASS: 24065 debug messages. PASS: 25573 debug2 messages. Copied log file "access_log-2019-06-14-buildd" to test directory. Copied log file "debug_log-2019-06-14-buildd" to test directory. Copied log file "error_log-2019-06-14-buildd" to test directory. Copied log file "page_log-2019-06-14-buildd" to test directory. Copied report file "cups-str-2019-06-14-buildd.html" to test directory. 1 tests failed. make[2]: *** [Makefile:257: check] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:201: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:17: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+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 1823448] Re: cogl ftbfs in disco (i386 only)
** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cogl in Ubuntu. https://bugs.launchpad.net/bugs/1823448 Title: cogl ftbfs in disco (i386 only) Status in cogl package in Ubuntu: New Status in cogl source package in Disco: New Bug description: https://launchpadlibrarian.net/417939758/buildlog_ubuntu- disco-i386.cogl_1.22.2-6_BUILDING.txt.gz make check-local make[5]: Entering directory '/<>/tests' ( cd ./conform && make test ) || exit $? make[6]: Entering directory '/<>/tests/conform' Key: ok = Test passed n/a = Driver is missing a feature required for the test FAIL = Unexpected failure FIXME = Test failed, but it was an expected failure PASS! = Unexpected pass Test GL+FF GL+ARBFP GL+GLSL GL-NPT GL3ES2 ES2-NPT test_pipeline_user_matrix: ok ok ok ok ok ok ok test_blend_strings: ok ok ok ok ok ok ok test_blend: ok ok ok ok ok ok ok test_premult: FIXMEFIXME FIXME FIXME FIXME FIXME FIXME test_path: ok ok ok ok ok ok ok test_path_clip: ok ok ok ok ok ok ok test_depth_test: ok ok ok ok ok ok ok test_color_mask: ok ok ok ok ok ok ok make[6]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[6]: *** Waiting for unfinished jobs make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[6]: *** wait: No child processes. Stop. make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs make[5]: *** [Makefile:875: test] Terminated make[2]: *** wait: No child processes. Stop. E: Caught signal ‘Terminated’: terminating immediately make[4]: *** [Makefile:750: check-am] Terminated make: *** [debian/rules:7: build-arch] Terminated make[1]: [debian/rules:60: override_dh_auto_test] Terminated (ignored) Build killed with signal TERM after 150 minutes of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1823448/+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 1834052] Re: autopkgtest failures: Chromium-Related in Tests
Submitted suggested change to the debian package: https://salsa.debian.org/giraffe-team/kopano-webapp/merge_requests/1 ** Changed in: kopano-webapp (Ubuntu) Status: New => In Progress ** Changed in: kopano-webapp (Ubuntu) Importance: Undecided => Medium -- 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/1834052 Title: autopkgtest failures: Chromium-Related in Tests Status in chromium-browser package in Ubuntu: Confirmed Status in kopano-webapp package in Ubuntu: In Progress Bug description: Hello. Currently, the kopano-webapp autopkgtests are failing. Three of these are related to Chromium crashes/failures (possibly because they're snapped) within the Selenium calls. The fourth is a snap related issue in general. These autopkgtest failures are blocking HTTPD packages in Proposed (nginx, apache, etc.) -- Relevant Links: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/arm64/k/kopano- webapp/20190624_084645_0ef6d@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/armhf/k/kopano- webapp/20190624_082623_0ef6d@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/i386/k/kopano- webapp/20190624_082523_0ef6d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1834052/+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 1574029] Re: Upgrade failed
*** This bug is a duplicate of bug 1550292 *** https://bugs.launchpad.net/bugs/1550292 ** This bug has been marked a duplicate of bug 1550292 package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1574029 Title: Upgrade failed Status in shared-mime-info package in Ubuntu: New Bug description: At the end of the upgrade, a dialog box appeared "The upgrade has aborted. Your system could be in an unstable state. A recovery will run now (dpkg -configure - a). Nothing happened after closing the dialog box. After shutdown, boot up failed after grub tries to load something with this message "Starting up", then after 10 seconds this message "Gave up waiting for root device., common problems:.ALERT! UUID = 2476e..does not exist. The the boot process stopped at the initramfs prompt. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.5-2 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 17:34:29 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-11-12 (162 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+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 1834052] Re: autopkgtest failures: Chromium-Related in Tests
I can now reproduce the failure by running the test with nosetests3
manually.
Removing the "--log-path=/tmp/chromedriver.log" service arg fixes the
issue. The confined chromedriver bails out when it fails to write there:
$ /snap/bin/chromium.chromedriver --log-path=/tmp/chromedriver.log
Starting ChromeDriver 75.0.3770.90
(a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}) on
port 9515
Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to
prevent access by malicious code.
Failed to redirect stderr to log file.
Unable to initialize logging. Exiting...
Given that the log file isn't exposed as a retrievable artefact when
autopkgtests are run, I suggest we just remove it.
If it turns out that a significant number of existing selenium tests do the
same, we could consider patching chromedriver in the snap to ignore that
argument, instead of bailing out.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
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/1834052
Title:
autopkgtest failures: Chromium-Related in Tests
Status in chromium-browser package in Ubuntu:
Confirmed
Status in kopano-webapp package in Ubuntu:
New
Bug description:
Hello.
Currently, the kopano-webapp autopkgtests are failing. Three of these
are related to Chromium crashes/failures (possibly because they're
snapped) within the Selenium calls.
The fourth is a snap related issue in general.
These autopkgtest failures are blocking HTTPD packages in Proposed
(nginx, apache, etc.)
--
Relevant Links:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan/eoan/arm64/k/kopano-
webapp/20190624_084645_0ef6d@/log.gz
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan/eoan/armhf/k/kopano-
webapp/20190624_082623_0ef6d@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan/eoan/i386/k/kopano-
webapp/20190624_082523_0ef6d@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1834052/+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 1568572] Re: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fixed in Xenial on 2016-07-18 by using interest-noawait in debian/bamfdaemon.triggers file. More info at bug 1589097. ** Changed in: bamf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1568572 Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in bamf package in Ubuntu: Fix Released Bug description: I submitted this bug report because Ubuntu advised me to do so during an upgrade to Xenial from Wily. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 Uname: Linux 4.0.3-bisect-test-01-0559366f72c86288c8d3dc5cae91dfc2f6e26ad9 x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 10 19:23:53 2016 DuplicateSignature: package:bamfdaemon:0.5.2~bzr0+15.10.20150627.1-0ubuntu1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: bamf Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1568572/+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 1574123] Re: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1568572 *** https://bugs.launchpad.net/bugs/1568572 ** This bug has been marked a duplicate of bug 1568572 package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1574123 Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in bamf package in Ubuntu: Confirmed Bug description: during upgrade bamfdaemon was noch possible to install. Now it seems to be missiong? how to install it now? via packet-installer or terminal? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Sat Apr 23 20:17:09 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-08-21 (246 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: bamf Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1574123/+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 1568572] Re: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bamf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1568572 Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in bamf package in Ubuntu: Fix Released Bug description: I submitted this bug report because Ubuntu advised me to do so during an upgrade to Xenial from Wily. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 Uname: Linux 4.0.3-bisect-test-01-0559366f72c86288c8d3dc5cae91dfc2f6e26ad9 x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 10 19:23:53 2016 DuplicateSignature: package:bamfdaemon:0.5.2~bzr0+15.10.20150627.1-0ubuntu1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: bamf Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1568572/+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 1599846] Re: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
*** This bug is a duplicate of bug 1568572 *** https://bugs.launchpad.net/bugs/1568572 ** This bug has been marked a duplicate of bug 1568572 package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1599846 Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet Status in bamf package in Ubuntu: New Bug description: Update failed while upgrading from xenial to yakkety. mahowi@T60:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 mahowi@T60:~$ apt-cache policy bamfdaemon bamfdaemon: Installiert: 0.5.3~bzr0+16.10.20160705-0ubuntu1 Installationskandidat: 0.5.3~bzr0+16.10.20160705-0ubuntu1 Versionstabelle: *** 0.5.3~bzr0+16.10.20160705-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 16.10 Package: bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 Date: Thu Jul 7 13:39:38 2016 ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet InstallationDate: Installed on 2016-07-06 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.9ubuntu1 apt 1.3~exp1 SourcePackage: bamf Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet UpgradeStatus: Upgraded to yakkety on 2016-07-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1599846/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
No worries, thanks for following up -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs: Unknown Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Released Status in samba source package in Bionic: Fix Released Status in gvfs source package in Cosmic: Fix Released Status in samba source package in Cosmic: Fix Released Bug description: [Impact] The so called "browsing a windows network" made use of an SMB1 protocol version feature. Recent versions of samba, including the one released with bionic, default to a higher versions of the protocol which lacks this feature. As a result, the "other locations -> windows network" tab in Nautilus is empty even when there are windows or samba machines in the network. Accessing such machines directly, via smb:/// type urls, continues to work. The fix is two-fold: - introduce a new samba API call that can be used to set the protocol version to use - change applications to make use of this API call to set the protocol versio to SMB1/NT1 just for the network browsing gvfs was updated to make use of this api call, if detected at build time. To complete this SRU, gvfs needs a no-change rebuild *after* samba was accepted into proposed. [Test case] * Launch a bionic desktop vm. You can start with a server one, and then install the "ubuntu-desktop" package. In the same command, also install the packages we need for this test: $ sudo apt update $ sudo apt install ubuntu-desktop samba smbclient * set a password for the ubuntu user, so you can login at the graphical console $ sudo passwd ubuntu * set the same password for the ubuntu samba user: sudo smbpasswd -a ubuntu * add a simple [pub] share to samba: $ printf "[pub]\n\tpath=/tmp\n\tguest ok = no\n" | sudo tee -a /etc/samba/smb.conf * reboot $ sudo reboot * login at the graphical console as the ubuntu user. Go through the first-user-setup motions as you want. * try to browse the windows network via "other locations -> windows network". You will get an empty folder. * update the samba and gvfs packages * logout and login again on the gui, browse the windows network again. This time it will show the "WORKGROUP" folder, and if you click through, you will see yourself (your VM) and the [pub] share, among others. * click on the "pub" share, select registered user and login with the ubuntu credentials you created earlier with smbpasswd. * in another terminal, run this command to confirm that the SMB protocol version that was used to connect to [pub] was not just NT1/SMB1, but higher: $ sudo smbstatus ... 8779ubuntu ubuntu 192.168.122.94 (ipv4:192.168.122.94:60818) SMB3_11 -partial(AES-128-CMAC) Note "SMB3_11" above. [Regression potential] The samba update itself just introduces and exposes a new API call. It's up to other applications to make use of that. gvfs was patched to detect this call at build time and use it if it's detected. Packages that are not rebuilt will not see the change, and packages that *are* rebuilt will only see the change if they make use of it. [Other Info] This update introduces a specific runtime dependency between gvfs and libsmbclient due to the new API call added to the latter. Any package that is rebuilt with libsmbclient and makes use of that API call will get this specific dependency. This is handled automatically by dh_mkshlibs. To complete this SRU, gvfs will need a no-change rebuild after samba was accepted into proposed. Disco's gvfs is already using the new call, as can be seen in this build log https://launchpadlibrarian.net/415424052/buildlog_ubuntu-disco-amd64.gvfs_1.40.0-1_BUILDING.txt.gz: ... Dependency smbclient found: YES 0.5.0 Checking for function "smbc_setOptionProtocols" with dependency smbclient: YES The smbc_setOptionProtocols() call is only used when the url is like "smb:///", or the server cannot be resolved. The downgrade overrides the setting in smb.conf, and is used just for this case: browsing the network. When connecting to a machine, the url is like "smb:///", and then this function we are adding is not called. I updated the test to actually click on the machine that shows up in the network browsing, and then check with "smbstatus" which version of the protocol was used when connecting to an actual share. --- Nautilus should show smbtree and host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor)
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Looks like I missed a notification in https://gitlab.gnome.org/GNOME/gvfs/issues/307, I'll followup there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1826550] Re: Fractional scaling options do not appear with multiple monitors
Possibly related to https://gitlab.gnome.org/GNOME/gnome-control- center/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #17 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17 -- 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/1826550 Title: Fractional scaling options do not appear with multiple monitors Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using 19.04 disco with Wayland. I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor. I have enabled the experimental fractional scaling support. When no external monitor is connected, the fractional scaling options are displayed as expected. When the external monitor is connected, only the old whole number scaling options are displayed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 14:32:55 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-04 (234 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+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 1826550] Re: Fractional scaling options do not appear with multiple monitors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1826550 Title: Fractional scaling options do not appear with multiple monitors Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using 19.04 disco with Wayland. I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor. I have enabled the experimental fractional scaling support. When no external monitor is connected, the fractional scaling options are displayed as expected. When the external monitor is connected, only the old whole number scaling options are displayed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 14:32:55 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-04 (234 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+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 1615116] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1615116 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade Status in gconf package in Ubuntu: Confirmed Bug description: Error received when upgrading from 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 19 18:49:10 2016 ErrorMessage: beroendeproblem - lämnar utlösare obehandlade InstallationDate: Installed on 2016-02-08 (193 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu2 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1615116/+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 1669632] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1669632 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 2 20:56:22 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-10 (326 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1669632/+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 1634151] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1634151 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld Status in gconf package in Ubuntu: New Bug description: Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system the message occured ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 13:29:10 2016 ErrorMessage: vereistenproblemen - triggers blijven onbehandeld InstallationDate: Installed on 2016-05-04 (166 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1634151/+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 1681137] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1681137 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: while upgrading from 16.04 to 16.10, it gave me this bug.. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Apr 9 01:01:29 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-08-01 (250 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-04-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1681137/+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 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1632415 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: error after updating from 16.04.1 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 11 22:08:46 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-25 (78 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1632415/+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 1741658] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623
** This bug has been marked a duplicate of bug 1551623
package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems
- leaving triggers unprocessed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1741658
Title:
package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
Status in gconf package in Ubuntu:
New
Bug description:
System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not
installed:
I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others.
Translated:
Failed to install during the systemupgrade:
==
gconf2 (+ "gconf2 will possibly not work")
gnupg-agent
gnupg2
libgdata22
gvfs-backends
adwaita-icon-theme-full
libgail-3-0
gstreamer1.0-plugins-bad
gstreamer0.10-plugins-good
gstreamer1.10-plugins-good
libgssdp-1.0-3
libupnp-1.0-4
libupnp-igd-1.0-4
libnice10
gstreamer1.0-nice
libfarstream-0.2-5
libpurple0
gnome-keyring
libgpgme11
libgmime-2.6-0
libwebkitgtk-3.0-0
geary
gnome-icon-theme
===
Hope the list is complete :-))
Since then only logging-out is possible, but the menu items: "Close the
system" ("Afsluiten" in Dutch) nor "Restart" gave any effect. Caption of this
menu is:
Lubuntu
Session Zorin-OS-lite 16.04
Best regards!
Dirk De Backer
mailto:debacker.d...@worldonline.be
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Jan 6 15:32:06 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-12-19 (748 days ago)
InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.3
apt 1.2.24
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1741658/+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 1636962] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1636962 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 26 23:42:05 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-27 (181 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1636962/+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 1656553] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1645117 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1656553 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: Error during partial update from 16.04 LTS to 16.10. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 Date: Sat Jan 14 15:46:26 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-12-14 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1656553/+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 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645117 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: -- ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Sun Nov 27 21:29:34 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-09-03 (85 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645117/+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
