[Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
I remember having run firefox and chromium side-by-side once on the same website and noticed the colors were off. The colors on firefox's images matched eog and other local image viewers, while chromium's were skewed. I googled it once and found that setting chrome://flags/#force-color-profile (setting srgb) fixed the issues. This was in like 2019, the flag is not available anymore. Does that have anything to do with it? I believe the chromium change that removed this flag was on the basis of chromium now "properly" handling color profiles from the OS, so I wanted to bring it up. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881415] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image() from st_theme_node_paint_equal() from st_widget_recompute_style()
I think I have this issue, but I'm not 100% sure. I tried to find the crash log in /var/crash, but it looks slightly different. There's no segvanalysis or stacktrace, though I can find a signal 11 crash in /var/log/apport.log. How can I go about confirming this is the bug I'm experiencing? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881415 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_border_image() from st_theme_node_paint_equal() from st_widget_recompute_style() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873541] Re: black screen with cursor on nouveau + i915
** Summary changed: - black screen with cursor and on nouveau + i915 + black screen with cursor on nouveau + i915 ** Summary changed: - black screen with cursor on nouveau + i915 + black screen with cursor on dual nouveau + i915 ** Description changed: - This bug should be able to be reproduced on any computer with i915 + - nouveau simultaneously modesetting, booting to stock gdm3 (wayland by - default). My main example is a MacBookPro6,2 with the infamous GT 330m - on 20.04 with -proposed enabled and booting with the following grub - manipulations to set gmux to the integrated LVDS: + This bug should be able to be reproduced on any computer with both an + nvidia (stock nouveau) and intel igpu (stock i915), booting to stock + gdm3 (wayland by default). My main example is a MacBookPro6,2 with the + infamous GT 330m on 20.04 with -proposed enabled and booting with the + following grub manipulations to set gmux to the integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine-- the only thing broken is the LVDS connection to the internal panel. I disable it with video=LVDS-2:d. --> NOTE: This mod is only for the convenience of not having to deal with a phantom second screen once booted (both GPU's have the LVDS and edid of the internal screen hooked up). The computer boots fine and the bug reproduces exactly the same with or without it. I tested with all these modifications disabled, and this still occurred - it's not specific to my configuration. A user booting stock Ubuntu on this laptop, or as I discovered later, any nouveau + i915 hardware combination will run into this as well. Anyways, I'm keeping the 330m enabled to use DRI_PRIME to run applications on the 330m for good reason- it supports OpenGL 3.3 while HD Graphics (arrandale aka Ironlake) is the only HD Graphics iGPU stuck on OpenGL 2.1, thus otherwise vastly restricting the modern graphics workloads of the system. When explicitly booting with gdm3 WaylandEnable=false (login and desktop both xorg), everything works as expected - single screen driven by the i915's KMS, nouveau with DRI_PRIME working, returning NVA5 stats and functional with OpenGL 3 apps as well. On GDM3 wayland, however (by default-- which is why I think this bug is rather important), gdm3 starts to a black screen with cursor. The login screen and shell still seem to be running-- I can type my password blindly and press enter and the cursor freezes briefly as it does during a non-broken login. After a few seconds, I can press the volume up/down keys and I hear the volume sound. Pressing the app grid shortcut makes the cursor lag, just as it does when I disable the nvidia at the pcie link level and rendering works on i915. Backlight control also works on the login screen and once logged in. It's as if everything except the actual rendering to the screen is working. The minute I pass nouveau.modeset=0 in cmdline, or cut the power to the 330m at the hardware level with outb 0x750, Wayland starts working again. The issue has something to do with GDM3's handling of a KMS- enabled nouveau GPU, whether it is headless or not (no difference with video=LVDS-2:d or not). To confirm my suspicions that it is not specific to the macbook pro line, this exact same issue (Xorg works wayland doesn't) also occurred on a desktop dual-gpu setup, with a GTX 760 (kepler) on nouveau tandem with a Haswell HD Graphics G3258-- with any combination of displays, all on the Intel, mixed on nvidia and intel, or all on nvidia, as long as both cards were modesetting, a black screen with cursor but blindly working gnome followed. This bug has existed since at least 19.04, if not earlier-- I replaced the nvidia gpu in that system with a Radeon 7870 when it ran that release due to this bug, as a matter of fact. ** Description changed: This bug should be able to be reproduced on any computer with both an nvidia (stock nouveau) and intel igpu (stock i915), booting to stock gdm3 (wayland by default). My main example is a MacBookPro6,2 with the infamous GT 330m on 20.04 with -proposed enabled and booting with the following grub manipulations to set gmux to the integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine-- the only thing broken is the LVDS connection to the internal panel. I disable it with video=LVDS-2:d. --> NOTE: This mod is only for the convenience of not having to deal with a phantom second screen once booted (both GPU's have the LVDS and edid of the internal screen hooked up). The
[Bug 1873541] [NEW] black screen with cursor and on nouveau + i915
Public bug reported: This bug should be able to be reproduced on any computer with i915 + nouveau simultaneously modesetting, booting to stock gdm3 (wayland by default). My main example is a MacBookPro6,2 with the infamous GT 330m on 20.04 with -proposed enabled and booting with the following grub manipulations to set gmux to the integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine-- the only thing broken is the LVDS connection to the internal panel. I disable it with video=LVDS-2:d. --> NOTE: This mod is only for the convenience of not having to deal with a phantom second screen once booted (both GPU's have the LVDS and edid of the internal screen hooked up). The computer boots fine and the bug reproduces exactly the same with or without it. I tested with all these modifications disabled, and this still occurred - it's not specific to my configuration. A user booting stock Ubuntu on this laptop, or as I discovered later, any nouveau + i915 hardware combination will run into this as well. Anyways, I'm keeping the 330m enabled to use DRI_PRIME to run applications on the 330m for good reason- it supports OpenGL 3.3 while HD Graphics (arrandale aka Ironlake) is the only HD Graphics iGPU stuck on OpenGL 2.1, thus otherwise vastly restricting the modern graphics workloads of the system. When explicitly booting with gdm3 WaylandEnable=false (login and desktop both xorg), everything works as expected - single screen driven by the i915's KMS, nouveau with DRI_PRIME working, returning NVA5 stats and functional with OpenGL 3 apps as well. On GDM3 wayland, however (by default-- which is why I think this bug is rather important), gdm3 starts to a black screen with cursor. The login screen and shell still seem to be running-- I can type my password blindly and press enter and the cursor freezes briefly as it does during a non-broken login. After a few seconds, I can press the volume up/down keys and I hear the volume sound. Pressing the app grid shortcut makes the cursor lag, just as it does when I disable the nvidia at the pcie link level and rendering works on i915. Backlight control also works on the login screen and once logged in. It's as if everything except the actual rendering to the screen is working. The minute I pass nouveau.modeset=0 in cmdline, or cut the power to the 330m at the hardware level with outb 0x750, Wayland starts working again. The issue has something to do with GDM3's handling of a KMS- enabled nouveau GPU, whether it is headless or not (no difference with video=LVDS-2:d or not). To confirm my suspicions that it is not specific to the macbook pro line, this exact same issue (Xorg works wayland doesn't) also occurred on a desktop dual-gpu setup, with a GTX 760 (kepler) on nouveau tandem with a Haswell HD Graphics G3258-- with any combination of displays, all on the Intel, mixed on nvidia and intel, or all on nvidia, as long as both cards were modesetting, a black screen with cursor but blindly working gnome followed. This bug has existed since at least 19.04, if not earlier-- I replaced the nvidia gpu in that system with a Radeon 7870 when it ran that release due to this bug, as a matter of fact. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: gdm3 kms nouveau.i915 ** Description changed: - MacBookPro6,2 with the infamous GT 330m and booting with the following - grub manipulations to set gmux to the integrated LVDS: + MacBookPro6,2 with the infamous GT 330m on 20.04 with -proposed enabled + and booting with the following grub manipulations to set gmux to the + integrated LVDS: outb 0x710 2 - switch LVDS to intel outb 0x728 1 - switch internal DDC to intel outb 0x740 2 - switch displayport out to intel I am not using outb 0x750 0, so that the 330m remains powered on. It still works just fine headless - I accomplished that by setting video=LVDS-2:d (disabling the non-functioning LVDS link from the nvidia to the internal screen). *I tested with all these modifications disabled, and this still occurred* - it's not specific to my configuration. A user booting stock Ubuntu on this laptop, or as I discovered later, any nouveau + i915 hardware combination will run into this as well. Anyways, I'm disabling the LVDS purely out of convenience so I can use DRI_PRIME to run applications on the 330m for good reason- it supports OpenGL 3.3 while HD Graphics (arrandale aka Ironlake) is the only HD Graphics iGPU stuck on OpenGL 2.1, thus vastly restricting the modern graphics workloads of the system. When booting with gdm3 WaylandEnable=false (login and desktop both xorg), everything works as expected - single screen driven by the i915's KMS, headless nouveau with DRI_PRIME working, returning NVA5 stats and functional with
[Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys
I currently experience this issue on an up-to-date 18.04 install. I came across this bug while googling for "gnome volume overlay wobble". It also affects the other two overlays that I can use (screen brightness and keyboard backlight.) I was able to record in in 60fps so as to make it more evident. Just wanted to share my experience on the most updated as possible Ubuntu. ** Attachment added: "Wobble screen recording" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1692394/+attachment/5129593/+files/wobble.mkv -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1692394 Title: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1692394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
Fresh install Ubuntu 15.10 - still happening.. Assume only fixed in 16.04 correct? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 835468] Re: gnome-settings-daemon crashed with SIGFPE in g_main_context_dispatch()
*** This bug is a duplicate of bug 835351 *** https://bugs.launchpad.net/bugs/835351 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/835468 Title: gnome-settings-daemon crashed with SIGFPE in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/835468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
