[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 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 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 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 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 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 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 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 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 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 1820960] Re: No support for armhf/arm64/other ports
** Changed in: calamares Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820960 Title: No support for armhf/arm64/other ports To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1820960/+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
Re comment #10, the crash still happens with mutter 3.32.0-1ubuntu2~randr+test2: Apr 07 14:24:04 kab org.gnome.Shell.desktop[1615]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:168:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Apr 07 14:24:05 kab org.gnome.Shell.desktop[1625]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:168:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Apr 07 14:25:25 kab org.gnome.Shell.desktop[1940]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:168:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Apr 07 14:25:26 kab org.gnome.Shell.desktop[1950]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:168:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** 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/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 1804513] Re: Cosmic: Mixxx 2.1.3 is not stable with Qt5
Thank you very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804513 Title: Cosmic: Mixxx 2.1.3 is not stable with Qt5 To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1804513/+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
** Changed in: budgie-desktop (Ubuntu) Status: Won't Fix => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Invalid -- 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
