[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
Verified fixed on bionic in 5.48-0ubuntu3.3 Also comment #41 verifies eoan. (I am replying by email because Launchpad is timing out and refusing all web entry at the moment) -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted
Update: a kernel upgrade solved the mic white noise for me. I had been running a 5.0 kernel. Updating to a 5.4 kernel fixed it. -- 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/1827440 Title: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hopefully all the necessary info is in the extra stuff that automatically got sent. Basically, I didn't do anything fancy, but audio recorded with my microphone (through Skype, and arecord in the Terminal) has tons of static and the voice is distorted or saturated. Booting this computer on Windows doesn't have issues, so that's why I don't think it's the computer, I think it's the OS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 1499 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 19:04:55 2019 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tyler 1562 F...m pulseaudio /dev/snd/pcmC0D0p: tyler 1562 F...m pulseaudio /dev/snd/controlC0: tyler 1562 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHS1TG00 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1861250] [NEW] Apparmor error failed to start profiles
Public bug reported: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: New Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script
[Touch-packages] [Bug 1860565] Re: Remove ubuntu-web-launchers from 18.04.4
I verified successfully that with bionic desktop 20200128 the amazon launcher is gone from the dock in both the live session and the installed system. marking as verification-done ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1860565 Title: Remove ubuntu-web-launchers from 18.04.4 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Committed Bug description: ubuntu-web-launchers only contains the amazon launcher and should be removed from 18.04.4 like focal. [Test Case] 1. On a freshly installed system, uninstall ubuntu-web-launchers, logout/login. 2. Boot an ISO without ubuntu-web-launchers being seeded to the live session 3. Do a default installation from an ISO without ubuntu-web-launchers being seeded 4. Customise your launcher by adding or removing some icons. Remove ubuntu-web-launchers and make sure that your custom icons are all there 5. *With the default set of launcher favourites*, update to ubuntu-settings 18.04.7 For all cases, verify that the Amazon launcher is not in the dock [Impact] None [Risk of regression] If the shell handles this removal badly on existing systems then maybe favourites wouldn't be displayed or you'd see a weird icon not found icon (test cases #4). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:41:43 2020 InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860565/+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 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted
Tyler, did you ever find a solution to this? I'm having the same problem with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The only "solution" I've found is to turn off "internal mic boost" using alsa-mixer (hit F5 to show all channels, cursor all the way to the right) and keep the mic capture level below 20%. So it works, but far from ideal since the mic is low (but better than making the person on the other end of a call hearing a shitload of white noise that's produced otherwise). -- 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/1827440 Title: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hopefully all the necessary info is in the extra stuff that automatically got sent. Basically, I didn't do anything fancy, but audio recorded with my microphone (through Skype, and arecord in the Terminal) has tons of static and the voice is distorted or saturated. Booting this computer on Windows doesn't have issues, so that's why I don't think it's the computer, I think it's the OS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 1499 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 19:04:55 2019 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tyler 1562 F...m pulseaudio /dev/snd/pcmC0D0p: tyler 1562 F...m pulseaudio /dev/snd/controlC0: tyler 1562 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHS1TG00 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Touch-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
Thanks. I don't know for sure what package fixed this, or how many years ago it really got fixed, but at least the bug is now closed. ** Changed in: bluez (Ubuntu) Status: Incomplete => Fix Released -- 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/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez-utils: New Status in Linux Mint: Invalid Status in Unity: Invalid Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Status in udev package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+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 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
It seems a shame that my affected hardware didn't live to see this day :( If it had held on another year and a half, I would've been able to test this out. Glad Martin's was still working to check it out over _eleven years_ (!) after he first commented on this issue! -- 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/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez-utils: New Status in Linux Mint: Invalid Status in Unity: Invalid Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Status in udev package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+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 1860764] Re: Line out audio device is missing after resume-from-suspend
** Tags added: regression-release -- 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/1860764 Title: Line out audio device is missing after resume-from-suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: this problem happened after i updated system when i power on after sleeping i have problem with sounds. it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2511 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (362 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+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 1861191] Re: System hangs on graphical boot after kernel and nVidia upgrade
Please reproduce the hang and black screen once again, then reboot again with the nouveau.modeset=0 workaround and run: journalctl -b-1 > prevboot.txt and attach the file 'prevboot.txt' here. ** Tags added: black-screen ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861191 Title: System hangs on graphical boot after kernel and nVidia upgrade Status in Ubuntu: Incomplete Bug description: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Tue Jan 28 09:57:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-26-generic, x86_64: installed nvidia, 390.116, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4] InstallationDate: Installed on 2019-12-05 (53 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 23445PU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5977afa2-a407-43bd-a6f4-e5dfd01188c0 ro quiet splash mouveau.modset=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445PU 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn23445PU:pvrThinkPadT430:rvnLENOVO:rn23445PU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445PU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1861191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1861216] Re: Dummy Output for audio output device after upgrade to focal
*** This bug is a duplicate of bug 1860697 *** https://bugs.launchpad.net/bugs/1860697 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1860697, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1860697 Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 -- 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/1861216 Title: Dummy Output for audio output device after upgrade to focal Status in pulseaudio package in Ubuntu: New Bug description: After and upgrade to Focal audio output not working. Dummy Output device in the sound settings. It seems like drivers are loaded: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 2292 Flags: bus master, fast devsel, latency 64, IRQ 177 Memory at ea23c000 (64-bit, non-prefetchable) [size=16K] Memory at ea00 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci #champagne ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 10:02:41 2020 InstallationDate: Installed on 2019-12-25 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-27 (0 days ago) dmi.bios.date: 10/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET15W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET15W(1.09):bd10/18/2019:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861216/+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 1861237] Re: Audio not detected on 20.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1861237 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** No longer affects: kubuntu-meta (Ubuntu) -- 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/1861237 Title: Audio not detected on 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861237/+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 1861237] [NEW] Audio not detected on 20.04
You have been subscribed to a public bug: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 audio focal thinkpad -- Audio not detected on 20.04 https://bugs.launchpad.net/bugs/1861237 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1782510] Re: lightdm automatically logs in after logout
So I've just restarted the lightdm.service : $ sudo service lightdm restart $ service lightdm status ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-01-29 02:09:37 CET; 13s ago Docs: man:lightdm(1) Process: 15476 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 15480 (lightdm) CGroup: /system.slice/lightdm.service ├─15480 /usr/sbin/lightdm ├─15490 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch └─15618 lightdm --session-child 12 19 Jan 29 02:09:37 sebastien-B206 systemd[1]: Starting Light Display Manager... Jan 29 02:09:37 sebastien-B206 systemd[1]: Started Light Display Manager. Jan 29 02:09:38 sebastien-B206 lightdm[15522]: pam_kwallet(lightdm-greeter:setcred): (null): pam_sm_setcred Jan 29 02:09:38 sebastien-B206 lightdm[15522]: pam_kwallet5(lightdm-greeter:setcred): (null): pam_sm_setcred Jan 29 02:09:38 sebastien-B206 lightdm[15522]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Jan 29 02:09:42 sebastien-B206 lightdm[15618]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "sebastien" -- 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/1782510 Title: lightdm automatically logs in after logout Status in GNOME Keyring: New Status in Light Display Manager: New Status in skype: New Status in lightdm package in Ubuntu: Confirmed Bug description: Lightdm makes it impossible to logout. After I logout the lightdm logs me automatically backs in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 19 01:18:52 2018 InstallationDate: Installed on 2016-04-26 (814 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1782510/+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 1782510] Re: lightdm automatically logs in after logout
Hi, I have the same pb. on my ubuntu xenial, here's what I get in the "lightdm.service" journal : $ journalctl -au lightdm -S "2020-01-29 1:59" -- Logs begin at lun. 2020-01-27 11:14:43 CET, end at mer. 2020-01-29 02:01:47 CET. -- janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Failed to write utmpx: Permission denied janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Error writing to daemon: Bad file descriptor janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Error writing to daemon: Bad file descriptor janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Error writing to daemon: Bad file descriptor janv. 29 01:59:45 sebastien-B206 lightdm[11808]: Failed to write utmpx: Permission denied -- 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/1782510 Title: lightdm automatically logs in after logout Status in GNOME Keyring: New Status in Light Display Manager: New Status in skype: New Status in lightdm package in Ubuntu: Confirmed Bug description: Lightdm makes it impossible to logout. After I logout the lightdm logs me automatically backs in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 19 01:18:52 2018 InstallationDate: Installed on 2016-04-26 (814 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1782510/+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 1861232] [NEW] ubuntu-bug has missing text in two dialogs
Public bug reported: I ran ubuntu-bug update-manager. The second and fourth dialogs that pop up just say "text". While we're on the subject, Launchpad has been timing out submitting the reports (or even getting past openid). I only persisted because I wanted to get bug reports in, but you're very likely missing reports from users because of the timeouts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.9 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 28 17:45:47 2020 InstallationDate: Installed on 2019-03-28 (306 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot_93.png" https://bugs.launchpad.net/bugs/1861232/+attachment/5323656/+files/screenshot_93.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861232 Title: ubuntu-bug has missing text in two dialogs Status in apport package in Ubuntu: New Bug description: I ran ubuntu-bug update-manager. The second and fourth dialogs that pop up just say "text". While we're on the subject, Launchpad has been timing out submitting the reports (or even getting past openid). I only persisted because I wanted to get bug reports in, but you're very likely missing reports from users because of the timeouts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.9 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 28 17:45:47 2020 InstallationDate: Installed on 2019-03-28 (306 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861232/+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 1861230] [NEW] _sasl_plugin_load failed
Public bug reported: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found ** Affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: New Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1577738] Re: pm-utils does not write pm-suspend.log file
EDIT: I wonder now how important bugs related to pm-utils are? Many distros now use systemd, which is the case of Kubuntu, although there still are some pm-utils installed. I upgraded to 19.10 a while back and I now use systemd with no issues and all logs created. If there is a fix for this bug affecting pm-utils (assuming it's a bug), I won't be part of testing and regression. I have moved to systemd. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1577738 Title: pm-utils does not write pm-suspend.log file Status in pm-utils package in Ubuntu: Fix Released Bug description: Hello, I hope I'm filing this information the proper way and I thank you for reading it. 1) Kubuntu 16.04 2) pm-utils 1.4.1-16 3) As far as the info I could find, the package "pm-utils" is supposed to write log files in /var/log, such as "pm-suspend.log". These log files, as you know, help troubleshoot hibernate/resume issues. I happen to have one issue with hooks that don't run on resume, that do run prior to hibernate when I run them manually and don't after resume when I run them the same manual way. (different issue than this bug report) 4) Therefore I need to scan through pm-suspeng.log file, but the file is not created on my machine, anywhere on the HDD. I have added my user to the "systemd-journal", "root" and "sudo" groups, in case that could help, I still don't see the log file. With previous Kubuntu versions (13.10 and others before, didn't try between 13.10 and 16.04), this log file was created right away. After searching and trying things out, I'm leaning towards the possibility of a bug, which is the reason why I am posting here. I do not know what other information to provide. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1577738/+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 1861177] Re: seccomp_rule_add is very slow
@mvo and @ijohnson, fyi, the fix for this may help with slow snap- seccomp (unconfirmed; not actively working on it at this time). ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: New Status in libseccomp package in Ubuntu: New Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1861191] Re: System hangs on graphical boot after kernel and nVidia upgrade
nVidia driver 340.107 is available, however switching to that in Software & Updates has resulted in some issues. After Apply Changes, I am kicked to the Nouveau driver. And I get an ErrorBrokenCount > 0 Trying to resolve with sudo apt --fix-broken install as recommended by apt gives me: The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 482145 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861191 Title: System hangs on graphical boot after kernel and nVidia upgrade Status in xorg package in Ubuntu: New Bug description: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Tue Jan 28 09:57:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-26-generic, x86_64: installed nvidia, 390.116, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4] InstallationDate: Installed on 2019-12-05
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Is there a rough timeline when this will be available in eoan? I can confirm the bug on all my ubuntu 19.10 installs and I have to switch vpns frequently. Thanks for the great work! -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1036764] Re: Guest username is nasty
Ubuntu releases no longer have a Guest account Further to comment #6, closing Papercuts task ** Changed in: hundredpapercuts Status: Confirmed => Won't Fix -- 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/1036764 Title: Guest username is nasty Status in One Hundred Papercuts: Won't Fix Status in Light Display Manager: Won't Fix Status in lightdm package in Ubuntu: Won't Fix Bug description: When logging in to the guest account, the user is assigned the username guest-hWf1ay. I am assuming that the latter half of that is an auto-generated string. This is rather ugly and I think it should be changed to something a little more user-friendly, such as 'Guest'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1036764/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
bionic: - lxcfs/3.0.3-0ubuntu1~18.04.1 (s390x) - 3.0.3-0ubuntu1~18.04.1 util-linux/2.31.1-0.4ubuntu3.5 2020-01-28 11:07:15 UTC 0h 02m 02s mfo pass - gnocchi/4.2.5-0ubuntu1 (armhf) - (same failure in -updates too, not a regression introduced in -proposed) - 4.2.5-0ubuntu1 util-linux/2.31.1-0.4ubuntu3.4 2020-01-28 13:48:01 UTC 0h 29m 16s mfo fail - 4.2.5-0ubuntu1 util-linux/2.31.1-0.4ubuntu3.5 2020-01-28 11:31:54 UTC 0h 30m 53s mfo fail - systemd/237-3ubuntu10.33 (amd64) - 237-3ubuntu10.33util-linux/2.31.1-0.4ubuntu3.5 2020-01-28 15:04:17 UTC 0h 38m 03s mfo pass - postgresql-10/10.10-0ubuntu0.18.04.1 (armhf) - 10.10-0ubuntu0.18.04.1 util-linux/2.31.1-0.4ubuntu3.5 2020-01-28 11:14:19 UTC 0h 11m 04s mfo pass -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Committed Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Committed Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
xenial: - nplan/0.32~16.04.7 (amd64) - 0.32~16.04.7util-linux/2.27.1-6ubuntu3.10 2020-01-28 11:12:12 UTC 0h 24m 52s mfo pass - mysql-5.7/5.7.28-0ubuntu0.16.04.2 (i386, ppc64el, amd64) - (new version in -updates fixed issues.) - 5.7.29-0ubuntu0.16.04.1 util-linux/2.27.1-6ubuntu3.10 2020-01-28 11:36:59 UTC 0h 50m 56s mfo pass - 5.7.29-0ubuntu0.16.04.1 util-linux/2.27.1-6ubuntu3.10 2020-01-28 11:07:56 UTC 0h 25m 01s mfo pass - 5.7.29-0ubuntu0.16.04.1 util-linux/2.27.1-6ubuntu3.10 2020-01-28 11:07:56 UTC 0h 25m 01s mfo pass - zfs-linux/0.6.5.6-0ubuntu28 (ppc64el) - 0.6.5.6-0ubuntu28 util-linux/2.27.1-6ubuntu3.10 2020-01-28 10:42:41 UTC 0h 07m 43s mfo pass - lxd/2.0.11-0ubuntu1~16.04.4 (s390x) - 2.0.11-0ubuntu1~16.04.4 util-linux/2.27.1-6ubuntu3.10 2020-01-28 10:36:48 UTC 0h 04m 46s mfo pass -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Committed Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Committed Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
eoan: - tracker/2.3.0-1 (armhf) - 2.3.0-1 util-linux/2.34-0.1ubuntu2.22020-01-28 13:29:26 UTC 0h 09m 34s mfo pass - kopanocore/8.7.0-3build2 (armhf) - 8.7.0-3build2 util-linux/2.34-0.1ubuntu2.22020-01-28 11:22:03 UTC 0h 09m 49s mfo pass - mir/1.4.0-0ubuntu3 (armhf) - 1.4.0-0ubuntu3 util-linux/2.34-0.1ubuntu2.22020-01-28 11:13:28 UTC 0h 04m 03s mfo pass - ola/unknown (armhf) - 0.10.7.nojsmin-2util-linux/2.34-0.1ubuntu2.22020-01-28 11:25:11 UTC 0h 13m 43s mfo pass - systemd/242-7ubuntu3.2 (s390x) - 237-3ubuntu10.33util-linux/2.31.1-0.4ubuntu3.5 2020-01-28 15:04:17 UTC 0h 38m 03s mfo pass - glib2.0/2.62.1-1 (i386) - 2.62.1-1util-linux/2.34-0.1ubuntu2.22020-01-28 11:30:50 UTC 0h 12m 25s mfo pass - openjdk-lts/11.0.5+10-0ubuntu1.1 (armhf, arm64) - FLAKY timed out (both archs) - sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386) - 1.4.0-18-g5e3283c-1ubuntu1 util-linux/2.34-0.1ubuntu2.22020-01-28 16:03:28 UTC 0h 14m 10s mfo pass -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Committed Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Committed Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1861220] [NEW] Same as 1860806 but executed on Ubuntu 18.04
Public bug reported: Ubuntu 18.04LTS and also Ubuntu 19.04 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. This may be redundant as I attached the file to Bug # 1860806. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 10:10:55 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: IwConfig: lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 disconnected started unknown enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1861220 Title: Same as 1860806 but executed on Ubuntu 18.04 Status in network-manager package in Ubuntu: New Bug description: Ubuntu 18.04LTS and also Ubuntu 19.04 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. This may be redundant as I attached the file to Bug # 1860806. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 10:10:55 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: IwConfig: lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 disconnected started unknown enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1861220/+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 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
SRU team, The autopkgtests regressions reported for the three releases (xenial/bionic/eoan) were all* transient issues resolved with re-runs (see 'pass' status records below). (*) The only the exception (not a transient issue) is gnocchi/bionic/armhf, which is _not_ a regression either as the same error happens with -updates (see both 'fail' status records below, with versions in -proposed/-updates.) The updated status (passing tests) is already reflected in pending-sru [1]. Thanks, Mauricio [1] https://people.canonical.com/~ubuntu-archive/pending-sru.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Committed Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Committed Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
The fix works for me, too (libpoppler90:amd64 0.80.0-0ubuntu1.1). No crash in evince or atril. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Eoan: Fix Committed Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1631631] Re: Trivial bug in man documentation: forgotten --strip-unneeded option in objcopy SYNOPSIS
--strip-unneeded is included in the SYNOPSIS section of the objcopy manpage for binutils 2.33.90.20200122-1ubuntu2 (focal release) so closing as fixed ** Changed in: binutils (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1631631 Title: Trivial bug in man documentation: forgotten --strip-unneeded option in objcopy SYNOPSIS Status in One Hundred Papercuts: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: In the man page of "objcopy" the "--strip-unneeded" option: - is described in OPTIONS section; - but is forgotten in SYNOPSIS section (don't confuse with "--strip-unneeded-symbol=" and "--strip-unneeded-symbols=", which aren't forgotten). $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy binutils binutils: Installed: 2.26.1-1ubuntu1~16.04.3 Candidate: 2.26.1-1ubuntu1~16.04.3 Version table: *** 2.26.1-1ubuntu1~16.04.3 500 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2.26-8ubuntu2 500 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I expected SYNOPSIS and OPTIONS sections of the man page of "objcopy" to be consistent. Option "--strip-unneeded" present in OPTIONS section, is absent in SYNOPSIS section. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1631631/+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 1860806] Re: Ubuntu 19.04 new ethernet problem
This file was generated just after a power-on boot. This is the condition where the ethernet icon is missing. I had to save the data to file since in this condition I have no Internet access. apport-cli -f -p network-manager --save 1860806.apport ** Attachment added: "1860806.apport" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+attachment/5323621/+files/1860806.apport ** Summary changed: - Ubuntu 19.04 new ethernet problem + Ubuntu 18.04 and 19.04 new ethernet problem -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] Re: Ubuntu 19.04 new ethernet problem
On a clean power on boot I ran: apport-cli -f -p network-manager --save 1860806.apport So this file contains (hopefully) the information needed while the machine is in the broken condition (only on fresh power-on). After restart (soft boot) to obtain Internet I ran: ubuntu-bug 1860806.apport I don't know how to force the last command to direct the information to this bug report. -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1861216] [NEW] Dummy Output for audio output device after upgrade to focal
Public bug reported: After and upgrade to Focal audio output not working. Dummy Output device in the sound settings. It seems like drivers are loaded: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 2292 Flags: bus master, fast devsel, latency 64, IRQ 177 Memory at ea23c000 (64-bit, non-prefetchable) [size=16K] Memory at ea00 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci #champagne ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 10:02:41 2020 InstallationDate: Installed on 2019-12-25 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-27 (0 days ago) dmi.bios.date: 10/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET15W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET15W(1.09):bd10/18/2019:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1861216 Title: Dummy Output for audio output device after upgrade to focal Status in pulseaudio package in Ubuntu: New Bug description: After and upgrade to Focal audio output not working. Dummy Output device in the sound settings. It seems like drivers are loaded: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 2292 Flags: bus master, fast devsel, latency 64, IRQ 177 Memory at ea23c000 (64-bit, non-prefetchable) [size=16K] Memory at ea00 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci #champagne ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 10:02:41 2020 InstallationDate: Installed on 2019-12-25 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-27 (0 days ago) dmi.bios.date: 10/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET15W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET15W(1.09):bd10/18/2019:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861216/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
I am an engineer at Broadcom and have been assigned to investigate this issue. To that end, I have a few clarifying questions: 1a) What is the benchmark tool you are using and could you provide a link to where I can get it? b) What kind of network traffic is it sending? 2a) In what units are the data rate parameters "--rx_rate 10e6 --tx_rate 10e6" specified? b) What data rate are you attempting to send? The report notes that the platform can't be the issue at 1G, but are you attempting to utilize 10G? 3) Perhaps stating the obvious here, but has anybody looked into the warning? "[WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected." which is probably related to this error: "EnvironmentError: OSError: error in pthread_setschedparam" 4 a) I am personally unfamiliar with the USRP x310, could you provide some more information about it? Googling for it seems to indicate it is some kind of software defined radio platform? b) Is there a way to get access to one to reproduce and diagnose this issue? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Could you also please dump the ethtool statistics for the NIC? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this link to try determine the problem: https://files.ettus.com/manual/page_usrp_x3x0_config.html - There is no firewall on that port
[Touch-packages] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)
@chad.smith The full branch will not be SRU-d, just individual changes.
The change itself is in focal-proposed waiting for an apt fix to migrate
to the release pocket, then the change can be SRU-d to stable releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
In Progress
Status in unattended-upgrades source package in Trusty:
New
Status in unattended-upgrades source package in Xenial:
New
Status in unattended-upgrades source package in Bionic:
New
Bug description:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1861191] Re: System hangs on graphical boot after kernel and nVidia upgrade
Thank you for reporting this bug and make ubuntu better. Does your graphics card list several driver versions? if yes, did you try switching to another nvidia driver yet? ubuntu-drivers list to check -- 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/1861191 Title: System hangs on graphical boot after kernel and nVidia upgrade Status in xorg package in Ubuntu: New Bug description: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Tue Jan 28 09:57:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-26-generic, x86_64: installed nvidia, 390.116, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4] InstallationDate: Installed on 2019-12-05 (53 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 23445PU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5977afa2-a407-43bd-a6f4-e5dfd01188c0 ro quiet splash mouveau.modset=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445PU 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn23445PU:pvrThinkPadT430:rvnLENOVO:rn23445PU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445PU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1861191/+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 1853203] Re: 30 seconds boot delay when usr fs is on lvm
I upgraded to Kubuntu 19.10 and the delay disappeared. -- 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/1853203 Title: 30 seconds boot delay when usr fs is on lvm Status in initramfs-tools package in Ubuntu: New Bug description: A bit similar to "30 seconds boot delay when root fs is on lvm": https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499 I installed Kubuntu 19.04 with 2 LVM volume groups (one per disk). My root and my /usr are both located on the same LVM. Mounting /usr takes 30s, but if I move the /usr to a non-LVM partition then the mounting takes no time and the whole boot process is very fast. In the script "scripts/local" of initramfs-tools, there is a 30s timeout called "slumber" passed to the "wait-for-root" program (from initramfs-tools-bin), and the wait comes from there (I could see it by adding traces before and after). If I decrease the timeout to 10s, the system can still boot correctly (and 20s faster). I don't know if the problem comes from the initramfs-tools scripts, from wait-for-root or from the integration in (K)Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: initramfs-tools-core 0.131ubuntu19.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 19 22:11:18 2019 InstallationDate: Installed on 2017-08-26 (815 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to disco on 2019-08-18 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1853203/+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 1861191] [NEW] System hangs on graphical boot after kernel and nVidia upgrade
Public bug reported: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Tue Jan 28 09:57:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-26-generic, x86_64: installed nvidia, 390.116, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4] InstallationDate: Installed on 2019-12-05 (53 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 23445PU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5977afa2-a407-43bd-a6f4-e5dfd01188c0 ro quiet splash mouveau.modset=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445PU 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn23445PU:pvrThinkPadT430:rvnLENOVO:rn23445PU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445PU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1861191 Title: System hangs on graphical boot after kernel and nVidia upgrade Status in xorg package in Ubuntu: New Bug description: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0
[Touch-packages] [Bug 1860806] Re: Ubuntu 19.04 new ethernet problem
I replaced Ubuntu 19.04 with 18.04 LTS. The problem is still the same. 1. Power up computer 2. Ethernet icon does not show. "Wired..." does not show. No network access. 3. Restart computer (soft boot). 4. Ethernet icon returns as well as Internet access. Note: I ran apport-collect 1860806 AFTER the reset process since I have no Internet access before that time, so likely the problem will not be obvious. Is there a way I can run "apport-collect 1860806" after a power on boot and send the data later when the Internet is working? -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323556/+files/ProcCpuinfoMinimal.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323557/+files/WifiSyslog.txt ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] NetDevice.eno1.txt
apport information ** Attachment added: "NetDevice.eno1.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323552/+files/NetDevice.eno1.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323555/+files/PciNetwork.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323553/+files/NetDevice.lo.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323554/+files/NetworkManager.conf.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323550/+files/Dependencies.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323551/+files/IpAddr.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1860806/+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 1860806] Re: Ubuntu 19.04 new ethernet problem
apport information ** Tags added: apport-collected bionic ** Description changed: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2020-01-26 (2 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + IpRoute: + default via 192.168.1.1 dev eno1 proto dhcp metric 100 + 169.254.0.0/16 dev eno1 scope link metric 1000 + 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 + IwConfig: + lono wireless extensions. + + eno1 no wireless extensions. + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + Package: network-manager 1.10.6-2ubuntu1.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-74-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + nmcli-con: + NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE + Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- + nmcli-dev: + DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH + eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 + lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1860806/+attachment/5323549/+files/CRDA.txt -- 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/1860806 Title: Ubuntu 19.04 new ethernet problem Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails
** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1861177] [NEW] seccomp_rule_add is very slow
Public bug reported: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in libseccomp package in Ubuntu: New Bug description: There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1861177/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)
Balint,
It looks like this is addressed by:
https://github.com/mvo5/unattended-upgrades/pull/244 which has now merged. Do
we know if that branch going to be SRU'd to Trusty, Xenial and Bionic
** Changed in: unattended-upgrades (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
In Progress
Status in unattended-upgrades source package in Trusty:
New
Status in unattended-upgrades source package in Xenial:
New
Status in unattended-upgrades source package in Bionic:
New
Bug description:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1370953] Re: layout switch is delayed
I confirm this bug is still present in ubuntu 19.10. My comment in gnome bug tracker: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1154#note_696130 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1154 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1154 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Status in gconf package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1861168] [NEW] [feature request] UFW export/import function
Public bug reported: Hello, is it possible to implement an export/import feature into UFW? This would increase the user friendliness of the program for people that are less handy with linux and firewalls. I also read the manpage of UFW but couldn't find where the configuration files are located, I had to go to stackoverflow to find the answer. A use case would be, user installs ufw and adds rules(e.g. 80, 8080, 443, 22, 3306), user exports the firewall configuration to a desired folder (ufw export ./firewall rules/export 28-01-2020.log), user logs in to second device with ufw installed and runs ufw import /firewall rules/export 28-01-2020.log. the "Export" feature is simply a command that copies the correct configuration files(even if ufw changes the location of the file) to a desired location, that way users don't have to dig into the filesystem to find the configuration files of ufw. ** Affects: ufw Importance: Undecided Status: New ** Tags: back-up export-import import ** Package changed: ufw (Ubuntu) => ufw -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1861168 Title: [feature request] UFW export/import function Status in ufw: New Bug description: Hello, is it possible to implement an export/import feature into UFW? This would increase the user friendliness of the program for people that are less handy with linux and firewalls. I also read the manpage of UFW but couldn't find where the configuration files are located, I had to go to stackoverflow to find the answer. A use case would be, user installs ufw and adds rules(e.g. 80, 8080, 443, 22, 3306), user exports the firewall configuration to a desired folder (ufw export ./firewall rules/export 28-01-2020.log), user logs in to second device with ufw installed and runs ufw import /firewall rules/export 28-01-2020.log. the "Export" feature is simply a command that copies the correct configuration files(even if ufw changes the location of the file) to a desired location, that way users don't have to dig into the filesystem to find the configuration files of ufw. To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1861168/+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 1762391] Re: pam_group.so is not evaluated by gnome-terminal
systemd in Xenial differs to much to cleanly apply the upstream fix. It would require reimplementing it and may be more risky than useful. Marking Won't fix. ** Changed in: systemd (Ubuntu Xenial) Status: New => Won't Fix -- 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/1762391 Title: pam_group.so is not evaluated by gnome-terminal Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Eoan: In Progress Status in systemd source package in Focal: Fix Released Bug description: [Impact] pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that processes were never getting group membership they were expected to get via pam_group module. [Test Case] * Add a /etc/security/group.conf entry, e.g. *;*;*;Al-2400;dialout,users * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus). Expected result: Logged in user is a member of 'dialout' and 'users' groups. Actual result: no group membership gained from pam_group. [Regression Potential] * It introduces a new PAM warning message in some scenarios (e.g. for systemd DynamicUser=1 units) for users that can't authenticate (pam_setcred fails in such case). * In certain systems user group membership may be extended by pam_group. [Other Info] Original bug description: We are using Ubuntu in a university network with lots of ldap users. To automatically map ldap users/groups to local groups we are using pam_group.so. This has worked for years. With the upgrade from Xenial to Bionic /etc/security/group.conf is not evaluated anymore by gnome-terminal as it runs as systemd --user. Xterm, ssh, su, and tty* however do work as expected. Only the default gnome-terminal behaves different. According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this might not be a bug, but a feature. Nevertheless this behavior is very unexpected when upgrading from Xenial to Bionic and therefore should at least added to the changelog. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 13:17:52 2018 InstallationDate: Installed on 2018-03-29 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+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 1861063] Re: Dualshock4 controller doesn't stay connected
I have just tried with kernel 5.5.0-050500-generic I got from here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/ Same issue. -- 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/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 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:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+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 1836444] Re: Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main)
I know that Qt4 is practically dead, however, it would be nice to merge with Debian to get the vulnerability fixes in 4:4.8.7+dfsg-18. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1836444 Title: Merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main) Status in qt4-x11 package in Ubuntu: New Bug description: Please merge qt4-x11 4:4.8.7+dfsg-18 (universe) from Debian unstable (main) I cannot work on this merge myself. I filed this bug as a reference. Explanation of the Ubuntu delta: * Merge with Debian since qtchooser has versioned Breaks. (LP: #1584654) * Add one more macro to qt4-x11 moc to fix failing to parse BOOST_JOIN. * No-change rebuild for libpng soname change. * Rebuild against libmysqlclient20. * Merge with Debian; remaining changes: - Pass list-missing to dh_install instead of fail-missing, since we don't install the QtWebkit headers - Make sure libqt4-opengl-dev depends on gles libs for armel and armhf - Do not package ibase/firebird and sqlite2 package + remove from debian/control + libqt4-sql doesn't recommend libqt4-sql-ibase and libqt4-sql-sqlite2 - Also exclude webkit examples from dh_shlibdeps - Do not build libqt4-phonon, disable in debian/control - Add debian/Trolltech.conf and install it in libqtcore4.install - Build with -no-neon on armel and armhf - Build with -no-javascript-jit on arm64 - Add patches: + kubuntu_10_ibus_input_method.diff + kubuntu_12_fix_stack_protector.diff + kubuntu_28_xi2.1.patch + kubuntu_30_translucent_drag_pixmap.diff + kubuntu_37_cups_settings.diff + kubuntu_39_fix_medium_font.diff + kubuntu_40_disable_neon.patch + kubuntu_43_no_meego_helper.patch + kubuntu_93_disable_overlay_scrollbars.diff + kubuntu_94_xinput_valuators_fix.diff + kubuntu_95_qt_disable_bounce.diff + kubuntu_97_a11y_qt_and_qml_backport.diff + kubuntu_98_a11y_fix_crash.diff + kubuntu_glib-honor-ExcludeSocketNotifiers-flag.diff + kubuntu_qclipboard_delay.diff + kubuntu_qclipboard_fix_recursive.diff - Drop powerpc_designer_gstabs.diff, it breaks powerpc * Update symbols files. Changelog entries since current eoan version 4:4.8.7+dfsg-7ubuntu1: qt4-x11 (4:4.8.7+dfsg-18) unstable; urgency=medium * Team upload. [ Edward Betts ] * debian/NEWS: Replace UNRELEASED with unstable. [ Alexander Volkov ] * Backport some vulnerability fixes from Qt 5 (closes: #923003). - CVE-2018-15518: double free or corruption in QXmlStreamReader. - CVE-2018-19869: Qt Svg crash when parsing malformed url reference. - CVE-2018-19870: NULL pointer dereference in QGifHandler. - CVE-2018-19871: QTgaFile CPU exhaustion. - CVE-2018-19872: crash when parsing a malformed PPM image. - CVE-2018-19873: QBmpHandler segfault on malformed BMP file. -- Dmitry Shachnev Fri, 12 Apr 2019 23:10:28 +0300 qt4-x11 (4:4.8.7+dfsg-17) unstable; urgency=medium * Add fix-build-icu59.patch from OpenSuse. Fixes build with icu59 (Closes: #898542). Thanks John Paul Adrian Glaubitz for digging the patch! * Put the source package in section oldlibs. We do not expect new developments with qt4-x11. * Update Vcs-[Git Browser] to the new location in salsa.debian.org. -- Lisandro Damián Nicanor Pérez Meyer Tue, 15 May 2018 13:24:10 -0300 qt4-x11 (4:4.8.7+dfsg-16) unstable; urgency=medium * Update symbols files with buildds' logs. * Add a patch by Manuel A. Fernandez Montecelo to provide riscv64 support (Closes: #897667). -- Lisandro Damián Nicanor Pérez Meyer Fri, 04 May 2018 22:53:17 -0300 qt4-x11 (4:4.8.7+dfsg-15) unstable; urgency=medium * Actually upload it to unstable. -- Lisandro Damián Nicanor Pérez Meyer Wed, 18 Apr 2018 17:45:31 -0300 qt4-x11 (4:4.8.7+dfsg-14) experimental; urgency=medium * Update symbols files with buildds' logs. * Add NEWS.Debian to explicitely tell users of the OpenSSL 1.1 patch. -- Lisandro Damián Nicanor Pérez Meyer Wed, 18 Apr 2018 16:30:10 -0300 qt4-x11 (4:4.8.7+dfsg-13) experimental; urgency=medium * Add extra patch from Dmitry Eremin-Solenikov to make Qt4 work with OpenSSL 1.1 (Closes: #873275). * Recommend default-libmysqlclient-dev instead of libmysqlclient-dev. -- Lisandro Damián Nicanor Pérez Meyer Fri, 10 Nov 2017 15:36:11 -0300 qt4-x11 (4:4.8.7+dfsg-12) experimental; urgency=medium * Add openssl_1.1.patch to let Qt4 use OpenSSL 1.1 (Closes: #828522). - Switch libssl-1.0-dev to libssl-dev to use OpenSSL 1.1. * Update symbols files with current build log. -- Lisandro Damián Nicanor Pérez Meyer
[Touch-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
In a recent clean install of Ubuntu 19.10 I did not have any problems with this keyboard/mouse. Actually, its an integrated track pad. > On January 28, 2020 at 3:41 AM Daniel van Vugt > wrote: > > > Can anyone confirm if this bug still exists with Logitech Dinovos in a > current Ubuntu release? > > > ** Changed in: bluez (Ubuntu) >Status: Confirmed => Incomplete > > ** No longer affects: bluez > > ** Bug watch removed: Debian Bug tracker #355497 >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497 > > ** Bug watch removed: Debian Bug tracker #589388 >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589388 > > ** Bug watch removed: Red Hat Bugzilla #635244 >https://bugzilla.redhat.com/show_bug.cgi?id=635244 > > ** Bug watch removed: bugs.sabayon.org/ #2687 >http://bugs.sabayon.org/show_bug.cgi?id=2687 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/123920 > > Title: > Bluetooth Logitech Dinovo Keyboard/Mouse don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+subscriptions "Don't fear the penguin" Dr. Martin G. Miller mgmil...@optonline.net ** Bug watch added: Debian Bug tracker #355497 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497 ** Bug watch added: Debian Bug tracker #589388 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589388 ** Bug watch added: Red Hat Bugzilla #635244 https://bugzilla.redhat.com/show_bug.cgi?id=635244 ** Bug watch added: bugs.sabayon.org/ #2687 http://bugs.sabayon.org/show_bug.cgi?id=2687 -- 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/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez-utils: New Status in Linux Mint: Invalid Status in Unity: Invalid Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Status in udev package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+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 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
The fix works for me (libpoppler90 0.80.0-0ubuntu1.1), I can't see the crash anymore. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Eoan: Fix Committed Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1860764] Re: Line out audio device is missing after resume-from-suspend
additional info after sleeping i see in my sounds "Dummy output" instead "Line out Family 17 .." -- 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/1860764 Title: Line out audio device is missing after resume-from-suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: this problem happened after i updated system when i power on after sleeping i have problem with sounds. it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2511 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (362 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+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 1853802] Re: Chinese input problems in 20.04
Ok, so not a bug with any specific package. I'm reassigning this to ubuntu-meta and adding a needs-reassignment tag. That'll be better than keeping it here where it may never attract the attention of those that can consider your request. ** Package changed: ubuntu => ubuntu-meta (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => New ** Summary changed: - Chinese input problems in 20.04 + Minimal Chinese input options on live ISO ** Tags added: needs-reassignment -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1853802 Title: Minimal Chinese input options on live ISO Status in ubuntu-meta package in Ubuntu: New Bug description: Boot from 191120 Ubuntu 20.04 daily built. Selected Simplified Chinese locale. When tried to input Chinese, the dialog window shows three options: 汉语，Hanyu Pinyin (altgr), and 中文（智能拼音）。 The first two options do not work. Indication of poor quality control. Suggest removing both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1853802/+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 1853802] [NEW] Chinese input problems in 20.04
You have been subscribed to a public bug: Boot from 191120 Ubuntu 20.04 daily built. Selected Simplified Chinese locale. When tried to input Chinese, the dialog window shows three options: 汉语，Hanyu Pinyin (altgr), and 中文（智能拼音）。 The first two options do not work. Indication of poor quality control. Suggest removing both. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- Chinese input problems in 20.04 https://bugs.launchpad.net/bugs/1853802 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1860764] Re: Line out audio device is missing after resume-from-suspend
i have 19.10 , but when i upgraded system apt upgrade(3-4 weeks ago) i got this problem. could you give me a link how i should apply this https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/ to my system? -- 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/1860764 Title: Line out audio device is missing after resume-from-suspend Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: this problem happened after i updated system when i power on after sleeping i have problem with sounds. it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob2511 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (362 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (79 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860764/+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 1660316] Re: apparmor denial of CUPS
I'm seeing this in 19.10 as well. Good to know it's gone for at least two years without being fixed, way to go Canonical! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: cups 2.2.0-2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm
[Touch-packages] [Bug 1858802] Autopkgtest regression report (util-linux/2.34-0.1ubuntu2.2)
All autopkgtests for the newly accepted util-linux (2.34-0.1ubuntu2.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: tracker/2.3.0-1 (armhf) kopanocore/8.7.0-3build2 (armhf) mir/1.4.0-0ubuntu3 (armhf) ola/unknown (armhf) systemd/242-7ubuntu3.2 (s390x) glib2.0/2.62.1-1 (i386) openjdk-lts/11.0.5+10-0ubuntu1.1 (armhf, arm64) sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#util-linux [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Bionic: Fix Committed Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Committed Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Unknown Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1715931] Re: Update to exiv2 version 0.27
exiv2 (0.27.2-7) just landed in debian unstable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.27 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1849859] Re: smb printing fails
I can confirm this bug is present on UBUNTU 19.10 with latest samba packages installed. Printer is working with virtual window 10 machine installed on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
Can anyone confirm if this bug still exists with Logitech Dinovos in a current Ubuntu release? ** Changed in: bluez (Ubuntu) Status: Confirmed => Incomplete ** No longer affects: bluez ** Bug watch removed: Debian Bug tracker #355497 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497 ** Bug watch removed: Debian Bug tracker #589388 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589388 ** Bug watch removed: Red Hat Bugzilla #635244 https://bugzilla.redhat.com/show_bug.cgi?id=635244 ** Bug watch removed: bugs.sabayon.org/ #2687 http://bugs.sabayon.org/show_bug.cgi?id=2687 -- 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/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez-utils: New Status in Linux Mint: Invalid Status in Unity: Invalid Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.22 package in Ubuntu: Won't Fix Status in udev package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+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 1861082] [NEW] ubuntu-bug doesn't know how to file bugs against snaps
Public bug reported: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: champagne ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in apport package in Ubuntu: New Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861082/+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 1860902] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Ok, I checked again and now it works. I think it was because I have not restarted after changing probe_mask=1. Thank you very much for your help and have a nice day! -- 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/1860902 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After installing an update (i can't remember which), i stopped hearing sound from the system. It only showed that headphones were connected(though they weren't), but even if i connected them, i could still hear no sound. I installed PulseAudio, tried changing other things, but nothing worked. I remember typing a command, though i cannot remember it, and it doesn't appear in my terminal history(i think it is in the bug description), and after that the sound appears to be playing from "HDMI/DisplayPort". Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ana1682 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 11:21:04 2020 InstallationDate: Installed on 2019-08-02 (177 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ana1682 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 0JTTXY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JTTXY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-08-22T15:47:18.564156 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860902/+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 1860902] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
According to the dmesg.txt, the analog audio works well, I don't know why you saw dummy output from UI. (if everything looks good in the /proc/asound/*, then there must be sth wrong in the pulseaudio). [ 22.546462] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3246: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 22.546464] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 22.546466] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 22.546467] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 22.546468] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 22.546469] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [ 22.546471] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [ 22.546472] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 22.595714] input: HDA Intel PCH Headphone Mic as /devices/pci:00/:00:1f.3/sound/card0/input12 -- 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/1860902 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After installing an update (i can't remember which), i stopped hearing sound from the system. It only showed that headphones were connected(though they weren't), but even if i connected them, i could still hear no sound. I installed PulseAudio, tried changing other things, but nothing worked. I remember typing a command, though i cannot remember it, and it doesn't appear in my terminal history(i think it is in the bug description), and after that the sound appears to be playing from "HDMI/DisplayPort". Ubuntu 18.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ana1682 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 11:21:04 2020 InstallationDate: Installed on 2019-08-02 (177 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ana1682 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.0 dmi.board.name: 0JTTXY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.8.0:bd12/05/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JTTXY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078C dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-08-22T15:47:18.564156 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860902/+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 1861081] Re: Dependency error installing pulseaudio-module-bluetooth
It seems this is a side effect of a mistake made in the release and subsequent withdrawal of update 1:11.1-1ubuntu7.5. So it's not a bug in the code but is a problem people will encounter with Ubuntu updates... This should automatically correct itself with the re-release of 1:11.1-1ubuntu7.5. In the meantime you can manually install whichever set of packages you need from either: 1:11.1-1ubuntu7.4: https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4/+build/17893827 1:11.1-1ubuntu7.5: https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.5/+build/18146190 ** Tags added: update-reverted ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Committed -- 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/1861081 Title: Dependency error installing pulseaudio-module-bluetooth Status in pulseaudio package in Ubuntu: Fix Committed Bug description: running apt install pulseaudio-module-bluetooth i get the following error: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pulseaudio-module-bluetooth : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) E: Unable to correct problems, you have held broken packages. seems likely related to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622 but with a different package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861081/+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 1861081] [NEW] Dependency error installing pulseaudio-module-bluetooth
Public bug reported: running apt install pulseaudio-module-bluetooth i get the following error: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pulseaudio-module-bluetooth : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) E: Unable to correct problems, you have held broken packages. seems likely related to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622 but with a different package ** Affects: pulseaudio (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/1861081 Title: Dependency error installing pulseaudio-module-bluetooth Status in pulseaudio package in Ubuntu: New Bug description: running apt install pulseaudio-module-bluetooth i get the following error: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pulseaudio-module-bluetooth : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) E: Unable to correct problems, you have held broken packages. seems likely related to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622 but with a different package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861081/+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
