[Bug 1849787] Re: The dock is shown in front of full screen windows since 19.10
my primary box; 20.04 (5.3.0-19) dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) xscreensaver (glmatrix) was active (two displays) however the Ubuntu DOCK was fully visible on my primary display. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849787 Title: The dock is shown in front of full screen windows since 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854601] Re: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD
Thanks for your suggestion. ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Medium ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Triaged ** Also affects: ubiquity (Ubuntu Focal) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854601 Title: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853864] Re: zfs installation fails on nvme devices
This is fixed in ubiquity 20.04.2 ** Changed in: ubiquity (Ubuntu) Status: Fix Committed => 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/1853864 Title: zfs installation fails on nvme devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1853864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
This bug was fixed in the package fftw3 - 3.3.8-2ubuntu1 --- fftw3 (3.3.8-2ubuntu1) focal; urgency=medium * debian/rules: Disable Neon for armhf single precision builds to avoid crashes. It's unclear if this is an fftw3 internal bug in its code generator (which fftw3 does by hand) or related to gcc changes in recent years. But certainly disabling Neon avoids the crashes. (LP: #1843733) -- Daniel van Vugt Sat, 30 Nov 2019 23:40:05 +0100 ** Changed in: fftw3 (Ubuntu) Status: In Progress => 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/1843733 Title: fftw3 ftbfs in eoan (armhf only) To manage notifications about this bug go to: https://bugs.launchpad.net/fftw3/+bug/1843733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
Please attach both /etc/cups/ppd/Brother_HL_L2375DW_series.ppd and /etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854610] [NEW] No Japanese input possible after upgrade from 19.04 to 19.10
Public bug reported: Description: After upgrading to xubuntu 19.10 my Japanese input did not work anymore. Regarding to this [https://askubuntu.com/questions/1182781/chinese- input-methods-not-working-in-ubuntu-mate-19-10] website, there seems to be the same problem with chinese input. Workaround: === install ibus-gtk and ibus-gtk3. `apt-cache show ibus-anthy` shows the following dependencies: === Depends: anthy (>= 1:0.3-6), ibus (>= 1.5), dconf-gsettings-backend | gsettings-backend, python3:any, libanthy1, libc6 (>= 2.4), libglib2.0-0 (>= 2.37.3) As ibus-gtk and ibus-gtk3 are not listed, I guess a/the solution would be to add those to the dependency list. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus-anthy 1.5.10-2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 1 16:15:58 2019 SourcePackage: ibus-anthy UpgradeStatus: Upgraded to eoan on 2019-12-01 (0 days ago) ** Affects: ibus-anthy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854610 Title: No Japanese input possible after upgrade from 19.04 to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-anthy/+bug/1854610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
** Attachment added: "attrs.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309039/+files/attrs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
I have the same problem with a Brother HL L2375-DW printer on Ubuntu 19.10. This was auto-detected and added to the GNOME Printers as 'Brother_HL_L2375DW_series' - if I print double sided (long-edge) using the then it prints the second page upside down (as though I had selected short-edge) - but selecting short-edge also prints as short-edge. However, I then went into 'Printer Details' via the gear menu for the printer, and selected 'Select from Database...' and chose the 'Brother HL-L2375DW series, driverless, cups-filters 1.25' driver. At this stage a second instance of the printer appeared in GNOME Printers ('Brother_HL_L2375DW_series@BRW0C96E67E441E.local') - and printing to this second instance seems to work correctly. I am unsure how to know which PPD was used for the first auto-detected + added instance but if you can help me to find out I will happily attach the PPD here. See below for error_log, attrs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309038/+files/error_log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
Let me know which of these PPDs to attach: $ ls -la /etc/cups/ppd/Brother_HL_L2375DW_series* -rw-r--r-- 1 root root 8499 Dec 1 17:14 /etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd -rw-r- 1 root lp 8424 Dec 1 17:13 /etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd.O -rw-r- 1 root lp 8615 Dec 1 17:13 /etc/cups/ppd/Brother_HL_L2375DW_series.ppd -rw-r--r-- 1 root root 8487 Dec 1 16:32 /etc/cups/ppd/Brother_HL_L2375DW_series.ppd.O ** Changed in: cups (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel
Power cycling does not appear to trigger the bug, as well as attempting to recreate the original circumstances (turning off wireless through system tray + shutdown). Specs: Dell Inspiron 17 3000 (Reg Model P35E) Ubuntu 18.04.1, kernel 5.0.0-36-generic Qualcomm Atheros QCA9377 wireless adapter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724317 Title: Shutdown hangs / no standby - possible Wifi-bug in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel
Bug also possibly found on 18.04, kernel 5.0.0-36-generic; will need confirmation. (First occurrence) ** Attachment added: "20191201_012839.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+attachment/5309037/+files/20191201_012839.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724317 Title: Shutdown hangs / no standby - possible Wifi-bug in the kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800043] Re: nautilus cannot write on nfs file share base dir
** Changed in: nautilus Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800043 Title: nautilus cannot write on nfs file share base dir To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1800043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854559] Re: install of Lubuntu 20.04 fails on "sfdisk /dev/sda"
*** This bug is a duplicate of bug 1851188 *** https://bugs.launchpad.net/bugs/1851188 ** This bug has been marked a duplicate of bug 1851188 Failed to create a partition table - install failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854559 Title: install of Lubuntu 20.04 fails on "sfdisk /dev/sda" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1854559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk
** Also affects: valgrind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942614 Importance: Unknown Status: Unknown ** Changed in: valgrind Status: Confirmed => Unknown ** Changed in: valgrind Remote watch: Debian Bug tracker #942614 => KDE Bug Tracking System #396656 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To manage notifications about this bug go to: https://bugs.launchpad.net/valgrind/+bug/1848211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854563] Re: Sync materia-gtk-theme 20190315-1 (universe) from Debian unstable (main)
** Changed in: materia-gtk-theme (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854563 Title: Sync materia-gtk-theme 20190315-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/materia-gtk-theme/+bug/1854563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822134] Re: Ubuntu Studio Installation - Black Text on Dark Gray
** No longer affects: ubiquity (Ubuntu) ** No longer affects: ubiquity-slideshow-ubuntu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822134 Title: Ubuntu Studio Installation - Black Text on Dark Gray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1822134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854608] [NEW] Screen Flickering during Boot up
Public bug reported: The Screen flickers during boot up and System runs very slow. This is my GPU info. 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 1 11:07:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-32-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3977] InstallationDate: Installed on 2019-05-22 (192 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20157 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic root=UUID=fb1d2555-5fe7-4a82-804c-8b91c22c2a1f ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN34WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr62CN34WW:bd04/26/2012:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 20157 dmi.product.sku: System SKUNumber dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854608 Title: Screen Flickering during Boot up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on
I don't think Compiz is relevant here. My computer isn't running Compiz — its display manager is GDM3 as best I can tell. (ri...@richw.org, the original reporter of this bug) ** Package changed: compiz (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854589 Title: Windows move to different monitor when multiple monitors turned off and back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1854589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox
The following workaround doesn't remove anything and allows the wrapper to survive updates: sudo -i printf '#!/bin/sh\n\n/usr/share/gdebi/gdebi-gtk "$@"\n' > /usr/local/bin/gdebi-gtk chmod +x /usr/local/bin/gdebi-gtk exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1845466] Re: UEFI/Secureboot - "Failed to start MokManager" error when trying to install 3rd party drivers during install, leading to unbootable device
Hi, Pierre, Thank you so much for your detailed response. I ended up solving my problem by installing Ubuntu 18.04.03 without including 3rd Party add-ons. I added what I needed manually after the installation. I wanted to go with 18.04.03 because I wanted a distro with LTS. I am glad I found a resolution because I spent about 6 hours working on this problem and was convinced that it was a BIOS issue, not a problem with Ubuntu. Thanks, Luke On Thu, Nov 28, 2019 at 8:20 PM Pierre Equoy wrote: > Hi Luke, > > First of all: don't worry, your device is not bricked. MOK (Machine- > Owner Keys) is a mechanism that allows the user of a system to add > his/her own secure keys in addition to the ones the machine already has. > It is used by Ubuntu because Ubuntu may include additional stuff (the > "3rd party drivers") that are not signed by the default security keys. > Therefore, it is required to add other security keys to be able to > install and enable these 3rd party drivers. > > Did you try the latest version (Ubuntu 19.10)? Or only different 18.04 > ISOs? > > Mathieu Trudel-Lapierre provided a fix (see comment #4) for grub2 > (included in 2.04-1ubuntu6). According to the packages list [1], the > version in 18.04 (bionic) is 2.02-2ubuntu8, so I don't think it includes > the fix. > > [1] https://packages.ubuntu.com/bionic/grub2 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1845466 > > Title: > UEFI/Secureboot - "Failed to start MokManager" error when trying to > install 3rd party drivers during install, leading to unbootable device > > Status in grub2 package in Ubuntu: > Fix Released > Status in grub2 source package in Eoan: > Fix Released > > Bug description: > Image: > http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso > Device: Dell XPS 13 7390 (201908-27305) > > Note: > - TPM2 is disabled (because of lp:1845454) > - Secure Boot is enabled > > Install Ubuntu 19.10. > Check the box "Install third party drivers". You'll have to input a > password used by Secure Boot at the next reboot. > Complete the installation and restart the device. > > Expected result: > The device reboots in the MOK Management screen where you can enroll the > new MOK. Then the boot process continues and you can log in Ubuntu. > > Actual result: > The following error is shown for a few seconds, then the device turns > off: > > Failed to open \EFI\ubuntu\mmx64.efi - Not Found > Failed to load image \EFI\ubuntu\mmx64.efi: Not Found > Failed to start MokManager: Not Found > Something has gone seriously wrong: import_mok_state() failed: Not Found > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845466/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845466 Title: UEFI/Secureboot - "Failed to start MokManager" error when trying to install 3rd party drivers during install, leading to unbootable device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854606] Re: Always reset HDMI out but I need line out
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1854606/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854606 Title: Always reset HDMI out but I need line out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1854606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382898] Re: gthumb freezes on startup in utopic
[Expired for gthumb (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gthumb (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382898 Title: gthumb freezes on startup in utopic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1382898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846153] Re: gpg generate-key fails
[Expired for gnupg2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnupg2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846153 Title: gpg generate-key fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1846153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845741] Re: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer.
[Expired for pam (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pam (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845741 Title: package libpam-runtime 1.1.8-3.6ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1845741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846155] Re: gpg --generate-key --batch prompt with SIGINT breaks shell
[Expired for gnupg2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnupg2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846155 Title: gpg --generate-key --batch prompt with SIGINT breaks shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1846155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854092] Re: pbcopy & pbpaste for Linux
Modified version of previous demo. Clipbard is cleaned in different way.. The same result, xsel version doesn't work ``` # MAIN pbcopy https://bugs.launchpad.net/bugs/1854092 Title: pbcopy & pbpaste for Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsel/+bug/1854092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754833] Re: Chromium complains that it's not the default browser when it is the default according to Gnome Settings
Has this issue been fixed yet? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754833 Title: Chromium complains that it's not the default browser when it is the default according to Gnome Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1754833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854604] [NEW] [Budgie 20.04] Using “ibus-mozc”, two “keyboard” icons may appear in the system tray.
Public bug reported: Ubuntu Budgie 20.04 Daily (Japanese environment) ## Using “ibus-mozc”, two “keyboard” icons may appear in the system tray. This is because an afterimage of the “keyboard” icon remains in the system tray. (It appears that the background of the icon is not cleared with the panel color before the icon is displayed.) --- usage environment: Ubuntu Budgie 20.04 Daily (Japanese environment) $ cat /var/log/installer/media-info Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20191125) $ uname -r 5.3.0-18-generic $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)" --- Input method: ibus-mozc (ibus-mozc/focal,now 2.23.2815.102+dfsg-7 amd64) ibus (ibus/focal,now 1.5.21-1~exp2ubuntu3 amd64) Applet: System tray --- Setting: $ im-config -> I selected “ibus”. $ ibus-setup -> Check "システムトレイにアイコンを表示する (Display icon in system tray)". --- Specifications of the machine used: Boot Mode: BIOS Processor Architecture in use: 64-bit Components Memory(RAM): 8.3 GB(7.7 GiB) Graphics: Intel Coporetion Haswell-ULT Integrated Graphics Controller(rev 09) --- ### Problem phenomenon: --- 1: Symptoms occur where the "keyboard" icon was originally located. At login, When the “Network Connection” icon appears in the system tray, the “Keyboard” icon moves to the left. There is an afterimage at the original position, and the “Network Connection” icon and the image overlap, but the “Network Connection” icon is not noticeable. So it looks like there are two “keyboard” icons. -> Attached image file - "When connected to network" Incorrect display: NG-2.jpeg Correct display: OK-2.jpeg --- 2: The same phenomenon occurs where the “keyboard” icon has moved. The “keyboard” icon usually changes depending on the keyboard input status. - "Keyboard image": (initial display) -> OK-1.jpeg - Orange "あ": (Mozc starting) -> OK-3.jpeg - Blue "A": (Japanese off) -> OK-4.jpeg - Blue "あ": (Japanese on) -> OK-5.jpeg Since all images corresponding to the transparency of the panel overlap and the image is filled, it is not useful as a Japanese on / off display. By the way, the afterimage of the orange “あ” stands out. --- By the way, the "keyboard" icon is not displayed by default. -> Attached image file: KB-icon-off.jpeg Japanese is a language that includes both kanji and alphanumeric characters. By default, the input mode changes each time you press the “Hankaku/Zenkaku” key. There are two input modes: “Japanese on” (Kanji / Hiragana / Katakana) and “Japanese off” (alphabet). It is set to display the “keyboard” icon to check the change of the keyboard status. -> Attached image file : OK-4.jpeg - Blue "A": (Japanese off) OK-5.jpeg - Blue "あ": (Japanese on) Therefore, it is difficult to input Japanese if the “keyboard” icon is not displayed correctly. -> Attached image file: NG-5.jpeg Perhaps those who use English will not notice this bug. However, it is very important for Japanese people. --- Workaround: 1. Log out -> Log in It may or may not return to normal. 2. By separating the input mode on and off into separate keys, you can enter without looking at the indicators. Personally, I assigned the input mode “Japanese on” to the “Hiragana” key and “Japanese off” to the “Muhenkan” key. I edited the “Custom” created in “Key Settings” in “Mozc Settings” (mozc_tool). It's not difficult, but it requires a little skill. --- Attached image file (KB-icon.tar.gz) KB-icon-off.jpeg - (Display icon in system tray) KB-icon-on.jpeg - (Display icon in system tray) NG-1.jpeg - "Keyboard image": (initial display) NG-2.jpeg - “Network Connection” NG-3.jpeg - Orange "あ": (Mozc starting) NG-4.jpeg - Blue "A": (Japanese off) NG-4-1.jpeg (Changed the background to make it easier to understand.) NG-4-2.jpeg (Changed the background to make it easier to understand.) NG-4-3.jpeg (Changed the background to make it easier to understand.) NG-5.jpeg - Blue "あ": (Japanese on) - The image is mixed OK-1.jpeg - "Keyboard image": (initial display) OK-2.jpeg - “Network Connection” OK-3.jpeg - Orange "あ": (Mozc starting) OK-4.jpeg - Blue "A": (Japanese off) OK-5.jpeg - Blue "あ": (Japanese on) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus-mozc 2.23.2815.102+dfsg-7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Dec 1 12:09:36 2019 ExecutablePath: /usr/lib/ibus-mozc/ibus-engine-mozc InstallationDate: Installed on 2019-11-27 (3 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20191125) ProcEnviron: LANGUAGE=ja_JP PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: mozc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mozc (Ubuntu)
[Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
On an Acer Aspire 5810TG running Ubuntu 18.04 with latest 5.3 kernel. HDA Intel. ALC269 Analog. Pulseaudio was monitoring minimal sound from internal mic with both channels on, but ok with either left or right off. Audacity and Gnome Sound Recorder had no issues. Audacity showed two phase inverted channels. Same issues as above re Skype and Hangouts and same workarounds worked. External mono plug in mic - no problem. Same problem on same machine with Debian 10 Buster. Tried remapping the Pulseaudio stereo channels to mono which allowed even output through both speakers. For instructions see: https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting #No_microphone_on_Steam_or_Skype_with_enable-remixing_=_no After this, Pulseaudio still has to have one internal mic channel off to function. However output is now through both speakers instead of one. In Ubuntu, Audacity shows two channels with same phase. In Debian, Audacity shows one mono channel. Same difference through the speakers. I believe this is still a bug as Pulseaudio cannot produce output from with a phase inverted stereo internal mic as Audacity and Sound recorder can. Best regards, Your bleeding user -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764172] Re: Unable to change hostname
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hostname (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/1764172 Title: Unable to change hostname from the one specified during Bionic server installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1764172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764172] Re: Unable to change hostname specified during Bionic server installation
** Summary changed: - Unable to change hostname + Unable to change hostname specified during Bionic server installation ** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Unable to change hostname specified during Bionic server installation + Unable to change hostname from the one specified during Bionic server installation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764172 Title: Unable to change hostname from the one specified during Bionic server installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1764172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854603] [NEW] Greek (polytonic) keyboard layout not handling some accent marks
Public bug reported: I’m running Ubuntu 20.04 (GNOME shell desktop: gnome-shell 3.34.1+git20191024-1ubuntu1) in a QEMU/KVM vm. I’m using a US keyboard which is set up to switch between English and polytonic Greek. This has been working satisfactorily in 18.04. However, in 20.04, I’m noticing that I can’t add the breathing marks or diaeresis to lower-case letters in polytonic Greek. When I try to type the marks, they appear on the screen but disappear immediately once I release the shift key. I can add breathing marks and diaeresis to capital letters. So far, I've seen this behaviour in LibreOffice, gedit and Firefox. ** Affects: gnome-shell (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/1854603 Title: Greek (polytonic) keyboard layout not handling some accent marks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 About the problem of "there is no /dev/mmcblk0* device", I checked your dmesg, there are two places are weird the 1st one is about the raspberrypi-firmware, on my board, the dmesg will show: [0.100540] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-08-15 12:03, variant start [0.110122] raspberrypi-firmware soc:firmware: Firmware hash is 9f8431fb7839c7f00f52b81f5822ddab2b31d0db And there are not errors about firmware, but your dmesg is different. the 2nd one is about mmc-bcm2835 driver, your kernel always report: mmc-bcm2835 fe30.mmcnr: could not get clk, deferring probe That is different from my board, on my board, it only reports that message once, Then the driver could get the clk successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854601] Re: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD
** Changed in: ubiquity (Ubuntu) Status: New => Confirmed ** Tags added: ubuntu ** Description changed: When booting from an iso all Ubuntu and flavours have the option to Install or "You can try without making any changes to your computer, directly from this CD" This should be changed to something other than "directly from this CD" I would recommend something like "directly from this iso" since many users - no will no longer try or install from a CD or DVD. + will no longer try or install from a CD or DVD. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.1 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-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: MATE Date: Sun Dec 1 01:11:27 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) ProcEnviron: - LANGUAGE=en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854601 Title: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
@tsger: You did not mention if you are booting in BIOS or UEFI mode. I have only had problem when using both UEFI and Grub 2.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
Launchpad has imported 1 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=25237. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-11-30T23:38:36+00:00 Balint Reczey wrote: Created attachment 12095 Patch adjusting offset to stay in the file This itself was tolerated for long time, but WSL's ELF loader crashes due to the offset and it seems to be easy to fix. Reply at: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/comments/7 ** Changed in: binutils Status: Unknown => New ** Changed in: binutils Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854601] Re: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD
This affects me, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854601 Title: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854601] Re: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD
** Attachment added: "VirtualBox_UM-20.04_30_11_2019_18_24_29.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+attachment/5309012/+files/VirtualBox_UM-20.04_30_11_2019_18_24_29.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854601 Title: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854601] [NEW] Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD
Public bug reported: When booting from an iso all Ubuntu and flavours have the option to Install or "You can try without making any changes to your computer, directly from this CD" This should be changed to something other than "directly from this CD" I would recommend something like "directly from this iso" since many users no will no longer try or install from a CD or DVD. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.1 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-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: MATE Date: Sun Dec 1 01:11:27 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.1 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854601 Title: Ubiquity installation says "You can try Ubuntu without making any changes to your computer directly from this CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90085] Re: When /tmp is mounted noexec, preconfigure fails
@jblainemitre indeed - but presumably one can pick any directory? I'm assuming there's no particular requirement that the selected dir is world-writeable like /tmp and /var/tmp (or at least there doesn't seem to be in my setup?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/90085 Title: When /tmp is mounted noexec, preconfigure fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854599] Re: package mariadb-server-core-10.3 1:10.3.17+maria~cosmic failed to install/upgrade: trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10
** 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/1854599 Title: package mariadb-server-core-10.3 1:10.3.17+maria~cosmic failed to install/upgrade: trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10.3.17+maria~cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1854599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854599] [NEW] package mariadb-server-core-10.3 1:10.3.17+maria~cosmic failed to install/upgrade: trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:
Public bug reported: During update received error message regarding versioning ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mariadb-server-core-10.3 1:10.3.17+maria~cosmic ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: mariadb-server-core-10.3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Nov 30 06:34:17 2019 DpkgTerminalLog: Preparing to unpack .../mariadb-server-core-10.3_1%3a10.3.20-0ubuntu0.19.10.1_amd64.deb ... Unpacking mariadb-server-core-10.3 (1:10.3.20-0ubuntu0.19.10.1) over (1:10.3.17+maria~cosmic) ... dpkg: error processing archive /var/cache/apt/archives/mariadb-server-core-10.3_1%3a10.3.20-0ubuntu0.19.10.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10.3.17+maria~cosmic DuplicateSignature: package:mariadb-server-core-10.3:1:10.3.17+maria~cosmic Unpacking mariadb-server-core-10.3 (1:10.3.20-0ubuntu0.19.10.1) over (1:10.3.17+maria~cosmic) ... dpkg: error processing archive /var/cache/apt/archives/mariadb-server-core-10.3_1%3a10.3.20-0ubuntu0.19.10.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10.3.17+maria~cosmic ErrorMessage: trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10.3.17+maria~cosmic InstallationDate: Installed on 2019-05-04 (210 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: mariadb-10.3 Title: package mariadb-server-core-10.3 1:10.3.17+maria~cosmic failed to install/upgrade: trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10.3.17+maria~cosmic UpgradeStatus: Upgraded to eoan on 2019-10-25 (36 days ago) ** Affects: mariadb-10.3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan package-conflict third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854599 Title: package mariadb-server-core-10.3 1:10.3.17+maria~cosmic failed to install/upgrade: trying to overwrite '/usr/bin/my_print_defaults', which is also in package mariadb-server-10.3 1:10.3.17+maria~cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1854599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854595] Re: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: openssl (Ubuntu) Importance: Undecided => Low ** Changed in: openssl (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/1854595 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464064] Re: Ubuntu apt repos are not available via HTTPS
The only solution ATM is to check https://www.reddit.com/r/Ubuntu/comments/3q53kc/list_of_ubuntu_repository_mirrors_available_over/ an chose a nearby mirror. Then compare http://security.ubuntu.com/ubuntu/dists/bionic- security/InRelease and your mirror, e.g. https://ftp.fau.de/ubuntu/dists /bionic-security/InRelease (mirror of the FAU (university) located in Germany) and make sure "Date:" in the top section of the InRelease file is equivalent (not more off than 6 to 12 hrs) between the two files. Then adjust your /etc/apt/sources.list e.g. like this: ## Main repository for Ubuntu distributions. This line was auto-added in ## 2018 to provide a fallback, in case no network mirror is available. # deb cdrom:[Xubuntu 18.04.1 LTS _Bionic Beaver_ - Release amd64 (20180725)]/ bionic main restricted # deb cdrom:[Xubuntu 18.04.1 LTS _Bionic Beaver_ - Release amd64 (20180725)]/ bionic universe # deb cdrom:[Xubuntu 18.04.1 LTS _Bionic Beaver_ - Release amd64 (20180725)]/ bionic multiverse ## See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to ## newer versions of the distribution. ## Major bug fix updates are produced after the final release of the ## distribution. deb https://ftp.fau.de/ubuntu/ bionic main restricted deb-src https://ftp.fau.de/ubuntu/ bionic main restricted deb https://ftp.fau.de/ubuntu/ bionic-updates main restricted deb-src https://ftp.fau.de/ubuntu/ bionic-updates main restricted deb https://ftp.fau.de/ubuntu/ bionic-security main restricted deb-src https://ftp.fau.de/ubuntu/ bionic-security main restricted ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb https://ftp.fau.de/ubuntu/ bionic-backports main restricted deb https://ftp.fau.de/ubuntu/ bionic-backports universe multiverse ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb https://ftp.fau.de/ubuntu/ bionic universe deb-src https://ftp.fau.de/ubuntu/ bionic universe deb https://ftp.fau.de/ubuntu/ bionic-updates universe deb-src https://ftp.fau.de/ubuntu/ bionic-updates universe deb https://ftp.fau.de/ubuntu/ bionic-security universe deb-src https://ftp.fau.de/ubuntu/ bionic-security universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb https://ftp.fau.de/ubuntu/ bionic multiverse deb-src https://ftp.fau.de/ubuntu/ bionic multiverse deb https://ftp.fau.de/ubuntu/ bionic-updates multiverse deb-src https://ftp.fau.de/ubuntu/ bionic-updates multiverse deb https://ftp.fau.de/ubuntu/ bionic-security multiverse deb-src https://ftp.fau.de/ubuntu/ bionic-security multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. ## It includes Adobe Flash, Google SDK and IBM Java. #deb http://archive.canonical.com/ubuntu bionic partner #deb-src http://archive.canonical.com/ubuntu bionic partner Then run: sudo apt-get check sudo apt-get update sudo apt-get upgrade sudo apt-get clean sudo apt-get autoclean sudo apt-get autoremove sudo dpkg --purge `dpkg --get-selections | grep deinstall | cut -f1` sudo apt-get check Make sure `sudo lsof /var/lib/apt/lists/lock` does not output something besides a warning of /run/user/1000/gvfs. If so terminate the offender if possible and/or run `sudo dpkg --configure -a`. That's it. All your APT updates will now run TLS-secured (HTTPS), -except- for your Launchpad PPA updates, located in /etc/apt/sources.list.d/. AFAIK their links cannot be transformed from HTTP to HTTPS yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464064 Title: Ubuntu apt repos are not available via HTTPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1464064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Bug watch added: Sourceware.org Bugzilla #25237 https://sourceware.org/bugzilla/show_bug.cgi?id=25237 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=25237 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
So I took over the screen and see that there is a user prompt to upgrade. I chose the regular updates which included an update for the unattended upgrade package. I'll try to cancel and restart the Landscape process with the new unattended-upgrade package. ii unattended-upgrades1.10ubuntu5.2 all automatic installation of security upgrades ** Attachment added: "Not very unattended" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5308999/+files/2019-12-01NotVeryUnattendedUpgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853056] Re: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress
Now 14 days into the upgrade. There has been no timeout of the process and it's still chugging along doing absolutely nothing at all. (see screenshot) ** Attachment added: "14 days in still no upgrade or timeout" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+attachment/5308998/+files/2019-12-01Landscape14daysStuckUpgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853056 Title: LANDSCAPE: Upgrade from disco to eoan running for 24 hours with no progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1853056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854596] Re: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10
** 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/1854596 Title: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1854596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854596] [NEW] package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10
Public bug reported: Update: operation failed ProblemType: Package DistroRelease: Ubuntu 19.10 Package: grub-pc 2.04-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sat Nov 30 22:46:24 2019 DuplicateSignature: package:grub-pc:2.04-1ubuntu12.1 Setting up grub-pc (2.04-1ubuntu12.1) ... dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 10 ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-08-26 (96 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0cdad0b6-4faa-498b-a792-205c4a693309 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: grub2 Title: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854596 Title: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1854596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854595] Re: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 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/1854595 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854595] [NEW] package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: I was doing a partial upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Nov 30 19:02:39 2019 ErrorMessage: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-06-13 (1631 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: openssl Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854595 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
There is only one PLL (Phase Locked Loop) in the processor, all CPUs get the resulting clock. When they go into deep idle states (deeper than C1, at least for my processor) then they give up their vote into the PLL as to what the frequency should be. Your single 100% task is dedicating the CPU frequency for all, for when they are active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
I'm using Ubuntu 18.04 since it came out, but are effected by this bug only since two weeks. What I noticed: I have a couple of programs setup to start automatically (via gnome-session-properties). When I log in and get kicked out because of this bug, those programs where never started at all. On a normal Login they start fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940030] Re: rsyslog stops working after logrotate until restarted
Has been hit by this bug on two of my servers apparently (both 18.04.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940030 Title: rsyslog stops working after logrotate until restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/940030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774711] Re: excessive seccomp audit logs
Will the required pat set be backported to older kernel, such as Ubuntu 4.15.0-70.79-generic 4.15.18? Will the patches be in 20.04 LTS (kernel >= 4.18), which is around the corner? NOTE: Unfortunately with issue #1774711 the use of "auditd" has become problematic on systems with SSDs, since systemd allows in-memory configuration (Storage=volatile; SplitMode=none), but auditd does not support such a complex configuration (write_logs = no; log_file = /var/log/audit/audit.log). That means with the excessive SECCOMP lines (i.e. tens/hundreds of thousands a day) we cannot re-enable auditd (sudo systemctl start|enable auditd.service) until this issue is resolved, UNLESS there is a way to make auditd not to write logs to disk but continue to function properly. We need auditd for enforcing audit.rules (complex ISO 27001, PCI-DSS, etc. compliant rulesets) and statistics (sudo aureport (-n)), which require log data stored (dmesg kernel bugger is insufficient for ISO compliant store and analysis of events and stats). Our tests show, that up to several hundred MiB of logs are written to the SSDs per pay, which accumulates to approx 0.5 TiB over the course of 4 years. With in avg. 50% of the SSD cells occupied and given the models, this translates to a slightly increased wear-out of our SSDs, even when a good wear-leveling algorithm and background garbage collector is in use (our desktop models: Samsung Enterprise SSD with super capacitor mod. SM/PM863(a)). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774711 Title: excessive seccomp audit logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713238] Re: gufw will not open in ubuntu wayland 17.10
Hmm, do you have the same issue on latest Ubuntu 19.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713238 Title: gufw will not open in ubuntu wayland 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1713238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
Any chance this could be improved? It is really frustrating that we have to manually translate this string every time before a new Ubuntu release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562219] Re: Unprivileged xinit wont start in unallocated vt
Does install the suid-root wrapper allow for any user to run an X server? This seems a little too open if so, as it seems better to allow only either root, or the user logged into the console to run the server, IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562219 Title: Unprivileged xinit wont start in unallocated vt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
@Doug Smythies: thanks for the reply. I'm sampling every second. Anyway, just to better understand. When my system is idle all cores spend in C0 less than 10% of the time and the frequency of each core reported by i7z is different and below 2.2GHz. When I run a single core (and single thread) task, there is just core "0" which is 100% of the time in C0 state (as it should) but I would have expected only such core to reach ~2.9GHz and the other to remain in below. Instead all cores goes to ~2.9GHz. https://www.youtube.com/watch?v=HBKfkiOgIv4 (sorry for the oversimplified reference) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847341] Re: plymouth-theme-spinner doesn't show Acer logo on boot but an older version of regular Ubuntu boot screen
So the iwlwifi bug is a different bug and is fixed now. However i have turned off my NVidia card and the issue with plymouth still stays. I purged and reinstalled the plymouth theme spinner theme, but issue still stays even with Intel turned on. ** Attachment added: "2019-11-30_23-14.png" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1847341/+attachment/5308980/+files/2019-11-30_23-14.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847341 Title: plymouth-theme-spinner doesn't show Acer logo on boot but an older version of regular Ubuntu boot screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1847341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (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/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Just ran into this issue on a fresh install of 19.10 with all updates installed as of 2019/11/30. The lock icon in the menu is missing and the keyboard shortcut is non-functional. The Screen Lock dialog in settings is greyed out entirely. chris-18's fix from earlier worked. Setting org/gnome/desktop/lockdown/disable-lock-screen to disabled: enabled the icon, the keyboard shortcut, and the Screen Lock dialog in settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Hello TJ, your gvfs-package build on https://launchpad.net/~tj/+archive/ubuntu/bugfixes seems to have resolved the problem for me! Therefore, a 1000 thanks! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854592] 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/1854592 Title: kern.log flooded by ACPI error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854592] [NEW] kern.log flooded by ACPI error messages
Public bug reported: I use Ubuntu 19.10 AMD64 (completely up to date) on a Lenovo Thinkpad S1 Yoga 12, and I've just noticed that /var/log/kern.log is flooded by messages like : Nov 30 21:12:44 yoga kernel: [ 526.471259] ACPI: \_SB.PCI0.LPCB.EC0.ECRD: 1 arguments were passed to a non-method ACPI object (RegionField) (20190703/nsarguments-204) Every about two seconds, 18 messages of this kind are recorded. What could I do to provide more informations ? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tley 1650 F pulseaudio /dev/snd/controlC1: tley 1650 F pulseaudio /dev/snd/pcmC1D0p: tley 1650 F...m pulseaudio Date: Sat Nov 30 21:18:09 2019 InstallationDate: Installed on 2019-11-17 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20DKS1MA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=6662e662-b3da-478c-bf6b-ea7d12495e6e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JEET69WW (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DKS1MA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJEET69WW(1.18):bd07/24/2015:svnLENOVO:pn20DKS1MA00:pvrThinkPadS1Yoga12:rvnLENOVO:rn20DKS1MA00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S1 Yoga 12 dmi.product.name: 20DKS1MA00 dmi.product.sku: LENOVO_MT_20DK_BU_Think_FM_ThinkPad S1 Yoga 12 dmi.product.version: ThinkPad S1 Yoga 12 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854592 Title: kern.log flooded by ACPI error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854591] [NEW] Boot screen not displaying correctly
Public bug reported: A blank pink screen with 1" black borders appears after the grub boot menu. After 27 seconds, it switches to a black screen. On that black screen, in the upper left quadrant, Ubuntu 19.10 is displayed as text with animated dots underneath. After a few more seconds, a purple screen appears for a couple of seconds and then the desktop is displayed. When I shutdown or restart ubuntu, the graphical shutdown screen works correctly. ** Affects: plymouth (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/1854591 Title: Boot screen not displaying correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1854591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854589] Re: Windows move to different monitor when multiple monitors turned off and back on
I note this bug has been classified as affecting Compiz. However, as best I can tell, Compiz is not running on my computer. /etc/X11 /default-display-manager on my computer contains the value "/usr/sbin/gdm3". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854589 Title: Windows move to different monitor when multiple monitors turned off and back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1854589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
@Davide Sangalli: What you describe and show in your comment #80 is correct and exactly what should happen. Your processor is spending an extraordinary amount of time in C1 as opposed to deeper idle states. At what sampling frequency do you run i7z? I would suggest once every 15 seconds or so, so that you don't wake up CPUs just to ask them status stuff. Everyone with this problem: If you don't bisect the kernel to isolate the offending commit, as has been asked for a couple of times now, then there will never be any progress for this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51554]
FYI, this reporter is gone - not responded to any bug reports. Perhaps this can be closed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/51554 Title: Unicode combining characters don't combine properly. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/51554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox
Goes back further than Ubuntu 18.04 then... https://stackoverflow.com/questions/49214954/gdebi-refusing-to-render- service-to-dead-parents ** Also affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Description changed: Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... - Basically on a fresh install of Ubuntu 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... + Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854469] Re: hwe-edge kernel 5.3.0-23.25 kernel does not poweroff
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-edge (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/1854469 Title: hwe-edge kernel 5.3.0-23.25 kernel does not poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1854469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854590] [NEW] No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal)
Public bug reported: I don't know much, so forgive me if I use the wrong terminology. Problem: There is no ComposeKey mapping for the symbols ≈ (Unicode 2248) and ≅ (Unicode 2248) in Compose Tables. Details: According to https://help.ubuntu.com/community/ComposeKey the files such as /usr/share/X11/locale/en_US.UTF-8/Compose have all ComposeKey combinations to type special symbols, characters and graphemes. Two standard graphemes (≈ and ≅) seem to be missing from multiple compose files although their negated versions (are present mapped to compositions Solution?!: I propose this (but wouldn't know how to commit it except by filing a bug - if it's straightforward to improve Linux, then please tell me how! I'd love to commit something to the code! I added these lines to a copy of the compose file that I made at ~/.Xcompose I propose that they should be added to the multiple, original Compose files in: /usr/share/X11/locale/en_US.UTF-8/Compose /usr/share/X11/locale/iso8859-1/Compose /usr/share/X11/locale/iso8859-15/Compose etc etc etc # _Added by Jackalux_ : "≅" U2245 # APPROXIMATELY OR ACTUALLY EQUAL TO : "≅" U2245 # APPROXIMATELY OR ACTUALLY EQUAL TO : "≈" U2248 # ALMOST EQUAL TO # End of Jackalux's additions Notes: The list at https://www.x.org/releases/X11R7.7/doc/libX11/i18n/compose/en_US.UTF-8.html also misses combinations for ≈ and ≅ . Perhaps that should be updated too if it is a reference list. I also wanted to add: : "≇" U2247 # NEITHER APPROXIMATELY NOR ACTUALLY EQUAL TO : "≇" U2247 # NEITHER APPROXIMATELY NOR ACTUALLY EQUAL TO : "≇" U2247 # NEITHER APPROXIMATELY NOR ACTUALLY EQUAL TO : "≇" U2247 # NEITHER APPROXIMATELY NOR ACTUALLY EQUAL TO : "≉" U2249 # NOT ALMOST EQUAL TO : "≉" U2249 # NOT ALMOST EQUAL TO But I've realised that they create clashes with other compositions, as the composition forms before the ComposeKey is released. If this can be corrected and added at the same time, then that would be amazing as I don't know how to access the actual compositions listed for those characters. Co-operatively, Jackalux ** Affects: update-manager (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/1854590 Title: No ComposeKey sequence for ≈ (almost equal) and ≅ (approximately equal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1854590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854589] [NEW] Windows move to different monitor when multiple monitors turned off and back on
Public bug reported: Ubuntu 19.10, gdm3 3.34.1-1ubuntu1, cinnamon 4.0.10-2, cinnamon- screensaver 4.0.3-1, nvidia-driver 435.21-0ubuntu2. I have a TV set connected to my computer as a second monitor (for displaying YouTube videos, etc.). When I turn off both my main monitor and the TV for the night, and turn them back on in the morning, I often find that the windows I had left open on the main monitor (email, browser, xterm, etc.) have moved from the main monitor to the TV and need to be moved back individually to the main monitor (via the "move to the other monitor" function on the taskbar icons). This doesn't always happen -- sometimes the windows show up on the main monitor where I left them the night before, and sometimes not. Maybe 50-50, one way or the other. The main monitor is configured (in the Display settings) as the primary monitor, and the taskbar panel remains on the main monitor -- and when I wake up the screen saver to unlock it, the password dialogue always shows up on the main monitor -- but the windows may end up on either device after I've unlocked. It doesn't appear to make any difference what order I turn the monitor and the TV off/on. In particular, I've conscientiously turned off the TV before locking the screen and turning off the monitor, and then turned on the monitor and unlocked the screen before turning the TV back on, but the windows frequently still end up on the TV instead of the main monitor. I would like to somehow flag the windows so that they will stay put on my main monitor when I turn things off at night and turn them back on in the morning -- or, even better, I would like the windows to remain associated with the same device and not move around on their own. ** Affects: compiz (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/1854589 Title: Windows move to different monitor when multiple monitors turned off and back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1854589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1845541] Re: OS becomes unresponsive when power is plugged in and battery is low
It is not possible to run top or even open a terminal when this occurs, and it is difficult to check right before as this requires predicting when it will occur On Mon, Sep 30, 2019 at 1:27 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please open a terminal and run 'top' in it to find out if any process is > hogging the CPU when this happens. > > Tip: DON'T run gnome-system-monitor because it uses too many resources > itself :) > > If no offending process is found then the next thing to check is for > over-aggressive power management: > 1. Make sure you don't have 'tlp' installed. > 2. Install and run 'powetop' as root to see if your machine is being > throttled to low frequency. > > ** Package changed: xorg-server (Ubuntu) => ubuntu > > ** Changed in: ubuntu >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1845541 > > Title: > OS becomes unresponsive when power is plugged in and battery is low > > Status in Ubuntu: > Incomplete > > Bug description: > Occasionally when I plug in my laptop at low (close to shut-down > levels, <10%) battery, the OS becomes unresponsive. The GUI doesn't > work, Ctrl+Alt+T doesn't work, nothing works. This makes it difficult > to collect information about the problem, since I basically have to > shutdown with the power button and reboot. It is probably related to > whichever processes monitor the battery and put the computer to sleep > when the battery gets low. Almost like it wants to put the computer to > sleep since the battery is at critical levels, but it just stalls > since the power is plugged in. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 > Uname: Linux 4.15.0-62-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Sep 26 11:41:31 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: >virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed >virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed > ExecutablePath: /usr/lib/xorg/Xorg > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) > (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] > [103c:81cb] > InstallationDate: Installed on 2019-01-28 (241 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 1bcf:2c83 Sunplus Innovation Technology Inc. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP HP ENVY Notebook > MonitorsUser.xml: > > > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/usr/bin/fish > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic > root=UUID=fcfb9abf-573d-4d5e-bc54-c8a65f678302 ro quiet splash vt.handoff=1 > SourcePackage: xorg-server > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/17/2016 > dmi.bios.vendor: Insyde > dmi.bios.version: F.22 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 81CB > dmi.board.vendor: HP > dmi.board.version: KBC Version 60.26 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.22:bd08/17/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CB:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV > dmi.product.name: HP ENVY Notebook > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > 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.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 > 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 > > To manage notifications about this bug go to: >
[Bug 1852072] Re: Conntrackd segfault when flushing tables
Hello, I also have this problem with conntrackd in ubuntu 18.04.3. Is there a known workaround while this is getting fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852072 Title: Conntrackd segfault when flushing tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/1852072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I also mention that, monitoring with i7z the clock of my CPU, when intel turbo is not working I get different freqs for each core Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % Temp VCore Core 1 [0]: 1126.19 (11.23x) 7.9993.9 1 1 40 0.6274 Core 2 [1]: 1239.87 (12.36x) 3.295.1 12.11 41 0.6208 Core 3 [2]: 1577.66 (15.73x) 3.795.4 1 1 38 0.6257 Core 4 [3]: 1316.89 (13.13x) 7.2381.9 112.8 39 0.6257 Core 5 [4]: 1572.58 (15.68x) 10.2 87 14.73 39 0.6257 Core 6 [5]: 1916.98 (19.11x) 8.0290.6 11.44 39 0.6266 However, as soon as I load 1 core to 100%, all goes at the maximum frequency (here I'm limiting the maximum and also the core is under-volted to keep the temperature stable. Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 % Temp VCore Core 1 [0]: 2891.95 (28.83x) 100 0 0 0 52 0.8234 Core 2 [1]: 2891.77 (28.83x) 2.4192.2 1 3.6 47 0.8229 Core 3 [2]: 2891.72 (28.83x) 1.7394.4 12.37 44 0.8225 Core 4 [3]: 2891.81 (28.83x) 191.5 16.46 44 0.8230 Core 5 [4]: 2892.39 (28.83x) 196.9 11.37 44 0.8242 Core 6 [5]: 2891.94 (28.83x)2562.9 1 3.3 43 0.8243 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854035] Re: window tasking unclear in 19.10 with Blackbird theme
I posted a question on AskUbuntu, too: https://askubuntu.com/questions/1191788/how-to-fine-tune-modify-xfce4 -theme-blackbird-theme-issue-fix-to-alttab-nicel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854035 Title: window tasking unclear in 19.10 with Blackbird theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blackbird-gtk-theme/+bug/1854035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845694] Re: youtube-dl dead on arrival when installed from the apt repositories
youtube-dl is not the latest version on apt repository (like 2 years old) You can download youtube-dl from: https://github.com/ytdl-org/youtube-dl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845694 Title: youtube-dl dead on arrival when installed from the apt repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/1845694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845694] Re: youtube-dl dead on arrival when installed from the apt repositories
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: youtube-dl (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/1845694 Title: youtube-dl dead on arrival when installed from the apt repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/1845694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444880] Re: xrandr report inverted gamma values
A bug report was filed in 2010, supposedly fixed in 2018 and patched in 2019 in `xrandr` version `1.5.1`. I tried compiling `1.5.1` in Ubuntu but it didn't seem to have been fixed yet. Documented in this Ask Ubuntu Q: [When will xrandr version 1.5.1 be available in Ubuntu?](https://askubuntu.com/questions/1192154/when-will-xrandr- version-1-5-1-be-available-in-ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444880 Title: xrandr report inverted gamma values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810070] Re: 18.04.1 Live CD fails to boot with EFI errors
I can confirm the same error on the Lifebook S761. Any solution? You cannot run any Linux Live Distribution from USB. "" Could not get fio For Li -DeviceHandle: Invalid Parameter Failed to find fs: Invalid Parameter Failed to load image /EFI/BOOT/grubx64.efi: INvaild parameter start_image() returned Invalid Parameter"" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810070 Title: 18.04.1 Live CD fails to boot with EFI errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1810070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854586] Re: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 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/1854586 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1854586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854586] [NEW] package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: was installing mysql.half done then interrupted. started again then this error showed up ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sat Nov 30 23:08:35 2019 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-11-29 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: 2019-11-30T17:38:32.574432Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18-0ubuntu0.19.10.1) starting as process 8394 2019-11-30T17:38:32.851170Z 1 [ERROR] [MY-013178] [Server] Execution of server-side SQL statement 'CREATE SCHEMA mysql DEFAULT COLLATE utf8mb4_0900_ai_ci' failed with error code = 1049, error message = 'System schema directory does not exist.'. 2019-11-30T17:38:32.852454Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2019-11-30T17:38:32.853010Z 0 [ERROR] [MY-010119] [Server] Aborting 2019-11-30T17:38:33.387831Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.18-0ubuntu0.19.10.1) (Ubuntu). MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['server-cert.pem', 'ca.pem', 'public_key.pem', 'server-key.pem', 'client-cert.pem', 'ib_logfile0', 'performance_schema', 'ca-key.pem', 'debian-5.7.flag', 'ib_buffer_pool', 'binlog.03', 'auto.cnf', 'private_key.pem', 'binlog.04', 'sys', 'ib_logfile1', 'mysql.ibd', '#innodb_temp', 'binlog.01', 'undo_002', 'binlog.05', 'binlog.02', 'binlog.index', 'client-key.pem', 'ibdata1', 'undo_001'] ProcCmdline: BOOT_IMAGE=/BOOT/ubuntu_qgn0bg@/vmlinuz-5.3.0-23-generic root=ZFS=rpool/ROOT/ubuntu_qgn0bg ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854586 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1854586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 Hi @hui.wang, the RPi4 boots off the sdcard normally but then I use a USB3 enclosure with disks to assemble a RAID1 BTRFS device to be used as rootfs. At the end of the boot, there is no /dev/mmcblk0* device: #> ls -ld /dev/m* drwxr-xr-x 2 root root 80 Nov 30 15:42 /dev/mapper crw--- 1 root root 10, 227 Nov 30 15:42 /dev/mcelog crw-r- 1 root kmem 1, 1 Nov 30 15:42 /dev/mem crw--- 1 root root 10, 56 Nov 30 15:42 /dev/memory_bandwidth drwxrwxrwt 2 root root 40 Nov 30 15:41 /dev/mqueue Anyway, this is just "an annoyance" that makes just a bit harder to switch kernel, the real problem is this one: Nov 29 10:36:05 raspippa kernel: [39364.240711] xhci_hcd :01:00.0: WARN Cannot submit Set TR Deq Ptr Nov 29 10:36:05 raspippa kernel: [39364.240725] xhci_hcd :01:00.0: A Set TR Deq Ptr command is pending. Nov 29 10:36:05 raspippa kernel: [39364.373694] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Nov 29 10:36:05 raspippa kernel: [39364.396405] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Nov 29 10:36:35 raspippa kernel: [39394.961204] xhci_hcd :01:00.0: WARN Cannot submit Set TR Deq Ptr Nov 29 10:36:35 raspippa kernel: [39394.961218] xhci_hcd :01:00.0: A Set TR Deq Ptr command is pending. Nov 29 10:36:36 raspippa kernel: [39395.324521] usb 2-1: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Nov 29 10:36:36 raspippa kernel: [39395.344764] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK Nov 29 10:36:36 raspippa kernel: [39395.344789] sd 0:0:0:0: [sda] tag#0 CDB: Read(16) 88 00 00 00 00 01 e1 20 4d 00 00 00 04 00 00 00 Nov 29 10:36:36 raspippa kernel: [39395.344813] blk_update_request: I/O error, dev sda, sector 8071957760 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0 According to this thread (https://bugzilla.kernel.org/show_bug.cgi?id=202541) every kernel >= 4.20 is affected and there's still no patch in 5.3. I'll try to go back to some 4.19.y kernel, I'm even prepared to lower the memory to 1 Gb, cause so far this raspberry hasn't had more than a day of consecutive uptime. ** Bug watch added: Linux Kernel Bug Tracker #202541 https://bugzilla.kernel.org/show_bug.cgi?id=202541 ** Attachment added: "dmesg-raspippa-fresh-boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+attachment/5308946/+files/dmesg-raspippa-fresh-boot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817307] Re: ipmitool crashed with SIGSEGV
** Changed in: ipmitool (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817307 Title: ipmitool crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1817307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773947] Re: package spotweb 20130826+dfsg3-4 failed to install/upgrade: installed spotweb package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: spotweb (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/1773947 Title: package spotweb 20130826+dfsg3-4 failed to install/upgrade: installed spotweb package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spotweb/+bug/1773947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668073] Re: Bleachbit: malformed database schema (collection_metadata) - near "WITHOUT": syntax error: kinto.sqlite.
Hi Daniel, as BB1.12 is very old, too, source is no more maintained and bugs/issues are hard to analyze, because they can be already fixed in newer versions! Btw.: Latest stable BleachBit with a lot of changes and improvements are version 3! Can you give version 3 a try and maybe try to reproduce the issue again, too? If issue is still reproducible, can you ppen a new issue ticket for it here: https://github.com/bleachbit/bleachbit/issues ? I think as you have a "malformed database schema" and I know some "language based data imports" hot fixrd lately to (in BB3), I would suggest you to provide your used Firefox language too and maybe attach (the empty) SQLite file for analyze, also. Greets, Tobias B. Besemer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668073 Title: Bleachbit: malformed database schema (collection_metadata) - near "WITHOUT": syntax error: kinto.sqlite. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1668073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854583] [NEW] [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] Sound is distorted
Public bug reported: this works ok with latest 5.3.x kernel but not with 4.15 kernel kernel 5.0.0 does not work ok with zfs so I can't confirm it is fixed or not in 5.0.0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Nov 30 18:43:40 2019 SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP108 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] Sound is distorted UpgradeStatus: Upgraded to bionic on 2018-08-22 (465 days ago) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854583 Title: [ProLiant MicroServer Gen8, Nvidia GPU 81 HDMI/DP, Digital Out, HDMI] Sound is distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1854583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854582] [NEW] systemd-timesyncd.service not starting
Public bug reported: Kubuntu -19.10 (though I believe the problem also exists on prior versions) Time synchronization not working: -- greenman@Crynfyd19.10 /lib/systemd/system$ timedatectl status Local time: Sat 2019-11-30 08:21:57 PST Universal time: Sat 2019-11-30 16:21:57 UTC RTC time: Sat 2019-11-30 16:21:57 Time zone: America/Los_Angeles (PST, -0800) System clock synchronized: no NTP service: inactive RTC in local TZ: no greenman@Crynfyd19.10 /lib/systemd/system$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) since Sat 2019-11-30 08:21:28 PST; 2min 0s ago Condition: start condition failed at Sat 2019-11-30 08:23:15 PST; 12s ago └─ ConditionFileIsExecutable=!/usr/sbin/VBoxService was not met Docs: man:systemd-timesyncd.service(8) Main PID: 813 (code=exited, status=0/SUCCESS) Status: "Shutting down..." Nov 30 07:29:50 Crynfyd systemd[1]: Starting Network Time Synchronization... Nov 30 07:29:51 Crynfyd systemd[1]: Started Network Time Synchronization. Nov 30 07:30:21 Crynfyd systemd-timesyncd[813]: Synchronized to time server for the first time 91.189. Nov 30 08:21:28 Crynfyd systemd[1]: Stopping Network Time Synchronization... Nov 30 08:21:28 Crynfyd systemd[1]: systemd-timesyncd.service: Succeeded. Nov 30 08:21:28 Crynfyd systemd[1]: Stopped Network Time Synchronization. Nov 30 08:23:15 Crynfyd systemd[1]: Condition check resulted in Network Time Synchronization being ski -- The problem has to do with the file /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf; -- greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ cat disable-with-time-daemon.conf [Unit] # don't run timesyncd if we have another NTP daemon installed ConditionFileIsExecutable=!/usr/sbin/ntpd ConditionFileIsExecutable=!/usr/sbin/openntpd ConditionFileIsExecutable=!/usr/sbin/chronyd ConditionFileIsExecutable=!/usr/sbin/VBoxService -- I do have virtualbox installed, but not running, so VBoxService is not running. This means that although the binary is there, it is not providing time sync services, so the system is not time syncing. If I remove the line "ConditionFileIsExecutable=!/usr/sbin/VBoxService" from the file and restart, all is well: -- greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ sudo systemctl daemon-reload greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ sudo systemctl restart systemd-timesyncd.service greenman@Crynfyd19.10 /lib/systemd/system/systemd-timesyncd.service.d$ timedatectl status Local time: Sat 2019-11-30 08:29:43 PST Universal time: Sat 2019-11-30 16:29:43 UTC RTC time: Sat 2019-11-30 16:29:43 Time zone: America/Los_Angeles (PST, -0800) System clock synchronized: yes NTP service: active RTC in local TZ: no -- So instead of testing just for the existence of the binary, which is resulting in no time sync service, what it probably should do is check for a running process, and allow the service to start if no other time syncing service is running. ** Affects: systemd (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/1854582 Title: systemd-timesyncd.service not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1854582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290028] Re: .bak and *~ files are not deleted
Mike, after all this years, do you still use BB1? And if, can you maybe update to latest stable BB3? A lof of things have changed since version 1... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290028 Title: .bak and *~ files are not deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bleachbit/+bug/1290028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
While this is a bug in WSL's ELF loader I located to problem in binutil's strip and after the fix passed my testing I'll send it upstream and also SRU it to Eoan to let us rebuild affected packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854576] Re: An unresolvable problem occurred while calculating the upgrade
** Tags added: xenial2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854576 Title: An unresolvable problem occurred while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1854576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853864] Re: zfs installation fails on nvme devices
Thanks for the help. The install works flawlessly now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853864 Title: zfs installation fails on nvme devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1853864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850162] Re: Akonadi server will not start after upgrade to kubuntu 19.10
I was able to get akonadi to work with postgresql using a different set of instructions, located here, modified as necessary for kubuntu: https://vinzv.de/en/bringing-kmail-and-postgresql-together/ I did have to delete everything in ~/.local/share/akoandi and ~/,config/akonadi This does not change the fact that it still does not work with mysql-8.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850162 Title: Akonadi server will not start after upgrade to kubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1850162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854581] [NEW] Bluetooth disconnect on 16.04
Public bug reported: Bluetooth disconnect randomly and is out of order since I restart the computer. Stop and restart BT service doesn't change the issue. This happen on Asus M70V computer. sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since sam. 2019-11-30 16:57:58 CET; 2s ago Docs: man:bluetoothd(8) Main PID: 21551 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─21551 /usr/lib/bluetooth/bluetoothd bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Current Time Service could not be registered bluetoothd[21551]: gatt-time-server: Input/output error (5) bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Not enough free handles to register service bluetoothd[21551]: Sap driver initialization failed. bluetoothd[21551]: sap-server: Operation not permitted (1) bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSource nov. 30 16:57:58 happy-buntu bluetoothd[21551]: Endpoint registered: sender=:1.153 path=/MediaEndpoint/A2DPSink Thanks for help ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 30 17:00:50 2019 InstallationDate: Installed on 2018-04-16 (593 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=d3601bac-5eb3-4f24-a402-9211b2c74282 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:22:43:C5:84:05 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5002654 acl:731390 sco:0 events:294427 errors:0 TX bytes:507962830 acl:587355 sco:0 commands:258 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854581 Title: Bluetooth disconnect on 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Also affects: binutils (Ubuntu) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu) Status: New => In Progress ** Changed in: binutils (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: gzip (Ubuntu) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854578] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1854578/+attachment/5308927/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854578 Title: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854578] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1854578/+attachment/5308925/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854578 Title: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854578] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1854578/+attachment/5308928/+files/xserver.devices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854578 Title: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs