[Touch-packages] [Bug 1650536] Re: wrong behaviour of interface - audio specific
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1650536 Title: wrong behaviour of interface - audio specific Status in pulseaudio package in Ubuntu: Expired Bug description: report 1 no audio on audio jack 2 in trying to fix after testing sound with the audio test Right and Left i changed the stereo to 5-1 surround option available in the test windows 3 this caused to remove from the audio setting windows all output devices ( now is empty) Audio stopped working completely and the volume in the top bar had the x and I cannot activate. is gray 4 I just update the system with regular updates and the sound now work on the browser but the volume still have an x and is greyed but the Audio is active!! I can hear sound on video on youtube and and play music but I cannot adjust volume. 5 try to activate pavucontrol but get message " establishing connection with pulseaudio please wait " but no responce system information: Linux jaki-XPS-13-9350 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux suppose to be one of the certified laptop Regarding the jack still do not work and when inserted the jack the audio from internal speaker stop but there is no output. Dell changed the motherboard but the problem persisted, tried windows 10 on a live usb memory and sound worked out of the jack. willing to let someone to log on the system and check remotely jaki@jaki-XPS-13-9350:~$ xprop WM_CLASS WM_CLASS(STRING) = "unity-control-center", "Unity-control-center" unity-control-center: Installato: 15.04.0+16.04.20160705-0ubuntu1 Candidato: 15.04.0+16.04.20160705-0ubuntu1 Tabella versione: *** 15.04.0+16.04.20160705-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 15.04.0+16.04.20160413-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages jaki@jaki-XPS-13-9350:~$ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Dec 16 13:29:44 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-25 (174 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to xenial on 2016-09-07 (99 days ago) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0H67KH dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1650536/+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 1794997] Re: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1794997 Title: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available Status in libnl3 package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Bug description: We are observing the following error while creating VMs Sep 27 14:25:47 xpl-dvt-41 libvirtd[4927]: 2018-09-27 21:25:47.387+: 4927: error : virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available This message is observed with latest Bionic libvirt packages. lab@xpl-dvt-35:~$ dpkg -l | grep libvirt ii gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 amd64GObject introspection files for the libvirt-glib library ii libsys-virt-perl 4.0.0-1 amd64Perl module providing an extension for the libvirt library ii libvirt-bin 4.0.0-1ubuntu8.5 amd64programs for the libvirt library ii libvirt-clients 4.0.0-1ubuntu8.5 amd64Programs for the libvirt library ii libvirt-daemon4.0.0-1ubuntu8.5 amd64Virtualization daemon ii libvirt-daemon-system 4.0.0-1ubuntu8.5 amd64Libvirt daemon configuration files ii libvirt-glib-1.0-0:amd64 1.0.0-1 amd64libvirt GLib and GObject mapping library ii libvirt0:amd644.0.0-1ubuntu8.5 amd64library for interfacing with different virtualization systems ii python-libvirt4.0.0-1 amd64libvirt Python bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1794997/+subscriptions -- Mailing list: https://launchpad.net/~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 1690933] Re: isc-dhcp-server/dhcpd listens on 0.0.0.0:67/UDP no matter which interfaces is specified
[Expired for isc-dhcp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: isc-dhcp (Ubuntu) Status: Incomplete => Expired -- 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/1690933 Title: isc-dhcp-server/dhcpd listens on 0.0.0.0:67/UDP no matter which interfaces is specified Status in isc-dhcp package in Ubuntu: Expired Bug description: The behaviour of the `systemd` unit `isc-dhcp-server.service` is the same as on the command line: both `sudo dhcpd` and `sudo dhcpd p18p1` (where `p18p1` is the name of a network interfaces) cause the daemon to listen on all interfaces according to `sudo netstat -tupln | grep :67`: udp0 0 0.0.0.0:67 0.0.0.0:* 5382/dnsmasq The `isc-dhcp-server6.service` unit is deactivated. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: isc-dhcp-server 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 15 23:41:54 2017 DhServerLeases: InstallationDate: Installed on 2015-04-20 (756 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to zesty on 2017-05-05 (9 days ago) mtime.conffile..etc.dhcp.dhcpd.conf: 2017-05-15T23:37:21.502892 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1690933/+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 1799353] Re: [Realtek ALC892, Green Line Out, Rear] No sound
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1799353 Title: [Realtek ALC892, Green Line Out, Rear] No sound Status in pulseaudio package in Ubuntu: Expired Bug description: Pulseaudio does not detect the card too. Configuration tab says that there are no cards available for configuration. In the settings, the only output device listed is Unix FIFO Sink (points to a chrome remote desktop extension's file). No other output devices are listed in the settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 11:37:32 2018 InstallationDate: Installed on 2017-01-19 (642 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA ATI SB Symptom_Jack: Green Line Out, Rear Title: [To be filled by O.E.M., Realtek ALC892, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: Upgraded to bionic on 2018-09-24 (28 days ago) dmi.bios.date: 08/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/15/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799353/+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 1794997] Re: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available
[Expired for libnl3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libnl3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1794997 Title: virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available Status in libnl3 package in Ubuntu: Expired Status in libvirt package in Ubuntu: Expired Bug description: We are observing the following error while creating VMs Sep 27 14:25:47 xpl-dvt-41 libvirtd[4927]: 2018-09-27 21:25:47.387+: 4927: error : virNetlinkEventCallback:700 : nl_recv returned with error: No buffer space available This message is observed with latest Bionic libvirt packages. lab@xpl-dvt-35:~$ dpkg -l | grep libvirt ii gir1.2-libvirt-glib-1.0:amd64 1.0.0-1 amd64GObject introspection files for the libvirt-glib library ii libsys-virt-perl 4.0.0-1 amd64Perl module providing an extension for the libvirt library ii libvirt-bin 4.0.0-1ubuntu8.5 amd64programs for the libvirt library ii libvirt-clients 4.0.0-1ubuntu8.5 amd64Programs for the libvirt library ii libvirt-daemon4.0.0-1ubuntu8.5 amd64Virtualization daemon ii libvirt-daemon-system 4.0.0-1ubuntu8.5 amd64Libvirt daemon configuration files ii libvirt-glib-1.0-0:amd64 1.0.0-1 amd64libvirt GLib and GObject mapping library ii libvirt0:amd644.0.0-1ubuntu8.5 amd64library for interfacing with different virtualization systems ii python-libvirt4.0.0-1 amd64libvirt Python bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1794997/+subscriptions -- Mailing list: https://launchpad.net/~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 1798712] Re: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)
[Expired for rtkit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rtkit (Ubuntu) Status: Incomplete => Expired -- 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/1798712 Title: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic) Status in pulseaudio package in Ubuntu: Expired Status in rtkit package in Ubuntu: Expired Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1798712] Re: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic)
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1798712 Title: [System76 Oryx Pro] No sound for the first 10 minutes (18.10 Cosmic) Status in pulseaudio package in Ubuntu: Expired Status in rtkit package in Ubuntu: Expired Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+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 1799564] Re: Consists of version 18.04 after update to 18.10 Cosmic
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- 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/1799564 Title: Consists of version 18.04 after update to 18.10 Cosmic Status in software-properties package in Ubuntu: Expired Bug description: Mesmo após atualização da versão 18.04 LTS para 18.10 Cosmic as informações contidas em "Programas e Atualizações" no campo outros programas, as informações mantidas são as do Ubuntu 18.04 LTS Bionic. Após atualização as informações não deveriam constar como 18.10 Cosmic? Desde já agradeço pela atenção. Segue em anexo imagens das informações. *** Consists of version 18.04 after update to 18.10 Cosmic Even after updating version 18.04 LTS to 18.10 Cosmic the information contained in "Programs and Updates" in the other programs field, the information maintained are those of Ubuntu 18.04 LTS Bionic. After updating the information should not appear as 18.10 Cosmic? I thank you for your attention. Attached is information images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1799564/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
my /etc/initramfs-tools/conf.d/resume file contains one line RESUME=UUID=99a2d3b2-0f29-4080-977c-35a5744279a8 I have tried several suggestions in this thread but I haven't found anything that works. I tried RESUME=/dev/vg_system/lv_swap then I ran the update-initramfs -u, as suggested. I got this: update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic W: initramfs-tools configuration sets RESUME=/dev/vg_system/lv_swap W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/dm-1 I: (UUID=99a2d3b2-0f29-4080-977c-35a5744279a8) I: Set the RESUME variable to override this. I'm not what to do from here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Confirmed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1809563] Re: package linux-firmware 1.157.20 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1809563 Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I was trying to let Ubuntu install the package to allow access to a W7 computer via LAN ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.20 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Dec 22 12:27:00 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-12-22 12:26:27 Commandline: aptdaemon role='role-commit-packages' sender=':1.97' Install: python-tdb:amd64 (1.3.8-2, automatic), python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), python-dnspython:amd64 (1.12.0-1, automatic), samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18), samba-dsdb-modules:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), libaio1:amd64 (0.3.110-2, automatic), tdb-tools:amd64 (1.3.8-2, automatic), attr:amd64 (1:2.4.47-2, automatic), python-crypto:amd64 (2.6.1-6ubuntu0.16.04.3, automatic), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), samba-vfs-modules:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), samba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), python-ldb:amd64 (2:1.1.24-1ubuntu3, automatic) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-14 (311 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1809563/+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 1809563] [NEW] package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I was trying to let Ubuntu install the package to allow access to a W7 computer via LAN ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.20 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Dec 22 12:27:00 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-12-22 12:26:27 Commandline: aptdaemon role='role-commit-packages' sender=':1.97' Install: python-tdb:amd64 (1.3.8-2, automatic), python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), python-dnspython:amd64 (1.12.0-1, automatic), samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18), samba-dsdb-modules:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), libaio1:amd64 (0.3.110-2, automatic), tdb-tools:amd64 (1.3.8-2, automatic), attr:amd64 (1:2.4.47-2, automatic), python-crypto:amd64 (2.6.1-6ubuntu0.16.04.3, automatic), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), samba-vfs-modules:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), samba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), python-ldb:amd64 (2:1.1.24-1ubuntu3, automatic) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-14 (311 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1809563 Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I was trying to let Ubuntu install the package to allow access to a W7 computer via LAN ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.20 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Dec 22 12:27:00 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-12-22 12:26:27 Commandline: aptdaemon role='role-commit-packages' sender=':1.97' Install: python-tdb:amd64 (1.3.8-2, automatic), python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), python-dnspython:amd64 (1.12.0-1, automatic), samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18), samba-dsdb-modules:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), libaio1:amd64 (0.3.110-2, automatic), tdb-tools:amd64 (1.3.8-2, automatic), attr:amd64 (1:2.4.47-2, automatic), python-crypto:amd64 (2.6.1-6ubuntu0.16.04.3, automatic), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), samba-vfs-modules:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), samba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.18, automatic), python-ldb:amd64 (2:1.1.24-1ubuntu3, automatic) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-14 (311 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.20 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1809563/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Hi everyone, right now I've got an emergency mode only with 18.04 (kde neon) and systemd=237-3ubuntu10.9 with btrfs. Is there a patch for 18.04/bionic that could be tested out? Seems like LTS release has been forgotten about. Downgrading to 237-3ubuntu10 isn't an option as it breaks ton of dependencies. Thanks for any suggestions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1025388] Re: Internal mic stops working when plugging in headphones
Confirming x1 5th gen. Any updates? -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1025388/+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 1809492] Re: nocache rsync files beween directories on ubuntu 18.10 stuck
more info here https://github.com/Feh/nocache/issues/34 ** Bug watch added: github.com/Feh/nocache/issues #34 https://github.com/Feh/nocache/issues/34 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1809492 Title: nocache rsync files beween directories on ubuntu 18.10 stuck Status in rsync package in Ubuntu: New Bug description: Hi I have weird problem on ubuntu 18.10 We use rsync in our scripts in armbian distro (armbian.com) for syncing files between directories and this don't work for some reason nocache rsync /home/someuser/folder1/ /home/someuser/folder2/ but this is working just fine rsync /home/someuser/folder1/ /home/someuser/folder2/ you can reproduce this on ubuntu 18.10 x86 64bit everything works fine on ubuntu 18.04 I checked packages rsync, nocache on ubuntu 18.10 and 18.04 and it looks like same versions rsync 3.1.2-2.2 nocache 1.0-1 So any idea where is problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1809492/+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 1809554] [NEW] Daemon "docker" not enabled after installation of "docker.io" on Ubuntu 18.04
Public bug reported: Hi @all, On a updated Ubuntu 18.04, if I installed docker via the package "docker.io" (from universe), the daemon "docker" is not enabled by default as you can seen in the following paste: - ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic ~# apt-get install -y docker.io Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libltdl7 Suggested packages: aufs-tools btrfs-progs debootstrap docker-doc rinse zfs-fuse | zfsutils Recommended packages: cgroupfs-mount | cgroup-lite git pigz ubuntu-fan The following NEW packages will be installed: docker.io libltdl7 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 40.2 MB of archives. After this operation, 198 MB of additional disk space will be used. Get:1 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 libltdl7 amd64 2.4.6-2 [38.8 kB] Get:2 http://fr.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 docker.io amd64 18.06.1-0ubuntu1~18.04.1 [40.2 MB] Fetched 40.2 MB in 1s (73.5 MB/s) Preconfiguring packages ... Selecting previously unselected package libltdl7:amd64. (Reading database ... 100286 files and directories currently installed.) Preparing to unpack .../libltdl7_2.4.6-2_amd64.deb ... Unpacking libltdl7:amd64 (2.4.6-2) ... Selecting previously unselected package docker.io. Preparing to unpack .../docker.io_18.06.1-0ubuntu1~18.04.1_amd64.deb ... Unpacking docker.io (18.06.1-0ubuntu1~18.04.1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10.9) ... Setting up libltdl7:amd64 (2.4.6-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up docker.io (18.06.1-0ubuntu1~18.04.1) ... Adding group `docker' (GID 112) ... Done. Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket. Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10.9) ... Processing triggers for ureadahead (0.100.0-20) ... ~# apt-cache policy docker.io docker.io: Installed: 18.06.1-0ubuntu1~18.04.1 Candidate: 18.06.1-0ubuntu1~18.04.1 Version table: *** 18.06.1-0ubuntu1~18.04.1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 17.12.1-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ~# systemctl is-enabled docker.service disabled - And of course, after a reboot, the daemon "docker" is not started automatically. So in the postinst script of the package "docker.io" maybe a kind of "systemctl enable docker.service" is missing, no? Regards. ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Package changed: mountall (Ubuntu) => docker.io (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1809554 Title: Daemon "docker" not enabled after installation of "docker.io" on Ubuntu 18.04 Status in docker.io package in Ubuntu: New Bug description: Hi @all, On a updated Ubuntu 18.04, if I installed docker via the package "docker.io" (from universe), the daemon "docker" is not enabled by default as you can seen in the following paste: - ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic ~# apt-get install -y docker.io Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libltdl7 Suggested packages: aufs-tools btrfs-progs debootstrap docker-doc rinse zfs-fuse | zfsutils Recommended packages: cgroupfs-mount | cgroup-lite git pigz ubuntu-fan The following NEW packages will be installed: docker.io libltdl7 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 40.2 MB of archives. After this operation, 198 MB of additional disk space will be used. Get:1 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 libltdl7 amd64 2.4.6-2 [38.8 kB] Get:2 http://fr.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 docker.io amd64 18.06.1-0ubuntu1~18.04.1 [40.2 MB] Fetched 40.2 MB in 1s (73.5 MB/s) Preconfiguring packages ... Selecting previously unselected package libltdl7:amd64. (Reading database ... 100286 files and directories curr
[Touch-packages] [Bug 1809552] Re: Ubuntu sees duplicate display for each graphics card on Macbook Pro
I should specify, the specific model of Macbook Pro which I am using is the mid-2012 15" version (version 10,1) -- 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/1809552 Title: Ubuntu sees duplicate display for each graphics card on Macbook Pro Status in xorg package in Ubuntu: New Bug description: After booting Ubuntu in BIOS mode on my machine for years, I just switched over to EFI boot. The reason for which I switched is that, on this machine, Ubuntu cannot detect the integrated GPU under BIOS boot. Ubuntu now recognizes both integrated and discrete GPU on my machine, but it also seems to think I have two monitors. Expected Behavior: Ubuntu properly recognizes that both graphics cards are in fact controlling the same display Actual Behavior: Ubuntu thinks I have two displays (each being controlled by a separate card?). If I navigate to the "Devices > Displays" section of the settings app, then Ubuntu lists two "Built in Displays," and offers options to "Join Displays," mirror them, etc. I have created a question on AskUbuntu (https://askubuntu.com/questions/1103696/ubuntu-duplicates-display- for-each-graphics-card-fresh-install) detailing this issue; it presents much of the same information in this bug report, along with several images. I have also discovered a similar thread from three years ago (https://askubuntu.com/questions/582574/my-macbook-has-two-built-in- displays) suggesting that I am not the only Macbook user to suffer from this issue. The user in said thread worked around this issue by powering off his iGPU. I would like to set up graphics switching in the future, so this is not an option for me. In any case, I have tested his "solution" and it DOES NOT work on my machine (I also don't have a /sys/kernel/debug/vgaswitcheroo folder like he apparently does) SYSTEM INFORMATION OS Version: Ubuntu (64-bit) 18.04.1 Kernel: 4.15.0-43-generic GRAPHICS CARD INFORMATION == $ lshw -c video *-display description: VGA compatible controller product: GK107M [GeForce GT 650M Mac Edition] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:45 memory:c000-c0ff memory:9000-9fff memory:a000-a1ff ioport:2000(size=128) memory:c100-c107 *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:47 memory:c140-c17f memory:b000-bfff ioport:3000(size=64) MORE GRAPHICS CARD INFORMATION == $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] (rev a1) DISPLAY CONFIGURATION INFO (1) == NOTE: In this diagnostic, I have chosen the "Single Display" option via the System Settings app. Only one of the two "built-in displays" is actually usable, selecting the other just gives me a black screen until my changes are auto-reverted $ xrandr - q Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384 LVDS-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1440x900 59.90*+ 1152x864 59.97 1024x768 59.95 800x600 59.96 640x480 59.94 720x400 59.97 640x400 59.96 640x350 59.84 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) LVDS-1-2 connected (normal left inverted right x axis y axis) 1440x900 59.90 + 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.00
[Touch-packages] [Bug 1809552] [NEW] Ubuntu sees duplicate display for each graphics card on Macbook Pro
Public bug reported: After booting Ubuntu in BIOS mode on my machine for years, I just switched over to EFI boot. The reason for which I switched is that, on this machine, Ubuntu cannot detect the integrated GPU under BIOS boot. Ubuntu now recognizes both integrated and discrete GPU on my machine, but it also seems to think I have two monitors. Expected Behavior: Ubuntu properly recognizes that both graphics cards are in fact controlling the same display Actual Behavior: Ubuntu thinks I have two displays (each being controlled by a separate card?). If I navigate to the "Devices > Displays" section of the settings app, then Ubuntu lists two "Built in Displays," and offers options to "Join Displays," mirror them, etc. I have created a question on AskUbuntu (https://askubuntu.com/questions/1103696/ubuntu-duplicates-display-for- each-graphics-card-fresh-install) detailing this issue; it presents much of the same information in this bug report, along with several images. I have also discovered a similar thread from three years ago (https://askubuntu.com/questions/582574/my-macbook-has-two-built-in- displays) suggesting that I am not the only Macbook user to suffer from this issue. The user in said thread worked around this issue by powering off his iGPU. I would like to set up graphics switching in the future, so this is not an option for me. In any case, I have tested his "solution" and it DOES NOT work on my machine (I also don't have a /sys/kernel/debug/vgaswitcheroo folder like he apparently does) SYSTEM INFORMATION OS Version: Ubuntu (64-bit) 18.04.1 Kernel: 4.15.0-43-generic GRAPHICS CARD INFORMATION == $ lshw -c video *-display description: VGA compatible controller product: GK107M [GeForce GT 650M Mac Edition] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:45 memory:c000-c0ff memory:9000-9fff memory:a000-a1ff ioport:2000(size=128) memory:c100-c107 *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:47 memory:c140-c17f memory:b000-bfff ioport:3000(size=64) MORE GRAPHICS CARD INFORMATION == $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] (rev a1) DISPLAY CONFIGURATION INFO (1) == NOTE: In this diagnostic, I have chosen the "Single Display" option via the System Settings app. Only one of the two "built-in displays" is actually usable, selecting the other just gives me a black screen until my changes are auto-reverted $ xrandr - q Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384 LVDS-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1440x900 59.90*+ 1152x864 59.97 1024x768 59.95 800x600 59.96 640x480 59.94 720x400 59.97 640x400 59.96 640x350 59.84 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) LVDS-1-2 connected (normal left inverted right x axis y axis) 1440x900 59.90 + 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.
[Touch-packages] [Bug 1808075] Re: Backport Unicode/Emoji 11 updates
I installed pango1.0 1.42.4-3ubuntu1 on Ubuntu 18.10 and verified that the red-haired man now displays correctly in gedit. I also opened the GNOME Characters app (.deb and snap versions) and verified that emoji there still displayed ok. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808075 Title: Backport Unicode/Emoji 11 updates Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Cosmic: Fix Committed Bug description: Impact == Once a year, there is a new Unicode and Emoji release. 2018's release is Unicode 11. Ubuntu 18.04 LTS and 18.10 already include Google's color emoji font for Unicode 11 (LP: #1788256) but neither Ubuntu 18.10 nor 18.04 LTS are able to display the new combinations introduced in Unicode 11 such as red-haired people. Test Case = Copy and paste the red-hair man 👨🦰 into gedit. It should show as a single character. Regression Potential Although the code was written several weeks ago, it was only released in pango 1.43 (a development release) today so it's not seen many users yet. On the other hand, pango does have a test suite run during the build and as autopkgtest and those tests still pass. I haven't seen any issues yet and we'll work to fix any issues that do develop. A significant portion of the change set comes from the Unicode data sets and from the Chromium Unicode/Emoji parser. Both of those parts have received wider testing and use over several months. Other Info == This issue is easy to fix with Ubuntu 18.10 but it may not be practical to try to update Ubuntu 18.04 LTS for this feature. GTK's "Insert Emoji" feature will need to be updated to offer these new emoji. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1808075/+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]
Still present in 6.2.0 RC 1 -- 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 1458204] Re: removing kernels should not require a restart afterward
I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were installed and a reboot performed. Today old kernel was removed and no reboot performed. This test also used the new update-notifier-common version 3.168.10. Yesterday I received an email telling me that new kernels had been installed and a reboot was performed, as it should, but today I received no email stating the old kernel had been removed. I expected one. Is this a new bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://laun
[Touch-packages] [Bug 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5
This forgotten issue still exists, also in Disco. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1789022 Title: libcaca0 still depends on old libncursesw5 and libtinfo5 Status in libcaca package in Ubuntu: New Bug description: Ubuntu Cosmic switched some time ago from ncurses5 to ncurses6. However, the package libcaca0 still depends on old libncursesw5 and libtinfo5 instead of libncursesw6 and libtinfo6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcaca/+bug/1789022/+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
