[Touch-packages] [Bug 1850015] Re: Rasbpery Pi upgrade from 18.04 to 19.10 - package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-too
** 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/1850015 Title: Rasbpery Pi upgrade from 18.04 to 19.10 - package linux- image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run- parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Encountered when updating my Raspberry PI 3B from 18.04 to 19.10. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34 ProcVersionSignature: Ubuntu 4.15.0-1048.52-raspi2 4.15.18 Uname: Linux 4.15.0-1048-raspi2 aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-1048-raspi2. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Oct 27 03:17:39 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Lsusb: Bus 001 Device 004: ID 045e:0810 Microsoft Corp. Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to disco on 2019-10-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1850015/+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 1850015] [NEW] Rasbpery Pi upgrade from 18.04 to 19.10 - package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-t
Public bug reported: Encountered when updating my Raspberry PI 3B from 18.04 to 19.10. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34 ProcVersionSignature: Ubuntu 4.15.0-1048.52-raspi2 4.15.18 Uname: Linux 4.15.0-1048-raspi2 aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-1048-raspi2. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Oct 27 03:17:39 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Lsusb: Bus 001 Device 004: ID 045e:0810 Microsoft Corp. Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to disco on 2019-10-27 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 disco uec-images -- 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/1850015 Title: Rasbpery Pi upgrade from 18.04 to 19.10 - package linux- image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run- parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Encountered when updating my Raspberry PI 3B from 18.04 to 19.10. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34 ProcVersionSignature: Ubuntu 4.15.0-1048.52-raspi2 4.15.18 Uname: Linux 4.15.0-1048-raspi2 aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-1048-raspi2. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Oct 27 03:17:39 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Lsusb: Bus 001 Device 004: ID 045e:0810 Microsoft Corp. Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to disco on 2019-10-27 (0 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1850012] [NEW] After log in, sound out/inputs resort to wrong devices
Public bug reported: I really hope I am submitting this bug to the right place, but every time I log in (whether after logout, reboot, etc.) the sound output and input devices resort to my HDMI cable (monitor) and the mic on my webcam instead of the devices I last selected. In previous versions of Ubuntu, if I were to select my speakers as the output device, they would remain the default until I changed it again, even after logout/log in. Now, whenever I log in, the sound still comes out of my speakers, but adjusting the volume does not work properly until I go into settings > sound > and then reselect my speakers as the output device. The volume indicator pops up on screen and it shows the sound going up or down, but it says it is adjusting the sound to my HDMI cable instead and it has no effect on my desktop speakers. I really hope that makes sense. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 21:20:59 2019 InstallationDate: Installed on 2018-12-22 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-14 (12 days ago) dmi.bios.date: 09/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0410 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS 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.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1850012 Title: After log in, sound out/inputs resort to wrong devices Status in alsa-driver package in Ubuntu: New Bug description: I really hope I am submitting this bug to the right place, but every time I log in (whether after logout, reboot, etc.) the sound output and input devices resort to my HDMI cable (monitor) and the mic on my webcam instead of the devices I last selected. In previous versions of Ubuntu, if I were to select my speakers as the output device, they would remain the default until I changed it again, even after logout/log in. Now, whenever I log in, the sound still comes out of my speakers, but adjusting the volume does not work properly until I go into settings > sound > and then reselect my speakers as the output device. The volume indicator pops up on screen and it shows the sound going up or down, but it says it is adjusting the sound to my HDMI cable instead and it has no effect on my desktop speakers. I really hope that makes sense. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 21:20:59 2019 InstallationDate: Installed on 2018-12-22 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-14 (12 days ago) dmi.bios.date: 09/06/2015 dmi.bios.vendor: American Megatrends Inc.
[Touch-packages] [Bug 1850009] [NEW] Issue with detecting new state in dhclient-enter-hooks.d/resolved
Public bug reported: After upgrading to 19.10 I noticed that resolving hostnames stopped working. Quick release, which package and version info: root@caret:~# lsb_release -r Release:19.10 root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved root@caret:~# apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status The file /etc/resolv.conf was pointing to the local instance of systemd-resolved however there was no search line, indicating something wasn't quite right. Restarting the systemd-resolved service did recreate /etc/resolv.conf with expected search line. After much debugging, I've worked out what was going wrong. The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug in the resolver state change logic. This may also impact on tickets 1805183, 1832050, 1832053 and maybe others. When doing the md5sum of the old and new state, the command is wrong. It isn't sending STDOUT (and optionally STDERR) to the temp file but rather putting the md5sum command into the background and then creating an empty file for both states. Which obviously isn't different, so systemd- resolved doesn't restart. Quick diff of a working version (I'm not capturing STDERR but one can with "2>&1") === BEGIN PATCH === *** .brk-resolved-20191027 2019-10-27 11:19:56.210069032 +1030 --- resolved2019-10-27 11:30:17.156381734 +1030 *** *** 30,36 mkdir -p $statedir oldstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $oldstate if [ -n "$new_domain_name_servers" ] ; then cat <$statedir/isc-dhcp-v4-$interface.conf [Resolve] --- 30,36 mkdir -p $statedir oldstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf > $oldstate if [ -n "$new_domain_name_servers" ] ; then cat <$statedir/isc-dhcp-v4-$interface.conf [Resolve] *** *** 55,61 fi newstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf &> $newstate if ! cmp $oldstate $newstate; then systemctl try-reload-or-restart systemd-resolved.service fi --- 55,61 fi newstate="$(mktemp)" ! md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc-dhcp-v6-$interface.conf > $newstate if ! cmp $oldstate $newstate; then systemctl try-reload-or-restart systemd-resolved.service fi === END PATCH === Also, the script removes the script removes the $oldstate file but doesn't remove the $newstate file. Not sure how this made it through QA testing... But breaking DHCP client shouldn't happen like this. ivan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sun Oct 27 11:48:33 2019 InstallationDate: Installed on 2017-04-21 (918 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 172.16.1.14 dev enp0s5 150.101.89.32/28 dev enp0s5 scope link 169.254.0.0/16 dev enp0s5 scope link metric 1000 172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120 IwConfig: lono wireless extensions. enp0s5no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en TERM=vt100 PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) nmcli-con: nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s5 ethernet unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started unknown disabledenabled enabled enabled enabled ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Package changed:
[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
As I feared from trying with Ubuntu 19.10, using ppa:ubuntu-x-swat/updates on 18.04 did not fix the flickering-shadows problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Incomplete Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video
[Touch-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
I'll try that and report, thanks. Meanwhile I have tried with Ubuntu ( default ) 19.10 and same problem… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Incomplete Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video acceleration drivers ii
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
The netplan.io (arm64) autopkgtest failure (due to timeout) has been retried today, it passed: http://autopkgtest.ubuntu.com/packages/n/netplan.io/bionic/arm64 No more failure reported in pending sru page. - Eric -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
Unfortunately, I had to leave the Linux community because if this bug...regretful. On Sat, Oct 26, 2019, 12:34 IkhwanArif <972...@bugs.launchpad.net> wrote: > How is this 7 year old bug still not resolve? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/972077 > > Title: > apt repository disk format has race conditions > > To manage notifications about this bug go to: > https://bugs.launchpad.net/apt/+bug/972077/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 972077] Re: apt repository disk format has race conditions
How is this 7 year old bug still not resolve? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 1849907] Re: Add Online Account Nextcloud no Connect button on Unity
** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-online-accounts (Ubuntu) Status: Incomplete => Confirmed ** Tags added: running-unity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Connect button on Unity Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1813090] Re: bash completions in /usr/share/bash-completion generate unbound variable errors
The attachment "add -g to declare of _xspecs to ensure it stays in the global scope" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1813090 Title: bash completions in /usr/share/bash-completion generate unbound variable errors Status in bash package in Ubuntu: New Status in bash-completion package in Ubuntu: New Bug description: After upgrading from Ubuntu 18.04 LTS to 18.04.1 LTS, I get errors whenever I attempt to tab-complete anything from an interactive bash prompt. Tab-completing nothing gives me: -bash: _xspecs[$cmd]: unbound variable Tab-completing an existing filename gives me: -bash: !ref: unbound variable I've partially narrowed down the cause to me putting `set -o nounset` in my `.bashrc` file, and something in `/usr/share/bash-completion` is triggering these unbound variable errors. (That is, the errors go away if I remove `set -o nounset` or if I make `/usr/share/bash- completion/bash_completion` exit immediately.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1813090/+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 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
im having the exact same problem on fresh install of 19.04 solution is to run this command (in terminal) after the machine boots: xrandr --output eDP-1 --rotate normal -- 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/1821641 Title: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sharper1380 F pulseaudio /dev/snd/controlC1: sharper1380 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330) MachineType: Hewlett-Packard HP EliteBook 840 G1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.44 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG4430MGN dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: D1F44AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
try newer mesa on ppa:ubuntu-x-swat/updates ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** No longer affects: xserver-xorg-video-intel ** No longer affects: mesa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Incomplete Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1
[Touch-packages] [Bug 1813090] Re: bash completions in /usr/share/bash-completion generate unbound variable errors
re-adding attachment due to copy error ** Attachment added: "add -g to declare of _xspecs to ensure it stays in the global scope" https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1813090/+attachment/5300381/+files/bash_completion.p -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1813090 Title: bash completions in /usr/share/bash-completion generate unbound variable errors Status in bash package in Ubuntu: New Status in bash-completion package in Ubuntu: New Bug description: After upgrading from Ubuntu 18.04 LTS to 18.04.1 LTS, I get errors whenever I attempt to tab-complete anything from an interactive bash prompt. Tab-completing nothing gives me: -bash: _xspecs[$cmd]: unbound variable Tab-completing an existing filename gives me: -bash: !ref: unbound variable I've partially narrowed down the cause to me putting `set -o nounset` in my `.bashrc` file, and something in `/usr/share/bash-completion` is triggering these unbound variable errors. (That is, the errors go away if I remove `set -o nounset` or if I make `/usr/share/bash- completion/bash_completion` exit immediately.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1813090/+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 1849907] Re: Add Online Account Nextcloud no Apply button
I have tried every setting I can find. The buttons remain invisible. I run Ubuntu 19.10 with default unity desktop. However.. when I changed to "Ubuntu on Wayland" in the login screen.. the buttons appeared. So, my problem with the "Online Accounts" is solved with a work-around, but the problem in Unity remains. ** Summary changed: - Add Online Account Nextcloud no Apply button + Add Online Account Nextcloud no Connect button on Unity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Connect button on Unity Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1813090] Re: bash completions in /usr/share/bash-completion generate unbound variable errors
I've been dealing with this issue for years and finally tracked it down a few minutes ago. This is caused by the line: declare -A _xspecs around line 1909 of /usr/share/bash-completion/bash_completion this line *should* read: declare -Ag _xspecs to ensure the _xspecs variable remains in the global scope, regardless of where bash_completion is sourced from. This has been fixed in the upstream repository for over a year: https://github.com/wpalmer/bash- completion/commit/a47bd375bb0f95dc6d388d4097c420bddb72ae33 This also causes errors in which _xspecs, having not been seen to be previously-declared, is treated as a non-associative array, resulting in errors when strings are erroneously treated as arithmetic operations to return an integer (ie: 'invalid arithmetic operator (error token is ".sh")' when trying to complete a command with .sh in the name) This issue has already been fixed, Ubuntu needs to either sync with upstream, or to apply the patch found at the above link. In the meantime, the attached patch can be used as a quick workaround -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1813090 Title: bash completions in /usr/share/bash-completion generate unbound variable errors Status in bash package in Ubuntu: New Status in bash-completion package in Ubuntu: New Bug description: After upgrading from Ubuntu 18.04 LTS to 18.04.1 LTS, I get errors whenever I attempt to tab-complete anything from an interactive bash prompt. Tab-completing nothing gives me: -bash: _xspecs[$cmd]: unbound variable Tab-completing an existing filename gives me: -bash: !ref: unbound variable I've partially narrowed down the cause to me putting `set -o nounset` in my `.bashrc` file, and something in `/usr/share/bash-completion` is triggering these unbound variable errors. (That is, the errors go away if I remove `set -o nounset` or if I make `/usr/share/bash- completion/bash_completion` exit immediately.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1813090/+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 1813090] Re: bash completions in /usr/share/bash-completion generate unbound variable errors
** Also affects: bash-completion (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1813090 Title: bash completions in /usr/share/bash-completion generate unbound variable errors Status in bash package in Ubuntu: New Status in bash-completion package in Ubuntu: New Bug description: After upgrading from Ubuntu 18.04 LTS to 18.04.1 LTS, I get errors whenever I attempt to tab-complete anything from an interactive bash prompt. Tab-completing nothing gives me: -bash: _xspecs[$cmd]: unbound variable Tab-completing an existing filename gives me: -bash: !ref: unbound variable I've partially narrowed down the cause to me putting `set -o nounset` in my `.bashrc` file, and something in `/usr/share/bash-completion` is triggering these unbound variable errors. (That is, the errors go away if I remove `set -o nounset` or if I make `/usr/share/bash- completion/bash_completion` exit immediately.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1813090/+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 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
please test with latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: Incomplete Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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/ubuntu/+source/linux/+bug/1849947/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
Anyway remember I have no flickering shadows problem when booting the same computer on 16.04. So it's a regression but how narrow down any culprit ? ** Also affects: supertuxkart (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in Mesa: New Status in xf86-video-intel: New Status in mesa package in Ubuntu: New Status in supertuxkart package in Ubuntu: New Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra
[Touch-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
could you test with ppa:ubuntu-x-swat/updates which has a newer mesa backported from eoan? ** Changed in: mesa (Ubuntu Bionic) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Bionic: Incomplete Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
thanks for confirming that 19.0.8-0ubuntu0~18.04.2 fixed it, the reason was due to meson not using -DDEBUG before, and it is forced in this version and should avoid known assertions in the drivers since you have some other issue now, you should file a new bug and against the kernel if it's a regression there ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Fix Released Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
I've added this to the 20.04 development blueprint, so let's revisit and discuss. If we can't solve the problem with packaging, let's document the mini.iso installation process so others have an easier time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+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 1849907] Re: Add Online Account Nextcloud no Apply button
On 2019-10-26 11:00, Magnus Pernemark wrote: > I think I have changed how menues and/or title bar of window should > show. I will look into that. Yeah, please do. I keep the "Incomplete" status of this bug until you have provided some details. It would be good if you could figure out exactly which changed setting(s) broke the window. > Regardless, it is not a good implementation if submit buttons > disapear if you change system settings of windows. The function of a > window should remain, even if the theam of the desktop change. Fair point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Apply button Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report
** Tags added: id-5db1d6f13d7e2c1b89dbb9de -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1848064 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@168:collect_info:process_report Status in apport package in Ubuntu: Confirmed Status in apport source package in Eoan: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+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 1849416] Re: Xubuntu ping command leading to all of sessions closed
** Package changed: ubuntu => iputils (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1849416 Title: Xubuntu ping command leading to all of sessions closed Status in iputils package in Ubuntu: New Bug description: Hi,my server version is Ubuntu 18.04.3 LTS. When I use ping command, all the sessions will be closed and returned socket error 10053. However,it is normal when I ping the valid address likes: ping -c 4 bugs.launchpad.net. But when I ping other address which would return "Destination Host Unreachable", all the distal session in putty or another shell would be colsed with "Connection closed by foreign host". Other commands like netcat have the same error. I checked the syslog without no returned error after using ping for this strange phenomenon, through syslog included some related information: syslog.1:Oct 22 21:15:16 dell systemd-timesyncd[1298]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). syslog.1:Oct 22 21:17:35 dell systemd-timesyncd[1298]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). or messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) I guess some daemon programs may peform their function via ping or other ways. User sessions always be closed immediately and connection refusion time usually takes no more than 1 min, and it won't kill running jobs in closed session. Especially, this phenomenon never happens in apt-get and conda or wget command. I have no idea what lead to this strange phenomenon. Please give me advice. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1849416/+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 1849947] [NEW] Dell XPS 13 (7390) Display Flickering - 19.10
Public bug reported: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in xorg package in Ubuntu: New Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 1849416] [NEW] Xubuntu ping command leading to all of sessions closed
You have been subscribed to a public bug: Hi,my server version is Ubuntu 18.04.3 LTS. When I use ping command, all the sessions will be closed and returned socket error 10053. However,it is normal when I ping the valid address likes: ping -c 4 bugs.launchpad.net. But when I ping other address which would return "Destination Host Unreachable", all the distal session in putty or another shell would be colsed with "Connection closed by foreign host". Other commands like netcat have the same error. I checked the syslog without no returned error after using ping for this strange phenomenon, through syslog included some related information: syslog.1:Oct 22 21:15:16 dell systemd-timesyncd[1298]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com). syslog.1:Oct 22 21:17:35 dell systemd-timesyncd[1298]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). or messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) messages:Oct 22 23:14:53 dell blueman.desktop[3974]: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) I guess some daemon programs may peform their function via ping or other ways. User sessions always be closed immediately and connection refusion time usually takes no more than 1 min, and it won't kill running jobs in closed session. Especially, this phenomenon never happens in apt-get and conda or wget command. I have no idea what lead to this strange phenomenon. Please give me advice. Thanks! ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- Xubuntu ping command leading to all of sessions closed https://bugs.launchpad.net/bugs/1849416 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. -- 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 1849907] Re: Add Online Account Nextcloud no Apply button
Thanks for moving the bug to the correct section. When creating it I hade to choices "Ubunto-docs" or "I don't know". I selected the latter. Looking at the reviews of "Online account" it looks that I am not alone. Someone else reported the problem. But I think I have an idea. The Ubuntu installation is a stock installation, but I think I have changed how menues and/or title bar of window should show. I will look into that. Regardless, it is not a good implementation if submit buttons disapear if you change system settings of windows. The function of a window should remain, even if the theam of the desktop change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1849907 Title: Add Online Account Nextcloud no Apply button Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: I am trying to add an online account, nextcloud three fields show, server, username and password. There is no Apply or OK button. I cannot add the account. Resizing the window does not help. Fields just get longer, still no buttons. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1849907/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I have a completely encrypted home (auto configured) in bionic and have the same error messages in dmesg. Moreover, since a few weeks ago, the home directory sometimes gets broken in a way that all list requests (ls, browse in nautilus) hang just on the home directory (process in S state) and only a reboot solves this. I found the dmesg messages only because of these hangs which might be unrelated. -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1790098] Re: vlan created on bond fails auto activation on updating parent network bond
** Changed in: network-manager (Ubuntu) Status: Won't Fix => Fix Released -- 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/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it
