[Touch-packages] [Bug 1895424] [NEW] duplicate rc local service
Public bug reported: Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d" Creates two systemd services: rc.local and rc-local This has the unfortunate event of running /etc/rc.local multiple times during bootup ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2 (Ubuntu) => systemd (Ubuntu) -- 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/1895424 Title: duplicate rc local service Status in systemd package in Ubuntu: New Bug description: Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d" Creates two systemd services: rc.local and rc-local This has the unfortunate event of running /etc/rc.local multiple times during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+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 1895424] [NEW] duplicate rc local service
You have been subscribed to a public bug: Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d" Creates two systemd services: rc.local and rc-local This has the unfortunate event of running /etc/rc.local multiple times during bootup ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- duplicate rc local service https://bugs.launchpad.net/bugs/1895424 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1594695] Re: apparmor service not started on fresh install
[Expired for apparmor (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apparmor (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1594695 Title: apparmor service not started on fresh install Status in apparmor package in Ubuntu: Expired Bug description: On fresh install of LXC, apparmor service (a dependency) is not started. In that case, it causes LXC guest startup to fail. apparmor postinstall seems only to configure the service but does not start it: if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ]; then if [ -x "/etc/init.d/apparmor" ]; then update-rc.d apparmor start 37 S . >/dev/null || true fi fi To me it is not clear, if this is just an apparmor/lxc combination issue or may affect apparmor installs in general: in later case, machines might be unprotected till the first reboot (which might be quite some time on servers when there are no upstream security fixes requiring reboot). # lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 # apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594695/+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 1885127] Re: ethernet interfaces explicity excluded from management in globally-managed-devices.conf
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1885127 Title: ethernet interfaces explicity excluded from management in globally- managed-devices.conf Status in network-manager package in Ubuntu: Expired Bug description: The file `/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` included with this package (installed via apt in 19.10 environment) contains the line: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma ``` In my system (laptop with no native ethernet), this results in the inability to easily use USB/ethernet adapters. After manually modifying: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma,except:type:ethernet ``` the USB/ethernet adapter is detected and configured automatically by NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885127/+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 1887016] Re: Openssh default config has two PasswordAuthentication params
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1887016 Title: Openssh default config has two PasswordAuthentication params Status in openssh package in Ubuntu: Expired Bug description: In Ubuntu server 20.04 the /etc/ssh/sshd_config file has an additional `PasswordAuthentication yes` string in the end. It can lead to security problems, because there's already one string `# PasswordAuthentication yes` in the beginning of the file. It is supposed to be uncommented if it's needed to change the default value. But if the user uncomments this string and set in to "no", it will be overriden by the last line of config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1887016/+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 1895422] Re: Sound card not detected on Dell Latitude 9510
** Attachment added: "pactl_list.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+attachment/5410263/+files/pactl_list.txt -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 Status in alsa-driver package in Ubuntu: New Bug description: I am running Ubuntu 20.04.01 LTS, kernel (linux-image-generic) version 5.4.0.47.50. I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics- cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en- us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1895422] Re: Sound card not detected on Dell Latitude 9510
** Attachment added: "demsg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+attachment/5410262/+files/demsg.txt -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 Status in alsa-driver package in Ubuntu: New Bug description: I am running Ubuntu 20.04.01 LTS, kernel (linux-image-generic) version 5.4.0.47.50. I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics- cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en- us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1895422] [NEW] Sound card not detected on Dell Latitude 9510
Public bug reported: I am running Ubuntu 20.04.01 LTS, kernel (linux-image-generic) version 5.4.0.47.50. I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics- cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en- us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1895422/+attachment/5410261/+files/lspci.txt -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 Status in alsa-driver package in Ubuntu: New Bug description: I am running Ubuntu 20.04.01 LTS, kernel (linux-image-generic) version 5.4.0.47.50. I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics- cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en- us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1895382] Re: Ability to install 2 or more versions at once
For reference: Ubuntu degraded to the state where they aren't able to ship fucking wallpapers (yes, not joke) https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1894347 -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
Why apt, dpkg, flatpack, snapd are invalid here? -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895418] [NEW] systemd-resolved default config for Caching is still "yes"
Public bug reported: Back in December, the default for systemd-resolved caching in Ubuntu systemd was changed to "no-negative" from the upstream default "yes" [0] In this change, the default value in the resolved.conf file was missed. As the defaults in this file are commented, the effective default is still "no-negative", however when viewing the config file, the commented default "yes" is at odds with the man page resolved.conf(5), which correctly states the default as "no-negative". This was an issue for me as I set DNSSEC to "yes", and expected Caching to also be "yes". Running DNSSEC with the default "no-negative" Caching is detrimental to performance resolving unsigned zones, as the non- existence of DNSSEC RRs must be looked up every time. The issue with the intersection of DNSSEC and Caching is for upstream, but the least that needs to be done here is updating the resolved.conf template with "Caching=no-negative" to match the man page and behaviour, and perhaps even adding a note to the "DNSSEC=" section of resolved.conf(5) that Caching should be enabled. Now that I'm looking at that man page, the default for DNSSEC is also listed as "allow- downgrade", whereas the default for Ubuntu is "no". [0] https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db =ubuntu-focal ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1895418 Title: systemd-resolved default config for Caching is still "yes" Status in systemd package in Ubuntu: New Bug description: Back in December, the default for systemd-resolved caching in Ubuntu systemd was changed to "no-negative" from the upstream default "yes" [0] In this change, the default value in the resolved.conf file was missed. As the defaults in this file are commented, the effective default is still "no-negative", however when viewing the config file, the commented default "yes" is at odds with the man page resolved.conf(5), which correctly states the default as "no-negative". This was an issue for me as I set DNSSEC to "yes", and expected Caching to also be "yes". Running DNSSEC with the default "no- negative" Caching is detrimental to performance resolving unsigned zones, as the non-existence of DNSSEC RRs must be looked up every time. The issue with the intersection of DNSSEC and Caching is for upstream, but the least that needs to be done here is updating the resolved.conf template with "Caching=no-negative" to match the man page and behaviour, and perhaps even adding a note to the "DNSSEC=" section of resolved.conf(5) that Caching should be enabled. Now that I'm looking at that man page, the default for DNSSEC is also listed as "allow- downgrade", whereas the default for Ubuntu is "no". [0] https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db =ubuntu-focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895418/+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 1815318] Re: mate 18.04.1 xserver won't open caja on local machine
** Changed in: mate-desktop Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1815318 Title: mate 18.04.1 xserver won't open caja on local machine Status in MATE Desktop: New Status in Ubuntu MATE: Invalid Status in caja package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 192.168.1.162) 2. Install SSH server on Ubuntu MATE 18.04 LTS 3. Open terminal on other remote system (client) and execute command to run Caja over X forwarding: ssh -X user@192.168.1.162 caja Expected results: * Caja is shown on remote (client) screen with window title *folder (on hostname)* Actual results: * Caja is not shown on remote (client) screen, but launches on server locally. Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but fails with 18.04 LTS. --- Original description below: I can open a remote terminal using ssh -X 192.168.1.162. All other gui's that I've tested opened locally except the file manager Caja. When issuing caja in the remote terminal, I get nothing locally. Caja does open on the remote machine however, just not locally. The ssh -X 18.04.1 client still works connecting to a mate 16.04 server. I've tested this on numerous mate 18.04 clients, two 16.04 servers and two 18.04 servers, all mate. Something is wonky with caja on an 18.04.1 server. Please let me know if I can provide any more information. The only file manager I've tested that works is an X file manager, xfimage. X2go works and connects to servers, SSH Connect to Server works, why isn't the remote X terminal working using caja? To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1815318/+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 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
This is still an issue in Ubuntu 20.20 VMWare vmnet1 and vmnet2 are displayed in NetworkManager applet in Gnome -- 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/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+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 1895416] [NEW] package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: This occurred doing a cli apt upgrade. May be due to /boot being too full, may not. Saw write permission problems on the screen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chuck 3514 F pulseaudio CasperMD5CheckResult: skip Date: Sat Sep 12 17:46:20 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=53b045cd-14a6-40e2-bda3-8b25923c8c21 InstallationDate: Installed on 2013-10-19 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2020-07-24 (50 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1895416 Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 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: This occurred doing a cli apt upgrade. May be due to /boot being too full, may not. Saw write permission problems on the screen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chuck 3514 F pulseaudio CasperMD5CheckResult: skip Date: Sat Sep 12 17:46:20 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=53b045cd-14a6-40e2-bda3-8b25923c8c21 InstallationDate: Installed on 2013-10-19 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
[Touch-packages] [Bug 1895405] [NEW] Wireless Mouse Wont WOrk
Public bug reported: 1. Submitted bug report 2. Manufactuere of mous is Windows surface mouse pink 3. Mouse is connected via bluetooth 4. Mouse uses trackpad 5. Mouse has 1 physical button, can press on left side or right side of button for different functions 6. Using Ubuntu 16.04 Wireless bluetooth mouse does not work in Ubuntu 16.04 but works in my standard Windows 10 OS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-117.118~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 12 13:21:38 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:82c1] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:82c1] InstallationDate: Installed on 2020-09-12 (0 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) Lsusb: Bus 002 Device 002: ID 125f:0001 A-DATA Technology Co., Ltd. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 064e:3401 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=94a7e873-47e3-4c72-af71-ef0c3fb72af1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.39 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 82C1 dmi.board.vendor: HP dmi.board.version: 09.42 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.39:bd11/12/2018:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn82C1:rvr09.42:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Sep 12 13:15:30 2020 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1895405 Title: Wireless Mouse Wont WOrk Status in xorg package in Ubuntu: New Bug description: 1. Submitted bug report 2. Manufactuere of mous is Windows surface mouse pink 3. Mouse is connected via bluetooth 4. Mouse uses trackpad 5. Mouse has 1 physical button, can press on left side or right side of button for different functions 6. Using Ubuntu 16.04 Wireless bluetooth mouse does not work in Ubuntu 16.04 but works in my standard Windows 10 OS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-117.118~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 12 13:21:38 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation
[Touch-packages] [Bug 1895382] Re: Ability to install 2 or more versions at once
"Ability to install 2 or more versions at once" - this means: Ability to install 2 or more versions of programm at once Ability to install 2 or more versions of .so at once Ability to install 2 or more versions of kernel at once It should be evident why title was exactly this and nothing else. This was done for Kernels (long time ago) but not for everything else... Pretty odd decision to do just 20%. This should have system-wide support, not just GRUB and not just Kernels. -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
The bug description states: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice I have no idea what that means, it also has no relation to the bug title. Flatpak and snap don't ask questions, and debconf stores the answer and does not ask questions it already did. -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
Also, the language you have chosen for that comment is inappropriate. -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
The bug is about "Ability to install 2 or more versions at once", the rest was incomprehensible -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879615 This one is related ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1879615] Re: headset microphone not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1879615 Title: headset microphone not working Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I can here sound in my bluetooth headsets (I tried several) but I cannot make the microphone work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 07:29:30 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-13 (188 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 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.5.1:bd03/26/2020: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. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:1D:96:DA:9E:12 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:130281 acl:173 sco:0 events:15048 errors:0 TX bytes:4105451 acl:5549 sco:12 commands:8979 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879615/+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 1881612] Re: Intel AX1650i Bluetooth will not work in HSP/HFP (Headset/Hands-free)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1881612 Title: Intel AX1650i Bluetooth will not work in HSP/HFP (Headset/Hands-free) Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On Dell Inspiron 3593 running Ubuntu 20.04, Bluetooth Headset Vipex VX-BH001 works in A2DP, but not in HSP/HFP. (So it cannot be used as a microphone.) Same headset works correctly on an older Dell Latitude under both 20.04 and 18.04, and works on the same laptop when using an external USB bluetooth adapter, so I conclude the issue is probably with the iwlwifi driver or firmware. The bluetooth headset pairs okay, but in sound settings if I switch configuration to "Headset Head Unit (HSP/HFP)", then the "test" dialog under "output" will not play sound, and the "input" panel does not show any incoming audio. I tried upgrading to -proposed kernel and installing updated firmware in /lib/firmware, but without improvement. I also note that 'modinfo iwlwifi' on my laptop lists support for firmware up to iwlwifi-Qu-c0-hr-b0-52.ucode, but linux-firmware.git has newer firmware published: iwlwifi-Qu-c0-jf-b0-55.ucode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.6.0-1011.11-oem 5.6.14 Uname: Linux 5.6.0-1011-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magnus207273 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 10:58:12 2020 InstallationDate: Installed on 2020-05-24 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Vipex VX-BH001 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magnus207273 F pulseaudio Symptom_Type: No sound at all Title: [Vipex VX-BH001, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0TGVJN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd03/24/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn0TGVJN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-24 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3593 Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1011-oem root=UUID=e02d97a7-7307-4838-8fdc-65824f3ea646 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1011.11-oem 5.6.14 Tags: focal Uname: Linux 5.6.0-1011-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0TGVJN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd03/24/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn0TGVJN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: AC:67:5D:DF:7C:A2 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21346 acl:112 sco:0 events:1029 errors:0 TX bytes:225218 acl:347 sco:1 commands:348 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe
[Touch-packages] [Bug 1879615] Re: headset microphone not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1879615 Title: headset microphone not working Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I can here sound in my bluetooth headsets (I tried several) but I cannot make the microphone work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 07:29:30 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-11-13 (188 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.11-050611-generic root=UUID=a07ae209-275c-4c8b-985d-ba52e5f7f214 ro quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-13 (6 days ago) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 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.5.1:bd03/26/2020: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. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:1D:96:DA:9E:12 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:130281 acl:173 sco:0 events:15048 errors:0 TX bytes:4105451 acl:5549 sco:12 commands:8979 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879615/+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 1881612] Re: Intel AX1650i Bluetooth will not work in HSP/HFP (Headset/Hands-free)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1881612 Title: Intel AX1650i Bluetooth will not work in HSP/HFP (Headset/Hands-free) Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On Dell Inspiron 3593 running Ubuntu 20.04, Bluetooth Headset Vipex VX-BH001 works in A2DP, but not in HSP/HFP. (So it cannot be used as a microphone.) Same headset works correctly on an older Dell Latitude under both 20.04 and 18.04, and works on the same laptop when using an external USB bluetooth adapter, so I conclude the issue is probably with the iwlwifi driver or firmware. The bluetooth headset pairs okay, but in sound settings if I switch configuration to "Headset Head Unit (HSP/HFP)", then the "test" dialog under "output" will not play sound, and the "input" panel does not show any incoming audio. I tried upgrading to -proposed kernel and installing updated firmware in /lib/firmware, but without improvement. I also note that 'modinfo iwlwifi' on my laptop lists support for firmware up to iwlwifi-Qu-c0-hr-b0-52.ucode, but linux-firmware.git has newer firmware published: iwlwifi-Qu-c0-jf-b0-55.ucode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.6.0-1011.11-oem 5.6.14 Uname: Linux 5.6.0-1011-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magnus207273 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 10:58:12 2020 InstallationDate: Installed on 2020-05-24 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Vipex VX-BH001 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: magnus207273 F pulseaudio Symptom_Type: No sound at all Title: [Vipex VX-BH001, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0TGVJN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd03/24/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn0TGVJN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-24 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3593 Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1011-oem root=UUID=e02d97a7-7307-4838-8fdc-65824f3ea646 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1011.11-oem 5.6.14 Tags: focal Uname: Linux 5.6.0-1011-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0TGVJN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd03/24/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn0TGVJN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: AC:67:5D:DF:7C:A2 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21346 acl:112 sco:0 events:1029 errors:0 TX bytes:225218 acl:347 sco:1 commands:348 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1881612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
** Tags removed: disco eoan ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+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 1815318] Re: mate 18.04.1 xserver won't open caja on local machine
Still happens on 20.10. ** Tags removed: eoan ** Tags added: groovy ** Changed in: caja (Ubuntu) Status: Expired => Confirmed ** Bug watch added: github.com/mate-desktop/caja/issues #1450 https://github.com/mate-desktop/caja/issues/1450 ** Also affects: mate-desktop via https://github.com/mate-desktop/caja/issues/1450 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1815318 Title: mate 18.04.1 xserver won't open caja on local machine Status in MATE Desktop: Unknown Status in Ubuntu MATE: Invalid Status in caja package in Ubuntu: Confirmed Status in openssh package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have installed Ubuntu MATE 18.04 LTS (you know its hostname and IP - i.e. 192.168.1.162) 2. Install SSH server on Ubuntu MATE 18.04 LTS 3. Open terminal on other remote system (client) and execute command to run Caja over X forwarding: ssh -X user@192.168.1.162 caja Expected results: * Caja is shown on remote (client) screen with window title *folder (on hostname)* Actual results: * Caja is not shown on remote (client) screen, but launches on server locally. Note: this works normally if server runs Ubuntu MATE 16.04 LTS, but fails with 18.04 LTS. --- Original description below: I can open a remote terminal using ssh -X 192.168.1.162. All other gui's that I've tested opened locally except the file manager Caja. When issuing caja in the remote terminal, I get nothing locally. Caja does open on the remote machine however, just not locally. The ssh -X 18.04.1 client still works connecting to a mate 16.04 server. I've tested this on numerous mate 18.04 clients, two 16.04 servers and two 18.04 servers, all mate. Something is wonky with caja on an 18.04.1 server. Please let me know if I can provide any more information. The only file manager I've tested that works is an X file manager, xfimage. X2go works and connects to servers, SSH Connect to Server works, why isn't the remote X terminal working using caja? To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1815318/+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 1895299] Re: Wrong scaling factor after reboot
** Attachment added: "Screenshot after rescalling from 1.00 to 0.99 back to 1.00" https://bugs.launchpad.net/ubuntu/+bug/1895299/+attachment/5410122/+files/Screenshot%20after%20rescalling%201_00-0_99-1_00.png ** Package changed: ubuntu => xorg (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/1895299 Title: Wrong scaling factor after reboot Status in xorg package in Ubuntu: Confirmed Bug description: After reboot I can see wrong scaling factor for icons, etc., although after opening Gnome Tweaks -> Fonts, I can verify that the Scaling Factor is set to 1,00. Changing it (by '+' or '-') to 1,01 or 0,99 and back to 1,00 recovers proper scaling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 15:34:09 2020 DistUpgraded: 2020-05-20 22:32:35,149 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-45-generic, x86_64: installed nvidia, 435.21, 5.4.0-47-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2020-04-02 (162 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QNS17N00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro psmouse.elantech_smbus=0 nouveau.modeset=0 quiet splash max_loop=64 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-20 (113 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNS17N00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:svnLENOVO:pn20QNS17N00:pvrThinkPadP53:rvnLENOVO:rn20QNS17N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNS17N00 dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1895299/+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 1895299] [NEW] Wrong scaling factor after reboot
You have been subscribed to a public bug: After reboot I can see wrong scaling factor for icons, etc., although after opening Gnome Tweaks -> Fonts, I can verify that the Scaling Factor is set to 1,00. Changing it (by '+' or '-') to 1,01 or 0,99 and back to 1,00 recovers proper scaling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 15:34:09 2020 DistUpgraded: 2020-05-20 22:32:35,149 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-45-generic, x86_64: installed nvidia, 435.21, 5.4.0-47-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2020-04-02 (162 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QNS17N00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro psmouse.elantech_smbus=0 nouveau.modeset=0 quiet splash max_loop=64 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-20 (113 days ago) dmi.bios.date: 06/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QNS17N00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:svnLENOVO:pn20QNS17N00:pvrThinkPadP53:rvnLENOVO:rn20QNS17N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QNS17N00 dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bot-comment focal fonts ubuntu -- Wrong scaling factor after reboot https://bugs.launchpad.net/bugs/1895299 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1895387] [NEW] Xorg freeze
Public bug reported: while playing video both online and offline it freezes for 1 sec again and again. i restarted the system many times but it didn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 12 18:01:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:382a] InstallationDate: Installed on 2020-09-11 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80QQ ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=21c6facc-8b10-4e0f-9737-451658d9a525 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E0CN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Nano 5B6 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 100-15IBD dmi.modalias: dmi:bvnLENOVO:bvrE0CN60WW:bd08/16/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD: dmi.product.family: IDEAPAD dmi.product.name: 80QQ dmi.product.sku: LENOVO_MT_80QQ_BU_idea_FM_Lenovo ideapad 100-15IBD dmi.product.version: Lenovo ideapad 100-15IBD dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 false-gpu-hang focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1895387 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: while playing video both online and offline it freezes for 1 sec again and again. i restarted the system many times but it didn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 12 18:01:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:382a] InstallationDate: Installed on 2020-09-11 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80QQ ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=21c6facc-8b10-4e0f-9737-451658d9a525 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E0CN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Nano 5B6 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 100-15IBD dmi.modalias: dmi:bvnLENOVO:bvrE0CN60WW:bd08/16/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD: dmi.product.family: IDEAPAD dmi.product.name: 80QQ dmi.product.sku: LENOVO_MT_80QQ_BU_idea_FM_Lenovo ideapad 100-15IBD dmi.product.version: Lenovo ideapad 100-15IBD dmi.sys.vendor: LENOVO version.compiz: compiz N/A
[Touch-packages] [Bug 1895382] Re: Ability to install 2 or more versions at once
Julian Andres Klode, your comment has nothing to do with what was requested. -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
Julian Andres Klode, you're fucking moron. -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
for reference: https://forum.snapcraft.io/t/parallel-installs/7679 -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] Re: Ability to install 2 or more versions at once
You can't install multiple versions at the same time for dpkg/apt, but you can with snaps, don't know about flatpaks - talk to flatpak people. ** Changed in: apt (Ubuntu) Status: New => Invalid ** Changed in: dpkg (Ubuntu) Status: New => Invalid ** Changed in: flatpak (Ubuntu) Status: New => Invalid ** Changed in: snapd (Ubuntu) Status: New => Invalid -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: Invalid Status in dpkg package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895383] Re: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess 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 shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1895383 Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 Status in shared-mime-info package in Ubuntu: New Bug description: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1895383/+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 1895383] [NEW] package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1
Public bug reported: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1895383 Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 Status in shared-mime-info package in Ubuntu: New Bug description: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1895383/+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 1895382] Re: Ability to install 2 or more versions at once
** Also affects: snap (Ubuntu) Importance: Undecided Status: New ** No longer affects: snap (Ubuntu) ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Description changed: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice + + The ideal solution should serve as an umbrella for all packaging tools. -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in flatpak package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice The ideal solution should serve as an umbrella for all packaging tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1895382] [NEW] Ability to install 2 or more versions at once
Public bug reported: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- 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/1895382 Title: Ability to install 2 or more versions at once Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: 1) do not ask questions with two identical answers in a row 2) ask user every time if multiple versions are present 3) if the same answer was given twice in a row - remember choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1895382/+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 1768203] Re: Connecting to a VPN clears DNS from parent connection
This works without problems, and without using `ipv4.dns-priority`, on Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1768203 Title: Connecting to a VPN clears DNS from parent connection Status in network-manager package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy network-manager network-manager: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status After connecting to a VPN the parent connection's DNS servers are cleared, as seen in the output of `systemd-resolve --status`. Before connection to VPN: (...) Link 3 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 62.179.1.63 62.179.1.62 DNS Domain: chello.pl Link 2 (enp1s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Connected to VPN, notice that only the ppp0 has DNS servers: (...) Link 20 (ppp0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.64.5 192.168.97.10 DNS Domain: ~dcs.pl Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp1s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no I want to use split-horizon DNS resolving, and this behaviour breaks resolving non-VPN names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768203/+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 1787368] Re: Caja does not show previews of text files on Bionic and newer versions
** Tags removed: disco eoan ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787368 Title: Caja does not show previews of text files on Bionic and newer versions Status in MATE Desktop: New Status in caja package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS (or upgrade from 16.04 LTS) 2. Create text file somewhere (in home folder for example) with `echo text > ~/file.txt`. 3. Open Caja in home folder Expected results: * Caja shows preview (the contents) of `file.txt` in Icon view. Actual results: * Caja does not show preview of `file.txt`. Notes: 1. all settings in Preview tab are set to *Local Only* 2. this happens on clean user profile and/or after `dconf reset -f /` and `gsettings reset-recursively org.mate.caja` 3. Problem first seen on AskUbuntu ( https://askubuntu.com/q/1065825/66509 ). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Aug 16 12:36:57 2018 InstallationDate: Installed on 2018-04-26 (111 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1787368/+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 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Status in lightdm package in Debian: Unknown Bug description: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+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 1894014] Re: Funky dual screen support at 20.04.1 live session
** Tags added: focal ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1894014 Title: Funky dual screen support at 20.04.1 live session Status in Ubuntu MATE: New Status in xorg package in Ubuntu: New Bug description: Using 20.04.1 ISO, if one selects live boot session and one has a "unique" screen pattern(See attachments), the "resolution redraw" feels like being high off acid. Reproduction steps are as simple as rotating the monitor and then pressing APPLY from brisk menu's Displays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1894014/+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 1894838] Re: FFe: update to 2.4.53, fixing crash bugs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openldap (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1894838 Title: FFe: update to 2.4.53, fixing crash bugs Status in openldap package in Ubuntu: Confirmed Bug description: Groovy has openldap 2.4.51 Upstream made two quick new releases after that: 2.4.52 and 2.4.53. A crash was reported in the mailing list: https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/NKOM6DI7RQY6FDLRZGSGYJSGONKIRFEP/ """ This segfault is due to a problem with the fix for ITS#9282 that went into the OpenLDAP 2.4.51 and OpenLDAP 2.4.52 releases. This is fixed in the 2.4.53 release (released today). """ Almost all changes in 2.4.52 and 2.4.53 are bug fixes, but a few feathre changes/additions slipped through, hence this FFe: OpenLDAP 2.4.53 (2020/09/07) Added slapd syncrepl additional SYNC logging (ITS#9043) Fixed slapd syncrepl segfault on NULL cookie on REFRESH (ITS#9282) Fixed slapd syncrepl to use fresh connection on REFRESH fallback (ITS#9338) Fixed slapo-ppolicy race condition for pwdFailureTime (ITS#9302,ITS#9334) Build Require OpenSSL 1.0.2 or later (ITS#9323) Fixed libldap compilation issue with broken C compilers (ITS#9332) OpenLDAP 2.4.52 (2020/08/28) Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option (ITS#9318) Added libldap OpenSSL support for multiple EECDH curves (ITS#9054) Added slapd OpenSSL support for multiple EECDH curves (ITS#9054) Fixed librewrite malloc/free corruption (ITS#9249) Fixed libldap hang when using UDP and server down (ITS#9328) Fixed slapd syncrepl rare deadlock due to network issues (ITS#9324) Fixed slapd syncrepl regression that could trigger an assert (ITS#9329) Fixed slapd-mdb index error with collapsed range (ITS#9135) I grouped the changes with links to the bug reports: Replication fixes: Fixed slapd syncrepl segfault on NULL cookie on REFRESH (https://bugs.openldap.org/show_bug.cgi?id=9282) Fixed slapd syncrepl to use fresh connection on REFRESH fallback (https://bugs.openldap.org/show_bug.cgi?id=9338) Fixed slapd syncrepl rare deadlock due to network issues (https://bugs.openldap.org/show_bug.cgi?id=9324) Fixed slapd syncrepl regression that could trigger an assert (https://bugs.openldap.org/show_bug.cgi?id=9329) Features and other non-fixes changes: Added slapd syncrepl additional SYNC logging (https://bugs.openldap.org/show_bug.cgi?id=9043) Require OpenSSL 1.0.2 or later (https://bugs.openldap.org/show_bug.cgi?id=9323) Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option (https://bugs.openldap.org/show_bug.cgi?id=9318) Added libldap OpenSSL support for multiple EECDH curves (https://bugs.openldap.org/show_bug.cgi?id=9054) Added slapd OpenSSL support for multiple EECDH curves (https://bugs.openldap.org/show_bug.cgi?id=9054) Other fixes: Fixed slapo-ppolicy race condition for pwdFailureTime (https://bugs.openldap.org/show_bug.cgi?id=9302,https://bugs.openldap.org/show_bug.cgi?id=9334) Fixed libldap compilation issue with broken C compilers (https://bugs.openldap.org/show_bug.cgi?id=9332) Fixed librewrite malloc/free corruption (https://bugs.openldap.org/show_bug.cgi?id=9249) Fixed libldap hang when using UDP and server down (https://bugs.openldap.org/show_bug.cgi?id=9328) Fixed slapd-mdb index error with collapsed range (https://bugs.openldap.org/show_bug.cgi?id=9135) PPA with a groovy proposed and all arches test build (still ongoing as I write this): https://launchpad.net/~ahasenack/+archive/ubuntu/openldap-2453/+packages I believe a backport of that many fixes is riskier than an update to the new upstream version at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1894838/+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 1895370] Re: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit
After trying and exclude I identify the package causing the issues which is libgnutls30. So I can upgrade all others in the list excluding this. -- 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/1895370 Title: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit Status in systemd package in Ubuntu: New Bug description: Last run apt update and apt upgrade and reboot render my system unbootable because systemd failed with message: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit So I tried to reset to the previous state and re-run the update and after the re-run update I try to run the systemd command and having the same result. root@work ~# apt update; apt upgrade Get:1 http://au.archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://au.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:3 http://au.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:4 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal InRelease [15.9 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:6 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B] Get:7 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages [970 kB] Get:9 http://au.archive.ubuntu.com/ubuntu focal/main i386 Packages [718 kB] Get:10 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en_AU [1,836 B] Get:11 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Get:12 https://packages.microsoft.com/repos/ms-teams stable InRelease [17.5 kB] Get:13 http://au.archive.ubuntu.com/ubuntu focal/main amd64 DEP-11 Metadata [494 kB] Get:14 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 48x48 Icons [98.4 kB] Get:15 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64 Icons [163 kB] Get:16 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64@2 Icons [15.8 kB] Get:17 https://packages.microsoft.com/repos/ms-teams stable/main amd64 Packages [6,403 B] Get:18 http://au.archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.5 kB] Get:19 http://au.archive.ubuntu.com/ubuntu focal/restricted i386 Packages [8,112 B] Ign:20 http://ppa.launchpad.net/hermlnx/dislocker/ubuntu focal InRelease Get:21 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [22.0 kB] Get:22 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en_AU [1,144 B] Get:23 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,163 B] Get:24 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en [6,212 B] Get:25 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 c-n-f Metadata [392 B] Get:26 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8,628 kB] Get:8 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease [23.5 kB] Get:27 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages [69.9 kB]