[Bug 1947438] [NEW] engrampa archive manager cannot open Stuffit archives
Public bug reported: The engrampa Archive Manager Manual claims that it can open Stuffit archives (.sit) but trying to do so gives the "Archive type not supported." error message. Either fix the software or the manual. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: engrampa 1.24.0-2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat Oct 16 01:39:10 2021 SourcePackage: engrampa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: engrampa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947438 Title: engrampa archive manager cannot open Stuffit archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/engrampa/+bug/1947438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873004] Re: lxd interaction blocked until snapd was restarted
** No longer affects: lxd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873004 Title: lxd interaction blocked until snapd was restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905478] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Setup snap "snapd" (9721) security profiles (cannot reload udev rules: exit status 1 Was that when updating a privileged LXD container by any chance? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905478 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1905478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908460] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143
I suspect you probably found a way out of this by now but if not or if you're hitting this on another system, let me know and I'll sort something out. It would have been interesting to see what those symlinks are pointing to, they may not have been rewritten properly due to the failure partway through the migration. ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908460 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1908460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909149] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
** Package changed: lxd (Ubuntu) => snapd (Ubuntu) ** Summary changed: - package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 + snapd failure when /home is a symlink -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909149 Title: snapd failure when /home is a symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1909149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909371] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Run install hook of "lxd" snap if present (run hook "install": /var/lib/snapd not root-owned 0:110) That's a new one I've never seen before. This suggests that directory ownership for /var/lib/snapd is quite wrong on your system which in turn causes some snapd actions to fail. I'll re-assign to snapd for investigation but it'd be useful if you could show `ls -lh /var/lib/` to see what's going on there. ** Package changed: lxd (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909371 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1909371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909693] Re: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Download snap "snapd" (10492) from channel "stable" (Get https://canonical-bos01.cdn.snapcraft.io/download-origin/canonical- lgw01/PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4_10492.snap?interactive=1=1609376400_22d9f1ee728894ebbb147d6cf985e1b06e1fbccd: dial tcp 91.189.91.42:443: connect: connection timed out) This shows some kind of network connectivity issue at the time. Re- trying the update, possibly from a different network should unstick things. It may be a good idea for snapd to more actively retry some of those network failures though... ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909693 Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1909693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912210] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install"Fupgrade: new lxd package pre-installation script subprocess returned error exxit status 1
error: unable to contact snap store This shows the reason for the failure, it's likely the system having dropped offline at the time or some other kind of networking or firewalling issues preventing your system from reaching the package store. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912210 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install"Fupgrade: new lxd package pre-installation script subprocess returned error exxit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1912210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915767] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess was killed by signal (Aborted)
That's pretty confusing, it shows as if it crashed while trying to test connectivity with the snap store but this appears to be outside of our script and is weirdly mixed in with gnome session output. Did you manage to fully unstick that system and apply all remaining updates afterwards? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915767 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess was killed by signal (Aborted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1915767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938809] Re: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
error: Unable to connect to the source LXD: Get "http://unix.socket/1.0": dial unix /var/lib/lxd/unix.socket: connect: connection refused This actually suggests a LXD upgrade failure. If this can be reproduce, the output of `journalctl -u snap.lxd.daemon -n 300` would be quite useful. ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938809 Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1938809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920667] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: »installiertes lxd-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
The issue with this one is translation handling in the old version of LXD. The migration script has since been changed to force LANG=C.UTF-8 to avoid such issues. ** Changed in: lxd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920667 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: »installiertes lxd-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1920667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909376] Re: package lxd 3.0.0-0ubuntu4 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Setup snap "core" (10577) security profiles (cannot setup udev for snap "core": cannot reload udev rules: exit status 1 Is that an update running inside of a privileged LXD container by any chance? ** Changed in: lxd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909376 Title: package lxd 3.0.0-0ubuntu4 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1909376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923685] Re: Unable to deploy LXD VM host on S390X
** Changed in: lxd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923685 Title: Unable to deploy LXD VM host on S390X To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1923685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933139] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
error: unable to contact snap store This suggests the system had network connectivity issues at the time of the upgrade. Did re-trying the upgrade get you through to the end eventually? Assuming this is all inside of a container (as your systemd change suggests), an alternative is to just remove the line from the /etc/fstab. Containers will happily boot without that line. ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933139 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1933139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931771] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Setup snap "snapd" (12057) security profiles (cannot reload udev rules: exit status 1 Is this an upgrade running inside of a privileged lxd container by any chance? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931771 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1931771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936985] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-913738666: mount failed: Operation not permitted. This looks odd, snapd should know to use snapfuse in such environments. Can you show "lxc config show --expanded" of such a container if you're still hitting this issue? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936985 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1936985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943734] Re: package lxd (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto lxd script pre-installation ha restituito lo stato di errore 1
- Download snap "lxd" (21545) from channel "4.0/stable/ubuntu-20.04" (download too slow: 0.00 bytes/sec) This suggests some pretty severe internet issue at the time of the upgrade. Re-trying later or on a more reliable network may help? ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943734 Title: package lxd (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto lxd script pre-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1943734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947137] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Setup snap "snapd" (13170) security profiles (cannot reload udev rules: exit status 1 Was that a privileged LXD container (security.privileged=true)? If so, I believe that's a known (and still unfixed) issue with snapd inside such containers. ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947137 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1947137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947428] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Moving over to snapd as that's hitting during snap installation. ** Package changed: lxd (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947428 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1947428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938005] Re: ufw ignores rules
[Expired for ufw (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ufw (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938005 Title: ufw ignores rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1938005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888186] Re: LibreOffice Writer unusably slow
Since this got updated: the bug persisted until 21.04, at which point it disappeared, but seemed to be coming back in the last patches to 21.04 (and affecting Calc, this time). I have only just upgraded to 21.10, so I cannot comment on its current status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888186 Title: LibreOffice Writer unusably slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947434] [NEW] Windows always open across monitors in a multi-monitor setup
Public bug reported: I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell U2719DC). Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 21.04 too. If I log in using Wayland (the default), the initial window position of any app is always in the middle (half on the internal display and half on the external monitor). No setting that I have found appears to be able to change this behavior. If I switch to Xorg, this problem does not exist. With Xorg, the app window always opens on the primary monitor (the external one, in my case). This is the preferred behavior. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947434 Title: Windows always open across monitors in a multi-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.11.0.1020.21)
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1020.21) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3.6 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888186] Re: LibreOffice Writer unusably slow
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888186 Title: LibreOffice Writer unusably slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947432] [NEW] Display backlight and brightness controls are not working
Public bug reported: The screen brightness is stuck at 50% of the max output and the brightness controls/slider do nothing at all. This issue started happening with the nvidia-driver-470 package even before I upgraded from 21.04, and it doesn't happen with 465. The bug manifests in both X11 and Wayland. (and GDM itself before logging in) Setting nvidia-drm.modeset to 1 doesn't seem to affect it either. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14 Uname: Linux 5.13.0-19-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.74 Mon Sep 13 23:09:15 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 03:46:49 2021 DistUpgraded: 2021-10-16 03:03:33,254 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.11.0-37-generic, x86_64: installed acpi-call, 1.1.0, 5.11.0-37-lowlatency, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-generic, x86_64: installed acpi-call, 1.1.0, 5.13.0-19-lowlatency, x86_64: installed nvidia, 470.74, 5.13.0-19-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP106BM [GeForce GTX 1060 Mobile 6GB] [103c:846a] InstallationDate: Installed on 2020-08-06 (436 days ago) InstallationMedia: MachineType: HP OMEN by HP Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-lowlatency root=UUID=4d38cd06-3a59-420a-be51-f664f12d213d ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 05/11/2018 dmi.bios.release: 15.3 dmi.bios.vendor: AMI dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 846A dmi.board.vendor: HP dmi.board.version: 68.19 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.19 dmi.modalias: dmi:bvnAMI:bvrF.03:bd05/11/2018:br15.3:efr68.19:svnHP:pnOMENbyHPLaptop:pvr:sku4PM48EA#ABV:rvnHP:rn846A:rvr68.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4PM48EA#ABV dmi.sys.vendor: HP nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish possible-manual-nvidia-install ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947432 Title: Display backlight and brightness controls are not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947431] Re: Black/boot logo screen on wayland session after installing nvidia drivers
** Description changed: Just did a fresh install. First thing I did was installing nvidia drivers. Tried wayland session and got a black screen with the boot logo page. Tried the instructions here: https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on- - ubuntu-21-10-nvidia but couldn't do it. I am submitting this as a bug + ubuntu-21-10-nvidia but didn't cut it. I am submitting this as a bug since it's a fresh install with the official drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.74-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 22:27:53 2021 InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Just did a fresh install. First thing I did was installing nvidia drivers. Tried wayland session and got a black screen with the boot logo page. Tried the instructions here: https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on- ubuntu-21-10-nvidia but didn't cut it. I am submitting this as a bug since it's a fresh install with the official drivers. + + Another thing to notice is that using the recovery option on grub I was able to get a wayland session, but some apps would crash the session + and the nvidia GUI menu doesn't work (blank GUI) there but works + normally on X11. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.74-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 22:27:53 2021 InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947431 Title: Black/boot logo screen on wayland session after installing nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947431] [NEW] Black/boot logo screen on wayland session after installing nvidia drivers
Public bug reported: Just did a fresh install. First thing I did was installing nvidia drivers. Tried wayland session and got a black screen with the boot logo page. Tried the instructions here: https://askubuntu.com/questions/1369250/how-do-i-enable-wayland-on- ubuntu-21-10-nvidia but didn't cut it. I am submitting this as a bug since it's a fresh install with the official drivers. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.74-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 22:27:53 2021 InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947431 Title: Black/boot logo screen on wayland session after installing nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1947431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947429] [NEW] linux-object-* not autoremoved on upgrade
Public bug reported: After upgrading my kernel, directories are left behind in /lib/modules for previous kernel because with the kernel packaging layout, not all binary packages are autoremoved: $ dpkg -S /lib/modules/5.11.0-34-generic linux-objects-nvidia-460-5.11.0-34-generic: /lib/modules/5.11.0-34-generic $ sudo apt autoremove --purge linux-objects-nvidia-460-5.11.0-34-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-objects-nvidia-460-5.11.0-34-generic* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Requesting to save current system state Successfully saved as "autozsys_sdijbm" (Reading database ... 362960 files and directories currently installed.) Purging configuration files for linux-objects-nvidia-460-5.11.0-34-generic (5.11 .0-34.36) ... dpkg: warning: while removing linux-objects-nvidia-460-5.11.0-34-generic, directory '/lib/modules/5.11.0-34-generic' not empty so not removed ZSys is adding automatic system snapshot to GRUB menu $ ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apt 2.3.9 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 14:36:40 2021 InstallationDate: Installed on 2019-12-23 (661 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apt UpgradeStatus: Upgraded to impish on 2021-10-15 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947429 Title: linux-object-* not autoremoved on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1947429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1946034] Re: https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 Thanks, I'll check it out. On Fri, Oct 15, 2021, 4:25 PM Grant Orndorff <1946...@bugs.launchpad.net> wrote: > *** This bug is a duplicate of bug 1930121 *** > https://bugs.launchpad.net/bugs/1930121 > > ** This bug has been marked a duplicate of bug 1930121 >package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No > module named 'uaclient' > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1946034 > > Title: > https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools > > Status in ubuntu-advantage-tools package in Ubuntu: > Incomplete > > Bug description: > We recently encountered an issue with our deployment pipeline when > installing Ubuntu 18.04. > > "ubuntu-minimal" now depends on ubuntu-advantage-tools, but that package > fails install with: > ModuleNotFoundError: No module named 'uaclient' > > I added OS packages 'python-opcua' and 'python3-opcua' and the error > changed to: > No module named 'uaclient.entitlements' > > I'm wondering why the dependencies can't be resolved at install time > through APT per usual. The setup consistently exits with a '1', which > fails our build pipeline. Hopefully that's not the default behavior. > More info in the comment below > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1946034/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946034 Title: https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1946034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947428] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Public bug reported: I was trying a upgrade on a server from 18.04 to 20.04 but do-release- upgrade fails when trying to upgrade lxd as the SNAP content site has an expired/revoked certificate The error in do-release-upgrade is ==> Installing the LXD snap from the 4.0 track for ubuntu-20.04 2021-10-15T15:34:39-04:00 INFO Waiting for automatic snapd restart... error: cannot perform the following tasks: - Download snap "core20" (1169) from channel "stable" (Get https://canonical-lcy 01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/DLqre5XGLbDqg9jPtiAh RRjDuPVa5X1q_1169.snap?interactive=1=1634338800_2b7ac0f78ddb21e1b3760018c7 00fe9e99fd4e8f: x509: certificate signed by unknown authority) dpkg: error processing archive /raid/scratch/apt-dpkg-install-FMjRvH/00-lxd_1%3a 0.9_all.deb (--unpack): new lxd package pre-installation script subprocess returned error exit status 1 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/lxd.0.crash' And we can see the issue with a simple 'wget' $ wget -O tmp.dpkg 'https://canonical-lcy01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q_1169.snap?interactive=1=1634338800_2b7ac0f78ddb21e1b3760018c700fe9e99fd4e8f' --2021-10-15 20:58:22-- https://canonical-lcy01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q_1169.snap?interactive=1=1634338800_2b7ac0f78ddb21e1b3760018c700fe9e99fd4e8f Resolving canonical-lcy01.cdn.snapcraftcontent.com... 91.189.88.179, 91.189.88.178 Connecting to canonical-lcy01.cdn.snapcraftcontent.com|91.189.88.179|:443... connected. ERROR: The certificate of ‘canonical-lcy01.cdn.snapcraftcontent.com’ is not trusted. ERROR: The certificate of ‘canonical-lcy01.cdn.snapcraftcontent.com’ has expired. The whole upgrade then fails as lxd is a dependency and one is left with the server in a partial state ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140 Uname: Linux 5.4.0-87-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 15 15:34:43 2021 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-11 (429 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-10-15 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947428 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1947428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947424] Re: Cannot set pbuilder build locale
I don't know about Ubuntu, but FTBFS under a common locale, which would include C, is regarded as a release-critical bug, so there is no "correct" locale, just the one that happens to be standardised across the Debian and Ubuntu buildds (otherwise, would "FTBFS in pbuilder" be a bug in pbuilder? because that's not the "correct" chroot-based build tool). I don't know if this is the right way to fix it though. I feel like a more general bash associative array in order to set arbitrary environment variables might be the better way to do it, rather than specifically for LANG and LC_ALL. We probably also should just change the locale in pbuilder-buildpackage to C.UTF-8; we might have some unicode-trashing bugs lurking in pbuilder itself otherwise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947424 Title: Cannot set pbuilder build locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947417] Re: Touchpad not recognized after BIOS update
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1947417/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947417 Title: Touchpad not recognized after BIOS update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947424] Re: Cannot set pbuilder build locale
The attachment "allow-setting-pbuilder-build-locale.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947424 Title: Cannot set pbuilder build locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947415] Re: A blackscreen is displayed after login.
** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947415 Title: A blackscreen is displayed after login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1947415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
Adding i915.fastboot=0 to the kernel params allows booting on these kernels. (Tested working on a XPS 9575) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905142] Re: [amdgpu] When entering sleep mode the monitors turn off then immediately turn back on
21.10 is still affected by this issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905142 Title: [amdgpu] When entering sleep mode the monitors turn off then immediately turn back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138611] Re: Sky2 ethernet failing randomly with Marvell 88E8056 gigabit
Launchpad has imported 23 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=8962. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-08-30T11:22:39+00:00 gbailey wrote: Most recent kernel where this bug did not occur: Unknown Distribution: CentOS 4.5 Hardware Environment: Intel server board SE7320VP21 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8050 PCI-E ASF Gigabit Ethernet Controller (rev 18) Subsystem: Intel Corporation: Unknown device 3466 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at deefc000 (64-bit, non-prefetchable) [size=16K] I/O ports at b800 [size=256] Expansion ROM at deec [disabled] [size=128K] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Capabilities: [e0] Express Legacy Endpoint IRQ 0 Software Environment: CentOS 4.5 install + "vanilla" kernel 2.6.23-rc4 Problem Description: Discovered while attempting to troubleshoot: https://bugzilla.redhat.com/show_bug.cgi?id=228733 I'm trying to understand the "tx timeout" messages, and how to reproduce them. In my test environment, I have 2 servers, each of which has a sky2 Marvell NIC connected to a switch as "eth0". On server "B", I type "nc -l -p 3409 > /dev/null" On server "A", I type "nc server-B 3409 < /dev/zero" I see lots of traffic from A->B, as would be expected. If I shutdown eth0 on server "B" using "ifdown eth0", wait a few seconds, and then re- enable eth0 on server "B" using "ifup eth0", I see the following in "dmesg" output on server B: sky2 eth0: disabling interface sky2 eth0: enabling interface sky2 eth0: ram buffer 48K sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control rx ip_tables: (C) 2000-2006 Netfilter Core Team As expected... The problem is that server B can occasionally end up in a state where it is unable to ping or access the local subnet anymore. Both "mii-tool" and "ethtool eth0" shows a link present. If I perform "ifdown eth0; ifup eth0" on server B, it doesn't help anything. If I unload the sky2 module, then things clear up and I'm back on the network again. I'm curious about this testcase because the symptom seems to match the earlier "tx timeout" messages; the driver tried to re-enable itself after a timeout, but it's still not able to see any traffic. Steps to reproduce: See "Problem Description" above. While traffic is continuously being transmitted from server "A" to server "B", shutdown the network interface on server "B", and then start the interface on server "B". Monitoring RX traffic on server "B" will indicate when it is no longer receiving the bytes sent from server "A". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/138611/comments/0 On 2007-08-30T13:40:30+00:00 stephen wrote: CentOS has older version of driver please update to latest version from 2.6.22.6 or 2.6.23-rc4. There are several bugs that caused tx timeouts (hung chip), and a problem that led to PHY clock issues. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/138611/comments/1 On 2007-08-30T14:42:09+00:00 gbailey wrote: The kernel version I encountered this on is 2.6.23-rc4, as marked in the bug report and is why I chose CentOS 4.5 install + "vanilla" kernel 2.6.23-rc4" under "Software Environment". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/138611/comments/2 On 2007-09-05T06:35:35+00:00 stephen wrote: Please enable the sky2 debugfs kernel configuration option. Mount debugfs on somewhere (/debug) Hang system then capture sky2 state. (cat /debug/sky2/eth0 >savefile) It will show the status of IRQ and receive/transmit. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/138611/comments/3 On 2007-09-07T13:59:57+00:00 gbailey wrote: Rebuilt 2.6.23-rc5 with SKY2_DEBUG. I've reproduced the issue where ifdown/ifup does not reset the interface properly. # cat /debug/sky2/eth0 IRQ src=0 mask=c01d control=0 Status ring (empty) Tx ring pending=24...24 report=24 done=24 Rx ring hw get=169 put=169 last=1023 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/138611/comments/4 On
[Bug 190587] Re: Local root exploit in kernel 2.6.17 - 2.6.24 (vmsplice)
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=9924.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2008-02-09T15:00:59+00:00 slava wrote:
Latest working kernel version:
Earliest failing kernel version: 2.6.17
Distribution: Gentoo
Hardware Environment:
Software Environment:
Problem Description:
Two root exploits have been reported:
http://milw0rm.com/exploits/5093
http://milw0rm.com/exploits/5092
Both exploits cause kernel Oops or (randomly) give root privilegies to
the user.
Here is the same bug reported in gentoo bugzilla:
http://bugs.gentoo.org/show_bug.cgi?id=209460
Steps to reproduce:
Compile and run the exploit.
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/0
On 2008-02-09T16:30:03+00:00 dsd wrote:
Assuming this is about CVE-2008-0009/10, this is fixed with "[PATCH]
splice: missing user pointer access verification" which is included in
2.6.24.1 and 2.6.23.15. If someone can confirm my assumption, please
close this bug.
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/1
On 2008-02-09T22:01:27+00:00 tm wrote:
It's not properly fixed in 2.6.24.1. E.g. see
http://bugs.gentoo.org/show_bug.cgi?id=209460
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/2
On 2008-02-10T03:19:49+00:00 dsd wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9924
> It's not properly fixed in 2.6.24.1. E.g. see
> http://bugs.gentoo.org/show_bug.cgi?id=209460
Indeed, I can confirm this.
2.6.24.1 fixes this exploit:
http://milw0rm.com/exploits/5093
(labelled "Diane Lane ...")
but does not fix this one, which still gives me root access on 2.6.24.1:
http://milw0rm.com/exploits/5092
("jessica_biel_naked_in_my_bed.c")
alternative link to the still-working exploit:
http://bugs.gentoo.org/attachment.cgi?id=143059=view
Daniel
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/4
On 2008-02-10T03:31:36+00:00 rpilar wrote:
This is NOT fixed in 2.6.24.1:
http://www.securityfocus.com/data/vulnerabilities/exploits/27704.c
But this probably is:
http://www.securityfocus.com/data/vulnerabilities/exploits/27704-2.c (at least
I can't reproduce it).
Linux Rimmer 2.6.24.1 #4 SMP PREEMPT Sat Feb 9 16:50:17 CET 2008 i686
GNU/Linux
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/5
On 2008-02-10T03:31:37+00:00 dsd wrote:
I have personally tested both exploits under a recent 2.6.22 release,
latest 2.6.23 and latest 2.6.24. Results:
http://milw0rm.com/exploits/5093 ("diane_lane")
This was a bug added in 2.6.23, still present in 2.6.24, but fixed by
the most recent -stable releases for both branches:
- Not exploitable in 2.6.22.10
- Not exploitable in 2.6.23.15
- Not exploitable in 2.6.24.1
so this one is done and dusted...
http://milw0rm.com/exploits/5092 ("jessica_biel")
alt link: http://bugs.gentoo.org/attachment.cgi?id=143059=view
This is still exploitable in the latest kernel releases and the exploit
source suggests it has been present since 2.6.17
- Exploitable in 2.6.22.10
- Exploitable in 2.6.23.15
- Exploitable in 2.6.24.1
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/6
On 2008-02-10T04:08:25+00:00 anonymous wrote:
Reply-To: a...@redhat.com
On Sun, Feb 10, 2008 at 11:28:51AM +, Daniel Drake wrote:
> I have personally tested both exploits under a recent 2.6.22 release,
> latest 2.6.23 and latest 2.6.24. Results:
There's a fix/explanation proposed for the other one on linux-kernel
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/7
On 2008-02-10T15:32:01+00:00 dsd wrote:
fixed in Linus' tree as 712a30e63c8066ed84385b12edbfb804f49cbc44
Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/190587/comments/19
On 2021-10-15T17:59:43+00:00 ucelsanicin wrote:
Possibly similar to 23220 however on 64-bit recent Debian sid with
trivial code I see : https://www.webb-dev.co.uk/category/crypto/
mimas$
[Bug 114019] Re: sky2 driver "tx timeout" with large uploads
Launchpad has imported 23 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=8962. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-08-30T11:22:39+00:00 gbailey wrote: Most recent kernel where this bug did not occur: Unknown Distribution: CentOS 4.5 Hardware Environment: Intel server board SE7320VP21 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8050 PCI-E ASF Gigabit Ethernet Controller (rev 18) Subsystem: Intel Corporation: Unknown device 3466 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at deefc000 (64-bit, non-prefetchable) [size=16K] I/O ports at b800 [size=256] Expansion ROM at deec [disabled] [size=128K] Capabilities: [48] Power Management version 2 Capabilities: [50] Vital Product Data Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable- Capabilities: [e0] Express Legacy Endpoint IRQ 0 Software Environment: CentOS 4.5 install + "vanilla" kernel 2.6.23-rc4 Problem Description: Discovered while attempting to troubleshoot: https://bugzilla.redhat.com/show_bug.cgi?id=228733 I'm trying to understand the "tx timeout" messages, and how to reproduce them. In my test environment, I have 2 servers, each of which has a sky2 Marvell NIC connected to a switch as "eth0". On server "B", I type "nc -l -p 3409 > /dev/null" On server "A", I type "nc server-B 3409 < /dev/zero" I see lots of traffic from A->B, as would be expected. If I shutdown eth0 on server "B" using "ifdown eth0", wait a few seconds, and then re- enable eth0 on server "B" using "ifup eth0", I see the following in "dmesg" output on server B: sky2 eth0: disabling interface sky2 eth0: enabling interface sky2 eth0: ram buffer 48K sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control rx ip_tables: (C) 2000-2006 Netfilter Core Team As expected... The problem is that server B can occasionally end up in a state where it is unable to ping or access the local subnet anymore. Both "mii-tool" and "ethtool eth0" shows a link present. If I perform "ifdown eth0; ifup eth0" on server B, it doesn't help anything. If I unload the sky2 module, then things clear up and I'm back on the network again. I'm curious about this testcase because the symptom seems to match the earlier "tx timeout" messages; the driver tried to re-enable itself after a timeout, but it's still not able to see any traffic. Steps to reproduce: See "Problem Description" above. While traffic is continuously being transmitted from server "A" to server "B", shutdown the network interface on server "B", and then start the interface on server "B". Monitoring RX traffic on server "B" will indicate when it is no longer receiving the bytes sent from server "A". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/114019/comments/4 On 2007-08-30T13:40:30+00:00 stephen wrote: CentOS has older version of driver please update to latest version from 2.6.22.6 or 2.6.23-rc4. There are several bugs that caused tx timeouts (hung chip), and a problem that led to PHY clock issues. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/114019/comments/5 On 2007-08-30T14:42:09+00:00 gbailey wrote: The kernel version I encountered this on is 2.6.23-rc4, as marked in the bug report and is why I chose CentOS 4.5 install + "vanilla" kernel 2.6.23-rc4" under "Software Environment". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/114019/comments/6 On 2007-09-05T06:35:35+00:00 stephen wrote: Please enable the sky2 debugfs kernel configuration option. Mount debugfs on somewhere (/debug) Hang system then capture sky2 state. (cat /debug/sky2/eth0 >savefile) It will show the status of IRQ and receive/transmit. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/114019/comments/8 On 2007-09-07T13:59:57+00:00 gbailey wrote: Rebuilt 2.6.23-rc5 with SKY2_DEBUG. I've reproduced the issue where ifdown/ifup does not reset the interface properly. # cat /debug/sky2/eth0 IRQ src=0 mask=c01d control=0 Status ring (empty) Tx ring pending=24...24 report=24 done=24 Rx ring hw get=169 put=169 last=1023 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/114019/comments/9 On
[Bug 787738]
Though Windows (and some Kernel version on Arch) did not present that issue, I got tired and replaced the keyboard FRU 01HX379 with FRU 01HX459 -- good so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 787738]
I can atest that as of today 10/15/2021 this bug is indeed present. I'm using OpenSUSE Tumbleweed with kernel "5.14.9-1-default" this annoying bug for me started arround 2 months ago and it is still present. At first i thought it was some weird hardware failure but i checked on my dmesg and i see the following; [ 115.626674] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost synchronization, throwing 1 bytes away. [ 152.287129] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost synchronization, throwing 1 bytes away. [ 221.063952] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost synchronization, throwing 1 bytes away. [ 649.792306] BTRFS info (device dm-2): qgroup scan completed (inconsistency flag cleared) [ 737.574400] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost synchronization, throwing 1 bytes away. PS: Upon rebooting, at the login screen in sddm i can actually use the trackpoint and its buttons but shoftly after 3-5 seconds i cant use it anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927808] Re: rtw88_8821ce causes freeze
Now at Ubuntu 21.10 (impish) and kernel 5.13.0-19, my Ollee (ProTempo) L116HTN6SPW is "happy". I wonder about other models with the same wireless device... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946667] Re: resolved reports Failed to send hostname reply: Invalid argument
Why is this marked invalid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946667 Title: resolved reports Failed to send hostname reply: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1946667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947424] [NEW] Cannot set pbuilder build locale
Public bug reported: The build locale cannot be set with pbuilder and always defaults to "C" (for both LANG and LC_ALL on Launchpad builds) rather than to "C.UTF-8" as used by sbuild for all official Debian and Ubuntu builds. This causes FTBFS of various packages that depend on the correct locale being set on the build system, often noticeable with the test suites of Python packages for instance. The attached patch changes only five lines of code (pbuilder- buildpackage and pbuilderrc) to allow easy setting of the pbuilder build locale. Based on local testing the patch works as intended, in that packages depending on the correct locale which FTBFS using unpatched pbuilder (yet build successfully with sbuild on Launchpad) now also build successfully with the local patched pbuilder. Please consider applying the patch. ** Affects: pbuilder (Ubuntu) Importance: Undecided Status: New ** Patch added: "allow-setting-pbuilder-build-locale.patch" https://bugs.launchpad.net/bugs/1947424/+attachment/5533328/+files/allow-setting-pbuilder-build-locale.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947424 Title: Cannot set pbuilder build locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928075] Re: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster
I was able to solve this on Ubuntu 20.04 by moving to latest qemu 5 using ``` sudo add-apt-repository ppa:jacob/virtualisation (for Ubuntu 20.04) sudo apt-get update && sudo apt-get install qemu qemu-user qemu-user-static ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928075 Title: Segfault with qemu-aarch64-static doing debootstrap for debian bullseye but not buster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1928075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
This looks like a duplicate of this: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931660 Title: PANIC at zfs_znode.c:339:zfs_znode_sa_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
The change worked on my PC. The difference has been tested with limited changes to my userdata, but I try tomorrow with the next set of updates. The current snapshots are: bertadmin@VM-Xubuntu-2110:~$ zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT bpool/BOOT/ubuntu_q3cgtj@211015-proposed56K - 78.6M - rpool/ROOT/ubuntu_q3cgtj@211015-proposed 54.0M - 3.51G - rpool/ROOT/ubuntu_q3cgtj/srv@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/usr@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/usr/local@211015-proposed 0B - 144K - rpool/ROOT/ubuntu_q3cgtj/var@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/games@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/lib@211015-proposed 300K - 33.6M - rpool/ROOT/ubuntu_q3cgtj/var/lib/AccountsService@211015-proposed56K - 100K - rpool/ROOT/ubuntu_q3cgtj/var/lib/NetworkManager@211015-proposed104K - 140K - rpool/ROOT/ubuntu_q3cgtj/var/lib/apt@211015-proposed 0B - 79.6M - rpool/ROOT/ubuntu_q3cgtj/var/lib/dpkg@211015-proposed 256K - 37.9M - rpool/ROOT/ubuntu_q3cgtj/var/log@211015-proposed 416K - 71.3M - rpool/ROOT/ubuntu_q3cgtj/var/mail@211015-proposed0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/snap@211015-proposed0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/spool@211015-proposed 72K - 112K - rpool/ROOT/ubuntu_q3cgtj/var/www@211015-proposed 0B - 96K - rpool/USERDATA/bertadmin_g64ltk@211015-proposed 1.91M - 177M - rpool/USERDATA/bertadmin_g64ltk@autozsys_6g35l0128K - 176M - rpool/USERDATA/root_g64ltk@211015-proposed 8K - 812K - bertadmin@VM-Xubuntu-2110:~$ That autosys snapshot has been created automatically the first time I did run the next script to create a snapshot: zsysctl save $1 -s zfs list -t snapshot | grep rpool zfs list -t snapshot | grep bpool According to the Internet the next commands would stop all autosys snapshots systemctl --user stop zsys-user-savestate.timer systemctl --user disable zsys-user-savestate.timer sudo mv /etc/apt/apt.conf.d/90_zsys_system_autosnapshot /etc/apt/apt.conf.d /90_zsys_system_autosnapshot_disabled Did I make an error or is it another bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942932] Re: oob_net0 up but stops processing Rx packets
Using 5.4.0-1020-bluefield, this Issue as been fixed: # ifconfig oob_net0 oob_net0: flags=4163 mtu 1500 inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast 192.168.200.255 inet6 prefixlen 64 scopeid 0x20 ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet) RX packets 136 bytes 11177 (11.1 KB) RX errors 0 dropped 3 overruns 0 frame 0 TX packets 64 bytes 6526 (6.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@localhost:~# ifconfig oob_net0 down root@localhost:~# ifconfig oob_net0 up # ifconfig oob_net0 oob_net0: flags=4163 mtu 1500 inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast 192.168.200.255 inet6 prefixlen 64 scopeid 0x20 ether XX:XX:XX:XX:XX:XX txqueuelen 1000 (Ethernet) RX packets 145 bytes 12281 (12.2 KB) RX errors 0 dropped 3 overruns 0 frame 0 TX packets 75 bytes 8438 (8.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942932 Title: oob_net0 up but stops processing Rx packets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425972] Re: Firefox no longer supports -remote parameter
** Changed in: python Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425972 Title: Firefox no longer supports -remote parameter To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/1425972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160413] Re: Wake on LAN (WOL) not working with r8169 driver
Launchpad has imported 118 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=9512. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-12-06T14:02:07+00:00 py.bretecher wrote: Most recent kernel where this bug did not occur:2.6.22 (also a brief test with 2.6.24) Distribution:ubuntu Gutsy AMD64 Hardware Environment:Gigabyte A P35-DSP3 Motherboard Software Environment: Problem Description: I Cannot make WOL (Wake on LAN) work with r8169 driver (Gigabyte A P35-DSP3 Motherboard under Gutsy AMD64). Since I'am slightly game addicted I have a second partition with Windows XP and I can tell that after shutting down from XP WOL is working OK (WOL from my DD-WRT router). After shutting down from Gutsy there is no way to wake up my PC. I have tried many things as suggested in different forums : - adding startup scripts to enable WOL through the "ethtool -s eth0 wol g" command (command is executed without any error and 'ethtool eth0' returns consistent WOL flags) - removing '-i' option on the 'halt' command from the /etc/init.d/halt script - using the Realtek official driver ( r8168 ) in place of the Gutsy provided r8169 - forcing network shutdown (ifdown -a --force) before 'halt' command in /etc/init.d/halt script ethtool output : Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) Link detected: yes lspci -nn output : 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01) Steps to reproduce: N/A I have submitted the bug under launchpad (https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413) and I have been advised to open a bug report here. Regards. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413/comments/7 On 2007-12-06T14:12:36+00:00 akpm wrote: > Most recent kernel where this bug did not occur:2.6.22 (also a brief test > with > 2.6.24) Eh? You say this bug is present in 2.6.22 and is also not present in 2.6.22 and 2.6.24. Wanna try again? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413/comments/8 On 2007-12-06T14:25:09+00:00 py.bretecher wrote: OK, you're completely right, there's a flaw in my report : The bug DID occur in 2.6.22 (Gutsy) and 2.6.24 (Hardy alpha) and I haven't found until now any configuration that works. Sorry for this inconsistency. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413/comments/9 On 2007-12-06T15:10:05+00:00 romieu wrote: Pierre Yves: [...] > - using the Realtek official driver ( r8168 ) in place of the Gutsy provided > r8169 It made no difference, right ? -- Ueimor Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413/comments/10 On 2007-12-06T15:12:33+00:00 romieu wrote: Created attachment 13898 Hardcoded wol hack Completely untested. I'll rework it if it kinda works. -- Ueimor Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413/comments/11 On 2007-12-06T15:41:55+00:00 py.bretecher wrote: Yes, using r8168 from Realtek (r8168-8.003.00) does not work better. I'll try your patch this WE. Thanks a lot. PY Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.22/+bug/160413/comments/12 On 2007-12-08T12:10:44+00:00 py.bretecher wrote: When I apply the patch to the r8169.c of my 2.6.22 source tree revision (patch warns me about a fuzz but it seems to work), I can compile the module and it loads without any problem... but when I shutdown, I cannot wake my machine through the magic packet method (which always works when I shutdown from XP). If I try to compile the r8169.c from git (head) after apply your patch (no warning), I have an error when compiling the module : py@PC-FIXE2:/usr/src/linux-source-2.6.22$ sudo make
[Bug 1938908] Re: Backport the container stack in Impish
I was able to use basically the same patch used in Impish to fix the golang-github-containers-buildah build failure in Hirsute, just needed to do some refresh. Debdiff is attached. ** Patch added: "golang-github-containers-buildah.debdiff" https://bugs.launchpad.net/ubuntu/hirsute/+source/golang-github-containers-buildah/+bug/1938908/+attachment/5533326/+files/golang-github-containers-buildah.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
For golang-github-containers-common in Hirsute, I was able to backport an upstream patch to fix the build. However, it depends on golang- github-containers-storage version that I attached in the debdiff above ** Patch added: "golang-github-containers-common.debdiff" https://bugs.launchpad.net/ubuntu/hirsute/+source/golang-github-containers-buildah/+bug/1938908/+attachment/5533325/+files/golang-github-containers-common.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts
Using 5.4.0-1020-bluefield, this Issue has been fixed: # ethtool -S oob_net0 NIC statistics: hw_access_errors: 0 tx_invalid_checksums: 0 tx_small_frames: 3 tx_index_errors: 0 sw_config_errors: 0 sw_access_errors: 0 rx_truncate_errors: 0 rx_mac_errors: 0 rx_din_dropped_pkts: 0 tx_fifo_full: 0 rx_filter_passed_pkts: 729 rx_filter_discard_pkts: 13 mac_intr_count: 3 rx_intr_count: 725 llu_plu_intr_count: 0 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943065] Re: mlxbf_gige: update driver version to 1.25
Using 5.4.0-1020-bluefield, this Issue has been fixed: # modinfo mlxbf_gige filename: /lib/modules/5.4.0-1020-bluefield/kernel/drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige.ko version:1.25 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919026] Re: cinnamon-settings-users: User dialog holds if user creates a user that already exists
I'm not that interested in groovy/hirsute, but feel free to play with it if you *really* wish. ** Patch added: "cinnamon_4.8.6-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+attachment/5533324/+files/cinnamon_4.8.6-2ubuntu0.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919026 Title: cinnamon-settings-users: User dialog holds if user creates a user that already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919026] Re: cinnamon-settings-users: User dialog holds if user creates a user that already exists
** Description changed: - In the user creation dialog if you create a user that already exists (or - try to), a GLib.Error is thrown and the dialog holds. I will make a - patch for this. + [Impact] + + * In the user creation dialog if you create a user that already exists + (or try to), a GLib.Error is thrown and the dialog holds. + + * While of course someone could see a user exists, it's better to maybe + not have someone try to make a user named 'root', 'sudo', 'linux', 'etc' + and watch Python mess up and think they screwed up their system. + + * This patch checks that the user exists when the information changes + and will adjust to not allow the user to be created (while giving a + helpful warning + + [Test Plan] + + * Boot up Cinnamon < 5.0.0 + + * Run cinnamon-settings-users, and enable root if you must + + * Try to create a user, type in a username, your own or another + existing one, and see that when trying to add it the application hangs. + + [Where problems could occur] + + * Nothing too big except the normal fact that we are using Python. + Python breakage to always happen (an update, syntax error, etc.) + + * Another patch that plays with cinnamon-settings, cinnamon-settings- + users, or critically the AccountsService or any part of the library that + is adjusted can mess up things. + + * Regression is unlikely, but still possible due to the world of + Python, and definitely AccountsService in this GTK4/libraries world with + Impish specifically + + [Other Info] + + * Two patches - one to fix and one for translations fixing Affected: Focal - Cinnamon 4.4.8 Impish - Cinnamon 4.8.6 - Jammy - Solved in Debian Unstable - Cinnamon 5.0.5 (Debian #985138) + Jammy - Fixed in the current unstable, 5.0.5. Check Debian #985138 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cinnamon 4.6.7-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 13 09:14:42 2021 InstallationDate: Installed on 2020-10-23 (141 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cinnamon UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919026 Title: cinnamon-settings-users: User dialog holds if user creates a user that already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947417] [NEW] Touchpad not recognized after BIOS update
Public bug reported: The touchpad of my Lenovo IdeaPad Flex 3 11ADA05 stopped working after an BIOS upgrade from FPCN21WW to FPCN24WW. (Here is the changelog of FPCN24WW: https://download.lenovo.com/consumer/mobiles/fpcn24ww.txt ) The touchpad is no longer detected. It doesn't appear in 'xinput list' or '/proc/bus/input/devices' in Ubuntu 21.10, 21.04 or 20.04. With the old Bios it appeared as "MSFT0001:00 04F3:3072". This Bug was also reported regarding archlinux ( https://bbs.archlinux.org/viewtopic.php?id=269900 ) some weeks ago, but there are no replies yet. It would be great if someone could help me with this problem. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947417 Title: Touchpad not recognized after BIOS update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
The attached debdiff fixed the API incompatibility in golang-github- containers-storage in Hirsute. ** Patch added: "golang-github-containers-storage-hirsute.debdiff" https://bugs.launchpad.net/ubuntu/hirsute/+source/golang-github-containers-buildah/+bug/1938908/+attachment/5533319/+files/golang-github-containers-storage-hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947055] Re: engrampa no longer opens rar files
Norbert rar: Installed: (none) Candidate: 2:5.5.0-1build1 Version table: 2:5.5.0-1build1 500 500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages unrar: Installed: 1:5.6.6-2build1 Candidate: 1:5.6.6-2build1 Version table: *** 1:5.6.6-2build1 500 500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages 100 /var/lib/dpkg/status unrar-free: Installed: (none) Candidate: 1:0.0.1+cvs20140707-4 Version table: 1:0.0.1+cvs20140707-4 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages p7zip-rar: Installed: (none) Candidate: 16.02-3build1 Version table: 16.02-3build1 500 500 http://us.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947055 Title: engrampa no longer opens rar files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/engrampa/+bug/1947055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947364] Re: mt76 module disagrees on a lot
Well Issue does not appear when you make a clean installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947364 Title: mt76 module disagrees on a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919026] Re: cinnamon-settings-users: User dialog holds if user creates a user that already exists
** Description changed: In the user creation dialog if you create a user that already exists (or try to), a GLib.Error is thrown and the dialog holds. I will make a patch for this. Affected: Focal - Cinnamon 4.4.8 - Groovy - Cinnamon 4.6.7 - Hirsute - current unstable. Check Debian #985138 + Impish - Cinnamon 4.8.6 + Jammy - Solved in Debian Unstable - Cinnamon 5.0.0 (Debian #985138) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cinnamon 4.6.7-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 13 09:14:42 2021 InstallationDate: Installed on 2020-10-23 (141 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cinnamon UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: In the user creation dialog if you create a user that already exists (or try to), a GLib.Error is thrown and the dialog holds. I will make a patch for this. Affected: Focal - Cinnamon 4.4.8 Impish - Cinnamon 4.8.6 - Jammy - Solved in Debian Unstable - Cinnamon 5.0.0 (Debian #985138) + Jammy - Solved in Debian Unstable - Cinnamon 5.0.5 (Debian #985138) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cinnamon 4.6.7-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 13 09:14:42 2021 InstallationDate: Installed on 2020-10-23 (141 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cinnamon UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919026 Title: cinnamon-settings-users: User dialog holds if user creates a user that already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1919026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 414679] Re: firefox print - page margins
Launchpad has imported 16 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=418271. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-02-18T18:40:23+00:00 Jürgen 'jiha' Harter wrote: With bug 193001 the old File ->Page Setup Dialog was replaced with the system's gnome dialog. Options not provided by the system's dialog should have been shifted to a custom options tab in the new print dialog (File ->Print ->Options). However the possibility of setting borders of the pages sent by Mozilla to the system's print system is missing. And Mozilla does not not recognize the page borders provided by the system. Actually I don't know whether it could get the border settings from i.e. the CUPS settings at all. We need the possibility to set the borders of the pages sent to the printing system. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/0 On 2008-02-18T18:42:00+00:00 Jürgen 'jiha' Harter wrote: Maybe this bug is a dupe of bug 192999 or it should depend on it. But I'm not really sure. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/1 On 2008-02-18T18:45:13+00:00 Jürgen 'jiha' Harter wrote: (In reply to comment #0) > We need the possibility to set the borders of the pages sent to the printing > system. The old functionality could/should be provided in the options tab of the new print dialog. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/2 On 2008-02-18T23:21:00+00:00 Ventnor-bugzilla wrote: You can set margins by making a custom paper size in the Page Setup, which is how it is usually done in GNOME apps. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/3 On 2008-02-27T22:48:03+00:00 Kairo-kairo wrote: That's very unintuitive, I don't think that normal, non-tech users even find that (heck, even I didn't) - apart from the known problems with custom paper sizes and various printer drivers. I don't even think that people will find that they can't change the paper format in the print dialog like everywhere else, but only via page setup. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/4 On 2008-10-05T20:56:35+00:00 Elmar-ludwig wrote: *** Bug 417391 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/5 On 2008-10-05T20:59:00+00:00 Elmar-ludwig wrote: *** Bug 458609 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/6 On 2010-04-09T16:47:12+00:00 Unghost-mozilla-russia wrote: *** Bug 509720 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/8 On 2012-07-03T20:23:20+00:00 Norbert wrote: Bump! It's 2012. Firefox 13.0.1 still does not have page margins, headers, footers settings. Please fix this issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/9 On 2013-08-09T11:33:49+00:00 Machinegodzilla wrote: Firefox 21. Setting margin settings still buried deep. Only found out how to do it while searching if there is a bug against that. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/10 On 2014-11-29T22:04:45+00:00 Hb-calen wrote: *** Bug 783079 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/11 On 2017-03-12T10:41:03+00:00 Norbert wrote: Bug exists in Firefox 52. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/414679/comments/12 On 2017-03-12T10:46:18+00:00 Norbert wrote: Found bug report on launchpad, which is 8 years old, was about Firefox 3.0 -
[Bug 1938908] Re: Backport the container stack in Impish
For opengcs in Hirsute, the patch used in Impish applied cleanly. Debdiff attached. ** Patch added: "opengcs-hirsute.debdiff" https://bugs.launchpad.net/ubuntu/hirsute/+source/golang-github-containers-buildah/+bug/1938908/+attachment/5533318/+files/opengcs-hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947414] [NEW] Update version to >= 0.31.3
Public bug reported: Package (even in jellyfish) is outdated. Current version is 0.31.3 https://github.com/digint/btrbk/releases ** Affects: btrbk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947414 Title: Update version to >= 0.31.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrbk/+bug/1947414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947415] [NEW] A blackscreen is displayed after login.
Public bug reported: A blackscreen is displayed after login. This error happens with Xorg and Wayland. The only way to get the ubuntu-desktop to work is login into textmode and then running startx. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-desktop 1.472 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Oct 15 15:25:16 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947415 Title: A blackscreen is displayed after login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705099] Re: Kernel 4.13-rc1 with custom patch for troubleshooting
Launchpad has imported 128 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=192591. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-01-15T01:46:43+00:00 davidnmfarrell wrote: Created attachment 251631 dmesg I've installed Fedora 25 on a Dell XPS 13 9365 (2 in 1) laptop. Duel booted with Windows, secure boot is enabled, SATA mode is ACPI, and it boots fine. Everything works - sound, trackpad, wifi etc, without issue. However suspending the machine does not work; the screen goes blank and it appears that the machine is entering sleep mode, but the power button remains lit, and it never seems to completely finish suspending. The behavior is the same with STI and STR, via these commands: echo > freeze /sys/power/state echo > mem /sys/power/state Booting the kernel into runlevel 3 makes no difference - the behavior is the same. Disabling async module power down also did not change the behavior; using this command: echo 0 > /sys/power/pm_async The kernel was booted with the following additional options: initcall_debug no_console_suspend ignore_loglevel 3 dyndbg=\\\"file suspend.c +p\\\". No change in behavior was seen. Attached are the outputs of various Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/0 On 2017-01-15T01:47:15+00:00 davidnmfarrell wrote: Created attachment 251641 lspci Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/1 On 2017-01-15T01:47:35+00:00 davidnmfarrell wrote: Created attachment 251651 lsmod Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/2 On 2017-01-15T01:48:20+00:00 davidnmfarrell wrote: Created attachment 251661 boot-config Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/3 On 2017-01-15T01:48:38+00:00 davidnmfarrell wrote: Created attachment 251671 lspci Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/4 On 2017-01-15T01:52:14+00:00 davidnmfarrell wrote: Exact same behavior is seen under kernel 4.8.6-300.fc25.x86_64. I should add: I can press the power button for a few seconds, and the system "resumes" (it doesn't appear to ever finish suspending). But closing/opening the lid, pressing keys or moving the trackpad does not resume. Only pressing the power button triggers the "resume". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/5 On 2017-01-16T02:05:35+00:00 yu.c.chen wrote: Could you please check if it still exist on latest upstream kernel, we mainly track upstream version rather than distribute version. If it is still there, you can use /sys/power/pm_test to figure out at which phase it failed. thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/6 On 2017-01-16T02:06:00+00:00 rui.zhang wrote: (In reply to davidnmfarrell from comment #0) > However suspending the machine does not work; the screen goes blank and it > appears that the machine is entering sleep mode, but the power button > remains lit, blink or lit? (In reply to davidnmfarrell from comment #5) > Exact same behavior is seen under kernel 4.8.6-300.fc25.x86_64. > > I should add: I can press the power button for a few seconds, and the system > "resumes" (it doesn't appear to ever finish suspending). please attach the dmesg after the system "resumes" we can check kernel log to see if it is a real suspend. BTW, you said press the power button for a few seconds? what if you press the button and release it immediately? > But closing/opening > the lid, pressing keys or moving the trackpad does not resume. Only pressing > the power button triggers the "resume". For STI only or for both STR and STI? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705099/comments/7 On 2017-01-16T02:38:58+00:00 davidnmfarrell wrote: (In reply to Zhang Rui from comment #7) > blink or lit? lit, constant light (no blinking) > BTW, you said press the power button for a few seconds? what if you press > the button and release it immediately? Nothing happens > For STI only or for both STR and STI? For
[Bug 1938074] Re: package ubuntu-advantage-tools 27.1~16.04.2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 This appears to be a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938074 Title: package ubuntu-advantage-tools 27.1~16.04.2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
The following packages regressed because of a libcontainer API change in runc: # Hirsute - opengcs - golang-github-containers-storage - golang-github-containers-common - golang-github-containers-buildah # Focal - opengcs - golang-github-containers-storage I'll be adding tasks for each of them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
golang-github-docker-go-connections is also blocking runc in Hirsute but the fix is sitting in proposed for a while but should be fixed once the new version of golang-github-containers-images disabling LTO is accepted. More info here: https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go- connections/+bug/1930891 ** Also affects: opengcs (Ubuntu) Importance: Undecided Status: New ** Changed in: opengcs (Ubuntu) Status: New => Invalid ** Changed in: opengcs (Ubuntu Focal) Status: New => Triaged ** Changed in: opengcs (Ubuntu Hirsute) Status: New => Triaged ** Also affects: golang-github-containers-storage (Ubuntu) Importance: Undecided Status: New ** Changed in: golang-github-containers-storage (Ubuntu) Status: New => Invalid ** Changed in: golang-github-containers-storage (Ubuntu Focal) Status: New => Triaged ** Changed in: golang-github-containers-storage (Ubuntu Hirsute) Status: New => Triaged ** Also affects: golang-github-containers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: golang-github-containers-common (Ubuntu) Status: New => Invalid ** Changed in: golang-github-containers-common (Ubuntu Hirsute) Status: New => Triaged ** Changed in: golang-github-containers-common (Ubuntu Focal) Status: New => Invalid ** Changed in: golang-github-containers-common (Ubuntu Bionic) Status: New => Invalid ** Changed in: golang-github-containers-storage (Ubuntu Bionic) Status: New => Invalid ** Also affects: golang-github-containers-buildah (Ubuntu) Importance: Undecided Status: New ** Changed in: golang-github-containers-buildah (Ubuntu) Status: New => Invalid ** Changed in: golang-github-containers-buildah (Ubuntu Bionic) Status: New => Invalid ** Changed in: golang-github-containers-buildah (Ubuntu Focal) Status: New => Invalid ** Changed in: golang-github-containers-buildah (Ubuntu Hirsute) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946532] Re: package ubuntu-advantage-tools 27.2.2~18.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 Thank you for the bug report! This appears to be a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946532 Title: package ubuntu-advantage-tools 27.2.2~18.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1946532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946608] Re: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 Thank you for the bug report! This appears to be a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946608 Title: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1946608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939330] Re: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 ** This bug is no longer a duplicate of bug 1938290 package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939330 Title: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1939330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938290] Re: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 This appears to be a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938290 Title: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946034] Re: https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946034 Title: https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1946034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944700] Re: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 This appears to be a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944700 Title: package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1944700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936683] Re: package ubuntu-advantage-tools 27.1~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 ** This bug is no longer a duplicate of bug 1934077 package ubuntu-advantage-tools 27.1~16.04.1 - ModuleNotFoundError: No module named 'uaclient' - maybe dup 1930121 ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936683 Title: package ubuntu-advantage-tools 27.1~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1936683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934077] Re: package ubuntu-advantage-tools 27.1~16.04.1 - ModuleNotFoundError: No module named 'uaclient' - maybe dup 1930121
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 I'm going to mark this a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934077 Title: package ubuntu-advantage-tools 27.1~16.04.1 - ModuleNotFoundError: No module named 'uaclient' - maybe dup 1930121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1934077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927905] Re: package ubuntu-advantage-tools 27.0~16.04.1 - ModuleNotFoundError: No module named 'uaclient' - maybe dup 1930121
*** This bug is a duplicate of bug 1930121 *** https://bugs.launchpad.net/bugs/1930121 In the absence of more information I'm going to mark this a duplicate of bug 1930121. For now, the likely quick fix is to set PYTHONPATH=/usr/lib/python3/dist-packages We will release a proper fix in ubuntu-advantage-tools in a coming release. ** This bug has been marked a duplicate of bug 1930121 package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927905 Title: package ubuntu-advantage-tools 27.0~16.04.1 - ModuleNotFoundError: No module named 'uaclient' - maybe dup 1930121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration
Sorry, the debdiff above is incorrect. The golang-github-containers- image package in hirsute was uploaded disabling LTO here: https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github- containers-image/+bug/1938908/comments/28 Once this is accepted, we will be able to land this update which is also blocking the container stack SRU one more time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930891 Title: FTBFS in Hirsute is blocking runc migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration
This is hitting us again while backporting the container stack: https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github- containers-image/+bug/1938908 I'll disable LTO to make it build fine on the failing architectures. Debdiff attached. ** Patch added: "golang-github-docker-go-connections.debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5533314/+files/golang-github-docker-go-connections.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930891 Title: FTBFS in Hirsute is blocking runc migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
Olivier, I am not sure what is the reasoning here. That you obviously want to land this in a non-LTS version has nothing to do with the fact the base product is not ready and that the change was announced unacceptably late here. The Flutter-based installer is a nice example. You can obviously develop something for years ánd still land it in a non-LTS. Locking out users is not just about "the deb still being available". Some people will have the snap, others the deb, and others both. If they have both I have no idea which one is run when they click the FF icon. The upgrade scenario you mention in comment #7 does not seem to be the real world case either. We just got teleported back in time, where the only way for our helpdesk to know what happens when a user calls the helpdesk, is to open a terminal and run "apt-get" and "ps aux". This is a support hell, especially at scale. Because of a non-critical move to another package format. And so far no guarantees on the LTS either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
Thanks for the review Sergio, package uploaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
The attached debdiff should fix the issue pointed above. ** Patch added: "golang-github-containers-image.debdiff" https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-containers-image/+bug/1938908/+attachment/5533309/+files/golang-github-containers-image.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
Thanks for the patch, Lucas. LGTM, +1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
There is a golang-github-containers-image/5.10.3-1ubuntu1 regression in hirsute which is not directly caused by docker.io but it is blocking it. The tests are failing only on arm64, ppc64el and s390x due to LTO. The simple fix here is disabling LTO in this package. ** Also affects: golang-github-containers-image (Ubuntu) Importance: Undecided Status: New ** Changed in: golang-github-containers-image (Ubuntu) Status: New => Invalid ** Changed in: golang-github-containers-image (Ubuntu Hirsute) Status: New => Triaged ** Changed in: golang-github-containers-image (Ubuntu Focal) Status: New => Invalid ** Changed in: golang-github-containers-image (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Hi, I really do not remember any more how that somehow disappeared. Could it be that changing the channel at the wifi router could help? Unfortunately I did not remember that I reported the problem otherwise I would have immediately reported a possible workaround. Best regards, Martin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947394] Re: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned
** Package changed: ca-certificates (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947394 Title: package ca-certificates 20210119ubuntu0.21.04.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1947394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947348] Re: i was installing ubunto on my device than it said my installation is crashed n idk what to do
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947348 Title: i was installing ubunto on my device than it said my installation is crashed n idk what to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1947348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947362] Autopkgtest regression report (debootstrap/1.0.123ubuntu6.1)
All autopkgtests for the newly accepted debootstrap (1.0.123ubuntu6.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: pbuilder/0.231build1 (arm64, ppc64el, s390x, amd64) sbuild/0.81.2ubuntu5 (arm64, ppc64el, s390x, amd64) lava/2020.12-1ubuntu2 (arm64) piuparts/1.1.2 (arm64, ppc64el, s390x, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947362 Title: Add Ubuntu Jammy as a known release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1947362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878457] Re: Window shrinks on switching focus
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878457 Title: Window shrinks on switching focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1878457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947408] [NEW] Xorg freeze
Public bug reported: My system completely freezes requiring a hard reset if I do the following: 1. Launch Runelite (Installed using "snap install runelite") 2. Right click on the Runelite icon on the sidebar 3. System freezes ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 15 13:43:37 2021 DistUpgraded: 2021-10-14 15:16:12,934 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1043:0521] InstallationDate: Installed on 2021-07-08 (99 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: MSI MS-7850 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.13.0-19-generic root=UUID=dd4950a5-dc48-42ca-a4ff-e804e6199425 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd07/21/2014:br4.6:svnMSI:pnMS-7850:pvr1.0:skuTobefilledbyO.E.M.:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947408 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1947408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947311] Re: Cloud init ignores growpart off on impish for raspberry pi
Thank you for filing a bug and making cloud-init and Ubuntu better. Can you run `sudo cloud-init collect-logs` and attach that tarfile to this bug for ease of triage? Note that cloud-init collect-logs potentially grabs user-data. If you have sensitive credentials defined in your user- data, please check and redact as necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Cloud init ignores growpart off on impish for raspberry pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
> I just found that this problem is not present in Debian testing Indeed, Xwayland is living on Debian/testing and ibus-daemon is restarted with --xim by gnome-shell. However xlsclients show only ibus-x11/gsd-xsettings/gnome-shell only. Is any X11 related process started and then closed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942929] Re: [SRU] ubuntu-advantage-tools (27.2.2 -> 27.3) Xenial, Bionic, Focal, Hirsute
Thank you Steve, you raise several good points. 1. The excessive nesting. I agree that it is annoying to read several layers of nested ifs. As an individual issue, we don't think this is a blocker; however if we decide to rewrite this function for this SRU for the below reasons, we can use the early return like you suggest. If not, then we will simplify this for next release. 2. The check for deb-systemd-helper existing. There's a longer story as to why we thought this check was a good idea at the time, but the end result is that we were mistaken and it is superfluous. We don't think this check hurts anything but it doesn't help either. We can remove it in our next release unless you think it blocks this one. 3. The check for systemd existing. This is present because we were copying a pattern that deb-systemd-helper uses in its autosnippets. Whenever d-s-h appends a snippet that uses systemctl, it makes this check first. For example, a snippet that is added to our postinst by d-s-h: # Automatically added by dh_systemd_start if [ -d /run/systemd/system ]; then systemctl --system daemon-reload >/dev/null || true deb-systemd-invoke start ua-timer.timer >/dev/null || true fi # End automatically added section However, it turns out our use of systemctl in this case is also unnecessary. We don't need to run systemctl stop in this case because ua-timer.timer will never have been started when this chunk of code runs. Again, this shouldn't hurt anything. We can remove it in our next release unless you think it blocks this one. 4. Running deb-systemd-helper enable is confusing. The use of enable was intentional. We attempted to explain in the comment above that line. The reason is that we want to take advantage of d-s-h's autosnippet for enabling/updating config for ua-timer.timer which appends the following to the bottom of postinst: # Automatically added by dh_systemd_enable # This will only remove masks created by d-s-h on package removal. deb-systemd-helper unmask ua-timer.timer >/dev/null || true # was-enabled defaults to true, so new installations run enable. if deb-systemd-helper --quiet was-enabled ua-timer.timer; then # Enables the unit on first installation, creates new # symlinks on upgrades if the unit file has changed. deb-systemd-helper enable ua-timer.timer >/dev/null || true else # Update the statefile to add new symlinks (if any), which need to be # cleaned up on purge. Also remove old symlinks. deb-systemd-helper update-state ua-timer.timer >/dev/null || true fi # End automatically added section The chunk of code that we are talking about happens before this d-s-h autosnippet, and the intent is to prevent this d-s-h snippet from running "enable". By running "enable" and then "disable" we update the d-s-h state such that "was-enabled" will fail and so that snippet will not run "enable". We acknowledge that this solution is confusing, to put it charitably. We've evaluated a number of alternatives: 4.1. Straightforward simplification deb-systemd-helper enable $UA_TIMER_NAME > /dev/null 2>&1 || true deb-systemd-helper disable $UA_TIMER_NAME > /dev/null 2>&1 || true This is the same solution but more consistent in its use of d-s-h for tooling. We think this reads better but is not a significant improvement on what is currently there. We'll simplify to this solution in the next release. 4.2. Rely on d-s-h implementation details touch /var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/ua-timer.timer This avoids needlessly enabling and disabling, but relies on the implementation detail of d-s-h that it won't enable if this file is present. It seems more fragile than the existing solution. 4.3 Rely on incidental behavior of update-state deb-systemd-helper update-state ua-timer.timer >/dev/null || true This command would set the d-s-h state appropriately to avoid enabling the timer, but it is not the command's intended purpose. We think this is at least as confusing as the existing solution and could be fragile as well. 4.4 We stop relying on `dh_systemd_enable -pubuntu-advantage-tools ua- timer.timer` and instead write the d-s-h enable code ourselves in postinst (and the other operations it provides in preinst, prerm, postrm). This shifts all of the ua-timer.timer management responsibility from d-s-h to us, the ua devs, and seems like an unnecessary burden just to make this use case more straightforward. A note on this use case: This snippet of code is only run for users who have previously disabled ua-messaging.timer, which has only existed for ~6 months. We expect the number of users this affects to be very low. With this snippet, we are trying to carry their preference forward to the new timer, and it works as written. We're not sure it is worth too much more effort to make the solution more efficient or cleaner for this small edge case. Overall, all of the issues you've pointed out
Re: [Bug 1947018] Re: Does not let me execute any command via GUI or CLI
Hi, Thank you for your response. I think root cause is only one. Its just causing different problems. I tried connecting other(new) mouse and keyboard but nothing worked. Also this weird behaviour started exactly when I enabled Livepatch. On Thu, Oct 14, 2021 at 11:50 AM Daniel van Vugt <1947...@bugs.launchpad.net> wrote: > Thanks for the bug report. It sounds like you have multiple issues so > please open separate bugs for each one. > > It also sounds like you might have a faulty mouse or keyboard plugged in > with a button stuck down that you're not aware of. Try unplugging both > the mouse and keyboard and plug in some other ones. > > ** Package changed: xorg (Ubuntu) => ubuntu > > ** Changed in: ubuntu >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1947018 > > Title: > Does not let me execute any command via GUI or CLI > > Status in Ubuntu: > Incomplete > > Bug description: > There are few problems that started on display. Note: There is no > image distortion or breaks or no blue/black screen. > > Examples of issues that I have been experiencing are as follows- > > 1. Characters get deleted when I type, especially when I hit Spacebar. > Tried to toggle Insert but didn't help. > 2. Something, I dont know what, does not let me use right click pop > window. It disappears instantly. e.g right click on desktop screen, drop > down click to power off, or right click to application in taskbar etc. > 3. If I try to launch activities, it disappears instantly. I try > multiple time but it won't let me access it. > 4. Commands do not appear as I type in Terminal. For example, when I > type 'sudo apt-get update', the terminal takes only sudo, and does not > allow me to enter character further and then executes just 'sudo' command. > 5.Netflix/Youtube on Chrome will not let me maximise the screen. If I do > so it instantly reverts to small/default screen. > 6. All of a sudden, especially Netflix window will start flickering, and > would not resolve unless I power off and start again. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 > Uname: Linux 5.4.0-88-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.20 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 13 23:00:30 2021 > DistUpgraded: 2021-01-21 16:29:36,380 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)) > DistributionChannelDescriptor: ># This is the distribution channel descriptor for the OEM CDs ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor > > canonical-oem-somerville-bionic-amd64-20180608-47+bison-elk-cougar-mlk+X54 > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: oem-pci-sunix-1769839-xenial-osp1, 2.0.4.4ubuntu2, > 4.15.0-1080-oem, x86_64: installed (WARNING! Diff between built and > installed module!) > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 > [VGA controller]) > Subsystem: Dell UHD Graphics 630 (Desktop) [1028:092f] >Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 > 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) > Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] > [1028:1711] > InstallationDate: Installed on 2019-10-03 (741 days ago) > InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary > 20180608-09:38 > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Dell MS116 USB > Optical Mouse >Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M >|__ Port 1: Dev 2, If 1, Class=Human Interface Device, > Driver=usbhid, 12M >|__ Port 1: Dev 2, If 0, Class=Human Interface Device, > Driver=usbhid, 12M >|__ Port 10: Dev 3, If 0, Class=Human Interface Device, > Driver=usbhid, 1.5M > MachineType: Dell Inc. OptiPlex 5070 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic > root=UUID=e9c0c50d-bbd2-4ca2-8775-47eccf91a03e ro mem_sleep_default=deep > quiet splash vt.handoff=7 > SourcePackage: xorg >
[Bug 1947405] Re: pm-suspend does not lock screen
Oh! On the 18.04 machine I actually executed: `xfce4-session-logout --suspend` Now realizing this, I'm asking myself if this issue should be closed since "pm-suspend" isn't supposed to lock, because that's "xflock4" job, right? :| Sorry for the noise. Yet, I hope it may at least point others towards "xfce4-session-logout" when suspending by command :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947405 Title: pm-suspend does not lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1947405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561497] Re: XML error: No PCI buses available when defining MIPS VM
Issue still present when attempting to create MIPS guest via virt- manager, and adding additional environments with same issue (virt- install and openstack nova leveraging libvirt). Attempts were made across multiple paths still receiving same error message 'XML error: No PCI buses available' when trying to define a VM using mips64el architecture. System Information: Description: Ubuntu Focal Fossa Release: 20.04.3 LTS Linux version 5.4.0-88-generic (buildd@lgw01-amd64-008) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 (Ubuntu 5.4.0-88.99-generic 5.4.140) Binary Information: /usr/sbin/libvirtd libvirtd (libvirt) 6.0.0 XML and Trace Errors: - virt-install attempt ### https://pastebin.com/nuPPieaw Error Message: ERRORXML error: No PCI buses available - virt-manager attempt ### https://pastebin.com/camUditW Error Message: libvirt.libvirtError: XML error: No PCI buses available - openstack attempt ### https://pastebin.com/3Tsj7Cxz ### https://pastebin.com/6VunTvpy Error Message: libvirt.libvirtError: XML error: No PCI buses available reference for original patch details: https://listman.redhat.com/archives/libvir-list/2016-May/msg00197.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561497 Title: XML error: No PCI buses available when defining MIPS VM To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1561497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
Yesterday evening I upgraded my laptop to Ubuntu 20.10, so today I tried the same on my HP Elitebook 8460p laptop based on an i5-2520M and there conky displayed as I expected. Also I had no flickering of top-bar and Ubuntu dock with VMs or videos in full screen. By the way that flickering also occurs with Xorg in my Ryzen 3 2200G. Maybe we have to spit both issues in 2 bug reports? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947405] [NEW] pm-suspend does not lock screen
Public bug reported: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947405 Title: pm-suspend does not lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1947405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947362] Autopkgtest regression report (debootstrap/1.0.118ubuntu1.5)
All autopkgtests for the newly accepted debootstrap (1.0.118ubuntu1.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: piuparts/1.1.1build1 (amd64, s390x, arm64, ppc64el) docker.io/20.10.7-0ubuntu1~20.04.2 (arm64) sbuild/0.79.0-1ubuntu1 (amd64, s390x, arm64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947362 Title: Add Ubuntu Jammy as a known release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1947362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
