[Bug 1689578] Re: Lack of shell completion installation support for command line apps
Isn't this feature already available now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689578 Title: Lack of shell completion installation support for command line apps To manage notifications about this bug go to: https://bugs.launchpad.net/review-tools/+bug/1689578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
Fix proposed here: https://gitlab.gnome.org/3v1n0/mutter/merge_requests/1 That will at least make this particular crash impossible, and will close the bug. P.S. An apparently unrelated problem which limits my ability to test the fix is that Xorg doesn't start properly with nvidia-drm.modeset=1 until after you have run it as root at least once. And if you do that then even this bug stops happening (no fix required). So there's something broken with basic Xorg when using nvidia-drm.modeset=1 and that might be the root cause here. ** Changed in: mutter (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => Daniel van Vugt (vanvugt) ** Also affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-410 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided => High ** Also affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Seems to be the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1591352 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Richard, I understand your point. Yes, time to time there are computers that have specific errors/messages thrown in dmesg [non fatal mostly], but usually can be fixed and solved rather easily (I always look at syslog, etc. on every new install to check/solve specifically for them). I've never, in my experience, have had issues where the system would immediately softlock in this way. Heck, I've even had Linux (and reactOS) running on an old gateway 800MHZ Celeron 192MB RAM run better than this thing! And it didn't softlock out of the box. My issues of contention is that the same MB/CPU combo runs perfectly fine now in both HP and Lenovo's versions of this laptop. It's really just lazy programming on Acer's part; to be honest, there were issues even with win10 on earlier BIOS revisions too. I moonlight as a programmer time to time [bad one at that], however, I dedicate a lot of time to debug my work so it works as expected. These issues, from multiple people, are telling Acer what the problems are and how to resolve them and we are still receiving buggy revisions.Thank you for all your work with this and trying to help us all out. I am willing to get a 8pin clip and deal with the BIOS myself at this point, but I'm not that great at decoding it. Let me know if interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
The Nvidia driver problem might be related to this, which I have also been seeing in other Nvidia bug reports recently: Apr 07 15:58:06 kab /usr/lib/gdm3/gdm-x-session[1493]: (II) NVIDIA(0): Validated MetaModes: Apr 07 15:58:06 kab /usr/lib/gdm3/gdm-x-session[1493]: (II) NVIDIA(0): "NULL" Apr 07 15:58:06 kab /usr/lib/gdm3/gdm-x-session[1493]: (II) NVIDIA(0): Virtual screen size determined to be 640 x 480 That's a general Nvidia driver problem with Xorg and not a problem with mutter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Also, if the MB/CPU combo are the same, can't we just flash a different Manufactures BIOS onto these. Just a thought. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
And this shows the problem really is originating in the Nvidia driver: $ xrandr --verbose Screen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 16384 So the GPU has no CRTCs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
and $ xrandr Screen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 16384 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
didrocks, While experiencing the bug, what output do you get from: 1. glxinfo | grep OpenGL 2. xrandr ? ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
Dylan, It's unlikely you will encounter this bug since so far it only affects one person. But also no one can say for sure. You would have to try it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823346] Re: SD card stays locked even when unlocked
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.1-rc3 kernel [0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed”, and attach dmesg. Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc3/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823346 Title: SD card stays locked even when unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
I have the same issue, but with a Ryzen 7 1700 with the following setups: Setup 1: Motherboard: Gigabyte B450 Aorus M (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Asus Mining Radeon RX 470 4G GDDR5 SSD: 240 GB WD Green Setup 2: Motherboard: ASRock AB350M Pro4 (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Sapphire Radeon RX 550 2G GDDR5 SSD: 240 GB WD Green The issue first started after installing the second GPU on each of the systems. I can't even boot the system, as the errors appear right after BIOS initialization. The errors are like: [exerpt] AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out ... AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7560] Entering emergecy mode. Exit the shell to continue. Type "journalctl" to view system logs. AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb75d0] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7700] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7630] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7660] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7690] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb76c0] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb76f0] ... AMD-Vi: Completion-Wait loop timed out AMD-Vi: Event logged [IO_PAGE_FAULT device=23:00.3 domain=0x000 address=0xfffd3990 flags=0x0070] ... Buffer I/O error on dev dm-0, logical block 104857472, async page read Buffer I/O error on dev dm-0, logical block 104857473, async page read Buffer I/O error on dev dm-0, logical block 104857474, async page read Buffer I/O error on dev dm-0, logical block 104857475, async page read Buffer I/O error on dev dm-0, logical block 104857476, async page read Buffer I/O error on dev dm-0, logical block 104857477, async page read . After some research I discovered that it is a IOMMU issue. I turned IOMMU off on both motherboards, and I managed to boot the system. I am an architect and I use blender for GPU rendering (this is the idea of having two), but the AMDGPU-Pro driver from the AMD's website (the only one that Blender uses for GPU rendering, as it can't use the open one) affects the way Gnome works on Xorg. It affects in the way that it doesn't start at all, it keeps restarting to the GDM screen... Any ideas? Thanks. ** Attachment added: "the screen photos when the errors appeared" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463/+attachment/5253632/+files/Photos.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.1-rc3 kernel [0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed”, and attach dmesg. Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc3/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
My bad, didn't notice it's AMD graphics instead of Intel graphics. Please test mainline kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823516] [NEW] Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Public bug reported: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco nvidia-drm.modeset third-party-packages ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Nvidia-418 installed but GLX is using LLVMpipe/Mesa in Wayland sessions + Nvidia-418 installed but GLX and EGL are using LLVMpipe/Mesa in Wayland sessions ** Description changed: - Nvidia-418 installed but GLX is using LLVMpipe/Mesa in Wayland sessions. + Nvidia-418 installed but GLX and EGL are using LLVMpipe/Mesa in Wayland + sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Nvidia-418 installed but GLX and EGL are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: + $ es2_info | grep ^GL + GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 + GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) + + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux
[Bug 1808108] Re: nvidia-drm.modeset=1 incurs very high CPU usage in [kworker/u16:1+events_unbound]
** Tags added: nvidia-drm.modeset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808108 Title: nvidia-drm.modeset=1 incurs very high CPU usage in [kworker/u16:1+events_unbound] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1808108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823256] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-p
*** This bug is a duplicate of bug 1617564 *** https://bugs.launchpad.net/bugs/1617564 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1617564, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1617564 [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823256 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1823256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
Hi, I think I have enabled pre-released updates. Is the kernel version (4.18.0-17-generic), the one that should have this patch? I am wondering because wifi does not seem to work with this kernel. Thank ** Attachment added: "devel-enabled.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818204/+attachment/5253636/+files/devel-enabled.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714705] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (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/1714705 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1714705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714705] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-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/1714705 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1714705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
Still, the fix to stop mutter crashing when it encounters the Nvidia bug is: https://gitlab.gnome.org/3v1n0/mutter/merge_requests/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815550] Re: gnome-shell high memory and CPU usage when using zsh
Chris, Please also do a sanity check and run: glxinfo What do you see? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815550 Title: gnome-shell high memory and CPU usage when using zsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
WORKAROUND: Before trying to log in, do this: 1. Ctrl+Alt+F4, log in to VT4 and run: sudo Xorg :4 vt4 2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in normally. No crash. Something about having run Xorg as root already seems to be enough to avoid the bug in the Nvidia driver which is the root cause here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818614] Related fix proposed to neutron (stable/stein)
Related fix proposed to branch: stable/stein Review: https://review.openstack.org/650574 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818614 Title: [SRU] Various L3HA functional tests fails often To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818614] Related fix proposed to neutron (stable/rocky)
Related fix proposed to branch: stable/rocky Review: https://review.openstack.org/650575 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818614 Title: [SRU] Various L3HA functional tests fails often To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818614] Related fix proposed to neutron (stable/queens)
Related fix proposed to branch: stable/queens Review: https://review.openstack.org/650576 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818614 Title: [SRU] Various L3HA functional tests fails often To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823296] Re: g++ 7.3 and g++ 8.2 report segmentation fault
The preprocessed source is included.
gcc -c test.ii
../test.cpp: In function ‘void test_shape_creator()’:
../test.cpp:19:18: internal compiler error: Ошибка сегментирования
blaspp<1> v({14});
^
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
** Attachment added: "Preprocessed source"
https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1823296/+attachment/5253640/+files/test.ii
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823296
Title:
g++ 7.3 and g++ 8.2 report segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1823296/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
** Description changed: https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c + + + WORKAROUNDS + + Don't use kernel parameter nvidia-drm.modeset=1 + + - or - + + Before trying to log in: + + 1. Ctrl+Alt+F4, log in to VT4 and run: + +sudo Xorg :4 vt4 + + 2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in + normally. + + + ORIGINAL DESCRIPTION I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3 vertical displays. I changed to the X.org driver and rebooted. This error popped up on reboot. And now only one display is working. This one display is only working in landscape instead of portrait mode. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: budgie-core 10.5-0ubuntu1 Uname: Linux 5.0.2-050002-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Apr 1 09:16:50 2019 ExecutablePath: /usr/bin/budgie-wm InstallationDate: Installed on 2019-01-10 (80 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) ProcCmdline: budgie-wm ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: budgie-desktop StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823521] [NEW] on_ac_power returns 1 if battery is not present
Public bug reported: on_ac_power should return 0 (as exit code). Besides Xfce Power Manager tells in Devices tab that Line power is "Not plugged in". Tested by an old Macbook. (I don't have battery to test with.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: powermgmt-base 1.33 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 7 14:02:36 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (821 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: powermgmt-base UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-power-manager Importance: Undecided Status: New ** Affects: powermgmt-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: xfce4-power-manager 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/1823521 Title: on_ac_power returns 1 if battery is not present To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1823521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823503] Re: systemd-resolved ignores /etc/network/interfaces on Ubuntu 18.04
For new installations, the /etc/network/interfaces file does have text explaining that ifupdown is no longer used and network config is now done via netplan. For upgrades of systems using ifupdown, it is not removed, and should still manage the networking, and changes to /e/n/i should still work. To address your bug that systemd-resolved ignores any settings in e/n/i, that's correct that systemd-resolved will not *directly* look at the e/n/i config to find nameserver configuration. However, if ifupdown is managing your system networking, then it will provide nameserver details to systemd-resolved. The specific mechanism depends on your specific network configuration (e.g. static vs dhcp) and if you have resolvconf installed or not. If you are having a specific problem with your system networking, please feel free to add details about what is wrong. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823503 Title: systemd-resolved ignores /etc/network/interfaces on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821491] Re: DNS lookup fails for local hosts
** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753518] Re: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Just hit this on an Dell E5250 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753518 Title: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823523] [NEW] Is bound to remove a kernel that a manually installed package depends on
Public bug reported: Say, I have linux-generic-hwe-18.04 and linux-generic installed. Software Updater may remove linux-image-4.15.0-47-generic even if manually installed linux-generic depends on it (recursively). $ apt-cache rdepends --important --installed --recurse linux-image-4.15.0-47-generic linux-image-4.15.0-47-generic Reverse Depends: linux-image-generic |linux-modules-extra-4.15.0-47-generic linux-image-generic Reverse Depends: linux-generic linux-generic linux-generic linux-modules-extra-4.15.0-47-generic Reverse Depends: linux-image-generic linux-generic Reverse Depends: $ apt-mark showmanual linux-generic linux-generic I think it should at least disable removing such a kernel by default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: update-manager 1:18.04.11.9 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 7 14:26:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (821 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug bionic 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/1823523 Title: Is bound to remove a kernel that a manually installed package depends on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1823523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822820 phase: Packaging phase-changed: Sunday, 07. April 2019 05:05 UTC reason: prepare-package-meta: Pending -- package tag not yet published - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- source package tags missing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822803 Title: linux-oem: 4.15.0-1036.41 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823523] Re: Is bound to remove a kernel that a manually installed package depends on
Software Updater installs newer version of linux-generic that depends on a newer version of linux-image-4.15.0 in the same run, so this is invalid. ** Changed in: update-manager (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/1823523 Title: Is bound to remove a kernel that a manually installed package depends on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1823523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654070] Re: sanity check can fail for packages missing dependencies
Verified with 1.1ubuntu1.18.04.7~16.04.2: Added a not existing dep to git: # vi /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_xenial-security_main_binary-amd64_Packages # apt-cache show git ... Package: git Architecture: amd64 Version: 1:2.7.4-0ubuntu1.6 Multi-Arch: foreign Priority: optional Section: vcs Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Gerrit Pape Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 23556 Provides: git-completion, git-core Depends: libc6 (>= 2.16), libcurl3-gnutls (>= 7.16.2), libexpat1 (>= 2.0.1), libpcre3, zlib1g (>= 1:1.2.0), perl-modules, liberror-perl, git-man (>> 1:2.7.4), git-man (<< 1:2.7.4-.), zz-not-existing-dep ... # installed old git # apt install git=1:2.7.4-0ubuntu1 ... # unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial ... Checking: git ([]) pkg git not in allowed origin sanity check failed pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: InstCount=0 DelCount=0 BrokenCount=0 # Now git is not listed among packages to be installed. The message of not being in an allowed origin is correct, git from -updates is installable. There could be a better debug message and when I add the missing dep to the version in -updates, only the "sanity check failed" is printed. Users can turn to APT to explain: root@x-uu-verify:~# apt install git Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: git : Depends: zz-missing-dep-updates but it is not installable E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654070 Title: sanity check can fail for packages missing dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654070] Re: sanity check can fail for packages missing dependencies
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654070 Title: sanity check can fail for packages missing dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811029] Re: Package installation fails when attempting to download GeoIP database files
The Debian BTS has a related report [1] which suggests to me this issue should have been fixed way back in v1.11. But even if installing wasn't broken, with the legacy databases discontinued, it's not much use in the long term. Geoip-database-contrib has already been removed from Debian entirely [2] due to deprecation by upstream, apparently in favor of geoipupdate [3]. (I'm not affiliated with either package and have no solutions; I'm just documenting the connections here.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666063 * [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900400 * [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885441 ** Bug watch added: Debian Bug tracker #666063 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666063 ** Bug watch added: Debian Bug tracker #900400 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900400 ** Bug watch added: Debian Bug tracker #885441 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885441 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811029 Title: Package installation fails when attempting to download GeoIP database files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoip-database-contrib/+bug/1811029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823461] Re: Font hinting lost on chrome like browser
Thank you for notify. Gunnar's patch looks good to me. I attach compared image on 18.10. Top: original config Middle: Mohammad's patch: Use embedded font for example "生み出された". Bottom: Gunnar's patch: Looks the same as like original config. ** Attachment added: "compare.png" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+attachment/5253679/+files/compare.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Description changed: + [Impact] + After opening nautilus, I open 'another' tab with the mouse wheel button (middle mouse button) in 'Other Locations' and nautilius crashes. + + [Test Case] + 1. Open nautilus + 2. Click with the middle mouse button on 'Other Locations' + 3. Crash nautilus + + [Original Description] I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 08:21:59 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' - b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' - b'org.gnome.nautilus.window-state' b'maximized' b'true' - b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' + b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' + b'org.gnome.nautilus.window-state' b'maximized' b'true' + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2018-12-02 (125 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () - ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () + ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Description changed: [Impact] After opening nautilus, I open 'another' tab with the mouse wheel button (middle mouse button) in 'Other Locations' and nautilius crashes. [Test Case] 1. Open nautilus - 2. Click with the middle mouse button on 'Other Locations' + 2. Click with the middle mouse button on 'Other Locations' (To open another tab) 3. Crash nautilus [Original Description] I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 08:21:59 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2018-12-02 (125 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446552] Re: Unattended upgrades handles new dependencies inconsistently
Verified 1.1ubuntu1.18.04.7~16.04.2 on Ubuntu Xenial. I changed a different, but equivalent way of verifying the fix, in /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages I bumped the version of bash-doc to 4.3-14ubuntu1.3, bumped git's version in updates to 1:2.7.4-0ubuntu1.7 and made git depend on bash-doc (>= 4.3-14ubuntu1) in both -updates and -security. Bash-doc was not installed originally on the system. With unfixed u-u it fails to upgrade git: root@x-uu-ref:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] Checking: git ([]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals root@x-uu-ref:~# vi /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages root@x-uu-ref:~# vi /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages root@x-uu-ref:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] adjusting candidate version: 'git=1:2.7.4-0ubuntu1.6' Checking: git ([]) pkg 'bash-doc' not in allowed origin sanity check failed adjusting candidate version: 'git=1:2.7.4-0ubuntu1.6' pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: adjusting candidate version: 'git=1:2.7.4-0ubuntu1.6' Packages that are auto removed: 'libfreetype6' Packages were successfully auto-removed InstCount=0 DelCount=0 BrokenCount=0 With fixed u-u, git is upgraded: root@x-uu-verify:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages Using (^linux-image-4\.18\.0\-17\-generic$|^linux-headers-4\.18\.0\-17\-generic$|^linux-image-extra-4\.18\.0\-17\-generic$|^linux-modules-4\.18\.0\-17\-generic$|^linux-modules-extra-4\.18\.0\-17\-generic$|^linux-signed-image-4\.18\.0\-17\-generic$|^kfreebsd-image-4\.18\.0\-17\-generic$|^kfreebsd-headers-4\.18\.0\-17\-generic$|^gnumach-image-4\.18\.0\-17\-generic$|^.*-modules-4\.18\.0\-17\-generic$|^.*-kernel-4\.18\.0\-17\-generic$|^linux-backports-modules-.*-4\.18\.0\-17\-generic$|^linux-modules-.*-4\.18\.0\-17\-generic$|^linux-tools-4\.18\.0\-17\-generic$|^linux-cloud-tools-4\.18\.0\-17\-generic$) regexp to find running kernel packages Checking: git ([]) adjusting candidate version: git=1:2.7.4-0ubuntu1.6 adjusting candidate version: bash-doc=4.3-14ubuntu1.2 pkgs that look like they should be upgraded: git Get:1 http://security.ubuntu.com/ubuntu xenial-security/main amd64 bash-doc all 4.3-14ubuntu1.2 [1151 kB] Fetched 1151 kB in 0s (0 B/s) fetch.run() result: 0 http://security.ubuntu.com/ubuntu/pool/main/b/bash/bash-doc_4.3-14ubuntu1.2_all.deb' ID:1 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/bash-doc_4.3-14ubuntu1.2_all.deb) No conffiles in deb /var/cache/apt/archives/bash-doc_4.3-14ubuntu1.2_all.deb (There is no member named 'conffiles') http://security.ubuntu.com/ubuntu/pool/main/g/git/git_2.7.4-0ubuntu1.6_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/git_1%3a2.7.4-0ubuntu1.6_amd64.deb) found pkg: git conffile line: /etc/bash_completion.d/git-prompt - blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: git Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log adjusting candidate version: bash-doc=4.3-14ubuntu1.2 adjusting c
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/980 + + --- + [Impact] After opening nautilus, I open 'another' tab with the mouse wheel button (middle mouse button) in 'Other Locations' and nautilius crashes. [Test Case] 1. Open nautilus - 2. Click with the middle mouse button on 'Other Locations' (To open another tab) + 2. Click with the middle mouse button on 'Other Locations' 3. Crash nautilus [Original Description] I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 08:21:59 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2018-12-02 (125 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647887] Re: NVMe driver accidentally reverted to use GSI instead of MSIX
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647887 Title: NVMe driver accidentally reverted to use GSI instead of MSIX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823532] [NEW] Não Entra no google. E as vezes fica com a tela azul
Public bug reported: As vezes a tela fica azul ou preta impossibilita acessar as funções e tela e preta . As não entra no google e nas outras funções, e parece algo relacionado ao software que impedi e baixar e atualiza . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evolution-data-server 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 7 09:39:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-02-24 (41 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: evolution-data-server Title: package evolution-data-server 3.18.5-1ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Summary changed: - não entra no google as vezes e tela azul + Não Entra no google e as vezes e tela azul ** Summary changed: - Não Entra no google e as vezes e tela azul + Não Entra no google. e as vezes e tela azul ** Summary changed: - Não Entra no google. e as vezes e tela azul + Não Entra no google. E as vezes fica com a tela azul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823532 Title: Não Entra no google. E as vezes fica com a tela azul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1823532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573594] Re: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573594 Title: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1573594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547680] Re: bonded interfaces in bridge do not have LRO turned off
** Changed in: linux-lts-utopic (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-utopic (Ubuntu) Status: Won't Fix => 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/1547680 Title: bonded interfaces in bridge do not have LRO turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823533] [NEW] Unable to click on anything inside the window on Krita
Public bug reported: When opening Krita, I am not able to click on anything inside the window, it looks like it only works with keyboard shortcuts, but it's still unusable This problem does not happen on Krita snap/flathub variants! Ubuntu 19.04, krita version 1:4.1.7+dfsg-1 I can reproduce the issue on both my laptop and desktop with Ubuntu 19.04 Program output Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use: QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen factors. QT_SCREEN_SCALE_FACTORS to set per-screen factors. QT_SCALE_FACTOR to set the application global scale factor. qt5ct: using qt5ct plugin No "breeze" available. Set style "fusion" Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" libpng warning: iCCP: profile 'icc': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'icc': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'icc': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'icc': 'RGB ': RGB color space not permitted on grayscale PNG WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! WARNING: vector instructions disabled by 'amdDisableVectorWorkaround' option! /usr/lib/x86_64-linux-gnu/krita-python-libs/krita added to PYTHONPATH krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Regular") krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Bold") krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Regular") krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Regular") krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Regular") krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Light") krita.general: Could not find font QVariant(QString, "Source Sans Pro") with style QVariant(QString, "Regular") qt5ct: D-Bus global menu: no file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/brushsize-increase file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/opacity-decrease file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/opacity-increase file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/lightness-increase file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/lightness-decrease file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/zoom-in file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/rotate-canvas-left file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/rotation-reset file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/rotate-canvas-right file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/zoom-out file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/brushsize-decrease file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/preset-switcher file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/krita/sketch/components/Button.qml:84:9: QML Image: Failed to get image from provider: image://icon/edit-cl
[Bug 1823534] [NEW] bugs, but i don't know. Experienced a lot, so
Public bug reported: am a newbie. Shouldn't have tested 18.10. Instead should have gone for LTS. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-17-generic 4.18.0-17.18 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 2979 F pulseaudio /dev/snd/controlC0: pranav 2979 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 19:19:30 2019 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=09e25397-4a2c-4fb0-a605-a7013eecb59c HotplugNewDevices: HotplugNewMounts: MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=aad43495-2006-41af-bcb1-f91673ac405e ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.18.0-17-generic N/A linux-backports-modules-4.18.0-17-generic N/A linux-firmware 1.175.1 SourcePackage: linux StagingDrivers: r8188eu Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 19:19:36.717: The udisks-daemon is running (name-owner :1.11). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2018:svnDellInc.:pnInspiron5548:pvrA09:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823534 Title: bugs, but i don't know. Experienced a lot, so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
https://gitlab.gnome.org/GNOME/nautilus/issues/980 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #980 https://gitlab.gnome.org/GNOME/nautilus/issues/980 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823535] Re: crashed a lot
let me know, ... if u want anything more -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823535 Title: crashed a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Already verified in 0.90ubuntu0.5 for Xenial, not additional test is needed. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823535] [NEW] crashed a lot
Public bug reported: experienced a lot of crashing on normal day-to-day activities. so this report ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11.5 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 19:26:52 2019 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2019-03-30 12:16:27.844625 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823535 Title: crashed a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823536] [NEW] Bugs in my life, episode 4
Public bug reported: i hope i knew someting... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11.5 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 19:30:27 2019 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2019-03-30 12:16:27.844625 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823536 Title: Bugs in my life, episode 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823537] [NEW] Bugs in my life, episode 5
Public bug reported: i wish i knew anything ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11.5 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 19:33:37 2019 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2019-03-30 12:16:27.844625 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823537 Title: Bugs in my life, episode 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823534] 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/1823534 Title: bugs, but i don't know. Experienced a lot, so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists
I think this has gotten even worse in duplicity. I believe this used to only affect full backups. But now it seems to affect incremental backups too. I've attached a simple reproduction script. It basically just does: PASSPHRASE=one duplicity full /tmp/testdir file://$DIR PASSPHRASE=two duplicity /tmp/testdir file://$DIR Although the second duplicity run complains about a bad password, it will still continue and make an incremental backup with a different passphrase than the full volumes. Tested with duplicity 0.7.18.2. I've worked around this behavior in deja-dup 39.1. ** Attachment added: "repro.sh" https://bugs.launchpad.net/duplicity/+bug/918489/+attachment/5253715/+files/repro.sh ** Summary changed: - duplicity allows bad passphrase on full backup if archive cache exists + duplicity allows a new, different passphrase if an archive cache exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows a new, different passphrase if an archive cache exists To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823461] Re: Font hinting lost on chrome like browser
Thanks for confirming! I have uploaded the fix to disco and bionic. ** Description changed: + [Impact] + + The file for configuring Japanese rendering with Noto fonts does not + refer to the font family with sufficient precision, so it may affect + rendering with other fonts unintentionally. The proposed upload fixes + the issue. + + [Test Case] + + The real tests have been reported in comment #6 and #7 of this bug + report. + + To verify that the modified file is properly installed: + + 1. Install language-selector-common and language-selector-gnome from +bionic-proposed + + 2. Run this command: + + cat /etc/fonts/conf.avail/69-language-selector-ja.conf | grep 'Noto Sans + CJK JP' + + (should output the line "Noto Sans CJK JP") + + [Regression Potential] + + That config file was added specifically for rendering Japanese with Noto + fonts, and the modified file has been confirmed by the original author. + Hence the regression risk should be low. + + [Original description] + Since Ubuntu 18.04 (maybe from 17.10, I don't remember now), Chrome browsers are horrible to use. Font hintings are not working as expected. There were always some hairy things above the fonts which caused me to abandon Ubuntu. Unfortunately, this bug affected all other Ubuntu derivatives as well. I was forced to use Debian and Manjaro, because nowhere in the Internet I found a solution. I've tested Ubuntu 19.04 again. I removed all of the *.conf file in `/etc/fonts/conf.d` dir and copied Manjaro's configs. The fonts are okay. Further investigating revealed that the culprit was symlink to this file `/etc/fonts/conf.avail/69-language-selector-ja.conf` I opened it and found that on Line no 8, it has this which should instead be since `JP` is language identifier, not family. I manually fixed the file and all is well! I'm attaching two screenshot of chrome browser. Inspect the "Autofill" and "Appearance" word of the chrome setting page screenshot. ** Also affects: language-selector (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: language-selector (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: language-selector (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: language-selector (Ubuntu Bionic) Status: New => In Progress ** Changed in: language-selector (Ubuntu Bionic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1823161] Re: fails to resume after suspend
fyi: kernel 5.0.7-050007-generic also fixes the issue. Raf Op 5/04/19 om 13:23 schreef Kai-Heng Feng: > Please try the kernels between 4.18.0-10 and 4.18.0-17 and find out the > last good and first bad kernel. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823161 Title: fails to resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819478] Re: xtables-addons package V 3.0 not compatible to new Maxmind Data format - Update to V 3.3 needed
*** This bug is a duplicate of bug 1810920 *** https://bugs.launchpad.net/bugs/1810920 ** This bug has been marked a duplicate of bug 1810920 GeoLite2-Country-CSV support for Ubuntu 16.04/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/1819478 Title: xtables-addons package V 3.0 not compatible to new Maxmind Data format - Update to V 3.3 needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1819478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823540] [NEW] Add support for "DS Telecom DSU7" Modem
Public bug reported: Hi! I have a 3G modem, manufactured by "DS Telecom" brand. Model is "DSU7". After first connect i see in lsusb: Bus 002 Device 017: ID 05c6:1000 Qualcomm, Inc. Mass Storage Device In dmesg i see: [524807.861921] usb 2-1: USB disconnect, device number 20 [524826.496200] usb 2-1: new high-speed USB device number 21 using xhci_hcd [524826.646489] usb 2-1: New USB device found, idVendor=05c6, idProduct=1000 [524826.646498] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [524826.646505] usb 2-1: Product: Qualcomm CDMA Technologies MSM [524826.646511] usb 2-1: Manufacturer: Qualcomm, Incorporated [524826.646516] usb 2-1: SerialNumber: 35160225260 [524826.649083] usb-storage 2-1:1.0: USB Mass Storage device detected [524826.650207] scsi host3: usb-storage 2-1:1.0 After some googling i have solution and i wrote small patch (see attach). ** Affects: usb-modeswitch-data (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Patch for support DSU7 in usb-modeswitch-data" https://bugs.launchpad.net/bugs/1823540/+attachment/5253731/+files/support-for-DSU7.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823540 Title: Add support for "DS Telecom DSU7" Modem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch-data/+bug/1823540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918489] Re: duplicity allows a new, different passphrase if an archive cache exists
** Changed in: duplicity Status: New => Confirmed ** Changed in: duplicity (Ubuntu) Importance: Undecided => High ** Changed in: duplicity (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows a new, different passphrase if an archive cache exists To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820187] Re: Huawei Hi1822 NIC has poor performance
Verification done. See comment #2 and #3. ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820187 Title: Huawei Hi1822 NIC has poor performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823542] [NEW] usbauth segfault
Public bug reported:
Under not entirely clear conditions, usbauth(1) will segfault
(see attached kern.log excerpt). In this particular case,
it is known the segfault is caused by the serial="..." Attribute
in /etc/usbauth.conf
allow idVendor==0x059f idProduct==0x1061
serial=="75686ff51019"
Without that serial="..." there is no segfault.
(It is also not clear if the "double quotes" are necessary or allowed;
either way there is a segfault (presumed to be the same).)
In what I _think_ is the usbauth source at
https://github.com/kochstefan/usbauth-all
commit 9a081a80b7c9 ("fix segfault on strtol") MAY be the fix?
https://github.com/kochstefan/usbauth-all/commit/9a081a80b7c9ed221b733e33d5fcd73b0da18f4d
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: usbauth 1.0~git20180214-1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Apr 7 16:39:21 2019
InstallationDate: Installed on 2016-10-07 (912 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: usbauth
UpgradeStatus: Upgraded to bionic on 2018-08-18 (232 days ago)
mtime.conffile..etc.usbauth.conf: 2019-04-07T16:38:01.039187
** Affects: usbauth (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/1823542
Title:
usbauth segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1823542/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822206] Re: pcmanfm suddenly froze when opening a folder
This bug is more frequent than what I initially expected: it’s the third time it occurred since I initially reported. Has something been changed recently in the software or its dependencies? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822206 Title: pcmanfm suddenly froze when opening a folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1822206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763942] Re: Text selection in dialog windows have low contrast
** Also affects: gtk+3.0 (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/1763942 Title: Text selection in dialog windows have low contrast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763942] Re: Text selection in dialog windows have low contrast
** Tags added: cosmic disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763942 Title: Text selection in dialog windows have low contrast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821412] Re: "System program problem" report button does nothing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-notifier (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/1821412 Title: "System program problem" report button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1821412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821412] Re: "System program problem" report button does nothing
It's happening to me with Ubuntu 18.04 LTS Desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821412 Title: "System program problem" report button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1821412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
vram usage on fresh start ** Attachment added: "freshstart.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+attachment/5253738/+files/freshstart.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823544] [NEW] Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Public bug reported: GPU: NVIDIA GTX 1060 3GB Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux NVIDIA driver version: 418.56 Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p I have noticed this strange behavior only on gnome-shell where the overall gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not happen on other desktops, or on Windows, happens after some hours of normal desktop usage Even the system RAM increases a lot during normal usage, but remains acceptable This behaviour can be observed by using "nvidia-smi" a tool from the NVIDIA proprietary driver gnome-shell VRAM usage on a cold start: 139MB, + 9 MB X.org VRAM usage on cold start: 48MB + 18MB Total: 214MB gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB X.org VRAM usage after some hours of normal usage: 244MB + 18MB Total: 800MB On windows or other desktops the GPU VRAM usage remains the same ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "vram usage after some hours" https://bugs.launchpad.net/bugs/1823544/+attachment/5253737/+files/aftersomehours.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821870] Re: gnome-shell segfault libmutter-clutter-2
https://errors.ubuntu.com/oops/9f40d39c-5948-11e9-a557-fa163ee63de6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821870 Title: gnome-shell segfault libmutter-clutter-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756191]
*** Bug 14790 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756191 Title: Thumbnail sidebar shows error icons in place of some images. To manage notifications about this bug go to: https://bugs.launchpad.net/ristretto/+bug/1756191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I've custom (fixed) ACPI tables which can be loaded using grub parameters however similar "AE_ALREADY_EXISTS" conflict occurs because of the original tables. I can't disable the original table load. [0.462398] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.472822] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000._PCT], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.472848] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.472874] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000._PSS], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.472879] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.472915] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000.XPSS], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.472922] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.472966] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000._PSD], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.472973] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.472983] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000.PPCV], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.472988] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.472992] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000._PPC], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.472996] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.472999] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.473001] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000._CST], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473005] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473024] ACPI BIOS Error (bug): Failure creating named object [\_PR.C000._CSD], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473030] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473043] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001._PCT], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473048] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473059] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001._PSS], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473063] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473085] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001.XPSS], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473092] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473136] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001._PSD], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473143] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473153] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001.PPCV], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473158] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473163] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001._PPC], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473167] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473170] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.473172] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001._CST], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473176] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473195] ACPI BIOS Error (bug): Failure creating named object [\_PR.C001._CSD], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473200] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473213] ACPI BIOS Error (bug): Failure creating named object [\_PR.C002._PCT], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473218] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473228] ACPI BIOS Error (bug): Failure creating named object [\_PR.C002._PSS], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473233] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473255] ACPI BIOS Error (bug): Failure creating named object [\_PR.C002.XPSS], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473261] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473305] ACPI BIOS Error (bug): Failure creating named object [\_PR.C002._PSD], AE_ALREADY_EXISTS (20190215/dswload2-324) [0.473312] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [0.473323] ACPI BIOS Error (bug): Failure creating n
[Bug 1756191]
brainwash, from the Xubuntu Bugs team found that reverting https://git.xfce.org/apps/ristretto/commit/?id=69b7459957427aed16caddb699c5b496dfb6deee seems to resolve this issue. I have tested and confirmed. Can we go ahead and do this to restore thumbnail generation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756191 Title: Thumbnail sidebar shows error icons in place of some images. To manage notifications about this bug go to: https://bugs.launchpad.net/ristretto/+bug/1756191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763942] Re: Text selection in dialog windows have low contrast
Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763942 Title: Text selection in dialog windows have low contrast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787368] Re: Caja does not show previews of text files on Bionic and newer versions
Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected. ** Also affects: gtk+3.0 (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/1787368 Title: Caja does not show previews of text files on Bionic and newer versions To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1787368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823547] [NEW] Kernel crash during boot with IOMMU - on Dual GPU AMD system using Ryzen 7 1700
Public bug reported: I have the same issue, but with a Ryzen 7 1700 with the following setups: Setup 1: Motherboard: Gigabyte B450 Aorus M (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Asus Mining Radeon RX 470 4G GDDR5 SSD: 240 GB WD Green Setup 2: Motherboard: ASRock AB350M Pro4 (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Sapphire Radeon RX 550 2G GDDR5 SSD: 240 GB WD Green The issue first started after installing the second GPU on each of the systems. I can't even boot the system, as the errors appear right after BIOS initialization. The errors are like: [exerpt] AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out ... AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7560] Entering emergecy mode. Exit the shell to continue. Type "journalctl" to view system logs. AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb75d0] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7700] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7630] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7660] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7690] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb76c0] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb76f0] ... AMD-Vi: Completion-Wait loop timed out AMD-Vi: Event logged [IO_PAGE_FAULT device=23:00.3 domain=0x000 address=0xfffd3990 flags=0x0070] ... Buffer I/O error on dev dm-0, logical block 104857472, async page read Buffer I/O error on dev dm-0, logical block 104857473, async page read Buffer I/O error on dev dm-0, logical block 104857474, async page read Buffer I/O error on dev dm-0, logical block 104857475, async page read Buffer I/O error on dev dm-0, logical block 104857476, async page read Buffer I/O error on dev dm-0, logical block 104857477, async page read . I can't even install any new system, because the errors are the same... After some research I discovered that it is a IOMMU issue. I turned IOMMU off on both motherboards, and I managed to boot the system. I have been trying with CentOS 7, Ubuntu 18.04.2 and Fedora 29. I am an architect and I use blender for GPU rendering (this is the idea of having two cards), but the AMDGPU-Pro driver from the AMD's website (the only one that Blender uses for GPU rendering, as it can't use the open one) affects the way Gnome works on Xorg. In Ubuntu 18.04 Gnome doesn't start at all, it hangs up stating an error about snapd. Even after purging snapd, it still doesn't start... Fedora 29 is the only one that works, but the official AMDGPU-Pro don't work in it, thus I don't have the GPU rendering available. Any ideas? Two years have passed, or probably even more, and this IOMMU issues on AMD are yet not resolved... I have two different chipsets on my MBs (B350 and B450) and the issues are still there... Please help. Last resort is to start using Windows, after 15 years of using only Linux, but I don't really find this very appealing... Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd dual-gpu iommu ryzen ** Attachment added: "Photos.zip" https://bugs.launchpad.net/bugs/1823547/+attachment/5253739/+files/Photos.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823547 Title: Kernel crash during boot with IOMMU - on Dual GPU AMD system using Ryzen 7 1700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823547] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1823547 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823547 Title: Kernel crash during boot with IOMMU - on Dual GPU AMD system using Ryzen 7 1700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823542] Re: usbauth segfault
That fix (commit 9a081a80b7c9 ("fix segfault on strtol")),
which is in usbauth v1.0.1, does seem to have fixed this
problem. Ubuntu 19.04(? disco) contains usbauth v1.0.1,
and installing that package on my 18.04 LTS (Ubuntu bionic)
system fixed the segfault.
Testing with invalid serial="..." values, and similar,
confirmed it works; see attached usbauth.conf
I suggest the usbauth 1.0.1+git20190123.5004f7d-1 Ubuntu disco
package also be used for Ubuntu bionic LTS.
** Attachment added: "Now working (with usbauth v1.0.1) /etc/usbauth.conf"
https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1823542/+attachment/5253740/+files/usbauth.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823542
Title:
usbauth segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbauth/+bug/1823542/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759452] Re: Xorg doesn't start after update on VMs - vboxvideo_drv.so missing
This problem (still or again) occurs with ubu 18.04 (host), 18.10 (guest) and virtualbox 5.2.18. After installing the guest additions at the host, the guest system will boot, but x server will crash and state "Warning, couldn't open module vboxvideo". Modprobe vboxvideo will load the module, nevertheless X server will crash with the same message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759452 Title: Xorg doesn't start after update on VMs - vboxvideo_drv.so missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1759452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821462] Re: Ubuntu 19.04 Desktop:slow boot
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821462 Title: Ubuntu 19.04 Desktop:slow boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
Comment #19 PPA solved issue for me, will notify if it remains solved after a few reboots. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992194] Re: BOM symbols in ru_RU.aff affect some package installation
The files /usr/share/hunspell/ru_RU.aff and /usr/share/hunspell/ru_RU.dic also have wrong line endings: "\r\n" instead of just "\n". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823550] [NEW] Pluma wrongly has monospaced font in dropdown (context) menu
Public bug reported: Steps to reproduce: 1. Have Ubuntu MATE 17.04 installed 2. Open Pluma 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: pluma (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful bionic cosmic disco zesty ** Attachment added: "wrong monospaced font in pluma" https://bugs.launchpad.net/bugs/1823550/+attachment/5253743/+files/pluma-dropdown.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: Pluma wrongly has monospaced font in dropdown (context) menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1823550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823551] [NEW] unable to upgrade 16.04 -> 18.04
Public bug reported: Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Invalid package information After updating your package information, the essential package 'ubuntu-minimal' could not be located. This may be because you have no official mirrors listed in your software sources, or because of excessive load on the mirror you are using. See /etc/apt/sources.list for the current list of configured software sources. In the case of an overloaded mirror, you may want to try the upgrade again later. Restoring original system state Aborting g package lists... 6% *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. Reading package lists... Done Building dependency tree Reading state information... Done . === Command terminated with exit status 1 (Sun Apr 7 17:15:11 2019) === ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Sun Apr 7 17:12:07 2019 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2019-04-07 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade uec-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823551 Title: unable to upgrade 16.04 -> 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992194] Re: BOM symbols in ru_RU.aff affect some package installation
Still affects Ubuntu 16.04 on installation of Postgres 9.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823551] Re: unable to upgrade 16.04 -> 18.04
/etc/apt/source.list offers no assistance; in addition, I modified sources.list to use official endpoints, and got the same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823551 Title: unable to upgrade 16.04 -> 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823550] Re: Context menu in Pluma wrongly has monospaced font in dropdown menu
The correct (expected) font is presented on the screenshot from Ubuntu MATE 16.04 LTS. ** Attachment added: "correct dropdown menu in Ubuntu MATE 16.04 LTS" https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1823550/+attachment/5253755/+files/pluma-dropdown-1604.png ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Context menu in Pluma wrongly has monospaced font in dropdown menu + Pluma wrongly has monospaced font in dropdown menu ** Summary changed: - Pluma wrongly has monospaced font in dropdown menu + Pluma wrongly has monospaced font in dropdown (context) menu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: Pluma wrongly has monospaced font in dropdown (context) menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1823550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
So after upgrading, I cannot see any abnormal rise in memory consumption. I'm glad I risked it and upgraded. I do not use zsh and am using the latest stable kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/ and the latest available nvidia driver from https://launchpad.net/~graphics-drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also affects Disco ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820074 Title: Running glxgears with Indirect GLX crashes Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823552] [NEW] JS TypeError results in failure to scale windows in activities view
Public bug reported: When I hit the super key or move to the top left corner, I do not get appropriate scaling of the windows. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Disco Dingo (development branch) Release:19.04 Updated as of today. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.0-1ubuntu1 Candidate: 3.32.0-1ubuntu1 Version table: *** 3.32.0-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen For all programs to scale appropriately when I click on the super key or go to the top left corner 4) What happened instead Some programs scale. most do not. Windows that do not scale are also not selectable and can only be switched to using alt-tab. Below is the result of `journalctl -f /usr/bin/gnome-shell` Apr 07 13:37:17 liberty gnome-shell[2512]: JS ERROR: TypeError: this._text is undefined enable/winInjections.relayout<@/home/user/.local/share/gnome-shell/extensions/windowsnaviga...@gnome-shell-extensions.gcampax.github.com/extension.js:227:9 injectToFunction/parent[name]@/home/user/.local/share/gnome-shell/extensions/windowsnaviga...@gnome-shell-extensions.gcampax.github.com/extension.js:16:19 _animateClone@resource:///org/gnome/shell/ui/workspace.js:1389:9 _updateWindowPositions@resource:///org/gnome/shell/ui/workspace.js:1343:17 _realRecalculateWindowPositions@resource:///org/gnome/shell/ui/workspace.js:1259:9 _recalculateWindowPositions/this._positionWindowsId<@resource:///org/gnome/shell/ui/workspace.js:1234:13 Apr 07 13:37:21 liberty gnome-shell[2512]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Apr 07 13:37:21 liberty gnome-shell[2512]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed ** 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/1823552 Title: JS TypeError results in failure to scale windows in activities view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823555] [NEW] Einstein resets multi-screen setup during start
*** This bug is a duplicate of bug 1394323 *** https://bugs.launchpad.net/bugs/1394323 Public bug reported: To reproduce: Connect a second screen Set it up in any configuration that is not 'mirror' Start Einstein What i expect to happen: Either: A) It should start full screen on one of the screens or B) (worse solution) Start as mirrored, but then restore the original layout upon termination What happens The screen layout will become mirrored. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: einstein 2.0.dfsg.2-9build1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 7 21:22:31 2019 InstallationDate: Installed on 2018-11-24 (133 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: einstein UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: einstein (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** This bug has been marked a duplicate of bug 1394323 Einstein breaks the multi-screen display settings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823555 Title: Einstein resets multi-screen setup during start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/einstein/+bug/1823555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
