[Touch-packages] [Bug 2017984] Re: Microsoft Edge "Save as" dialog is not in dark mode
Sorry for the delay. The same behavior is in firefox browser ** Attachment added: "Issue in firefox" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+attachment/5670431/+files/Screenshot%20from%202023-05-02%2023-07-35.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017984 Title: Microsoft Edge "Save as" dialog is not in dark mode Status in gtk+3.0 package in Ubuntu: Incomplete Status in yaru-theme package in Ubuntu: New Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2017984/+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 2017984] [NEW] "Save as" window from browser is not in dark mode
Public bug reported: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session ** Attachment added: "Screenshot from 2023-04-28 12-31-38.png" https://bugs.launchpad.net/bugs/2017984/+attachment/5669369/+files/Screenshot%20from%202023-04-28%2012-31-38.png -- 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/2017984 Title: "Save as" window from browser is not in dark mode Status in xorg package in Ubuntu: New Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 )
[Touch-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Same issue on HP Envy 17 Alder Lake-P and Realtek ALC245. Tried all LTS kernels, 6.0 & 6.1. Tried on Ubuntu 23.01, 22.04, PopOS 22.04, Manjaro and speakers won't work on any of them. -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1874020] Re: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic
Apparently a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 -- 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/1874020 Title: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic Status in lightdm package in Ubuntu: New Bug description: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874020/+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 1874020] [NEW] Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic
Public bug reported: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) ** Affects: lightdm (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/1874020 Title: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic Status in lightdm package in Ubuntu: New Bug description: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874020/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
Works for me with 5.50-0ubuntu2.1 on an old dell. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Committed Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1680330] Re: lxc-execute can run commands in current namespace
I didn't expect it. While I understand that there is no such entity as "a container" on linux, the functionality of lxc being a construct of several underlying features, lxc appears to me to be trying to construct a consistent abstraction on those features. The unit of reference throughout the documentation is "the container", and seems geared to be towards being able to treat them as atomic units. I can name them, create, delete and snapshot them, given them IP addresses etc. For lxc-execute to function with partial functionality, without warning, breaking the abstraction model of the suite, seems to me to be undesirable behavior. Regards, Tristan -- 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/1680330 Title: lxc-execute can run commands in current namespace Status in lxc package in Ubuntu: Invalid Bug description: If lxc-execute is passed a non-existent container name, then the command given is run in the current namespace. I believe it should failed with a "container not found" error, as otherwise it can lead to unexpected consequences in the host environment. example: # lxc-ls files foreman ns01proxy ## Example typo on the -n option # lxc-execute -n ns1 -- touch /tmp/ns01 # ls -l /tmp/ns01 -rw-r--r-- 1 root root 0 Apr 6 16:07 /tmp/ns01 ## Command ran outside of container! # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1680330/+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 1680330] [NEW] lxc-execute can run commands in current namespace
Public bug reported: If lxc-execute is passed a non-existent container name, then the command given is run in the current namespace. I believe it should failed with a "container not found" error, as otherwise it can lead to unexpected consequences in the host environment. example: # lxc-ls files foreman ns01proxy ## Example typo on the -n option # lxc-execute -n ns1 -- touch /tmp/ns01 # ls -l /tmp/ns01 -rw-r--r-- 1 root root 0 Apr 6 16:07 /tmp/ns01 ## Command ran outside of container! # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" ** 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/1680330 Title: lxc-execute can run commands in current namespace Status in lxc package in Ubuntu: New Bug description: If lxc-execute is passed a non-existent container name, then the command given is run in the current namespace. I believe it should failed with a "container not found" error, as otherwise it can lead to unexpected consequences in the host environment. example: # lxc-ls files foreman ns01proxy ## Example typo on the -n option # lxc-execute -n ns1 -- touch /tmp/ns01 # ls -l /tmp/ns01 -rw-r--r-- 1 root root 0 Apr 6 16:07 /tmp/ns01 ## Command ran outside of container! # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1680330/+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 1434986] Re: Not working network connection after boot
I too am affected by this bug, on Ubuntu 16.04 LTS. The bug has been present for me, in a way or another, since 15.04. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1572041] Re: Can't create click target for armhf
Same problem, also on Ubuntu 16.04. Really disappointing because I was looking forward to developing apps now that I have an Ubuntu tablet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1572041 Title: Can't create click target for armhf Status in click package in Ubuntu: Confirmed Bug description: sudo click chroot -a armhf -f ubuntu-sdk-15.04 create The following packages have unmet dependencies: ubuntu-sdk-libs:armhf : Depends: ubuntu-html5-container:armhf E: Unable to correct problems, you have held broken packages. Command returned 100: schroot -u root -c source:click-ubuntu-sdk-15.04-armhf -- /finish.sh Traceback (most recent call last): File "/usr/bin/click", line 110, in sys.exit(main()) File "/usr/bin/click", line 106, in main return mod.run(args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 266, in run return args.func(parser, args) File "/usr/lib/python3/dist-packages/click/commands/chroot.py", line 68, in create return chroot.create(args.keep_broken_chroot) File "/usr/lib/python3/dist-packages/click/chroot.py", line 599, in create self.full_name, ret_code)) click.chroot.ClickChrootException: Failed to create chroot 'click-ubuntu-sdk-15.04-armhf' (exit status 100) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1572041/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Andrea, a DNS Leak is defined as any DNS traffic going outside your VPN's assigned servers. Even if 8.8.8.8 goes through the VPN, it's still leaking your traffic. https://www.dnsleaktest.com/what-is-a-dns- leak.html -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@Andrea, I tried that, but then my VPN connection uses the static servers. And unless Google DNS connections are encrypted, it's still a DNS leak. -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Same issue for me on 15.10, but it didn't happen on 15.04. Using the script-security 2 option in the configuration file, everything works correctly when run from command line: "sudo openvpn --config file.ovpn" For me, this problem only happens when connecting through Network Manager. -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1518450] [NEW] package libreadline-gplv2-dev 5.2+dfsg-3 fails to install
Public bug reported: I tried installing libreadline-gplv2-dev and libreadline-gplv2-dev:i386 all together and it failed. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreadline-gplv2-dev 5.2+dfsg-3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 Date: Fri Nov 20 15:22:47 2015 DuplicateSignature: Unpacking libreadline-gplv2-dev:i386 (5.2+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 InstallationDate: Installed on 2015-11-05 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151104) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: readline5 Title: package libreadline-gplv2-dev 5.2+dfsg-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: readline5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict xenial ** Summary changed: - package libreadline-gplv2-dev 5.2+dfsg-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 + package libreadline-gplv2-dev 5.2+dfsg-3 fails to install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to readline5 in Ubuntu. https://bugs.launchpad.net/bugs/1518450 Title: package libreadline-gplv2-dev 5.2+dfsg-3 fails to install Status in readline5 package in Ubuntu: New Bug description: I tried installing libreadline-gplv2-dev and libreadline- gplv2-dev:i386 all together and it failed. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreadline-gplv2-dev 5.2+dfsg-3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 Date: Fri Nov 20 15:22:47 2015 DuplicateSignature: Unpacking libreadline-gplv2-dev:i386 (5.2+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-3_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 InstallationDate: Installed on 2015-11-05 (15 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151104) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: readline5 Title: package libreadline-gplv2-dev 5.2+dfsg-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline5/+bug/1518450/+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 1475876] [NEW] PCI/internal sound card not detected
Public bug reported: Pulse Audio will not load, only dummy audio is available. I have tried purging and reinstalling pulse audio to no avail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jul 18 15:05:07 2015 InstallationDate: Installed on 2015-07-18 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0G261D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1475876 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Pulse Audio will not load, only dummy audio is available. I have tried purging and reinstalling pulse audio to no avail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jul 18 15:05:07 2015 InstallationDate: Installed on 2015-07-18 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0G261D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1475876/+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 1308378] Re: Name resolving not working after 12.04 LTS - 14.04 LTS if /etc/resolv.conf was absent
I had a similar issue but not quite the same. I upgraded from Precise (installed at the factory on a Dell Sputnik device) to Trusty. After upgrade, DNS did not work. I did have the /etc/resolv.conf symlink, but the content generated by resolvconf just listed 127.0.0.1 twice (the old address). Following the suggestion at http://askubuntu.com/a/462377/75121, I purged and reinstalled resolvconf --which didn't immediately fix it--and then rebooted. After reboot, the resolv.conf now lists the correct address of 127.0.1.1 followed by the old address of 127.0.0.1, and DNS resolution works. -- 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/1308378 Title: Name resolving not working after 12.04 LTS - 14.04 LTS if /etc/resolv.conf was absent Status in “resolvconf” package in Ubuntu: Won't Fix Status in “resolvconf” source package in Trusty: Fix Released Status in “resolvconf” source package in Utopic: Won't Fix Bug description: [Impact] Name resolving using the NetworkManager-controlled nameserver discontinues working after upgrading from 12.04 (precise) to 14.04 (trusty) in the case where /etc/resolv.conf is absent. Precise works fine with that file absent because the resolver defaults to using nameserver 127.0.0.1 — so it is possible to run Precise for a long time without even noticing that the file is absent. In Trusty, resolving does not work if /etc/resolv.conf is absent because the NetworkManager-controlled nameserver listens at 127.0.1.1. People suffering from bug #1000244 may lack /etc/resolv.conf on upgrade. [Test Case] 1. Install 12.04 LTS 2. rm /etc/resolv.conf and observe everything works fine 3. update-manager -c -d 4. Observe that in 14.04 LTS name resolving does not work. [Test Case for testing the fix on 14.04] 1. wget http://de.archive.ubuntu.com/ubuntu/pool/main/r/resolvconf/resolvconf_1.63ubuntu16_all.deb 2. dpkg -i resolvconf_1.63ubuntu16_all.deb 3. Running that precise version, test the possible cases like rm /etc/resolv.conf (note you lose name resolving at this point in 14.04) 4. Run 'bzr bd' (apt-get install bzr-builddeb first) in the proposed branch, dpkg -i ../build-area/*.deb 5. Check how either, depending on the case being tested, /etc/resolv.conf is intact / non-touched or it's created when not-existing, restoring network connectivity [Regression Potential] Seems low considering the limiting of the proposed fix to 12.04 - 14.04 upgrades only, and only in the case of the user/3rd party app/something intentionally removed /etc/resolv.conf (instead of just modifying it). --- I fixed it manually with: cd /etc sudo ln -s /run/resolvconf/resolv.conf . It turns out 12.04 LTS works fine without /etc/resolv.conf, so that increases the likelihoods that 12.04 LTS systems do not have that file. When such a system is upgraded to 14.04 LTS, network seemingly stops working to the user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1308378/+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