[Bug 1894221] Re: system is not able to recognize touchpad
touchpad is not showing in mouse and touchpad setting. Also touchpad not showing in xinput list command output. ** Attachment added: "Screenshot from 2020-10-01 12-15-45.png" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1894221/+attachment/5415974/+files/Screenshot%20from%202020-10-01%2012-15-45.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894221 Title: system is not able to recognize touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1894221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526093] Re: /usr/bin/totem:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect
No crashes since 18.10. Consider it fixed. ** Changed in: totem (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/1526093 Title: /usr/bin/totem:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1526093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526093] Re: /usr/bin/totem:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect
love it thank for the valuable information… https://www.walgreenslistens.mobi/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526093 Title: /usr/bin/totem:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1526093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898010] Re: pcmanfm should use git for file operations if containing folder is part of a git repository
Thank you for taking the time to report this issue and helping to make Ubuntu better. `pcmanfm` used GTK2 libs so is mostly seen as depreciated. Please note `pcmanfm` was used by Lubuntu up to and including Lubuntu 18.04 LTS, being replaced by `pcmanfm-qt` for later releases. The main developer PCman (https://github.com/PCMan) now works on `pcmanfm-qt` so the chance of action on this is rather limited. If you mean the now `pcmanfm-qt` package, you've filed against a legacy package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898010 Title: pcmanfm should use git for file operations if containing folder is part of a git repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1898010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897942] Re: crash on brcmfmac
** Description changed: I have Ubuntu 20.04 64bit, ubuntu desktop, network-manager on RPI4 8GB wifi work well for some time but then all gone very slow and system is unusable. to me it seems a brcmfmac module problem. - My power configuration do not go well if switch off - "wi-fi can be turn off to power save": all wifi chash. + My power configuration do not go well if switch off + "wi-fi can be turn off to power save": all wifi crash. - Rest of my power conf: + Rest of my power conf: automatic suspend = no action on turn off supply button = nothing black screen = never -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897942 Title: crash on brcmfmac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1897942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898008] Re: [Errno5] Input/output error
Thank you for taking the time to report this issue and helping to make Ubuntu better. This package failure looks like it was caused by bad ISO download, corrupted install media, or device failure. eg. look in the logs and you'll see messages like these :- Oct 1 05:16:09 ubuntu kernel: [ 546.418029] SQUASHFS error: zlib decompression failed, data probably corrupt Oct 1 05:16:09 ubuntu kernel: [ 546.418036] SQUASHFS error: squashfs_read_data failed to read block 0x33de1bd Examining the information you have given us, this does not appear to be a useful bug report so I am closing it, as it appears to be a bad ISO or faulty device (inc. bad write-to-device). If you believe I'm in error, please leave a comment explaining why and change the status back to 'New'. I suggest you verify your ISO download, and use the 'check disc for defects' option to validate your media before install to ensure a good download & write. Possibly useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to- verify-ubuntu#0 and https://help.ubuntu.com/community/Installation/CDIntegrityCheck (where CD refers to your install media, be it CD, DVD, HDD, SSD, thumb-drive etc) NOTE: If this is a VM, the error can occur if too little RAM is supplied to the VM. ** Changed in: 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/1898008 Title: [Errno5] Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898009] [NEW] upgrader failes -Could not calculate the upgrade
Public bug reported: An uresolvable problem occurred while calculating the upgrade This was likely caused by: *Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge from the ppa-purge package to remove software from a LaunchpadPPA and try the upfrade again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 11:33:09 2020 InstallationDate: Installed on 2019-07-08 (450 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1898009 Title: upgrader failes -Could not calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896885] Re: [SRU] Please add Finnish translation for gnome-flashback
Everything seems to work as planned on both bionic and focal using the proposed builds, see screenshot. ** Attachment added: "verified-lp-#1896885-bionic-and-focal.png" https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1896885/+attachment/5415973/+files/verified-lp-%231896885-bionic-and-focal.png ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal ** Tags added: verification-done verification-done-bionic 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/1896885 Title: [SRU] Please add Finnish translation for gnome-flashback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1896885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898010] [NEW] pcmanfm should use git for file operations if containing folder is part of a git repository
Public bug reported: I suggest adding the following feature: For file operations like mv and rm pcmanfm should check if the current directory is part of a git repository. If this is the case the operations should be carried out using the respective git commands so as not to break file management within the repository. This would be extremely useful as pcmanfm does not show the user that the current directory is part of a git repository. On second thought: may be this should be the first step: show that you are moving within a git repo. Kind regards Andreas ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcmanfm 1.3.1-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Config_pcmanfm_System_xubuntu: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/etc/xdg/pcmanfm/xubuntu/pcmanfm.conf' CurrentDesktop: XFCE Date: Thu Oct 1 08:02:28 2020 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pcmanfm Udisks_dump: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'udisks' UpgradeStatus: Upgraded to focal on 2020-05-18 (135 days ago) ** Affects: pcmanfm (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/1898010 Title: pcmanfm should use git for file operations if containing folder is part of a git repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1898010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Okay, ever since I installed this bug fix, my mouse has been playing up. First, dragging and dropping across windows exhibited errant behaviour, such as dropping the dragging item in between box borders. Now, every once in a while, my mouse's primary buttons switch. The original issue has been resolved but this new issue is a little bit more problematic. I am using Ubuntu 20.04 with @cristiano patch ** Attachment added: "lshw" https://bugs.launchpad.net/ubuntu/focal/+source/mutter/+bug/1892440/+attachment/5415961/+files/specsaver.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898008] [NEW] [Errno5] Input/output error
Public bug reported: The installer encountered an error copying files to the hard disk: [Errno 5] Input/output error This is often due to a faulty CD/DVD disk or drive,or a faulty hard disk. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers), to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 10:49:52 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898008 Title: [Errno5] Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897853] Re: [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but not 5.8.0-18
** Description changed: gnome-shell stutters noticeably with kernel 5.8.0-19 - I've now tested three recent kernels: + I've now tested four recent kernels: + 5.8.0-20: stutters 5.8.0-19: stutters 5.8.0-18: smooth 5.8.0-16: smooth ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 30 13:52:38 2020 InstallationDate: Installed on 2020-07-16 (76 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint - Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse - Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint + Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Classic IntelliMouse + Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcEnviron: - LANGUAGE=en_AU:en - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic root=UUID=21e70a66-4d0f-49fc-b42c-668fc1594d91 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.8.0-19-generic N/A - linux-backports-modules-5.8.0-19-generic N/A - linux-firmware1.190 + linux-restricted-modules-5.8.0-19-generic N/A + linux-backports-modules-5.8.0-19-generic N/A + linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.release: 0.47 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:br0.47:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897853 Title: [regression] gnome-shell stutters noticeably with kernel 5.8.0-19, but not 5.8.0-18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64
This error is populating on Focal 'aws : 5.4.0-1026.26 : amd64' on c5.large and ' aws : 5.4.0-1026.26 : arm64' on a1.2xlarge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898007] [NEW] unsolvable problem prompted during installation of upgrade (
Public bug reported: >From ubuntu 18.04 to 20.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-1097.107-oem 4.15.18 Uname: Linux 4.15.0-1097-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 01:08:38 2020 InstallationDate: Installed on 2018-10-20 (711 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2020-09-29T01:32:33.327653 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1898007 Title: unsolvable problem prompted during installation of upgrade ( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
37 minutes so far. Top shows final using 100% of a core. Top -H shows only one thread. Main.log shows the skipping messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897956] Re: While upgrading to Ubuntu 20.04.1, it said that the upgrade couldn't be calculated, and stopped.
Thank you for reporting this bug and make ubuntu better! Could you make a screenshot or attach a textfile with the errors of your upgrade calculate errors please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897956 Title: While upgrading to Ubuntu 20.04.1, it said that the upgrade couldn't be calculated, and stopped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897875] Re: Unexpected warning from partman during entire disk installation
** Changed in: ubiquity (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/1897875 Title: Unexpected warning from partman during entire disk installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897999] Re: groovy flash-kernel fails on rpi4b 8GB
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1897999 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897999 Title: groovy flash-kernel fails on rpi4b 8GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1897999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898006] [NEW] -Bsymbolic-functions linker flag causes bdirjson output problem
Public bug reported: Hello Everybody, In Ubuntu Focal the Bacula binaries are prepared with the following linker flag: -Wl,-Bsymbolic-functions It causes a problem because when this flag is used then in bdirjson output all "Storage" directive values are "null". More information about this problem you can see in the following ticket in the Bacula Bug tracker: https://bugs.bacula.org/view.php?id=2557#c8234 As you can read there Bacula developers recommend to not use this flag to prepare Bacula binaries. Could it be possible to stop using the liker flag in Ubuntu Bacula binaries? Thank you in advance for your help with solving this problem. Best regards, Marcin Haba (gani) ** Affects: bacula (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/1898006 Title: -Bsymbolic-functions linker flag causes bdirjson output problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1898006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897513] Re: Ubuntu server 20.04.1 setup running from USB Live thumb drive doesn't see any hard drive to install to
** Also affects: subiquity Importance: Undecided Status: New ** Summary changed: - Ubuntu server 20.04.1 setup running from USB Live thumb drive doesn't see any hard drive to install to + Ubuntu server 20.04.1 Subiquity running from USB Live thumb drive doesn't see any hard drive to install to ** Description changed: - Ubuntu server 20.04.1 setup running from USB Live thumb drive doesn't - see any hard drive to install to. Even if there's only one hard drive - in the computer and regardless of which SATA port the hard drive is - connected to. Even if the optical drive is removed. + Ubuntu server 20.04.1 Subiquity install running from USB Live thumb + drive doesn't see any hard drive to install to. Even if there's only + one hard drive in the computer and regardless of which SATA port the + hard drive is connected to. Even if the optical drive is removed. Dell PowerEdge T310 Service Tag CYC2QM1 - no RAID card installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897513 Title: Ubuntu server 20.04.1 Subiquity running from USB Live thumb drive doesn't see any hard drive to install to To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1897513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897515] Re: Ubuntu server 20.04.1 setup running from DVD doesn't see drive 0 as a drive to install to
** Also affects: subiquity Importance: Undecided Status: New ** Summary changed: - Ubuntu server 20.04.1 setup running from DVD doesn't see drive 0 as a drive to install to + Ubuntu server 20.04.1 Subiquity running from DVD doesn't see drive 0 as a drive to install to -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897515 Title: Ubuntu server 20.04.1 Subiquity running from DVD doesn't see drive 0 as a drive to install to To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1897515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897511] Re: Ubuntu server 20.04.1 setup doesn't check for hard drives before network setup
** Also affects: subiquity Importance: Undecided Status: New ** Summary changed: - Ubuntu server 20.04.1 setup doesn't check for hard drives before network setup + Ubuntu server 20.04.1 - when installing with Subiquity, it doesn't check for hard drives before network setup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897511 Title: Ubuntu server 20.04.1 - when installing with Subiquity, it doesn't check for hard drives before network setup To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1897511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898001] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1898001 Title: package linux-image-5.4.0-47-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897993] Re: Upgrade from v18 LTS to 20.04.1 LTS doesn't work both via shell and using upgrade manager
** Description changed: Was experiencing 2 issues. The first one is resolved but may be related to the one currently being faced, hence why I'm sharing it: Issue 1) Software-Updater prompts to upgrade to 20.04.1 LTS but clicking on upgrade causes the dialog box to disappear and does nothing in the - background. After fiddling around and updating and upgrading all - packages, I found that wine wasn't getting updated for some reason, so I - readded the PPAs for that and updated it via shell. This resolved the - issue and upon a restart, the Software-Updater upgrade to 20.04.1 LTS - started going to the actual upgrade screen upon clicking upgrade. + background. After following the steps highlighted below this paragraph, + I found that wine wasn't getting updated for some reason, so I readded + the PPAs for that and updated it via shell. This resolved the issue and + upon a restart, the Software-Updater upgrade to 20.04.1 LTS started + going to the actual upgrade screen upon clicking upgrade. + + sudo apt update + sudo apt upgrade + sudo reboot command (up till this, upgraded everything except wine) + + To fix wine: + sudo dpkg --add-architecture i386 + wget -qO - https://dl.winehq.org/wine-builds/winehq.key | sudo apt-key add - + sudo add-apt-repository ppa:cybermax-dexter/sdl2-backport + sudo apt update + sudo apt upgrade + sudo reboot command + + Doing the above upgraded wine to v5 from v4 and allowed me to proceed to + Issue 2 below. Issue 2) Software-Updater fails at the 2nd step during upgrade and generates the error in the attached screenshot. I disabled all third - party ppas, restarted, and ran again. This did not fix the overall issue - but the prompt mentioning 3rd party ppas as a possible cause no longer - shows up in the dialog box and only suggests filing a bug. + party ppas by going to the "Software & Updates" tool, clicked on "Other + Software" and disabled anything that had a checkmark to it (namely the + kisak-mesa/bionic ppa and the google chrome ppa, there was one other but + I can't recall which one anymore), restarted, and ran again. This did + not fix the overall issue but the prompt mentioning 3rd party ppas as a + possible cause no longer shows up in the dialog box and only suggests + filing a bug. I also tried using sudo do-release-upgrade and it generates the exact same error as using the GUI interface. All packages are up to date and nothing is identified as possible packages left to update, third party or otherwise. I also don't see unnecessary packages sitting on the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 22:15:34 2020 InstallationDate: Installed on 2017-10-25 (1071 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago) + + Edit: Added additional details for Issue 1 as my resolution steps were + incredibly vague. Also added details on exactly where I went to disable + the third party ppas and what ppas I recall disabling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897993 Title: Upgrade from v18 LTS to 20.04.1 LTS doesn't work both via shell and using upgrade manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889960] Re: kubuntu 20.04.1 keeps pausing, strange behavior
[Expired for kubuntu-meta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kubuntu-meta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1889960 Title: kubuntu 20.04.1 keeps pausing, strange behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1889960/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1659719] Autopkgtest regression report (pam/1.1.8-3.2ubuntu2.3)
All autopkgtests for the newly accepted pam (1.1.8-3.2ubuntu2.3) for xenial have finished running. The following regressions have been reported in tests triggered by the package: systemd/229-4ubuntu21.29 (amd64, i386) kscreenlocker/5.5.5-0ubuntu1 (armhf) 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/xenial/update_excuses.html#pam [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/1659719 Title: ssh can't call a binary from a snap without the full path To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666203] Autopkgtest regression report (pam/1.1.8-3.2ubuntu2.3)
All autopkgtests for the newly accepted pam (1.1.8-3.2ubuntu2.3) for xenial have finished running. The following regressions have been reported in tests triggered by the package: systemd/229-4ubuntu21.29 (amd64, i386) kscreenlocker/5.5.5-0ubuntu1 (armhf) 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/xenial/update_excuses.html#pam [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/1666203 Title: pam_tty_audit failed in pam_open_session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
SRU reviewer:
https://pastebin.ubuntu.com/p/PcZq7Hr3NQ/
These are the functional tests results.
There was an issue running one test, I had to re-ran, and it is all
good:
Oct 01 04:09:09 Running test SimulStop (focal02) [ 1]
Oct 01 04:09:24 Stopping Cluster Manager on all nodes
Oct 01 04:09:31
Oct 01 04:09:31 Overall Results:{'success': 1, 'failure': 0, 'BadNews': 0,
'skipped': 0}
Oct 01 04:09:31
Oct 01 04:09:31 Test Summary
Oct 01 04:09:31 Test SimulStop: {'calls': 1, 'failure': 0, 'skipped':
0, 'auditfail': 0}
Oct 01 04:09:31 TESTS COMPLETED
Nothing to worry as it wasn't a failure.
The other one, being a failure, is already expected because we don't
package cts-exec-helper command on purpose.
So, with those 2 set of tests I'm confident this fix is stable enough.
Thanks for reviewing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881762
Title:
resource timeout not respecting units
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898001] [NEW] package linux-image-5.4.0-47-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit sta
Public bug reported: i keep getting this error after updating the kernel using sudo apt-get dist-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shashikanth 1945 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 30 10:12:31 2020 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+loki-n3-v3-whl+X32 ErrorMessage: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3480 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=1cde599c-4502-4a38-9400-2802117f7ca7 ro mem_sleep_default=deep usbcore.quirks=2386:3119:k quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-5.4.0-47-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0H40C6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3480 dmi.product.sku: 08C8 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898001 Title: package linux-image-5.4.0-47-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-47-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898000] [NEW] bogus handling of DAEMON_OPTS by chronyd-starter.sh
Public bug reported: By default, chrony's DAEMON_OPTS is set to "-F -1" which means to enable seccomp but not in kill mode. To enable kill mode while also running in a container, one would use "-F 1 -x" but it seems to confuse getopts (from /usr/lib/systemd/scripts/chronyd-starter.sh) into thinking that no "-x" was provided and thus wrongly logs a warning about the CAP_SYS_TIME missing and also adds an extraneous "-x". # Steps to reproduce: 1) create and enter into a test container: lxc launch images:ubuntu/focal foo lxc shell foo 2) install chrony: apt update apt install -y chrony 3) set DAEMON_OPTS="-F 1 -x" in /etc/default/chrony 4) restart chrony systemctl restart chrony 5) check arguments passed to chronyd ps aux| grep chrony The last step should show that chronyd was invoked with 3 args: "-F 1 -x" but due to the bug, it shows 4 arguments: _chrony106 0.0 0.0 13212 2072 ?S03:08 0:00 /usr/sbin/chronyd -F 1 -x -x _chrony107 0.0 0.0 5032 1728 ?S03:08 0:00 /usr/sbin/chronyd -F 1 -x -x # Workaround: Simply setting DAEMON_OPTS to "-x -F 1" or "-F1 -x" will do. # Simpler way to reproduce Kkeep an eye on $X_SET and run: sh -x /usr/lib/systemd/scripts/chronyd-starter.sh -F -1 -x or sh -x /usr/lib/systemd/scripts/chronyd-starter.sh -F 1 -x I realize this is an edge case that probably really few might run into but since I've lost a good chunk of time wondering was what going on, I felt I needed to report it. I would have preferred to send a patch but it's too late for me to try to tame getopts ;) The bug does not affect Debian as /usr/lib/systemd/scripts/chronyd- starter.sh is an Ubuntu delta (carried to Groovy). Don't get me wrong, I appreciate the delta as I can easily run chrony inside a container, so thank you ;) # Additional information $ apt-cache policy chrony chrony: Installed: 3.5-6ubuntu6.2 Candidate: 3.5-6ubuntu6.2 Version table: *** 3.5-6ubuntu6.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.5-6ubuntu6 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ** Affects: chrony (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/1898000 Title: bogus handling of DAEMON_OPTS by chronyd-starter.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1898000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897999] [NEW] groovy flash-kernel fails on rpi4b 8GB
Public bug reported: When running 'sudo flash-kernel' on an 8GB rpi4, it fails with the following error: ubuntu@ubuntu:~$ sudo flash-kernel Unsupported platform. This only seems to happen on the 8GB model, not 2GB, 4GB, etc. This is reproducible on both the armhf and the arm64 kernel flash-kernel: Installed: 3.100ubuntu2 Kernel versions: Linux ubuntu 5.8.0-1002-raspi #5-Ubuntu SMP PREEMPT Thu Sep 3 12:48:22 UTC 2020 armv7l armv7l armv7l GNU/Linux Linux ubuntu 5.8.0-1002-raspi #5-Ubuntu SMP PREEMPT Thu Sep 3 12:40:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ** Affects: flash-kernel (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/1897999 Title: groovy flash-kernel fails on rpi4b 8GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1897999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897995] Re: Internal speaker not working because it's treated as headphone and muted by default
** Package changed: ubuntu => alsa-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897995 Title: Internal speaker not working because it's treated as headphone and muted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1897995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546724] Re: KDE processes writing to icon-cache files "prevents the disk from going to powersave mode."
** Changed in: kde-baseapps Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/546724 Title: KDE processes writing to icon-cache files "prevents the disk from going to powersave mode." To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/546724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546724]
(In reply to Nate Graham from comment #8) > Is this still a problem in recent versions of Plasma 5, like 5.19 or later? I doubt it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/546724 Title: KDE processes writing to icon-cache files "prevents the disk from going to powersave mode." To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/546724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] Re: xubuntu groovy install - bootloader install failure
kubuntu groovy (daily) installed cleanly to this box (minor unrelated graphic glitches after reboot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897991 Title: xubuntu groovy install - bootloader install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897173] Re: 20.10 Installer crashes with partitions being written but unable to inform kernel of the change
xubuntu daily still fails to install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) but no appearance of the error message key to this bug. It's a bootloader issue I mentioned in comment #9 so I've started a new bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991 kubuntu daily however succeeded on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897173 Title: 20.10 Installer crashes with partitions being written but unable to inform kernel of the change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1897173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small
Then, how can we get any other developer attention to fix this xnox's incompetent swap calculation algorithm? ** Summary changed: - Ubuntu 18.04 Installer creates swap partition too small + Ubuntu 18.04-20.04 Installer creates swap partition too small -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04-20.04 Installer creates swap partition too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351267] Re: partman-auto prefers to give disk to swap, leaving root too small
This is a really ridiculous fix and algorithm, favoring high-memory systems and neglecting the more common low-memory systems. I installed Ubuntu 20.04 on a machine with this specs 12GB RAM and 240GB SSD, it created just 1GB Swap partition. !!! Dimitri John Ledkov (xnox) if you are still employed by Canonical, please fix this mess you have done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351267 Title: partman-auto prefers to give disk to swap, leaving root too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1351267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895199] Re: web apps no longer launch into separate windows
For step 5 above I also sometimes deleted the app from chrome://apps and re-created it. SO the actual bug on this issue seems to be some discontinuity with my old webapp definitions because I have been able to make them work again by recreating them again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895199 Title: web apps no longer launch into separate windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1895199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897983] Re: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15
Spotted this on 4.15.0-1083.87, though the current version is 4.15.0-1084.88. All LTP tests failed on the current version and I'm re- running the tests. Will report back verifying if this is still failing on 4.15.0-1084.88. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897983 Title: cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897995] [NEW] Internal speaker not working because it's treated as headphone and muted by default
Public bug reported: I am using Ubuntu Focal in HP Pavilion g4, the internal speaker not working, no sound at all. However it works if I run alsamixer and unmute the headphone. It's strange that the internal speaker is assumed as headphone. For your information, it happens after upgrading to Focal, it was good in the previous LTS version. For additional information, I upgraded to Focal while using external monitor that has speaker by using HDMI cable. The HDMI was connected before and after upgrade process. I don't know if this is related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-utils 1.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 09:23:53 2020 InstallationDate: Installed on 2018-12-23 (647 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: alsa-utils UpgradeStatus: Upgraded to focal on 2020-05-30 (124 days ago) ** Affects: 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/1897995 Title: Internal speaker not working because it's treated as headphone and muted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1897995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897992] Re: No VGA video signal after installing pkg and rebooting
Obviously that should be temporarily solution, because my intention is to use the openchrome driver, not generic vesa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897992] Re: No VGA video signal after installing pkg and rebooting
UPDATE: Could login into Recovery mode and created etc/X11/xorg.conf with contents: Section "Device" Identifier "Configured Video Device" Driver "vesa" EndSection ...As indicated in https://help.ubuntu.com/community/OpenChrome Now lubuntu runs with 1024x768 resolution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897993] [NEW] Upgrade from v18 LTS to 20.04.1 LTS doesn't work both via shell and using upgrade manager
Public bug reported: Was experiencing 2 issues. The first one is resolved but may be related to the one currently being faced, hence why I'm sharing it: Issue 1) Software-Updater prompts to upgrade to 20.04.1 LTS but clicking on upgrade causes the dialog box to disappear and does nothing in the background. After fiddling around and updating and upgrading all packages, I found that wine wasn't getting updated for some reason, so I readded the PPAs for that and updated it via shell. This resolved the issue and upon a restart, the Software-Updater upgrade to 20.04.1 LTS started going to the actual upgrade screen upon clicking upgrade. Issue 2) Software-Updater fails at the 2nd step during upgrade and generates the error in the attached screenshot. I disabled all third party ppas, restarted, and ran again. This did not fix the overall issue but the prompt mentioning 3rd party ppas as a possible cause no longer shows up in the dialog box and only suggests filing a bug. I also tried using sudo do-release-upgrade and it generates the exact same error as using the GUI interface. All packages are up to date and nothing is identified as possible packages left to update, third party or otherwise. I also don't see unnecessary packages sitting on the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 22:15:34 2020 InstallationDate: Installed on 2017-10-25 (1071 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade ** Attachment added: "screenshot of error" https://bugs.launchpad.net/bugs/1897993/+attachment/5415898/+files/Screenshot%20from%202020-09-30%2021-56-19.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897993 Title: Upgrade from v18 LTS to 20.04.1 LTS doesn't work both via shell and using upgrade manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897992] [NEW] No VGA video signal after installing pkg and rebooting
Public bug reported: MOBO: Asus p5v-vm ultra Have a VIA P4M890 onboard gfx card . First after installing lubuntu 18 i could login but couldn't change 640x480 resolution. So i installed this package. After rebooting and seeing the lubuntu loading screen i loose video signal and the screen is black, green light blinking, as if the pc isn't sending any signal. ** Affects: xserver-xorg-video-openchrome (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/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] Re: xubuntu groovy install - bootloader install failure
FYI. This box isn't mine, so it's not used very often in my QA Lubuntu & main Ubuntu have installed to it in recent day(s) though. (I've been trying to re-install windows 7 for it's owner, and it's been failing to install for unknown reason.. When that's resolved I'll lose access to the box again) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897991 Title: xubuntu groovy install - bootloader install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card"
It looks like 'pipewire' has stolen the audio devices so pulseaudio may not work properly. Please try uninstalling or reconfiguring 'pipewire'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] Re: xubuntu groovy install suspected install failure (bootloader?)
** Description changed: - Xubuntu groovy (daily) QA-test install on + Xubuntu groovy (daily) QA-test install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) Error writing boot loader, asked for my to select device, but I was unable to select SDA device + + Bootloader install failed - + https://photos.app.goo.gl/qyh42gnuqXJo3WcU6 + Bootloader install failed selections - + https://photos.app.goo.gl/GPzsEwBH58T3MdxU7 + -- iso.qa.ubuntu.com details box had internet cable disconnected, install was as expected until error box appeared that it was unable to write boot loader to device & select box asking me to select device was offered, I kept trying to use sda (ssd) but it'd reject & ask again. I tried a few times before clicking continue install completed, on reboot I get no OS found error ** Expected Results I'd expect the SSD selected to be acceptable, not repeating errors & then fail to boot on selecting continue. - ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.10 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Thu Oct 1 11:29:32 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-20-generic linux-base SourcePackage: ubiquity 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/1897991 Title: xubuntu groovy install - bootloader install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] Re: xubuntu groovy install - bootloader install failure
** Summary changed: - xubuntu groovy install suspected install failure (bootloader?) + xubuntu groovy install - bootloader install failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897991 Title: xubuntu groovy install - bootloader install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] Re: xubuntu groovy install suspected install failure (bootloader?)
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1897991 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897991 Title: xubuntu groovy install - bootloader install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Installed correctly the first time. Upon reinstall, received 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/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897959] Re: Audio Shuts Down with Screen Blanking
First, can we assume your sound is not going through HDMI or DisplayPort? If it is then this is expected. What kind of sound connection are you using? Second, please follow these instructions to report the crash: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: gnome-shell (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/1897959 Title: Audio Shuts Down with Screen Blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897917] Re: Ubuntu 20.04 does not boot to GDM forever spining wheel
Do you have an external monitor connected when the problem happens? I am reminded of bug 1872159. ** Package changed: xorg-server (Ubuntu) => plymouth (Ubuntu) ** Changed in: plymouth (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/1897917 Title: Ubuntu 20.04 does not boot to GDM forever spining wheel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1897917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897830] Re: 20.04.1 goes fully blank (screens) after replugging 2nd monitor
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1897830 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal multimonitor ** Changed in: gnome-shell (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/1897830 Title: 20.04.1 goes fully blank (screens) after replugging 2nd monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897830] Re: 20.04.1 goes fully blank (screens) after replugging 2nd monitor
Also, after the problem happens next and immediately after restarting, please run: journalctl -b-1 > prevboot.txt lspci -kv > lspci.txt and attach the resulting text files here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897830 Title: 20.04.1 goes fully blank (screens) after replugging 2nd monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
This bug is closed so please open new bugs from now on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1868519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897823] Re: FTBFS due to deprecated sigignore()
** Changed in: memcached (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: memcached (Ubuntu) Importance: Undecided => Critical ** Changed in: memcached (Ubuntu) Importance: Critical => High ** Changed in: memcached (Ubuntu) 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/1897823 Title: FTBFS due to deprecated sigignore() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1897823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887535] Re: build operates differently if source is a git repo
> And on that resend thread Daniel denied the patch as-is in: > https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg07966.html ah thanks, I hadn't made it down to that email yet; I just followed up and hopefully something can be worked out upstream. I asked for Michael and your opinion also, in case you have anything you want to suggest/add there. Thanks! > one should never try to build a package locally out of the dir anyway using sbuild/pbuilder etc may be recommended, but many people (myself included) build locally with debuild and dpkg-buildpackage, especially during debugging/testing. I find sbuild/pbuilder excessively cumbersome and antiquated. But anyway, we don't need to devolve this bug into a build tool argument :) > Maybe we can bundle it with another upload that we'd need to do anyway. yes absolutely, I didn't mean we should release with just this fix, I just wanted to get it queued up to include in the next bugfix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887535 Title: build operates differently if source is a git repo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] Re: xubuntu groovy install suspected install failure (bootloader?)
This issue has been noted before, but it was occuring after the error reported in the bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897173 the error message that is mentioned in that bug however no longer appears, thus the separate filing ** Description changed: - to be filled in + Xubuntu groovy (daily) QA-test install on + dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) + + Error writing boot loader, asked for my to select device, but I was + unable to select SDA device + + -- iso.qa.ubuntu.com details + box had internet cable disconnected, install was as expected until error box appeared that it was unable to write boot loader to device & select box asking me to select device was offered, I kept trying to use sda (ssd) but it'd reject & ask again. I tried a few times before clicking continue + + install completed, on reboot I get no OS found error + + ** Expected Results + I'd expect the SSD selected to be acceptable, not repeating errors & then fail to boot on selecting continue. + ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.10 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Thu Oct 1 11:29:32 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 RebootRequiredPkgs: - linux-image-5.8.0-20-generic - linux-base + linux-image-5.8.0-20-generic + linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: ubiquity (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897991 Title: xubuntu groovy install suspected install failure (bootloader?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897991] [NEW] xubuntu groovy install suspected install failure (bootloader?)
Public bug reported: Xubuntu groovy (daily) QA-test install on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) Error writing boot loader, asked for my to select device, but I was unable to select SDA device -- iso.qa.ubuntu.com details box had internet cable disconnected, install was as expected until error box appeared that it was unable to write boot loader to device & select box asking me to select device was offered, I kept trying to use sda (ssd) but it'd reject & ask again. I tried a few times before clicking continue install completed, on reboot I get no OS found error ** Expected Results I'd expect the SSD selected to be acceptable, not repeating errors & then fail to boot on selecting continue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.10 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Thu Oct 1 11:29:32 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-20-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.10 xubuntu ** Changed in: ubiquity (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/1897991 Title: xubuntu groovy install suspected install failure (bootloader?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896774] Re: [ASUS UX430UQ] Headphone output stopped working after perfoming dist-upgrade
Hello, In AlsaInfo.txt, under `!!Amixer output`, the Master and Headphone audio output controls are set to off, a possible starting point for debugging this issue may be looking into trying to unset those. The file contents are just writing the output of `/usr/sbin/alsa-info.sh --stdout --no- upload`. For reference, this is part of the output from a Xenial system with working audio: https://pastebin.ubuntu.com/p/2nzBjfpC6C/ Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896774 Title: [ASUS UX430UQ] Headphone output stopped working after perfoming dist- upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897990] [NEW] update-manager failed to update: apt has no solutions
Public bug reported: apt.log appears to be full of complaints about python2 packages. in any case, the update manager seems to have restored my system to a sane state. i haven't tried removing infrequently used python2 packages yet to see if that would help. Description:Ubuntu 18.04.5 LTS Release:18.04 update-manager: Installed: 1:18.04.11.13 Candidate: 1:18.04.11.13 Version table: *** 1:18.04.11.13 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1:18.04.11 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages update-manager-core: Installed: 1:18.04.11.13 Candidate: 1:18.04.11.13 Version table: *** 1:18.04.11.13 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1:18.04.11 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages i expected a seamless upgrade to 20.04. update-manager failed, but seems to have restored the system to a sane state. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 18:04:23 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-19 (1319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2020-09-30T17:59:57.212485 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1897990 Title: update-manager failed to update: apt has no solutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592853] Re: sshuttle doesn't autodetect python3 instead of 'python'
The verification failure in Xenial is fixed by the version in the upload queue via bug 1897987 and bug 1897961 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592853 Title: sshuttle doesn't autodetect python3 instead of 'python' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1592853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897987] Re: connection to py34 fails
** Description changed: [impact] connecting to a remote host with py3.4 fails [test case] root@lp1896299-x:~# sshuttle --python python3 -r lp1896299-t.lxd 1.2.3.4/24 client: Connected. Traceback (most recent call last): - File "", line 1, in - File "assembler.py", line 39, in - File "sshuttle.server", line 273, in main + File "", line 1, in + File "assembler.py", line 39, in + File "sshuttle.server", line 273, in main TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple' client: fatal: server died with error code 1 [regression potential] any regression would likely prevent the initial connection from being setup correctly. [scope] this is needed only for x this was fixed in 4241381d827ca42fd40b6a4bc5a4e2fdde92577b which is included upstream in v0.78.0 so bionic and later are already fixed. [other info] since xenial defaults to py35, this is mainly needed to connect from xenial to trusty using py3 instead of py2. this is particularly important with the change made in bug 1592853, which effectively causes sshuttle to default to py3 if it is found on the system (previously, it defaulted to py2 unless py3 version 3.5 exactly was available). so this bug is needed to allow sshuttle from x to t to continue working without - needing to specify --python python2 + needing to specify --python python2. Note that sshuttle will continue to + use py2 (it will use simply 'python') on the remote system if py3 is not + available. also the commit that fixes this was partially included in the backport for bug 1896299, this bug only adds a missing part of that backport into the patch file to fix this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897987 Title: connection to py34 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1897987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1897781] Re: System upgrade from Ubuntu 18.04 to 20.04 stops part-way through.
Dear Brian, Two questions. What do you mean by "the ubuntu-desktop package"? Do you mean the iso I downloaded for Ubuntu 18.04? And, if so, in what format? Iso? Second, where might I get directions on just how to install the package from the command line. By command line I take it you mean a terminal where I might use sudo as the first word. Hopfully, George Rodier On 2020-09-30 4:11 p.m., Brian Murray wrote: > Could you please try re-installing the ubuntu-desktop package via the > command line and then try the upgrade again? Thanks! > > ** Changed in: ubuntu-release-upgrader (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/1897781 Title: System upgrade from Ubuntu 18.04 to 20.04 stops part-way through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1897781] Re: System upgrade from Ubuntu 18.04 to 20.04 stops part-way through.
Brian, by ubuntu-desktop package, do you mean ubuntu-release-upgrader-core ? And, if so, where to I find that? George On 2020-09-30 4:11 p.m., Brian Murray wrote: > Could you please try re-installing the ubuntu-desktop package via the > command line and then try the upgrade again? Thanks! > > ** Changed in: ubuntu-release-upgrader (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/1897781 Title: System upgrade from Ubuntu 18.04 to 20.04 stops part-way through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
@Gabirele, Looks there is no difference between Debian 1.2.3 and testing 1.2.2, so should I submit the testing 1.2.2 to ubuntu package? And for the problem you met, maybe it is a kernel issue or a pulseaudio issue, you could file bugs against to linux kernel and pulseaudio. Because we don't have hardware, we couldn't reproduce the issue you mentioned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897988] [NEW] GitKraken Flatpak doesn't display Icon in task switcher
Public bug reported: The GitKraken or any other flatpak doesn't display the icon on top of the window in the task switcher like other applications. I have attached a screenshot. It's the same for the bottom task bar too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phillipsj 1317 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 30 20:33:37 2020 InstallationDate: Installed on 2020-09-30 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor Bus 001 Device 004: ID 04f2:b52c Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 1199:9079 Sierra Wireless, Inc. Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20F6006FUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=5a1e3d3b-2e79-426e-9641-1447dcd64341 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6006FUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:svnLENOVO:pn20F6006FUS:pvrThinkPadX260:rvnLENOVO:rn20F6006FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6006FUS dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO ** Affects: ubuntu-mate Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Package changed: ubuntu => ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897988 Title: GitKraken Flatpak doesn't display Icon in task switcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1897988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897961] Re: python command detection fails
** Description changed:
[impact]
bug 1592853 patches python command detection but is an incomplete
backport, resulting in failure to correctly detect the python command,
which causes sshuttle to fail if --python is not provided.
[test case]
- run sshuttle without --python to any remote system
+ run sshuttle without --python to any remote system:
+
+ root@lp1896299-x:~# sshuttle -r lp1896299-x.lxd 1.2.3.4/24
+ Traceback (most recent call last):
+ File "/usr/bin/sshuttle", line 9, in
+ load_entry_point('sshuttle==0.76', 'console_scripts', 'sshuttle')()
+ File "/usr/lib/python3/dist-packages/sshuttle/cmdline.py", line 226, in main
+ opt.daemon, opt.pidfile)
+ File "/usr/lib/python3/dist-packages/sshuttle/client.py", line 701, in main
+ seed_hosts, auto_nets, daemon)
+ File "/usr/lib/python3/dist-packages/sshuttle/client.py", line 408, in _main
+ options=dict(latency_control=latency_control))
+ File "/usr/lib/python3/dist-packages/sshuttle/ssh.py", line 112, in connect
+ "exec \"$P\" -c %s") % quote(pyscript)
+ NameError: name 'quote' is not defined
+
[regression potential]
regressions would likely cause the initial connection to fail
[scope]
this is needed only for x
the backport missed upstream commit 3541e4bd which was included first in
v0.78.0 so this is fixed already in b and later.
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897961
Title:
python command detection fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1897961/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666203] Re: pam_tty_audit failed in pam_open_session
Hello Toru, or anyone else affected, Accepted pam into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pam/1.1.8-3.2ubuntu2.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pam (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659719] Re: ssh can't call a binary from a snap without the full path
Hello Leo, or anyone else affected, Accepted pam into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pam/1.1.8-3.2ubuntu2.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pam (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897987] [NEW] connection to py34 fails
Public bug reported: [impact] connecting to a remote host with py3.4 fails [test case] root@lp1896299-x:~# sshuttle --python python3 -r lp1896299-t.lxd 1.2.3.4/24 client: Connected. Traceback (most recent call last): File "", line 1, in File "assembler.py", line 39, in File "sshuttle.server", line 273, in main TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple' client: fatal: server died with error code 1 [regression potential] any regression would likely prevent the initial connection from being setup correctly. [scope] this is needed only for x this was fixed in 4241381d827ca42fd40b6a4bc5a4e2fdde92577b which is included upstream in v0.78.0 so bionic and later are already fixed. [other info] since xenial defaults to py35, this is mainly needed to connect from xenial to trusty using py3 instead of py2. this is particularly important with the change made in bug 1592853, which effectively causes sshuttle to default to py3 if it is found on the system (previously, it defaulted to py2 unless py3 version 3.5 exactly was available). so this bug is needed to allow sshuttle from x to t to continue working without needing to specify --python python2 also the commit that fixes this was partially included in the backport for bug 1896299, this bug only adds a missing part of that backport into the patch file to fix this bug. ** Affects: sshuttle (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: sshuttle (Ubuntu Xenial) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: sshuttle (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sshuttle (Ubuntu) Status: New => Fix Released ** Changed in: sshuttle (Ubuntu Xenial) Status: New => In Progress ** Changed in: sshuttle (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: sshuttle (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897987 Title: connection to py34 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1897987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897980] Re: Installer crashed
Exception during installation: Sep 30 23:05:28 ubuntu /plugininstall.py: Traceback (most recent call last): Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1767, in Sep 30 23:05:28 ubuntu /plugininstall.py: install.run() Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 62, in wrapper Sep 30 23:05:28 ubuntu /plugininstall.py: func(self) Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 248, in run Sep 30 23:05:28 ubuntu /plugininstall.py: self.install_restricted_extras() Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1156, in install_restricted_extras Sep 30 23:05:28 ubuntu /plugininstall.py: self.do_install(packages) Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 938, in do_install Sep 30 23:05:28 ubuntu /plugininstall.py: mark_install(cache, pkg) Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 550, in mark_install Sep 30 23:05:28 ubuntu /plugininstall.py: raise InstallStepError( Sep 30 23:05:28 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Unable to install 'linux-modules-nvidia-440-generic-hwe-20.04' due to conflicts. Sep 30 23:05:28 ubuntu /plugininstall.py: ** Tags added: installer-crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897980 Title: Installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897980] Traceback
Exception during installation: Sep 30 23:05:28 ubuntu /plugininstall.py: Traceback (most recent call last): Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1767, in Sep 30 23:05:28 ubuntu /plugininstall.py: install.run() Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 62, in wrapper Sep 30 23:05:28 ubuntu /plugininstall.py: func(self) Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 248, in run Sep 30 23:05:28 ubuntu /plugininstall.py: self.install_restricted_extras() Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1156, in install_restricted_extras Sep 30 23:05:28 ubuntu /plugininstall.py: self.do_install(packages) Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 938, in do_install Sep 30 23:05:28 ubuntu /plugininstall.py: mark_install(cache, pkg) Sep 30 23:05:28 ubuntu /plugininstall.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 550, in mark_install Sep 30 23:05:28 ubuntu /plugininstall.py: raise InstallStepError( Sep 30 23:05:28 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: Unable to install 'linux-modules-nvidia-440-generic-hwe-20.04' due to conflicts. Sep 30 23:05:28 ubuntu /plugininstall.py: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897980 Title: Installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
SRU reviewer: https://pastebin.ubuntu.com/p/rgVVb66xGd/ These are the regression tests results. All good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881762 Title: resource timeout not respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
Still happening on 2020-10-01 (since at least 2019-10-01) on multiple computers. Quoting what bug description says: "Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897986] [NEW] add minidlna ports to /etc/services to help ufw
Public bug reported: minidlna is a simple DLNA compliant media streamer. It requires 1900/udp and 8200/tcp (in default configuration) to be open if using a firewall eg ufw or iptables. ufw reads /etc/services How do I request that minidlna ports are added to the /etc/services file centrally ie upstream - didn't want to just start a bug... I have done this on the local machine by appending to the bottom of that file as implied is ok so I can now: sudo ufw allow minidlna / sudo ufw deny minidlna which would significantly improve the ability to install minidlna with an active ufw as I have spent most of last night tracking down the correct ports to open... (I've now restricted to LAN). Hoping to ease other peoples experience. ** Affects: minidlna (Ubuntu) Importance: Undecided Status: New ** Tags: configure minidlna services ufw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897986 Title: add minidlna ports to /etc/services to help ufw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minidlna/+bug/1897986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
Created attachment 165976 rhbz#1847031 cleaned crash bt That whole bt looks broken. RH has no reproducer either, so the fix is just a guess. Version was libreoffice-6.4.4.2-2.fc32.x86_64, as you can see in the bt paths. The bt itself looks "wrong". The user did a right-click on a Calc cell, that would open the context menu, but at that point, when the Gtk event is processed, a lot more stuff is already "gone", like all the aGuard objects have nullptr, so no mutex in them. So I guess this is just for reference, but won't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897823] Re: FTBFS due to deprecated sigignore()
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/memcached/+git/memcached/+merge/391662 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897823 Title: FTBFS due to deprecated sigignore() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1897823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
It's hard to pin down what other new packages could have made it onto the users system because of the way Ubuntu rolls out releases in a "phased" manner: https://wiki.ubuntu.com/StableReleaseUpdates#Phasing This is happening simultaneously for all sorts of packages too, at various stages in the phasing process. So unfortunately, there's no way to really get a sense of other new packages that might be causing the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
No. (In reply to Michael Weghorn from comment #2)
> The only relatively recent commit related to QMimeData handling (i.e. mostly
> copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in
> 6.4.4 already.
>
> @jmux: Any ideas?
We know the fix for tdf#131533 is rather fishy and more of a workaround,
then a real fix. But if we have the same backtraces before 6.4.4 (and I
checked that libreoffice_6.3.3-0ubuntu1.debian.tar.xz doesn't carry that
fix), we can - kind of - rule that out. Also all the backtraces just
indicate Calc (ScSelectionTransferObj), not any other LO modules (at
least Writer), which is strange. Maybe an active selection in Calc is
just more common on shutdown, then in other applications? OTOH a copy in
Calc keeps the selection, even if you move the "cursor rectangle". There
is also nothing suspicious new on
https://crashreport.libreoffice.org/stats/version/6.4.6.2
And the only "fix" in vcl/qt5 between 6.4.2 and 6.4.3 is commit
1000169ebca79478a05b4c23e760d99bd77e739e ("Qt5 unify font attribute
conversions"), which I would also rule out as the origin of any bug
(famous last words).
There is also no other fix in vcl/ or sc/ since commit
cbac26c52ccbe59c51c6631cb8c4b0a314a9848a / 6.4.0, which looks suspicious
at all w.r.t. the backtrace at a first glance. And the whole lazy
clipboard stuff was already in 6.3. And your fix for tdf#129809 was
already in 6.4.2.
Still nothing would explain the current peak, I can see in
https://errors.ubuntu.com since
https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=libreoffice-
core&from=2020-08-24&to=2020-09-25, which matches the publishing date
from
https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.6-0ubuntu0.20.04.1
.
So I checked the diff of the 6.4.6 fix range for sc and interestingly it
contains commit 8718d243edc9400b0e0131b096702af8d33df327 (rhbz#1847031
null-deref), which fixes a null-deref in ~ScTransferOb. That should
really just fix a bug, not cause one, but eventually this just papers-
over some real bug in the other fixes, which now hits Qt in some way.
Because ScTransferObj is part of libsclo, which can't exists with
"pScMod == nullptr".
$ git log --pretty=oneline
f2e448175cee92fc695413e7281223e9f23e30ee~1..origin/libreoffice-6-4-6 | wc -l
123
Now I really would like to have a reproducer, which eventually should
also happen on master... and tdf#130559 is the only additional thing in
sc that looks strange, but that's just 17 out of the 123 patches.
Someone from Kubuntu could "mine" the crash reports, if there is
anything reproducible in it. And I have to get the RHEL bug report from
someone (Caolan, eventually).
So while I first suspected something non-LO, it now smells like a LO
bug, independent of VCL, evetually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897784
Title:
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
The only relatively recent commit related to QMimeData handling (i.e. mostly copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in 6.4.4 already. I'm wondering whether the increase of reported crashes is actually due to some change in LibreOffice qt5/kf5 code or rather the side-effect of something completely different (like more users having installed Kubuntu 20.04 since then, or some completely different commit that changed timing in some place, ...). @jmux: Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897784]
Created attachment 165978 Kubuntu shutdown crash bt It appears that one can just DL the text with a Launchpad login. So this is just a copy from the BT as reference. For whatever reason the clipboard object is still active, while the module is already gone, which is causing the crash. An other question is, what other packages were published that day, just in the case it's eventually no LO bug (I still think it is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
** 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892214] Re: vboxweb.service: Failed with result 'protocol' on Kernel 5.8.0-16.17-generic 5.8.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: virtualbox (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/1892214 Title: vboxweb.service: Failed with result 'protocol' on Kernel 5.8.0-16.17-generic 5.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1892214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
I have some further details about this bug! Not super positive, but still. First, I'm going to mark bug #676767 a duplicate of this. That's a slightly older bug with the same symptom, and a workaround (of deleting the cache) that doesn't seem to work in all cases. But ultimately, it's indistinguishable from this, so I'll dup it. Second, I was recently helping a user that was affected by this. They were on Ubuntu 14.04 moving to 16.04 (meaning a backup made with duplicity 0.6.23-1ubuntu4.1 and deja-dup 30.0-0ubuntu4.1, trying to restore with duplicity 0.7.06-2ubuntu2 and deja-dup 34.2-0ubuntu1.1). After investigating it with them, we found that many (100s!) of their volume files (size 50mb) were all zeros. That is, not valid gzip files but just a file full of zero-bytes. Other files seemed corrupted in a different way (not valid gzip, but not all zeros either). There were less of these. They did not use encryption. They stopped and resumed the backup a few times. It was altogether a single full backup. I don't know what to do with this information. But there it is. I note that we don't see this often anymore? The latest report here is from 18.04, which would be duplicity 0.7.17-0ubuntu1.1. It may be too optimistic to hope that it's solved now. But certainly less common than it used to be, I think? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897983] [NEW] cpuset_inherit in controllers from ubuntu_ltp failed on B-AWS-4.15
Public bug reported: 99224. 09/10 19:12:56 DEBUG| utils:0153| [stdout] startup='Thu Sep 10 19:09:04 2020' 99225. 09/10 19:12:56 DEBUG| utils:0153| [stdout] /opt/ltp/testcases/bin/cpuset_inherit_testset.sh: 109: /opt/ltp/testcases/bin/cpuset_inherit_testset.sh: let: not found 99226. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 1 TPASS: cpus: Inherited information is right! 99227. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 3 TPASS: cpus: Inherited information is right! 99228. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 5 TPASS: cpus: Inherited information is right! 99229. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 7 TPASS: cpus: Inherited information is right! 99230. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 9 TPASS: cpus: Inherited information is right! 99231. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 11 TFAIL: cpus: Test result - 0-7 Expected string - "0-" 99232. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 13 TPASS: mems: Inherited information is right! 99233. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 15 TPASS: mems: Inherited information is right! 99234. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 17 TPASS: mems: Inherited information is right! 99235. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 19 TPASS: mems: Inherited information is right! 99236. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 21 TPASS: mems: Inherited information is right! 99237. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 23 TPASS: mems: Inherited information is right! 99238. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 25 TPASS: cpu_exclusive: Inherited information is right! 99239. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 27 TPASS: cpu_exclusive: Inherited information is right! 99240. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 29 TPASS: mem_exclusive: Inherited information is right! 99241. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 31 TPASS: mem_exclusive: Inherited information is right! 99242. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 33 TPASS: mem_hardwall: Inherited information is right! 99243. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 35 TPASS: mem_hardwall: Inherited information is right! 99244. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 37 TPASS: memory_migrate: Inherited information is right! 99245. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 39 TPASS: memory_migrate: Inherited information is right! 99246. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 41 TPASS: memory_spread_page: Inherited information is right! 99247. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 43 TPASS: memory_spread_page: Inherited information is right! 99248. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 45 TPASS: memory_spread_slab: Inherited information is right! 99249. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 47 TPASS: memory_spread_slab: Inherited information is right! 99250. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 49 TPASS: sched_load_balance: Inherited information is right! 99251. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 51 TPASS: sched_load_balance: Inherited information is right! 99252. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 53 TPASS: sched_relax_domain_level: Inherited information is right! 99253. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 55 TPASS: sched_relax_domain_level: Inherited information is right! 99254. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 57 TPASS: sched_relax_domain_level: Inherited information is right! 99255. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 59 TPASS: sched_relax_domain_level: Inherited information is right! 99256. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 61 TPASS: sched_relax_domain_level: Inherited information is right! 99257. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 63 TPASS: sched_relax_domain_level: Inherited information is right! 99258. 09/10 19:12:56 DEBUG| utils:0153| [stdout] cpuset_inherit 65 TPASS: sched_relax_domain_level: Inherited information is right! 99259. 09/10 19:12:56 DEBUG| utils:0153| [stdout] tag=cpuset_inherit stime=1599764944 dur=2 exit=exited stat=1 core=no cu=68 cs=45 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: 4.15 amd64 bionic cpuset-inherit kqa-blocker sru-20200921 ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New --
[Bug 1605875] Re: screen lock cycles screens on/off constantly
I have this exact same problem on Ubuntu 18.04.5 After locking the screen, the monitor is cycled on and off after several seconds constantly unless I interact with the keyboard or mouse in which case it doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605875 Title: screen lock cycles screens on/off constantly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1605875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666203] Re: pam_tty_audit failed in pam_open_session
** Changed in: pam (Ubuntu Xenial) Status: Won't Fix => In Progress ** Changed in: pam (Ubuntu Xenial) Assignee: Don van der Haghen (donvdh) => Michael Hudson-Doyle (mwhudson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695899] Re: [MIR] python-scrypt, python-bcrypt
This bug was fixed in the package python-scrypt - 0.8.0-0.3ubuntu2 --- python-scrypt (0.8.0-0.3ubuntu2) groovy; urgency=medium [ Corey Bryant ] * d/gbp.conf: Update gbp configuration file. * d/control: Update Vcs-* links and maintainers. [ Chris MacNaughton ] * d/p/add-missing-rfc-test-vector.patch: Apply patch to enable additional test vectors from the scrypt RFC (LP: #1695899). * d/rules: Enable DEB_BUILD_MAINT_OPTIONS hardening at build time (LP: #1695899). -- Chris MacNaughton Tue, 08 Sep 2020 13:06:52 + ** Changed in: python-scrypt (Ubuntu) Status: Triaged => 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/1695899 Title: [MIR] python-scrypt, python-bcrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-bcrypt/+bug/1695899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
SRU for Focal testing.
Created 2 Vagrant boxes to cover the 2 main build cases of CPC (produced
of the Vagrant image and user of the hook changed)
box A: Created via ubuntu-bartender(https://github.com/chrisglass
/ubuntu-old-fashioned/tree/master/scripts/ubuntu-bartender) utilizing
the source download of the proposed package (found here in the web UI).
ran bartender using multipass as a provider with the following command
./ubuntu-bartender --livecd-rootfs-dir
/home/jchittum/dev01/troubleshooting/vagrant-testing/1874453/livecd-
rootfs --build-provider multipass -- --series focal --project ubuntu-cpc
--image-target vagrant
box B: Created via a Launchpad build utilizing a recipe pointed to
~livecd-rootfs ubuntu/focal. This created a livecd-rootfs package in a
personal PPA which was then used to run the build.
boxes were then added to the vagrant inventory
vagrant box add --name focal-sru-test-from-(bartender
|| lp)
2 directories were then created from-bartender & from-lp
Ran the following 2 test cases:
[Test Case 1]
-- vagrant up with minimal configuration --
1. made minimal Vagrantfiles in each directory
```
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "focal-sru-test-from-bartender" # Or from-lp
end
```
2. ran `time vagrant up`
3. observed that boxes successfully booted
4. observed that boxes booted in a reasonable amount of time (on my machine
~30s)
5. ensured the ability to SSH into the box
6. checked the guest system has mounted the default guest directory (./ on host
mounted to /vagrant on guest)
7. exited host and destroyed boxes (vagrant halt && vagrant destroy)
Both boxes worked.
[Test Case 2]
1. Update Vagrantfiles to override default serial connection and write file
```
Vagrant.configure("2") do |config|
NOW = Time.now.strftime("%d.%m.%Y.%H:%M:%S")
FILENAME = "serial-debug-%s.log" % NOW
config.vm.box = "focal-sru-test-from-bartender" # Or from-lp
config.vm.provider "virtualbox" do |vb|
vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]
vb.customize [ "modifyvm", :id, "--uartmode1", "file",
File.join(Dir.pwd, FILENAME) ]
end
end
```
2. ran `time vagrant up`
3. Observed that boxes successfully booted
4. observed the log file was created
5. observed that boxes booted in a reasonable amount of time (on my machine
~30s)
6. ensured the ability to SSH into the box
7. checked the guest system has mounted the default guest directory (./ on host
mounted to /vagrant on guest)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874453
Title:
ubuntu/focal64 very slow to boot and reboots once
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1874453/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897980] [NEW] Installer crashed
Public bug reported: During the installation, the installer has crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.132-0ubuntu2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 01:07:00 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1897980/+attachment/5415854/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897980 Title: Installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897442] Re: bug in upgrading to 18.04
The mirror of the Ubuntu archive which you have configured is not an official one and subsequently it was disabled during the release upgrade. Please either run the release upgrade with '--allow-third- party' or switch to using an official mirror of the Ubuntu archive. ** Changed in: ubuntu-release-upgrader (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/1897442 Title: bug in upgrading to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897465] Re: Ubuntu Freezes
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897465 Title: Ubuntu Freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1897465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878996] Re: Blueman uses incorrect hardcoded path to iptables binary
what needs to be done to get the fix into ubuntu 20.04? backport the patch from blueman 2.1.3 to 2.1.2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878996 Title: Blueman uses incorrect hardcoded path to iptables binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1878996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897474] Re: update aborts when ubuntu-minimal package not found
Reviewing the log file, /var/log/dist-upgrade/main.log, from your upgrade attempt there was a failure to communicate with the mirror of the Ubuntu archive which you use. This could either be due to an issue with your connection to the mirror or with the mirror itself. Regardless, this is an issue you'll need to sort out before the upgrade can complete. If after resolving the communication error with the mirror you are still unable to upgrade to a new release of Ubuntu please open a new bug report so we'll have fresh log files. Thanks and good luck! ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Tags added: connection-refused -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897474 Title: update aborts when ubuntu-minimal package not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1897474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
For me, as far I remember, to fix the issue on my local machine, I have to remove python and reinstalled it.It seems that after upgrading ubuntu18 to ubuntu focal, some python 2 footprints still remains, I am not sure if it was the cause of issue but after removing python and purging both python2 and the newly installed python 3, and reinstalled python3, It works. On Thu, 1 Oct 2020 at 00:25, Foobar <1891...@bugs.launchpad.net> wrote: > To be clear, I have since successfully upgraded but done so by: > > 0. (running apt-get update, dist-upgrade, etc to prepare) > 1. deinstalling (via apt-get) gdm3 > 2. booting into recovery mode & initiating networking > 3. running do-release-upgrade > 4. restarting the system. > > I don't think I can exactly 'recommend' this way of doing it, but for me > it was successful. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891165 > > Title: > gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but > 3.28.4-0ubuntu18.04.2 is to be installed > > Status in gsettings-desktop-schemas package in Ubuntu: > Confirmed > > Bug description: > I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 > install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run > sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in > https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. > But i got more errors > > > The following packages have unmet dependencies: >gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but > 3.28.4-0ubuntu18.04.2 is to be installed >libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but > 3.26.1-2ubuntu1 is to be installed > E: Error, pkgProblemResolver::Resolve generated breaks, this may be > caused by held packages. > > sudo ln -sf /usr/bin/python2.7 /usr/bin/python > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: mutter 3.28.4-0ubuntu18.04.2 > ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.16 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Aug 11 20:38:08 2020 > InstallationDate: Installed on 2020-02-08 (184 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > SourcePackage: mutter > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897610] Re: Wrong executable name in description
** Description changed: * lsb_release -rd: Description:Ubuntu 20.04.1 LTS Release:20.04 * apt-cache policy bat: bat: Installed: 0.12.1-1build1 Candidate: 0.12.1-1build1 Version table: *** 0.12.1-1build1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status --- The package description says: "In this package the executable and its manpage have been renamed from ‘bat’ to ‘batbat’ because of a file name clash with another Debian paclage." But the executable for `bat` is de facto `batcat` not `batbat` as the description states. Furthermore, there is a typo in the `package` word it the same sentence: it's "with another Debian paclage" instead of "with another Debian package". + + Also, the USAGE sections for --help flag and the man page are inconsistent: + - `batcat --help` output (correct): + + USAGE: + batcat [OPTIONS] [FILE]... + batcat + + - `man batcat` output (incorrect): + + USAGE + bat [OPTIONS] [FILE]... + + bat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897610 Title: Wrong executable name in description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-bat/+bug/1897610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883175] Autopkgtest regression report (pycodestyle/2.6.0-1~20.04.1)
All autopkgtests for the newly accepted pycodestyle (2.6.0-1~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: budgie-extras/1.0.2-0ubuntu1 (arm64, amd64, armhf, i386, ppc64el, s390x) update-manager/1:20.04.10.1 (arm64, amd64, armhf, ppc64el, s390x) ubuntu-release-upgrader/1:20.04.23 (arm64, amd64, armhf, ppc64el, s390x) 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#pycodestyle [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/1883175 Title: missing support for python3.8 language features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycodestyle/+bug/1883175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896299] Re: remote requires netstat installed
just a final note on this, sshuttle from trusty is still affected by this, and since focal does not install the 'net-tools' package (which provides netstat) by default, sshuttle from trusty to a default install of focal will fail. ** Description changed: [impact] the remote system sshuttle connects to must have netstat installed, or sshuttle fails [test case] from a xenial system, install sshuttle and attempt to create a sshuttle connection to a remote system that does not have netstat installed [regression potential] any regression would likely result in a failure to successfully create/initialize the sshuttle connection. it is unlikely any regression would cause problems after the tunnel is established. [scope] this is needed only for xenial. this is fixed upstream with commit 809fad537fa6977da3e3915f5a125e2a3d163254 which is included in v0.78.3 and later, so this is already fixed in bionic and later. + + note this bug does affect sshuttle in trusty, but that release is out of + standard support and into ESM only, so will not be patched (unless the + security team wishes to patch it in the ESM repository). ** Also affects: sshuttle (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: sshuttle (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896299 Title: remote requires netstat installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1896299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
