[Bug 1858347] Re: Wrong PID-File-Directory in /usr/sbin/keactrl in Ubuntu 20.04 LTS
** Changed in: isc-kea (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/1858347 Title: Wrong PID-File-Directory in /usr/sbin/keactrl in Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/1858347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809262] Re: Missing hooks library
Ran into this today, confirming. ** Changed in: isc-kea (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/1809262 Title: Missing hooks library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-kea/+bug/1809262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321296/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321294/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321292/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321298/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321291/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321290/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] Re: kernel-5.3.0-26 could not use appliicatins on core2 Duo
apport information ** Tags added: apport-collected bionic ** Description changed: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nakasima 1711 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-30 (140 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) + IwConfig: + enp2s0no wireless extensions. + + lono wireless extensions. + MachineType: System manufacturer P5K/EPU + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ja_JP.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 + ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-26-generic N/A + linux-backports-modules-5.3.0-26-generic N/A + linux-firmware1.173.14 + RfKill: + + Tags: bionic + Uname: Linux 5.3.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/06/2008 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0304 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: P5K/EPU + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: P5K/EPU + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321289/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860185] Re: kernel-5.3.0-26 could not boot up notePC
** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860185 Title: kernel-5.3.0-26 could not boot up notePC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321293/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321295/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321299/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321297/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] Re: kernel-5.3.0-26 could not use appliicatins on core2 Duo
I boot up 5.3.0-26 recovery mode. apport-collect 1860196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860196] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1860196/+attachment/5321300/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860196 Title: kernel-5.3.0-26 could not use appliicatins on core2 Duo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860185] 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/1860185 Title: kernel-5.3.0-26 could not boot up notePC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860101] Re: smc (Secret Maryo Chronicles) is not on Bionic's repositories anymore
May I point you to click through the 'Overview' https://launchpad.net/ubuntu/+source/smc and on to the full publishing history https://launchpad.net/ubuntu/+source/smc/+publishinghistory. The reasons given are FTBFS (fails to build from source), removed from Debian testing, Debian bug https://bugs.debian.org/812096, needs porting to CEGUI 0.8.4, no rdepends (no other package depends on smc). Similar publishing history is available regarding Debian: https://tracker.debian.org/pkg/smc. ** Bug watch added: Debian Bug tracker #812096 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812096 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860101 Title: smc (Secret Maryo Chronicles) is not on Bionic's repositories anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smc/+bug/1860101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860101] Re: smc (Secret Maryo Chronicles) is not on Bionic's repositories anymore
To get the package back to Ubuntu repositories, I suggest you contact Debian & Ubuntu Games Team. Email contact: debian-devel-ga...@lists.debian.org (mailing list) Public IRC channel: #debian-games on irc.debian.org (OFTC) ** Changed in: smc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860101 Title: smc (Secret Maryo Chronicles) is not on Bionic's repositories anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smc/+bug/1860101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860024] Re: squid-deb-proxy-client is missed in focal repositories
Looks like it got removed as part of the python2 removal (https://launchpad.net/ubuntu/+source/squid-deb- proxy/+publishinghistory), see also Debian bug https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=945738 for more details. I'm guessing someone would need to port the upstream source to python3 before the package can be reintroduced. ** Bug watch added: Debian Bug tracker #945738 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945738 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860024 Title: squid-deb-proxy-client is missed in focal repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1860024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859819] Re: bionic/linux-azure-5.3: 5.3.0-1010.11~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859820 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Thursday, 16. January 2020 21:51 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859819 Title: bionic/linux-azure-5.3: 5.3.0-1010.11~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Taha, Did the screenpad work out of the box or did you have to download/setup additional drivers ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859691] Re: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859691 Title: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859691] Re: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859692 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 - phase: Ready for Promote to Proposed - phase-changed: Friday, 17. January 2020 16:58 UTC + phase: Promote to Proposed + phase-changed: Saturday, 18. January 2020 09:55 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859691 Title: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859691] Re: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859692 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 phase: Promote to Proposed phase-changed: Saturday, 18. January 2020 09:55 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859691 Title: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859795] Re: bionic/linux-aws: 4.15.0-1058.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1859705 + kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859795 Title: bionic/linux-aws: 4.15.0-1058.60 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860204] [NEW] GNOME3 notification background layer paints over notification text if mouse is moved in notification area
Public bug reported: Hello, I do not know if it is a problem of the current proprietary driver or xorg or GNOME. I tried my best to include all the info you might need. Problem: When I receive a notification in the notification centre of GNOME, it shows up in the notification bubble. If the text in the notification bubble is longer than the amount of text can be shown at once, the it needs to be opened. If I click on the bubble, it opens, but if I move my mouse pointer inside the said notification the light greyish background color of the notification area paints over the text rendering it to be unreadable. If I wait some seconds then this 'layer' disappears partly or completely. Since my VGA works fine under heavy load (GPU intensive applications and games) I guess it is a software related bug --- Release:19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 NVIDIA Driver Version: 435.21 VGA: GTX 960 4GB ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 11:21:51 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 960] [1458:36c2] InstallationDate: Installed on 2020-01-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860204 Title: GNOME3 notification background layer paints over notification text if mouse is moved in notification area To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850439] Re: No sound on ASUS UX534FT
Same problem on ASUS Zenbook 15 UX533FTC-A8157R # hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.9G5mT1GK4nF SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x02c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1a61 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable) Memory Range: 0xc410-0xc41f (rw,non-prefetchable) IRQ: 148 (1016 events) Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci is active Driver Activation Cmd: "modprobe snd_sof_pci" Config Status: cfg=new, avail=yes, need=no, active=unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860205] [NEW] DRBD not work after Upgrade to linux-image-5.3.0-26-generic
Public bug reported: Hi, After Kernel upgrade and System Reboot DRBD not mohr working. System nfs01 ## lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 uname -a Linux nfs01 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux cat /proc/drbd version: 8.4.11 (api:1/proto:86-101) srcversion: 1A039827F6ABC247A25EC61 1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r- ns:45890195 nr:43260388 dw:86292083 dr:1061858 al:6452 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:200856 System nfs02 ## lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 uname -a Linux nfs02 5.3.0-26-generic #28~18.04.1-Ubuntu SMP Wed Dec 18 16:40:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux cat /proc/drbd version: 8.4.11 (api:1/proto:86-101) srcversion: A7701877BDDC2E38E3FC52B service drbd start /var/log/kern.log ### Jan 18 11:46:42 nfs02. kernel: [ 3607.812647] drbd: initialized. Version: 8.4.11 (api:1/proto:86-101) Jan 18 11:46:42 nfs02. kernel: [ 3607.812649] drbd: srcversion: A7701877BDDC2E38E3FC52B Jan 18 11:46:42 nfs02. kernel: [ 3607.812649] drbd: registered as block device major 147 ### /var/log/syslog ### Jan 18 11:46:42 nfs02. kernel: [ 3607.812647] drbd: initialized. Version: 8.4.11 (api:1/proto:86-101) Jan 18 11:46:42 nfs02. kernel: [ 3607.812649] drbd: srcversion: A7701877BDDC2E38E3FC52B Jan 18 11:46:42 nfs02. kernel: [ 3607.812649] drbd: registered as block device major 147 Jan 18 11:46:42 nfs02. drbd[25327]: * Starting DRBD resources Jan 18 11:46:42 nfs02. drbd[25327]: [ Jan 18 11:46:42 nfs02. drbd[25327]: create res: NFS:failed(new-resource:20) Jan 18 11:46:42 nfs02. drbd[25327]:prepare disk: [skipped:NFS] Jan 18 11:46:42 nfs02. drbd[25327]: adjust disk: [skipped:NFS] Jan 18 11:46:42 nfs02. drbd[25327]: adjust net: [skipped:NFS] Jan 18 11:46:42 nfs02. drbd[25327]: ] Jan 18 11:46:52 nfs02. drbd[25327]: WARN: stdin/stdout is not a TTY; using /dev/consoleoutdated-wfc-timeout has to be shorter than degr-wfc-timeout Jan 18 11:46:52 nfs02. drbd[25327]: outdated-wfc-timeout implicitly set to degr-wfc-timeout (120s) Jan 18 11:46:52 nfs02. drbd[25327]: error determining which timeout to use: minor not available Jan 18 11:46:52 nfs02. drbd[25327]:...done. ### /var/log/dpkg.log 2020-01-17 18:15:39 install linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:39 status half-installed linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:40 status unpacked linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:40 status unpacked linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:46 upgrade linux-image-generic-hwe-18.04:amd64 5.0.0.37.95 5.3.0.26.95 2020-01-17 18:15:46 status half-configured linux-image-generic-hwe-18.04:amd64 5.0.0.37.95 2020-01-17 18:15:46 status unpacked linux-image-generic-hwe-18.04:amd64 5.0.0.37.95 2020-01-17 18:15:46 status half-installed linux-image-generic-hwe-18.04:amd64 5.0.0.37.95 2020-01-17 18:15:46 status half-installed linux-image-generic-hwe-18.04:amd64 5.0.0.37.95 2020-01-17 18:15:46 status unpacked linux-image-generic-hwe-18.04:amd64 5.3.0.26.95 2020-01-17 18:15:46 status unpacked linux-image-generic-hwe-18.04:amd64 5.3.0.26.95 2020-01-17 18:15:47 configure linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:47 status unpacked linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:47 status half-configured linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:47 status installed linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:47 status triggers-pending linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:48 configure linux-image-generic-hwe-18.04:amd64 5.3.0.26.95 2020-01-17 18:15:48 status unpacked linux-image-generic-hwe-18.04:amd64 5.3.0.26.95 2020-01-17 18:15:48 status half-configured linux-image-generic-hwe-18.04:amd64 5.3.0.26.95 2020-01-17 18:15:48 status installed linux-image-generic-hwe-18.04:amd64 5.3.0.26.95 2020-01-17 18:15:48 trigproc linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:15:48 status half-configured linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-17 18:16:04 status installed linux-image-5.3.0-26-generic:amd64 5.3.0-26.28~18.04.1 2020-01-18 06:21:59 status installed linux-image-5.0.0-36-generic:amd64 5.0.0-36.39~18.04.1 2020-01-18 06:21:59 remove linux-image-5.0.0-36-generic:amd64 5.0.0-36.39~18.04.1 2020-01-18 06:21:59 status half-configured linux-image-5.0.0-36-generic:amd64 5.0.0-36.39~18.04.1 2020-01-18 06:21:59 status half-installed linux-image-5.0.0-36-generic:amd64 5.0.0-36.39~18.04.1 2020-01-18 06:22:00 status config-files linux-image-5.0.0-36-generic:amd64 5.0.0-36.39~18.04.1 2020-01-18 06:22:00 status config-files linux-image-5.0.0-36-generic:amd64 5.0.0-36.39
[Bug 1859704] Re: xenial/linux-hwe: 4.15.0-75.85~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1859705 + kernel-stable-master-bug: '1860123' packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 16. January 2020 10:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1859799 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859704 Title: xenial/linux-hwe: 4.15.0-75.85~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859819] Re: bionic/linux-azure-5.3: 5.3.0-1010.11~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859820 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Thursday, 16. January 2020 21:51 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Ongoing -- package copied to Proposed signed:building variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859819 Title: bionic/linux-azure-5.3: 5.3.0-1010.11~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859820] Re: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1859819 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859820 Title: eoan/linux-azure: 5.3.0-1010.11 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860206] [NEW] Wireguard is broken after yesterdays apt-get dist-upgrade
Public bug reported: [Ubuntu server 18.04.1] Yesterdays apt-get update && apt-get dist-upgrade broke wireguard on all systems. This is a little annoying if some of this systems are located 1600km away and the wireguard-vpn is used to reach them... Packages relevant upgraded: linux-image-5.0.0-37-generic -> linux-image-5.3.0-26-generic The wireguard-dkms was rebuilded during this upgrade, and loads into the new kernel without problems: [5.038245] wireguard: loading out-of-tree module taints kernel. [5.038396] wireguard: module verification failed: signature and/or required key missing - tainting kernel [5.039066] wireguard: WireGuard 0.0.20191219 loaded. See www.wireguard.com for information. [5.039067] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved. Wireguard is configured through systemd-networkd, the config has not changed since months. There are no errors/warnings other signs of problems regarding wireguard in any log. But Wireguard just don't transfer any data, with TCP-Dump I can see that the wireguard-server don't answer to any of the packets that are arriving from not affected clients. And affected clients are not sending out any data to the wireguard server. One thing is eye-catching, in the output of wg on the affected devices the peers are missing: Affected device: interface: wg0 public key: xxx private key: (hidden) listening port: 443 Not affected device: interface: wg0 public key: xxx private key: (hidden) listening port: 443 peer: xxx preshared key: (hidden) endpoint: xxx allowed ips: xxx transfer: 0 B received, 2.89 KiB sent persistent keepalive: every 25 seconds Config of one device: 30-wg0.netdev: [NetDev] Name = wg0 Kind = wireguard Description = Wireguard [WireGuard] PrivateKey = xxx # PublicKey = xxx ListenPort = xxx [WireGuardPeer] PublicKey = xxx PresharedKey = xxx AllowedIPs = xxx Endpoint = xxx PersistentKeepalive = 25 30-wg0.network: [Match] Name = wg0 [Link] MTUBytes=1300 [Network] DNS = xxx DNS = xxx Domains=xxx [Address] Address = xxx [Address] Address = xxx [Route] Gateway = xxx Destination = xxx Metric=5 Full List of Packages updated: Start-Date: 2020-01-17 14:40:50 Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confold -o Dpkg::Options::=--force-confdef --force-yes dist-upgrade Install: linux-image-5.3.0-26-generic:amd64 (5.3.0-26.28~18.04.1, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28~18.04.1, automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28~18.04.1, automatic), linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28~18.04.1, automatic), linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28~18.04.1, automatic) Upgrade: php7.2-bz2:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-common:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-cli:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-fpm:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-mysql:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), linux-headers-generic-hwe-18.04:amd64 (5.0.0.37.95, 5.3.0.26.95), php7.2-sqlite3:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-json:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-opcache:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-curl:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-xml:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-intl:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-zip:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-mbstring:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-readline:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), php7.2-gd:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), linux-image-generic-hwe-18.04:amd64 (5.0.0.37.95, 5.3.0.26.95), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), linux-generic-hwe-18.04:amd64 (5.0.0.37.95, 5.3.0.26.95), php7.2-pgsql:amd64 (7.2.24-0ubuntu0.18.04.1, 7.2.24-0ubuntu0.18.04.2), libdrm-common:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-17 14:46:41 ** Affects: wireguard-linux Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - Yesterdays apt-get update && apt-get dist-upgrade broke wireguard on all - systems. This is a little annoying if some of this systems are located - 1600km away and the wireguard-vpn is used to reach them... + [Ubuntu server 18.04.1] + Yesterdays apt-get update && apt-get dist-upgrade broke wireguard on all systems. This is a little annoying if some of this systems are located 1600km away and the wireguard-vpn is used to reach them... Packages relevant upgraded: linux-image-5.0.0-37-generic -> linux-image-5.3.0-26-generic The wireguard-dkms was rebuilded during this upg
Re: [Bug 1851956] Re: Initialization too slow, about 2 minutes. After is normal.
Ok!!! Thanks Em qui., 5 de dez. de 2019 às 06:56, Daniel van Vugt < daniel.van.v...@canonical.com> escreveu: > It sounds like the problem is already fixed in a later kernel. Maybe > just try installing a newer kernel then: > > https://kernel.ubuntu.com/~kernel-ppa/mainline/ > > and see what was the earliest version to fix the problem. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > ** Summary changed: > > - Initialization too slow, about 2 minutes. After is normal. > + [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After is > normal. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851956 > > Title: > [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After > is normal. > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > When init the grub boot, stop and wait for 2 minutes, circa... > After this time, normal speed and OS load normally, no problem !!! > Ubuntu Studio 18.04 LTS. Sony Vaio VPCEE45B. > Ubuntu Studio 20.04 (Daily) work fine, without wait > Thanks > > > (My english is bad,,,sorry) > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-66.75-lowlatency 4.15.18 > Uname: Linux 4.15.0-66-lowlatency x86_64 > ApportVersion: 2.20.9-0ubuntu7.9 > Architecture: amd64 > CompositorRunning: None > Date: Sat Nov 9 16:26:42 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD > 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) > Subsystem: Sony Corporation RS880M [Mobility Radeon HD 4225/4250] > [104d:9077] > InstallationDate: Installed on 2019-11-08 (1 days ago) > InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release > amd64 (20180426) > MachineType: Sony Corporation VPCEE45FB > ProcEnviron: >LANGUAGE=pt_BR >PATH=(custom, no user) >LANG=pt_BR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-lowlatency > root=/dev/mapper/ubuntu--studio--vg-root ro locale=pt_BR quiet splash > vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/09/2010 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: R0200Z5 > dmi.board.asset.tag: N/A > dmi.board.name: VAIO > dmi.board.vendor: Sony Corporation > dmi.board.version: N/A > dmi.chassis.asset.tag: N/A > dmi.chassis.type: 10 > dmi.chassis.vendor: Sony Corporation > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnInsydeCorp.:bvrR0200Z5:bd12/09/2010:svnSonyCorporation:pnVPCEE45FB:pvrC8002NHR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: > dmi.product.family: VAIO > dmi.product.name: VPCEE45FB > dmi.product.version: C8002NHR > dmi.sys.vendor: Sony Corporation > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Sat Nov 9 15:54:20 2019 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.19.6-1ubuntu4.3 > xserver.video_driver: radeon > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851956/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851956 Title: [Sony Vaio VPCEE45FB] Initialization too slow, about 2 minutes. After is normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859704] Re: xenial/linux-hwe: 4.15.0-75.85~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 16. January 2020 10:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-deeplens: bug 1859799 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859704 Title: xenial/linux-hwe: 4.15.0-75.85~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
I take it as given that Snap and various use cases were considered important enough to use a top-level directory in $HOME. That said, you can call me a pedantic, persnickety, nitpicker, but I dislike the default name "$HOME/snap" and that it's not configurable. The default name should follow the existing title-case convention, and it should be plural for a directory that contains multiple instances of the item class -- e.g. Downloads, Pictures, Videos, and even Music (a mass noun). I don't see "Snap" as a mass noun for Snap packages, so the default name should be "$HOME/Snaps". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859819] Re: bionic/linux-azure-5.3: 5.3.0-1010.11~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859820 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Thursday, 16. January 2020 21:51 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:building + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859819 Title: bionic/linux-azure-5.3: 5.3.0-1010.11~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859798] Re: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1859705 + kernel-stable-master-bug: '1860123' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1859797 xenial/linux-azure/azure-kernel: bug 1859796 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1859797 xenial/linux-azure/azure-kernel: bug 1859796 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859798 Title: xenial/linux-azure: 4.15.0-1067.72 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858533] Re: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1858534 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1858532 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858533 Title: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
The HWE package now force-upgrades to 5.3.0, rendering that entire package useless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857378] Re: Please drop i386 dkms package, as there are no i386 kernel
Or don't. https://discourse.ubuntu.com/t/intel-32bit-packages-on-ubuntu-from-19-10-onwards/11263/90 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857378 Title: Please drop i386 dkms package, as there are no i386 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1857378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860207] [NEW] Erreur lors de l'installation de 18.04.3 LTS
Public bug reported: Le plantage à eu leu lors de l'installation depuis une clef USB ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 Date: Sat Jan 18 12:39:29 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860207 Title: Erreur lors de l'installation de 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1860207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859691] Re: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859692 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 - phase: Promote to Proposed - phase-changed: Saturday, 18. January 2020 09:55 UTC + phase: Testing + phase-changed: Saturday, 18. January 2020 11:51 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859691 Title: bionic/linux-raspi2-5.3: 5.3.0-1017.19~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Pending -- ready for review trackers: + bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 - xenial/linux-hwe: bug 1860122 + xenial/linux-azure: bug 1859798 + xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844613] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844613 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1844613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853196] Re: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853196 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1853196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
Did you build a custom kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (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/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771] Re: Reboot after resume from suspend (deep)
A similar case for Linux Mint 19.3 Tricia after upgrading to the new kernel i.e. 5.3.0-26-generic no switch to suspend option ... Only hard reset helps in logs nothing specific can be found except for entries: Jan 18 12:05:08 kris-R780 kernel: [49.932794] PM: suspend entry (deep) Jan 18 12:06:09 kris-R780 kernel: [0.00] microcode: microcode updated early to revision 0x11, date = 5/8/2018 on earlier kernels the suspend option worked OK 4.15.0-54-generic - OK 4.15.0-72-generic - OK 4.15.0-74-generic - OK 5.0.0-32-generic - OK 5.0.0-37-generic - OK 5.3.0-26-generic - ERROR ! ( suspend ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
Probably the same as Bug #1851162 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843385 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1843385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488620] Re: Add LZ4 support to initramfs-tools
Can this be closed/tagged as fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488620 Title: Add LZ4 support to initramfs-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860208] [NEW] Can not install new Ubuntu (19.10 I guess)
Public bug reported: There is only one thing that is not as ordinary as it was before. I've selected erasing disk with ZFS file system installation. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 13:40:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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 eoan third-party-packages ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860208 Title: Can not install new Ubuntu (19.10 I guess) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738774] Re: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display
This is still an issue, and due to HiDPI getting more and more common, Ubuntu should really look into this to give users a good experience with the setups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1738774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
And in Clear Linux: https://community.clearlinux.org/t/new-installation- no-sound-swift-5-i7-1065gt-iris-plus/2407/14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
A Fedora user reported the same issue in https://bugzilla.redhat.com/show_bug.cgi?id=1772498#c16, and the created an upstream GitHub issue https://github.com/thesofproject/sof/issues/2126. Please update the meta-information of this bug accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
[Sorry, I wasn’t subscribed to the notifications.] @hui.wang, your attached firmware, what version is that? $ md5sum sof-icl.ri 2ca373e6254b0e9b37439f7a31984973 /dev/shm/sof-icl.ri @adamfubuntu, do you still have the problem *without* `dsp_driver=0` on an up-to-date Ubuntu 19.10 with Linux 5.5-rc6? ** Bug watch added: Red Hat Bugzilla #1772498 https://bugzilla.redhat.com/show_bug.cgi?id=1772498 ** Bug watch added: github.com/thesofproject/sof/issues #2126 https://github.com/thesofproject/sof/issues/2126 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860206] Re: Wireguard is broken after yesterdays apt-get dist-upgrade
Update: If I build a config with my data to according to the wg manpage and pass it to wg setconf, I See the peers again with wg. So, maybe it is a problem between systemd-networkd and the new 5.3 kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860206 Title: Wireguard is broken after yesterdays apt-get dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/wireguard-linux/+bug/1860206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Tags removed: vivid ** Tags added: bionic focal xenial ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1859515] Re: device no longer recognized after activating Tethering USB
Yes, I'm sure: I changed nothing on my device. Il 14/01/20 15:07, Sebastien Bacher ha scritto: > Thank you for your bug report. Can you try with the phone on another > computer/OS? Are you sure it's not a change on the phone side? > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => Low > > ** Changed in: nautilus (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/1859515 Title: device no longer recognized after activating Tethering USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1859515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
Nope. Stock kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
dbus: failed to construct signal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835114] Re: [MIR] ec2-instance-connect
** Tags added: id-5e21ca0949c79659969a46bd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835114 Title: [MIR] ec2-instance-connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1835114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860142] Re: Please update ec2-instance-connect to 1.1.12 release
** Tags added: id-5e1e340b6338410899d33213 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860142 Title: Please update ec2-instance-connect to 1.1.12 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1860142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850201] Re: Memory usage grows when locking/unlocking the screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1850201 Title: Memory usage grows when locking/unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991004] Re: Replace libusb-0.1 with libusb-compat-0.1
IMO this should be above "wishlist" importance, because the lcdproc project had to disable a lot of display drivers (such as hd44780-lcd2usb) still relying on libusb 0.1 API, while libusb- compat-0.1 probably would've solved their issues easily. An LCD that worked perfectly with Ubuntu 16.04 is now dead in 18.04. I fail to see why Debian maintainers are so worried about introducing some corner case bugs while things are breaking completely without the compatibility wrapper. Apparently it's just a matter of packaging libusb-compat-0.1 and making it conflict with libusb-0.1 so that only either one can be used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991004 Title: Replace libusb-0.1 with libusb-compat-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/991004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
attached the output ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+attachment/5321345/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860213] [NEW] xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Public bug reported: the program was unexpectedly closed while setting the color profile ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xfce4-settings 4.14.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 18 14:45:53 2020 ExecutablePath: /usr/bin/xfce4-color-settings InstallationDate: Installed on 2020-01-18 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: xfce4-color-settings --socket-id=25176188 ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1e3b55c671 :mov(%rax),%rax PC (0x7f1e3b55c671) ok source "(%rax)" (0x10102c09e60080) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xfce4-settings StacktraceTop: g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: xfce4-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860213 Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1860213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860172] Re: Crashes all the time
added syslog ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860172/+attachment/5321346/+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/1860172 Title: Crashes all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860214] [NEW] xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a duplicate of bug 1860213 *** https://bugs.launchpad.net/bugs/1860213 Public bug reported: This is a duplicate of Bug #1860213 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xfce4-settings 4.14.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Sat Jan 18 15:13:47 2020 ExecutablePath: /usr/bin/xfce4-color-settings InstallationDate: Installed on 2020-01-18 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: xfce4-color-settings --socket-id=25194775 ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f873ad4e671 :mov(%rax),%rax PC (0x7f873ad4e671) ok source "(%rax)" (0x10102c09e60080) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xfce4-settings StacktraceTop: g_type_check_instance_is_fundamentally_a () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: xfce4-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1860213 xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860214 Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1860214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860214] Re: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a duplicate of bug 1835579 *** https://bugs.launchpad.net/bugs/1835579 ** This bug is no longer a duplicate of bug 1860213 xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() ** This bug has been marked a duplicate of private bug 1835579 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860214 Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1860214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860213] Re: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a duplicate of bug 1835579 *** https://bugs.launchpad.net/bugs/1835579 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1835579, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1860213/+attachment/5321347/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1860213/+attachment/5321349/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1860213/+attachment/5321352/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1860213/+attachment/5321353/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1860213/+attachment/5321354/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1860213/+attachment/5321355/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1860213/+attachment/5321356/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1835579 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860213 Title: xfce4-color-settings crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1860213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823730] Re: Bionic: interface stuck in state "configuring" on a VM with two NICs, DHCP, and the secondary NIC configured to ignore routes from DHCP
*** This bug is a duplicate of bug 1804478 *** https://bugs.launchpad.net/bugs/1804478 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1823730 Title: Bionic: interface stuck in state "configuring" on a VM with two NICs, DHCP, and the secondary NIC configured to ignore routes from DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860215] [NEW] During a fresh install of Ubuntu 18.04 LTS at the end of installation the program flashed message stating that bootloader cannot be installed on any of the drives.
Public bug reported: All available drives were offered for installation, but none of them worked. Not sure what will happen next when I reboot the desktop. The message said that it may not boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 20:46:34 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860215 Title: During a fresh install of Ubuntu 18.04 LTS at the end of installation the program flashed message stating that bootloader cannot be installed on any of the drives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1860215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860216] [NEW] During a fresh install of Ubuntu 18.04 LTS at the end of installation the program flashed message stating that bootloader cannot be installed on any of the drives.
Public bug reported: All available drives were offered for installation, but none of them worked. Not sure what will happen next when I reboot the desktop. The message said that it may not boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 20:46:34 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860216 Title: During a fresh install of Ubuntu 18.04 LTS at the end of installation the program flashed message stating that bootloader cannot be installed on any of the drives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1860216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1860122, bug 1859704 + xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610075] Re: kubuntu-driver-manager application opens to show nothing
I am testing the Plasma 5.18 beta and noticed this behavior. I have another 19.10 install that's at Plasma 5.17.5 and it is doing the same thing. The window loads and shows the "Collecting information about your system" message but doesn't get any further. I've left it open for 30 minutes and no change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610075 Title: kubuntu-driver-manager application opens to show nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1610075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860217] [NEW] dpkg-reconfigure clamav-daemon in infinite loop
Public bug reported: There appears to be another issue with > dpkg-reconfigure clamav-daemon Like in #1792051, the command ends up in an infinite loop, just that this time it happens between 'Log file for clamav-daemon' and 'Do you want to enable log rotation?', with one more step between also included in the loop. Purged and reinstalled the package with no effect. Effected package: clamav-daemon 0.102.1+dfsg-0ubuntu0.19.10.2 (arm64) ** Affects: clamav (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/1860217 Title: dpkg-reconfigure clamav-daemon in infinite loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1860217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860219] [NEW] Resolve the error
Public bug reported: I couldn't install the ubuntu because of this error.Please try to resolve this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 21:22:59 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860219 Title: Resolve the error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1860219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860218] [NEW] LVM and seperate home installation or let users change partition manuelly
Public bug reported: It's a pitty, that i can't create a LVM partition manuelly at the Installation. It would be great if i could create a seperated /home Directory. ** Affects: ubiquity (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/1860218 Title: LVM and seperate home installation or let users change partition manuelly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860221] [NEW] 5.3.0.26.95 breaks Nvidia dual monitor support in Linux Mint 19.3
Public bug reported: I am running Linux Mint Cinnamon 19.3 Tricia on a Lenovo ThinkPad W530 with Nvidia Quadro K2000M / Intel HD 4000 switchable GPU running nvidia driver 390.116. After upgrading from 5.0.0.37.95 to 5.3.0.26.95 a second monitor can no longer be detected. The Nvidia X Server Settings dialog box no longer lists connected displays. ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Attachment added: "whereisthrest.png" https://bugs.launchpad.net/bugs/1860221/+attachment/5321390/+files/whereisthrest.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860221 Title: 5.3.0.26.95 breaks Nvidia dual monitor support in Linux Mint 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1860221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860218] Re: LVM and seperate home installation or let users change partition manuelly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (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/1860218 Title: LVM selection should create separate home lv or manual partition should have lvm as partition option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860217] Re: dpkg-reconfigure clamav-daemon in infinite loop
** Description changed: There appears to be another issue with > dpkg-reconfigure clamav-daemon Like in #1792051, the command ends up in an infinite loop, just that this time it happens between 'Log file for clamav-daemon' and 'Do you want to enable log rotation?', with one more step between also included in the loop. Purged and reinstalled the package with no effect. Effected package: clamav-daemon 0.102.1+dfsg-0ubuntu0.19.10.2 (arm64) + + EDIT: I was able to reproduce the error on a different system (also + 0.102.1+dfsg-0ubuntu0.19.10.2, just amd64 instead) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860217 Title: dpkg-reconfigure clamav-daemon in infinite loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1860217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Package changed: llvm-toolchain-9 (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860218] Re: LVM selection should create separate home lv or manual partition should have lvm as partition option
** Summary changed: - LVM and seperate home installation or let users change partition manuelly + LVM selection should create separate home lv or manual partition should have lvm as partition option -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860218 Title: LVM selection should create separate home lv or manual partition should have lvm as partition option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860218] Re: LVM selection should create separate home lv or manual partition should have lvm as partition option
** Attachment added: "ubiquity-lvm-2.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+attachment/5321392/+files/ubiquity-lvm-2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860218 Title: LVM selection should create separate home lv or manual partition should have lvm as partition option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860218] Re: LVM selection should create separate home lv or manual partition should have lvm as partition option
Request to create separate home logical volume or allow manual LVM in Ubiquity. Currently it only creates root and swap logical volumes when LVM option is selected for automated installation type. When manual partitioning is selected, there is no LVM option unlike in Debian installer. ** Attachment added: "ubiquity-lvm-1.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+attachment/5321391/+files/ubiquity-lvm-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860218 Title: LVM selection should create separate home lv or manual partition should have lvm as partition option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1860218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
With virt-manager the crashes occur with Cirrus, QXL, VGA video drivers. But does not occur with VMVGA video driver. Possibly kernel (drm) issue. ** Also affects: linux (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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hi everyone, Thank you very much Daniel for your attention and recommendations but ..; 1. I installed ubuntu 20.04, everything started fine, but it failed again in the same way as in ubuntu 18, before this I was testing fedora 31 and the same errors were presented for both ubuntu 18, 20 and fedora 31, (screen crash, black screen with the message [2658.28 ...] systemd-journald [378]: failed to write entry (22 items, 749 bytes), ignoring: read-only file system). 2. Thinking that it may be a hardware error especially of the micron m2 SSD, contact dell technical service and just have an answer from them I will comment on it by this means. 3. I also cannot get the id of the .crash file, but when I select to report the error, an error window appears indicating the following: "The problem cannot be reported: It has some packages installed with obsolete versions bsdutils, libblkid1, libmount1, libsmartcols1, libuuid1, mount, utillinux, uuid-runtime " Any advice to fix those versions of the packages? Thank you very much to all! ** Attachment added: "crash.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1859730/+attachment/5321393/+files/crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860224] Re: package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 1708777 *** https://bugs.launchpad.net/bugs/1708777 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1708777, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1708777 package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860224 Title: package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1860224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860224] [NEW] package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 1708777 *** https://bugs.launchpad.net/bugs/1708777 Public bug reported: removing this steam server I got an error. I removed it with Synaptic, regards John ProblemType: Package DistroRelease: Ubuntu 16.04 Package: steam (not installed) ProcVersionSignature: Ubuntu 4.4.0-170.199-generic 4.4.200 Uname: Linux 4.4.0-170-generic i686 ApportVersion: 2.20.1-0ubuntu2.21 AptOrdering: steam-launcher: Remove steam: Install steam: Configure NULL: ConfigurePending Architecture: i386 Date: Sat Jan 18 18:14:46 2020 DpkgTerminalLog: Preparing to unpack .../steam_1%3a1.0.0.48-1ubuntu4_i386.deb ... dpkg: error processing archive /var/cache/apt/archives/steam_1%3a1.0.0.48-1ubuntu4_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 DuplicateSignature: package:steam:(not installed) Preparing to unpack .../steam_1%3a1.0.0.48-1ubuntu4_i386.deb ... dpkg: error processing archive /var/cache/apt/archives/steam_1%3a1.0.0.48-1ubuntu4_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-05-31 (232 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: steam Title: package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: steam (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860224 Title: package steam (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1860224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796437] 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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843873] Re: Sound distored on Hades Canyon NUC
Finally I can confirm that issue has been fixed with kernel 5.5-rc5 suggested by Kai-Heng Feng. Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843873 Title: Sound distored on Hades Canyon NUC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860226] [NEW] broadcom wifi broken at 5.3.0.26.95 kernel update
Public bug reported: Kernel came in with regular maintenance. I DID notice some error messages in Update Manager log about broadcom drivers, but didn't realize it was for real. Upon boot, couldn't access wifi. Booted using 5.0 kernel and all is well again. ubuntu-bug linux output -- N/A version.log attached lspci-vnvn.log attached Update Manager log (apt-term.log) attached ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "KernelBugReport.tar.gz" https://bugs.launchpad.net/bugs/1860226/+attachment/5321399/+files/KernelBugReport.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860226 Title: broadcom wifi broken at 5.3.0.26.95 kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
** Changed in: ubuntu-mate-meta (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-mate-welcome (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: gstreamer-vaapi (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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1796437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
I found the real reason for the crashes. The problematic package is the `gstreamer1.0-vaapi` (see https://packages.ubuntu.com/focal/gstreamer1.0-vaapi). It is a dependency of `ubuntu-restricted-addons` (see https://packages.ubuntu.com/focal/ubuntu-restricted-addons). So ubuntu-mate-welcome and for example Cheese may be fixed by removing this package with ``` sudo apt-get purge gstreamer1.0-vaapi sudo apt-get autoremove --purge # to remove libgstreamer-plugins-bad1.0-0 (is not a problem) ``` So please carefully analyze the crash dumps for errors in `gstreamer1.0-vaapi` and fix this package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1796437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860227] [NEW] package linux-firmware-raspi2 1.20190215-0ubuntu3 failed to install/upgrade: installed linux-firmware-raspi2 package post-installation script subprocess returned error exit status
Public bug reported: While upgrading my system ( command do-release-upgrade) ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-firmware-raspi2 1.20190215-0ubuntu3 Uname: Linux 4.4.38-v7+ armv7l ApportVersion: 2.20.10-0ubuntu27.3 Architecture: armhf Date: Sat Jan 18 20:19:25 2020 Dependencies: DuplicateSignature: package:linux-firmware-raspi2:1.20190215-0ubuntu3 Setting up linux-firmware-raspi2 (1.20190215-0ubuntu3) ... Error: missing /boot/firmware, did you forget to mount it? dpkg: error processing package linux-firmware-raspi2 (--configure): installed linux-firmware-raspi2 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed linux-firmware-raspi2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: linux-firmware-raspi2 Title: package linux-firmware-raspi2 1.20190215-0ubuntu3 failed to install/upgrade: installed linux-firmware-raspi2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2020-01-18 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-02-11T20:21:47.356345 ** Affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860227 Title: package linux-firmware-raspi2 1.20190215-0ubuntu3 failed to install/upgrade: installed linux-firmware-raspi2 package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1860227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860227] Re: package linux-firmware-raspi2 1.20190215-0ubuntu3 failed to install/upgrade: installed linux-firmware-raspi2 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860227 Title: package linux-firmware-raspi2 1.20190215-0ubuntu3 failed to install/upgrade: installed linux-firmware-raspi2 package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1860227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860226] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1860226 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860226 Title: broadcom wifi broken at 5.3.0.26.95 kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860228] [NEW] addition of zfsutils-linux scrib every 2nd sunday
Public bug reported:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
==System information==
{{{
TypeVersion/Name
Distribution Name Ubuntu
Distribution Version18.04.3 LTS
Linux Kernel4.15.0-73-generic
Architecturex86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
}}}
==When did this file get added into zfsonlinux ecosystem?==
{{{
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] &&
/usr/lib/zfs-linux/scrub
}}}
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the month to
avoid system I/O overload on any one day of the month, like this:
{{{
# zfsmain scrub: 2:30AM 7th of every month
30 02 7 * * /sbin/zpool scrub zfsmain
# zstorage scrub: 2:30AM 5th of every month
30 02 5 * * /sbin/zpool scrub zstorage
# zmedia scrub: 1:00AM 14th of every month
00 01 14 * * /sbin/zpool scrub zmedia
# zstorage scrub: 2:30AM 21st of every month
30 02 21 * * /sbin/zpool scrub ztank
}}}
However suddenly I noticed in an adhoc check of zpool status that ALL my pools
were scrubbed on Sunday January 12th 2020!
{{{
# zpool status | grep -i "scrub"
scan: scrub repaired 0B in 0h13m with 0 errors on Sun Jan 12 00:37:31 2020
scan: scrub repaired 0B in 11h24m with 0 errors on Tue Jan 14 12:24:33 2020
<-- (one of my own since the Jan12 mega scrub)
scan: scrub repaired 0B in 0h45m with 0 errors on Sun Jan 12 01:09:40 2020
scan: scrub repaired 0B in 7h10m with 0 errors on Sun Jan 12 07:34:11 2020
}}}
this is NOT what I had configured, so I went digging and found that zfsutil
cron file :(
{{{
# cat /usr/lib/zfs-linux/scrub
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] &&
/usr/lib/zfs-linux/scrub
}}}
This MAY be a desirable default for some system admins, but having it
suddenly appear IMO is at the same time undesirable for many.
==Describe how to reproduce the problem==
* Having been a ZoL user sys admin for many years.
* Be a decent sys admin and know the basics, you've configured your own
cron/schedule for pool scrubbing per guidelines and individual needs.
* Follow stable upgrade channels. (for me this is Ubuntu LTS 16.04, then 18.04)
* Suddenly after some upgrade version XX(?) your pools start scrubbing on the
2nd Sunday of every month without your having configured it or asked for that.
==Expectations==
Hoping we can:
1. Confirm when and why this was rolled out to all systems by default (does
the explanation make sense? is it really OK to do this? how was it
communicated?)
2. Ensure "how to disable" is documented and supported (i.e. if I just delete
that cron file, will some future upgrade replace and re-enable it?)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.7
ProcVersionSignature: Ubuntu 4.15.0-73.82-generic 4.15.18
Uname: Linux 4.15.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
Date: Sat Jan 18 13:41:29 2020
InstallationDate: Installed on 2015-06-28 (1664 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to bionic on 2019-05-10 (253 days ago)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission
denied: '/etc/sudoers.d/zfs']
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Description changed:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
+ ```
System information
Type Version/Name
Distribution Name Ubuntu
Distribution Version 18.04.3 LTS
Linux Kernel 4.15.0-73-generic
Architecture x86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
+ ```
When did this file get added into zfsonlinux ecosystem?
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the
month to avoid
[Bug 1848387] Re: dpkg error when triggers are activated
This is resolved in appstream >= 0.12.10-1 ** Changed in: appstream (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/1848387 Title: dpkg error when triggers are activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1848387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
