[Bug 1823346] Re: SD card stays locked even when unlocked

2019-04-07 Thread Kai-Heng Feng
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

[Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-07 Thread Kai-Heng Feng
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

[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1

2019-04-07 Thread Daniel van Vugt
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.

[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1

2019-04-07 Thread Daniel van Vugt
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.

[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

2019-04-07 Thread Daniel van Vugt
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.

[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

2019-04-07 Thread Daniel van Vugt
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

[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

2019-04-07 Thread Michael J
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

[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

2019-04-07 Thread Michael J
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

[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

2019-04-07 Thread Daniel van Vugt
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"

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

2019-04-07 Thread Aleksas Pantechovskis
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

[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

2019-04-07 Thread Daniel van Vugt
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

[Bug 1689578] Re: Lack of shell completion installation support for command line apps

2019-04-07 Thread Buo-ren, Lin
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

[Bug 1820960] Re: No support for armhf/arm64/other ports

2019-04-07 Thread Bug Watch Updater
** 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

[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

2019-04-07 Thread Daniel van Vugt
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 &&

[Bug 1804513] Re: Cosmic: Mixxx 2.1.3 is not stable with Qt5

2019-04-07 Thread Daniel Schürmann
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:

[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

2019-04-07 Thread Daniel van Vugt
** 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.

<    1   2   3   4