[Touch-packages] [Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
No problem. The bug will automatically close after 60 days of no comments. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mes
[Touch-packages] [Bug 1878635] Re: Intel Titan Ridge TB3 USB Controller prevents system from suspending
** Package changed: powermgmt-base (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1878635 Title: Intel Titan Ridge TB3 USB Controller prevents system from suspending Status in linux package in Ubuntu: Confirmed Bug description: The dmesg log states the following: PM: Device :0f:00.0 failed to suspend async: error -110 When checking lspci this points to the following device: 0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) which is the integrated Thunderbolt 3 Controller of the ITX Motherboard. I will still try suspending without a Thunderbolt 3 Dock attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spyfly 2424 F pulseaudio /dev/snd/controlC3: spyfly 2424 F pulseaudio /dev/snd/controlC1: spyfly 2424 F pulseaudio /dev/snd/controlC2: spyfly 2424 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 17:09:55 2020 HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2 InstallationDate: Installed on 2018-09-06 (616 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.78 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878635/+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 1878782] Re: Bluetooth is on but scanned devices are not showing.
While the problem is happening please run: rfkill > rfkill.txt in a terminal and then attach the resulting file here. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1878782 Title: Bluetooth is on but scanned devices are not showing. Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth in spite of being switched on, shows the same image as when it is off in the paired devices menu. I cannot access my paired devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dashtrox 1582 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 13:48:16 2020 InstallationDate: Installed on 2020-05-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1TCN27WW(V2.08) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1TCN27WW(V2.08):bd07/06/2018:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK: dmi.product.family: ideapad 110-15ISK dmi.product.name: 80UD dmi.product.sku: LENOVO_MT_80UD_BU_idea_FM_ideapad 110-15ISK dmi.product.version: Lenovo ideapad 110-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878782/+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 1878587] Re: pk-client-error-quarl could not get lock when selecting driver from synaptic
Thank you for your bug report, indeed that's synaptic taking the lock and including the option so the problem needs to be resolved from there ** Package changed: software-properties (Ubuntu) => synaptic (Ubuntu) ** Changed in: synaptic (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1878587 Title: pk-client-error-quarl could not get lock when selecting driver from synaptic Status in synaptic package in Ubuntu: New Bug description: Steps to reproduce (Ubuntu 20.04, synaptic 0.84.6ubuntu5, software-properties-gtk 0.98.9) 1. Open synaptic 2. click in "parameters" menu, then "repositories". This will open a "Software and update" window 3. click on "additional drivers" tab 4. select a new driver (example : I have nvidia 435 installed, I select nvidia 440) 5. click apply Expected behaviour : the selected driver is installed Actual behaviour: you get an error window with message: "pk-client-error-quark: E: could not get lock /var/lib/dpkg/lock-front-end. It is held by process 9246 (synaptic)" Workaround: launch "software update" directly without synaptic I understand that synaptic must be closed in order to let another software updating process operate. But this software update has been initiated from synaptic and I cannot close synaptic when software update is opened. It is opened like a modal window... Ithink either this feature should be removed from synaptic or avtrick must be found to have it releasing the lock as long as the "software update" window it has triggered is opened; or maybe synaptic and software-update-gtk could share the lock in this situation ? For now it is impossible to install additional driver if you launched it from synaptic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 14 11:34:44 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-05-12 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=fr_FR.UTF-8 PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-05-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1878587/+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 1876882] Re: Backport packages for 18.04.5 HWE stack
right, I think the default driver should still be i965 for the backport, as TGL support isn't a priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876882 Title: Backport packages for 18.04.5 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-10 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-10 source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-10: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 20.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1879237] [NEW] Lines appear on Desktop when moving mouse around.
You have been subscribed to a public bug: Ubuntu 20.04 LTS Release:20.04 It is not related to Xorg. After upgrade to 20.04. Not with any previous version. It happens only on the Desktop, never in any other programs. Lines stay on screen between 1 and 2 seconds. It happens on my laptop hp probook 450-G1 (under wayland), dell inspiron 7773 (under wayland) and pc built box (GPU radeon under Xorg). Posted the issue on Ask Ubuntu, but no answer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 06:47:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3811] InstallationDate: Installed on 2020-04-24 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=97a84f93-4387-4b54-bdc6-7e20b816ecb9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu -- Lines appear on Desktop when moving mouse around. https://bugs.launchpad.net/bugs/1879237 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878970] Re: 3 times the system crashed and I had to do a hard reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Ubuntu 20.04 - AOC HDMI Monitor + 3 times the system crashed and I had to do a hard reboot ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1878970 Title: 3 times the system crashed and I had to do a hard reboot Status in xorg-server package in Ubuntu: Incomplete Bug description: This is a fresh install of Ubuntu 20.04 on a Dell Inspiron 5590. I've just bought a monitor AOC 22B1H and I'm using as a second monitor plugged in HDMI. For 3 times the system crashed and I had to do a hard reboot for no reason apparently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 15:02:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:0957] Subsystem: Dell GP108M [GeForce MX250] [1028:0957] InstallationDate: Installed on 2020-05-04 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 5590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=1a490b05-de14-4d4f-8795-c0fe269ac8cb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0XRXN9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/15/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878970/+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 1878951] Re: [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re-enabled
** Summary changed: - External monitor won't reconnect after reattaching HDMI cable + [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re-enabled ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: multimonitor nvidia ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided => Low ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Low -- 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/1878951 Title: [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re- enabled Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Steps to reproduce: 1. Successfully connect AOC u2879vf external display by attaching HDMI cable 2. Remove the cable, output switches to the built-in display and external display goes black 3. Reconnect the HDMI cable again What is expected: The external screen should display the image (as in step 1) What happened instead: The system thinks the display is connected (see the xrandr output), but the external display is still black (no signal). The clumsy workaround is to use Super+P to switch to "built-in display only" and then back to "joint". After that, the external monitor comes back. xrandr outputs: Step 1 Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 1920x2160 59.99 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 connected 1920x1080+909+2160 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) Step 2 Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) Step 3 Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 1920x2160 59.99 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 connected 1920x1080+1097+2160 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May
[Touch-packages] [Bug 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
Workaround: echo "Set disable_coredump false" | sudo tee -a /etc/sudo.conf ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container Status in lxd package in Ubuntu: New Status in sudo package in Ubuntu: Confirmed Bug description: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: Installed: 1.8.31-1ubuntu1 Candidate: 1.8.31-1ubuntu1 Version table: *** 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status This is not an issue on Bionic: bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1.2 Candidate: 1.8.21p2-3ubuntu1.2 Version table: *** 1.8.21p2-3ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.8.21p2-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages From the redhat bug, the described workaround does clear these messages up: # set disable_coredump false Once I've done that, the error messages go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1868456/+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 1873476] Re: incorrect status intel 8265 / 8275
*** This bug is a duplicate of bug 1859308 *** https://bugs.launchpad.net/bugs/1859308 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1859308, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1859308 software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1873476 Title: incorrect status intel 8265 / 8275 Status in software-properties package in Ubuntu: New Bug description: software-properties reporting I have not working Intel 8265 / 8275 device it offer options: This device not working. grayed 1) using iwlwifi 2) continue using manually installed drivers. grayed 3) Do not use device But device working fine without any manually installed drivers. I'm using original Ubuntu 19.10 installation. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 17:52:46 2020 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1873476/+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 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
Container management seems to be the source of the error, sudo just suppresses it. So a potential fix is in LXD or related packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container Status in lxd package in Ubuntu: New Status in sudo package in Ubuntu: Confirmed Bug description: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: Installed: 1.8.31-1ubuntu1 Candidate: 1.8.31-1ubuntu1 Version table: *** 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status This is not an issue on Bionic: bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1.2 Candidate: 1.8.21p2-3ubuntu1.2 Version table: *** 1.8.21p2-3ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.8.21p2-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages From the redhat bug, the described workaround does clear these messages up: # set disable_coredump false Once I've done that, the error messages go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1868456/+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 1876518] Re: Gtk.Clipboard set_text() not working
Thanks for reporting it to upstream!
** Changed in: pygobject (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1876518
Title:
Gtk.Clipboard set_text() not working
Status in pygobject:
Unknown
Status in pygobject package in Ubuntu:
Triaged
Bug description:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1876518/+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 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Hi, I think this is a disappointing papercut and a long lasting issue. I'm discussing with gtk devs if this behaviour is intended or is a bug. -- 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/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 1879237] Re: Lines appear on Desktop when moving mouse around.
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879237 Title: Lines appear on Desktop when moving mouse around. Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 LTS Release: 20.04 It is not related to Xorg. After upgrade to 20.04. Not with any previous version. It happens only on the Desktop, never in any other programs. Lines stay on screen between 1 and 2 seconds. It happens on my laptop hp probook 450-G1 (under wayland), dell inspiron 7773 (under wayland) and pc built box (GPU radeon under Xorg). Posted the issue on Ask Ubuntu, but no answer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 06:47:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3811] InstallationDate: Installed on 2020-04-24 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=97a84f93-4387-4b54-bdc6-7e20b816ecb9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879237/+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 1877023] [NEW] Unhandled exception in check_ignored()
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
Hi,
I have found a security issue on apport 2.20.11 and earlier.
## Vulnerability
apport 2.20.11 and earlier have an unhandled exception vulnerability during
parsing apport-ignore.xml.
An attacker can cause a denial of service (i.e., application crash) via a
crafted apport-ignore.xml file.
## Description
Reports can be suppressed by blacklisting in apport-ignore.xml.
This is an example of apport-ignore.xml
Unfortunately, it may cause an unhandled exception when 'mtime'
attribute is specified as a string value, not a number like this.
It may disrupt apport service and allow an attacker to potentially
enable a denial of service via local access.
The flaw lies in improper exception handling of 'mtime' attribute in
apport-ignore.xml (see
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).
## Log
Here is /var/log/apport.log when the above exception occurs.
ERROR: apport (pid 25904) Tue May 5 18:38:21 2020: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 629, in
if info.check_ignored():
File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in
check_ignored
if float(ignore.getAttribute('mtime')) >= cur_mtime:
ValueError: could not convert string to float: 'string'
Sincerely,
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
Unhandled exception in check_ignored()
https://bugs.launchpad.net/bugs/1877023
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to apport in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877023] Re: Unhandled exception in check_ignored()
** Project changed: apport => apport (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1877023
Title:
Unhandled exception in check_ignored()
Status in apport package in Ubuntu:
New
Bug description:
Hi,
I have found a security issue on apport 2.20.11 and earlier.
## Vulnerability
apport 2.20.11 and earlier have an unhandled exception vulnerability during
parsing apport-ignore.xml.
An attacker can cause a denial of service (i.e., application crash) via a
crafted apport-ignore.xml file.
## Description
Reports can be suppressed by blacklisting in apport-ignore.xml.
This is an example of apport-ignore.xml
Unfortunately, it may cause an unhandled exception when 'mtime'
attribute is specified as a string value, not a number like this.
It may disrupt apport service and allow an attacker to potentially
enable a denial of service via local access.
The flaw lies in improper exception handling of 'mtime' attribute in
apport-ignore.xml (see
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).
## Log
Here is /var/log/apport.log when the above exception occurs.
ERROR: apport (pid 25904) Tue May 5 18:38:21 2020: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 629, in
if info.check_ignored():
File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in
check_ignored
if float(ignore.getAttribute('mtime')) >= cur_mtime:
ValueError: could not convert string to float: 'string'
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1877023/+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 1878707] Re: Openconnect provided DNS servers are not read by NetworkManager
Thanks, it could also be useful to report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ but changing to new again, it should have enough information for someone to investigate ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1878707 Title: Openconnect provided DNS servers are not read by NetworkManager Status in network-manager package in Ubuntu: New Bug description: If I connect using openconnect comamnd line, all works fine! If I add connection to NetworkManager, when I connect, I loose dns, and with that, all connectivity! PS: worked without issue on 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 metric 100 192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 600 Package: network-manager 1.22.10-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2020-05-14T20:00:14.210715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
sorry, working on verifying it, got distracted by other stuff. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 269441] Re: Trash always full
** Changed in: glib2.0 (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/269441 Title: Trash always full Status in Ubuntu MATE: New Status in glib2.0 package in Ubuntu: Confirmed Bug description: I've seen other users having problems with that the trash appears empty even though it isn't. I have the opposite problem: my trash icon on the desktop always appears full, even if empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+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 1879206] Re: cups hplip not install printer
thank you for your bug report, what's the output of $ ls -l /etc/cups/ppd/DeskJet-3630.ppd $ ls -ld /etc/cups/ppd $ ls -ld /etc/cups the log suggests the ppd file is not accessible to the process -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879193] Re: folder with applications freezes
Thank you for your bug report, could you give some extra details on what you are doing? Is that dragging icons from the GNOME overview to applications folders created there? Does it happen every time even on the first one? Could you maybe take a video showing the issue? ** Package changed: xorg (Ubuntu) => gnome-shell (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/1879193 Title: folder with applications freezes Status in gnome-shell package in Ubuntu: New Bug description: when placing applications in the folder the screen freezes, when removing the folder, the screen freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879193/+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 1877023] Re: Unhandled exception in check_ignored()
The attachment "unhandled-XML-exception.patch" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1877023
Title:
Unhandled exception in check_ignored()
Status in apport package in Ubuntu:
New
Bug description:
Hi,
I have found a security issue on apport 2.20.11 and earlier.
## Vulnerability
apport 2.20.11 and earlier have an unhandled exception vulnerability during
parsing apport-ignore.xml.
An attacker can cause a denial of service (i.e., application crash) via a
crafted apport-ignore.xml file.
## Description
Reports can be suppressed by blacklisting in apport-ignore.xml.
This is an example of apport-ignore.xml
Unfortunately, it may cause an unhandled exception when 'mtime'
attribute is specified as a string value, not a number like this.
It may disrupt apport service and allow an attacker to potentially
enable a denial of service via local access.
The flaw lies in improper exception handling of 'mtime' attribute in
apport-ignore.xml (see
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).
## Log
Here is /var/log/apport.log when the above exception occurs.
ERROR: apport (pid 25904) Tue May 5 18:38:21 2020: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 629, in
if info.check_ignored():
File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in
check_ignored
if float(ignore.getAttribute('mtime')) >= cur_mtime:
ValueError: could not convert string to float: 'string'
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1877023/+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 1879007] Re: Xorg freeze
1. In case the freeze was a crash please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 2. Your system log has one unusual thing in it: bluetoothd is running out of files. If that problem was system-wide then it might theoretically hang Xorg too. Please run this command to find out which process ID is using the most file descriptors: sudo grep FDSize /proc/*/status and then find out the name of the process(es) with the most file descriptors. 3. Try stopping the program 'popcorntime' in case that's using too many resources per above. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879007 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I first did a clean install of Ubuntu 20.04. The system got frequently frozen at random times 4-5 times a day and mostly every time when it was on charging and I tried to boot. I was using the nouveau display driver instead of the Nvidia driver. I did a clean install again and the same thing happened. I upgraded to Nvidia drivers with Intel GPU PRIME profile (earlier I hadn't performed key management so I guess they were not being used properly, but this time I did). The system didn't freeze for 2 days. This time too it was plugged into power and I was watching a video when it just froze. Mouse and keyboard became irresponsive(like before). I couldn't perform any magic sysreq so I had to force reboot by pressing the power key. It has been happening every 2-3 days since that. My kdump crash logs are empty. Everytime the system froze the system has been plugged into power(or I couldn't recall if the system froze otherwise). It gets very irritating. Please help. Release : Ubuntu 20.04 LTS Xorg Package version : 1:7.7+19ubuntu14 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 03:40:43 2020 DistUpgraded: 2020-04-26 15:14:05,561 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0923] Subsystem: Dell GP107M [GeForce GTX 1050 3 GB Max-Q] [1028:0923] InstallationDate: Installed on 2020-04-26 (19 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 002: ID 0c45:671b Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7591 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c933ad76-6d7d-4174-97aa-0c543f666e94 ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-26 (19 days ago) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1
[Touch-packages] [Bug 1879237] Re: Lines appear on Desktop when moving mouse around.
*** This bug is a duplicate of bug 1874856 *** https://bugs.launchpad.net/bugs/1874856 Bug 1874856 reports the same issue so I have generalized that. ** This bug has been marked a duplicate of bug 1874856 Unwanted mouse trail -- 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/1879237 Title: Lines appear on Desktop when moving mouse around. Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 LTS Release: 20.04 It is not related to Xorg. After upgrade to 20.04. Not with any previous version. It happens only on the Desktop, never in any other programs. Lines stay on screen between 1 and 2 seconds. It happens on my laptop hp probook 450-G1 (under wayland), dell inspiron 7773 (under wayland) and pc built box (GPU radeon under Xorg). Posted the issue on Ask Ubuntu, but no answer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 06:47:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3811] InstallationDate: Installed on 2020-04-24 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=97a84f93-4387-4b54-bdc6-7e20b816ecb9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879237/+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 1879010] Re: Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink
1. Please tell us the model of speaker you are having trouble with. 2. Please confirm that you can select higher quality mode in Settings, and that it works. ** Tags added: a2dp ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1879010 Title: Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink Status in bluez package in Ubuntu: Incomplete Bug description: This seems identical to this bug: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was suggested to open a new bug as the other one was closed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 16:13:24 2020 InstallationDate: Installed on 2020-05-06 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 54:8D:5A:D8:BA:43 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1126282 acl:178 sco:0 events:156624 errors:0 TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879010/+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 1879206] Re: cups hplip not install printer
No one driver work ~$ ls -l /etc/cups/ppd/DeskJet-3630.ppd ls: impossibile accedere a '/etc/cups/ppd/DeskJet-3630.ppd': File o directory non esistente ~$ ls -ld /etc/cups/ppd drwxr-xr-x 2 root lp 4096 mag 18 10:47 /etc/cups/ppd :~$ ls -ld /etc/cups drwxr-xr-x 5 root lp 4096 mag 18 10:50 /etc/cups ~$ ls -l /etc/cups/ppd/HP_DeskJet_3630_series.ppd.O -rw-r- 1 root lp 31205 mag 18 10:46 /etc/cups/ppd/HP_DeskJet_3630_series.ppd.O ** Attachment added: "Cups180520.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5373304/+files/Cups180520.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879042] Re: [radeon] Xorg high CPU usage and stuttering on ubuntu 20.04
Please run 'top' in a terminal to confirm it is the 'Xorg' process using the most CPU. ** Summary changed: - Xorg high CPU usage and stuttering on ubuntu 20.04 + [radeon] Xorg high CPU usage and stuttering on ubuntu 20.04 ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879042 Title: [radeon] Xorg high CPU usage and stuttering on ubuntu 20.04 Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: After upgrading Xubuntu from 19.10 to 20.04, some window operations (e.g. bringing one to foreground) can take an unusually long time (tenths of second, enough to compromise the general responsiveness of the system). Even switching from one terminal window to another causes a 80-90% CPU spike due to Xorg. (Tested with xfce4-terminal as well as rxvt.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat May 16 11:12:32 2020 DistUpgraded: 2020-05-09 17:20:01,127 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4290] [1002:9714] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS880 [Radeon HD 4290] [1043:8454] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=7ac7906b-f137-4adf-9de3-2ec128242354 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (6 days ago) dmi.bios.date: 04/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/13/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-10-10T22:39:42.917279 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879042/+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 1879039] Re: [prl_vid] Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Xorg crash + [prl_vid] Xorg crash ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879039 Title: [prl_vid] Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: After Firefox crushes couldnt open any browser, no Firefox nor Chromium and I had to restart the OS. Ubuntu 19.10 is a guest OS on Parallels 15 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat May 16 12:17:36 2020 DistUpgraded: 2020-05-09 07:53:36,319 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: parallels-tools, 15.1.4.47270, 4.15.0-100-generic, x86_64: installed parallels-tools, 15.1.4.47270, 5.3.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 [VGA controller]) Subsystem: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:0400] InstallationDate: Installed on 2018-08-10 (644 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Parallels Software International Inc. Parallels Virtual Platform MonitorsUser.xml: Virtual1unknownunknownunknown144090059.988003001yes ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=b214da3c-eaae-4adf-bfcc-c64b050618e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2020-05-09 (7 days ago) dmi.bios.date: 04/13/2020 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 15.1.4 (47270) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 9 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr15.1.4(47270):bd04/13/2020:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct9:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879039/+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/ListH
[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] - 1. Install server with subiquity to VM + 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1879090] Re: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set
Thank you for your bug report, why do you expect those to be set? Does it create any visible issue? ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1879090 Title: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set Status in lightdm package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+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 1879054] Re: No sound after 20.04 update with timidity installed
*** This bug is a duplicate of bug 1793640 *** https://bugs.launchpad.net/bugs/1793640 ** Summary changed: - No sound after 20.04 update + No sound after 20.04 update with timidity installed ** Package changed: pulseaudio (Ubuntu) => timidity (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/1879054 Title: No sound after 20.04 update with timidity installed Status in timidity package in Ubuntu: New Bug description: After update from 18.04 to 20.04 sound stopped working. KDE does not display Xonar sound card at all. $ aplay /usr/share/sounds/alsa/Front_Center.wav does not make any sound Alsamixer displays Xonar set at full volume but changing anything there does not seem to have any effect. Moving/deleting the pulse config ( ~/.config/pulse/ ) and restarting machine did not have any effect. Running: $ sudo alsa force-reload fixes the issue (until restart sound is back, and is displayed properly in KDE) (data arecord and cards display same data before and after restart) $ arecord -l Lista CAPTURE urządzeń karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 $ cat /proc/asound/cards 0 [DX ]: AV200 - Xonar DX Asus Virtuoso 100 at 0xd000, irq 31 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfe96 irq 67 $ lspci | grep -i audio 21:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio] 23:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] (build in motherboard soundcard is disabled in BIOS) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nait 5242 F pulseaudio /dev/snd/controlC1: nait 5242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 16 14:54:07 2020 InstallationDate: Installed on 2018-11-11 (552 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago) dmi.bios.date: 09/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd09/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1879054/+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 1879044] Re: gnome-shell restarts due to bluetooth disconnection
I've never seen that before; Xorg says WH-1000XM3 is a keyboard device. Which might be relevant. But also... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879044 Title: gnome-shell restarts due to bluetooth disconnection Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am logged in an X session with gnome. Just after logging, I start a Sony Bluetooth headphones (WH-1000XM3). After they connect (and they work), I switch them off (using the switch in the headphones). < 3 seconds after disconnections, the gnome-session crashes (and restarts). If I do this in Wayland, since the server does not seem to support restarts, I am logged out of the session and the laptop returns to the login screen. Best, Manuel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 11:23:01 2020 DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-03-26 (416 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879044/+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 1879075] Re: Bluetooth sound card not detected.
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1879075 Title: Bluetooth sound card not detected. Status in linux package in Ubuntu: New Bug description: not connecting to my Bluetooth headphones. same problem on my desktop computor. all worked ok with 18.04 .sometimes it will connect but after a few seconds it will disconnect, if i remove the device, and then add it, i can get it to connect, but YouTube video stalls with no sound, if i disconnect the headphones, the video plays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 1501 F pulseaudio /dev/snd/controlC0: chris 1501 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 16 17:06:19 2020 InstallationDate: Installed on 2020-05-04 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879075/+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 1879237] Re: Lines appear on Desktop when moving mouse around.
*** This bug is a duplicate of bug 1874856 *** https://bugs.launchpad.net/bugs/1874856 Thank you! And not only with nvidia but with amdgpu as you mentionned. Thaks again, Yves On 2020-05-18 10:40, Daniel van Vugt wrote: > *** This bug is a duplicate of bug 1874856 *** > https://bugs.launchpad.net/bugs/1874856 > > Bug 1874856 reports the same issue so I have generalized that. > > ** This bug has been marked a duplicate of bug 1874856 > Unwanted mouse trail > -- 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/1879237 Title: Lines appear on Desktop when moving mouse around. Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 LTS Release: 20.04 It is not related to Xorg. After upgrade to 20.04. Not with any previous version. It happens only on the Desktop, never in any other programs. Lines stay on screen between 1 and 2 seconds. It happens on my laptop hp probook 450-G1 (under wayland), dell inspiron 7773 (under wayland) and pc built box (GPU radeon under Xorg). Posted the issue on Ask Ubuntu, but no answer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 06:47:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3811] InstallationDate: Installed on 2020-04-24 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=97a84f93-4387-4b54-bdc6-7e20b816ecb9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879237/+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 1879076] Re: Xorg freeze
In case the freeze is caused by a crash, please start by following these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: nvidia -- 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/1879076 Title: [nvidia] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When in both Firefox and Opera hardware acceleration is on and browser is running it will trigger freeze with X.OrgX driver on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 12:17:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b] InstallationDate: Installed on 2020-04-08 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879076/+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 1879076] Re: Xorg freeze
Also, it appears your graphics setup might be misconfigured. Because you have: * An Nvidia GPU * The Nvidia kernel driver * The modesetting (for Intel) Xorg driver Please try: 1. Uninstall the Nvidia driver. 2. Reboot. 3. Open the app 'Additional Drivers' and install the Nvidia driver through that. 4. Reboot. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + [nvidia] Xorg freeze -- 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/1879076 Title: [nvidia] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When in both Firefox and Opera hardware acceleration is on and browser is running it will trigger freeze with X.OrgX driver on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 16 12:17:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b] InstallationDate: Installed on 2020-04-08 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision M6300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JM680 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6300 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879076/+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 1879177] Re: Sound cuts off and back on randomly during online streaming of videos
*** This bug is a duplicate of bug 1879182 *** https://bugs.launchpad.net/bugs/1879182 ** This bug has been marked a duplicate of bug 1879182 Sound cuts off and back on randomly during online streaming of videos -- 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/1879177 Title: Sound cuts off and back on randomly during online streaming of videos Status in alsa-driver package in Ubuntu: New Bug description: Sound cuts off and comes back on every 10 or so minutes. I have tried the usual stuff like purging and removing alsa and pulseaudio and restarting, forcing alsa reload, killing pulseaudio and starting again, etc. Here is the output from cat /var/log/syslog* | grep -i pulse gnome-shell[7674]: [8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation is nullptr. I have attached alsa information also as an attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879177/+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 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
Thank you for your bug report. Does it happen with any sound /application? Could you add your 'journalctl -b 0' log after getting the issue? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+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 1879158] Re: congelamento da tela
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879158 Title: congelamento da tela Status in xorg package in Ubuntu: Incomplete Bug description: congelamento da tela ao colocar aplicativos como o libreoffice em categoria de escritorio, jogos na categoria de jogos, navegadores na categoria de internet, ao renover um aplicativo da categoria a tela congela, fica somente o cursor do mouse fucionando tendo de forçar o desligamente do notebook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879158/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM - 2. Add second disk to it - 3. Run pvcreate /dev/vdb - 4. Run vgextend ubuntu-vg /dev/vdb - 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv + 2. Remove demsetup + 3. Add second disk to it + 4. Run pvcreate /dev/vdb + 5. Run vgextend ubuntu-vg /dev/vdb + 6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. ** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM - 2. Remove demsetup - 3. Add second disk to it - 4. Run pvcreate /dev/vdb - 5. Run vgextend ubuntu-vg /dev/vdb - 6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv + 2. Add second disk to it + 3. Run pvcreate /dev/vdb + 4. Run vgextend ubuntu-vg /dev/vdb + 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv + + Reboot and check that it still boots. + + 6. Remove demsetup + + Reboot and check that it fails to boot + + 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1879156] Re: Xorg freeze
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 Thank you for your bug report. Are you speaking about dragging icons in the GNOME overview to folders? How often do you hit the issue? ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879156 Title: Xorg freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: freezing the screen when placing applications such as libreoffice in the category of office, games in the category of games, browsers in the category of internet, when renewing an application of the category the screen freezes, it is only the mouse cursor working having to force the shutdown of the notebook. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 09:49:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Core Processor Integrated Graphics Controller [14c0:0051] InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ZMAX MOBILE 8100 B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=0ac96226-6558-4a62-993b-ee78ff9f1f00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.0D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NCL60/61 dmi.board.vendor: Compal dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0D:bd01/10/2011:svnZMAX:pnMOBILE8100B:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: MOBILE 8100 B dmi.product.sku: Calpella_Fab dmi.product.version: F01 dmi.sys.vendor: ZMAX version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879156/+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 1879206] Re: cups hplip not install printer
Screen of Hplip ** Attachment added: "Hplip 5012.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5373326/+files/Hplip%205012.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1879144] Re: Volume output settings reset on analog surround 4.0
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1879144] Re: Volume output settings reset on analog surround 4.0
Thank you for the bug report, could you upstream the issue on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/ ? -- 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/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. - 6. Remove demsetup + 6. Remove mdadm Reboot and check that it fails to boot 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. ** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm - - Reboot and check that it fails to boot - 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. + + 8. Downgrade lvm2 to release + + Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1879113] Re: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Thank you for your bug report, the issue is likely a corruption, could you try to download the update again? ** Changed in: pygobject (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1879113 Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in pygobject package in Ubuntu: Incomplete Bug description: Installing ra1nstorm virtual Mac ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-gi-cairo 3.26.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun May 17 13:06:06 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-16 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.3 SourcePackage: pygobject Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1879113/+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 1878752] Related fix merged to charm-ceph-osd (master)
Reviewed: https://review.opendev.org/728488
Committed:
https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=b1aab5d0e12e433b714e39f78945baf16e508a41
Submitter: Zuul
Branch:master
commit b1aab5d0e12e433b714e39f78945baf16e508a41
Author: James Page
Date: Fri May 15 17:00:25 2020 +0100
Trigger udev rescan if pv_dev disappears
Workaround for kernel by in Ubuntu 20.04 LTS.
When using by-dname device paths with MAAS and bcache, the pvcreate
operation results in the by-dname entry for the block device being
deleted. The subsequent vgcreate then fails as the path cannot
be found.
Trigger a rescan of block devices if the pv_dev path does not
exists after the pvcreate operation.
Change-Id: If7e11f6bd1effd2d5fc2dc5abbaba6865104006f
Depends-On: Ifb16c47ae5ff316cbcfc3798de3446a3774fa012
Related-Bug: 1878752
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
New
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+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 1879114] Re: Sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main)
This bug was fixed in the package dee - 1.2.7+17.10.20170616-6 Sponsored for Logan Rosen (logan) --- dee (1.2.7+17.10.20170616-6) unstable; urgency=low * Bumped dh to 12. * Updated Standards-Version to 4.4.0 * Added patches from Ubuntu: + build_no_werror.patch: Don't build with Werror (Closes: #940163) + vapi-skip-properties.patch: Disable properties that fail to build on newer versions of Vala and aren't required. * Removed python2 support (Closes: #936379) * debian/rules: + Update for dh 12. * Updated examples. -- Kartik Mistry Mon, 30 Sep 2019 23:12:16 +0530 dee (1.2.7+17.10.20170616-5) unstable; urgency=low * Do not add unnecessary dependency on python. Thanks to Steve Langasek for patch. (Closes: #922632) * Added debian/gitlab-ci.yml for pipeline. -- Kartik Mistry Thu, 21 Feb 2019 10:35:44 +0530 ** Changed in: dee (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1879114 Title: Sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main) Status in dee package in Ubuntu: Fix Released Bug description: Please sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/control: Build-Depends on the versioned python binary * debian/patches/vapi-skip-properties.patch: - Disable properties that fail to build on newer versions of Vala and aren't required * Drop dependency on python and python3; package should not depend on python just because it provides python bindings. * debian/patches/build_no_werror.patch - Don't build with Werror, it makes the build fail on some glib deprecations (lp: #1843730) Both of the patch files were incorporated into Debian. They dropped Python 2 support, so the versioned build dependency is no longer relevant. They also dropped the hardcoded dependencies on python/python3 for gir1.2-dee-1.0. Changelog entries since current groovy version 1.2.7+17.10.20170616-4ubuntu6: dee (1.2.7+17.10.20170616-6) unstable; urgency=low * Bumped dh to 12. * Updated Standards-Version to 4.4.0 * Added patches from Ubuntu: + build_no_werror.patch: Don't build with Werror (Closes: #940163) + vapi-skip-properties.patch: Disable properties that fail to build on newer versions of Vala and aren't required. * Removed python2 support (Closes: #936379) * debian/rules: + Update for dh 12. * Updated examples. -- Kartik Mistry Mon, 30 Sep 2019 23:12:16 +0530 dee (1.2.7+17.10.20170616-5) unstable; urgency=low * Do not add unnecessary dependency on python. Thanks to Steve Langasek for patch. (Closes: #922632) * Added debian/gitlab-ci.yml for pipeline. -- Kartik Mistry Thu, 21 Feb 2019 10:35:44 +0530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1879114/+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 1879158] Re: congelamento da tela
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 The English version is bug 1879156. ** This bug has been marked a duplicate of bug 1872268 Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders -- 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/1879158 Title: congelamento da tela Status in xorg package in Ubuntu: Incomplete Bug description: congelamento da tela ao colocar aplicativos como o libreoffice em categoria de escritorio, jogos na categoria de jogos, navegadores na categoria de internet, ao renover um aplicativo da categoria a tela congela, fica somente o cursor do mouse fucionando tendo de forçar o desligamente do notebook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879158/+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 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
Please: 1. Look in Settings > Sound and make sure 'Over-Amplification' is OFF. Does that fix it? 2. Open a terminal window and run 'top'. Now tell us if any process is using high CPU when the problem occurs. -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
Could you try if it works better in nm-connection-editor? Could you add your 'journalctl -b 0' log after triggering the issue? It would also be useful to have details on how it's not working. Is the menu option disabled? do you fail to connect? do you connect by have no data working? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
verified in bionic Did all the steps (install vm, create pv, extend pv, remove dmadm, upgrade). It booted after the upgrade to 2.02.176-4.1ubuntu3.18.04.3, and it failed again following a downgrade to the 2.02.176-4.1ubuntu3.18.04.2 from updates pocket. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: id-5d0ba914f340e31a8e9f2cf1 removal-candidate ** Tags added: id-5d0ba914f340e31a8e9f2cf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1878617] Re: Apple pages file type should be added to MIME types
I created a bug report in shared-mime-info's issues tracker here: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136 ** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #136 https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in mime-support package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1878617] Re: Apple pages file type should be added to MIME types
As requested, here is an example of an Apple Pages document, taken from an online templates website. ** Attachment added: "New Job Resignation Letter.pages" https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+attachment/5373328/+files/New%20Job%20Resignation%20Letter.pages ** Changed in: mime-support (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in mime-support package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1879206] Re: cups hplip not install printer
In the properties window of the printer connected as USB it indicates the absence of an HP file, on test printing with network installation the printer does not report an error, but does not connect. Inattiva - Il file "/usr/lib/cups/backend/hp" non è disponibile: No such file or directory ** Attachment added: "Localhost.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5373331/+files/Localhost.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: New Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1878553] [NEW] Ubuntu could not install Virtualbox Guest addons
You have been subscribed to a public bug: It seems that Ubuntu is not able to install the VirtualBox Guest add-ons even Ubuntu is able to detect it. See Attachement. Ubuntu 20.04 Basic install after Reboot, Update and Reboot again. Similar Tickets in Launchpad but really old: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: focal guestaddon innotek rls-ff-incoming virtualbox virtualisation -- Ubuntu could not install Virtualbox Guest addons https://bugs.launchpad.net/bugs/1878553 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878553] Re: Ubuntu could not install Virtualbox Guest addons
Thank you for the bug report, indeed there is something weird with software-properties Starting a focal iso in virtual, sofware-properties-gtk lists VMware drivers with only with continue manual mode available, but 'sudo ubuntu- drivers install' does install open-vm-tools seems rather an issue with the gui ** Tags added: focal rls-ff-incoming ** Package changed: ubuntu-drivers-common (Ubuntu) => software- properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1878553 Title: Ubuntu could not install Virtualbox Guest addons Status in software-properties package in Ubuntu: New Bug description: It seems that Ubuntu is not able to install the VirtualBox Guest add- ons even Ubuntu is able to detect it. See Attachement. Ubuntu 20.04 Basic install after Reboot, Update and Reboot again. Similar Tickets in Launchpad but really old: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1878553/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
This bug was fixed in the package linux - 4.15.0-101.102
---
linux (4.15.0-101.102) bionic; urgency=medium
* bionic/linux: 4.15.0-101.102 -proposed tracker (LP: #1877262)
* 4.15.0-100.101 breaks userspace builds due to a bug in the headers
/usr/include/linux/swab.h of linux-libc-dev (LP: #1877123)
- include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for
swap
* bionic snapdragon 4.15 snap failed Certification testing (LP: #1877657)
- Revert "drm/msm: Use the correct dma_sync calls in msm_gem"
- Revert "drm/msm: stop abusing dma_map/unmap for cache"
linux (4.15.0-100.101) bionic; urgency=medium
* bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)
* built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data
* Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
* QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs
* Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising
* LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
session
- scsi: target: iscsi: calling iscsit_stop_session() inside
iscsit_close_session() has no effect
* Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs
* Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- ALSA: hda: Add driver blacklist
- ALSA: hda: Fix potential access overflow in beep helper
- ALSA: ice1724: Fix invalid access for enumerated ctl items
- ALSA: pcm: oss: Fix regression by buffer overflow fix
- ALSA: do
[Touch-packages] [Bug 1878738] Re: program abort by "lh_table_new: calloc failed"
Seems to affect all software which uses this library. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878738 Title: program abort by "lh_table_new: calloc failed" Status in json-c package in Ubuntu: Confirmed Bug description: I wrote small sample program which abort by lh_table_new calloc failed. see this. https://gist.github.com/735eec6fd0869df1facb08da5baa402c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+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 1869940] Re: No networks available/visible after suspend
Please reproduce the issue then attach dmesg. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1869940 Title: No networks available/visible after suspend Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 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 SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNE
[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
same here on lenovo x1 carbon u20.04 upgraded from 18.04: ubuntu-drivers devices == /sys/devices/pci:00/:00:1c.2/:04:00.0 == modalias : pci:v8086d24FDsv8086sd1130bc02sc80i00 vendor : Intel Corporation model: Wireless 8265 / 8275 (Dual Band Wireless-AC 8265) manual_install: True driver : backport-iwlwifi-dkms - distro free ubuntu-drivers install No drivers found for installation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+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 1875605] Re: SRU the current 0.20.3 stable update
The gvfs regression is a known flaky test and cleared after retry The new 0.20.3-0ubuntu1 works fine, including ssh and gpg keys handling and the password manager software, marked as verified ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1875605 Title: SRU the current 0.20.3 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that using passwords in GNOME applications or gpg/ssh keys still work correctly * Regression potential There is a segfault fix for flapak portals, testing that usecase would be useful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1875605/+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 1869940] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1869940 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1869940 Title: No networks available/visible after suspend Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869940/+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 1876125] Re: SRU the current 3.36.2 stable update
Using 3.36.2-0ubuntu1 calendar integration in the desktop, the standalone application and the evolution components still work correctly, marking as verified The libreoffice test is flackyness and worked after a retry ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1876125 Title: SRU the current 3.36.2 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
Please attach output of: cat /lib/systemd/system/systemd-udevd.service Running the following command may fix the issue: sudo apt install --reinstall udev ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+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 1870442] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1870442 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 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 SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: netwo
[Touch-packages] [Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
@ddstreet, thanks, the fix works and I'll include it in the next upload
to Groovy, in the next days.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => 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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Focal:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1879311] [NEW] [There is no sound on the headset, Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem
Public bug reported: When I select in the settings what sound comes out of the headset. He continues to go through the notebook's internal speaker. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merencio 1779 F pulseaudio /dev/snd/controlC2: merencio 1779 F pulseaudio /dev/snd/controlC0: merencio 1779 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 08:06:49 2020 InstallationDate: Installed on 2020-04-18 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: None of the above Title: [Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-17 (0 days ago) dmi.bios.date: 11/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd11/21/2013:svnAcer:pnAspireE1-572:pvrV2.13:rvnAcer:rnEA50_HW:rvrV2.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E1-572 dmi.product.sku: Aspire E1-572_0775_V2.13 dmi.product.version: V2.13 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-18T07:17:21.090034 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879311 Title: [There is no sound on the headset, Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: When I select in the settings what sound comes out of the headset. He continues to go through the notebook's internal speaker. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: merencio 1779 F pulseaudio /dev/snd/controlC2: merencio 1779 F pulseaudio /dev/snd/controlC0: merencio 1779 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 08:06:49 2020 InstallationDate: Installed on 2020-04-18 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: None of the above Title: [Aspire E1-572, Realtek ALC282, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-17 (0 days ago) dmi.bios.date: 11/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd11/21/2013:svnAcer:pnAspireE1-572:pvrV2.13:rvnAcer:rnEA50_HW:rvrV2.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: SharkBay System dmi.product.name: Aspire E1-572 dmi.product.sku: Aspire E1-572_0775_V2.13 dmi.product.version: V2.13 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-18T07:17:21.090034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879311/+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 1872824] Re: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package ke
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1872824 Title: Can't upgrade console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5), trying to overwrite '/lib/systemd/system/console- setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 Status in console-setup package in Ubuntu: Confirmed Bug description: Upgrade path from 16.04 to 20.04 fails. console-setup-linux_1.194ubuntu3_all.deb tries to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5. I have reproduced this bug on bare metal and WSL. Log: Unpacking console-setup-linux (1.194ubuntu3) over (1.108ubuntu15.5) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb (--unpack): trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../keyboard-configuration_1.194ubuntu3_all.deb ... Unpacking keyboard-configuration (1.194ubuntu3) over (1.108ubuntu15.5) ... Preparing to unpack .../busybox-initramfs_1%3a1.30.1-4ubuntu6_amd64.deb ... Unpacking busybox-initramfs (1:1.30.1-4ubuntu6) over (1:1.22.0-15ubuntu1.4) ... Preparing to unpack .../initramfs-tools-bin_0.136ubuntu6_amd64.deb ... Unpacking initramfs-tools-bin (0.136ubuntu6) over (0.122ubuntu8.16) ... Preparing to unpack .../cpio_2.13+dfsg-2_amd64.deb ... Unpacking cpio (2.13+dfsg-2) over (2.11+dfsg-5ubuntu1.1) ... Preparing to unpack .../liblz4-1_1.9.2-2_amd64.deb ... Unpacking liblz4-1:amd64 (1.9.2-2) over (0.0~r131-2ubuntu2) ... Processing triggers for libc-bin (2.31-0ubuntu7) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.27) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/console-setup-linux_1.194ubuntu3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1872824/+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 1879282] [NEW] Workspace shows windows that is not on the current workspace
You have been subscribed to a public bug: If I have two workspaces and have for example firefox on both workspaces, then the second workspace will show the firefox windows that is on the first workspace. I can not controll this window, its just a piece of the background. I get this problem 100% of the time. The way I get it is by being on my second workspace, howering my pointer over the firefox on my topbar, go through the windows of the windows open for firefox, which makes my screen jump to the first window when i hower over the firefox window that is open on the first workspace, to indicate where it is located. Then when i click on the firefox window that is on the second workspace, the window from the first workspace is "stuck" as a wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 10:59:15 2020 DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740] InstallationDate: Installed on 2020-04-17 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago) dmi.bios.date: 11/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA 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.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Workspace shows windows that is not on the current workspace https://bugs.launchpad.net/bugs/1879282 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879282] Re: Workspace shows windows that is not on the current workspace
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879282 Title: Workspace shows windows that is not on the current workspace Status in xorg package in Ubuntu: New Bug description: If I have two workspaces and have for example firefox on both workspaces, then the second workspace will show the firefox windows that is on the first workspace. I can not controll this window, its just a piece of the background. I get this problem 100% of the time. The way I get it is by being on my second workspace, howering my pointer over the firefox on my topbar, go through the windows of the windows open for firefox, which makes my screen jump to the first window when i hower over the firefox window that is open on the first workspace, to indicate where it is located. Then when i click on the firefox window that is on the second workspace, the window from the first workspace is "stuck" as a wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 10:59:15 2020 DistUpgraded: 2020-04-26 19:27:56,468 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:1740] InstallationDate: Installed on 2020-04-17 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58e4 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=dc6ec013-e29e-4a5e-8dd0-17ae3cf639fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-26 (21 days ago) dmi.bios.date: 11/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA 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.:bvrUX430UA.304:bd11/14/2017:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879282/+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 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
I can't download the attachment, but it looks quite odd already from the original name. Please try reinstalling udev. -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
** Tags added: id-5eac701c52dbda63e8c9b00c
--
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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Focal:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Tags added: id-5d0ba914f340e31a8e9f2cf1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
** Attachment added: "jrnlctl.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+attachment/5373391/+files/jrnlctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04
1. I removed the network from the Wi-Fi setting and "Turn On Wi-Fi Hotspot..." is not grayed out. 2. I opened nm-connection-editor and click the +, then "Wi-Fi", then chose: - Mode: Hotspot - Device: wlp3s0 - No security 3. I connect with Ubuntu from another machine. There does appear to be a connection (WiFi settings has a check mark next to the network), but there is no internet and the icon remains a question mark. -- 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/1870359 Title: My machine as Wi-Fi Hotspot broken after upgrade to 20.04 Status in network-manager package in Ubuntu: Confirmed Bug description: I have a machine with a wired network connection and a wifi card. I've been using the machine as a wireless router and server in my house. I've attached a screenshot of the Wi-Fi network settings. It looks as expected. Upon updating to 20.04, none of my machines can use the connection. The linux machine will not connect. The windows machine will connect but will not have internet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 15:47:02 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-30 (1645 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.0.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-01-13T14:45:42.987041 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870359/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
eoan verified. So, eoan is tougher. I installed it with subiquity and tried to follow the steps, but failed to convert to raid1, apparently, subiquity created the LV 1 PE larger than before or something, so it needed 1 free PE in the original PV to be able to add the raid1 metadata, which it did not have. Worked around this by extending the PV size after the install (after tryin to shrink the existing LV first, messing up the install, and reinstalling ...). With proposed lvm2 ubuntu6.1 it boots as wanted, downgrading to ubuntu6 in release breaks it again. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
The regressions in bionic seem unrelated to me adding the raid1 module to the list of modules installed to the initramfs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1879326] [NEW] DNS resolution ceased to work after update
Public bug reported: Hi I did a Focal install on 14th of May 2020, could work until in the night of 16th of May 2020 and in the morning of the 18th of May 2020 I could not resolve domain names anymore. I can ping DNS servers but the resolution to IP addresses fails. I have switched on automatic installation of security relevant updates. I can reproduce the behaviour with a fresh install accepting all the updates there are. I did not try to find out which update is the cause. See the behaviour below where I even have tried to work around by removing the DNS server of my router: thiemo @ Fujitsu-HO ~ :-( % systemd-resolve --status 20-05-18 12:54 Global LLMNR setting: no MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (enp0s25) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 139.18.25.33 139.18.25.34 77.59.232.36 62.167.241.5 62.2.107.35 62.2.121.84 62.2.121.88 fd00::7eff:4dff:feaa:2528 2001:638:902:1::10 DNS Domain: ~. thiemo @ Fujitsu-HO ~ % host -v myworkspaceinet.post.ch 20-05-18 12:54 Trying "myworkspaceinet.post.ch" ;; connection timed out; no servers could be reached thiemo @ Fujitsu-HO ~ :-( % alias pong 20-05-18 12:55 pong='ping -c3' thiemo @ Fujitsu-HO ~ % pong 139.18.25.33 20-05-18 12:58 PING 139.18.25.33 (139.18.25.33) 56(84) bytes of data. 64 bytes from 139.18.25.33: icmp_seq=1 ttl=246 time=39.9 ms 64 bytes from 139.18.25.33: icmp_seq=2 ttl=246 time=39.0 ms 64 bytes from 139.18.25.33: icmp_seq=3 ttl=246 time=39.4 ms --- 139.18.25.33 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 39.000/39.431/39.868/0.354 ms Kind regards Thiemo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon May 18 13:03:40 2020 InstallationDate: Installed on 2020-05-15 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.33 metric 100 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 3ce8a4c9-c011-3344-bbfd-9618a499a099 ethernet 1589799780 Mon May 18 13:03:00 2020 yes -100 no /org/freedesktop/NetworkManager/Settings/1 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DE
[Touch-packages] [Bug 1871763] Re: Duplicity is not working
** Changed in: duplicity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1871763 Title: Duplicity is not working Status in Duplicity: Invalid Status in python-defaults package in Ubuntu: New Bug description: Duplicity is failing to make backup. It produces error message: see attached 000_Error_message.png After starting duplicity from terminal, I got much better error message: unim95@ubuntu-BitFenix-Prodigy:~$ duplicity bash: /usr/bin/duplicity: /usr/bin/python2: bad interpreter: No such file or directory After searching system for python2 i found, that there is no python2 executable unim95@ubuntu-BitFenix-Prodigy:~$ locate python2 | grep -v lib | grep -v man | grep -v doc | grep -v include /etc/python2.7 /etc/python2.7/sitecustomize.py /snap/core/8689/usr/share/bash-completion/completions/python2 /snap/core/8689/usr/share/dh-python/dh_python2 /snap/core/8689/usr/share/dh-python/dist/cpython2_fallback /snap/core/8935/usr/share/bash-completion/completions/python2 /snap/core/8935/usr/share/dh-python/dh_python2 /snap/core/8935/usr/share/dh-python/dist/cpython2_fallback /usr/bin/python2-futurize /usr/bin/python2-pasteurize /usr/bin/python2.7 /usr/bin/python2.7-config /usr/bin/waitress-serve-python2 /usr/bin/x86_64-linux-gnu-python2.7-config /usr/share/app-install/desktop/idle-python2.7:idle-python2.7.desktop /usr/share/applications/python2.7.desktop /usr/share/bash-completion/completions/python2 /usr/share/binfmts/python2.7 /usr/share/dh-python/dh_python2 /usr/share/dh-python/dist/cpython2_fallback /usr/share/lintian/overrides/python2.7 /usr/share/lintian/overrides/python2.7-minimal /usr/share/pixmaps/python2.7.xpm Default python is: unim95@ubuntu-BitFenix-Prodigy:~$ python --version Python 2.7.17 Duplicity version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s duplicity Package: duplicity Status: install ok installed Priority: optional Section: utils Installed-Size: 1064 Maintainer: Ubuntu Developers Architecture: amd64 Version: 0.7.17-0ubuntu1.1 Depends: libc6 (>= 2.4), librsync1 (>= 0.9.6), python (<< 2.8), python (>= 2.7~), python-fasteners, python:any (<< 2.8), python:any (>= 2.7.5-5~), python-lockfile (>> 1:0.9), gnupg | gnupg1 Suggests: rsync, python-paramiko, python-pexpect, python-urllib3, python-oauthlib, python-boto, ncftp, python-cloudfiles, lftp, python-gdata, tahoe-lafs, python-swiftclient Description: encrypted bandwidth-efficient backup Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server. Homepage: http://duplicity.nongnu.org/ Original-Maintainer: Alexander Zangerl Python2 version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s python Package: python Status: install ok installed Priority: optional Section: python Installed-Size: 624 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: allowed Source: python-defaults Version: 2.7.15~rc1-1 Replaces: python-dev (<< 2.6.5-2) Provides: python-ctypes, python-email, python-importlib, python-profiler, python-wsgiref Depends: python2.7 (>= 2.7.15~rc1-1~), libpython-stdlib (= 2.7.15~rc1-1) Pre-Depends: python-minimal (= 2.7.15~rc1-1) Suggests: python-doc (= 2.7.15~rc1-1), python-tk (>= 2.7.15~rc1-1~) Breaks: update-manager-core (<< 0.200.5-2) Conflicts: python-central (<< 0.5.5) Description: interactive high-level object-oriented language (default version) Python, the high-level, interactive object oriented language, includes an extensive class library with lots of goodies for network programming, system administration, sounds and graphics. . This package is a dependency package, which depends on Debian's default Python version (currently v2.7). Original-Maintainer: Matthias Klose Homepage: http://www.python.org/ Cnf-Extra-Commands: python Cnf-Priority-Bonus: 3 OS: unim95@ubuntu-BitFenix-Prodigy:~$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" VERSION_ID="18.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=bionic UBUNTU_CODENAME=bionic FS used: ext4. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
SEARCHING IS NOT NAVIGATING, please. Besides the debate on whether the option to disable search when starting to type should exist (I think it should), #144 has raised quite an important side effect: searching should not make it look like files are deleted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1879144] Re: Volume output settings reset on analog surround 4.0
There is one thing I am not sure: it is an issue of pulseaudio or an issue of the ubuntu settings. But I will upstream it though. -- 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/1879144 Title: Volume output settings reset on analog surround 4.0 Status in pulseaudio package in Ubuntu: New Bug description: It seems to be a pulseaudio issue but unsure if it is a settings error. Version: Ubuntu 20.04 LTS / 20.04 Computer Model: HP Envy x360 13 with AMD Ryzen 3500U PulseAudio version: 1:13.99.1-1ubuntu3.2 Problem Description: When manually reduce volume, Balance and Fade level resets when such reduction reaches 0 audio output. This is not the case when I manually mute the audio output (or with a mute switch) Intended Outcome: There should not be any reset at all. Other information: It seems to be a problem with pulseaudio. However, I cannot confirm if it is a bug from the pulseaudio side or the Ubuntu settings side. Intended outcome: It should work the same: turning the volume to 0 should not reset the fade settings nor the balance settings. Check the screencast below for what is going on (youtube link) (0:00-0:22): https://www.youtube.com/watch?v=EEsClQ7Pj08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879144/+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 1826003] Re: software properties unknown to ubuntu software
Problem disappeared. changed status to invalid ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1826003 Title: software properties unknown to ubuntu software Status in software-properties package in Ubuntu: Invalid Bug description: open the dash, right click on 'software properties' select 'show details' gnome software opens with a message 'unable to find "software-properties-gtk.desktop" corrado@corrado-HP-p4-ee:~$ inxi -Fx System:Host: corrado-HP-p4-ee Kernel: 5.0.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.0 Distro: Ubuntu 19.10 (Eoan EANIMAL) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 16.0 Wh condition: 20.0/20.0 Wh (100%) model: 13-42 OA03031 status: Discharging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 798 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.2 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.0.0-13-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 465.76 GiB used: 5.88 GiB (1.3%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 31.25 GiB used: 5.87 GiB (18.8%) fs: ext4 dev: /dev/sda4 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 41.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 209 Uptime: 2h 44m Memory: 3.78 GiB used: 1.14 GiB (30.0%) Init: systemd runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33 corrado@corrado-HP-p4-ee:~$ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC=it_IT.UTF-8 LC_TIME=it_IT.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=it_IT.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=it_IT.UTF-8 LC_NAME=it_IT.UTF-8 LC_ADDRESS=it_IT.UTF-8 LC_TELEPHONE=it_IT.UTF-8 LC_MEASUREMENT=it_IT.UTF-8 LC_IDENTIFICATION=it_IT.UTF-8 LC_ALL= corrado@corrado-HP-p4-ee:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 17:13:53 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-04-21 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190421) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826003/+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 1879090] Re: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set
Thank you for responding. I wonder if it's intended by design. I used to logout via `dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 'org.freedesktop.login1.Manager.TerminateSession' string:$XDG_SESSION_ID` or `loginctl kill-session $XDG_SESSION_ID` in my scripts. I can live without them. Did developers drop those environment variables? Another question: Is that issue related to `lightdm` or `systemd`? Regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1879090 Title: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set Status in lightdm package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+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 1879333] [NEW] Black screen on loading latest system update
Public bug reported: This bug has been around since 16.04 and still occurs with 18.04 when using nvidia drivers. When update required for the OS the black screen situation happens after the required reboot. Only way to regain desktop is to login via ssh terminal and run the commands listed here: https://askubuntu.com/questions/1129516/black-screen-at-boot-after- nvidia-driver-installation-on-ubuntu-18-04-2-lts sudo apt-get update sudo apt-get upgrade sudo apt-get purge nvidia* sudo apt autoremove sudo apt-get install dkms build-essential linux-headers-$(uname -r) echo "# Disable the default Nouveau kernel driver" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "# -" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d /blacklist-nouveau.conf echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf cat /etc/modprobe.d/blacklist-nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d/nouveau- kms.conf cat /etc/modprobe.d/nouveau-kms.conf sudo update-initramfs -u sudo service lightdm stop sudo apt-get install nvidia-driver-440 lsmod | grep nvidia sudo lshw -c video | grep 'configuration' sudo reboot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon May 18 08:44:05 2020 DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1] NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a] InstallationDate: Installed on 2019-09-26 (234 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N3150M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd02/27/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Apr 29 07:15:33 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** 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/1879333 Title: Black screen on loading latest system update Status in xorg package in Ubuntu: New Bug description: This bug has been around since 16.04
[Touch-packages] [Bug 1698388] Re: Assertion failure in journal-remote-parse.c
Fixed in Bionic and later. ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1698388 Title: Assertion failure in journal-remote-parse.c Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: I am observing the following assertion failure in systemd-journal- remote: Assertion 'source->filled <= source->size' failed at ../src/journal- remote/journal-remote-parse.c:95, function get_line(). Aborting. Systemd version: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version: systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu17 It looks like this issue has been fixed upstream in v230, specifically in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this particular commit be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+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 1326536] Re: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM
This bug is still present in ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1326536 Title: libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd resolution behaviour on the VM Status in libvirt package in Ubuntu: Triaged Status in lxc package in Ubuntu: Triaged Bug description: When libvirt configures / starts up dnsmasq on the host, it does not pass --no-hosts, resulting in it reading in the /etc/hosts file from the host. The default ubuntu setup will have the host's hostname in /etc/hosts under 127.0.1.1. Since libvirt's dnsmasq is reading this file, anything querying that dnsmasq instance will resolve the host's hostname out of /etc/hosts. The result of this is any VM running on the host will resolve the host's hostname as 127.0.1.1. For example, if the host's hostname is BoxA, any VM running on the host will resolve BoxA to 127.0.1.1, which is not BoxA's actual address. Would recommend passing --no-hosts to dnsmasq when libvirt starts it up. If a user wants hardcoded hosts for their libvirt network, they can add them to /var/lib/libvirt/dnsmasq/default.addnhosts . If this is an acceptable solution, I'd be happy to write the patch up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+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 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
This doesn't seem to be a curtin bug to me; feel free to disagree (with
reasoning!).
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
Invalid
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+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 1879058] [NEW] Display viewport incorrect with 90° rotated displayed
You have been subscribed to a public bug: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment x11 -- Display viewport incorrect with 90° rotated displayed https://bugs.launchpad.net/bugs/1879058 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879058] Re: Display viewport incorrect with 90° rotated displayed
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879058 Title: Display viewport incorrect with 90° rotated displayed Status in xorg package in Ubuntu: New Bug description: The system which automatically configure the position and size of the display seems to not handle the display viewport correctly. When configuring the position of displays with Ubuntu display settings interface, If I set a vertical display (rotated 90°) for a 1920x1080 display, then it seems the viewport or virtual display (I don't really know how you name is) seems to be 1920x1920. So the desktop is bigger than the screen and it can be moved with the mouse. Considering I use multi screens (3 rotated and one normal) it makes some crazy things. So my feeling is that while the screen is rotated, the viewport definition remains 1920x1080 instead of 1080x1920, and the system resolve it by providing a viewport of 1920x1920. This issue can be more or less circumvented using Nvidia Tools to configure displays. With it, the viewport seems to work correctly. However, as soon as a screen is disconnected, the system reconfigure the various displays and the issue comes back. So often, after a sleep or something like that, the issue comes back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879058/+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 1878752] Re: vgcreate fails on /dev/disk/by-dname block devices
I would very much agree with xnox (it's a duplicate) (and Dan, nothing
for curtin to do);
curtin generated dname rules rely upon pointing to a /dev/bcache/by-
uuid/* symlink which is currently broken per
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941
which at this time points some issue in udev itself (the kernel emits
all of the correct uevents we expect).
And as James' workaround shows; it's *not* always happening; a rescan
can "restore" the links; but that's not 100% reliable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752
Title:
vgcreate fails on /dev/disk/by-dname block devices
Status in OpenStack ceph-osd charm:
New
Status in curtin package in Ubuntu:
Invalid
Status in lvm2 package in Ubuntu:
New
Bug description:
Ubuntu Focal, OpenStack Charmers Next Charms.
juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
dname/bcache2
unit-ceph-osd-0:
UnitId: ceph-osd/0
id: "5"
message: exit status 1
results:
ReturnCode: 1
Stderr: |
partx: /dev/disk/by-dname/bcache2: failed to read partition table
Failed to find physical volume "/dev/bcache1".
Failed to find physical volume "/dev/bcache1".
Device /dev/disk/by-dname/bcache2 not found.
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 79, in
request = add_device(request=request,
File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk",
line 34, in add_device
charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
File "lib/charms_ceph/utils.py", line 1497, in osdize
osdize_dev(dev, osd_format, osd_journal,
File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
cmd = _ceph_volume(dev,
File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
cmd.append(_allocate_logical_volume(dev=dev,
File "lib/charms_ceph/utils.py", line 1965, in
_allocate_logical_volume
lvm.create_lvm_volume_group(vg_name, pv_dev)
File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in
create_lvm_volume_group
check_call(['vgcreate', volume_group, block_device])
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['vgcreate',
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']'
returned non-zero exit status 5.
Stdout: |2
Physical volume "/dev/disk/by-dname/bcache2" successfully created.
status: failed
timing:
completed: 2020-05-15 06:04:41 + UTC
enqueued: 2020-05-15 06:04:30 + UTC
started: 2020-05-15 06:04:39 + UTC
The same action on the /dev/bcacheX device succeeds - looks like some
sort of behaviour break in Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+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 1879343] [NEW] REGRESSION - Ctrl+Alt+F1 no longer gives me access to virtual terminal, just a black screen
Public bug reported: Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual console, not entirely sure what that's called, where you can log in into a shell and run commands. I use that when some of the tons of bugs in Ubuntu makes the system hang so badly that I can't even open a terminal window, in order to figure out if there's a process that I can kill. Then I'd be able to return to the xorg screen with Ctrl+Alt+F7. Now (and even while the system is not hung at all) I'm doing ctrl+Alt+F1, and all I get is a black screen with no console/terminal at all. Completely fucking useless, ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 18 17:02:03 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2410 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 17 02:39:40 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879343 Title: REGRESSION - Ctrl+Alt+F1 no longer gives me access to virtual terminal, just a black screen Status in xorg package in Ubuntu: New Bug description: Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual console, not entirely sure what that's called, where you can log in into a shell and run commands. I use that when some of the tons of bugs in Ubuntu makes the system hang so badly that I can't even open a terminal window, in order to figure out if there's a process that I can kill. Then I'd be able to return to the xorg screen with Ctrl+Alt+F7. Now (and even while the system is not hung at all) I'm doing ctrl+Alt+F1, and all I get is a black screen with no console/terminal at all. Completely fucking useless, ProblemType: Bug DistroRelea
[Touch-packages] [Bug 1875493] Re: [core] log rotation doesn't properly restart rsyslogd
@ogra If the component in question was removed and/or deprecated and no longer used in the current development release, then the policy shouldn't apply. In this case I don't think it would be much of a stretch to get a waiver for this. That said, as I'm pretty sure this bug is specific to Core, so fixing the issue in the core snap directly is probably the better approach. We can't just leave things "as is", as this bug can lead to Core devices running out of storage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd Status in Snappy: New Status in rsyslog package in Ubuntu: New Bug description: One of our commercial partners is developing a device agent snap for UC16. One of their engineers just shared the following bug report: I wanted to give you a heads up on an issue that we encountered with one of our gateways (a Dell 3000) regarding a full disk (/writable). It seems as though rsyslog had a bad logrotate config and was holding on to deleted files as described here: - https://www.claudiokuenzler.com/blog/861/after-ubuntu-update-trusty-xenial-disk-filled-syslog-logrotate - https://bugzilla.redhat.com/show_bug.cgi?id=1713358 Both df and du where showing different results for the “/writable” path on the Dell gateway. We were able to copy the lsof binary over and found this: $ sudo /tmp/lsof | grep deleted ... rsyslogd 1765 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rsyslogd 1765 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rsyslogd 1765 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imuxso 1765 1776 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imuxso 1765 1776 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imuxso 1765 1776 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) in:imklog 1765 1777 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) in:imklog 1765 1777 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) in:imklog 1765 1777 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) rs:main 1765 1778 syslog 5w REG 179,4 1993793536 130599 /var/log/syslog (deleted) rs:main 1765 1778 syslog 6w REG 179,4 45056 130836 /var/log/auth.log (deleted) rs:main 1765 1778 syslog 7w REG 179,4 211976192 130782 /var/log/kern.log (deleted) ... Restarting the service freed up the deleted files / disk space: sudo service rsyslog restart The rsyslog config (/etc/logrotate.d/rsyslog) calls this script post rotate: /usr/lib/rsyslog/rsyslog-rotate Which does not actually kill the rsyslog process: admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.7 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2464 0.0 0.0 12984 932 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo /usr/lib/rsyslog/rsyslog-rotate admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2469 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog The fix appears to be using the following command: sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2305 0.6 0.1 262692 3432 ? Ssl 20:35 0:00 /usr/sbin/rsyslogd -n admin 2482 0.0 0.0 12984 972 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog admin@GR0GP42:~$ sudo systemctl restart rsyslog >/dev/null 2>&1 || true admin@GR0GP42:~$ ps aux | grep rsyslog syslog 2487 1.0 0.1 262692 3432 ? Ssl 20:36 0:00 /usr/sbin/rsyslogd -n admin 2496 0.0 0.0 12984 980 pts/0 S+ 20:36 0:00 grep --color=auto rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+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 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
Thanks for the reply. Over amplification is already off. No process takes more than 12% CPU utilization. -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+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 1879352] [NEW] /usr/bin/im-launch i3 fails
Public bug reported: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in xorg package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879352/+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 1879182] Re: Sound cuts off and back on randomly during online streaming of videos
journalctl -b 0 log attached The sound goes out with a double pop sound and comes back on within 10 minutes with a double pop sound. During the time when the sound is off, crackling noises can be heard in sync with the audio that is playing. ** Attachment added: "journal_log.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+attachment/5373493/+files/journal_log.txt -- 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/1879182 Title: Sound cuts off and back on randomly during online streaming of videos Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound shuts off and turns back on again with two pop clicks. When the sound is off, if i turn up the volume to the max, i can hear crackling sound in speakers in tune with sound playing on the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: siddahuja 31829 F pulseaudio /dev/snd/controlC0: siddahuja 31829 F pulseaudio /dev/snd/pcmC0D0p: siddahuja 31829 F...m pulseaudio /dev/snd/timer: siddahuja 31829 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 17 23:56:27 2020 InstallationDate: Installed on 2020-04-27 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/20/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z170X-Gaming 3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-05-17T19:59:02.590821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879182/+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 1877895] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1
hello, follows attached Em segunda-feira, 18 de maio de 2020 07:45:57 BRT, Balint Reczey escreveu: Please attach output of: cat /lib/systemd/system/systemd-udevd.service Running the following command may fix the issue: sudo apt install --reinstall udev ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR0170D5:bd11/14/2012:svnSonyCorporation:pnSVE15125CBW:pvrC800EQPLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: SVE15125CBW dmi.product.sku: 54508549 dmi.product.version: C800EQPLK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877895/+subscriptions ** Attachment added: "=?UTF-8?b?Y2F0?=" https://bugs.launchpad.net/bugs/1877895/+attachment/5373384/+files/%3D%3FUTF-8%3Fb%3FY2F0%3F%3D -- 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/1877895 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 Status in systemd package in Ubuntu: Incomplete Bug description: after updating from 18.04 to 20.04, appears errors constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules Date: Sat May 9 10:24:26 2020 ErrorMessage: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Sony Corporation SVE15125CBW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=53223737-2091-4487-a0b3-a2b80db164ad ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: o subprocesso instalado, do pacote udev, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R0170D5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor:
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
This bug affects me too, with a client certificate that now "magically"
does not match the requirements.
Ironically, the error message says only:
OpenSSL error error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md
too weak, (no key found, wrong pass phrase, or wrong file format?)
although there was no MD5 signature involved at all. So, even when you
know that with OpenSSL 1.1, an "SSL security level" has been introduced,
and that Ubuntu has set that level to 2, it is hard to find that it
deprecates SHA1 now (see
https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_security_level.html).
Thus, even for more knowledgable people than me this is a major hassle
to find and/or fix. I wonder why Ubuntu has chosen to raise the level
that high considering that the documentation page contains a clear
warning indication:
"WARNING at this time setting the security level higher than 1 for
general internet use is likely to cause considerable interoperability
issues and is not recommended. This is because the SHA1 algorithm is
very widely used in certificates and will be rejected at levels higher
than 1 because it only offers 80 bits of security."
I think that this is an extremely unwise choice for an OS to make.
That being said, here is the fix (also hard to find):
In /etc/ssl/openssl.cnf, add this line before the start of the file:
openssl_conf = default_conf
At the end of the file, add these lines:
[default_conf]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
CipherString = DEFAULT:@SECLEVEL=1
This will bring down the SSL security level to the former level of 1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in OpenSSL:
Unknown
Status in openssl package in Ubuntu:
Confirmed
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/";)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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
