[Touch-packages] [Bug 2017422] [NEW] package tzdata 2023c-0ubuntu0.22.04.0 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 1
Public bug reported: I was trying to fix an issue with installing a virtual machine so i don't know if this is somehow related but whenever i use my the laptop this error pops up ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.0 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: tzdata:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 23 13:35:10 2023 DuplicateSignature: package:tzdata:2023c-0ubuntu0.22.04.0 Setting up tzdata (2023c-0ubuntu0.22.04.0) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 1 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-17 (188 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.0 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017422 Title: package tzdata 2023c-0ubuntu0.22.04.0 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 1 Status in tzdata package in Ubuntu: New Bug description: I was trying to fix an issue with installing a virtual machine so i don't know if this is somehow related but whenever i use my the laptop this error pops up ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.0 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: tzdata:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 23 13:35:10 2023 DuplicateSignature: package:tzdata:2023c-0ubuntu0.22.04.0 Setting up tzdata (2023c-0ubuntu0.22.04.0) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 1 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-17 (188 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.0 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Hi, I also have the same issue. In my case, I use DP to connect my monitor to my computer and I was able to use the monitor's built in audio without problems. I have even reinstalled Ubuntu just to check if it was my fault that the audio stopped working. Note, the audio works on Windows. I am currently on kernel 5.19.0-38-generic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982057] [NEW] gdebi-gtk is not installing .deb package if "Open With Gdebi" is used on right-click
Public bug reported: In Xfce on 22.04 Xubuntu, when trying to install .deb package with "Open With Gdebi packge Installer" right-click option while in Thunar file manager, Gdebi-gtk just silently dies, without installing package. If gdebi-gtk is started from CLI, and then .deb file is opened via File>Open , then .deb package is able to be installed. Gdebi=gtk should be able to install package with open with method and should not die. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdebi 0.9.5.7+nmu6 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jul 19 07:08:58 2022 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: Upgraded to jammy on 2022-04-29 (80 days ago) ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1982057 Title: gdebi-gtk is not installing .deb package if "Open With Gdebi" is used on right-click Status in gdebi package in Ubuntu: New Bug description: In Xfce on 22.04 Xubuntu, when trying to install .deb package with "Open With Gdebi packge Installer" right-click option while in Thunar file manager, Gdebi-gtk just silently dies, without installing package. If gdebi-gtk is started from CLI, and then .deb file is opened via File>Open , then .deb package is able to be installed. Gdebi=gtk should be able to install package with open with method and should not die. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdebi 0.9.5.7+nmu6 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Jul 19 07:08:58 2022 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: Upgraded to jammy on 2022-04-29 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1982057/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descr
When I do right-click on .deb package and open it with Gdebi-gtk, and try to install a package on 21.10 (also used to happen od 21.04) program closes. I have downloaded 0.9.5.7+nmu6 and I think I have built it with dpkg- buildpackage - us -uc and still happens the same. 0.9.5.7+nmu6 works of gdebi-gtk is called from Terminal and .deb opened via File>Open , but it does not when on right-click and install in Thunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to:
[Touch-packages] [Bug 1923437] [NEW] can't set 2560x1440 resolution after installing nvidia drivers
Public bug reported: Hello ! I have 2 monitors 1) one is 4K 2) another one is FULLHD, when I installed lubuntu I had 4k monitor work at maximum 4k and another at fullhd , I want to change that 4k monitor to 2560x1440(2k). after install nvidia drivers there is no 2560x1440 resolution in "monitor settings" resolutions tab like it was before installing drivers. when trying to add it manually from xrandr, at some point it gives me that error: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 35 Current serial number in output stream: 35 in short , I can't set monitor to 2560x1440. what it might be ? -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen have 2560x1440 resolution option after installing nvidia driver 4) What happened instead have no 2560x1440 listed in "monitor settings" and can't even create it manually from xrandr commands Best Regard ! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-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 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Mon Apr 12 14:07:34 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-13-generic root=UUID=acd8d9c8-3bd0-4c68-9a02-19818e4cf3c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2017 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd09/05/2017:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute resolution 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/1923437 Title: can't set 2560x1440 resolution after installing nvidia drivers Status in xorg package in Ubuntu: New Bug description:
[Touch-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I can confirm that libasound2 from ppa:hui.wang/pa-testing works. -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
Hi, installing older packages sudo dpkg -i libasound2_1.2.2-2.1ubuntu2_amd64.deb libasound2-data_1.2.2-2.1ubuntu2_all.deb fixed sound issues on my Lenovo Ideapad 5 14are05 with Ryzen 4500u. Please release fix asap, this is a huge bug (to lose sound after update). -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1799747] [NEW] Xorg freeze
Public bug reported: I can't run Ubuntu 18.10 with nVidia drivers (340.107). They ran just fine on 18.04, but not on 18.10. The system freezes at start up (the furthest that it gets is 'Starting Gnome Display Manager'). X-org Nouveau driver is working ok, but it's not ideal, I get strange flickering at subtle color gradients... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 18:29:54 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=3e2e480d-ea50-412f-88cd-55820becb551 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.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.:bvr2209:bd03/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze 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/1799747 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I can't run Ubuntu 18.10 with nVidia drivers (340.107). They ran just fine on 18.04, but not on 18.10. The system freezes at start up (the furthest that it gets is 'Starting Gnome Display Manager'). X-org Nouveau driver is working ok, but it's not ideal, I get strange flickering at subtle color gradients... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 18:29:54 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=3e2e480d-ea50-412f-88cd-55820becb551 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1682540] [NEW] package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: --EOF-- ProblemType: Package DistroRelease: Ubuntu 16.10 Package: sudo 1.8.16-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Apr 12 21:26:08 2017 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-11-07 (156 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1682540 Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: --EOF-- ProblemType: Package DistroRelease: Ubuntu 16.10 Package: sudo 1.8.16-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Apr 12 21:26:08 2017 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-11-07 (156 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1682540/+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 1385817] Re: initscripts package fails to upgrade if there are local init scripts on the system with no LSB headers
thx for answer. There are more than one way to install an operation system. In my opinion it was a -not fixed fault- during installation with a non-efi bios. Bernhard Am 17.02.2017 um 15:50 schrieb Phillip Susi: > If this isn't a bug in Ubuntu and there isn't anything we can do about > it, then why has it not been closed as invalid or wontfix? > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1385817 Title: initscripts package fails to upgrade if there are local init scripts on the system with no LSB headers Status in sysvinit package in Ubuntu: Triaged Bug description: The dependency-based boot sequencing originally introduced upstream with Debian 6.0 is now always enabled in Ubuntu 14.10. For optimal sequencing, all init.d scripts should declare their dependencies in an LSB header. This is already the case for scripts shipped in Ubuntu, but users should check their local scripts and consider adding that information. For more information on this feature refer to the information available in /usr/share/doc/insserv/README.Debian. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: initscripts-2.88dsf 41ubuntu18 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux x86_64 3.13.0-37-generic ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Sun October 26 2014 7:52:55 DuplicateSignature: Package: initscripts: 2.88dsf-41ubuntu18: the post-installation script subprocess installed returned error exit status 1 ErrorMessage: The post-install script subprocess installed returned error exit status 1 InstallationDate: Installed on 2014-08-06 (80 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sysvinit Title: initscripts package 2.88dsf-41ubuntu18 failed to install / upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1385817/+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 1543031] Re: Sometimes no notification when new OTA is available
*** This bug is a duplicate of bug 1508081 *** https://bugs.launchpad.net/bugs/1508081 I am still stuck on OTA-8 update since december 2015. I did not get any single OTA update notificaition after OTA-8, can somebody help fix this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1543031 Title: Sometimes no notification when new OTA is available Status in The Avila project: Confirmed Status in Canonical System Image: New Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: frieza 7 I flashed build 7, there is build 8 on system-image.u.c but I didn't receive a notification. client.log and u-d-m attached. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1543031/+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 1508081] Re: Fails to receive OTA updates
I did not recieve the OTA-9 update since the date of release, and OTA-10 has not arrived on my BQ E4.5 yet, will I ever get another update for my phone? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1508081 Title: Fails to receive OTA updates Status in Canonical System Image: Fix Committed Status in Ubuntu system image: Fix Released Status in system-image package in Ubuntu: Fix Released Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: Ubuntu Touch 15.04 (r23) [mako] Issue: Phone appears to fail to receive OTA updates. Previously, I jumped from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears to be released on 2015 Oct 16. Expected behavior: System Settings > System > Updates (or System Settings > About this phone > Check for updates) reveals new image that I can release and download. Actual behavior: Checking for updates... > Software is up to date See the comment regarding similar issues for large app installs. It seems if anything interrupts the transfer or if the connection is somewhat slow the download performance degenerates then times out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+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 1565130] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben
Public bug reported: update started in 16.04 / beta ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 1 23:57:23 2016 ErrorMessage: Trigger bilden eine Schleife, aufgegeben InstallationDate: Installed on 2016-02-22 (39 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160221) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.9 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (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 ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1565130 Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben Status in ca-certificates package in Ubuntu: New Bug description: update started in 16.04 / beta ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 1 23:57:23 2016 ErrorMessage: Trigger bilden eine Schleife, aufgegeben InstallationDate: Installed on 2016-02-22 (39 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160221) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.9 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1565130/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ** Attachment added: "Alsa-info" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+attachment/4490701/+files/alsa-info.txt.oHiYSKycn0 -- 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/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1504778] [NEW] Lenovo G50-80 - Inverted Internal microphone (phase inversion)
Public bug reported: Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: nikola 1819 F...m pulseaudio /dev/snd/controlC1: nikola 1819 F pulseaudio /dev/snd/controlC0: nikola 1819 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 10 15:31:56 2015 InstallationDate: Installed on 2015-10-06 (3 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN72WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80L0 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "Alsa-info" https://bugs.launchpad.net/bugs/1504778/+attachment/4490714/+files/alsa-info.txt.oHiYSKycn0 -- 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/1504778 Title: Lenovo G50-80 - Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: New Bug description: Can confirm the bug on Lenovo g50-80. Alsa-hda-dkms package doesn't help (there is no "Inverted Internal Mic" entry in alsamixer after reboot). Removed alsa-hda-dkms and tried "option snd-hda-intel model=auto" but it doesn't help. Workaround "mute right channel" works but can it be fixed permanently (I don't want to manually mute right mic channel every time I use skype)? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: nikola 1819 F...m pulseaudio /dev/snd/controlC1: nikola 1819 F pulseaudio /dev/snd/controlC0: nikola 1819 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 10 15:31:56 2015 InstallationDate: Installed on 2015-10-06 (3 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN72WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN72WW:bd01/27/2015:svnLENOVO:pn80L0:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80L0 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1504778/+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 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Bug report for Lenovo G50-80 https://bugs.launchpad.net/ubuntu/+source /alsa-driver/+bug/1504778 -- 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/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo
Someone should really look into this bug, I've been getting it *at least* once per day on my thinkpad t60 (it's more like 2-3 times daily on average though) running xubuntu 15.04 64 bit, rendering whole operating system pretty much unusable for anything that requires longer/permanent internet connection... Logs show same errors as the ones already attached. -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in linux-firmware package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+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 1445613] [NEW] package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: update failed ProblemType: Package DistroRelease: Ubuntu 14.10 Package: util-linux 2.25.1-3ubuntu4.1 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic i686 ApportVersion: 2.14.7-0ubuntu8.3 Architecture: i386 Date: Fri Apr 17 20:37:34 2015 DuplicateSignature: package:util-linux:2.25.1-3ubuntu4.1:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2015-04-11 (6 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) SourcePackage: util-linux Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 utopic -- 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/1445613 Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in util-linux package in Ubuntu: New Bug description: update failed ProblemType: Package DistroRelease: Ubuntu 14.10 Package: util-linux 2.25.1-3ubuntu4.1 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic i686 ApportVersion: 2.14.7-0ubuntu8.3 Architecture: i386 Date: Fri Apr 17 20:37:34 2015 DuplicateSignature: package:util-linux:2.25.1-3ubuntu4.1:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2015-04-11 (6 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) SourcePackage: util-linux Title: package util-linux 2.25.1-3ubuntu4.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1445613/+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 1402839] [NEW] Suspend hangs
Public bug reported: Trying to suspend results in the the screen going blank, the fans speeding up, and the computer hanging. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: resume: libgcrypt version: 1.5.4 * Setting up X socket directories... [80G [74G[ OK ] * Starting early crypto disks... [80G [74G[ OK ] CompizPlugins: [core,bailer,detection,composite,opengl,decor,vpswitch,compiztoolbox,gnomecompat,snap,imgpng,resize,regex,move,grid,mousepoll,place,session,animation,expo,ezoom,unitymtgrabhandles,wall,fade,scale,workarounds,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 15 22:38:24 2014 DistUpgraded: 2014-10-23 16:37:47,769 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3625] InstallationDate: Installed on 2014-03-31 (258 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. P35-DS3R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=c740d858-96be-4dfc-b301-91c5aab9e9d2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-23 (53 days ago) dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 15 22:28:50 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 fonts third-party-packages ubuntu utopic ** Attachment added: pm-suspend.log https://bugs.launchpad.net/bugs/1402839/+attachment/4281674/+files/pm-suspend.log ** Package changed: xorg (Ubuntu) = 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/1402839 Title: Suspend hangs Status in Ubuntu: New Bug description: Trying to suspend results in the the screen going blank, the fans speeding up, and the computer hanging. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: resume: libgcrypt version: 1.5.4 * Setting up X socket directories... [80G [74G[ OK ] * Starting early crypto disks... [80G [74G[ OK ] CompizPlugins:
[Touch-packages] [Bug 1378738] [NEW] guest os boot stuck with mount operation error
Public bug reported:
I'm trying to migrate an OS running on a physical machine to an LXC container,
but no luck so far. Right now the system gets stuck somewhere during lxc-start:
...
* Stopping cgroup management proxy ...done.
* Starting load modules from /etc/modules ...done.
* Stopping Mount network filesystems ...done.
* Starting set sysctls from /etc/sysctl.conf ...done.
* Stopping set sysctls from /etc/sysctl.conf ...done.
* Stopping load modules from /etc/modules ...done.
* Starting configure network device ...done.
* Starting Bridge socket events into upstart ...done.
hangs indefinitely here
Both host and guest are running ubuntu 14.04 LTS and same guest boots
properly via VirtualBox... kern.log shows some issues with mounts:
Oct 7 10:35:45 ares kernel: [138643.960789] device veth0RG5HU entered
promiscuous mode
Oct 7 10:35:45 ares kernel: [138643.961450] IPv6: ADDRCONF(NETDEV_UP):
veth0RG5HU: link is not ready
Oct 7 10:35:45 ares kernel: [138643.987832] EXT4-fs (dm-5): couldn't mount as
ext3 due to feature incompatibilities
Oct 7 10:35:45 ares kernel: [138643.987967] EXT4-fs (dm-5): couldn't mount as
ext2 due to feature incompatibilities
Oct 7 10:35:45 ares kernel: [138643.988322] EXT4-fs (dm-5): mounted filesystem
with ordered data mode. Opts: (null)
Oct 7 10:35:45 ares kernel: [138644.002660] IPv6: ADDRCONF(NETDEV_CHANGE):
veth0RG5HU: link becomes ready
Oct 7 10:35:45 ares kernel: [138644.002702] lxcbr0: port 1(veth0RG5HU) entered
forwarding state
Oct 7 10:35:45 ares kernel: [138644.002719] lxcbr0: port 1(veth0RG5HU) entered
forwarding state
Oct 7 10:35:46 ares kernel: [138644.340780] type=1400
audit(1412670946.254:113): apparmor=DENIED operation=mount info=failed
type match error=-13 profile=lxc-container-default
name=/run/cgmanager/fs/none,name=systemd/ pid=399 comm=cgmanager
fstype=cgroup srcname=none,name=systemd flags=rw
Oct 7 10:36:00 ares kernel: [138659.015558] lxcbr0: port 1(veth0RG5HU) entered
forwarding state
Here is the container's configuration file:
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.utsname = myvm
lxc.autodev = 1
lxc.tty = 4
lxc.pts = 1024
lxc.rootfs = /dev/mapper/ubuntu--vmvg-lvroot
lxc.arch = x86_64
lxc.cap.drop = sys_module mac_admin
#lxc.aa_profile = lxc-container-default-with-mounting
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
#lxc.cgroup.devices.allow = b 7:* rwm
Any suggestions?
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1378738
Title:
guest os boot stuck with mount operation error
Status in “lxc” package in Ubuntu:
New
Bug description:
I'm trying to migrate an OS running on a physical machine to an LXC
container, but no luck so far. Right now the system gets stuck somewhere during
lxc-start:
...
* Stopping cgroup management proxy ...done.
* Starting load modules from /etc/modules ...done.
* Stopping Mount network filesystems ...done.
* Starting set sysctls from /etc/sysctl.conf ...done.
* Stopping set sysctls from /etc/sysctl.conf ...done.
* Stopping load modules from /etc/modules ...done.
* Starting configure network device ...done.
* Starting Bridge socket events into upstart ...done.
hangs indefinitely here
Both host and guest are running ubuntu 14.04 LTS and same guest boots
properly via VirtualBox... kern.log shows some issues with mounts:
Oct 7 10:35:45 ares kernel: [138643.960789] device veth0RG5HU entered
promiscuous mode
Oct 7 10:35:45 ares kernel: [138643.961450] IPv6: ADDRCONF(NETDEV_UP):
veth0RG5HU: link is not ready
Oct 7 10:35:45 ares kernel: [138643.987832] EXT4-fs (dm-5): couldn't mount
as ext3 due to feature incompatibilities
Oct 7 10:35:45 ares kernel: [138643.987967] EXT4-fs (dm-5): couldn't mount
as ext2 due to feature incompatibilities
Oct 7 10:35:45 ares kernel: [138643.988322] EXT4-fs (dm-5): mounted
filesystem with ordered data mode. Opts:
Re: [Touch-packages] [Bug 1377973] [NEW] lxc-destroy/lxc-stop gets stuck
Looks like the lxc-start command got stuck, after killing the process
everything went back to normal.
root@ares:~# netstat -x | grep lxc
unix 2 [ ] STREAM CONNECTING0
@/var/lib/lxc/myvm/command
unix 2 [ ] STREAM CONNECTING0
@/var/lib/lxc/myvm/command
unix 2 [ ] STREAM CONNECTING0
@/var/lib/lxc/myvm/command
unix 2 [ ] STREAM CONNECTING0
@/var/lib/lxc/myvm/command
unix 2 [ ] STREAM CONNECTING0
@/var/lib/lxc/myvm/command
unix 2 [ ] STREAM CONNECTING0
@/var/lib/lxc/myvm/command
root@ares:~# ps -ef | grep lxc
root 1697 1250 0 Okt06 ?00:00:00 strace lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
root 1704 1697 0 Okt06 ?00:00:00 lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
lxc-dns+ 13856 1 0 Okt05 ?00:00:00 dnsmasq -u lxc-dnsmasq
--strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid
--conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254
--dhcp-lease-max=253 --dhcp-no-override --except-interface=lo
--interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases
--dhcp-authoritative
root@ares:~# ps -ef | grep 1697
root 1697 1250 0 Okt06 ?00:00:00 strace lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
root 1704 1697 0 Okt06 ?00:00:00 lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
root 15861 21116 0 08:12 pts/16 00:00:00 grep --color=auto 1697
root@ares:~# kill -3 1697
root@ares:~# ps -ef | grep lxc-start
root 15870 21116 0 08:13 pts/16 00:00:00 grep --color=auto lxc-start
root@ares:~# lxc-ls --fancy
NAME STATE IPV4 IPV6 AUTOSTART
--
root@ares:~# lxc-destroy -n myvm
Container is not defined
still, I find it a bit strange that not even lxc-ls was working properly
On Mon, Oct 6, 2014 at 4:57 PM, Serge Hallyn 1377...@bugs.launchpad.net
wrote:
thanks for reporting this bug.
Could you please show:
1. The result of 'netstat -x | grep lxc'
2. ps -ef | grep lxc
status: incomplete
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1377973
Title:
lxc-destroy/lxc-stop gets stuck
Status in “lxc” package in Ubuntu:
Incomplete
Bug description:
On ubuntu 14.04 I ran lxc-start with a custom built container and
interrupted the setup before it could finish. Now lxc-ls --fancy, lxc-
destroy -n container or lxc-stop -n container are getting stuck. LXC
package version is 1.0.5-0ubuntu0.1
Output from strace:
# strace lxc-destroy -n myvm
mkdir(/, 0755)= -1 EEXIST (File exists)
mkdir(/run/, 0755)= -1 EEXIST (File exists)
mkdir(/run/lock/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/lib/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/lib/lxc, 0755) = -1 EEXIST (File exists)
stat(/var/lib/lxc/myvm/config, 0x7fff06d64f50) = -1 ENOENT (No such
file or directory)
stat(/var/lib/lxc/myvm/partial, 0x7fff06d64e80) = -1 ENOENT (No such
file or directory)
socket(PF_LOCAL, SOCK_STREAM, 0)= 3
connect(3, {sa_family=AF_LOCAL, sun_path=@/var/lib/lxc/myvm/command},
28) = 0
getuid()= 0
getgid()= 0
sendmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=32,
{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=2028,
uid=0, gid=0}}, msg_flags=0}, MSG_NOSIGNAL) = 16
recvmsg(3,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+subscriptions
--
Pozdrav / Regards,
Nikola Krzalic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1377973
Title:
lxc-destroy/lxc-stop gets stuck
Status in “lxc” package in Ubuntu:
Incomplete
Bug description:
On ubuntu 14.04 I ran lxc-start with a custom built container and
interrupted the setup before it could finish. Now lxc-ls --fancy, lxc-
destroy -n container or lxc-stop -n container are getting stuck. LXC
package version is 1.0.5-0ubuntu0.1
Output from strace:
# strace lxc-destroy -n myvm
mkdir(/, 0755)= -1 EEXIST (File exists)
mkdir(/run/, 0755)= -1 EEXIST (File exists)
mkdir(/run/lock/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc
[Touch-packages] [Bug 1377973] [NEW] lxc-destroy/lxc-stop gets stuck
Public bug reported:
On ubuntu 14.04 I ran lxc-start with a custom built container and
interrupted the setup before it could finish. Now lxc-ls --fancy, lxc-
destroy -n container or lxc-stop -n container are getting stuck. LXC
package version is 1.0.5-0ubuntu0.1
Output from strace:
# strace lxc-destroy -n myvm
mkdir(/, 0755)= -1 EEXIST (File exists)
mkdir(/run/, 0755)= -1 EEXIST (File exists)
mkdir(/run/lock/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/lib/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/lib/lxc, 0755) = -1 EEXIST (File exists)
stat(/var/lib/lxc/myvm/config, 0x7fff06d64f50) = -1 ENOENT (No such file or
directory)
stat(/var/lib/lxc/myvm/partial, 0x7fff06d64e80) = -1 ENOENT (No such file or
directory)
socket(PF_LOCAL, SOCK_STREAM, 0)= 3
connect(3, {sa_family=AF_LOCAL, sun_path=@/var/lib/lxc/myvm/command}, 28) = 0
getuid()= 0
getgid()= 0
sendmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0,
16}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_CREDENTIALS{pid=2028, uid=0, gid=0}}, msg_flags=0}, MSG_NOSIGNAL)
= 16
recvmsg(3,
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1377973
Title:
lxc-destroy/lxc-stop gets stuck
Status in “lxc” package in Ubuntu:
New
Bug description:
On ubuntu 14.04 I ran lxc-start with a custom built container and
interrupted the setup before it could finish. Now lxc-ls --fancy, lxc-
destroy -n container or lxc-stop -n container are getting stuck. LXC
package version is 1.0.5-0ubuntu0.1
Output from strace:
# strace lxc-destroy -n myvm
mkdir(/, 0755)= -1 EEXIST (File exists)
mkdir(/run/, 0755)= -1 EEXIST (File exists)
mkdir(/run/lock/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/lib/, 0755) = -1 EEXIST (File exists)
mkdir(/run/lock/lxc//var/lib/lxc, 0755) = -1 EEXIST (File exists)
stat(/var/lib/lxc/myvm/config, 0x7fff06d64f50) = -1 ENOENT (No such file or
directory)
stat(/var/lib/lxc/myvm/partial, 0x7fff06d64e80) = -1 ENOENT (No such file
or directory)
socket(PF_LOCAL, SOCK_STREAM, 0)= 3
connect(3, {sa_family=AF_LOCAL, sun_path=@/var/lib/lxc/myvm/command}, 28) = 0
getuid()= 0
getgid()= 0
sendmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=32,
{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=2028, uid=0,
gid=0}}, msg_flags=0}, MSG_NOSIGNAL) = 16
recvmsg(3,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+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
