[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
Hi, this issue happens to me to. But I figured it out that this only happens in vertical multi-monitor setup with the dock on the left or on the right. If I move the dock to the bottom, the issue disappears. So that could be a temporary workaround for you until this bug is solved. -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863614] Re: file-roller crashed with SIGSEGV in _gdk_window_has_impl()
[Expired for file-roller (Ubuntu) because there has been no activity for 60 days.] ** Changed in: file-roller (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1863614 Title: file-roller crashed with SIGSEGV in _gdk_window_has_impl() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1863614/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1854346] Re: No choice can be made to format non-listed file type
** Changed in: gnome-disk-utility Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1854346 Title: No choice can be made to format non-listed file type To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1854346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
** No longer affects: gnome-shell (Ubuntu Bionic) ** No longer affects: gnome-shell (Ubuntu) -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf under 20.04 has no impact on the autologin bug with nvidia-340. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
Tracked upstream with further information: https://github.com/micheleg /dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1136 https://github.com/micheleg/dash-to-dock/issues/1136 -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873530] Re: Super-key not opening application overview on secondary keyboard layouts
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 ** This bug has been marked a duplicate of bug 1871913 super key does not work with secondary keyboard layout -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873530 Title: Super-key not opening application overview on secondary keyboard layouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873424] Re: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04
Thanks! ** Changed in: eog (Ubuntu) Status: Confirmed => Triaged -- 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/1873424 Title: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1873424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873530] [NEW] Super-key not opening application overview on secondary keyboard layouts
Public bug reported: After upgrading to Ubuntu 20.04 the super-key is no longer opening the activities overview when the keyboard layout is set to a secondary layout. After switching the order of the layouts I use around the issue kept persisting only on the (new) secondary layout. I would expect the super-key behaviour to be consistent across all keyboard layouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 23:39:32 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-24 (418 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-17 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873530 Title: Super-key not opening application overview on secondary keyboard layouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867302] Re: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.86
I don't think it's fixed/repaired. I have the same error. dpkg -l | grep gnome-cale ii gnome-calendar3.36.0-1 amd64Calendar application for GNOME I am not sure if my logs (G_MESSAGES_DEBUG=all gnome-calendar) are safe to share (these entries look like credentials to me: (...) gnome-calendar:70444): GcalEvent-DEBUG: 23:02:26.562: 953cb9f07c1c((:46290()@google.com:20200501T083000 (...) (gnome-calendar:70444): dconf-DEBUG: 23:02:38.137: change_fast (gnome-calendar:70444): dconf-DEBUG: 23:02:38.137: change_notify: /org/gnome/calendar/active-view (gnome-calendar:70444): GcalTimeZoneMonitor-DEBUG: 23:02:38.781: System timezone is Europe/Warsaw (gnome-calendar:70444): GcalSearchEngine-DEBUG: 23:02:38.781: Timezone changed (gnome-calendar:70444): dconf-DEBUG: 23:02:39.650: change_fast (gnome-calendar:70444): dconf-DEBUG: 23:02:39.650: change_notify: /org/gnome/calendar/active-view ^F(gnome-calendar:70444): GcalClock-DEBUG: 23:03:00.545: Updating clock time (gnome-calendar:70444): GcalClock-DEBUG: 23:03:00.546: Scheduling update for 60 seconds (gnome-calendar:70444): GcalWindow-DEBUG: 23:03:07.407: Updating active date to 17.04.2020 23:03:07 +0200 (gnome-calendar:70444): GcalEvent-CRITICAL **: 23:03:07.472: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:70444): GcalEvent-CRITICAL **: 23:03:07.472: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed Segmentation fault -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1867302 Title: gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed (gnome-calendar:32235): GcalEvent-CRITICAL **: 21:08:09.868: gcal_event_is_multiday: assertion 'GCAL_IS_EVENT (self)' failed Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1867302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873525] [NEW] Gnome 3.36 with two monitors
Public bug reported: After upgrading to 20.04, the "Activities" menu had display problems. Tracked upstream: https://github.com/micheleg/dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873525 Title: Gnome 3.36 with two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
No fractional scaling is enabled. I eventually started just not using fullscreen to avoid the flashing annoyance. I have since upgraded to 20.04. I see now that when I put an app into fullscreen, I no longer see the flashing I reported in this issue. So my guess is something was fixed in focal. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873424] Re: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04
Thanks for looking at this bug. I now reported it upstream at https://gitlab.gnome.org/GNOME/eog/-/issues/124. ** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #124 https://gitlab.gnome.org/GNOME/eog/-/issues/124 ** Also affects: eog via https://gitlab.gnome.org/GNOME/eog/-/issues/124 Importance: Unknown Status: Unknown -- 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/1873424 Title: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1873424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1205 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro 3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is shown instead. While the login works fine at the point, restarting then causes the system to hang rather than completing the restart. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872851] Re: GNOME Contacts 3.36 is broken (can't get past welcome screen), needs one line upstream fix
Upstream GNOME Contacts 3.36.1 was just released with fix for the welcome screen issue, so another possible solution for this issue is to wait for the package to be updated to 3.36.1 in Debian, then sync it into Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1872851 Title: GNOME Contacts 3.36 is broken (can't get past welcome screen), needs one line upstream fix To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1872851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872844] Re: Changing theme Light<->Standard preserves theme for title bar
And it's not firefox-specific, chrome is also affected. ** Attachment added: "Screencast from 04-17-2020 08:39:16 PM.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872844/+attachment/5356256/+files/Screencast%20from%2004-17-2020%2008%3A39%3A16%20PM.webm ** Attachment removed: "Screencast from 17.04.2020 20:20:49.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872844/+attachment/5356254/+files/Screencast%20from%2017.04.2020%2020%3A20%3A49.webm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872844] Re: Changing theme Light<->Standard preserves theme for title bar
Yes, here is a screencast of this bug. See how title bar theme persists when switching from standard to white ** Attachment added: "Screencast from 17.04.2020 20:20:49.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872844/+attachment/5356254/+files/Screencast%20from%2017.04.2020%2020%3A20%3A49.webm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873493] Re: icons missing from main and internal pages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1873493 Title: icons missing from main and internal pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1873493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873493] Re: icons missing from main and internal pages
** Summary changed: - icons missings from recent releases section + icons missing from main and internal pages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1873493 Title: icons missing from main and internal pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1873493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873493] Re: icons missings from recent releases section
Clicking the more button also shows missing icons ** Attachment added: "software store mising icons.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1873493/+attachment/5356238/+files/software%20store%20mising%20icons.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1873493 Title: icons missing from main and internal pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1873493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873493] [NEW] icons missing from main and internal pages
Public bug reported: The recent releases category on the homepage of software on Xubuntu 20.04 has no icons. https://bluesabre.org/content/images/2020/04/desktop-06-software.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 17 20:36:46 2020 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1873493 Title: icons missing from main and internal pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1873493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, Thank you for coming back to me so fast. I don't think it's related to either of those bugs you mentioned. This is happening only when I'm running virtual machines and have "virt- manager" opened. Is it a bug in gnome-shell? It's difficult to say. I'm not experiencing the issue with non-desktop VMs (no X) so it might be something in X11. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873483] [NEW] Screensaver locks when advancing to YouTube's next autoplay video
Public bug reported: So I'm watching YouTube videos, and I have autoplay enabled, so when it gets to the end of one, it lingers for a moment then jumps right into another. While watching a video, the screensaver is inhibited, as it should be. Because most of these videos are considerably longer than my lock period. But during that jump, there's an instant where there isn't technically a video playing, and since I haven't touched the keyboard in a while, BAM, the screensaver springs into action. And I'm sitting here during the intro of the next video, listening to the theme and narrator, and going "Well that's interesting, is he leading with a black screen for some narrative reason?" until I bump the mouse and there's my lockscreen... In this situation, the end of the video-is-playing status should have a moment of holdoff before killing the screen, in case another video starts playing a few milliseconds later. Ubuntu 18.04 LTS, gnome-screensaver 3.6.1-8ubuntu3, Firefox 75.0. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1873483 Title: Screensaver locks when advancing to YouTube's next autoplay video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1873483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873429] Re: Problem with printing in 20.04 version
** Package changed: gnome-control-center (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873429 Title: Problem with printing in 20.04 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1873429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873424] Re: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04
Thank you for your bug report, could you report it upstream on https://gitlab.gnome.org/GNOME/eog/issues/ ** Changed in: eog (Ubuntu) Importance: Undecided => Low ** Changed in: eog (Ubuntu) Status: New => Confirmed -- 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/1873424 Title: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1873424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "co
Ubuntu 19.10, mutter-3.34.3-1ubuntu1~19.10.1 and still crash sometimes with IntelliJ -- apr 17 16:40:45 delphy gnome-shell[2612]: ** apr 17 16:40:45 delphy gnome-shell[2612]: mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should be NULL apr 17 16:40:45 delphy gnome-shell[2612]: Bail out! mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should be NULL apr 17 16:40:45 delphy gnome-shell[2612]: GNOME Shell crashed with signal 6 apr 17 16:40:45 delphy gnome-shell[2612]: == Stack trace for context 0x56084b40d3b0 == apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Failed with result 'core-dump'. apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Service has no hold-off time (RestartSec=0), scheduling restart. apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 1. apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session (session: ubuntu). apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session (session: ubuntu). apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session. apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session. apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME Shell on X11. apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME Shell on X11. apr 17 16:40:45 delphy systemd[2342]: Stopped GNOME Shell on X11. apr 17 16:40:45 delphy systemd[2342]: Starting GNOME Shell on X11... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866088] Re: Problems with the Dock setting of "Show on" in the Appearance tab
Fix is at https://salsa.debian.org/gnome-team/gnome-control- center/-/merge_requests/16 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1866088 Title: Problems with the Dock setting of "Show on" in the Appearance tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1866088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868872] Re: Nautilus Cant open files in shared folders
Could you try if https://launchpad.net/ubuntu/+source/glib2.0/2.64.2-1~fakesync1 fixes it? it sounds similar to the most recent comment in bug #1869881 -- 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/1868872 Title: Nautilus Cant open files in shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873462] [NEW] gimp crashes 90% if i want to scale a pic in a layer
Public bug reported: Betriebssystem: Kubuntu 19.10 KDE-Plasma-Version: 5.16.5 KDE-Frameworks-Version: 5.62.0 Qt-Version: 5.12.4 Kernel-Version: 5.3.0-46-generic Art des Betriebssystems: 64-bit Prozessoren: 4 × Intel® Xeon® CPU X3220 @ 2.40GHz Speicher: 3,8 GiB Arbeitsspeicher ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1873462 Title: gimp crashes 90% if i want to scale a pic in a layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1873462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873454] Re: /usr/bin/gnome-control-center:11:cc_panel_get_title_widget:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke
*** This bug is a duplicate of bug 1862553 *** https://bugs.launchpad.net/bugs/1862553 ** This bug has been marked a duplicate of bug 1862553 gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873454 Title: /usr/bin/gnome-control- center:11:cc_panel_get_title_widget:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873454] Re: /usr/bin/gnome-control-center:11:cc_panel_get_title_widget:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Description changed: + Test Case + 1. On a fresh installation of Ubuntu Desktop Focal run software-properties-gtk + 2. Go to the tab "Livepatch" + 3. Click on the button "Sign in..." + 4. A dialog box opens to use an Ubuntu One account. Click on "Sign In / Register" + + Expected result: + The user can register his U1 account. + + Actual result: + This crash + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.1-1ubuntu5, the problem page at https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873454 Title: /usr/bin/gnome-control- center:11:cc_panel_get_title_widget:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868872] Re: Nautilus Cant open files in shared folders
Sorry Sebastian for some reason i don't received an email with your questions. - I only see this in .doc files in shared folders. PDF opens ok - the access is smb:// - I will post try to post the journal later - The error says: no app cant open the file "nameof the file".doc the file is of an unknown type -- 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/1868872 Title: Nautilus Cant open files in shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873454] [NEW] /usr/bin/gnome-control-center:11:cc_panel_get_title_widget:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke
Public bug reported: Test Case 1. On a fresh installation of Ubuntu Desktop Focal run software-properties-gtk 2. Go to the tab "Livepatch" 3. Click on the button "Sign in..." 4. A dialog box opens to use an Ubuntu One account. Click on "Sign In / Register" Expected result: The user can register his U1 account. Actual result: This crash The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.36.1-1ubuntu5, the problem page at https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: High Status: Confirmed ** Tags: bionic disco eoan focal rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873454 Title: /usr/bin/gnome-control- center:11:cc_panel_get_title_widget:activate_panel:set_active_panel_from_id:launch_panel_activated:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873398] Re: gnome-disks won't do SMART on NVME drive
Thank you for your bug report, indeed that's a known issue, see upstream report https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/50 which requires udisks work, see https://github.com/storaged-project/udisks/issues/386 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #50 https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/50 ** Bug watch added: github.com/storaged-project/udisks/issues #386 https://github.com/storaged-project/udisks/issues/386 ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Triaged ** Also affects: gnome-disk-utility via https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/50 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1873398 Title: gnome-disks won't do SMART on NVME drive To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1873398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866841] Re: [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
Jeremy, I have changed this bug name and description to a SRU. Is there anything else needed to do from my side? Should I subscribe ~ubuntu-sru to this bug? ** Summary changed: - Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends + [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends ** Description changed: - Please, consider adding the chrome-gnome-shell package as a recommended - dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome- - shell package provides GNOME Shell integration (connector) for Firefox, - Chrome, Chromium and other web browsers that is necessary for users to - be able to manage GNOME Shell extensions using a extensions.gnome.org - website. Since the Shell Extensions support was removed from gnome- - software since 3.36 and the replacement Extensions application cannot be - used to find and install new extensions, there is not any user friendly - way to install new Shell Extensions without having the chrome-gnome- - shell package installed. + [Impact] - More information: - https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome + * Since GNOME 3.36, Shell Extensions can no longer be installed using + GNOME Software (Ubuntu Software), instead there was a new Extensions + (gnome-shell-extension-prefs) application prepared to replace this + functionality. However, this application itself does not support + installing new extensions, instead, it opens a web browser with a + extensions.gnome.org website that allows browsing and installing new + extensions. This website depends on a chrome-gnome-shell package that + provides GNOME Shell integration (connector) for Firefox, Chrome, + Chromium and other web browsers for this functionality. Without this + connector, it is not possible to install Shell Extensions on Ubuntu + 20.04. + + * In this SRU, I want to propose adding this chrome-gnome-shell package + to recommends of the gnome-shell-extension-prefs package. However, since + the gnome-shell-extension-prefs package is in a main repository and + chrome-gnome-shell is in universe, it would be probably also needed to + first move the gnome-shell-extension-prefs package to universe. + + [Test Case] + + * Install the "gnome-shell-extension-prefs" (Extensions) application. + + * Open the "Extensions" application, click the "i" button in the window + header, click the "extensions.gnome.org" link. + + * In the web browser window, click on link inside the blue notification + on extensions.gnome.org to install a browser extension (frontend for the + connector), then refresh the page. + + * After this, a red notification appears on the web page telling the + user that host connector is not running. + + [Regression Potential] + + * Without the chrome-gnome-shell package installed, it is not possible + to install Shell Extensions on Ubuntu 20.04. + + [Other Info] + + * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome ** Description changed: [Impact] - * Since GNOME 3.36, Shell Extensions can no longer be installed using + * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. - * In this SRU, I want to propose adding this chrome-gnome-shell package + * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] - * Install the "gnome-shell-extension-prefs" (Extensions) application. + * Install the "gnome-shell-extension-prefs" (Extensions) application. - * Open the "Extensions" application, click the "i" button in the window + * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. - * In the web browser window, click on link inside the blue notification + * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. - * After this, a red notification appears on the web page
[Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
The release is next week, the title is just being updated in preparation, it doesn't matter really -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872851] Re: GNOME Contacts 3.36 is broken (can't get past welcome screen), needs one line upstream fix
(I have changed the bug description to better reflect the issue including its fix.) ** Summary changed: - GNOME Contacts can't get past welcome screen + GNOME Contacts 3.36 is broken (can't get past welcome screen), needs one line upstream fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1872851 Title: GNOME Contacts 3.36 is broken (can't get past welcome screen), needs one line upstream fix To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1872851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1873266/+attachment/5356137/+files/ProcCpuinfoMinimal.txt ** Changed in: mutter (Ubuntu) Status: Incomplete => Opinion ** Changed in: mutter (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873266 Title: cannot change main monitor after setting scaling for monitors w/nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: cannot change main monitor after setting scaling for monitors w/nvidia drivers
apport information ** Tags added: apport-collected focal package-from-proposed ** Description changed: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard-reboot (though I could probably try switching ttys, etc). - This is with focal and focal-proposed enabled. I also have the - proprietary 440 nvidia drivers enabled, and I'm using default gnome with - x11. + This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-07-05 (287 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: nvidia-graphics-drivers-440 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 + Tags: focal package-from-proposed + Uname: Linux 5.4.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1873266/+attachment/5356136/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873266 Title: cannot change main monitor after setting scaling for monitors w/nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
I'd like to suggest that you don't fix it by moving the dot but by replacing the dot with a treatment of the text (bold, underline, italics, color) because that fix would never break due to resolution. -- 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/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
Confirming that this issue happens on my 1366x786 laptop screen but not my 1600 x 900 monitor. -- 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/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
I just saw, that it is not Ubuntu 20.04 beta, it is the real Ubuntu 20.04 now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
Thanks Dirk, a new report would probably better to avoid confusion. Can you see the content of that same mount doing $ smbclient //192.168.178.1/sharename ? if it fails could you add --debuglevel=10 and attach the log to the report? (and ideally reporting upstream gvfs would make sense) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
Again: gvfs-backends is installed (it was removed without my knowledge during the update from Ubuntu 19.10 to 20.04 beta). Perhaps you should not install a beta version on a productive system ;-) When I want to mount the drive as in Ubuntu 19.10, I get: $ gio mount smb://192.168.178.1/sharename Password required for share sharename on 192.168.178.1 User [SessionUserName]: NewUserIfDifferent Domain [WORKGROUP]: NewDomainIfDifferent Password: PassWord In Ubuntu 20.04 beta I still get (after manual installation of `gvfs- backends`, which was removed during the update from 19.10 to the beta $ gio mount smb://192.168.178.1/sharename gio: smb://192.168.178.1/sharename/: Failed to mount Windows share: Software caused connection abort So, Ubuntu 20.04 does not request to enter the user, domain/workgroup, password at all. Remark: I could mount the drive via "sudo mount -t cifs ..." using the "vers=1.0" switch in all Ubuntu versions, also in 20.04 beta. Should I open a new bug? The error and it's error message is now different. That the beta installer did remove the package `gvfs- backends`, I will not test again, because I have only productive 19.10 systems. I had several small glitches during the installation, so also the repositories were grilled away but one - I am doing this since 2008 at least twice a year on at least 2 laptops, mostly I start with the beta version. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873429] Re: Problem with printing in 20.04 version
** Package changed: ubuntu => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873429 Title: Problem with printing in 20.04 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873429] [NEW] Problem with printing in 20.04 version
You have been subscribed to a public bug: In previous 19.10 my Epson Stylus CX3600 both prints & scans fine. In 20.04 it scans fine, but in print mode the process banners show the job is sent to the printer, then printing is complete. However there is no print output. I reinstalled the Epson print drivers but without success. I'm staying on 20.04, but by running Ubuntu 19.10 from a USB drive the printing issue is solved. The Epson is recognised and my documents print and scan fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 10:59:10 2020 InstallationDate: Installed on 2019-12-10 (128 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-01 (15 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Problem with printing in 20.04 version https://bugs.launchpad.net/bugs/1873429 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866841] Re: Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
** Summary changed: - Add chrome-gnome-shell to ubuntu-desktop recommends + Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1866841 Title: Move gnome-shell-extension-prefs to universe and add chrome-gnome- shell to its recommends To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873326] Re: Icons in the appindicator are too small
>From comments to the upstream issue, it follows that the decrease of the icon size was done intentionally. Though I am not sure that this is reasonable decision, marking the issue as NotABug since this is by- design. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1873326 Title: Icons in the appindicator are too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1873326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] Re: xorg lock-up on GPU hotplug
Point is, there is no crash file. Graphical environment is not responsive, but nothing seems to have crashed. If there's a stacktrace or core file needed, no problem, I can rebuild in debug mode, attach debugger and gather those. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873401 Title: xorg lock-up on GPU hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873394] Re: Terminal does not respond to theme changes
This is intended. Gnome-terminal is shipped with "prefer-dark" enabled, so it keeps the dark theme unless you change the application configuration clicking on options (the "hamburger" menu) > preferences > theme variant menu ** Changed in: yaru-theme (Ubuntu) Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873394 Title: Terminal does not respond to theme changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
https://gitlab.gnome.org/GNOME/mutter/-/issues/1113 https://github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/issues/198 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1204 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1113 https://gitlab.gnome.org/GNOME/mutter/-/issues/1113 ** Bug watch added: github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/issues #198 https://github.com/Tudmotu/gnome-shell-extension-clipboard-indicator/issues/198 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873424] [NEW] Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04
Public bug reported: In Ubuntu 19.10 I was able to view HEIF/HEIC files in Eye of Gnome by installing an appropriate gdk-pixbuf loader. In Ubuntu 20.04 eog just shows the message "Could not load image . Unrecognized image file format". The HEIF gdk-pixbuf loader itself seems to work correctly, because gcpicview is able to display HEIF images even on Ubuntu 20.04. It's just eog that doesn't seem to use the loader anymore. I attached an example file 2020-04-11-14-45-361180.heic. This command works and displays the file: gpicview 2020-04-11-14-45-361180.heic This command shows the error message mentioned above: eog 2020-04-11-14-45-361180.heic Installed versions: eog: Installed: 3.36.1-1 Candidate: 3.36.1-1 Version table: *** 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status heif-gdk-pixbuf: Installed: 1.6.1-1build1 Candidate: 1.6.1-1build1 Version table: *** 1.6.1-1build1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status libheif1: Installed: 1.6.1-1build1 Candidate: 1.6.1-1build1 Version table: *** 1.6.1-1build1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2020-04-11-14-45-361180.heic" https://bugs.launchpad.net/bugs/1873424/+attachment/5356034/+files/2020-04-11-14-45-361180.heic -- 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/1873424 Title: Regression: eog cannot open files via gdk-pixbuf loader in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1873424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Also, this may overlap with bug 1852183. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Please also follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment If the freeze you experience is a crash somewhere (like bug 1872254 originally reported "everything froze when attempting to use the clipboard") then the issue will be clearer. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
I'm not sure gnome-shell is responsible here. Are you able to reproduce the same issue if the host is not using gnome-shell? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] [NEW] hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Public bug reported: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
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 Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] Re: xorg lock-up on GPU hotplug
If the HW cursor still moves then it's not Xorg that's locked/frozen/crashed, it is gnome-shell (via the mutter project). ** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873401 Title: xorg lock-up on GPU hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] Re: xorg lock-up on GPU hotplug
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: displaylink -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873401 Title: xorg lock-up on GPU hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
See also bug 1873403. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set fractional scaling values
WORKAROUND: 1. Ctrl+Alt+F4 and log into a text console. 2. rm ~/.config/monitors.xml 3. sudo reboot ** Summary changed: - [nvidia] Screen turns off when trying to set fractional scaling values + [nvidia] Screen turns off when trying to set some fractional scaling values -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set fractional scaling values
Weirdly, I can set 125% OK, but the screen turns off if I set 150%. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Oh, no 125% doesn't really work either. That just triggers bug 1870736. ** Description changed: - [nvidia] Screen turns off when trying to switch to fractional scaling - values. + When the nvidia driver is installed, the screen turns off when trying to + set some fractional scaling values like 150%. And it stays off even + after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) -1920x1200 59.95 + 59.88 + 1920x1200 59.95 + 59.88 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Oh, not 125% doesn't really work either. That just triggers bug 1870736. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873407] [NEW] totem warns every time: "Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)
Public bug reported: I am running Ubuntu 20.04 beta amd64 Desktop from the liveCD ISO. Whenever I run totem from a shell window to play a video, I get on stderr: "(totem:13002): Gtk-WARNING **: 07:50:52.916: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)" This has also been happening in totem in Ubuntu 18.04.4 LTS for years. I was shocked when I first ran it on 20.04 that apparently nobody else noticed this error. It happens every single time I run totem, as soon as it actually opens a video and starts playing it. For example, I made a screencast for a few seconds (with Ctl-Alt- Shift-R) and then played it from "totem ~/Videos/Screencast*.webm", and this error came out on stderr. If I just run "totem &" the error doesn't come out -- until I select a video from totem's interface. Once I pick one and play it, then the error comes out on the terminal screen where I typed the totem command. Is there supposed to be a slider for scaling the video? That would be a nice feature, but no slider appears, possibly due to this bug... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:46:58 2020 ExecutablePath: /usr/bin/totem LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1873407 Title: totem warns every time: "Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1873407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] [NEW] [nvidia] Screen turns off when trying to set some fractional scaling values
Public bug reported: When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug black-screen champagne focal nvidia xrandr-scaling ** Tags added: black-screen ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [nvidia] Screen turns off when trying to switch to fractional scaling values + [nvidia] Screen turns off when trying to set fractional scaling values -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873401] [NEW] xorg lock-up on GPU hotplug
You have been subscribed to a public bug: Discovered when testing EVDI-backed screen (https://github.com/DisplayLink/evdi). While adding new device /dev/dri/cardX xorg locks, it can be observed by the cursors that stop blinking or menus not responding. Sometimes it is just a short (1-2 sec.) pause, but sometimes (hard to state the exact reproduction rate, rather rarely) the screen stops completely. Interestingly enough, if using HW cursor, it moves fine. Keyboard is at least partially functional, as it's possible to "bail out" to tty with C-A-Fx and kill the session. Anything else is difficult to check, as nothing really happens on the screen, it just remains frozen. When adding 4 GPUs at once (e.g. via config in /etc/modprobe.d according to https://support.displaylink.com/knowledgebase/articles/1843660-screen-freezes-after-opening-an-application-only). Haven't checked other numbers yet, to be done soon. The problem occurs, when adding the devices, not enabling their associated screens/reading EDID or anything like that. Also, to be checked with UDL, similar behaviour is expected, but due to the fact that it adds only a single device at a time reproducing "complete" freeze might be difficult. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 09:24:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415) MachineType: Dell Inc. Dell Precision M3800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=e0a7aba8-1c09-4367-9d6b-c74b73017fb4 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- xorg lock-up on GPU hotplug https://bugs.launchpad.net/bugs/1873401 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847112] Re: gnome-control-center SIGSEGV in cc_display_config_set_minimum_size() when used outside of GNOME
This bug is now fixed in focal. It has been marked as fixed in a duplicate bug report. How about closing this report? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1847112 Title: gnome-control-center SIGSEGV in cc_display_config_set_minimum_size() when used outside of GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1847112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869750] Re: [nvidia] Screens turn off when setting display scaling to 200%
Actually the problems continue in bug 1873403. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1869750 Title: [nvidia] Screens turn off when setting display scaling to 200% To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1869750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847112] Re: gnome-control-center SIGSEGV in cc_display_config_set_minimum_size() when used outside of GNOME
Thanks Laurent, closing! ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1847112 Title: gnome-control-center SIGSEGV in cc_display_config_set_minimum_size() when used outside of GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1847112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
** Summary changed: - Screen scaling 125% gives 200% (nvidia) + [nvidia] Screen scaling 125% gives 200% -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873402] [NEW] Can't connect to google account (The name :1.10 was not provided by any .service files)
Public bug reported: Can't connect to google account (Calendar, Mail doesn't matter) always got error "The name :1.10 was not provided by any .service files" On Ubuntu 18.04 all is ok ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: evolution 3.34.1-2 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 17 10:50:42 2020 InstallationDate: Installed on 2020-01-06 (101 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1873402 Title: Can't connect to google account (The name :1.10 was not provided by any .service files) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1873402/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870735] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size()
*** This bug is a duplicate of bug 1847112 *** https://bugs.launchpad.net/bugs/1847112 Thanks a lot for the fix! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870735 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
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 Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873398] [NEW] gnome-disks won't do SMART on NVME drive
Public bug reported: I'm running 20.04 beta amd64 Desktop from a USB stick of the live ISO. I opened Disks (gnome-disks) and it sees all my drives, but it won't show SMART stats on my NVME drive (Samsung SSD 970 EVO Plus 500GB). The SMART menu item is greyed out. It works fine on other drives. The NVME has SMART support; it works fine with smartctl -a /dev/nvme0n1 for example. (Though smartctl is not in this live ISO, I have apt-get installed it at another time and tried it; and it works fine in the Ubuntu 18.04 that is installed on this machine.) I've attached a screencast showing the failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 07:32:43 2020 ExecutablePath: /usr/bin/gnome-disks LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screencast of Disks failing to show SMART data on NVME drive" https://bugs.launchpad.net/bugs/1873398/+attachment/5355919/+files/Screencast%20from%2004-17-20%2007%3A38%3A22.webm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1873398 Title: gnome-disks won't do SMART on NVME drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1873398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869881] Re: html file detected as unknown application/octet-stream
perfect now it works! -- 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/1869881 Title: html file detected as unknown application/octet-stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1869881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1416751] Re: gnome-terminal randomly refuses input
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1416751 Title: gnome-terminal randomly refuses input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1416751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865071] Re: Power indicator doesn't show when charging (eoan)
Thank you for your bug report. Could you add a 'upower -d' log when getting the issue? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1865071 Title: Power indicator doesn't show when charging (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868155] Re: Banner text and user list functionality seem broken
Thanks. On the upstream report you wrote that disable-user-list is working, so did you get that one resolved? is the only issue remaining the banner one? ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Importance: Low => High -- 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/1868155 Title: Banner text and user list functionality seem broken To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873394] [NEW] Terminal does not respond to theme changes
Public bug reported: Terminal does not respond to theme changes. In the Settings app > Appearance > Window theme, I can select Light, Standard or Dark. Changing this setting seems to affect all other apps but not Terminal. ** Affects: gnome-terminal (Ubuntu) Importance: Low Status: New ** Affects: yaru-theme (Ubuntu) Importance: Low Status: New ** Tags: focal ** Description changed: Terminal does not respond to theme changes. - In the Settings app > Appearance > Window theme I can select Light, + In the Settings app > Appearance > Window theme, I can select Light, Standard or Dark. Changing this setting seems to affect all other apps but not Terminal. ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873394 Title: Terminal does not respond to theme changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868083] Re: gnome-shell establishes https connections to extensions.gnome.org
** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low -- 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/1868083 Title: gnome-shell establishes https connections to extensions.gnome.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868083/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872844] Re: Changing theme Light<->Standard preserves theme for title bar
I can't seem to reproduce any bug here. Can you provide a screenshot of the problem you see? ** Tags added: focal ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872861] Re: Sound applet won't change output device
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 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 1866194, 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 1866194 External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872861 Title: Sound applet won't change output device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872779] Re: apparence should change the shell theme
*** This bug is a duplicate of bug 1842886 *** https://bugs.launchpad.net/bugs/1842886 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 1842886, 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 1842886 Yaru-dark shell menus and dialogs are not dark -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872779 Title: apparence should change the shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871868] Re: Shell dialog text is truncated and ellipsized
** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged -- 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/1871868 Title: Shell dialog text is truncated and ellipsized To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1871868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869897] Re: missing ssh prompt to touch yubikey device when using gnome
** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1869897 Title: missing ssh prompt to touch yubikey device when using gnome To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873378] Re: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc()
Thank you for your bug report. The segfault is in the user panels and it had an empty name on refresh. Where you adding or removing users from a command line or another interface when the issue happened? ** Information type changed from Private to Public ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873378 Title: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
