[Touch-packages] [Bug 1986619] Re: Fail to install base-passwd
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1986619 Title: Fail to install base-passwd Status in base-passwd package in Ubuntu: Confirmed Bug description: /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb (Reading database ... 236425 files and directories currently installed.) Preparing to unpack base-passwd_3.5.52build1_amd64.deb ... Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ... Setting up base-passwd (3.5.52build1) ... Changing home-directory of irc from /var/run/ircd to /run/ircd 1 changes have been made, rewriting files Writing passwd-file to /etc/passwd Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission denied dpkg: error processing package base-passwd (--install): installed base-passwd package post-installation script subprocess returned error exit status 4 Errors were encountered while processing: base-passwd root@CNQDSX:/home/frank/Downloads# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1986619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028571] Re: klibc-utils contains identical binaries
This is fixed upstream with: https://git.kernel.org/pub/scm/libs/klibc/klibc.git/commit/?id=d16525038612be94cf2573c02eac8c7f76321f62 It's about time to make a new upstream release, so I will aim to do that and the Debian update this week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2028571 Title: klibc-utils contains identical binaries Status in klibc package in Ubuntu: Confirmed Bug description: ``` $ jdupes -r /usr/lib/klibc/bin Scanning: 38 files, 1 items (in 1 specified) /usr/lib/klibc/bin/gunzip /usr/lib/klibc/bin/gzip /usr/lib/klibc/bin/zcat /usr/lib/klibc/bin/halt /usr/lib/klibc/bin/poweroff /usr/lib/klibc/bin/reboot ``` Please replace these binaries with symlinks to reduce the size of the uncompressed initramfs. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: klibc-utils 2.0.12-1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jul 24 21:14:36 2023 Dependencies: libklibc 2.0.12-1 InstallationDate: Installed on 2022-03-20 (491 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: klibc UpgradeStatus: Upgraded to lunar on 2023-04-20 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/2028571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2021929] [NEW] upgrade to exiv2 0.28.0
Public bug reported: The latest release is 0.28.0 and fixes some bugs I've encountered https://github.com/Exiv2/exiv2/releases/tag/v0.28.0 ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/2021929 Title: upgrade to exiv2 0.28.0 Status in exiv2 package in Ubuntu: New Bug description: The latest release is 0.28.0 and fixes some bugs I've encountered https://github.com/Exiv2/exiv2/releases/tag/v0.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/2021929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
A couple of days ago I upgraded my 21.10 system to 22.04 and got this "out of memory" issue (Dell XPS 15 9550 with 3840x2160 display). The fix in comment #41 worked (changing the compression to 19), and the sequence of commands in #44 helped. However, just noting that there are several typos in #44 that had me stumped for a while (it's the first time I've used chroot to update grub). So here are (I think!) the corrected commands to update grub: $ sudo su - # mkdir root # mkdir boot # mkdir efi # cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt # mount /dev/mapper/vgubuntu-root ./root # mount /dev/nvme0n1p1 ./efi # was "nvme01p1" # mount /dev/nvme0n1p2 ./boot # was "nvme01p2" # mount -B ./boot ./root/boot # mount -B ./efi ./root/boot/efi # mount -B /dev ./root/dev # was: mount -B ./dev ./root/boot/dev # mount -B /dev/pts ./root/dev/pts # was: mount -B ./dev/pts ./root/boot/dev/pts # mount -B /proc ./root/proc # was: mount -B ./proc ./root/proc # mount -B /sys ./root/sys # was: mount -B ./sys ./root/sys # chroot ./root # ### Now edit line 196 of /usr/sbin/mkinitramfs to to use -19 instead of -1 # update-initramfs -u -k all # update-grub # exit # reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Joseph, out of interest, what model of XPS 13 do you have? I'm getting new XPS 13 soon and wondering if it'll have the same issue (I guess it's likely given the 4k screen). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/
[Touch-packages] [Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04
I also can’t install it on my i9 12900k system. Some people have suggested that it might help do deactivate TPM but as I am using Windows 11 for gaming this is not an option for me unfortunately. Also on my T14 no problem with TPM! (i5 10310u) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
I can say, that I have this dialog only if I have a flatpak updates, not apt updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: New Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939211] [NEW] Screen flickering after upgrading from 5.8 kernel to 5.11 kernel
Public bug reported: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_l80o1s@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_l80o1s ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd05/27/2021:br1.14:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1939211 Title: Screen flickering after upgrading from 5.8 kernel to 5.11 kernel Status in xorg package in Ubuntu: New Bug description: Hello! After the upgrade to the 5.8 series kernel to the 5.11 series kernel, I have noticed some screen flickering. I had the same problem previously on Fedora after upgrading to the 5.0 series kernel, but this was not present on Ubuntu 20.04 on either the 5.4 or 5.8 series kernels. On Fedora, it was fixed by turning off panel self-refresh on my Dell XPS 13 9380. I can try that again here if you all think it would be a useful piece of information. In the Fedora bug, it was reported that this problem is fixed in the 5.13 kernel. Let me know whatever else I can do. Thanks! Ben ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 18:56:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2021-06-24 (44 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM
[Touch-packages] [Bug 1924964] [NEW] screen glitches
Public bug reported: The issue is screen glitches issue is intermittent and temporary I think it started after a recent update But it gives the impression of an unstable system things flickering like a highlighted file in nautilus or in filezilla shadows under dialog boxes flickering the icons in the activities bar flickering like its displayed twice but scrolled vertically there are flickers of the other apps behind each, and some appear highlighted as they do when you put your mouse over them by scrolling them manually and running mouse over them seemed to get it to stop it didn't stop immediately but it did sometimes unresponsive apps like zoom sometimes zoom showing empty dialog a symptom that has existed for a while in nautilus when deep in a directory structure the top bar containing directory names flickers like its scrolling horizontally. I click on a higher folder to get it to stop all the above happen regardless of where the mouse is in gedit with multiple tabs open one tab (the tab) appeared blank no file name, no flickering Ubuntu 20.04.2 LTS Laptop model Asus N550JV old 16GB RAM mouse is new but basic wired J.BURROWS had to replace small one becuase button got stuck and it kept double clicking when i only single clicked Additional relevant I recently updated twice normally I wait a while perhaps a month before I update I think it started after a recent update Additional I do have many app running at the same time many opera windows 5+ with many tabs each 30+ which drains my ram 16GB Has both NVIDIA and built in INTEL graphics at the time NVIDIA is turned off using INTEL could be related to RAM or maybe mouse Additional minor after latest update my desktop wallpaper which was just ubuntu 20.04 default now appears black in settings I can choose others and they display, but choose the one it was it stays black actually I would like an option for black. save power graphics CPU I really would like a ubuntu without screen glitches Thank you for your time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 15:58:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2020-09-08 (222 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=UUID=18f3ecb2-cebb-4134-aa73-7d85d52089a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.204:bd05/14/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1924964 Title: screen glitches Status in xorg package in Ubuntu: New Bug description: The issue is screen glitches issue is intermittent and temporary I think it started after a recent up
[Touch-packages] [Bug 1904924] [NEW] Xorg freeze
Public bug reported: Sounds like a fairly common problem according to [this page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display freezes, and while I'm still able to move the mouse around, I can't successfully click or type at any windows. It takes about 30 seconds for gnome-shell to restart, and then the clock starts running (and the system monitor starts updating) again. This problem has been bugging me for a few months now, but I'm not sure when it started. It tends to happen in clumps; sometimes it will go several days without happening, but once it starts it often happens twice pretty quickly, and often a few times across a day. I haven't been able to isolate what causes it, but more often than not it has something to do with clicking on a window or tab in Chrome. (It definitely also happens in other applications, though.) Every time it happens, dmesg contains a stack dump for gnome-shell ("page allocation failure"). I can provide gists of these dumps if that's helpful (and not already included in the apport data). So I'm not sure if this is actually an xorg thing or a gnome-shell thing. % lsb_release -rd Description:Ubuntu 20.10 Release:20.10 % dpkg -l xorg* gnome-shell* | grep '^ii' ii gnome-shell 3.38.1-1ubuntu1.1 amd64graphical shell for the GNOME desktop ii gnome-shell-common 3.38.1-1ubuntu1.1 all common files for the GNOME graphical shell ii gnome-shell-extension-appindicator 34-1 all AppIndicator/KStatusNotifierItem support for GNOME Shell ii gnome-shell-extension-desktop-icons 20.04.0+git20200908-1 all desktop icon support for GNOME Shell ii gnome-shell-extension-prefs 3.38.1-1ubuntu1.1 amd64tool to enable / disable GNOME Shell extensions ii gnome-shell-extension-system-monitor 38+git20200414-32cc79e-1 all Display system information in GNOME Shell status bar ii gnome-shell-extension-system76-power 2.0.0~1602857239~20.10~914b531~dev all Gnome-shell extension for System76 Power Management ii gnome-shell-extension-ubuntu-dock68ubuntu20.10.1 all Ubuntu Dock for GNOME Shell ii gnome-shell-extensions 3.38.1-1 all Extensions to extend functionality of GNOME Shell ii xorg 1:7.7+19ubuntu15 amd64X.Org X Window System ii xorg-docs-core 1:1.7.1-1.1 all Core documentation for the X.org X Window System ii xorg-sgml-doctools 1:1.11-1 all Common tools for building X.Org SGML documentation ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108806~20.10~7e52b13~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 15:05:17 2020 DistUpgraded: 2020-11-16 10:15:57,099 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu 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-01-19 (1035 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7630-generic root=UUID=e12a4ebc-6235-4471-a2da-3f9da9d48f74 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-11-16
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Noticed that I couldn't use my headset mic on any apps in the past month, but the above reports are describing the same behavioural issues as I am seeing soI think I am hitting the same problem. Using Sennheisser HD 4.40BT headphones on a System76 Gazelle. Connects default audio through headphones with the A2DP profile as expected when connecting through BT, but the Internal Microphone stays selected for input. Trying to select the HD4.4 microphone setting does nothing, and no signal of any kind comes through the input. Switching to the HFP/HSP profile also leads to a break in audio, and after the A2DP setting is shown as unavailable until I wipe the userland pulse configs. It cuts off the audio through the headset and ends up in a bad configuration where I have to turn BT off and on again to reconnect and when it does, the configuration is stuck on HFP/HSP and in mono. No audio through the headset mic can be picked up through any pulseaudio-enabled monitors, all showing zero input with whatever configuration or set-up I can muster. Running Linux pop-os 5.4.0-7642-generic #46~1598628707~20.04~040157c- Ubuntu SMP Fri Aug 28 18:02:16 UTC x86_64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887289] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: System version detection falsh ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 12 16:22:11 2020 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2019-10-17 (268 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1887289 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 Status in initramfs-tools package in Ubuntu: New Bug description: System version detection falsh ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 12 16:22:11 2020 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2019-10-17 (268 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1887289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
+1 to bionic backport please -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Expired Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 After looking through the posted bug and comments I'm not sure that the issues are related. It seems more like, in this case, GNOME is just out of sync with pulse about what the default device is thanks to pulse changing it out during login. Changing the selected device fixes the issue (until the next login). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device Status in pulseaudio package in Ubuntu: New Bug description: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 Is it supposed to switch back on reboot though? If I select a certain device I expect it to stay that way. It's not like I'm unplugging and replugging my USB device. From a user's perspective this certainly doesn't feel like the desired behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio still outputs using my previously-selected device Status in pulseaudio package in Ubuntu: New Bug description: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869513] [NEW] package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1
Public bug reported: /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by /usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::ChannelList::insert(char const*, Imf_2_2::Channel const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::hasChromaticities(Imf_2_2::Header const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::readPixels(int, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::channels() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::InputFile(char const*, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::insert(char const*, Imf_2_2::Slice const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::chromaticities(Imf_2_2::Header const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::globalThreadCount()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::header() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::writePixels(int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Channel::Channel(Imf_2_2::PixelType, int, int, bool)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::begin()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Slice::Slice(Imf_2_2::PixelType, char*, unsigned long, unsigned long, int, int, double, bool, bool)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::dataWindow() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::channels()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::~Header()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::OutputFile(char const*, Imf_2_2::Header const&, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::ChannelList::findChannel(char const*) const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::end()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::Header(int, int, float, Imath_2_2::Vec2 const&, float, Imf_2_2::LineOrder, Imf_2_2::Compression)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Chromaticities::Chromaticities(Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::~OutputFile()' collect2: error: ld returned 1 exit status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openexr 2.3.0-6build1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 27 15:58:19 2020 ErrorMessage: installed openexr package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-11-27 (121 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.1 SourcePackage: openexr Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago) ** Affects: openexr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1869513 Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1 Status in openexr package in Ubuntu: New Bug description: /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by /usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or
[Touch-packages] [Bug 1865088] Re: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
I notice that the output from setupcon mentions loading the font twice. That seems to correspond to this fragment of code in setupcon: # FONTFILES FONTFILES='' if [ "$FONT" ]; then for f in $FONT; do FONTFILES="$FONTFILES `findfile $fontdir $f`" RES=`findfile $fontdir $f` if [ -z "$RES" ]; then fdec="${f%.gz}" RES=`findfile $fontdir $fdec` fi FONTFILES="$FONTFILES $RES" done fi It looks to me like this will add each font file to FONTFILES twice, once in the first line of the loop body, and once in the last. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1865088 Title: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument" Status in console-setup package in Ubuntu: New Bug description: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865088] [NEW] setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
Public bug reported: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ** Attachment added: "Output from "setupcon -v test2"" https://bugs.launchpad.net/bugs/1865088/+attachment/5331723/+files/setupcon.out -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1865088 Title: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument" Status in console-setup package in Ubuntu: New Bug description: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan
Steve Langasek wrote: > The root failure is: > objcopy -O binary usr/klibc/syscalls/typesize.o > usr/klibc/syscalls/typesize.bin > mkdir -p usr/include/klibc/; perl /tmp/klibc-2.0.6/usr/klibc/syscalls.pl -2 > usr/klibc/syscalls/SYSCALLS.i > /tmp/klibc-2.0.6/usr/klibc/arch/x86_64/sysstub.ph x86_64 64 > usr/klibc/syscalls/syscalls.nrs usr/klibc/syscalls > usr/include/klibc/havesyscall.h usr/klibc/syscalls/typesize.bin > > usr/klibc/syscalls/syscalls.mk || ( rm -f usr/klibc/syscalls/syscalls.mk ; > exit 1 ) > [...] > /tmp/klibc-2.0.6/usr/klibc/syscalls.pl: usr/klibc/syscalls/typesize.bin: > magic number not found Thanks, I wasn't able to access the build log so I didn't see this. Adam Conrad wrote: > 2.0.7-1 fails to build in the same way on Ubuntu 19.10. I'm assuming it's > either glibc 2.30 (Debian is at 2.29) or linux 5.3 (Debian is at 5.2), with > the latter being more likely. I tested upstream with Linux 5.3 headers, and klibc doesn't use glibc, so it's unlikely to be either of those. The best guess I can come up with is that there's something different about the compiler defaults you're using that causes "objcopy -O binary" to not include static data in the output. objcopy itself probably isn't the difference as Debian unstable and Ubuntu eoan seem to have the same version of binutils. (But I wonder whether the objcopy is even necessary. syscalls.pl doesn't require the magic number to be at the beginning of the file, so presumably it would also work with a regular ELF object file.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
(In reply to Takashi Iwai from comment #127) > Hm, interesting, AZX_DCAPS_POSFIX_LPIB basically sets the position reporting > based on LPIB instead of the position buffer. I thought the position buffer > isn't available or unreliable on non-Intel chips, but it might be different > on the recent AMD one. Contrary to what Ernst experienced, removing AZX_DCAPS_POSFIX_LPIB completely broke audio on my system (ASUS PRIME X470, also 1022:1457), so I guess it's still unreliable as you mentioned. Was looking through the pci_ids array in sound/pci/hda/hda_intel.c and noticed that my audio controller (1022:1457) isn't listed. The only thing I can see that would match is the following, which seems to be intended for AMD GPUs. { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_ANY_ID), .class = PCI_CLASS_MULTIMEDIA_HD_AUDIO << 8, .class_mask = 0xff, .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_HDMI }, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
IS this fix now implemented to the latest ISO available for download? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: In Progress Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838577] [NEW] Default audio device changes on reboot; audio still outputs using my previously-selected device
Public bug reported: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and Gnome shell / Gnome settings volume control adjusts the USB speaker volume. Despite seeing the USB device as the current output device, I still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic cosmic disco eoan ** Description changed: This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It was not present in Ubuntu 16.04. I have a USB microphone which also appears to pulse as a speaker. Pulse keeps picking it as the default audio device. I can switch audio devices to my analog line out, which works as expected until I reboot. After reboot, my audio device switches back to the USB "speaker", and - volume control adjusts the USB speaker volume. Despite pulse seeing the - USB device as the current output device, I still hear sound from my - line-out. + Gnome shell / Gnome settings volume control adjusts the USB speaker + volume. Despite seeing the USB device as the current output device, I + still hear sound from my line-out. In the interest of narrowing down this bug, I have found that disabling "module-switch-on-connect" fixes the problem (my line-out stays as the default audio device and I hear sound). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 17:39:38 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838577 Title: Default audio device changes on reboot; audio stil
[Touch-packages] [Bug 1801540]
(In reply to Marco from comment #100) > Yea, I'm still trying to find the energy to begin to write a parser for the > codec commands, but this will surely take quite a lot of time. This actually sounds like something I would be interested in working on. However I don't really have any experience working with low level audio like this. Are the dumps you gave for the ALC892? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
Is there a workaround? This is currently breaking my entire audio setup (using Ubuntu Studio, where jackd is crucial) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory
How does one upgrade to systemd-241 in ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Unknown Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832651] [NEW] jackdbus fails to start: cannot allocate memory
Public bug reported: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in jackd2 package in Ubuntu: New Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1832651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792164] Re: ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf
This bug affects far more than 2 users. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1792164 Title: ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf Status in python2.7 package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 python2.7: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 -Python 2.7.15rc1 has the problem below --- $ python Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import fpectl Traceback (most recent call last): File "", line 1, in ImportError: No module named fpectl >>> import sysconfig >>> print sysconfig.get_config_var('CONFIG_ARGS') '--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4' '--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos' '--with-system-ffi' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-nbjU53/python2.7-2.7.15~rc1=. -fstack-protector-strong -Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' >>> --while Python 2.7.12 has no problem --- $ python Python 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import fpectl >>> import sysconfig >>> print sysconfig.get_config_var('CONFIG_ARGS') '--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4' '--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos' '--with-system-ffi' '--with-fpectl' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' >>> -- Please help to check '--with-fpectl' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1792164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821496] [NEW] Sennheiser GSX 1000/1200 Volume control is interpreted badly
Public bug reported: These cards are picked up as having mute/VolUp/VolDown buttons, but they only ever report a VolDown. Windows behavior (without manually installed drivers) appears to match OS-side volume to the display on the card, which suggests the card tries to report its volume level as an absolute value. Ubuntu interprets it as turning the volume down (even if the volume was actually turned up). My workaround was to remap the "buttons" on the card to "reserved" using the hwdb and manage OS-side volume with media keys on my actual keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 90-pulseaudio-local.rules 70-snap.core.rules Date: Sat Mar 23 23:42:31 2019 InstallationDate: Installed on 2018-09-12 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series 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-16-generic root=UUID=fec38878-ce70-47ad-a40b-7710266eb99b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1821496 Title: Sennheiser GSX 1000/1200 Volume control is interpreted badly Status in systemd package in Ubuntu: New Bug description: These cards are picked up as having mute/VolUp/VolDown buttons, but they only ever report a VolDown. Windows behavior (without manually installed drivers) appears to match OS-side volume to the display on the card, which suggests the card tries to report its volume level as an absolute value. Ubuntu interprets it as turning the volume down (even if the volume was actually turned up). My workaround was to remap the "buttons" on the card to "reserved" using the hwdb and manage OS-side volume with media keys on my actual keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 90-pulseaudio-local.rules 70-snap.core.rules Date: Sat Mar 23 23:42:31 2019 InstallationDate: Installed on 2018-09-12 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series 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-16-generic root=UUID=fec38878-ce70-47ad-a40b-7710266eb99b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1821494] [NEW] Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping
Public bug reported: Similar to the Steelseries Arctis headphones, these sound "cards" present as two output devices, one intended for voice chat and one for everything else. As a result they also need a special profile. But there's another complication. They also have hardware HRTF that requires no special driver logic; instead, the "everything else" output pretends to be 7.1, and simply applies the HRTF to the streams sent by the host. However, the channel mappings picked up by ALSA are wrong -- the rear speakers and center/LFE are swapped. I know, technically this is two bugs, but they have the same fix which is impractical to separate. I'm attaching a "sennheiser-gsx.conf" based on the Arctis 7 profile that both corrects the channel mapping and exposes both output subdevices. A simple udev rule seals the deal: ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e", ENV{PULSE_PROFILE_SET }="sennheiser-gsx.conf" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: roothorick 7548 F pulseaudio /dev/snd/controlC2: roothorick 7548 F pulseaudio /dev/snd/controlC0: roothorick 7548 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 23:09:21 2019 InstallationDate: Installed on 2018-09-12 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2019-03-23T20:51:33.488207 mtime.conffile..etc.pulse.default.pa: 2019-03-23T23:03:49.029912 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "sennheiser-gsx.conf" https://bugs.launchpad.net/bugs/1821494/+attachment/5248935/+files/sennheiser-gsx.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1821494 Title: Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping Status in pulseaudio package in Ubuntu: New Bug description: Similar to the Steelseries Arctis headphones, these sound "cards" present as two output devices, one intended for voice chat and one for everything else. As a result they also need a special profile. But there's another complication. They also have hardware HRTF that requires no special driver logic; instead, the "everything else" output pretends to be 7.1, and simply applies the HRTF to the streams sent by the host. However, the channel mappings picked up by ALSA are wrong -- the rear speakers and center/LFE are swapped. I know, technically this is two bugs, but they have the same fix which is impractical to separate. I'm attaching a "sennheiser-gsx.conf" based on the Arctis 7 profile that both corrects the channel mapping and exposes both output subdevices. A simple udev rule seals the deal: ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e", ENV{PULSE_PROFILE_SET}="sennheiser-gsx.conf" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: roothorick 7548 F pulseaudio /dev/snd/controlC2: roothorick 7548 F pulseaudio /dev/snd/controlC0: roothorick 7548 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 23:09:21 2019 InstallationDate: Installed on 2018-09-12 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beave
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The UX391UA fix is not in 4.20 as it was already a release candidate. To get sound working on this model you'll need to download the 4.20 source, apply the patch to sound/pci/hda/patch_realtek.c then compile and install the kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224923/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224921/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224917/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224916/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224919/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224918/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224922/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224920/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224915/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224913/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224914/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStatus: amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H Package: wayland (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic wayland-session ubuntu Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-DS3H dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809656] Re: Small windows output corrupted in XWayland clients
apport information ** Tags added: apport-collected bionic ubuntu wayland-session ** Description changed: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + 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: pop:GNOME + DistUpgraded: Fresh install + DistroCodename: bionic + DistroRelease: Pop!_OS 18.04 + DistroVariant: ubuntu + DkmsStatus: + amdgpu, 18.50-708488, 4.15.0-43-generic, x86_64: installed + system76, 1.0.1~1545237826~18.04~2159d22, 4.15.0-43-generic, x86_64: installed + system76-io, 1.0.0~1543900015~18.04~6bb2635, 4.15.0-43-generic, x86_64: installed + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Radeon RX 560] [1462:8a91] + MachineType: Gigabyte Technology Co., Ltd. AB350M-DS3H + Package: wayland (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: initrd=\EFI\Pop_OS-0761529f-4dc5-49e6-8f97-d98396dba3d6\initrd.img root=UUID=0761529f-4dc5-49e6-8f97-d98396dba3d6 ro quiet loglevel=0 systemd.show_status=false splash + ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 + Tags: bionic wayland-session ubuntu + Uname: Linux 4.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm sudo + _MarkForUpload: True + dmi.bios.date: 08/08/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F23 + dmi.board.asset.tag: Default string + dmi.board.name: AB350M-DS3H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: AB350M-DS3H + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.91-2 + version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1pop0 + version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1pop0 + version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1809656/+attachment/5224912/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 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: pop:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Pop!_OS 18.04 DistroVariant: ubuntu DkmsStat
[Touch-packages] [Bug 1809656] [NEW] Small windows output corrupted in XWayland clients
Public bug reported: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Снимок экрана от 2018-12-24 13-38-38.png" https://bugs.launchpad.net/bugs/1809656/+attachment/5224638/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202018-12-24%2013-38-38.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients Status in wayland package in Ubuntu: New Bug description: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@sojusnik Yes, you're right, I missed the closing bracket. The correct line to add is: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK), You won't find patch_realtek.c anywhere in /lib/modules/ because it's already been compiled and installed. You need to download the source code, apply the patches, then compile and install the kernel. Try downloading the 4.20-rc7 from kernel.org (the patches are already applied to this version), extract it, and then edit /sound/pci/hda/patch_realtek.c Look for this line: SND_PCI_QUIRK(0x1043, 0x14a1, "ASUS UX533FD", ALC294_FIXUP_ASUS_SPK), And beneath it add: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK), If you then compile and install the kernel, you should have working sound on your UX391UA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The fixes in the 4.20-rc kernels are for other laptops, not the UX391UA. You'll need to add: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK to /sound/pci/hda/patch_realtek.c to get sound working on this laptop. I used the 4.19.9 kernel, applied the 3 linked patches and added the line above. If you're using 4.20-rc6 / 7, you may only need to add the line to patch_realtek.c -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Also works for me @vblack2006 I downloaded the current stable kernel from kernel.org (4.19.9), applied the 3 patches that you linked to and added: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK to /sound/pci/hda/patch_realtek.c After compiling and installing, I now have sound working on my UX391UA running Fedora 29! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I got an error when building the modules from @VanVan's github due to /sound/pci/hda_codec.h having been moved to /include/sound/hda_codec.h Fixing this let the compile finish without error (this is on Fedora 29). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I've compiled 4.20-rc6 from VanVan's github repository, and it has no effect on my UX391UA - still no sound. I notice the patch doesn't actually refer specifically to the UX931UA though, only other ASUS models. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793433] Re: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I was able to workaround this problem by following Mauricio Grueso's suggestion in bug #1776652: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1776652 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1793433 Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Triaged Bug description: unable to update to any newer kernel after upgrade. stuck on version linux-image-4.15.0-32-generic currently. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: viral 4203 F pulseaudio /dev/snd/controlC0: viral 4203 F pulseaudio Date: Wed Sep 19 22:56:45 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=c358033e-93c3-4821-b8fd-cfe6862d5a91 InstallationDate: Installed on 2011-10-06 (2541 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: eth3 no wireless extensions. lono wireless extensions. eth1 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=1a3abf75-9125-457a-b20c-b45dc6774fd9 ro quiet splash security=selinux selinux=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1793433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
Thanks for getting back to me! I no longer have this piece of hardware so it's ok for me to close this one for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php&p_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1741128] Re: libmagic1 in 16.04 reports XLS files as application/CDFV2-unknown
This bug was fixed upstream almost a year ago. It would be nice to see this addressed in Ubuntu 16.04 LTS, which is still on libmagic1 version 5.25. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1741128 Title: libmagic1 in 16.04 reports XLS files as application/CDFV2-unknown Status in file package in Ubuntu: Confirmed Bug description: The libmagic1 package repots XLS files as application/CDFV2-unknown This is a bug in the libmagic code and has been fixed in version 5.31 and up. see: https://github.com/mscdex/mmmagic/issues/107 We have a file transfer app running on LTS 16.04 and it's constantly rejecting files of .xls Deleted /companies/5412/FROM/RDMS_History.XLS Mime Type:application/CDFV2-unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1741128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795698] [NEW] Cannot communicate with bitbucket repo through ssh
Public bug reported: After upgrading to kernal 4.15.0-36.39~16.04.1 this morning (2018-10-02) I am no longer able to communicate with remote repos using ssh keys. Reverting back to the previous kernal ( 4.15.0-34.37~16.04.1 ) fixes this issue. Git version is 2.19.0 1) Description: Ubuntu 16.04.5 LTS Release: 16.04 2) Unsure of the specific package that is the issue. There is something different between the two kernals mentioned. The latest kernal is causing the issue. 3) When performing any git commands that require communication with the remote I expect that I will get some communication back from the remote about the success or failure of the request. 4) What actually happens is any action that requires interaction with the remote simply hangs indefinitely. There is no success or failure. It simply hangs until I kill the process with crtl+c. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: 16.04.5 git lts ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1795698 Title: Cannot communicate with bitbucket repo through ssh Status in initramfs-tools package in Ubuntu: New Bug description: After upgrading to kernal 4.15.0-36.39~16.04.1 this morning (2018-10-02) I am no longer able to communicate with remote repos using ssh keys. Reverting back to the previous kernal ( 4.15.0-34.37~16.04.1 ) fixes this issue. Git version is 2.19.0 1) Description: Ubuntu 16.04.5 LTS Release: 16.04 2) Unsure of the specific package that is the issue. There is something different between the two kernals mentioned. The latest kernal is causing the issue. 3) When performing any git commands that require communication with the remote I expect that I will get some communication back from the remote about the success or failure of the request. 4) What actually happens is any action that requires interaction with the remote simply hangs indefinitely. There is no success or failure. It simply hangs until I kill the process with crtl+c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1795698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792164] [NEW] ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 python2.7: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 -Python 2.7.15rc1 has the problem below --- $ python Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import fpectl Traceback (most recent call last): File "", line 1, in ImportError: No module named fpectl >>> import sysconfig >>> print sysconfig.get_config_var('CONFIG_ARGS') '--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4' '--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos' '--with-system-ffi' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-nbjU53/python2.7-2.7.15~rc1=. -fstack-protector-strong -Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' >>> --while Python 2.7.12 has no problem --- $ python Python 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import fpectl >>> import sysconfig >>> print sysconfig.get_config_var('CONFIG_ARGS') '--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4' '--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos' '--with-system-ffi' '--with-fpectl' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' >>> -- Please help to check '--with-fpectl' ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1792164 Title: ImportError: /PATH/xxx.so: undefined symbol: PyFPE_jbuf Status in python2.7 package in Ubuntu: New Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 python2.7: Installed: 2.7.15~rc1-1 Candidate: 2.7.15~rc1-1 -Python 2.7.15rc1 has the problem below --- $ python Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import fpectl Traceback (most recent call last): File "", line 1, in ImportError: No module named fpectl >>> import sysconfig >>> print sysconfig.get_config_var('CONFIG_ARGS') '--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4' '--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos' '--with-system-ffi' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-nbjU53/python2.7-2.7.15~rc1=. -fstack-protector-strong -Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' >>> --while Python 2.7.12 has no problem --- $ python Python 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import fpectl >>> import sysconfig >>> print sysconfig.get_config_var('CONFIG_ARGS') '--enable-shared' '--prefix=/usr' '--enable-ipv6' '--enable-unicode=ucs4' '--with-dbmliborder=bdb:gdbm' '--with-system-expat' '--with-computed-gotos' '--with-system-ffi' '--with-fpectl' 'CC=x86_64-linux-gnu-gcc' 'CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security ' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' >>> -- Please help to check '--with-fpectl' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1792164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
*** This bug is a duplicate of bug 1768610 *** https://bugs.launchpad.net/bugs/1768610 I had these exact same symptoms today with my nVidia GTX 960 after doing a platform upgrade from 17.10 to 18.04. Issue was actually dead simple to fix, the upgrade to 18.04 removed some PPAs (including the graphics drivers), so although the nVidia driver package was present on the system it wasn't getting updates and the system appears to have selected a software only driver to use instead. All I did was uninstall nvidia-390 using apt, re-added the ppa, apt-get updated, then reinstalled nvidia-390 again using apt. Fixed it fine for me. ### sudo apt-get autoremove nvidia-390 sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-390 ### hope this is useful :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration Status in nux package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. Apparently the problem is that nux-tools is not purged, leaving the above file (also see #1768610). > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
Hey all, Kubuntu (which means plasma and KDE) is no exception. Running default config. But for some time it worked. So it must have been in an update of the past few weeks, It's not just alt+arrow for me. Even alt+f1 through alt+f8 will switch (to) console. I guess this is a problem: $ sudo dumpkeys | grep -E '(\W+)alt(\W+)keycode.*Cons' alt keycode 59 = Console_1 shift alt keycode 59 = Console_13 control alt keycode 59 = Console_1 shift control alt keycode 59 = Console_13 alt keycode 60 = Console_2 shift alt keycode 60 = Console_14 control alt keycode 60 = Console_2 shift control alt keycode 60 = Console_14 alt keycode 61 = Console_3 shift alt keycode 61 = Console_15 control alt keycode 61 = Console_3 shift control alt keycode 61 = Console_15 alt keycode 62 = Console_4 shift alt keycode 62 = Console_16 control alt keycode 62 = Console_4 shift control alt keycode 62 = Console_16 alt keycode 63 = Console_5 shift alt keycode 63 = Console_17 control alt keycode 63 = Console_5 shift control alt keycode 63 = Console_17 alt keycode 64 = Console_6 shift alt keycode 64 = Console_18 control alt keycode 64 = Console_6 shift control alt keycode 64 = Console_18 alt keycode 65 = Console_7 shift alt keycode 65 = Console_19 control alt keycode 65 = Console_7 shift control alt keycode 65 = Console_19 alt keycode 66 = Console_8 shift alt keycode 66 = Console_20 control alt keycode 66 = Console_8 shift control alt keycode 66 = Console_20 alt keycode 67 = Console_9 shift alt keycode 67 = Console_21 control alt keycode 67 = Console_9 shift control alt keycode 67 = Console_21 alt keycode 68 = Console_10 shift alt keycode 68 = Console_22 control alt keycode 68 = Console_10 shift control alt keycode 68 = Console_22 alt keycode 87 = Console_11 shift alt keycode 87 = Console_23 control alt keycode 87 = Console_11 shift control alt keycode 87 = Console_23 alt keycode 88 = Console_12 shift alt keycode 88 = Console_24 control alt keycode 88 = Console_12 shift control alt keycode 88 = Console_24 alt keycode 99 = Last_Console shift alt keycode 99 = Last_Console altgr alt keycode 99 = Last_Console shift altgr alt keycode 99 = Last_Console alt keycode 105 = Decr_Console alt keycode 106 = Incr_Console -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
I just modified comment 31 (https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1508146/comments/31): $ sudo dumpkeys | grep -v -E '^(\W+)alt(\W+)keycode.*Cons' | sudo loadkeys Everything with alt at the beginning and Console will not switch (to) consoles anymore. ** Also affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778366] [NEW] apt.package.Version.raw_description doesn’t work
Public bug reported: The raw_description property of apt.package.Version returns the summary rather than the long description. This is because it accesses self._records instead of self._translated_records, and the long description is located only in the translated records. Ubuntu 18.04 LTS python3-apt 1.6.1 ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1778366 Title: apt.package.Version.raw_description doesn’t work Status in python-apt package in Ubuntu: New Bug description: The raw_description property of apt.package.Version returns the summary rather than the long description. This is because it accesses self._records instead of self._translated_records, and the long description is located only in the translated records. Ubuntu 18.04 LTS python3-apt 1.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1778366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697535] Re: [Envy24 ICE1724] Audio doesn't work
This bug still exists in Ubuntu 18.04 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic $ pulseaudio --version pulseaudio 11.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1697535 Title: [Envy24 ICE1724] Audio doesn't work Status in pulseaudio package in Ubuntu: New Bug description: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1697535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
ahhh cool that helped. I have updated to 18.04 last week and did not come across any problems any more. gRTZ ben On Tue, 27 Mar 2018 at 11:20 DimanNe <1720...@bugs.launchpad.net> wrote: > Thank you, benvantende! Reinstalling pulseaudio has helped me too > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1720519 > > Title: > KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once > at most. Refusing to load. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions > -- ben van 't ende Web:* ben.vanten.de <http://ben.vanten.de/>* Tel: +31 (0)6 47074151 Email: b...@vantende.net Social: benvantende -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC0D0p: ben 2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747138] Re: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned
This happened to me upgrading from Artful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1747138 Title: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned Status in resolvconf package in Ubuntu: Confirmed Bug description: Happened on upgrade to bionic on 2/2. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu9 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sat Feb 3 00:58:50 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-08-19 (899 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150818) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: resolvconf Title: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1747138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755010] [NEW] package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Tried upgrading from Artful to Bionic this weekend, had problems. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 11 13:47:24 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-10-08 (153 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. G752VY ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=2bbeb898-f4c5-4a25-ba8d-f7874903809e ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: systemd Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VY.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G752VY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755010 Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned Status in systemd package in Ubuntu: New Bug description: Tried upgrading from Artful to Bionic this weekend, had problems. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 11 13:47:24 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-10-08 (153 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. G752VY ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=2bbeb898-f4c5-4a25-ba8d-f7874903809e ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: systemd Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VY.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G752VY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1755010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750411] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat
Public bug reported: No observed failure in user space - but I got a pop-up warning, so here we go... ProblemType: Package DistroRelease: Ubuntu 17.10 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: gcc-7-base:i386: Install libgcc1:i386: Install libc6:i386: Install libssl1.0.0:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Feb 19 17:40:49 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-19 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 172.26.45.1 dev enx8cae4cf6075e proto static metric 100 169.254.0.0/16 dev enx8cae4cf6075e scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.26.45.0/24 dev enx8cae4cf6075e proto kernel scope link src 172.26.45.67 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: network-manager Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2018-02-19 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/4 docker0 7cea7338-7829-47c6-979a-8ffd94d5819d /org/freedesktop/NetworkManager/ActiveConnection/2 enx8cae4cf6075e ethernet connected /org/freedesktop/NetworkManager/Devices/3 Wired connection 2 0b257ca3-b031-4a10-b4ec-319e8c4fcd2b /org/freedesktop/NetworkManager/ActiveConnection/1 wlp58s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1750411 Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in network-manager package in Ubuntu: New Bug description: No observed failure in user space - but I got a pop-up warning, so here we go... ProblemType: Package DistroRelease: Ubuntu 17.10 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: gcc-7-base:i386: Install libgcc1:i386: Install libc6:i386: Install libssl1.0.0:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Feb 19 17:40:49 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-19 (245 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 172.26.45.1 dev enx8cae4cf6075e proto static metric 100 169.254.0.0/16 dev enx8cae4cf6075e scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.26.45.0/24 dev enx8cae4cf6075e proto kernel scope link src 172.26.45.67 metric 100 NetworkManager.state: [main] Networ
[Touch-packages] [Bug 1697535] Re: [Envy24 ICE1724] Audio doesn't work
The bug still exists in Ubuntu 17.10. The following might be useful information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful $ pulseaudio --version pulseaudio 10.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1697535 Title: [Envy24 ICE1724] Audio doesn't work Status in pulseaudio package in Ubuntu: Incomplete Bug description: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1697535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697535] Re: [Envy24 ICE1724] Audio doesn't work
You also said to "change the bug status to Confirmed." It is my impression that I'm not supposed to do that since I'm the original reporter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1697535 Title: [Envy24 ICE1724] Audio doesn't work Status in pulseaudio package in Ubuntu: Incomplete Bug description: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1697535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734745] [NEW] NM assumes avahi ip addres and default gw for disconnected device
Public bug reported: I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet device is not connected at all. The WiFi is connected to WiFi network. The problem is, the connection drops itself after a while. I did some research and find out, the NM creates a new connection for the ethernet device, assuming Avahi IP for that connection, actually making this device a default route in a routing table. Thus, all outgoing packets are going through a non-connected ethernet device instead of gateway in WiFi network. See commands output for details. If I delete that default route manually, re-run dhclient to get a new route or disconnect enp9s0 using NM, the internet start working again. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "commands_output" https://bugs.launchpad.net/bugs/1734745/+attachment/5015325/+files/commands_output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1734745 Title: NM assumes avahi ip addres and default gw for disconnected device Status in network-manager package in Ubuntu: New Bug description: I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet device is not connected at all. The WiFi is connected to WiFi network. The problem is, the connection drops itself after a while. I did some research and find out, the NM creates a new connection for the ethernet device, assuming Avahi IP for that connection, actually making this device a default route in a routing table. Thus, all outgoing packets are going through a non-connected ethernet device instead of gateway in WiFi network. See commands output for details. If I delete that default route manually, re-run dhclient to get a new route or disconnect enp9s0 using NM, the internet start working again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722971] [NEW] USB sound card not detected
Public bug reported: also no PCI sound. Description:Ubuntu 17.04 Release:17.04 Kernel 4.10.0-32-generic reverting to kernel 4.10.0-30-generic works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Thu Oct 12 11:53:34 2017 InstallationDate: Installed on 2015-03-27 (929 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to zesty on 2017-08-05 (67 days ago) dmi.bios.date: 07/15/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L51 v01.23 dmi.board.asset.tag: SGH438QBLM dmi.board.name: 1905 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: SGH438QBLM dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL51v01.23:bd07/15/2014:svnHewlett-Packard:pnHPZ230TowerWorkstation:pvr:rvnHewlett-Packard:rn1905:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Z230 Tower Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1722971 Title: USB sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: also no PCI sound. Description: Ubuntu 17.04 Release: 17.04 Kernel 4.10.0-32-generic reverting to kernel 4.10.0-30-generic works ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Thu Oct 12 11:53:34 2017 InstallationDate: Installed on 2015-03-27 (929 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to zesty on 2017-08-05 (67 days ago) dmi.bios.date: 07/15/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L51 v01.23 dmi.board.asset.tag: SGH438QBLM dmi.board.name: 1905 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: SGH438QBLM dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL51v01.23:bd07/15/2014:svnHewlett-Packard:pnHPZ230TowerWorkstation:pvr:rvnHewlett-Packard:rn1905:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP Z230 Tower Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1722971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Good to know. Honestly for some weird reason the same bug re-appeared. I had to do the same again to solve that, but also removed Discord <https://discordapp.com/>. I vaguely remembered reading somewhere that could cause problems. For now all is fine. On Mon, 2 Oct 2017 at 21:41 David Eichelsdörfer <1720...@bugs.launchpad.net> wrote: > had the same problem and could only fix it by removing the line > load-module module-switch-on-connect > from > /etc/pulse/default.pa > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1720519 > > Title: > Module "module-switch-on-connect" should be loaded once at most. > Refusing to load. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/+subscriptions > -- ben van 't ende Web:* ben.vanten.de <http://ben.vanten.de/>* Tel: +31 (0)6 47074151 Email: b...@vantende.net Social: benvantende -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
fixed myself by reinstalling pulseaudio ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => ben van 't ende (benvantende) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F.... chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Heyla, After reading up some more I removed alsa and pulseaudio and reinstalled like this: sudo apt-get remove --purge alsa-base pulseaudio Now install again Alsa and Pulse Audio: sudo apt-get install alsa-base pulseaudio Then, reload Alsa: sudo alsa force-reload That made audio up and running again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] [NEW] Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Public bug reported: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. >From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
This bug has just hosed a system I installed for my parents. An unattended-upgrader that breaks your system if you don't attend to it IS broken. Having known about this problem for many years, the least you could have done is added a warning to the installer that choosing lvm or encryption will make a system that breaks itself. The idea that novice users can just run script workarounds is entirely unrealistic. a) They don't know about the problem if they haven't been told (burying it deep in the manuals or text that whizzes by is not good enough) b) from a security PoV they shouldn't be run anything they cut & paste in The general attitude to a major showstopper that is causing a lot of pain for novice users shown in this bug is frankly appalling and I'm pretty much inclined to ditch Ubuntu because of it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714083] [NEW] package linux-image-4.4.0-91-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Public bug reported: Attempted to remove kernel but errored on removal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-91-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bennabiy 20615 F pulseaudio /dev/snd/controlC0: bennabiy 20615 F pulseaudio Date: Wed Aug 30 16:09:17 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=36c5fd8a-1e38-4efb-a6ac-e848c494d792 InstallationDate: Installed on 2016-07-24 (402 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed root=UUID=b54fb9d9-4aee-4e22-8863-f34266582c9c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-91-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-DS2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/17/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1714083 Title: package linux-image-4.4.0-91-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: Attempted to remove kernel but errored on removal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-91-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bennabiy 20615 F pulseaudio /dev/snd/controlC0: bennabiy 20615 F pulseaudio Date: Wed Aug 30 16:09:17 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=36c5fd8a-1e38-4efb-a6ac-e848c494d792 InstallationDate: Installed on 2016-07-24 (402 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed root=UUID=b54fb9d9-4aee-4e22-8863-f34266582c9c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-91-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-DS2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanM
[Touch-packages] [Bug 1714081] [NEW] package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Public bug reported: attempted to remove old kernels and could not remove the extra packages. Having issues with zfs, trying to find a good kernel to work with. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-93-generic 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bennabiy 20615 F pulseaudio /dev/snd/controlC0: bennabiy 20615 F pulseaudio Date: Wed Aug 30 16:09:20 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=36c5fd8a-1e38-4efb-a6ac-e848c494d792 InstallationDate: Installed on 2016-07-24 (402 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed root=UUID=b54fb9d9-4aee-4e22-8863-f34266582c9c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-DS2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/17/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1714081 Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: attempted to remove old kernels and could not remove the extra packages. Having issues with zfs, trying to find a good kernel to work with. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-93-generic 4.4.0-93.116 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bennabiy 20615 F pulseaudio /dev/snd/controlC0: bennabiy 20615 F pulseaudio Date: Wed Aug 30 16:09:20 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=36c5fd8a-1e38-4efb-a6ac-e848c494d792 InstallationDate: Installed on 2016-07-24 (402 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed root=UUID=b54fb9d9-4aee-4e22-8863-f34266582c9c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-DS2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.
[Touch-packages] [Bug 1714039] [NEW] nslcd shuts down before sshd, causing errors
Public bug reported: 1] >lsb_release -rd Description:Ubuntu 17.04 Release:17.04 2] >apt-cache policy systemd systemd: Installed: 232-21ubuntu5 Candidate: 232-21ubuntu5 Version table: *** 232-21ubuntu5 500 500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty-updates/main amd64 Packages 500 http://dca-ubuntu-repo.ipipenet.com/ubuntu-security zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty/main amd64 Packages 3] i expected nslcd to not be terminated when sshd still needs it 4] it was logs: Aug 30 15:17:26 template nslcd[956]: thread 1 is still running, shutting down anyway Aug 30 15:17:26 template sshd[988]: pam_ldap(sshd:session): error opening connection to nslcd: No such file or directory Aug 30 15:17:26 template sshd[988]: pam_systemd(sshd:session): Failed to release session: Connection reset by peer Aug 30 15:17:26 template sshd[988]: pam_mail(sshd:session): user unknown Aug 30 15:17:26 template sshd[988]: fatal: login_init_entry: Cannot find user "jdoe" ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714039 Title: nslcd shuts down before sshd, causing errors Status in systemd package in Ubuntu: New Bug description: 1] >lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 2] >apt-cache policy systemd systemd: Installed: 232-21ubuntu5 Candidate: 232-21ubuntu5 Version table: *** 232-21ubuntu5 500 500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty-updates/main amd64 Packages 500 http://dca-ubuntu-repo.ipipenet.com/ubuntu-security zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty/main amd64 Packages 3] i expected nslcd to not be terminated when sshd still needs it 4] it was logs: Aug 30 15:17:26 template nslcd[956]: thread 1 is still running, shutting down anyway Aug 30 15:17:26 template sshd[988]: pam_ldap(sshd:session): error opening connection to nslcd: No such file or directory Aug 30 15:17:26 template sshd[988]: pam_systemd(sshd:session): Failed to release session: Connection reset by peer Aug 30 15:17:26 template sshd[988]: pam_mail(sshd:session): user unknown Aug 30 15:17:26 template sshd[988]: fatal: login_init_entry: Cannot find user "jdoe" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709384] Re: failed to unmount filesystems during shutdown, reboot hangs
i've figured out at least part of this issue. the system now no longer hangs at shutdown, but there are still filesystems it complains it is unable to unmount, and the system still hangs if it unable to unmount /home, which happens to be an nfs share [i'm uncertain if this is of particular relevance, but it is a characteristic unique among this system's filesystems]. the root cause was pam_systemd inadvertently excluded from the pam session config, following customization. this was causing another problem [ssh sessions hanging during shutdown instead of being cleanly terminated], and it was during troubleshooting of the ssh issue when it hit me that there was a relationship between the two. during shutdown, systemd brings down the network connection before ssh processes are gracefully disconnected/terminated. this leaves the client unaware, thus the hanging symptom. additionally, this appears to also leave processes active or files open, etc., in various locations, and thus affected filesystems are still in use and cannot be unmounted. to make matters worse, when the filesystem in use happens to be an nfs share [in this case, /home/foo.example.com/], the system hangs at shutdown. with pam_systemd properly configured in the pam session config, ssh processes/sessions get to gracefully close, /home/foo.example.com/ and /tmp/ are cleanly/successfully unmounted, and since the nfs share gets unmounted, the system does not hang. however, /var/ and /var/log/ still fail to be unmounted: Aug 30 03:27:09 template systemd[1]: Failed unmounting /var/log. Aug 30 03:27:09 template systemd[1]: Failed unmounting /var. this is still a problem which shouldn't be happening, but fortunately, since it's only the nfs unmount fail that makes the system hang, reboots aren't disastrous. there are still issues here that need to be addressed: 1] under nominal conditions, filesystems should cleanly unmount. unmounting should not fail. 2] if a filesystem fails to unmount [nfs or otherwise], the system should not hang during shutdown. this can be recreated by doing the following: • configure the system to mount an nfs share at boot [i used fstab]. it may also be enough to just mount an nfs share manually after boot • disable pam_systemd in the pam session config • ssh to the computer • change directory into the nfs share, so the filesystem is in use • reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709384 Title: failed to unmount filesystems during shutdown, reboot hangs Status in systemd package in Ubuntu: New Bug description: i'd done a new install of 17.04, and this had been working ok. this morning, i did an update, and now the system complains about being unable to unmount certain filesystems, as well as hanging during the shutdown process upon displaying "[ ok ] reached target shutdown" Aug 8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com. Aug 8 16:11:49 template systemd[1]: Failed unmounting /var/log. Aug 8 16:11:49 template systemd[1]: Failed unmounting /tmp. Aug 8 16:11:49 template systemd[1]: Failed unmounting /home. Aug 8 16:11:49 template systemd[1]: Failed unmounting /var. 1] >lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 2] >apt-cache policy systemd systemd: Installed: 232-21ubuntu5 Candidate: 232-21ubuntu5 Version table: *** 232-21ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 3] i expected the system to not fail when unmounting filesystems during shutdown 4] it did To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709384] [NEW] failed to unmount filesystems during shutdown, reboot hangs
Public bug reported: i'd done a new install of 17.04, and this had been working ok. this morning, i did an update, and now the system complains about being unable to unmount certain filesystems, as well as hanging during the shutdown process upon displaying "[ ok ] reached target shutdown" Aug 8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com. Aug 8 16:11:49 template systemd[1]: Failed unmounting /var/log. Aug 8 16:11:49 template systemd[1]: Failed unmounting /tmp. Aug 8 16:11:49 template systemd[1]: Failed unmounting /home. Aug 8 16:11:49 template systemd[1]: Failed unmounting /var. 1] >lsb_release -rd Description:Ubuntu 17.04 Release:17.04 2] >apt-cache policy systemd systemd: Installed: 232-21ubuntu5 Candidate: 232-21ubuntu5 Version table: *** 232-21ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 3] i expected the system to not fail when unmounting filesystems during shutdown 4] it did ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709384 Title: failed to unmount filesystems during shutdown, reboot hangs Status in systemd package in Ubuntu: New Bug description: i'd done a new install of 17.04, and this had been working ok. this morning, i did an update, and now the system complains about being unable to unmount certain filesystems, as well as hanging during the shutdown process upon displaying "[ ok ] reached target shutdown" Aug 8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com. Aug 8 16:11:49 template systemd[1]: Failed unmounting /var/log. Aug 8 16:11:49 template systemd[1]: Failed unmounting /tmp. Aug 8 16:11:49 template systemd[1]: Failed unmounting /home. Aug 8 16:11:49 template systemd[1]: Failed unmounting /var. 1] >lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 2] >apt-cache policy systemd systemd: Installed: 232-21ubuntu5 Candidate: 232-21ubuntu5 Version table: *** 232-21ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 3] i expected the system to not fail when unmounting filesystems during shutdown 4] it did To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697535] [NEW] Envy24 ICE1724 doesn't work
Public bug reported: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1697535 Title: Envy24 ICE1724 doesn't work Status in pulseaudio package in Ubuntu: New Bug description: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.n
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
Just a few updates which may be of use to anyone else having the same issues... 1). As this issue persists without a truly good solution, it may be a good idea to simply replace the wifi card with, say, an Atheros one which works better. You can find them relatively cheaply on ebay. 2). One of the major issues that I was having was that my main Wifi would crash internally, then whenever I tried to plug in a USB Wifi adapter they wouldn't work either, leaving me literally without any method of getting (wireless) internet. I assumed these two issues were connected, however, further research has led me to believe otherwise. I tried entirely removing the internal wifi card to see if that would make a difference on the USB wifi cards, yet still neither of mine worked. Further looking revealed one or two strange oddities... phy#1 Interface wlx000f6001cb1f ifindex 3 wdev 0x10001 addr 00:0f:60:01:cb:1f type managed txpower 20.00 dBm The interface is WAY out of convention. As explained here (https://superuser.com/questions/1086632/wlan1-showing-as-weird- characters#1086705), interface names are limited to 16 bytes. My theory is that when network-manager tries to connect with this interface, it breaks that limit. The solution suggested in that thread works, append net.ifnames=0 to the kernel parameters in grub and suddenly all of my USB wifi adapters work fantastically. I have a feeling this itself may warrant a separate bug report, I'll do some looking and see if anyone else is having the same issue/if someone's already reported it. TL;DR: If your USB wifi doesn't work and you get weird/long interface names from "iw dev", use "net.ifnames=0" to fix the interface name and take back your wifi. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-
[Touch-packages] [Bug 1690355] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 12 14:01:31 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690355 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: ... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 12 14:01:31 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-11 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
Issue definitely persists on 4.11/upstream. I came across an interesting output in dmesg which may explain why bluetooth works while the WiFi doesn't: [17326.525545] iwlwifi :01:00.0: Could not load the [0] uCode section [17326.525697] iwlwifi :01:00.0: Failed to start INIT ucode: -5 [17326.525702] iwlwifi :01:00.0: Failed to run INIT ucode: -5 [17326.525705] iwlwifi :01:00.0: Failed to start RT ucode: -5 [17391.638774] usb 1-4: USB disconnect, device number 64 [17392.015275] usb 1-4: new full-speed USB device number 65 using xhci_hcd [17392.156505] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc [17392.156520] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [17392.179288] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [17392.179426] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [17392.367199] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated What's interesting is that iwlwifi "can't load" the uCode/firmware, causing the internet/wifi portion to fail, but Bluetooth uses a separate firmware file on the same card, which itself works fine. So this probably explains why the bluetooth still works. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
It took less than 10 minutes of testing for the issue to come back up again under 4.11-rc7. Definitely NOT fixed upstream. I'll keep testing and see if I find any other unique behaviours/error messages. Thanks again, let me know if there's anything I can do! ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
** Attachment added: "Output dmesg crash on resume" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866130/+files/ucode-error-crash.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
** Attachment added: "Output of modinfo iwlwifi" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866129/+files/modinfo-iwlwifi.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
Some additional notes after testing for a while... The crashing behavior doesn't occur consistently in the same way. Sometimes the Bluetooth crashes with the Wifi, while sometimes it recovers fine and continues to work while the Wifi doesn't. In addition, it seems that the Wifi crash breaks NetworkManager as well- when I try to plug in a USB WiFi card, the networks show up but give me the following error in dmesg whenever the usb adapter tries to connect: [21857.875157] wlx002129e30688: authenticate with 8e:15:44:a9:86:22 [21857.924545] wlx002129e30688: send auth to 8e:15:44:a9:86:22 (try 1/3) [21857.926882] wlx002129e30688: authenticated [21863.316129] wlx002129e30688: authenticate with 8e:15:44:a9:85:f8 [21863.371861] wlx002129e30688: send auth to 8e:15:44:a9:85:f8 (try 1/3) [21863.374438] wlx002129e30688: authenticated [21868.376165] wlx002129e30688: aborting authentication with 8e:15:44:a9:85:f8 by local choice (Reason: 3=DEAUTH_LEAVING) [21868.740813] wlx002129e30688: authenticate with 8e:15:44:a9:82:fa [21868.788615] wlx002129e30688: send auth to 8e:15:44:a9:82:fa (try 1/3) [21868.790444] wlx002129e30688: authenticated [21873.795552] wlx002129e30688: aborting authentication with 8e:15:44:a9:82:fa by local choice (Reason: 3=DEAUTH_LEAVING) This repeats until it gives up trying to connect. Yet, tethering to my Android phone over USB DOES usually work. Restarting the NetworkManager service has no effect on the wifi issue. @jsalisbury: This issue has persisted across kernel versions and Ubuntu versions. I had the same issue on 16.10, as well as Arch when I used it, upgrade or not. I'm not ruling out a regression however, but frankly I have no qualifications to say what the issue is caused by. If I have time (and I get desperate enough) I'll try 16.04 and 14.04 and let you know if it's still present there. I'll test the 4.11 kernel this weekend, in the meantime, I'll upload some more dmesg outputs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE
[Touch-packages] [Bug 1684213] [NEW] Intel Wireless 7260 often crashes
Public bug reported: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Dmesg output when issue is occuring." https://bugs.launchpad.net/bugs/1684213/+attachment/4864922/+files/dmesg-errors.txt ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. - Bug: Wifi/Bluetooth crashes crashes and refuses to come back up, even - after multiple reboots. Issue persists across distros (Arch, Ubuntu, - etc.) + Bug: Wifi/Bluetooth crashes and refuses to come back up, even after + multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previo
[Touch-packages] [Bug 828895] Re: Bash loses track of background children sometimes
Just a quick note: having moved some affected systems back to Ubuntu, this bug has just manifested in production on Ubuntu 16.04 LTS: /opt/dump/bin/dump_multi: line 11: wait: pid 56652 is not a child of this shell My test script above no longer demonstrates it though. I'll see if I can come up with one that does. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/828895 Title: Bash loses track of background children sometimes Status in bash package in Ubuntu: Confirmed Bug description: Under some circumstances (I've not worked out precisely what), bash can forget about background child processes. For instance, if the file "simpletest" contains: #! /bin/bash count=0 while [ $count -lt 51 ]; do count=$((count+1)) /nonexist true & bgpids="$bgpids $!" done for pid in $bgpids; do wait $pid done then running "bash simpletest", seems to reliably report "simpletest: line 13: wait: pid 28850 is not a child of this shell" (with different PIDs each time, obviously). Increasing the "51" in the script increases the number of errors. Curiously, removing the call to a nonexistent program causes the problem to stop manifesting. "getconf CHILD_MAX" returns "undefined", which I think means that Bash should support an unlimited number of unwaited children. I've observed this on two different amd64 boxes running Ubuntu 10.04 LTS, and it persisted after I upgraded the bash package to 4.2-0ubuntu4. I couldn't reproduce it on an i386 box running Ubuntu 11.04. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: bash 4.1-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-server x86_64 Architecture: amd64 Date: Thu Aug 18 17:04:23 2011 InstallationMedia: Ubuntu-Server 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110719.2) ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/828895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1680381] [NEW] package initramfs-tools 0.122ubuntu8.8 [modified: usr/sbin/update-initramfs] failed to install/upgrade: subprocess installed post-installation script returned erro
Public bug reported: Ubuntu16.04.2 LTS_Xenial Xerus_-Release amd64(20170215.2} This bug if it is one is as a result of a previous attempt to get Ubuntu to install on this ssd(Samsung 840 EVO). The installation stalled straight after the automated restart( the ubuntu splash screen sat there for 15 minutes!), having downloaded everything. I used standard installation defaults, nothing special, so it shouldn't have done this. The installation is a complete installation over Win10, so the disk was formatted by Ubuntu. THis 'bug' was created by a second attempt to re-install Ubuntu over the previous copy which stalled or failed to setup, it apparently failed, though being a noob it may be a partial success, I don't know and defer to your better judgement... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 [modified: usr/sbin/update-initramfs] ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: iucode-tool: Install intel-microcode: Install iucode-tool: Configure intel-microcode: Configure NULL: ConfigurePending Architecture: amd64 CasperVersion: 1.376.2 Date: Thu Apr 6 16:24:15 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 [modified: usr/sbin/update-initramfs] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1680381 Title: package initramfs-tools 0.122ubuntu8.8 [modified: usr/sbin/update- initramfs] failed to install/upgrade: subprocess installed post- installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Ubuntu16.04.2 LTS_Xenial Xerus_-Release amd64(20170215.2} This bug if it is one is as a result of a previous attempt to get Ubuntu to install on this ssd(Samsung 840 EVO). The installation stalled straight after the automated restart( the ubuntu splash screen sat there for 15 minutes!), having downloaded everything. I used standard installation defaults, nothing special, so it shouldn't have done this. The installation is a complete installation over Win10, so the disk was formatted by Ubuntu. THis 'bug' was created by a second attempt to re-install Ubuntu over the previous copy which stalled or failed to setup, it apparently failed, though being a noob it may be a partial success, I don't know and defer to your better judgement... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 [modified: usr/sbin/update-initramfs] ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: iucode-tool: Install intel-microcode: Install iucode-tool: Configure intel-microcode: Configure NULL: ConfigurePending Architecture: amd64 CasperVersion: 1.376.2 Date: Thu Apr 6 16:24:15 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 [modified: usr/sbin/update-initramfs] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1680381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools
** Description changed: The change of how cloud-init renders /etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as expected: * resolvconf will nullify nameservers * if* commands ignore secondary addresses - - The rendering is considered dangerous per Debian (https://wiki.debian.org/NetworkConfiguration), to whit: - "Also, ifupdown supports specifying multiple interfaces by repeating iface sections with the same interface name. The key difference from the method described above is that all such sections are treated by ifupdown as just one interface, so user can't add or remove them individually. However, up/down commands, as well as scripts, are called for every section as it used to be. - - "Note however that this method is dangerous! Certain driver/hardware combinations may sometimes fail to bring the link up if no labels are assigned to the alias interfaces. (Seen this on Debian Wheezy and Jessie with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) auto-negotiating to 10/full. A similar warning from another person exists in the history of this page.) - " - [ORIGINAL REPORT] Regresion from Bug #1657940. When provisioning with multiple eth0 addresses, /etc/resolv.conf is empty: Consider: root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 138.197.98.102 dns-nameservers 8.8.8.8 8.8.4.4 gateway 138.197.96.1 netmask 255.255.240.0 # control-alias eth0 iface eth0 inet static address 10.17.0.11 netmask 255.255.0.0 Which then yields an empty /etc/resolv.conf: root@tester:/run/resolvconf# cat interface/eth0.inet root@tester:/run/resolvconf# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN The problem is that resolvconfg does pattern matching for eth*.inet. The second definition of eth0 has no nameserver and therefore overrides the definition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1675571 Title: Cloud-init update renders secondary addresses to be incompatible with standard tools Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: New Bug description: The change of how cloud-init renders /etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as expected: * resolvconf will nullify nameservers * if* commands ignore secondary addresses [ORIGINAL REPORT] Regresion from Bug #1657940. When provisioning with multiple eth0 addresses, /etc/resolv.conf is empty: Consider: root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 138.197.98.102 dns-nameservers 8.8.8.8 8.8.4.4 gateway 138.197.96.1 netmask 255.255.240.0 # control-alias eth0 iface eth0 inet static address 10.17.0.11 netmask 255.255.0.0 Which then yields an empty /etc/resolv.conf: root@tester:/run/resolvconf# cat interface/eth0.inet root@tester:/run/resolvconf# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN The problem is that resolvconfg does pattern matching for eth*.inet. The second definition of eth0 has no nameserver and therefore overrides the definition. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1675571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365375] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3
The fact that this was reported on 2014-09-04 and *still* has not been fixed is unbelievable. It seems related to (or the same as) https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1512992 , which was opened on 2015-11-04 and has not been fixed yet either. Only ten days ago was a fix proposed, which, by the way, doesn't seem to resolve the problem. That is to say nothing of the obsoleted instructions at https://wiki.ubuntu.com/Testing/EnableProposed , which still mention the "aptitude" executable, which doesn't even exist in Ubuntu 16. Pretty disappointing, all around. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1365375 Title: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6 -dev-amd64 2.19-0ubuntu6.3 Status in eglibc package in Ubuntu: Confirmed Bug description: apt-get install gcc-multilib broke it! ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc6-dev-i386 (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Thu Sep 4 08:50:46 2014 DpkgTerminalLog: Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ... Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ... dpkg: error processing archive /var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack): trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3 DuplicateSignature: package:libc6-dev-i386:(not installed):trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3 ErrorMessage: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3 SourcePackage: eglibc Title: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1365375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
I'm afraid I did not, no. On 21 February 2017 at 10:16, Ben <1434...@bugs.launchpad.net> wrote: > I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by > removing all xscreensaver remnants (which I believe to be conflicting with > Light Locker). I did this, but use at your own risk: > ``` > sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 | > tr '\n' ' ') > ``` > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1434351 > > Title: > X fonts and widgets disappear after suspend/resume cycle > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > After a suspend/resume cycle, the screen comes up normally, but every > time I move my mouse over a piece of text, button, widget, etc, the > text vanishes and it's replaced by a plain rectangle. > > This does not affect xterm, but it does affect any GTK apps, firefox, > etc. > > xfce-panel vanishes, although it's still responding to mouse-clicks. > Newly opened menus are grey rectangles. > > The lines underlining menu hotkeys do NOT disappear. > > In the attached screenshot, you can clearly see which buttons I have > waved the mouse over, and which I have not. > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 > ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 > Uname: Linux 3.19.0-9-generic x86_64 > ApportVersion: 2.16.2-0ubuntu3 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Thu Mar 19 19:51:37 2015 > InstallationDate: Installed on 2015-03-05 (14 days ago) > InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 > (20150218.1) > SourcePackage: xserver-xorg-video-intel > UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Incomplete Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by removing all xscreensaver remnants (which I believe to be conflicting with Light Locker). I did this, but use at your own risk: ``` sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 | tr '\n' ' ') ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Incomplete Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 735675] Re: bzdiff does not pass -I option to diff
This patch is broken: 1. $OPTIONS is used (unquoted) in 4 different places but this patch only updates one of them 2. Quoting $OPTIONS prevents use of multiple options Unfortunately I don't see a reasonable way to fix this while using only POSIX shell features. - If bzdiff is changed to use bash then the options can be accumulated into an array variable. This would be fine in Debian and Ubuntu, but not upstream. - POSIX allows positional arguments to be used in an array-like way, but we already use them for the filenames. - This could be done by escaping, quoting and concatenating the options and then using eval to expand to multiple arguments. But this is not what I would consider reasonable! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/735675 Title: bzdiff does not pass -I option to diff Status in bzip2 package in Ubuntu: New Bug description: Binary package hint: bzip2 When trying to use bzdiff with the -I option (ignore regex), the options are not properly passed to diff. I have 2 files (MySQL dumps) that differ in only one line: $ bzdiff tmp1.bz2 tmp2.bz2 9c9 < -- Dump completed on 2011-03-11 1:06:50 --- > -- Dump completed on 2011-03-11 0:40:11 However, when trying to avoid that line from matching a problem arises: $ ./bzdiff_orig -I'Dump completed' tmp1.bz2 tmp2.bz2 diff: extra operand `/tmp/bzdiff.JnwGRlHnMM' diff: Try `diff --help' for more information. After some attempts at quoting and unquoting, I solved the problem by modifying the bzdiff shell script at /bin/bzdiff. The issues were 2: i) the options were not correctly parsed, a space was added before the first option, and ii) the options were not passed quoted to diff, therefore they were incorrectly interpreted as a file and not an option. Will include a patch. Version info: $ lsb_release -rd Description: Ubuntu 10.10 $ apt-cache policy bzip2 bzip2: Installed: 1.0.5-4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/735675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
Judging from the posts in this bug report, it took 2 weeks and three days to solve this problem for the end-users (for the other releases. Support for precise ends in 16 weeks... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec Status in libav: Unknown Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Invalid Status in firefox source package in Precise: Fix Released Status in libav source package in Precise: Confirmed Status in firefox source package in Trusty: Fix Released Status in libav source package in Trusty: Fix Released Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/libav/+bug/1643467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658250] [NEW] Window positions change in nonsensical ways when a secondary display is moved above the primary
Public bug reported: Most commonly, they'll be partway on the upper monitor, but mostly on the bottom. But sometimes, they'll be halfway off the screen on the bottom monitor. New windows are sometimes created in slightly odd places as well; usually, the titlebar will be on the top screen and the rest of the window on the bottom, meaning the gnome-shell bar is obscuring part of the window. Windows that are maximized when the change is made aren't affected. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Jan 20 18:09:51 2017 DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 480 [1682:9480] InstallationDate: Installed on 2017-01-17 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: ASUS All Series 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.9.0-11-generic root=UUID=638d73c8-aa0e-423b-907c-6bbb2c237275 ro i915.modeset=0 quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to zesty on 2017-01-18 (2 days ago) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.74-1 version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jan 16 20:46:55 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug reproducible single-occurrence third-party-packages ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1658250 Title: Window positions change in nonsensical ways when a secondary display is moved above the primary Status in xorg package in Ubuntu: New Bug description: Most commonly, they'll be partway on the upper monitor, but mostly on the bottom. But sometimes, they'll be halfway off the screen on the bottom monitor. New windows are sometimes created in slightly odd places as well; usually, the titlebar will be on the top screen and the rest of the window on the bottom, meaning the gnome-shell bar is obscuring part of the window. Windows that are maximized when the change is made aren't affected. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Jan 20 18:09:51 2017 DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running PostI
[Touch-packages] [Bug 1654113] [NEW] USB drive with lvm on an encrypted partition does not unmount cleanly when removed, making it impossible to use again without a reboot or use of command line tools
Public bug reported: I have a USB drive with two partitions, one unencrypted and one encrypted. The encrypted partition serves as the physical volume for a LVM volume group. cfdisk shows me: Disk: /dev/sdb Size: 74.5 GiB, 80026361856 bytes, 156301488 sectors Label: dos, identifier: 0x0006866a DeviceBoot Start End Sectors Size Id Type >> /dev/sdb1 * 2048 500094 498047 243.2M 83 Linux /dev/sdb2 501758 156301311 15579955474.3G 5 Extended └─/dev/sdb5501760 156301311 15579955274.3G 83 Linux When I plug in the drive, one partition is mounted automatically. A popup window also appears, prompting for a password to unlock the volume. After I enter the password, four more volumes appear on my Desktop, and in /media/username: $ ls -l /media/username total 25 drwxr-xr-x 22 root root 4096 Jan 6 2014 0c321a15-e3b4-47b5-a173-05adfb5ea40c drwxrwxrwt 9 root root 12288 Dec 21 00:26 14ea30b5-5ace-4bc7-a483-7d800ee77579 drwxr-xr-x 15 root root 4096 Dec 21 00:27 41f9c7bb-62e5-4afd-b4c1-efdecfd70083 drwxr-xr-x 7 root root 4096 Nov 12 2013 42d838d8-b797-4782-8473-5d42a29667c1 drwxr-xr-x 4 root root 1024 Mar 18 2014 ba0575b2-f570-4e40-b374-f1d3dc0ca48b The output of findmnt is as follows, with my username again replaced with 'username': TARGETSOURCE FSTYPE OPTIONS / /dev/mapper/burrow-root │ext4rw,relatime,errors=remo ├─/syssysfs sysfs rw,nosuid,nodev,noexec, [snip] ├─/boot /dev/sda1 ext2rw,relatime,block_valid ├─/home /dev/mapper/burrow-home │ext4rw,relatime,data=ordere ├─/media/username/ba0575b2-f570-4e40-b374-f1d3dc0ca48b │ /dev/sdc1 ext2rw,nosuid,nodev,relatim ├─/media/username/14ea30b5-5ace-4bc7-a483-7d800ee77579 │ /dev/mapper/antler-temp │ext4rw,nosuid,nodev,relatim ├─/media/username/42d838d8-b797-4782-8473-5d42a29667c1 │ /dev/mapper/antler-home │ext4rw,nosuid,nodev,relatim ├─/media/username/41f9c7bb-62e5-4afd-b4c1-efdecfd70083 │ /dev/mapper/antler-var │ext4rw,nosuid,nodev,relatim └─/media/username/0c321a15-e3b4-47b5-a173-05adfb5ea40c /dev/mapper/antler-root ext4rw,nosuid,nodev,relatim To unmount the drive, I can right click on each volume on the desktop, choose unmount, and I receive a pop up notification that the drive has been safely removed. After unplugging the USB drive, the icon for the unencrypted volume disappears from the desktop, but the icons for the lvm volumes remain. I have attached the long errors that appear in the syslog. When plugging the drive back in, the unencrypted partition is again mounted, and I am prompted for a password. Nothing further happens. If I double click on the encryted drive icon on the desktop, I am again prompted for a password, and then receive this error: Failed to mount "80 GB Encrypted" Error unclocking /dev/sdb5: Command-line `cryptsetup luksOpen "/dev/sdb5" "luks-1d2a9dd8-91a4-4e34-9531-b0cde53579c0" ' exited with non-zero exit status 5: Device luks-1d2a9dd8-91a4-4e34-9531-b0cde53579c0 already exists. The usb drive is unusable without a reboot, or issuing this command, antler is the volume group name: $ sudo vgchange -a n antler 0 logical volume(s) in volume group "antler" now active Upon issuing this command, the icons for the four lvm volumes disappears from my desktop. If I now plug in the drive, it acts normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 4 19:40:18 2017 InstallationDate: Installed on 2016-11-28 (37 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "syslog when unplugging the USB drive" https://bugs.launchpad.net/bugs/1654113/+attachment/4800158/+files/attach.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.la
[Touch-packages] [Bug 1637779] Re: ext4 filesystem fails randomly with checksum error
I'm experiencing this exact issue. 16.10 x64, not dual booted. Only difference is mine is fill disk encrypted, so my device is dm-0. Let me know what to attach -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1637779 Title: ext4 filesystem fails randomly with checksum error Status in e2fsprogs package in Ubuntu: New Bug description: Description: Ubuntu 16.10 Release: 16.10 package version: linux-image-4.8.0-26-generic: Installed: 4.8.0-26.28 Candidate: 4.8.0-26.28 Version table: *** 4.8.0-26.28 500 500 http://sk.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64 Packages 100 /var/lib/dpkg/status fresh installation of Ubunut 16.10, all updates included While I am working with system after few minutes root filesystem /dev/sdb5 switches into readonly mode in dmesg is this: [ 304.921552] EXT4-fs error (device sdb5): ext4_iget:4476: inode #24577: comm updatedb.mlocat: checksum invalid [ 304.925565] Aborting journal on device sdb5-8. [ 304.926507] EXT4-fs (sdb5): Remounting filesystem read-only [ 304.927416] EXT4-fs error (device sdb5): ext4_journal_check_start:56: Detected aborted journal [ 304.943408] EXT4-fs error (device sda1): ext4_iget:4476: inode #12: comm updatedb.mlocat: checksum invalid when it happens I must do fsck f /dev/sdb1 once, second time it says everything is fine. after reboot when I start dto do something it soon happens again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
16.10 have unity-panel-service taking up 3.5 GB of RAM. I've mainly noticed it after resume, as Firefox randomly begins to crash/freeze before the entire system becomes unstable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in Unity HUD: Confirmed Status in Application Menu Indicator: Confirmed Status in Unity: Won't Fix Status in firefox package in Ubuntu: Incomplete Status in hud package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Status in firefox source package in Xenial: Incomplete Status in hud source package in Xenial: Confirmed Status in unity source package in Xenial: Invalid Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/987060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544251] Re: mount ignores exec option for 'users' mounts
This bug appears to have been re-introduced in the re-write from stand- alone `mount` to libmount, and thus is still present in Ubuntu 16.04 LTS. Reported upstream and got a fix there (https://github.com/karelzak /util-linux/commit/3c4a3de0fcb8f21bffacfd8bdc3d6fbd683c71f5). Would love to see this incorporated in the LTS release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1544251 Title: mount ignores exec option for 'users' mounts Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Trusty: New Bug description: The version of 'mount' included in Ubuntu 14.04 LTS and 12.04 LTS has a bug wherein the 'exec' option in /etc/fstab is ignored on mounts with the 'user' or 'users' options when they are mounted by root. For example: $ grep 48tb2d /etc/fstab labdisk.site.com:/Public4 /mnt/lab_48tb2d nfs users,exec,nosuid 0 0 $ sudo mount /mnt/lab_48tb2d $ mount | grep 48tb2d labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs (rw,nosuid,nodev,noexec,addr=172.16.222.158) $ umount /mnt/lab_48tb2d $ mount /mnt/lab_48tb2d $ mount | grep 48tb2d labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs (rw,nosuid,nodev,addr=172.16.222.158) This bug was fixed upstream several years ago and I believe therefore doesn't affect 15.10, but seems not to have made it into the current LTS releases of ubuntu. https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/mount/mount.c?id=a4c0cc75ff9744299f108c259efab1bd30c8007a https://bugzilla.redhat.com/show_bug.cgi?id=769636 System info: Ubuntu 14.04.3 LTS, util-linux 2.20.1-5.1ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1544251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402787] Re: Ubuntu Desktop Next does not show on-screen keyboard when needed
I have the same problem on an X220T, whose screen can flip into a tablet mode. The touchscreen works great for everything until I want to type something. In Gnome Shell, anytime I select a text field with the touchscreen, it assumes I want to use the on-screen keyboard (OSK) and automatically pops it up. If I begin to type on a physical keyboard, it gets rid of the OSK and lets me get on with life. It seems to me that this may be a good approach here as well! Definitely would work better than the MS way of doing it, always having to press a button to make the keyboard appear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1402787 Title: Ubuntu Desktop Next does not show on-screen keyboard when needed Status in unity8 package in Ubuntu: Triaged Bug description: When booting the amd64 daily iso of the Ubuntu Desktop Next image on a tablet, I am unable to get the on-screen keyboard to appear by tapping into a textfield. Without this functionality, it is impossible to use the terminal, the search, or perform basically any task that would make the operating system useful on a tablet. In my humble opinion, whatever logic you guys use for displaying on- screen keyboards in Ubuntu Touch on phones and tablets should be available in Ubuntu Desktop Next when there is no physical keyboard attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1402787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635775] Re: No sound unity8 apps 16.10
@Jim For some reason it wasn't installed, but installing it didn't fix it. Is there any configuration required or any other packages I should try installing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1635775 Title: No sound unity8 apps 16.10 Status in Canonical System Image: Incomplete Status in media-hub package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Testing on a Lenovo Thinkpad X220T running fresh install of Ubuntu 16.10. Running Checkbox passes the sound tests (as audio is played), but when using unity8 apps no sound comes out. However, sound does come out from Libertine containerized apps. For example, I can be running the default Browser app playing a video, and no sound will come out. However, when playing the same video under Firefox or playing music in Pithos in a Libertine container, sound works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1635775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp