[Touch-packages] [Bug 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
Well my lid actions say that the computer should go to sleep, but it doesn't. I also noticed I'm missing a sleep.sh in /etc/acpi. -- 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/1840817 Title: System won't suspend when closing the lid of my laptop, just shuts down Status in systemd package in Ubuntu: New Bug description: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [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 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840817/+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 1838485] Re: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
[Expired for policykit-1 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: policykit-1 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1838485 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: Expired Bug description: I don't have Window. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 30 11:19:23 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-07-27 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1838485/+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 1844422] Re: WPA3-SAE support
above automated response is correct - it's three backported commits. There should be more before it's done though, so consider this "something to test things out". The network-manager UI does not yet have SAE / WPA3 personal support in this backport, and doesn't look like that's available upstream yet - at least not in the network-manager git. -- 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/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1844422] Re: WPA3-SAE support
The attachment "Backport of upstream support" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
> I'm using a manually reinstalled Ubuntu Bionic Actually it looks like I upgraded up to it from Artful. -- 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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in alsa-driver package in Ubuntu: New Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845810/+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 1845810] [NEW] [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
Public bug reported: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic 4.15.0-60.67 BAD: linux-image-4.15.0-62-generic 4.15.0-62.69 BAD: linux-image-4.15.0-64-generic 4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression-update -- 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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in alsa-driver package in Ubuntu: New Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through
[Touch-packages] [Bug 1844422] Re: WPA3-SAE support
On one side this fixes SAE / WPA3 personal support on the other, you still can't edit or update WPA3 connections in the GUI components. If you use nmtui or try connecting to WPA3 though, it works. (I've tested this) Consider upstream to be "nearing complete" I've been working on WPA3 support on some AP series so I very much can test this. Up until now I've been using manual settings on a custom compile of wpa_supplicant (etc). Attached is the backported patches (from networkmanager master, they're not even in any tags yet) I'm going to keep an eye on networkmanager development and follow this report. However I'd class support as "not yet ready". ** Patch added: "Backport of upstream support" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+attachment/5292389/+files/nm-sae-backport.patch -- 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/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1792167] Re: Display size detected incorrectly
Bug still present. In my multi-display setup a 40" display is reported as a 7" in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Expired Status in qtbase-opensource-src package in Ubuntu: Expired Bug description: My external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. It seems not related to the display server, compositor or window manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1845802] [NEW] Smeared top panel and hint tips on Plank and browser icon
Public bug reported: It would take more than one snapshot, but this all happens on Dell external monitor: 1. Top panel has blurred/smeared icons. 2. Hint tips on browser icons are also smeared. 3. Plank tips are smeared or blurry on some icons. Screenshot after exiting full screen (could not restore to full) and top panel was set to autohide and would not budge. https://justpaste.it/7rqzp Otherwise, everything is okay on laptop monitor itself. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Sep 28 13:23:08 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=64852f66-77ef-4b0f-b326-aec23cfe7db3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: CNU148133S dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: LQ168AW#ABA dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1845802 Title: Smeared top panel and hint tips on Plank and browser icon Status in xorg package in Ubuntu: New Bug description: It would take more than one snapshot, but this all happens on Dell external monitor: 1. Top panel has blurred/smeared icons. 2. Hint tips on browser icons are also smeared. 3. Plank tips are smeared or blurry on some icons. Screenshot after exiting full screen (could not restore to full) and top panel was set to autohide and would not budge. https://justpaste.it/7rqzp Otherwise, everything is okay on laptop monitor itself. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Sep 28 13:23:08 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=64852f66-77ef-4b0f-b326-aec23cfe7db3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: CNU148133S dmi.chassis.type: 10
[Touch-packages] [Bug 1844422] Re: WPA3-SAE support
** Summary changed: - WPA3-support + WPA3-SAE support -- 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/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1844422] Re: WPA3-support
** Description changed: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 + + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi- networks using WPA3. -- 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/1844422 Title: WPA3-support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
It's a real shutdown. Please check the current action on lid close. -- 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/1840817 Title: System won't suspend when closing the lid of my laptop, just shuts down Status in systemd package in Ubuntu: New Bug description: 1) Using Ubuntu MATE 18.04.3 LTS 2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17 3) I expected the laptop to suspend when i closed the lid 4)It just shut down even though in the logs it reports that it suspended ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.25 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Aug 20 17:36:30 2019 InstallationDate: Installed on 2019-08-15 (5 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X541SC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /lib/systemd/system/samba-ad-dc.service [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 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541SC.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541SC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X541SC dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840817/+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 1845801] [NEW] Trying to log in just takes me back to the login screen. Killing gnome-session-binary fixes it.
Public bug reported: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: Trying to log in just takes me back to the login screen. Killing gnome-session-binary fixes it. Status in xorg package in Ubuntu: New Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
[Touch-packages] [Bug 1844422] Re: WPA3-support
Indeed. 19.04 shipped with wpasupplicant 2.6, which had no support at all for WPA3, although network-manager 1.16 already started to support it. With 19.10 shipping wpasupplicant 2.9 and network-manager 1.20, there's just no excuse. I have WPA2+WPA3 mixed-mode deployed on my home network and all my connections are downgraded to WPA2. -- 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/1844422 Title: WPA3-support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1844422] Re: WPA3-support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1844422 Title: WPA3-support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1845797] Re: Microphone not detected Lenovo Yoga S940
** Tags added: disco ** Tags added: eoa ** Tags removed: eoa ** Tags added: eoan -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845797/+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 1845797] [NEW] Microphone not detected Lenovo Yoga S940
Public bug reported: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-09-28 18-25-03.png" https://bugs.launchpad.net/bugs/1845797/+attachment/5292290/+files/Screenshot%20from%202019-09-28%2018-25-03.png -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845797/+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 1845795] [NEW] authentication window got stuck over other windows
Public bug reported: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-09-28 18-16-35.png" https://bugs.launchpad.net/bugs/1845795/+attachment/5292289/+files/Screenshot%20from%202019-09-28%2018-16-35.png ** Description changed: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. + + Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 ** Package changed: pulseaudio (Ubuntu) => 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/1845795 Title: authentication window got stuck over other windows Status in Ubuntu: New Bug description: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845795/+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 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
*** This bug is a duplicate of bug 1617564 *** https://bugs.launchpad.net/bugs/1617564 ** This bug has been marked a duplicate of bug 1617564 [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1768752 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in account-plugins package in Ubuntu: New Status in kaccounts-providers package in Ubuntu: New Bug description: apart from kde config telepathy accounts package install error, I even cant update ubuntu base as i try every time the results is broken file. then it asks me to report the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 29 07:05:33 2018 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2018-04-26 (6 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+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 1845793] [NEW] Since upgrade to ubuntu 19.10, dhclient doesn't respect the "supersede domain-name-servers" in dhclient.conf
Public bug reported:
dnsleaktest.com shows my ISP servers instead of the configured ones in
dnscrypt-proxy. When i checked in network settings it was written the
DNS for my router, but there is still this line below inside
/etc/dhcp/dhclient.conf. Also, ifconfig shows that the interface name is
still the same as below.
interface "wlp3s0" {
supersede domain-name-servers 127.0.0.1;
}
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: isc-dhcp-client 4.4.1-2ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 28 19:40:14 2019
DhclientLeases:
InstallationDate: Installed on 2019-07-23 (66 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago)
mtime.conffile..etc.dhcp.dhclient.conf: 2019-08-31T22:54:40.376662
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1845793
Title:
Since upgrade to ubuntu 19.10, dhclient doesn't respect the "supersede
domain-name-servers" in dhclient.conf
Status in isc-dhcp package in Ubuntu:
New
Bug description:
dnsleaktest.com shows my ISP servers instead of the configured ones in
dnscrypt-proxy. When i checked in network settings it was written the
DNS for my router, but there is still this line below inside
/etc/dhcp/dhclient.conf. Also, ifconfig shows that the interface name
is still the same as below.
interface "wlp3s0" {
supersede domain-name-servers 127.0.0.1;
}
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: isc-dhcp-client 4.4.1-2ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 28 19:40:14 2019
DhclientLeases:
InstallationDate: Installed on 2019-07-23 (66 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago)
mtime.conffile..etc.dhcp.dhclient.conf: 2019-08-31T22:54:40.376662
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1845793/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
I'm wondering why this has not been fixed after such a long time. It can at
least be improved easily.
If the Adwaita theme works (which it does in may case, too), then it is (at
least partly) a theme issue.
In fact, some defaults seem to be missing in the Ambiance and Radiance themes:
By setting a default for the text background color in the following
file, most problems (gnome-calculator, gedit) are resolved for me:
/usr/share/themes/Ambiance/gtk-3.20/gtk.css:
textview text {
background-color: white; }
@import url("gtk-main.css");
However:
* Some problems remain., e.g. emacs scrollbar background color broken, too.
The following solves that partly, too, but not completely:
scrollbar {
background-color: white; }
* If you change such system files, they will get reset with some later system
updates.
(dpkg-divert can help to prevent such resetting/updating of files)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1760818
Title:
gedit and gnome-calculator transparency/graphics corruption issue when
GTK_IM_MODULE=xim is set
Status in gtk+3.0 package in Ubuntu:
Confirmed
Status in im-config package in Ubuntu:
Confirmed
Bug description:
In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
suffer from a graphics issue where parts of their windows hold parts
of wallpaper or other windows' contents as background.
See attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180328-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 3 09:12:31 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1760818/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
** Also affects: charm-keepalived
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in Keepalived Charm:
New
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Triaged
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in heartbeat source package in Bionic:
Triaged
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Confirmed
Status in heartbeat source package in Disco:
Triaged
Status in keepalived source package in Disco:
Confirmed
Status in systemd source package in Disco:
Confirmed
Status in heartbeat source package in Eoan:
Triaged
Status in keepalived source package in Eoan:
In Progress
Status in systemd source package in Eoan:
In Progress
Bug description:
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection {
group {
wan
lan
phone
}
vrrp_instance wan {
state MASTER
interface eth2
virtual_router_id 77
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass BlahBlah
}
virtual_ipaddress {
12.13.14.20
}
}
vrrp_instance lan {
state MASTER
interface eth3
virtual_router_id 78
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass MoreBlah
}
virtual_ipaddress {
10.22.11.13/24
}
}
vrrp_instance phone {
state MASTER
interface eth4
virtual_router_id 79
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass MostBlah
}
virtual_ipaddress {
10.22.14.3/24
}
}
At boot the affected interfaces have:
5: eth4: mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff
inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4
valid_lft forever preferred_lft forever
inet 10.22.14.3/24 scope global secondary eth4
valid_lft forever preferred_lft forever
inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link
valid_lft forever preferred_lft forever
7: eth3: mtu
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Thanks Rafael/Christian,
I see that all those patches are in 243 and Eoan is currently on 242
(albeit -6 but i dont think any are already backported) so we'll need to
get this backported all the way down to Bionic.
max@power:~/git/systemd$ _c=( 7da377e 95355a2 db51778 c98d78d 1e49885 )
max@power:~/git/systemd$ for c in ${_c[@]}; do git tag --contains $c| egrep -v
"\-rc"; done| sort -u
v243
Do we have a feel for if/when the keepalived fix(es) will be
backportable to B (1.x) as well? Since those fixes already exist in
Discco (2.0.10) it might be easier to start with those?
I will add the charm-keepalived to this LP since it will need support
for the networkd/netplan fix once that is available.
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Triaged
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in heartbeat source package in Bionic:
Triaged
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Confirmed
Status in heartbeat source package in Disco:
Triaged
Status in keepalived source package in Disco:
Confirmed
Status in systemd source package in Disco:
Confirmed
Status in heartbeat source package in Eoan:
Triaged
Status in keepalived source package in Eoan:
In Progress
Status in systemd source package in Eoan:
In Progress
Bug description:
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection {
group {
wan
lan
phone
}
vrrp_instance wan {
state MASTER
interface eth2
virtual_router_id 77
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass BlahBlah
}
virtual_ipaddress {
12.13.14.20
}
}
vrrp_instance lan {
state MASTER
interface eth3
virtual_router_id 78
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass MoreBlah
}
virtual_ipaddress {
10.22.11.13/24
}
}
vrrp_instance phone {
state MASTER
interface eth4
virtual_router_id 79
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
[Touch-packages] [Bug 1845775] [NEW] Xorg freeze
Public bug reported: Reproduced on VmWare virtual machine. Ubuntu" Desktop session worked after fresh install of Eoan 19.10 beta install + fresh update. Added Italian language and set it system-wide Restarted Ubuntu Logging with "Ubuntu": session starts but mouse & keyboard do not respond --> have to hard reset the machine. Logging with "Ubuntu Wayland": session starts and properly work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 03:34:25 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=fb519e2f-a6b3-4c97-a72c-ffbaec2246bb ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze ubuntu wayland-session -- 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/1845775 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Reproduced on VmWare virtual machine. Ubuntu" Desktop session worked after fresh install of Eoan 19.10 beta install + fresh update. Added Italian language and set it system-wide Restarted Ubuntu Logging with "Ubuntu": session starts but mouse & keyboard do not respond --> have to hard reset the machine. Logging with "Ubuntu Wayland": session starts and properly work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 03:34:25 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
[Touch-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time
hi guys, on ubuntu bionic 18.04 amd64 I still can't install libsdl2-dev:i386 and libsdl2-dev:amd64 because of that libxkbcommon- dev:i386 and libxkbcommon-dev:amd64 can't coexist. Is there any progress so far? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Committed Bug description: [Impact] libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the package isn't properly multi-archified in bionic [Test case] apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64 should succeed [Regression potential] not really -- Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done 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: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: Fix Committed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1609750] Re: Audio not working on Acer Chromebook R11
thanks for the feedback On Thu, Sep 26, 2019, 09:55 daniel primo stuart <1609...@bugs.launchpad.net> wrote: > Kernel needs this patch for maxim98090 to work on cyan and some baytrail > chromebooks: > > https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f > > As it didn't make to 5.3 on time, would be nice if it were backported by > ubuntu devs > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1803810). > https://bugs.launchpad.net/bugs/1609750 > > Title: > Audio not working on Acer Chromebook R11 > > Status in linux: > Confirmed > Status in linux package in Ubuntu: > In Progress > Status in pulseaudio package in Ubuntu: > Invalid > > Bug description: > Audio is not working at all on Acer Chromebook R11 (codename CYAN). > It's a Intel Braswell platform. snd_hda_intel messages seem normal, > but Pulseaudio does not detect sound hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: pulseaudio 1:9.0-1.1ubuntu1 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > Uname: Linux 4.4.0-33-generic x86_64 > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Thu Aug 4 14:12:03 2016 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > SourcePackage: pulseaudio > Symptom: audio > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > --- > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.10 > HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Cyan > Package: linux-image-4.4.0-33-generic 4.4.0-33.52 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic > root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.4.0-33-generic N/A >linux-backports-modules-4.4.0-33-generic N/A >linux-firmware1.159 > Tags: yakkety > Uname: Linux 4.4.0-33-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions > -- 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/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support Status: Confirmed => In Progress -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: In Progress Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down
Here's the logs: -- Logs begin at Sat 2019-09-14 17:41:26 CEST, end at Sat 2019-09-28 10:33:23 CEST. -- Sep 27 18:06:25 nathsom-X541SC kernel: microcode: microcode updated early to revision 0x411, date = 2019-04-23 Sep 27 18:06:25 nathsom-X541SC kernel: Linux version 5.0.0-29-generic (buildd@lgw01-amd64-039) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 (Ubuntu 5.0.0-29.31~18.04.1-generic 5. Sep 27 18:06:25 nathsom-X541SC kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=db339006-ae4c-4bfd-af8e-26d7d90b9e6f ro quiet splash vt.handoff=1 Sep 27 18:06:25 nathsom-X541SC kernel: KERNEL supported cpus: Sep 27 18:06:25 nathsom-X541SC kernel: Intel GenuineIntel Sep 27 18:06:25 nathsom-X541SC kernel: AMD AuthenticAMD Sep 27 18:06:25 nathsom-X541SC kernel: Hygon HygonGenuine Sep 27 18:06:25 nathsom-X541SC kernel: Centaur CentaurHauls Sep 27 18:06:25 nathsom-X541SC kernel: x86/fpu: x87 FPU will use FXSAVE Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-provided physical RAM map: Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x-0x0003efff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x0003f000-0x0003] ACPI NVS Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x0004-0x0009dfff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x0009e000-0x0009] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x0010-0x1eff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x1f00-0x201f] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x2020-0x79904fff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x79905000-0x79982fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x79983000-0x7a097fff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x7a098000-0x7ae29fff] ACPI NVS Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x7ae2a000-0x7b8f0fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x7b8f1000-0x7baf8fff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x7baf9000-0x7bff6fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x7bff7000-0x7bff] usable Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xe000-0xefff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfea0-0xfeaf] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfec0-0xfec00fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfed01000-0xfed01fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfed03000-0xfed03fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfed06000-0xfed06fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfed08000-0xfed09fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfed1c000-0xfed1cfff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfed8-0xfedb] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xfee0-0xfee00fff] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0xffa0-0x] reserved Sep 27 18:06:25 nathsom-X541SC kernel: BIOS-e820: [mem 0x0001-0x00017fff] usable Sep 27 18:06:25 nathsom-X541SC kernel: NX (Execute Disable) protection: active Sep 27 18:06:25 nathsom-X541SC kernel: e820: update [mem 0x769de018-0x769ee057] usable ==> usable Sep 27 18:06:25 nathsom-X541SC kernel: e820: update [mem 0x769de018-0x769ee057] usable ==> usable Sep 27 18:06:25 nathsom-X541SC kernel: e820: update [mem 0x769c6018-0x769ddc57] usable ==> usable Sep 27 18:06:25 nathsom-X541SC kernel: e820: update [mem 0x769c6018-0x769ddc57] usable ==> usable Sep 27 18:06:25 nathsom-X541SC kernel: e820: update [mem 0x769b9018-0x769c5857] usable ==> usable Sep 27 18:06:25 nathsom-X541SC kernel: e820: update [mem 0x769b9018-0x769c5857] usable ==> usable Sep 27 18:06:25 nathsom-X541SC kernel: extended physical RAM map: Sep 27 18:06:25 nathsom-X541SC kernel: reserve setup_data: [mem 0x-0x0003efff] usable Sep 27 18:06:25 nathsom-X541SC kernel: reserve setup_data: [mem 0x0003f000-0x0003] ACPI NVS Sep 27 18:06:25 nathsom-X541SC kernel: reserve setup_data: [mem 0x0004-0x0009dfff] usable Sep 27 18:06:25 nathsom-X541SC kernel: reserve setup_data: [mem 0x0009e000-0x0009] reserved Sep 27 18:06:25 nathsom-X541SC kernel: reserve
