[Touch-packages] [Bug 1846988] Re: [Audio playback] No 'Speaker - Built-in Audio'
Please test mainline kernel v5.3, let us see if this kernel works or not. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3/ -- 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/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' Status in alsa-driver package in Ubuntu: New Bug description: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer /dev/snd/pcmC0D0c: lawrence 2033 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 09:27:18 2019 InstallationDate: Installed on 2019-09-07 (29 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TMB dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: IT Channel Pty Ltd dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: IT Channel Pty Ltd dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TMB:bd04/10/2019:svnITChannelPtyLtd:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnITChannelPtyLtd:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnITChannelPtyLtd:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: IT Channel Pty Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-07T11:50:26.934452 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846988/+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 1838912] Re: Bluetooth doesn't remember my Logitech MX Master mouse.
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1838912 Title: Bluetooth doesn't remember my Logitech MX Master mouse. Status in bluez package in Ubuntu: Expired Bug description: I can pair my mouse, and sometimes Ubuntu will remember it, but more often it doesn't automatically connect when I turn the computer on or wake it up. I've noticed that it'll have the same BT address, so it should connect (?). When it DOES connect, it's when I've had the mouse turned off and don't turn it on until Ubuntu is completely awake and running. That doesn't always work, but if I have the mouse turned on before turning Ubuntu on, then it never connects. I have to re-pair them. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 18:40:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838912/+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 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Do you mean the you can't hear sound from headphone or lineout jack? -- 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/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+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 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1463 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1463 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1463 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:46:25 2019 DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a] InstallationDate: Installed on 2019-07-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID :0538 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1846941/+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 1846899] Re: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic)
Searching nvidia.com for that GPU seems to recommend installing driver '430.50'. So please try: sudo apt install nvidia-driver-430 At present that will give you 430.26 but version 430.50 is in bionic- proposed so will come in a future update for Ubuntu 18.04, soonish. ** Summary changed: - X won't start at boot with either nvidia driver + X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- 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/1846899 Title: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846899/+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 1846807] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1846807 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: When upgrade (include firmware update) can't see login screen when i use startx looping login screen Upgrade to 19.10 and install lightdm still again when i use wayland is ok. other gnome, gnome-classic, ubuntu is looping ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 00:50:39 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-01-22 (254 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) MachineType: LENOVO 20KH007UVA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007UVA 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.modalias: dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007UVA dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846807/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
sorry for getting back to you late. Tried to collect the logs under windows with RtHDDump but error reported: "The HD audio codec could not be found in your system" But the mic is working. Attached the error message. ** Attachment added: "error_pic.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5294928/+files/error_pic.png -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846988] [NEW] [Audio playback] No 'Speaker - Built-in Audio'
Public bug reported: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer /dev/snd/pcmC0D0c: lawrence 2033 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 09:27:18 2019 InstallationDate: Installed on 2019-09-07 (29 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TMB dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: IT Channel Pty Ltd dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: IT Channel Pty Ltd dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TMB:bd04/10/2019:svnITChannelPtyLtd:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnITChannelPtyLtd:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnITChannelPtyLtd:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: IT Channel Pty Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-07T11:50:26.934452 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' Status in alsa-driver package in Ubuntu: New Bug description: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue.
[Touch-packages] [Bug 1846984] [NEW] package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: got this bug by updating , I don't know any more than this ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2019c-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189 Uname: Linux 4.4.0-165-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Sun Oct 6 13:23:37 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-09-09 (392 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tzdata Title: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-09 (392 days ago) ** Affects: tzdata (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 tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1846984 Title: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: New Bug description: got this bug by updating , I don't know any more than this ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2019c-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189 Uname: Linux 4.4.0-165-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Sun Oct 6 13:23:37 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-09-09 (392 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tzdata Title: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-09 (392 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1846984/+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 1846984] Re: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1846984 Title: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: New Bug description: got this bug by updating , I don't know any more than this ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2019c-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-165.193-generic 4.4.189 Uname: Linux 4.4.0-165-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Sun Oct 6 13:23:37 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-09-09 (392 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: tzdata Title: package tzdata 2019c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-09 (392 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1846984/+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 1843768] Re: [FFe] Ubiquity with zfs install option
** Changed in: ubuntustudio-meta (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1843768 Title: [FFe] Ubiquity with zfs install option Status in ubiquity package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Committed Bug description: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. Update as of 20/09/2019: the plan is to not seed zsys (security review will take a while), but to only seed zfsutils-linux. People can then opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+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 1843768] Re: [FFe] Ubiquity with zfs install option
Here is the patch to fix the FTBFS on archs without grub-installer: diff --git a/debian/rules b/debian/rules index a90e57f1f..f6a758cf4 100755 --- a/debian/rules +++ b/debian/rules @@ -161,8 +161,10 @@ endif < d-i/patches/localechooser-post-base-installer.patch patch debian/ubiquity/lib/partman/finish.d/25create_swapfile \ < d-i/patches/partman-swapfile-background.patch +ifeq (,$(filter armhf ppc64el s390x,$(DEB_HOST_ARCH))) patch debian/ubiquity/usr/share/grub-installer/grub-installer \ < d-i/patches/zfs-0.8-support.patch +endif chmod +x debian/ubiquity/usr/lib/ubiquity/localechooser/post-base-installer sed 's/\\\$${!TAB}/ /g' \ debian/ubiquity/usr/lib/ubiquity/localechooser/localechooser \ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1843768 Title: [FFe] Ubiquity with zfs install option Status in ubiquity package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: In Progress Bug description: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. Update as of 20/09/2019: the plan is to not seed zsys (security review will take a while), but to only seed zfsutils-linux. People can then opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+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 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
I can confirm the behavior. At least its possible to deactivate 'discoverable' and 'discovery' on the command line: sudo hiconfig hci0 noscan Interesting: This survives a reboot! Note: 'discoverable' and 'discovery' is switched-on again when selecting the Bluetooth settings. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1846140] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1846140 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1843768] Re: [FFe] Ubiquity with zfs install option
** Also affects: ubuntustudio-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntustudio-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntustudio-meta (Ubuntu) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1843768 Title: [FFe] Ubiquity with zfs install option Status in ubiquity package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: In Progress Bug description: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. Update as of 20/09/2019: the plan is to not seed zsys (security review will take a while), but to only seed zfsutils-linux. People can then opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+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 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
For me it looks more like a kernel issue, as the Wi-Fi principally works (network-manager must have set it up correctly). The weak signal issue looks more like something in the driver. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 I get the following for the Logitech H800 wireless headset (without "headset"): Device 00:0D:44:D2:71:61 (public) Name: H800 Logitech Headset Alias: H800 Logitech Headset Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
Here is a link to the code (& log) regarding the impress remote project: https://cgit.freedesktop.org/libreoffice/impress_remote/ I have a presentation upcoming in three days and really would have liked to use the remote feature to impress/wow the audience. There's not enough time for me to dig into the code and try to determine the state of bluetooth vis-a-vis Android and Impress. Looks like something that might require 10-20 hours to master just to assess. Agree: it doesn't behoove the project to advertise features which may not work, e.g. remote impress. Using Gentoo Linux (4.19.72-gentoo) on a Dell Inspiron 17 5000 laptop purchased October 2018 (Bluetooth 4) with net-wireless/bluez 5.50-r2 against an Android 7.0, kernel version 3.10.49, model LGL158VL -- 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/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
The issue is present in ibus version 1.5.17-3ubuntu5.2 running in KDE Neon (based on Ubuntu 18.04) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1846941] [NEW] Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
Public bug reported: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:46:25 2019 DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a] InstallationDate: Installed on 2019-07-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID :0538 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan possible-manual-nvidia-install third-party-packages ubuntu ** Summary changed: - Since upgrading to Eoan Ermine the screen doesn't dim progressively before going to sleep, but at once. + Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. -- 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/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. Status in xorg package in Ubuntu: New Bug description: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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
[Touch-packages] [Bug 1846930] [NEW] [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Public bug reported: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1839501] Re: Can't Switch between Nvidia Drivers because of error in SoftwarePropertiesQt.py
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1839501 Title: Can't Switch between Nvidia Drivers because of error in SoftwarePropertiesQt.py Status in software-properties package in Ubuntu: Confirmed Bug description: Hardware: Dell Latitude E6430 with GF108GLM [NVS 5200m] Lubuntu 19.04 LBS Release: Description:Ubuntu 19.04 software-properties-qt: Installed: 0.97.11 Candidate: 0.97.11 Version table: *** 0.97.11 500 500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status I ran "Additional Drivers" from the menu and switched from Nouveau to the nvidia-driver-418 to see how it ran. After testing for a couple days I tried to switch back. When I select Nouveau and click "Apply changes" nothing happens. I ran software-properties-qt from the command line and get this error when I click "Apply Changes". #lxsudo /usr/bin/software-properties-qt '--open-tab=4' (0x7ffda7818770) Warning: Icon theme "breeze" not found. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 845, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined I searched through the source and I'm guessing it's the extra parameter 'nvidia' at the end that's causing the issue, since there's no 3 parameter function definition for get_dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1839501/+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 1768190] Re: prepend domain-name-servers does not parse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1768190 Title: prepend domain-name-servers does not parse Status in isc-dhcp package in Ubuntu: Confirmed Bug description: "prepend domain-name-servers ;" in /etc/dhcp/dhclient.conf fails on Ubuntu from as early as artful and also tested on bionic the result is that /etc/resolv.conf never shows "nameserver " however on other distributions this works as expected.. (other distributions use an earlier version of 4.3.1) simply append this to the dhclient.conf file, or create a lease section .. it always fails.. perhaps something after 4.3.1 upstream... please take a look thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1768190/+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 1768190] Re: prepend domain-name-servers does not parse
Maybe something to do with https://bugs.launchpad.net/ubuntu/+source /isc-dhcp/+bug/1845793? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1768190 Title: prepend domain-name-servers does not parse Status in isc-dhcp package in Ubuntu: Confirmed Bug description: "prepend domain-name-servers ;" in /etc/dhcp/dhclient.conf fails on Ubuntu from as early as artful and also tested on bionic the result is that /etc/resolv.conf never shows "nameserver " however on other distributions this works as expected.. (other distributions use an earlier version of 4.3.1) simply append this to the dhclient.conf file, or create a lease section .. it always fails.. perhaps something after 4.3.1 upstream... please take a look thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1768190/+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