[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
@Dimitri, thank you for looking into this issue. This is the output of apt-cache policy: $ apt-cache policy oem-release oem-release: Installed: 20.04ubuntu2 Candidate: 20.04ubuntu2 Version table: *** 20.04ubuntu2 100 100 /var/lib/dpkg/status As per synaptic package manager, the maintainer of oem-release package is: "Commercial Engineering " This package also has dependencies with 'lsb-release'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in Dell Ubuntu Project: New Status in OEM Priority Project: New Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependen
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
This is the output of my dpkg-query for os-release: $ dpkg-query --search os-release systemd: /usr/share/man/man5/os-release.5.gz diversion by oem-release from: /usr/lib/os-release diversion by oem-release to: /usr/lib/os-release.oem-release base-files: /etc/os-release diversion by oem-release from: /usr/lib/os-release diversion by oem-release to: /usr/lib/os-release.oem-release base-files: /usr/lib/os-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinst
[Touch-packages] [Bug 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
@Steve, thank you for looking into this. If this is not a base-files issue, where could the problem be? I have not installed any other package myself. This is just the Ubuntu installation that the laptop came with. As an end user I am unable to see whether upgrade to 20.04.3 is successful or not. Clearly lsb_release is not saying so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. Af
[Touch-packages] [Bug 1946343] [NEW] Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
Public bug reported: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched 60.6 kB in 1s (55.7 kB/s) (Reading database ... 191154 files and directories currently installed.) Preparing to unpack .../base-files_11ubuntu5.4_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Unpacking base-files (11ubuntu5.4) over (11ubuntu5.4) ... Setting up base-files (11ubuntu5.4) ... motd-news.service is a disabled or a static unit, not starting it. Processing triggers for cracklib-runtime (2.9.6-3.2) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.4git20200323-0ubuntu6.2) ... update-initramfs: deferring update (trigger activated) Processing triggers for install-info (
[Touch-packages] [Bug 1938623] Re: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
Realizing this likely has more to do with the lack of driver support for usb-c hubs on linux - per pulseaudio's documentation ( https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module- switch-on-port-available ) : "# module-switch-on-connect Earlier this module was required to automatically switch to a newly plugged in USB sound card, but nowadays USB sound cards have higher priority than internal sound cards, so they automatically become the default sink (unless you have manually configured the default sink to be something else) and the need for this module is greatly reduced." "#module-switch-on-port-available (not on USB sound cards, though, since they don't support jack detection)" -- 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/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers Status in pulseaudio package in Ubuntu: Opinion Bug description: I'm using Ubuntu 21.04 with an intel tablet and a lenovo usb-c hub that has an audio adapter: See https://linux- hardware.org/?probe=09f8c72d80/ I never have anything hooked into the audio jack on usb-c hub, yet every time I plug my tablet into the usb-c hub the sound output switches to the usb-c hub instead of staying routed to the tablet speakers. I then have to go either into settings or use a sound output extension to switch it back to the speakers. This issue does not happen when using Windows 10 - audio stays routed through the tablet speakers - my guess is that it goes a step further and detects whether an audio jack actually has a cable plugged in or not. What package handles determining default audio routing for Ubuntu 21.04 / Gnome 3.38.5? I'd like to file a bug about this / possibly see if I can help make the defaults work better. See also OS confusion about default audio sink - pulse: https://askubuntu.com/questions/1231935/os-confusion-about-default- audio-sink-pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938623/+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 1938623] Re: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers
realized this has more to do with pulseaudio settings ** Changed in: ubuntu Status: New => Opinion ** Package changed: ubuntu => pulseaudio (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/1938623 Title: Audio output & input routes to usb-c hub (where audio jack is disconnected) instead of laptop speakers Status in pulseaudio package in Ubuntu: Opinion Bug description: I'm using Ubuntu 21.04 with an intel tablet and a lenovo usb-c hub that has an audio adapter: See https://linux- hardware.org/?probe=09f8c72d80/ I never have anything hooked into the audio jack on usb-c hub, yet every time I plug my tablet into the usb-c hub the sound output switches to the usb-c hub instead of staying routed to the tablet speakers. I then have to go either into settings or use a sound output extension to switch it back to the speakers. This issue does not happen when using Windows 10 - audio stays routed through the tablet speakers - my guess is that it goes a step further and detects whether an audio jack actually has a cable plugged in or not. What package handles determining default audio routing for Ubuntu 21.04 / Gnome 3.38.5? I'd like to file a bug about this / possibly see if I can help make the defaults work better. See also OS confusion about default audio sink - pulse: https://askubuntu.com/questions/1231935/os-confusion-about-default- audio-sink-pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1938623/+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 1872287] [NEW] I'm getting CPU freezing issues.
Public bug reported: The bugs are related to CSGO, getting fps drops after few minutes of usage. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:23:27 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed nvidia, 430.50, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 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 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/1872287 Title: I'm getting CPU freezing issues. Status in xorg package in Ubuntu: New Bug description: The bugs are related to CSGO, getting fps drops after few minutes of usage. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:23:27 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed nvidia, 430.50, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0]
[Touch-packages] [Bug 1865254] [NEW] After fresh installation 19.10 on Dell vostro 15 3568 it is showing screen blinking when I try to unlock and locking with Super+L
Public bug reported: I am new to report such issues so I just don't know what to share here. though below is the kernel and syslog of the system. I having this issue with this model only as many of this model to test. Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Syslog:- Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 5603e0fd7930 i resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 5603e0fd7930 i resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4540 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4ed0 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4ed0 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 11:49:13 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-02-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=e4c9da5a-c5ed-4509-ac83-acf0ed89a193 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri:
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
I also faced the same issue and thanks to the Lumar's comment, workaround mentioned in the link worked for me too: https://dev.solus-project.com/T5224 -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1692001] [NEW] package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 2017050
Public bug reported: When I update using apt update, these errors started to come. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-common 2:7.4.1689-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 19 15:24:50 2017 DuplicateSignature: package:vim-common:2:7.4.1689-3ubuntu1.2 Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ... dpkg: error processing archive /var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 InstallationDate: Installed on 2017-02-01 (107 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: vim Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1692001 Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 Status in vim package in Ubuntu: New Bug description: When I update using apt update, these errors started to come. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-common 2:7.4.1689-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri May 19 15:24:50 2017 DuplicateSignature: package:vim-common:2:7.4.1689-3ubuntu1.2 Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ... dpkg: error processing archive /var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 InstallationDate: Installed on 2017-02-01 (107 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: vim Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1692001/+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 1642507] [NEW] Not internet after waking from suspend
Public bug reported: Release Information: Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety Package Information: network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status System Information: Dell XPS 15 9550 Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]) Problem Description: I have noticed the problem on both wired and wireless. Ever since upgrading to 16.10(from 16.04), the system loses internet after waking from suspend. Internet works fine after a reboot or when powering on normally. "service network-manager restart" fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 17 09:37:30 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (169 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.80.1 dev enx7cc3a187f0f2 proto static metric 100 default via 192.168.80.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.80.0/24 dev enx7cc3a187f0f2 proto kernel scope link src 192.168.80.209 metric 100 192.168.80.0/24 dev wlp2s0 proto kernel scope link src 192.168.80.225 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-28 (19 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enx7cc3a187f0f2 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 e6493319-b925-3b33-92a7-259922dccdaa /org/freedesktop/NetworkManager/ActiveConnection/1 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 whymusticry_fast 1 b51f9098-d053-45d7-ba42-97bf2e87bda2 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1642507 Title: Not internet after waking from suspend Status in network-manager package in Ubuntu: New Bug description: Release Information: Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety Package Information: network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status System Information: Dell XPS 15 9550 Wireless: Network controller: Broad com Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) Wired: Wired Ethernet via Apple USB Ethernet Adapter (ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277]) Problem Description: I have noticed the problem on both wired and wireless. Ever since upgrading to 16.10(from 16.04), the system loses internet after waking from suspend. Internet works fine after a reboot or when powering on normally. "service network-manager restart" fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 17 09:37:30 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-31 (169 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
[Touch-packages] [Bug 1569342] [NEW] Airplane Mode cannot be turned off
Public bug reported: My hp laptop has a rt3290 chipset which stopped working while I used ubuntu 15.10 although it works on Windows 10 which I dual boot. I bought a usb wifi with a rt2870 chipset, which worked out of the box with ubuntu 15.10 but has stopped working since I upgraded to 16.04. Also, the airplane mode in connection settings is fixed at on and cannot be turned off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Apr 13 05:28:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-11 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.109.250.1 dev eno1 proto static metric 100 10.109.0.0/16 dev eno1 proto kernel scope link src 10.109.141.50 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false WimaxEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 9d39a0f7-8bf2-4a7c-a64d-4cb5a359a51a 802-3-ethernet 1460505238 Wednesday 13 April 2016 05:23:58 AM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 yes eno1 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eno1 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 9d39a0f7-8bf2-4a7c-a64d-4cb5a359a51a /org/freedesktop/NetworkManager/ActiveConnection/0 wlo1 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- wlxc83a35ca4110 wifi unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1569342 Title: Airplane Mode cannot be turned off Status in network-manager package in Ubuntu: New Bug description: My hp laptop has a rt3290 chipset which stopped working while I used ubuntu 15.10 although it works on Windows 10 which I dual boot. I bought a usb wifi with a rt2870 chipset, which worked out of the box with ubuntu 15.10 but has stopped working since I upgraded to 16.04. Also, the airplane mode in connection settings is fixed at on and cannot be turned off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: i3 Date: Wed Apr 13 05:28:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-11 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) IpRoute: default via 10.109.250.1 dev eno1 proto static metric 100 10.109.0.0/16 dev eno1 proto kernel scope link src 10.109.141.50 metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false WimaxEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install)
